Viptel sub-interface ping doesnt work. So TLOC Extension doesn't work
Posted: Mon Mar 23, 2020 2:34 am
Hello Boss,
As there is one requirement for using sub-interface running TLOC Extension.
ping doesn't work in sub-interface
Can you give me same advice ?
Thanks a lot
version:18.3.3
vEdge1:
0 ge0/7 ipv4 - Up Up NA -
0 ge0/7.10 ipv4 10.193.197.244/31 Up Up NA -
vedge1# ping 10.193.197.245 (ping p2p fail)
Ping in VPN 0
PING 10.193.197.245 (10.193.197.245) 56(84) bytes of data.
From 10.193.197.244 icmp_seq=1 Destination Host Unreachable
From 10.193.197.244 icmp_seq=2 Destination Host Unreachable
vedge1# ping 10.193.197.244 (ping itself , it is ok)
Ping in VPN 0
PING 10.193.197.244 (10.193.197.244) 56(84) bytes of data.
64 bytes from 10.193.197.244: icmp_seq=1 ttl=64 time=0.018 ms
64 bytes from 10.193.197.244: icmp_seq=2 ttl=64 time=0.048 ms
vedge2# show interface descriptio
0 ge0/7 ipv4 - Up Up NA -
0 ge0/7.10 ipv4 10.193.197.245/31 Up Up NA -
As there is one requirement for using sub-interface running TLOC Extension.
ping doesn't work in sub-interface
Can you give me same advice ?
Thanks a lot
version:18.3.3
vEdge1:
0 ge0/7 ipv4 - Up Up NA -
0 ge0/7.10 ipv4 10.193.197.244/31 Up Up NA -
vedge1# ping 10.193.197.245 (ping p2p fail)
Ping in VPN 0
PING 10.193.197.245 (10.193.197.245) 56(84) bytes of data.
From 10.193.197.244 icmp_seq=1 Destination Host Unreachable
From 10.193.197.244 icmp_seq=2 Destination Host Unreachable
vedge1# ping 10.193.197.244 (ping itself , it is ok)
Ping in VPN 0
PING 10.193.197.244 (10.193.197.244) 56(84) bytes of data.
64 bytes from 10.193.197.244: icmp_seq=1 ttl=64 time=0.018 ms
64 bytes from 10.193.197.244: icmp_seq=2 ttl=64 time=0.048 ms
vedge2# show interface descriptio
0 ge0/7 ipv4 - Up Up NA -
0 ge0/7.10 ipv4 10.193.197.245/31 Up Up NA -