Related References

• Cisco Catalyst SD-WAN Control Components Compatibility Matrix and Server Recommendations

• Cisco Catalyst SD-WAN Device Compatibility

User Documentation

Communications, Services, and Additional Information

• Sign up for Cisco email newsletters and other communications at: Cisco Profile Manager.

• For information on the latest technical, advanced, and remote services to increase the operational reliability of your network visit Cisco Services.

• To browse and discover secure, validated enterprise-class apps, products, solutions, and services, visit Cisco Devnet.

• To obtain general networking, training, and certification titles from Cisco Press Publishers, visit Cisco Press.

• To find warranty information for a specific product or product family, visit Cisco Warranty Finder.

• To view open and resolved bugs for a release, access the Cisco Bug Search Tool.

• To submit a service request, visit Cisco Support.

Documentation Feedback

To provide feedback about Cisco technical documentation use the feedback form available in the right pane of every online document.

Use the SNMP template to configure SNMP parameters for all Cisco vEdge devices and Cisco IOS XE Catalyst SD-WAN devices running the Cisco Catalyst SD-WAN software.

Navigate to the Template Screen and Name the Template

1. From the Cisco SD-WAN Manager menu, choose Configuration > Templates.

2. Click Device Templates.

   Note	In Cisco vManage Release 20.7.x and earlier releases, Device Templates is titled as Device

3. From the Create Template drop-down, select From Feature Template.

4. From the Device Model drop-down, select the type of device for which you are creating the template.

5. Click Additional Templates, which scrolls the page to Additional Templates section.

6. From the Cisco SNMP drop-down under Additional Templates, click Create Template.

   The SNMP template form is displayed. The top of the form contains fields for naming the template, and the bottom contains fields for defining SNMP parameters.

7. In the Template Name field, enter a name for the template. The name can be up to 128 characters and can contain only alphanumeric characters.

8. In the Template Description field, enter a description of the template. The description can be up to 2048 characters and can contain only alphanumeric characters.

9. To save the SNMP feature template, click Save.

When you first open a feature template, for each parameter that has a default value, the scope is set to Default (indicated by a check mark), and the default setting or value is shown. To change the default or to enter a value, click the scope drop-down and select one of the following:

Attach the SNMP Feature Template to the Device Template

Once you have created the SNMP feature template, you need to attach the feature template to the device template.

Note	You are required to recreate the SNMP feature templates as the templates created prior to Cisco vManage Release 20.5 fails when attached to the device.

To attach the SNMP feature template:

1. In Device Templates, select the SNMP template that you created.

2. Click ... and choose Attach Devices. The Attach Devices dialog box opens with Select Devices selected.

3. In the Available Devices column, select a group and search for one or more devices, select a device from the list, or click Select All.

4. Click the arrow pointing right to move the device to the Selected Devices column on the right.

5. Click Attach.

Configure Basic SNMP

To configure basic SNMP, select SNMP and configure the following parameters. All parameters are required.

To save the feature template, click Save.

To configure SNMPv3, in SNMP Version, navigate to template page and configure groups and trap information:

• From the Cisco SD-WAN Manager menu, choose Configuration > Templates.

• Click Device Templates.

  Note	In Cisco vManage Release 20.7.x and earlier releases, Device Templates is titled as Device

• From the Create Template drop-down, select From Feature Template.

• From the Device Model drop-down, select the type of device for which you are creating the template.

• Click Additional Templates, which scrolls the page to Additional Templates section.

• From the SNMP drop-down under Additional Templates, click Create Template.

  The SNMP template form is displayed. The top of the form contains fields for naming the template, and the bottom contains fields for defining SNMP parameters.

• In the Template Name field, enter a name for the template. The name can be up to 128 characters and can contain only alphanumeric characters.

• In the Template Description field, enter a description of the template. The description can be up to 2048 characters and can contain only alphanumeric characters.

