I recently became the network tech at my office and I am testing some of our gear. I came across a Cisco 2811 which boots up and shows some very strange text. I am not sure what caused this, and I have been looking everywhere for a way to resolve this but I have not found any solutions that work.
Here is the text that shows when the system is booted.
I have let the device sit like this for about 30 minutes to see if anything else would happen but no luck. I have tried to boot the device with no compact flash card in it, but that didn't do much either. Is there a way i.e. reset button, or anything to get this to go back to a fully defualt setup?
The thing that most often causes symptoms like this is that the console speed does not match the configured speed of your terminal emulator. In this case the router boots generating this very strange output but will actually complete the boot process and go into normal processing. After this router boots do the interface lights indicate that they are operating? If you plug a device into the Ethernet ports do you get the link light illuminated?
Probably the best way to investigate this would be to set the speed of your terminal emulator at each of the possible speeds (starting at 1200 and working up through 2400, 4800 etc up to the maximum speed). Bear in mind that some emulators require that after you change the speed setting in the emulator that you stop and restart the connection.
Question We run asr9001 with XR 6.1.3, and we have a very long delay to
login w/ SSH 1 or 2 to the device compare to IOS device. After
investigation, the there is 1s delay between the client KEXDH_INIT and
the server (XR) KEXDH_REPLY. After debug ssh serv...
Introduction The purpose of this document is to demonstrate the Open
Shortest Path First (OSPF) behavior when the V-bit (Virtual-link bit) is
present in a non-backbone area. The V-bit is signaled in Type-1 LSA only
if the router is the endpoint of one or ...
Hi, I am seeing quite a few issues with patch install and wanted to
share my experience and workaround to this. Login to admin via CLI, then
access root with the “shell” command Issue “df –h” and you’ll probably
see the following directory full or nearly ...