Description

Major CB 0 Ethernet Switch Failure" on the PTX10008

Symptoms

> show chassis alarms no-forwarding
1 alarms currently active
Alarm time        Class Description
 PDT Major CB 0 Ethernet Switch Failure

re0> show chassis hardware detail no-forwarding
Hardware inventory:
Item       Version Part number Serial number   Description
Chassis                DM123       JNP10008 [PTX10008]
CB 0       REV 04  750-075572  ABCD123     Control Board

Jun 12 09:01:11.518  inetd[32501]: Number of tftp connections at max limit (1)
Jun 12 09:01:11.638  chassisd[32480]: CHASSISD_SNMP_TRAP7: SNMP trap generated: Fru Failed (jnxFruContentsIndex 12, jnxFruL1Index 1, jnxFruL2Index 0, jnxFruL3Index 0, jnxFruName CB 0, jnxFruType 5, jnxFruSlot 0)
Jun 12 09:01:11.307  craftd[32488]: Receive FX craftd set alarm message: color: 2 class: 100 object: 105 slot: 0 silent: 0 short_reason=VMHost RE 0 Host unreachable long_reason=VMHost RE 0 Host unreachable id=1090519145 reason=1090519040
Jun 12 09:01:11.307  craftd[32488]: Minor alarm set, VMHost RE 0 Host unreachable
Jun 12 09:01:11.311  alarmd[33210]: Alarm set: RE id=1090519145, color=YELLOW, class=CHASSIS, reason=VMHost RE 0 Host unreachable
Jun 12 09:01:11.311  craftd[32488]: Receive FX craftd set alarm message: color: 1 class: 100 object: 143 slot: 0 silent: 0 short_reason=CB 0 Eswitch Fail long_reason=CB 0 Ethernet Switch Failure id=83886223 reason=83886080
Jun 12 09:01:11.311  craftd[32488]: Major alarm set, CB 0 Ethernet Switch Failure
Jun 12 09:01:11.313  alarmd[33210]: Alarm set: CB id=83886223, color=RED, class=CHASSIS, reason=CB 0 Ethernet Switch Failure

 

Solution

To resolve the "Major CB 0 Ethernet Switch Failure" issue on the PTX10008, follow these steps:

1.Check the Current Status of Both Routing Engines:**
> show chassis routing-engine | match state

2.Reset RE0 and Check for Any Alarms on RE1:**
   - Reset RE0 by physically reseating it or using the appropriate command.
   - Verify if there are any alarms on RE1 after resetting RE0.

3.Switch the Mastership Back to RE1 and See if the Alarm Persists:**
 request chassis routing-engine master switch check
 request chassis routing-engine master switch

- Once the mastership has switched to RE1, verify the alarm status on the chassis by logging into RE1:
   request routing-engine login other-routing-engine
   show chassis alarms

4.If Any Alarms Are Present, Try Reseating CB0 and Check Again:**
   - Physically reseat CB0 and verify if the alarms persist.
   - If the alarms are still present, further hardware diagnostics or replacement may be necessary.

Following these steps should help in resolving the "Major CB 0 Ethernet Switch Failure". If the issue persists, consider contacting technical support for further assistance.

Modification History

2024-07-13 : Article Created