
Bret.Jaquish at navistar
Nov 2, 2009, 6:12 AM
Post #2 of 2
(2213 views)
Permalink
|
If it is stuck in "boot" mode, then the router is "halfway booted" Here is what you need to do: Verify the "boot helper image" matches with the main IOS image: Show bootflash: Show disk0: (or whatever disk you have the image on) For example: Show bootflash: shows a XD image Show disk0: shows a "T" train image They would be incompatible. This document is pretty good at explaining the images. The bootflash image needs to be the right version to support all of the interface modules (PA) installed in the chassis. http://www.cisco.com/en/US/docs/routers/7200/install_and_upgrade/network_process_engine_install_config/npense.html Hope this helps, Bret From: cisco-ubr-bounces [at] puck [mailto:cisco-ubr-bounces [at] puck] On Behalf Of LeeRNorman1 [at] aol Sent: Sunday, November 01, 2009 1:15 PM To: cisco-ubr [at] puck Subject: [c-ubr] uBR7246VXR - RJ45 Greetings from the Dallas area - I have a uBR7246VXR with a uBR7200-I/O-FE (I/O Controller) that I can't get up & running. 1. The RJ45-jack does not respond, nor does the LED beside it. When I go into "Config Terminal" mode to assign the media-type as RJ45, I get a error. But it will stay in MII (media-type) mode. 2. The uBR7246VXR boots up in "boot-mode". It's stuck in boot-mode. I've done the "confreg" thing, doesn't work. How do I format a flash-disk if it won't recognize the slot &/or disk? Best Regards, Lee R. Norman. 972-736-3380 - hm-ofc. 508-527-0370 - mobile 972-767-3740 - fax LeeRNorman1 [at] aol<http://mail/> ________________________________ Disclaimer Confidentiality Notice: This e-mail, and any attachments and/or documents linked to this email, are intended for the addressee and may contain information that is privileged, confidential, proprietary, or otherwise protected by law. Any dissemination, distribution, or copying is prohibited. This notice serves as a confidentiality marking for the purpose of any confidentiality or nondisclosure agreement. If you have received this communication in error, please contact the original sender.
|