Chassis Management Module (CMM) CLI

The Chassis Management Module (CMM) monitors and controls hardware modules in the Chassis. Communication with a CMM occurs by SNMP requests from a dedicated SGM. If a hardware sensor reports a problem, the CMM automatically takes action or sends a report. CMMs also have a Command Line Interface.

There are two procedures to connect to a CMM CLI:

1. Connect to the serial port on the front panel of the CMM
2. In your terminal emulation program, set the baud rate to 9600
3. Enter admin for the user name and password
4. Open a telnet or SSH session from one of the SGMs
5. First make sure that you have connectivity to the CMMs by pinging both addresses:
6. 198.51.100.33 (routed via SSM1)
7. 198.51.100.233 (routed from SSM2)
8. Telnet or SSH from the SGM to the CMM
9. Enter admin for the user name and password

When connected:

1. Modify the Chassis configuration, including the Chassis ID (1 or 2) by editing
   /etc/shmm.cfg
2. Useful commands: (Should be run after entering CLI shell, via clia command)
3. Show the full list of commands:
   CLI> help
4. Show alerts
   CLI> alarm
5. Reset alerts
   CLI> alarm 0
6. Show power consumption information
   CLI> shelf pd
7. Retrieve event logs
   CLI> sel
8. Reboot the CMM
   CLI> reboot
   Note: reboot initiates a failover to the standby CMM
9. Make sure that a board is recognized in its slot
   CLI> board
10. Reset the specified board
    CLI> boardreset <slot number>
11. Display FRU information

• CLI> fru [fru_id]
  This table shows the mapping between SGM ID in CMM and SGM ID in Chassis.

  Example: SGM 5 shows as 8a on CMM

61000 slot information

41000 Security System slot information

CMM debug commands – How to activate the log function:

1. Log into the active CMM
2. Run
   /etc/summary
   can take several minutes
3. Run
   cat /tmp/debug.log
   prints debug log with all basic information
4. Run
   i2c_test
   tests the internal CMM I2C and prints all devices connected on the I2C
5. Run
   cat /etc/shmm.cfg
   prints ShMM’s custom configuration
6. Run
   clia fruinfo 20 x
   on the 61000: Where x is between 0 to 16

   on the 41000 Security System: Where x is between 0 to 9

7. Run
   clia fruinfo y 0
   16 times where y is 10,12,82,84,86,88,8a,8c,8e,90,92,94,96,98,9a,9c
8. Close your terminal program. /tmp/debug.log file will hold the debug information.