• In SNMP Version section, click V3. For SNMPv3, you can configure groups, users, and trap information.

• In the Trap section, select Trap Group to configure trap. Then click Add New Trap Group, and configure the parameters as listed below:

To save the trap type module, click Save.

To configure SNMP views, in the View & Groups section, select View. Then click New View, and configure the following parameters:

To configure the SNMP group, click New Group, and configure the following parameters:

Note	It's mandatory to create an SNMP view before you proceed with SNMP group configuration.

To add the SNMP group, click Add.

In the User section, click Add New User and enter the following parameters to configure SNMPv3 users:

Note	In Cisco vManage Release 20.6.x, if the SNMP user is configured with Auth-SHA-256 and Priv-AES-256, use a special port 1161 for SNMP queries.

To configure trap target servers, in the Trap section, select Trap Target Server. Then click Add New Trap Group, and configure the parameters as listed below:

To add the Trap Target Server, click Add.

To save the feature template, click Save.

To configure SNMPv3, in SNMP Version, navigate to Template page and configure groups and trap information:

1. From the Cisco SD-WAN Manager menu, choose Configuration > Templates.

2. Click Device Templates.

   Note	In Cisco vManage Release 20.7.x and earlier releases, Device Templates is titled Device

3. From the Create Template drop-down list, choose From Feature Template.

4. From the Device Model drop-down list, choose the type of device for which you are creating the template.

5. Click Additional Templates. This takes you to the Additional Templates section.

6. From the Cisco SNMP drop-down list, choose Create Template.

   The SNMP template form containing fields for naming the template and for defining SNMP parameters is displayed.

7. In the Template Name field, enter a name for the template. The name can be up to 128 characters and can contain only alphanumeric characters.

8. In the Template Description field, enter a description of the template. The description can be up to 2048 characters and can contain only alphanumeric characters.

9. In SNMP Version section, click V3. For SNMPv3, you can configure groups and trap information.

10. In the View & Groups section, click View, choose New View, and configure the following fields:

    Table 18. View and Groups Parameters for Cisco IOS XE Catalyst SD-WAN Devices

    Field Name	Description
    Name	Enter a name for the view. A view specifies the MIB objects that the SNMP manager can access. The view name can be a maximum of 255 characters. You must add a view name for all the views before adding a group.
    Object Identifiers (OID)	Click Add Object Identifiers and configure the following parameters: Object Identifier: Enter the OID of the object. For example, to view the internet part of the SNMP MIB, enter the OID 1.3.6.1. To view the private part of the Cisco Catalyst SD-WAN MIB, enter the OID 1.3.6.1.4.1.9. Use the asterisk wildcard (*) in any position of the OID subtree to match any value at that position rather than matching a specific type or name. Exclude OID: Click Off to include the OID in the view or click On to exclude the OID from the view. To remove an OID from the list, click Delete adjacent to the corresponding entry. To add an OID to the view list, click Add.

11. Click Add.

Click Group, choose New Group, and configure the following parameters.

Note	It's mandatory to create an SNMP view before you proceed with SNMP group configuration.

To add the SNMP group, click Add.

To configure SNMPv3 users, in the User section, click New User, and provide information in the following fields. Note that it's mandatory to create an SNMP group before you proceed with SNMP user configuration.

Note	The SNMP authentication password supports all the special characters except exclamation (!) character. If you want to use the exclamation (!) in your password, you must use that password in double quotes. For example, "password!".

To add an SNMP user, click Add.

(Optional) To configure the Trap Target server, in the Trap section, click New Trap Target, and enter information in the following fields. Note that it's mandatory to create an SNMP user before you proceed with trap target server configuration.

To add the Trap Target server, click Add.

To save the feature template, click Save.

Assign SNMP Agent System Information

Set the system contact and location of the SNMP agent.

1. Set the system contact string, which is the SNMP contact name:

   Device# config-transaction 
   Device(config)# snmp-server contact text

2. Set the system location string, which is the SNMP location:

   Device(config)# snmp-server location text

Configure Context-to-Network Entity Mapping

Configure an SNMP context-to-map to a logical network entity, such as a virtual routing and forwarding (VRF):

1. Map an SNMP context to a logical network, using the following command:

   Device# config-transaction
   Device(config)# snmp-server context context-name

2. Enable SNMP authorization failure (authFail) traps during an unknown SNMP context error:

   Device(config)# snmp-server trap authentication unknown-context

Configure SNMPv1 and SNMPv2c

(Optional) When you configure SNMPv1 and SNMPv2c, you can optionally create or modify views for community strings to limit which MIB objects an SNMP manager can access using the following procedure:

1. Create or modify an SNMP view along with an Object Identifier (OID):

   Device# config-transaction
   Device(config)# snmp-server view view-name oid-tree included

2. Create or modify access control for an SNMP community:

   Device(config)# snmp-server community string [view view-name][ro |rw ][access-list-number/name]

Configure SNMPv3

Ensure that you configure SNMP groups and users with passwords to configure SNMPv3 and to use the SNMPv3 security mechanism for handling SNMP packets.

1. Specify a new SNMPv3 server group or a table that maps SNMP users to SNMP views:

   Device# config-transaction
   Device(config)# snmp-server group group-name v3 {auth |noauth |priv}[read readview][write writeview
   ][notify notifyview][access [access-list-number | access-name][ipv6 named-access-list]
   

2. Configure a new user to an SNMPv3 group:

   Device(config)# snmp-server user username group-name [remote ip-address[udp-port port][vrf vrf-name]]
   v3 [encrypted][auth {md5|sha} auth-password][access [ipv6 nacl][priv {des|3des|aes|aes {128|256}}privpassword]{acl-number|acl-name}]

Note	For security reasons, the user command is not listed in the possible completions of the command line help. However, you can still use the user command when configuring a new user for an SNMPv3 group.

Define the Maximum SNMP Agent Packet Size

Define the maximum packet size that is permitted when the SNMP agent is receiving a request or generating a reply:

Device# config-transaction
Device(config)# snmp-server packetsize byte-count

Configure SNMP Notifications

Configure a device to send SNMP traps.

1. Specify the recipient of an SNMP notification operation:

   Device# config-transaction
   Device(config)# snmp-server host {host-name|ip-address}[vrf vrf-name|traps|version{1|2c|3[auth|noauth|priv]}]community-string
   [udp-port port [notification-type]|notification-type]

2. Change SNMP notification operation values:

   Device(config)# snmp-server  trap-source interface

Enable SNMP Notifications

Note that you can enable or disable SNMP notifications.

Use the following commands in configuration mode to enable the specified notification.

1. Enable all the possible traps (omp, policy, security, system) for Cisco Catalyst SD-WAN notification:

   Device# config-transaction
   Device(config)# snmp-server enable traps sdwan

2. Enable SNMP notifications for rising alarm changes:

   Device# config-transaction
   Device(config)# snmp-server enable traps alarms priority

3. Enable SNMP notifications for configuration changes:

   Device# config-transaction
   Device(config)# snmp-server enable traps config

4. Send entity MIB notifications to a host:

   Device# config-transaction
   Device(config)# snmp-server enable traps entity

5. Send information about the state of physical components such as disk, memory, and CPU utilization:

   Device# config-transaction
   Device(config)# snmp-server enable traps entity-state

6. Enable SNMP notifications for OSPF transition state changes on a virtual or nonvirtual OSPF interface:

   Device# config-transaction
   Device(config)# snmp-server enable traps ospf state-change

7. Enable SNMP notifications for OSPF errors (authentication failure, bad packet issues, and configuration errors):

   Device# config-transaction
   Device(config)# snmp-server enable traps ospf errors

8. Enable SNMP notifications for OSFP link-state advertisements (LSAs):

   Device# config-transaction
   Device(config)# snmp-server enable traps ospf lsa

9. Enable SNMP notifications for OSPF configuration mismatch errors on virtual or nonvirtual interfaces:

   Device# config-transaction
   Device(config)# snmp-server enable traps ospf cisco-specific errors

10. Enable the authentication failure, linkup, linkdown, coldstart, or warmstart notifications:

    Device# config-transaction
    Device(config)# snmp-server enable traps snmp [authentication][linkup][linkdown][coldstart][warmstart]

11. Enable SNMP configuration copy notifications:

    Device# config-transaction
    Device(config)# snmp-server enable traps config-copy

12. Enable SNMP configuration CTID notifications:

    Device# config-transaction
    Device(config)# snmp-server enable traps config-ctid

13. Enable SNMP Embedded Event Manager notifications:

    Device# config-transaction
    Device(config)# snmp-server enable traps event-manager

14. Enable CPU thresholding violation notifications:

    Device# config-transaction
    Device(config)# snmp-server enable traps cpu threshold

15. Enable Flash device insertion and removal SNMP notifications:

    Device# config-transaction
    Device(config)# snmp-server enable traps flash [insertion][removal]

16. Enable a device to send SNMP notifications when memory pool buffer usage reaches a new peak:

    Device# config-transaction
    Device(config)# snmp-server enable traps memory [bufferpeak]

17. Enable a device to send system logging message notifications:

    Device# config-transaction
    Device(config)# snmp-server enable traps syslog

Configure Interface Index Persistence

You can globally enable ifIndex values in the IF-MIB so that it persists across reboots. This configuration allows consistent identification of specific interfaces that use SNMP.

Device# config-transaction
Device(config)# snmp ifmib ifindex persist

To configure SNMP traps using Cisco SD-WAN Manager, use the information provided in CLI Add-on Feature templates to enter the configuration applicable to your environment. The following example shows how to configure SNMP to send traps to 172.16.1.111 and 172.16.1.27 using SNMPv2c, and to the host 172.16.1.33 using SNMPv3. The SNMP traps are sent by configuring a VRF routing table and address family submode.

config-transaction
!
    
       vrf definition 172
       address-family ipv4
       exit-address-family

       snmp-server contact Admin
       snmp-server location Lab-7
       
       snmp-server context CISCOCONTEXT
       no snmp-server trap authentication unknown-context
!
       snmp-server view v2 1.3.6.1.6.3.15 included
       snmp-server community public view v2 ro
       snmp-server view v3 1.3.6.1.6.3.18 included
!
       snmp-server community private view v3 ro 5
       snmp-server community public view v3 ro
       snmp-server group groupNoAuthNoPriv v3 noauth read v3
       
!
       snmp-server packetsize 1300
       snmp-server host 172.16.1.27 vrf 172 version 2c public udp-port 162
       snmp-server host 172.16.1.111 vrf 172 version 2c public udp-port 161
       snmp-server host 172.16.1.33 vrf 172 version 3 auth v3userAuthPriv udp-port 16664

       snmp-server trap-source Loopback0
!
       snmp-server enable traps sdwan
       snmp-server enable traps alarms informational
       snmp-server enable traps config
       snmp-server enable traps entity
       snmp-server enable traps entity-state
       snmp-server enable traps snmp authentication coldstart linkdown linkup warmstart
       snmp-server enable traps ospf state-change
       snmp-server enable traps ospf errors
       snmp-server enable traps ospf lsa
       snmp-server enable traps ospf cisco-specific errors!
       snmp-server enable traps ospf state-change
       snmp-server enable traps ospf errors
!
       snmp ifmib ifindex persist
!
       

Enabling SNMP

By default, SNMP is disabled on Cisco vEdge devices. To enable it and provide support for SNMP Versions 1, 2, and 3:

vEdge(config)# snmp
vEdge(config-snmp)# no shutdown

Enabling SNMP allows the device to use MIBs, generate traps, and respond to requests from an SNMP walk application.

Configuring an SNMP View

To create an SNMP view, along with an OID, so that SNMP information is available to the SNMP server, configure an SNMP view and its corresponding OID subtree:

vEdge(config-snmp)#  view string
vEdge(config-snmp)#  oid oid-subtree

In the OID subtree, you can use the wildcard * (asterisk) in any position to match any value at that position.

The following example creates a view of the Internet portion of the SNMP MIB:

vEdge(config)# snmp view v2 oid 1.3.6.1

The following example creates a view of the private portion of the Cisco Catalyst SD-WAN MIB:

vEdge(config)# snmp view vEdge-private oid 1.3.6.1.4.1.41916

Configuring Access to an SNMP View

To require authentication privileges to access an SNMP view, configure SNMPv3. To do this, you configure authentication credentials for SNMPv3 users, and you configure groups of SNMP views and the authentication credentials required to access the views.

To configure authentication credentials for an SNMPv3 user, create a user and assign them an authentication level and a privacy level, depending on the authentication type you configure for the SNMP group (with the snmp group command, described below):

vEdge(config)# snmp user username
vEdge(config-user)# auth authentication
vEdge(config-user)# auth-password password
vEdge(config-user)# priv privacy
vEdge(config-user)# priv-password password

The username can be a string from 1 to 32 characters.

The authentication commands enable authentication privileges for the user. You can enter the password as a cleartext string or as an AES-encrypted key.

The privacy commands enable a privacy mechanism for the user. You can enter the password as a cleartext string or as an AES-encrypted key.

Then associate the SNMPv3 user with an SNMP group:

vEdge(config-user)# group group-name

group-name is the name of a group of views that you configure with the snmp group command.

To configure a group of views:

Device(config)# snmp group group-name authentication
Device(config-group)# view view-name

The group name can be a string from 1 to 32 characters.

The authentication to use for the group can be one of the following:

• auth-no-priv —Authenticate using the selected authentication algorithm. When you configure this authentication, users in this group must be configured with an authentication and an authentication password (with the snmp user auth and auth-password commands).

  From Cisco Catalyst SD-WAN Manager Release 20.12.1, the authentication method auth-no-priv is not supported.

• auth-priv —Authenticate using the selected authentication algorithm. When you configure this authentication, users in this group must be configured with an authentication and an authentication password (with the snmp user auth and auth-password commands) and a privacy and privacy password (with the snmp user priv and priv-password commands).

• no-auth-no-priv —Authenticate based on a username. When you configure this authentication, you do not need to configure authentication or privacy credentials.

Note	Use two separate transactions to move an SNMP user to a new group and to delete the old group. Moving an SNMP user to a new group and deleting the old group in the same transaction is not supported.

The view name is the name of an SNMP view that you configure with the snmp view command.

Configuring Contact Parameters

For each Cisco vEdge device, you can configure its SNMP node name, physical location, and contact information for the person or entity responsible for the device:

vEdge(config)#  snmp
vEdge(config-snmp)#  name string
vEdge(config-snmp)#  location string
vEdge(config-snmp)#  contact string

If any of the strings include spaces, enclose the entire string in quotation marks (" ").

Configuring an SNMP Community

The SNMP community string defines the relationship between an SNMP server system and the client systems. This string acts like a password to control the clients' access to the server. To configure a community string, use the community command:

vEdge(config-snmp)#  community name
vEdge(config-community-name)# authorization read-only
vEdge(config-community-name)# view string

The community name can be 1 through 32 characters long. It can include angle brackets (< and >). If the name includes spaces, enclose the entire name in quotation marks (" ").

Use the view command to specify the portion of the MIB tree to view. string is the name of a view record configured with the snmp view command, as described below.

The Cisco Catalyst SD-WAN software supports the standard interfaces, MIB, IF-MIB, and the system MIB (SNMPv2-MIB), which are automatically loaded onto the Cisco vEdge device when you install the Cisco Catalyst SD-WAN software. For a list of enterprise MIBs, see Supported SNMP MIBs. The MIBs supported by the Cisco Catalyst SD-WAN software do not allow write operations, so you can configure only read-only authorization (which is the default authorization).

Configuring View Records

To configure a portion of an SNMP MIB to view, use the view command:

vEdge(config-snmp)#  view string
vEdge(config-view)# oid oid-subtree [exclude]

For example, to view the internet portion of the SNMP MIB, configure the OID 1.3.6.1:

vEdge(config-snmp)# view v2 oid 1.3.6.1

To view the private portion of the Cisco Catalyst SD-WAN MIB, configure the OID 1.3.6.1.4.1.41916.

SNMP Configuration Commands

Use the following commands to configure SNMP:

snmp
  community name    
    authorization (read-only | read-write)
    view string  
  contact string
  group group-name authentication
    view string
  location string  
  name string
  [no] shutdown
  trap
    group group-name
      trap-type
        level severity
    target vpn vpn-id ip-address udp-port
      community-name community-name
      group-name group-name
      source-interface interface-name
  user username
    auth authentication
    auth-password password
    group group-name
    priv privacy
    priv-password password
  

SNMP Monitoring Commands

Use the following command to monitor SNMP:

Use the show running-config snmp command to monitor SNMP. The command output shows the active configuration that is running on the Cisco vEdge device.

The SNMP traps are asynchronous notifications that a Cisco device sends to an SNMP management server. Traps notify the management server of events, whether normal or significant, that occur on the device. By default, SNMP traps aren’t sent to an SNMP server. Note that for SNMPv3, the PDU type for notifications is either SNMPv2c inform (InformRequest-PDU) or trap (Trapv2-PDU).

To configure SNMP traps, define the traps and configure the SNMP server that receives the traps.

Note	The trap group UI option isn’t supported from Cisco SD-WAN Release 20.1.1 and later.

To configure groups of traps to be collected on Cisco vEdge devices, use the trap group command:

Note	You don't need to configure groups of traps on Cisco IOS XE Catalyst SD-WAN devices.

vEdge(config-snmp)#  trap group group-name
vEdge(config-group)# trap-type level severity

A single trap group can contain multiple trap types. In the configuration, specify one trap type per line, and each trap type can have one, two, or three severity levels. See the following configuration example for an illustration of the configuration process.

To configure the SNMP server to receive the traps, use the trap target command on Cisco vEdge devices:

Note	You don't need to configure the SNMP server to receive the traps on Cisco IOS XE Catalyst SD-WAN devices.

vedge(config-snmp)#  trap target vpn  vpn-id ipv4-address udp-port
vedge(config-target)# group-name name
vedge(config-target)# community-name community-name
vedge(config-target)# source-interface interface-name

For each SNMP server, specify the identifier of VPN where the server is located, the server's IPv4 address, and the UDP port on the server to connect to. When configuring the trap server's address, you must use an IPv4 address. You can’t use an IPv6 address.

In the group-name command, associate a previously configured trap group with the server. The traps in that group are sent to the SNMP server.

In the community-name command, associate a previously configure SNMP community with the SNMP server.

In the source-interface command, configure the interface to use to send traps to the SNMP server that is receiving the trap information. This interface cannot be a subinterface.

In the following configuration example, all traps are sent to one SNMP server and only critical traps to another SNMP server. Two SNMP trap groups and the two target SNMP servers are configured:

vEdge# config
Entering configuration mode terminal
vEdge(config)# snmp
vEdge(config-snmp)# view community-view 
vEdge(config-view-community-view)# exit
vEdge(config-snmp)# community public
vEdge(config-community-public)# authorization read-only 
vEdge(config-community-public)# view community-view 
vEdge(config-community-public)# exit
vEdge(config-snmp)# trap group all-traps
vEdge(config-group-all-traps)# all level critical major minor
vEdge(config-group-all)# exit
vEdge(config-group-all-traps)# exit
vEdge(config-snmp)# trap group critical-traps
vEdge(config-group-critical-traps)# control level critical
vEdge(config-group-control)# exit
vEdge(config-group-critical-traps)# exit
vEdge(config-snmp)# trap target vpn 0 10.0.0.1 162
vEdge(config-target-0/10.0.0.1/162)# group-name all-traps 
vEdge(config-target-0/10.0.0.1/162)# community-name public
vEdge(config-target-0/10.0.0.1/162)# exit
vEdge(config-snmp)# trap target vpn 0 10.0.0.2 162
vEdge(config-target-0/10.0.0.2/162)# group-name critical-traps 
vEdge(config-target-0/10.0.0.2/162)# community-name public
vEdge(config-target-0/10.0.0.2/162)# exit
vEdge(config-snmp)# show full-configuration 
snmp
 view community-view
 !
 community public
  view          community-view
  authorization read-only
 !
 group groupAuthPriv auth-priv
  view v2
 !
 user u1
  auth          sha
  auth-password $8$UZwdx9eu49iMElcJJINm0f202N8/+RGJvxO+e9h0Uzo=
  priv          aes-cfb-128
  priv-password $8$eB/I+VXrAWDw/yWmEqLMsgTcs0omxcHldkVN2ndU9QI=
  group         groupAuthPriv
 !
 trap target vpn 0 10.0.0.1 162
  group-name     all-traps
  community-name public
 !
 trap target vpn 0 10.0.0.2 162
  group-name     critical-traps
  community-name public
 !
 trap group all-traps
  all
   level critical major minor
  !
 !
 trap group critical-traps
  bfd
   level critical
  !
  control
   level critical
  !
  hardware
   level critical
  !
  omp
   level critical
  !
 !
!
vEdge(config-snmp)#

Cisco IOS XE Catalyst SD-WAN Devices

You can download the MIBs supported on Cisco IOS XE Catalyst SD-WAN devices from https://github.com/cisco/cisco-mibs

Note

Starting from Cisco IOS XE Catalyst SD-WAN Release 17.8.1a, OMP MIB tables and scalar objects are supported in CISCO-SDWAN-OMP-MIB.my. In Cisco IOS XE Release 17.6.1a, only ciscoSdwanOmpOmpNumberOfVsmartsChange, ciscoSdwanOmpOmpStateChange, ciscoSdwanOmpOmpPeerStateChange, and ciscoSdwanOmpOmpPolicy OMP traps are supported and no OMP MIB tables and scalar objects are supported in CISCO-SDWAN-OMP-MIB.my.

Note

For the CISCO-SDWAN-POLICY-MIB.my MIB, the Object Identifier (OID) value cannot exceed 128 sub-identifiers, as defined in RFC 2578. When the OID limit exceeds 128 sub-identifiers, we recommend you to use the Real-Time Monitoring - Policy Netconf or REST API on Cisco IOS XE Catalyst SD-WAN devices as alternative APIs for monitoring and troubleshooting.

Note	Starting from Cisco IOS XE Release 17.6.3, CISCO-SDWAN-APP-ROUTE-MIB includes appRouteStatisticsAppProbeClassTable and appRouteStatisticsAppProbeClassIntervalTable OIDs to support Mean Jitter, Latency and Packet Drop data requests from SNMP.

Note	Starting from Cisco IOS XE Catalyst SD-WAN Release 17.9.2a, if a SNMP MIB table includes a large number of table entries, then we recommend that you use snmp-server subagent fetch count100 command. By default, the count value is 50.

Cisco vEdge Devices

For supported Cisco vEdge MIBs, see https://github.com/cisco/cisco-mibs/tree/main/viptela-mibs.

For information about downloading these MIB files, see the Release Notes for your software release.