david-barbion / monitoring Goto Github PK

Hi,

We use a MSA2060, which only support SNMPv3. Can you tell me the default SNMPv3-Options for your nice sript?

SecuritySevel ? (noAuthNoPriv|authNoPriv|authPriv)
AuthLevel? (MD5/SHA)
PrivLevel? (DES)

I try several combinations, but I get always following Error:
UNKNOWN: SNMP Session : No response from remote host "172.31.244.143" during discovery
(In the firewall i can the, taht the SNMP-Request accepted)

Thanks!

Marco

replace Nagios::Plugin by Monitoring::Plugin line 39 on check_msa_hardware

Hello, can you add "snmp port" as argument for active check behind NAT?

Thank you.

I have encountered one "buggy" transceiver that sets the following limits for Rx Power:

• warning: -30 dBm (-30000)
• alarm: 0 dBm (0)

As seen on the switch:

           SFP Detail Diagnostics Information (internal calibration)
  ----------------------------------------------------------------------------
                Current              Alarms                  Warnings
                Measurement     High        Low         High          Low
  ----------------------------------------------------------------------------
  Temperature   29.24 C       100.00 C    -10.00 C     95.00 C       -5.00 C
  Voltage        3.29 V         3.63 V      2.90 V      3.50 V        3.00 V
  Current       19.68 mA      100.00 mA     0.00 mA    80.00 mA       1.00 mA
  Tx Power      -5.63 dBm       6.99 dBm  -15.08 dBm    4.99 dBm    -13.01 dBm
  Rx Power     -10.91 dBm       1.99 dBm    0.00 dBm    0.00 dBm    -30.00 dBm
  Transmit Fault Count = 0
  ----------------------------------------------------------------------------

Obviously, the limits are totally wrong. The sensible limits would be -12 and -15 or something similar.

Maybe check_cisco_nexus_hardware.pl could workaround such buggy transceivers something like:

• Maybe only for value type dBm?
• Test if the thresh_value for warning is lower than thresh_value for alarm
• If true, then set the alarm thresh_value to same as warning thresh_value

Debug output showing the transceiver:

threshold data: thresh_value=1997 tresh_relation=3 thresh_severity=20 sensor_value=-10915
compare -10915 to 1997 and will return 20 if operator 3 is met
greaterthan compare
comparison result: 1
threshold data: thresh_value=-30000 tresh_relation=1 thresh_severity=10 sensor_value=-10915
compare -10915 to -30000 and will return 10 if operator 1 is met
lessthan compare
comparison result: 1
threshold data: thresh_value=0 tresh_relation=1 thresh_severity=20 sensor_value=-10915
compare -10915 to 0 and will return 20 if operator 1 is met
lessthan compare
comparison result: 20
threshold data: thresh_value=0 tresh_relation=3 thresh_severity=10 sensor_value=-10915
compare -10915 to 0 and will return 10 if operator 3 is met
greaterthan compare
comparison result: 1
sensor_alarm = 20 (nagios_rc=2)
add new sensor status for sensor_id = 300014093 (Ethernet1/9 Lane 1 Transceiver Receive Power Sensor->Transceiver(slot:1-port:9)->Linecard-1 Port-9->x + x Supervisor->LinecardSlot-1->nexus->Fabric Stack Root) rc=OK. type is =dBm

Hi we are currently testing this check and did some tests of how it would react if a few went offline, but it doesnt seem to raise a critical, it only shows errors if its able to reach the FEXes, Here is my output, it would be great to "expect" all of these below to be reachable and testable over snmp.

7 7 Offline

nexus5000# show fex
  FEX         FEX           FEX                       FEX               
Number    Description      State            Model            Serial     
------------------------------------------------------------------------
1          1           Online       
2          2           Online         
3          3           Online         
4          4           Online         
5          5           Online         
6          6           Online         
7          7           Offline         
8          8           Online         

Hi David

check_cisco_nexus_hardware.pl failing to get info on getting info for few, further verified from cisco that oid 1.3.6.1.4.1.9.9.91.1.2.1.1.4 is not supported as of now.

ciscodev.example.com: CRITICAL (12 sensors failed on 394, 0 fan failed on 38, 0 psu failed on 36)
OK: dBm (Ethernet1/32(Rx-dBm)) is failed: 0milli dBm is less than 2999
OK: dBm (Ethernet3/15(Rx-dBm)) is failed: 0milli dBm is less than 2999
OK: dBm (Ethernet1/31(Rx-dBm)) is failed: 0milli dBm is less than 2999
MAJOR: amperes (Ethernet1/31(ampere)) is failed: 0milli amperes is less than 11800
MAJOR: amperes (Ethernet3/15(ampere)) is failed: 238milli amperes is less than 11800
OK: dBm (Ethernet1/32(Tx-dBm)) is failed: 0milli dBm is less than 2699
OK: dBm (Ethernet3/15(Tx-dBm)) is failed: 0milli dBm is less than 2699
MAJOR: dBm (Ethernet1/31(Tx-dBm)) is failed: -17695milli dBm is less than 2699
OK: dBm (Ethernet3/16(Rx-dBm)) is failed: 0milli dBm is less than 2999
MAJOR: amperes (Ethernet1/32(ampere)) is failed: 210milli amperes is less than 11800
MAJOR: dBm (Ethernet3/16(Tx-dBm)) is failed: -20969milli dBm is less than -7304
MAJOR: amperes (Ethernet3/16(ampere)) is failed: 0milli amperes is less than 11800
| Ethernet1/17(ampere)=8528amperes;;;;

check_netapp_allvols.pl while running this script Giving Error
Use of uninitialized value in string ne at ./check_netapp_allvols.pl line 170.
Use of uninitialized value in string ne at ./check_netapp_allvols.pl line 170.
Use of uninitialized value in string ne at ./check_netapp_allvols.pl line 170.