Being given the task of replacing a failed Nexus 5596UP (no console output, powers up with fans but no lights except amber on the mgmt. module at the back), I quickly ran into some annoying problems trying to configure the FEX uplinks before actually racking it and plugging it in. I wanted to get as much config done beforehand as possible to minimize any interruptions – I was also a bit nervous as this unit was in the VPC primary role before it failed.
This is BTW the LED table:
vPC Auto-Recovery Feature in Nexus 7000.
This chapter includes system messages for the Cisco NX-OS Nexus 3000 family of switches. The messages are listed in alphabetical order by the system facility that produces them. Within each system facility section, messages are listed alphabetically by severity and mnemonics. Each error message is followed by an explanation and a recommended action.
Have you ever wondered what commands were actually in a “show tech” on the Nexus 5000? Well, I did. There seems to be a lot of info in there, and there really is. I compiled a list of commands that a show tech runs on a Nexus 5000 and have listed them below. Enjoy!
Hi..have you ever seen this error message while trying to configure a port?
“ERROR: Ethernet1/4: Config not allowed, as first port in the port−grp is dedicated”
If you take a look at the description of a SFP transceiver module, you will see the “DOM support” appeared in the product details. What does it mean? In fact, DOM or Digital Optical Monitoring as the words implies, is used for monitoring some parameters of the transceiver, which can help to identify the location of the fiber link failure, simplify maintenance, improve system reliability. Obviously a SFP with DOM function is high-ender than one without it. This is why most of modern optical SFP transceivers support DOM functions. To have a further understanding of DOM, some detailed information will be introduced in the following passage. Continue reading