08-02-2013 04:00 AM - edited 03-01-2019 07:22 AM
If entity traps are enabled, will the failure of a PSU in a FEX (with 2 PSU's) result in a trap being sent or are the entity traps only for the 5000 rather than the 2000.
Reason for asking:I have a number of failed PSU's in FEX's which might have been a failed since power on and therefore have never transitioned from working to failing to send a trap. The FEX itself is constantly complaining of voltage issues
08/02/2013 04:52:41.572800: Err:over volt fault occured for ps:1
08/02/2013 04:52:41.572839: Err:stat=2048
08/02/2013 04:52:41.572853: Err:over-output-current fault occured ps:1
08/02/2013 04:53:14.936602: Err:over volt fault occured for ps:1
08/02/2013 04:53:14.936645: Err:stat=2048
08/02/2013 04:53:14.936658: Err:over-output-current fault occured ps:1
08/02/2013 04:52:41.572800: Err:over volt fault occured for ps:1
08/02/2013 04:52:41.572839: Err:stat=2048
08/02/2013 04:52:41.572853: Err:over-output-current fault occured ps:1
08/02/2013 04:53:14.936602: Err:over volt fault occured for ps:1
08/02/2013 04:53:14.936645: Err:stat=2048
08/02/2013 04:53:14.936658: Err:over-output-current fault occured ps:1
08/02/2013 04:53:30.46732: satctrl_alive_hdlr: alive_count is 23001700
Power Supply Fex 103:
---------------------------------------------------------------------------
Voltage: 12 Volts
-----------------------------------------------------
PS Model Power Power Status
(Watts) (Amp)
-----------------------------------------------------
1 -- -- -- fail/shutdown
2 N2200-PAC-400W 396.00 33.00 ok
Thanks Andy Metcalf
08-05-2013 01:06 AM
Hello Andy,
Do you receive SNMP traps for other events ? any special config like SNMPv3 / authentication etc ?
I have not tested in lab. Is it possible for you to check " cefcFRUPowerStatusEntry " / 1.3.6.1.4.1.9.9.117.1.1.2.1.2.471 OID ?
or do snmp walk for 1.3.6.1.4.1.9.9.117.1.1.2.1 ?
Padma
08-05-2013 01:45 AM
Padma,
Thanks for your response, we do get snmp traps from these switches, I tested that with a "test pfm snmp test-trap powersupply" and the trap was received, There is no special snmp configuration. The OID you are requesting returns a different value for each of our two 5010 switches
switch A= SNMPv2-SMI::enterprises.9.9.117.1.1.2.1.3.471 = INTEGER: 1087
switch B= SNMPv2-SMI::enterprises.9.9.117.1.1.2.1.3.471 = INTEGER: 1018
In both switches entity traps are enabled
entity : entity_mib_change Yes
entity : entity_module_status_change Yes
entity : entity_power_status_change Yes
entity : entity_module_inserted Yes
entity : entity_module_removed Yes
entity : entity_unrecognised_module Yes
entity : entity_fan_status_change Yes
entity : entity_power_out_change Yes
I notice your OID references "FRU" and I see a hidden extension to the snmp-server enable trap command
hidden-nameB(config)# snmp-server enable trap entity ?
entity_fan_status_change Entity Fan Status Change
entity_mib_change Entity MIB change
entity_module_inserted Entity Module Inserted
entity_module_removed Entity Module Removed
entity_module_status_change Entity Module Status Change
entity_power_out_change Entity Power Out Change
entity_power_status_change Entity Power Status Change
entity_unrecognised_module Entity Unrecognised Module
hidden-nameB(config)# snmp-server enable trap entity fru
hidden-nameB(config)#
I would be interested to see if this FRU was required yet hidden.
SW version system: version 5.0(3)N2(2)
07-15-2014 09:51 AM
5.1(3) does not have the fru command option. The command is snmp_server enable traps entity entity_power_status_change.
I don't believe this is turned on by default, but I cannot find any documentation that says this command is not enabled by default with the snmp-server enable traps command.
I also do not see any documentation that states this command will notify us of a Nexus 2000 power supply failure. Please advise.
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: