![]() I can however, ping from the tunnel IP to the loopback IP in either direction. I setup loopbacks on both sides but I can't ping from loopback to loopback. The default GW for the LAN is the 4321 so I don't understand why I'm not getting any replies. For more information, see Troubleshooting network connectivity issues using Address Resolution Protocol (ARP) (1008184). Clear the Address Resolution Protocol (ARP) cache. For more information, see VLAN configuration on virtual switches, physical switches, and virtual machines (1003806). However, from the 7301 I am unable to ping anything on the LAN behind the 4321. Check the virtual switch VLAN configuration. I can bring up the tunnel between the peers just fine and I'm able to ping router LAN address, tunnel IP and loopback IP (from tunnel IP only!) in either direction. Resolution To use ping to verify that TCP/IP is working correctly, run the command: ping 127.0.0.1 The output for a working connection appears similar to: Pinging 127.0.0. Ip route vrf CU_XXXXX 106.106.106.106 255.255.255.255 10.41.4.18 This article provides steps to troubleshoot network connection issues by pinging the loopback address (127.0.0.1). Tunnel protection ipsec profile cust-dmvpn shared address is a virtual interface and is automatically up, so it cannot fail with this. Ip address 106.106.106.106 255.255.255.255Ĭrypto ipsec transform-set ESP-SHA esp-aes 256 esp-sha-hmacĬrypto isakmp key ********** address 67.x.x.x WebTo ping the loopback interface on your system to troubleshoot the. ![]() Tunnel protection ipsec profile cust-dmvpn ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |