HPE Community read-only access December 15, 2018
This is a maintenance upgrade. You will be able to read articles and posts, but not post or reply.
Hours:
Dec 15, 4:00 am to 10:00 am UTC
Dec 14, 10:00 pm CST to Dec 15, 4:00 am CST
Dec 14, 8:00 pm PST to Dec 15, 2:00 am PST
BladeSystem - General
cancel
Showing results for 
Search instead for 
Did you mean: 

Slowness and Hanging in the System every 30 seconds.

 

Slowness and Hanging in the System every 30 seconds.

I have problem of slowness and hanging in an Blade Server BL 45p G1. MS SQL 2005 is installed.

In the system event viewr:

Remote Insight Agent: The Remote Insight Board has detected a controller interface error.
[SNMP TRAP: 9006 in CPQSM2.MIB]

3 REPLIES
Pasquino
Occasional Advisor

Re: Slowness and Hanging in the System every 30 seconds.

Hi,

NT Event ID: 1111 (Hex)0xc4350457 (cpqsvmsg.dll)
Log Severity: Error (3)
Log Message: The Remote Insight Board has detected a controller interface error.
SNMP Trap: cpqSm2InterfaceError - 9006 in CPQSM2.MIB
Symptom: Remote Insight/Integrated Lights-Out Interface Error. The host OS has detected an error in
the Remote Insight/ Integrated Lights-Out interface. The firmware is not responding.
Supporting SNMP Trap Data:
â ¢ sysName
â ¢ cpqHoTrapFlags
Supporting SNMP Trap Description: â Server [sysName], Remote Insight/Integrated Lights-Out
interface error.â

try this fix:

In Insight Manager >>Options, Events, SNMP Trap Settings.
At the top dropdown box that says Mib Name:
find cpqsm2.mib. Then at the drop down box that says Trap Name: find cpqSm2InterfaceError
After that, the Event type should read RemoteInsight/Integrated LightsOut Interface Error (9006).
At the drop down box that says Enable Trap Handling, select NO, then click the OK button. The error will still show up in the Windows event logs but won't generate an alert.

Re: Slowness and Hanging in the System every 30 seconds.

Does this has anything to do with the slowness
Pasquino
Occasional Advisor

Re: Slowness and Hanging in the System every 30 seconds.

Hi,

perhaps, but certainly it fixes the problem in the event log!