2 Respuestas
- Más nuevo
- Más votos
- Más comentarios
0
IP Addressing seems correct, are you able to confirm that the tunnels are indeed up? You should be able to ping them.
respondido hace 2 años
0
Yes, both tunnels are working. I've added a static route to the config:
ip route 10.110.0.0 255.255.0.0 Tunnel2
and now can successfully communicate between on-prem VMs and AWS instances (both private and public segments). Also, I can change the route to Tunnel1, and it works too. But I need to set up SLAs to automatically switch between tunnels. Checked one more time just now. Still no ping:
chd-r0-c1921#ping 169.254.2.5 source tunnel 2
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 169.254.2.5, timeout is 2 seconds:
Packet sent with a source address of 169.254.2.6
.....
Success rate is 0 percent (0/5)
chd-r0-c1921#ping 10.110.110.96
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 10.110.110.96, timeout is 2 seconds:
..
Success rate is 0 percent (0/2)
chd-r0-c1921#ping 10.110.110.96 sour
chd-r0-c1921#ping 10.110.110.96 source vlan 41
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 10.110.110.96, timeout is 2 seconds:
Packet sent with a source address of 10.100.10.1
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 60/67/72 ms
chd-r0-c1921#
respondido hace 2 años
Contenido relevante
- OFICIAL DE AWSActualizada hace 2 años
- OFICIAL DE AWSActualizada hace un año
- OFICIAL DE AWSActualizada hace 3 años