Marshall Morgan (marshall@netdoor.com) wrote:
Did you check the second ARC to ensure it was not set to own the cards? Was chassis awareness enabled when it booted? As well, when we swapped from NMCs to HiperNMCs the chassis went bezerk and was doing all sorts of weird stuff until we rebooted it (minutes later). All better!
This pre-exists the second ARC, so we can probably acquit that. It is set non-owner and the slots are dynamically assigned. The NMC settings for the first ARC (the lead dog) are: Chassis Awareness: DISABLED Dynamic Slot Assignment: DISABLED DSA Idle Rebalancing: ENABLED It has HDMs in slots 1 - 7, type = static, owner=yes, console=no The settings for the second ARC (spare) are: Chassis Awareness: ENABLED Dynamic Slot Assignment: ENABLED DSA Idle Rebalancing: ENABLED It has HDMs in slots 1-7, type=dynamic, owner=no, console=yes Again, everything is now working, but the regular appearance of a red hub status condition on the HNMC makes we wonder why it's doing it (that condition pre-dates the second ARC and the HNMC, which I added while I happened to be at that POP to look at the HDM that was acting up). Has anyone seen anything like this when something was ready to fail but hadn't actually done so yet? Jonathan Byrne Engineering Division Exodus Communications K.K. http://www.exodus.co.jp/ Tel: +81 3-5334-1700 Fax: +81 3-5334-1702 Direct: +81 3-5334-1756 - To unsubscribe to usr-tc, send an email to "majordomo@xmission.com" with "unsubscribe usr-tc" in the body of the message. For information on digests or retrieving files and old messages send "help" to the same address. Do not use quotes in your message.