VMware_SDWAN_Edge_SNMP_Guidance_and_tutor

VMware SDWAN Edge SNMP

1. VMware SD-WAN MIB (SNMP) VMware Oct 2019

2. SD-WAN MIB SNMP

3. Prior to version 3.3.2, the MIB supported by VMware SD-WAN Edge are: Host MIB: http://www.net-snmp.org/docs/mibs/HOST-RESOURCES-MIB.txt MIB-2: https://www.activexperts.com/admin/mib/rfc/rfc1213-mib/ And only system and interface portion are supported That means prior to version 3.3.2, by accessing the SNMP OID, there is no visibility to SD-WAN Overlay tunnel information, or SD-WAN Edge HA status In version 3.3.2, SD-WAN MIB feature is added New Feature: SD-WAN MIB in 3.3.2

4. Step 1: Configure SNMP (such as version, community, authentication) at the Device tab Step 1 How to enable SNMP access on the SD-WAN Edge

5. Step 2: In the firewall tab, whitelist the SNMP client IP address Step 2 How to enable SNMP access on the SD-WAN Edge *Note: Understood it looks a duplicated configuration to have allowed source IP in both “Device” and “Firewall” tab. However, that’s how the product works now, we need whitelist source IP in both “Device” and “Firewall” to make SNMP query works

6. There are two MIB files specific for VMware SD-WAN MIB, they are VELOCLOUD-MIB VELOCLOUD-EDGE-MIB FYI, these two files are located in /opt/ vc / etc / mibs folder in the SD-WAN Edge There are other MIBs required (dependency) to work with the two Velocloud MIB, they are SNMPv2-SMI SNMPv2-CONF SNMPv2-TC INET-ADDRESS-MIB IF-MIB UUID-TC-MIB Velocloud MIB VelocloudMIB

7. By loading the VELOCLOUD-MIB and VELOCLOUD-EDGE-MIB into MIB browser The VELOCLOUD-EDGE is specific under the OID .1.3.6.1.4.1.45346 There are 5 groups as of current release (3.3.2): vceHA vceHealth vceLink vcePath vceARP Understanding the Velocloud MIB

8. s nmpwalk : it is the best tool to query the SD-WAN Edge to get understand how the VELOCLOUD MIB works Here I will use a ubuntu Linux as an example Install snmp (apt-get install snmp ) Copy all the required MIB (SNMPv2-SMI, SNMPv2-CONF, SNMPv2-TC, INET-ADDRESS-MIB, IF-MIB, UUID-TC-MIB, VELOCLOUD-MIB, and VELOCLOUD-EDGE-MIB) to the folder / usr /share/ snmp / mibs In / etc / snmp / snmp.conf , put “ mibs +ALL” to load all MIBS To confirm the Velocloud MIB is loaded, issue command such as “ snmptranslate - Tp -IR vcePath ” SNMP client to learn about the Velocloud-EDGE-MIB

9. If MIB loaded properly: SNMP client to learn about the Velocloud-EDGE-MIB - continue

10. Say the SD-WAN Edge is with IP address 10.100.100.254, snmp v2c configured with community “vmware2019”, the command to walk-through the group vcePath is “ snmpwalk -v 2c -O X -c vmware2019 10.100.100.254 .1.3.6.1.4.1.45346.1.1.2.4.2” Sample snmpwalk Not showing all output for simplicity

11. Understanding the VELOCLOUD-EDGE-MIB by snmpwalk Notice the last field of the index is the tunnel IP address on the peer side

12. Understanding the VELOCLOUD-EDGE-MIB by snmpwalk By grep the tunnel peer’s IP address (in this example is 10.253.254.11), we can obtain all the information available regarding the overlay tunnel terminating at IP address 10.253.254.11. In this example, the peer Edge is named “VCE1-GoodTea”. The Rx and Tx latency are both 3ms, there are no packet loss or jitter in any direction (all jitter and lost are 0)

13. Understanding the VELOCLOUD-EDGE-MIB by snmpwalk If you want to get the full OID value, use -O fn instead of -O X

14. The following is a sample output of walking through the vceHealth group (which you can obtain CPU, memory usage): You can taste the other group like vceHA , vceLink , vceARP , I am not including the output here. Thank you snmpwalk of the vceHealth group