- Integrated Systems
- About Us
- Integrated Systems
- About Us
09-06-2013 09:33 AM
ProLiant BL465c G7 PSP 188.8.131.52 Erroneous SNMP Trap 3033_4
Last night someone reported that the server trapped with a 3033_4. I was able to verify this in our alerting log in our alerting system.
I know that the 3033_4 is a cable issue and it's source is the Intelligent Drive Array Controller. The CPQIDA-MIB DEFINITIONS is the source MIB file.
Server is running W2k8 R2 Enterprise. The system managmenet home page doesn't show any errors, the IML hasn't logged an event in 4 months, and the windows system event logs have no such event. I checked our alerting system and it's fine. The source ip address informaiton of the alert matches the ip address assigned to the HOST that supposed to have alerted. I even pinged the server from the alert server console and the name resolves correctly.
Here's the trap informaiton.
serverhostname, 16, Slot 0, 4, 3, 39, 5001438011FD8160, 5.70, 1048576
[184.108.40.206.220.127.116.11.0, 18.104.22.168.22.214.171.124.126.96.36.199, 188.8.131.52.184.108.40.206.220.127.116.11.20.4, 18.104.22.168.22.214.171.124.126.96.36.199.1.4, 188.8.131.52.184.108.40.206.220.127.116.11.10.4, 18.104.22.168.22.214.171.124.126.96.36.199.2.4, 188.8.131.52.184.108.40.206.220.127.116.11.15.4, 18.104.22.168.22.214.171.124.126.96.36.199.3.4, 188.8.131.52.184.108.40.206.220.127.116.11.12.4]
I'm going to have our operations group reboot the HOST and watch the POST in the ILO to see if it produces a POST error message.
09-07-2013 01:57 AM - edited 09-07-2013 02:00 AM
Re: ProLiant BL465c G7 PSP 18.104.22.168 Erroneous SNMP Trap 3033_4
The trap 3033 is cpqDa6CntrlStatusChange:
Controller Status Change. This trap signifies that the agent has detected a change in the status of a drive array controller. The variable cpqDaCntlrBoardStatus indicates the current controller status. User Action: If the board status is generalFailure(3), you may need to replace the controller. If the board status is cableProblem(4), check the cable connections between the controller and the storage system. Contained in Module(s): CPQIDA-MIB
The trap information objects are, in order:
- sysName (= serverhostname)
- cpqHoTrapFlags (= 16, see below)
- cpqDaCntrlHwLocation (= Slot 0)
- cpqDaCntrlIndex (= 4)
- cpqDaCntrlBoardStatus (= 3 = generalFailure)
- cpqDaCntrlModel (= 39 = sa-p410i)
- cpqDaCntrlSerialNumber (= 5001438011FD8160)
- cpqDaCntrlFWRev (= 5.70)
- cpqDaAccelTotalMemory (= 1048576)
So it does not look like a cable problem (status 4), but a general failure (status 3) in controller #4 (which is Slot 0 as indicated).
The description of the cpqHoTrapFlags in the MIB file is as follows:
This is a collection of flags used during trap delivery. Each bit has the following meaning: Bit 5-31: RESERVED: Always 0. Bit 2-4: Trap Condition 0 = Not used (for backward compatibility) 1 = Condition unknown or N/A 2 = Condition ok 3 = Condition degraded 4 = Condition failed 5-7 = reserved Bit 1: Client IP address type 0 = static entry 1 = DHCP entry Bit 0: Agent Type 0 = Server 1 = Client NOTE: bit 31 is the most significant bit, bit 0 is the least significant. Contained in Module(s): CPQHOST-MIB
Value 16 is 0x00000010 in hex, so only bit 4 is set. So the value of bits 2-4 is 4: that's "Condition failed".
Before rebooting, you might use the ACU to verify the state of the disk array controller(s).
The current firmware version for Smart Array P410i is 9.30, so your version 5.70 seems very, very old. While you're at the ACU, verify the firmware version and consider updating if necessary.