No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

E9000 MM910 report alarm:0743FF27, and cound not power on CX310

Publication Date:  2014-09-18 Views:  226 Downloads:  0
Issue Description
1. Both SMM module get alarm with red furcation.
2. imana critical alarm: 0743FF27,transition to non-recoverable from less server.


Alarm Information
0x00743FF27, transition to non-recoverable from less server
Handling Process
1. Follow GPI alarm manaul:
root@SMM:/# smmget -d outportmode                   //0-means out mode is switch, 1- means out mode is MM910the outportmode: 0
root@SMM:/# smmget -l swi2 -d hotswapstate    //2X switch can not communicate, state is M7. "M4" is normal state.
Swi2 hot swap state is M7.
root@SMM:/# smmget -l swi3 -d hotswapstate  
Swi3 hot swap state is M7.
root@SMM:/# smmset -l swi2:fru2 -d powerstate -v poweron   //Try to poweron the board manually, but failed.
CLI Invalid FruId Error.
root@SMM:/# smmset -l swi3:fru2 -d powerstate -v poweron  
CLI Invalid FruId Error.

Tips:
8 kinds of hot swap state definition:
M0:FRU not install
M1:FRU not activate
M2:FRU activate request
M3:FRU activate processing
M4:FRU activated
M5:FRU unactivated
M6:FRU unactivate processing
M7:Loss communication

2X/3X switch boards are on M7 of lost communication.
Check the state of Mezz card and the position, found Mezz card install in position 1, and it's correct position.

2. Suspect CX310 board doesn't install properly.
Pulled out the cables between CX310 and BMC, re-insert the board and poweron, alarm disappear and recovered.

MM910 default set the out mode is Switch, means MM910 will go throuth 2X/3X CX310 to connect to management network. And there is a internal interface between 2X/3X plane and MM910, so when you connect another cable additionally, it will cause network loop. A ton of loop network packets cause MM910 port failed, then the alarm appear When pull out this extra cable, the network loop packet doesn't exist anymore and then port startup normally.
Root Cause
This alarm means SMM communication abnormal, follow GPI alarm manual, there are two reason cause the alarm:
1. SMM management port doesn't connect management cables
2. SMM Out mode is setted out from switch, 2X/3X switch plane board abnormal
Suggestions
BMC/SYS port of CX310 are console port, use to maintain and tune the board, in common usage, no need to connect cable to them.

END