Hello,
I've done a quick patch to get vPC metrics from NX-OS devices, can you kindly take a look at it? The Jira issue is https://jira.observium.org/projects/OBS/issues/OBS-3006
For now, that adds just graphs to Status section. I can put some effort to create a full-blown vPC tab on the Device page to get even more stats for it, what do you think on that?
--- Sergei Fomin
Hi Sergei,
That’s pretty cool. Adding a vPC entity type might be useful.
Can you show me how NX-OS presents this information in the CLI/web UI?
Thanks,
Adam.
From: observium observium-bounces@observium.org On Behalf Of xomka686 via observium Sent: 25 April 2020 16:26 To: Observium observium@observium.org Cc: xomka686 xomka686@protonmail.com Subject: [Observium] Attention to OBS-3006 (vPC onNX-OS)
Hello,
I've done a quick patch to get vPC metrics from NX-OS devices, can you kindly take a look at it? The Jira issue is https://jira.observium.org/projects/OBS/issues/OBS-3006
For now, that adds just graphs to Status section. I can put some effort to create a full-blown vPC tab on the Device page to get even more stats for it, what do you think on that?
---
Sergei Fomin
Hi Adam,
Sure, CLI commands are "show vpc" and "show vpc peer-keepalive". There's no on-the-box GUI to NX-OS, all the GUIs are external servers like DCNM and to be honest not everyone runs them.
Outputs of the vPC CLI commands are:
-------------------------- # show vpc Legend: (*) - local vPC is down, forwarding via vPC peer-link
vPC domain id : 123 Peer status : peer link is down vPC keep-alive status : Suspended (Destination IP not reachable) Configuration consistency status : failed Per-vlan consistency status : success Configuration inconsistency reason: Consistency Check Not Performed Type-2 inconsistency reason : Consistency Check Not Performed vPC role : primary Number of vPCs configured : 0 Peer Gateway : Enabled Dual-active excluded VLANs : - Graceful Consistency Check : Disabled (due to peer configuration) Auto-recovery status : Enabled, timer is off.(timeout = 60s) Delay-restore status : Timer is off.(timeout = 30s) Delay-restore SVI status : Timer is off.(timeout = 10s) Operational Layer3 Peer-router : Disabled Virtual-peerlink mode : Disabled
--------------------------
# show vpc peer-keepalive
vPC keep-alive status : Suspended (Destination IP not reachable) --Send status : Success --Last send at : 2020.04.27 20:12:26 438 ms --Sent on interface : mgmt0 --Receive status : Failed --Last update from peer : (305) seconds, (365) msec
vPC Keep-alive parameters --Destination : 10.0.0.12 --Keepalive interval : 1000 msec --Keepalive timeout : 5 seconds --Keepalive hold timeout : 3 seconds --Keepalive vrf : management --Keepalive udp port : 3200 --Keepalive tos : 192
--------------------------
And here's a sample snmpwalk on CISCO-VPC-MIB on NX-OSv 9.3.3:
cVpcPeerKeepAliveDestAddrType.123 = ipv4 cVpcPeerKeepAliveDestAddr.123 = "0A 00 00 0C " cVpcPeerKeepAliveSourceAddrType.123 = ipv4 cVpcPeerKeepAliveSourceAddr.123 = "0A 00 00 03 " cVpcPeerKeepAliveUdpPort.123 = 3200 cVpcPeerKeepAliveInterval.123 = 1000 cVpcPeerKeepAliveTimeout.123 = 5 cVpcPeerKeepAliveHoldTimeout.123 = 3 cVpcPeerKeepAliveTos.123 = 0 cVpcPeerKeepAlivePrecedence.123 = 6 cVpcPeerKeepAliveTosByte.123 = 192 cVpcPeerKeepAliveVrfName.123 = management cVpcPeerKeepAliveStatus.123 = suspendedAsDestIPUnreachable cVpcPeerKeepAliveTime.123 = 0 cVpcPeerKeepAliveMsgSendStatus.123 = success cVpcPeerKeepAliveMsgLastSendTime.123 = 2020-4-27,20:10:41.0,+0:0 cVpcPeerKeepAliveMsgSendInterface.123 = 83886080 cVpcPeerKeepAliveMsgRcvrStatus.123 = failure cVpcPeerKeepAliveMsgLastReceiveTime.123 = 2020-4-27,20:7:21.0,+0:0 cVpcPeerKeepAliveMsgReceiveInterface.123 = 83886080 cVpcRoleStatus.123 = primary cVpcDualActiveDetectionStatus.123 = false cVpcSystemAdminMacAddress.123 = 0:0:0:0:0:0 cVpcSystemOperMacAddress.123 = 0:23:4:ee:be:7b cVpcLocalOperMacAddress.123 = 0:69:f1:9c:1b:8 cVpcSystemAdminPriority.123 = 32667 cVpcSystemOperPriority.123 = 32667 cVpcLocalRoleAdminPriority.123 = 4096 cVpcLocalRoleOperPriority.123 = 0 cVpcStatsPeerKeepAliveMsgsSent.123 = 204 cVpcStatsPeerKeepAliveMsgsRcved.123 = 0 cVpcStatsPeerKeepAliveAvgInterval.123 = 0 cVpcStatsPeerStatusChangeCount.123 = 0 cVpcStatusPeerLinkIfIndex.123 = 369099207
That MIB provides some nice stats like amount of keepalives sent/received, uptime of keepalive and role priorities.
--- Sergei Fomin
‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ On Sunday, April 26, 2020 3:57 PM, Adam Armstrong via observium observium@observium.org wrote:
Hi Sergei,
That’s pretty cool. Adding a vPC entity type might be useful.
Can you show me how NX-OS presents this information in the CLI/web UI?
Thanks,
Adam.
From: observium observium-bounces@observium.org On Behalf Of xomka686 via observium Sent: 25 April 2020 16:26 To: Observium observium@observium.org Cc: xomka686 xomka686@protonmail.com Subject: [Observium] Attention to OBS-3006 (vPC onNX-OS)
Hello,
I've done a quick patch to get vPC metrics from NX-OS devices, can you kindly take a look at it? The Jira issue is https://jira.observium.org/projects/OBS/issues/OBS-3006
For now, that adds just graphs to Status section. I can put some effort to create a full-blown vPC tab on the Device page to get even more stats for it, what do you think on that?
Sergei Fomin
participants (2)
-
Adam Armstrong
-
xomka686