Network technologies and trends » bootflash:

What is CMP in Nexus 7000 Series Supervisor Module?

Yasir Irfan — Sun, 31 Jul 2011 12:52:46 +0000

The Connectivity Management Processor (CMP) is separate processor on the Cisco Nexus 7000 Series supervisor module that is in addition to the main control processor (CP). The CMP provides a second network interface to the device for use even when the CP is not reachable. You can access the CMP to configure it and to perform system operations, such as taking over the CP console or restarting the CP. The CMP can reset all system components, including power supplies; it can also reset the host supervisor module to which it is attached, enabling a complete system restart.

The Connectivity Management Processor (CMP) available even if its supervisor module is in standby mode or the device is down because of issues such as over-temperature alarms. Each CMP gets power from an auxiliary power bus in the device that remains operational so long as you have at least one power cable attached to the device.

All these options are available through the Connectivity Management Processor (CMP) because it contains its own RAM, bootflash, and front panel management Ethernet port.

The Connectivity Management Processor (CMP) provides the following functions:

• Communicates with the supervisor module and I/O modules even if Cisco NX-OS device is not responding on the mgmt0 port.

• Maintains connectivity when you reboot the supervisor module.

• Monitors the supervisor module console port.

• Reboots the local supervisor module or the entire system.

• Takes over the supervisor module console port.

• Collects failure logs and watches bootup diagnostic messages.

SUP 720 -3B Supervisor Engine Crashed

Yasir Irfan — Wed, 25 May 2011 05:17:56 +0000

In my previous post I talked about the crashed Sup 720- 3B supervisor Engine for a Cisco Catalyst 6513 Switch. Since there was no ray of hope for the SUP 720-3B Supervisor Engine and I couldn’t make use of “show tech” IOS command. I decided to open a TAC case with Cisco.

The TAC Engineer after studying the logs generated by the crashed Sup 720- 3B supervisor Engine came up with the following reply

“Hello Yasir

It seems we have faulty SUP and need to be replaced since it is keep crashing and not coming up.”

After looking at the log’s I predict there might be problem with flash memory of SUP 720 -3B Supervisor Engine.

System Bootstrap, Version 8.1(3)

Cat6k-Sup720/SP processor with 524288 Kbytes of main memory

rommon 1 >

I tried to boot the SUP 720-3B using the boot command from rommon mode but that too failed and I am getting the following error.

%DIAG-SP-6-RUN_MINIMUM: Module 7: Running Minimal Diagnostics…

Also I tried to boot the SUP 720-3B from the flash memory using the “bootflash:”command that too failed again I am getting the same error

%DIAG-SP-6-RUN_MINIMUM: Module 7: Running Minimal Diagnostics…

%Software-forced reload

Breakpoint exception, CPU signal 23, PC = 0×41D8BE6C

-Traceback= 41D8BE6C 41D89DB8 41B370D8 41B37104 41A09A1C 41A4ACCC 41A41000 41A41058 4075B9FC 4075C6E4 419168D8 419166F4 41AD8610 41AD5530 41AD574C 41D7E35C

$0 : 00000000, AT : 43100000, v0 : 44AF0000, v1 : 43640000

a0 : 50E46E18, a1 : 0000F100, a2 : 00000000, a3 : 42E30000

t0 : 41D7E978, t1 : 3400F101, t2 : 41D7E988, t3 : FFFF00FF

t4 : 41D7E978, t5 : 00000000, t6 : 00000000, t7 : 00000000

s0 : 00000000, s1 : 430B0000, s2 : 5033A36C, s3 : 087365C8

s4 : 50D740D0, s5 : 50D1AC48, s6 : 00000040, s7 : 43890000

t8 : 5000BA74, t9 : 00000009, k0 : 00000000, k1 : 00000000

gp : 431011F0, sp : 5000BB28, s8 : 00000000, ra : 41D89DB8

EPC : 41D8BE6C, ErrorEPC : 65DFF3A3, SREG : 3400F103

MDLO : 00000000, MDHI : 00000000, BadVaddr : 00000000

DATA_START : 0×42DDFAF0

Cause 00000024 (Code 0×9): Breakpoint exception

Writing crashinfo to bootflash:crashinfo_20110523-131601

=== Flushing messages (16:16:01 KSA Mon May 23 2011) ===

Buffered messages:

00:01:01: curr is 0×0

This is why Cisco is a leader among its competitor and they are exceling because they are pioneers of Networking. I love Cisco for two reasons strong technical support and commitment they show to the customer.

SUP 720- 3B failing to boot

Yasir Irfan — Tue, 24 May 2011 05:14:01 +0000

Friends we have a Cisco Catalyst 6513 Switch installed with SUP 720-3B as a supervisor engine. From past 7 years its working fine but suddenly we the SUP 720-3B supervisor Engine failed. The SUP 720-3B is always going in to rommom mode and I am getting the following error

System Bo otstrap, Version 8.1(3)

Cat6k-Sup720/SP processor with 524288 Kbytes of main memory

rommon 1 >

I tried to boot the SUP 720-3B using the boot command from rommon mode but that too failed and I am getting the following error.

%DIAG-SP-6-RUN_MINIMUM: Module 7: Running Minimal Diagnostics…

Also I tried to boot the SUP 720-3B from the flash memory using the “bootflash:”command that too failed again I am getting the same error

%DIAG-SP-6-RUN_MINIMUM: Module 7: Running Minimal Diagnostics…

%Software-forced reload

Breakpoint exception, CPU signal 23, PC = 0x41D8BE6C

-Traceback= 41D8BE6C 41D89DB8 41B370D8 41B37104 41A09A1C 41A4ACCC 41A41000 41A41058 4075B9FC 4075C6E4 419168D8 419166F4 41AD8610 41AD5530 41AD574C 41D7E35C

$0 : 00000000, AT : 43100000, v0 : 44AF0000, v1 : 43640000

a0 : 50E46E18, a1 : 0000F100, a2 : 00000000, a3 : 42E30000

t0 : 41D7E978, t1 : 3400F101, t2 : 41D7E988, t3 : FFFF00FF

t4 : 41D7E978, t5 : 00000000, t6 : 00000000, t7 : 00000000

s0 : 00000000, s1 : 430B0000, s2 : 5033A36C, s3 : 087365C8

s4 : 50D740D0, s5 : 50D1AC48, s6 : 00000040, s7 : 43890000

t8 : 5000BA74, t9 : 00000009, k0 : 00000000, k1 : 00000000

gp : 431011F0, sp : 5000BB28, s8 : 00000000, ra : 41D89DB8

EPC : 41D8BE6C, ErrorEPC : 65DFF3A3, SREG : 3400F103

MDLO : 00000000, MDHI : 00000000, BadVaddr : 00000000

DATA_START : 0x42DDFAF0

Cause 00000024 (Code 0×9): Breakpoint exception

Writing crashinfo to bootflash:crashinfo_20110523-131601

=== Flushing messages (16:16:01 KSA Mon May 23 2011) ===

Buffered messages:

00:01:01: curr is 0×0

Seems like the SUP 720-3B is crashed, I will open a TAC case and see what the issue is. I know Cisco TAC team is quite helpful and they will come out with a solution for this problem. If anyone has any inputs or solutions they are welcome provide solutions in the comment area of this post.