Chassis Management Module (CMM)
Problem Blue LED on the CMM
Cause CMM is not properly assembled
Resolution Re-seat the CMM
Validation Verify the Blue LED on the CMM turned off
Problem Power Supplies are not monitored
Cause Chassis type is not configured properly in the CMM
Resolution:
- Login via serial console to the CMM and repeat the CMM installation process (install.sh).
- Select correct Chassis type:
- Telkor - 3 PSUs per 1U
- Lambda - 5 PSUs per 1U
- In case of dual CMM, perform it on each CMM individually.
Validation Run asg stat -v and check the power supplies amount
Problem Failed to install 2nd Chassis in dual Chassis setup
Cause Chassis ID is identical on both Chassis
Resolution
- Login via serial console to the CMM
- Set the Chassis ID by editing the SHMM_CHASSID in /etc/shmm.cfg
- Reboot the CMM
Validation Check whether 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 faulty CMM individually and reseat the other CMM
Validation Verify version by invoking asg_version
Problem No connectivity to the CMM through one of the CIN interfaces
Cause CMM interface is set to the front panel instead of the backplane
Resolution:
- Remove CMM
- Change JP4 jumpers' position to 2-3
- Plug in the CMM
Validation Run asg stat -v and check the CMM amount
Problem Alarm LED is on
Cause High temperature in Chassis surroundings
Resolution:
- Login via serial console to the CMM and reset LED by running:
clia alarm 0 - Make sure that all open slots (missing SGMs/CMMs/PSUs) are covered with blanks
- Make sure that all fans are properly attached
- Make sure there is proper cooling in Chassis surroundings
Validation Alarm LED should remain off
|