Solved

Monitoring power supply/fan/temperature of VDX 6740s

  • 19 August 2019
  • 4 replies
  • 241 views

Hello,

I'm trying to configure Nagios to get the state of PS/fan and temperature on two 6740 VDXs (one running 6.0.2b NOS and another one running 7.2.0b NOS).

The SNMP configuration on both devices is identical:

code:
snmp-server contact noc@domain.org
snmp-server location "DCA"
snmp-server sys-descr "Brocade VDX 6740"
snmp-server community xxxxx groupname NOC
snmp-server view All 1 included
snmp-server view NOC 1 included
snmp-server group NOC v2c read All


The script I'm using is from here.

I have no issues with the VDX running 7.2.0b NOS, but with 6.0.2b I can't get a list of sensors (it looks like relevant OIDs don't exist, hence the script fails).

Below is a working flow (from 7.2.0b):

code:
14:55:57.949952 IP 192.168.111.31.55754 > 10.9.200.55.161:  C="xxxxx" GetRequest(28)  .1.3.6.1.2.1.1.1.0
14:55:57.954456 IP 10.9.200.55.161 > 192.168.111.31.55754: C="xxxxx" GetResponse(111) .1.3.6.1.2.1.1.1.0="Brocade VDX 6740 SFP, BR-VDX6740, Network Operating System Software Version 7.2.0b."
14:55:57.955427 IP 192.168.111.31.55754 > 10.9.200.55.161: C="xxxxx" GetBulk(33) N=0 M=25 .1.3.6.1.4.1.1588.2.1.1.1.1.22
14:55:58.011811 IP 10.9.200.55.161 > 192.168.111.31.55754: C="xxxxx" GetResponse(591) .1.3.6.1.4.1.1588.2.1.1.1.1.22.1.1.1=1 .1.3.6.1.4.1.1588.2.1.1.1.1.22.1.1.2=2 .1.3.6.1.4.1.1588.2.1.1.1.1.22.1.1.3=3 .1.3.6.1.4.1.1588.2.1.1.1.1.22.1.1.4=4 .1.3.6.1.4.1.1588.2.1.1.1.1.22.1.1.5=5 .1.3.6.1.4.1.1588.2.1.1.1.1.22.1.1.6=6 .1.3.6.1.4.1.1588.2.1.1.1.1.22.1.1.7=7 .1.3.6.1.4.1.1588.2.1.1.1.1.22.1.1.8=8 .1.3.6.1.4.1.1588.2.1.1.1.1.22.1.2.1=1 .1.3.6.1.4.1.1588.2.1.1.1.1.22.1.2.2=1 .1.3.6.1.4.1.1588.2.1.1.1.1.22.1.2.3=1 .1.3.6.1.4.1.1588.2.1.1.1.1.22.1.2.4=1 .1.3.6.1.4.1.1588.2.1.1.1.1.22.1.2.5=2 .1.3.6.1.4.1.1588.2.1.1.1.1.22.1.2.6=2 .1.3.6.1.4.1.1588.2.1.1.1.1.22.1.2.7=3 .1.3.6.1.4.1.1588.2.1.1.1.1.22.1.2.8=3 .1.3.6.1.4.1.1588.2.1.1.1.1.22.1.3.1=4 .1.3.6.1.4.1.1588.2.1.1.1.1.22.1.3.2=4 .1.3.6.1.4.1.1588.2.1.1.1.1.22.1.3.3=4 .1.3.6.1.4.1.1588.2.1.1.1.1.22.1.3.4=4 .1.3.6.1.4.1.1588.2.1.1.1.1.22.1.3.5=4 .1.3.6.1.4.1.1588.2.1.1.1.1.22.1.3.6=4 .1.3.6.1.4.1.1588.2.1.1.1.1.22.1.3.7=4 .1.3.6.1.4.1.1588.2.1.1.1.1.22.1.3.8=4 .1.3.6.1.4.1.1588.2.1.1.1.1.22.1.4.1=38


And here is a non-working one (from 6.0.2b):

