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

FAQ-the new changed controller can't be seen in ISM of S2600

Publication Date:  2012-09-18 Views:  36 Downloads:  0
Issue Description
In some bureau, the controller B of S2600 is broken, that can not be powered on. After replacing it with a new one, the new one can not be mounted.
Alarm Information
None
Handling Process
1. Connect to controller B with serial, enter the original user name/password, admin/123456, to get in the AK-I login, there occurs an attention “deal fail!”. Click “shift+9” to enter the command, then enter the “mml” pattern, check the current status using command “sys status”.
spu ui>sys status
Input cmd is sys status
Double Or Single : [ double ]
Master Or Slave : [ slave ]
Power on status : [ doulbe]
Local Controller Status : [ abnormal ]
Peer Controller Status : [ normal ]
System Running Status : [ power on ]
System error reason : [ master start DEV failed ]
System flush result: [cache flush no failure]
We can see that the system didn’t load normally.
2. Input “dev keyvar” in mml to check the reason.
Input cmd is dev keyvar
iniDoCli() : MML is working, keyvar
arg[ 0]="keyvar"

Compile time stamp : May 10 2010 14:31:56
g_bHasWork                     = 1
g_bStartWork                   = 0
g_bStartWorkOk                 = 0
g_uiStartWorkFailReason        = 1,  peer local memszie nomatch

g_bPeerStartWorkFinish         = 0
g_uiProcessFlashConnect        = 0
g_uiProcductModel              = 9
g_bFindCtrl                    = 1
g_uiCtrlId                     = 1
g_uiCtrlFrameId                = 0
g_uiCtrlType                   = 561000h
g_bReadDbOk                    = 0h
g_bReadDbFinish                = 0
g_bFindVault                   = 1
g_uiSBDiskType                 = 2
g_bSbDiskReady                 = 1
g_acProductSerial              = "210231G323Z0A7000013"
g_bLoopMapTableRenew           = 0
g_uiDevVersion                 = 1
g_ullSystemSerial              = 21000022A102C524h
g_bIsAuthenticatonEnable       = 1
g_uiDiskTestTime               = 60
g_uiProcductODMManufacture     = 0
g_abUserFrameIdTable[]:[UsrFrameId,  InnerFrameId]
[ 0, 0],[ 1, 1],[ 2, 2],[ 3, 3],
From “peer local memszie nomatch”, we can see that change the memory of controller B to equal that of controller A to fix the problem.
Root Cause
None
Suggestions
It is suggested that make sure the device changed is same to the field, especially the memory.

END