02-13-2013 05:54 PM - edited 03-07-2019 11:42 AM
Hello,
I was asked to configure a new ASR 1002 today and after successfully puttintg the config on the router (via TFTP) the router will no longer communicate with anything. There is nothing in the config to cause this (it was actually pulled off a working production ASR 1002) and I am unable to ping a local loopback IP while consoled into the router?? I removed the config, reloaded the router and configured a new loopback - same issue...cannot ping the loopback or anything else connected to this router. I have a hard time believing that the hardware is defective but I have never seen a router act like this before...any thoughts? As a side note, I received three other ASR 1002s today and none of them have this issue???
Thanks in advance,
Bill
02-13-2013 06:39 PM
Hi,
That is very unusual for a router to act this way. Do you have the same IOS on the bad router as the other 3. If not, change the IOS and make it the same as the other 3 good routers and test again.
HTH
02-13-2013 06:49 PM
Agreed. I thought about the IOS version after I left work but can't see how that could cause the router to act in this way...it's really odd. It's not just ICMP traffic either, telnet, ssh etc do not work. The router worked fine for about 30 minutes and then just stopped communicating with everything - including itself:-) I also considered some kind of weird license issue but that seems like a longshot...
02-13-2013 06:54 PM
Yes, usually license issue doesn't prevent you from ping Telnet, etc....
Keep an eye on the CPU. There maybe something causing it to spike and freeze the router.
Very strange.
02-13-2013 07:02 PM
Strange it is....I have never seen a router act like this. I dont have extensive experience with the ASR platform but then again, this isnt exactly complicated stuff.
Bill
02-13-2013 11:36 PM
After loading the config from other router, it may seem basic and i am sure you have already checked that but still, interfaces remain in shut mode. So you need to check that (just in case if you have forgotten it)
02-14-2013 02:50 PM
Issue has been resolved. It all comes down to a lack of experience on the ASR platform. I had initially configured the ASR via the mgt interface and then tried to communicate with the router via other interfaces/addresses which was NEVER going to work as the vendor did not ship this ASR with the ESP module installed (Duh). I would have expected the ASR to provide an error message or give me a clue in the log but I guess you just need to know what you are doing
Thanks again for the responses....
02-14-2013 03:18 PM
Bill
I am glad that you got it worked out. Thank you for posting back to the forum and indicating what the problem turned out to be. This may be helpful to other readers who might face similar problems.
HTH
Rick
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