Chassis Management Module (CMM)

Problem Blue LED is lit on the CMM.

Cause CMM is not correctly assembled.

Resolution Re-seat the CMM.

Validation Make sure that the Blue LED on the CMM turned off.

Problem Power Supplies are not monitored.

Cause The Chassis type is not configured correctly in the CMM.

Resolution:

1. Log in through a serial console to the CMM and repeat the CMM installation process (install.sh).
2. Select the correct Chassis type:
   • Telkor - 3 PSUs for each 1U
   • Lambda - 5 PSUs for each 1U
3. If you have dual CMMs, repeat steps 1 and 2 again on the other CMM.

Validation

1. Run:

   > asg stat -v

2. Make sure the number of power supplies is correct.

Problem Failed to install 2nd Chassis in dual Chassis environment.

Cause Chassis ID is the same on both Chassis.

Resolution

1. Log in through a serial console to the CMM.
2. Set the Chassis ID by editing the SHMM_CHASSID in /etc/shmm.cfg.
3. Reboot the CMM.

Validation Make sure the installation on the 2nd Chassis works.

Problem CMM firmware is different after CMM failover.

Cause CMM firmware mismatch in a dual CMM.

Resolution Upgrade the defective CMM individually and reseat the other CMM.

Validation Make sure the firmware version is correct: asg_version

Problem There is no connectivity to the CMM through one of the CIN interfaces.

Cause The CMM interface is set to the front panel instead of the backplane.

Resolution:

1. Remove the CMM.
2. Change the JP4 jumpers' position to 2-3.
3. Connect the CMM.

Validation

1. Run:

   > asg stat -v

2. Make sure the number of CMMs is correct.

Problem The alarm LED is on.

Cause The temperature in the Chassis surroundings is high.

Resolution:

1. Log in through a serial console to the CMM.
2. Reset the LED:

   # clia alarm 0

3. Make sure that all open slots (missing SGMs/CMMs/PSUs) are covered with blanks.
4. Make sure that all fans are correctly attached.
5. Make sure there is correct cooling in Chassis surroundings.

Validation The alarm LED stays off.