User Tools

Site Tools


hardware:pureflex_cli

Lenovo PureFlex command line

Connect to the PureFlex using ssh:

ssh USERID@<ip_cmm_flex>

List the objetct tree:

list -l all 

Select a target: CMM or switch


env -T mm[1]                    (Valeur : 1 ou 2)
env -T mm[p]                    (primary)
env -T switch[3]               (Valeur : 1 ou 2 = Network switches, 3 ou 4 = SAN switches)
env -T system                   (Pour revenir au sommet de l’arborescence)

Print the information about that device


info                                       (Liste les infos de l’objet sélectionné. Le système par défaut.)

Restart CMM


reset                                     (Restart)
reset-standby                   (Restart de la CMM en standby)
reset -f                                 (Restart, et failover sur la CMM de standby)

Clear logs

To clear both the CMM audit log and the CMM system event log, while the primary CMM in bay 1 is set as the persistent command environment, at the system:mm[1]> prompt, type

clearlog

To clear the CMM audit log, while the primary CMM in bay 1 is set as the persistent command environment, at the system:mm[1]> prompt, type

clearlog -l audit

To clear the CMM system event log, while the primary CMM in bay 1 is set as the persistent command environment, at the system:mm[1]> prompt, type

clearlog -l system

The following examples shows the information that is returned from these commands:

system:mm[1]> clearlog -l audit
OK
I  Audit     (CMM 02) The Audit log has been cleared by user ID USERID from SSH at address 9.42.104.88.
I  SERVPROC  (CMM 02) The Event log has been cleared by user ID USERID from SSH at address 9.42.104.88.
system:mm[1]>clearlog -l audit
OK
I  Audit     (CMM 02) The Audit log has been cleared by user ID USERID from SSH at address 9.42.104.88.
clearlog -1 system
OK
I  SERVPROC  (CMM 02) The Event log has been cleared by user ID USERID from SSH at address 9.42.104.88.

Using SSH:

After that below command can be safely run and the event log should be cleared:

# ssh USERID@mm00X clearlog -T mm[1]

It may fail if the mm[1] is not primary. In that case you should use:

# ssh USERID@mm00X clearlog -T mm[2]

Health status

system> health -l a -f -t
system   :                    Non-Critical
         blade[1]  :          OK
         blade[2]  :          OK
         blade[3]  :          OK
         blade[4]  :          OK
         blade[5]  :          OK
         blade[6]  :          OK
         blade[7]  :          OK
         blade[8]  :          OK
         blade[9]  :          OK
         blade[10] :          OK
         blade[11] :          OK
         blade[12] :          OK
         blade[13] :          OK
         blade[14] :          OK
         blower[1] :          OK
         blower[2] :          OK
         blower[3] :          OK
         blower[4] :          OK
         blower[5] :          OK
         blower[6] :          OK
         blower[7] :          OK
         blower[8] :          OK
         blower[9] :          OK
         blower[10]:          OK
         power[1]  :          OK
                  blower[1] : OK
         power[2]  :          OK
                  blower[1] : OK
         power[3]  :          OK
                  blower[1] : OK
         power[4]  :          OK
                  blower[1] : OK
         power[5]  :          OK
                  blower[1] : OK
         power[6]  :          OK
                  blower[1] : OK
         mm[1]     :          Non-Critical
         (08/11/20, 09:24:53) (FQXCMCR2901F) (000FF1BA) (00004F9B) The SMTP server at address 10.1.1.17 is not reachable.
         mm[2]     :          OK
         switch[1] :          OK
         switch[2] :          OK
         switch[3] :          OK
         switch[4] :          OK
         mt[1]     :          OK
         fanmux[1] :          OK
         fanmux[2] :          OK
system>

To check if the warning was cleared you may use folowing command:

ssh USERID@mm00X health -l 2 -f

It should display: Ok.

hardware/pureflex_cli.txt · Last modified: 2021/08/05 10:10 by manu