Fujitsu M10-1/M10-4/M10-4S XSCF Panic/Hang: XSCF with XCP < 2090 may Reboot or Perform Poorly After Being Up For More Than 30 Days (Doc ID 1677542.1)

Last updated on MAY 29, 2014

Applies to:

Fujitsu M10-1 - Version All Versions and later
Fujitsu M10-4 - Version All Versions and later
Fujitsu M10-4S - Version All Versions and later
Information in this document applies to any platform.

Symptoms

XSCF may experience a reboot, or a delay in XSCF processing when the XSCF has been up for more than a month without rebooting.
External monitoring software may detect the issue.

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

Symptom2:  XSCF performs poorly:

Ex.1; The CLI command might terminate abnormally with the message as follows.

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

Ex.2;  Logging into the XSCF is delayed or takes an abnormally long time.

    • The login processing by the Telnet/SSH client and/or Web browser might experience a timeout because the XSCF processing is impacted.

Ex.3;  The response to commands that acquire MIB information such as a get command and so on become slow. 

    • When this occurs the external SNMP manager might detect a timeout.

     

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms