Re: [c-nsp] 4500X weird issue...
Follow-up to the follow-up :) Long story short... Switch essentially had no flash and dir, etc gave errors. TAC had us boot from tftp image via ROMMON. Booted up, found config, write mem worked, founds it's VSS partner, and dropped to standby. Rebooted the other switch, this one became primary, and all is well. Still don't understand why even ROMMON couldn't find a flash, yet tftp booting IOS seemed to make everything well again. But not looking a gift horse in the mouth, just wondering in case this shows up again. I really don't like the restart breaking things scenario :) Jeff On 12/10/2013 8:45 PM, Jeff Kell wrote: Follow-up... the secondary booted up OK. We're looking at a possible RMA on the failing one (TAC case open) rather than cracking the case on a virgin switch to mess with flash :). Jeff On 12/6/2013 11:25 PM, Jeff Kell wrote: We received our first pair of 4500X switches, and proceeded to try to prepare them for deployment. They came up OK on console access, we got a very basic configuration setup, linked them together, and did an initial VSS pairing. With that successful, we put in a management IP address for the management port, saved everything, and proceeded to move them to the server room. Upon power-up at the new location, they won't boot... * * * Rom Monitor NVRAM configuration is being initialized to * * default values. This may be because it was never initialized.* * * Writing to Primary Region failed Writing to Backup Region failed ___ cisco-nsp mailing list cisco-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
Re: [c-nsp] 4500X weird issue...
On Friday, December 13, 2013 01:05:20 AM Jeff Kell wrote: Still don't understand why even ROMMON couldn't find a flash, yet tftp booting IOS seemed to make everything well again. But not looking a gift horse in the mouth, just wondering in case this shows up again. I really don't like the restart breaking things scenario :) TFTP would work because it's like assuming your flash is the network. Saving to NVRAM will still work because the NVRAM storage is different from flash (well, typically). So what is the situation now? Can you reboot from flash, or do you really have no flash? Mark. signature.asc Description: This is a digitally signed message part. ___ cisco-nsp mailing list cisco-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
Re: [c-nsp] 4500X weird issue...
Follow-up... the secondary booted up OK. We're looking at a possible RMA on the failing one (TAC case open) rather than cracking the case on a virgin switch to mess with flash :). Jeff On 12/6/2013 11:25 PM, Jeff Kell wrote: We received our first pair of 4500X switches, and proceeded to try to prepare them for deployment. They came up OK on console access, we got a very basic configuration setup, linked them together, and did an initial VSS pairing. With that successful, we put in a management IP address for the management port, saved everything, and proceeded to move them to the server room. Upon power-up at the new location, they won't boot... * * * Rom Monitor NVRAM configuration is being initialized to * * default values. This may be because it was never initialized.* * * Writing to Primary Region failed Writing to Backup Region failed ___ cisco-nsp mailing list cisco-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
Re: [c-nsp] 4500X weird issue...
On Saturday, December 07, 2013 06:25:05 AM Jeff Kell wrote: What the heck??? Hmmh, that's dodgy, considering we're looking at buying a pile of these soon (these or either Juniper's EX4550 - we currently have some EX4550's in production, so we know they work). Are you still booting them as a VSS pair, or individually? Mark. signature.asc Description: This is a digitally signed message part. ___ cisco-nsp mailing list cisco-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
Re: [c-nsp] 4500X weird issue...
Your config-register looks to be set wrong... Shouldnt it be 0x2102? There also seems to be an issue with some rommon versions looking at google if config register ends in 2. They suggest trying 2101... Sent from a mobile device On 7 Dec 2013, at 15:25, Jeff Kell jeff-k...@utc.edu wrote: We received our first pair of 4500X switches, and proceeded to try to prepare them for deployment. They came up OK on console access, we got a very basic configuration setup, linked them together, and did an initial VSS pairing. With that successful, we put in a management IP address for the management port, saved everything, and proceeded to move them to the server room. Upon power-up at the new location, they won't boot... * * * Rom Monitor NVRAM configuration is being initialized to * * default values. This may be because it was never initialized.* * * Writing to Primary Region failed Writing to Backup Region failed Rommon (G) Signature verification PASSED flash0:/codesign/rm1.dat open failure Rommon (P) Signature verification PASSED flash0:/codesign/rm2.dat open failure * * * Rom Monitor NVRAM configuration is being initialized to * * default values. This may be because it was never initialized.* * * Writing to Primary Region failed Writing to Backup Region failed FPGA (P) Signature verification PASSED flash0:/codesign/fpga.dat open failure * * * Welcome to Rom Monitor forWS-C4500X-16 System. * * Copyright (c) 2008-2013 by Cisco Systems, Inc. * * All rights reserved. * * * Rom Monitor (P) Version 15.0(1r)SG10 CPU Rev: 2.2, Board Rev: 9, Board Type: 108 CPLD Mobat Rev: 2.0x549a.0x59a4 Chassis: WS-C4500X-16 MAC Address : e4-c7-22-**-**-** Ip Address : Not set. Netmask : Not set. Gateway : Not set. TftpServer : Not set. Non-Redundant system or peer not running IOS System Uplinks Linecards have been reset!! * The system will autoboot in 5 seconds * Type control-C to prevent autobooting. . . . . Management Ethernet Link Up: 1Gb Full Duplex . The system will autoboot now config-register = 0x102 Writing to Primary Region failed Writing to Backup Region failed Autobooting using BOOT variable specified file. Could not find a valid file in BOOT environment variable. BOOT variable can be set from IOS. To find currently set Rom Monitor variables, please type 'set' command. For help on choosing a boot method, type 'confreg' command. Writing to Primary Region failed Writing to Backup Region failed Writing to Primary Region failed Writing to Backup Region failed Writing to Primary Region failed Writing to Backup Region failed rommon 1 boot Writing to Primary Region failed Writing to Backup Region failed ExtX super block invalid signature No bootable image found ! boot: can not determine first file name on device flash1:/USER rommon 2 What the heck??? Jeff ___ cisco-nsp mailing list cisco-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/ ___ cisco-nsp mailing list cisco-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
Re: [c-nsp] 4500X weird issue...
On 12/6/2013 10:25 PM, Jeff Kell wrote: We received our first pair of 4500X switches, and proceeded to try to prepare them for deployment. They came up OK on console access, we got a very basic configuration setup, linked them together, and did an initial VSS pairing. With that successful, we put in a management IP address for the management port, saved everything, and proceeded to move them to the server room. Upon power-up at the new location, they won't boot... * * * Rom Monitor NVRAM configuration is being initialized to * * default values. This may be because it was never initialized.* * * Writing to Primary Region failed Writing to Backup Region failed Rommon (G) Signature verification PASSED flash0:/codesign/rm1.dat open failure Rommon (P) Signature verification PASSED flash0:/codesign/rm2.dat open failure * * * Rom Monitor NVRAM configuration is being initialized to * * default values. This may be because it was never initialized.* * * Writing to Primary Region failed Writing to Backup Region failed FPGA (P) Signature verification PASSED flash0:/codesign/fpga.dat open failure * * * Welcome to Rom Monitor forWS-C4500X-16 System. * * Copyright (c) 2008-2013 by Cisco Systems, Inc. * * All rights reserved. * * * Rom Monitor (P) Version 15.0(1r)SG10 CPU Rev: 2.2, Board Rev: 9, Board Type: 108 CPLD Mobat Rev: 2.0x549a.0x59a4 Chassis: WS-C4500X-16 MAC Address : e4-c7-22-**-**-** Ip Address : Not set. Netmask : Not set. Gateway : Not set. TftpServer : Not set. Non-Redundant system or peer not running IOS System Uplinks Linecards have been reset!! * The system will autoboot in 5 seconds * Type control-C to prevent autobooting. . . . . Management Ethernet Link Up: 1Gb Full Duplex . The system will autoboot now config-register = 0x102 Writing to Primary Region failed Writing to Backup Region failed Autobooting using BOOT variable specified file. Could not find a valid file in BOOT environment variable. BOOT variable can be set from IOS. To find currently set Rom Monitor variables, please type 'set' command. For help on choosing a boot method, type 'confreg' command. Writing to Primary Region failed Writing to Backup Region failed Writing to Primary Region failed Writing to Backup Region failed Writing to Primary Region failed Writing to Backup Region failed rommon 1 boot Writing to Primary Region failed Writing to Backup Region failed ExtX super block invalid signature No bootable image found ! boot: can not determine first file name on device flash1:/USER rommon 2 What the heck??? Jeff I thought you were running into the confreg issue but it appears you have the upgraded rom in which this is fixed. Odd. http://www.cisco.com/en/US/docs/switches/lan/catalyst4500/release/note/OL_24829.html#wp196197 What's the normal commands show in rommon (dev, dir flash:, etc)? Everything there? tv --- This email is free from viruses and malware because avast! Antivirus protection is active. http://www.avast.com ___ cisco-nsp mailing list cisco-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
