Description

M10 XSCF running XCP2080 or earlier may exhibit unexpected operational behavior such as panic or delayed/slow response to normal operations if XCSF has been running without a reboot for 1 month or more.

Occurrence

This issue can occur on the following platforms:

• XSCF with XCP2080 or earlier (for M10 Systems)

Note: This issue only occurs if both the following are true:

1. XSCF is running XCP2080 or earlier.
2. XCSF has been running without a reboot for 1 month or more.

To determine the XCP version, use the following command:

    XSCF> version -c xcp 
    BB#00-XSCF#0 (Master)
    XCP0 (Reserve): 2044
    XCP1 (Current): 2044

To determine how long XSCF has been running, use the following command:

    XSCF> showlogs power -Mr
    Date                          Event              Cause             ID  Switch
    <snip>
    May 29 02:08:15 UTC 2014      SCF Reset          Power On          00  Locked <-----
    <snip>
    May 20 21:09:38 UTC 2014      SCF Reset          Self Reset        00  Locked <-----
    <snip>

Symptoms

If the described issue occurs, the following symptoms may be seen:

Symptom 1:

XSCF panic occurs with the following error log and XSCF resets:

    Date: Feb 03 11:47:03 JST 2014
    Code: 80000000-00fcff0056020000ff-010400130000000000000000 
    Status: Alarm Occurred: Jan 28 23:18:10.000 JST 2014 
    FRU: /FIRMWARE,/BB#0/CMUL
    Msg: SCF panic detected
    Diagnostic Code:
      00000000 00000000 0000
      00000000 00000000 0000
      00000000 00000000 0000
      00000000 00000000 00000000 00000000 00000000 00000000 0000

Note: The following logs may be detected along with the above error log:

    Date: Feb 14 09:08:27 JST 2014
    Code: 20000000-00fcff000e010000ff-010400010000000000000000 
    Status: Notice Occurred: Feb 14 09:08:05.827 JST 2014 
    FRU: /FIRMWARE,/MBU
    Msg: SCF process down detected

    Date: Feb 03 11:47:04 JST 2014
    Code: 80000000-0090010000ff0000ff-010480100000000000000000 
    Status: Alarm Occurred: Feb 03 11:46:55.034 JST 2014 
    FRU: /BB#0/PSUBP
    Msg: SCF Diagnosis error on System backup memory

    Date: Nov 02 06:53:23 JST 2013
    Code: 40000000-0090010000ff0000ff-011f00010000000000000000 
    Status: Warning Occurred: Nov 02 06:48:07.601 JST 2013 
    FRU: /BB#0/PSUBP
    Msg: System backup memory access error

    Date: Nov 09 18:36:18 JST 2013
    Code: 40000000-00560100fcff0000ff-010400150000000000000000 
    Status: Warning Occurred: Nov 09 18:35:55.157 JST 2013 
    FRU : /BB#0/CMUL,/FIRMWARE
    Msg: SCF WDT detected

Symptom 2:

An abnormality or the delay of XSCF processing occurs. For example:

1. The CLI command might terminate abnormally with the following message:

   "Cannot communicate with the other XSCF. Check the other XSCF stat"

2. The login process by the Telnet/SSH client and/or web browser might result in a timeout because of the processing of XSCF delays.

3. The response of SNMP commands which acquire MIB information (such as the 'get' command) become slow. When this happens, the external SNMP manager might detect a timeout.

Workaround

There is no workaround for this issue.

Until the XCP version can be updated, use the rebootxscf(8) command to reboot XSCF to restore normal operation.

This issue is addressed in the following releases:

• XCP2090 or later

Note: This issue was fixed in XCP2090 or later but only the latest release of this firmware is available for download from MOS as listed in <Document:1554086.1>.

History

30-Jun-2014: Document released; State: Resolved

References

This solution has no attachment