code:
14:56:44.268436 IP 192.168.111.31.44629 > 10.8.200.93.161:  C="xxxxx" GetRequest(28)  .1.3.6.1.2.1.1.1.0
14:56:44.283328 IP 10.8.200.93.161 > 192.168.111.31.44629: C="xxxxx" GetResponse(112) .1.3.6.1.2.1.1.1.0="Brocade VDX 6740T-1G, VDX6740T-1G, Network Operating System Software Version 6.0.2b."
14:56:44.284395 IP 192.168.111.31.44629 > 10.8.200.93.161: C="xxxxx" GetBulk(33) N=0 M=25 .1.3.6.1.4.1.1588.2.1.1.1.1.22
14:56:45.106942 IP 10.8.200.93.161 > 192.168.111.31.44629: C="xxxxx" GetResponse(1045) .1.3.6.1.4.1.1588.2.1.1.1.4.12.0="" .1.3.6.1.4.1.1588.2.1.1.1.4.13.0="" .1.3.6.1.4.1.1588.2.1.1.1.28.1.1.1.16.0.196.245.124.26.165.72.0.0.0.0.0.0.0.0.65="NA" .1.3.6.1.4.1.1588.2.1.1.1.28.1.1.1.16.0.196.245.124.26.165.72.0.0.0.0.0.0.0.0.66="NA" .1.3.6.1.4.1.1588.2.1.1.1.28.1.1.1.16.0.196.245.124.26.165.72.0.0.0.0.0.0.0.0.67="NA" .1.3.6.1.4.1.1588.2.1.1.1.28.1.1.1.16.0.196.245.124.26.165.72.0.0.0.0.0.0.0.0.68="NA" .1.3.6.1.4.1.1588.2.1.1.1.28.1.1.1.16.0.196.245.124.26.165.72.0.0.0.0.0.0.0.0.69="NA" .1.3.6.1.4.1.1588.2.1.1.1.28.1.1.1.16.0.196.245.124.26.165.72.0.0.0.0.0.0.0.0.70="NA" .1.3.6.1.4.1.1588.2.1.1.1.28.1.1.1.16.0.196.245.124.26.165.72.0.0.0.0.0.0.0.0.71="NA" .1.3.6.1.4.1.1588.2.1.1.1.28.1.1.1.16.0.196.245.124.26.165.72.0.0.0.0.0.0.0.0.72="NA" .1.3.6.1.4.1.1588.2.1.1.1.28.1.1.1.16.0.196.245.124.26.165.72.0.0.0.0.0.0.0.0.73="NA" .1.3.6.1.4.1.1588.2.1.1.1.28.1.1.1.16.0.196.245.124.26.165.72.0.0.0.0.0.0.0.0.74="NA" .1.3.6.1.4.1.1588.2.1.1.1.28.1.1.1.16.0.196.245.124.26.165.72.0.0.0.0.0.0.0.0.75="NA" .1.3.6.1.4.1.1588.2.1.1.1.28.1.1.1.16.0.196.245.124.26.165.72.0.0.0.0.0.0.0.0.76="NA" .1.3.6.1.4.1.1588.2.1.1.1.28.1.1.1.16.0.196.245.124.26.165.72.0.0.0.0.0.0.0.0.77="NA" .1.3.6.1.4.1.1588.2.1.1.1.28.1.1.1.16.0.196.245.124.26.165.72.0.0.0.0.0.0.0.0.78="NA" .1.3.6.1.4.1.1588.2.1.1.1.28.1.1.1.16.0.196.245.124.26.165.72.0.0.0.0.0.0.0.0.79="NA" .1.3.6.1.4.1.1588.2.1.1.1.28.1.1.1.16.0.196.245.124.26.165.72.0.0.0.0.0.0.0.0.80="NA" .1.3.6.1.4.1.1588.2.1.1.1.28.1.1.1.16.0.196.245.124.26.165.72.0.0.0.0.0.0.0.0.81="NA" .1.3.6.1.4.1.1588.2.1.1.1.28.1.1.1.16.0.196.245.124.26.165.72.0.0.0.0.0.0.0.0.82="NA" .1.3.6.1.4.1.1588.2.1.1.1.28.1.1.1.16.0.196.245.124.26.165.72.0.0.0.0.0.0.0.0.83="NA" .1.3.6.1.4.1.1588.2.1.1.1.28.1.1.1.16.0.196.245.124.26.165.72.0.0.0.0.0.0.0.0.84="NA" .1.3.6.1.4.1.1588.2.1.1.1.28.1.1.1.16.0.196.245.124.26.165.72.0.0.0.0.0.0.0.0.85="NA" .1.3.6.1.4.1.1588.2.1.1.1.28.1.1.1.16.0.196.245.124.26.165.72.0.0.0.0.0.0.0.0.86="NA" .1.3.6.1.4.1.1588.2.1.1.1.28.1.1.1.16.0.196.245.124.26.165.72.0.0.0.0.0.0.0.0.87="NA"


Any hints would be greatly appreciated.

Thank you.
icon

Best answer by Truyen Phan 20 August 2019, 19:52

Hello,

If you are not using FCoE and/or NPIV, then there are no impact to disabling AG mode. After disabling it in the CLI, it will stop the AG service and re-sync HA between the two switch partitions which takes about 3-5 mins.
View original

4 replies

Userlevel 2
Hi,

Can you try the solution in this KB?

https://gtacknowledge.extremenetworks.com/articles/Solution/SNMP-OIDs-stopped-working-after-upgrade
@Truyen Phan many thanks -- I'll try it.

What would be the impact of disabling AG? Our 6740Ts running 6.0.2b are in a fabric, no FCoE, L2 only, with several ISLs.
Userlevel 2
Hello,

If you are not using FCoE and/or NPIV, then there are no impact to disabling AG mode. After disabling it in the CLI, it will stop the AG service and re-sync HA between the two switch partitions which takes about 3-5 mins.
Thank you very much -- worked like a charm!

Reply