Add vPC support for Cisco Nexus switches

Added in r12908.

Thanks!

Any update here?

Do you still need second vPC snmp dump. 

Hey Mike,

I'm using NX-OSv on a personal PC, so that's hard to provide access to it

Let me also attach the outputs you requested as Satish provided output for 1 switch only and asked for an output from 2 switches in a vPC pair. Those have Port-channel456 as a Peer-link, Ethernet1/1 and Ethernet 1/2 are its member ports. vPC Peer-Keepalive is run with default timers over Mgmt0 interfaces, their IPs are 10.0.0.11 and 10.0.0.12. Priority of sw1 is 4096, sw2 - 8192.

[^myagent_sw1.snmpwalk.tar.gz] [^myagent_sw2.snmpwalk.tar.gz]

@Mike, 

Here is my vPC N9K-9396PX switch snmp dump file as you request (This is the output of one of vPC pair device). [^myagent.snmpwalk]

j-v-c can you provide snmp access for example device(s)?
If that not possible, make at least snmp dumps for 2 (vPC linked) devices as:

snmpbulkwalk -v2c -c <community>  --hexOutputLength=0 -ObentxU <hostname> .1 > myagent.snmpwalk

snmpbulkwalk -v2c -c <community>  --hexOutputLength=0 -ObentxU <hostname> .1.3.6.1.4.1 >> myagent.snmpwalk

You're welcome!

"discovery.php -h all" -m sensors saying invalid options

True, full syntax is "discovery.php -h all -m sensors" for that to work. I meant to advise to run discovery only for the sensors module as otherwise it might be tedious to watch all the params of all the hosts to be discovered in sequence.

My N3K running 6.x nxos version so not able to detect those MIBs. but N9K working great.

Cool for N9K! For N3K, NX-OS 7.0(3)I7 is current stable branch, so it's safe to go for it.

Do you think we should make seperate tab button call vPC (Just like we have OSFP section or routing section in front page of device) that way we know which switch working under vPC

I asked Mike here and wrote to the mailing list. Let's see what he feels about it.

Thanks! its working now after doing "discovery.php -h all"   -m sensors saying invalid options. 

My N3K running 6.x nxos version so not able to detect those MIBs. but N9K working great. Do you think we should make seperate tab button call vPC (Just like we have OSFP section or routing section in front page of device)  that way we know which switch working under vPC 

Hello Satish,

There shouldn't be any problem with VPC-MIB on N9K-C9396PX because according to Cisco CISCO-VPC-MIB support for Nexus 9000 was introduced in 7.0(3)I2(1). For N3K-3048PQ a similar doc was updated in 2014 and talks about NX-OS 5.0(3)U1(1) so no idea if VPC-MIB support was added later on.

I think you can try upgrading N3Ks to 7.0(3)I2(1) or newer to get CISCO-VPC-MIB support on those. As N3K and N9K share the NX-OS code trains, I believe 7.0(3)I2(1) introduced the same features for both of them.

Regarding Observium-specific bits, do `discovery.php -m sensors` after you apply the patch to get the vPC metrics. No restart of the Apache is required though.

@Sergei, 

I have applied your patch but somehow i can't see any status on GUI, do i need to do anything else except just patch those file. I did restarted apache. 

I am running cisco N9K-9396PX switches and N3K-3048PQ.