04-01-2014 11:01 AM - edited 03-12-2019 07:18 AM
Hi, i currently have a problem with a CSR1000V AWS test installation that something disables the primary interface of the CSR and reenables it, unfortunately this brakes my connectivity to the box. The System Log shows -> *Apr 1 16:27:30.747: %LINK-5-CHANGED: Interface GigabitEthernet1, changed state to administratively down *Apr 1 16:27:31.748: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1, changed state to down *Apr 1 16:27:39.116: %LINEPROTO-5-UPDOWN: Line protocol on Interface Tunnel1, changed state to down *Apr 1 16:27:39.119: %DUAL-5-NBRCHANGE: EIGRP-IPv4 10: Neighbor 172.18.14.77 (Tunnel1) is down: interface down *Apr 1 16:27:44.105: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1, changed state to up *Apr 1 16:27:56.183: %LINEPROTO-5-UPDOWN: Line protocol on Interface Tunnel0, changed state to down
I also can't get it back to work when i reload the box. It hangs in "1/2 checks"
?
Did you have such issues before ?
Is it possible that i need to allow specific IPs from Amazon that they can do ICMP-healtchecks ?
In a "non-cloud" environment i would block everything i don't need
04-07-2014 05:46 AM
As for the health checks with ping you would need too enable ICMP on Amazon firewall,
https://www.youtube.com/watch?v=ZJ8IIVCXMBs
around 2nd minute , it is presented.
04-09-2014 07:34 AM
Are you still seeing this issue? I have not seen the primary interface going down or flapping in AWS. Can you attach your configuration?
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide