-
Cisco IOS SNMP Support Command Reference
-
action (event) through rising (test threshold)
-
sample (event trigger) through snmp mib event sample
-
snmp mib event trigger owner through snmp-server enable informs
-
snmp-server enable traps through snmp-server enable traps ospf cisco-specific retransmit
-
snmp-server enable traps ospf cisco-specific state-change through snmp-server enable traps voice poor-qov
-
snmp-server engineID local through snmp trap link-status
-
startup (test boolean) through write mib-data
-
Index
-
Feedback
snmp mib event trigger owner through snmp-server enable informs
- snmp mib event trigger owner
- snmp mib expression delta
- snmp mib expression owner
- snmp mib flash cache
- snmp mib flowmon alarmhistorysize
- snmp mib notification-log default
- snmp mib notification-log default disable
- snmp mib notification-log globalageout
- snmp mib notification-log globalsize
- snmp mib persist
- snmp mib target list
- snmp trap link-status
- snmp set
- snmp-server cache
- snmp-server chassis-id
- snmp-server community
- snmp-server contact
- snmp-server context
- snmp-server drop vrf-traffic
- snmp-server enable informs
snmp mib event trigger owner
To specify an event trigger owner while configuring management event trigger information, use the snmp mib event trigger owner command in global configuration mode. To disable event trigger configuration and set the default parameters, use the no form of this command.
snmp mib event trigger owner trigger-owner name trigger-name
no snmp mib event trigger owner trigger-owner name trigger-name
Usage Guidelines
The snmp mib event trigger owner command enables event trigger configuration mode to configure conditions to trigger events. While configuring a trigger, you can associate each trigger to an event and configure the objects to be monitored.
Examples
The following example shows how to specify a trigger owner:
Router(config)# snmp mib event trigger owner owner1 name trigger1 Router(config-event-trigger)# endRelated Commands
Command
Description
description
Provides a description of the function and use of a trigger.
enable
Enables an event.
frequency
Specifies an interval between trigger samples.
object id
Specifies the object identifier of an object.
object list owner
Specifies the list of objects that can be added to notifications according to trigger type.
snmp mib expression delta
To specify a delta interval for object sampling, use the snmp mib expression delta command in global configuration mode. To disable the specified interval, use the no form of this command.
snmp mib expression delta { minimum { delta-value | seconds } | wildcard maximum wildcard-instance }
no snmp mib expression delta { minimum | wildcard maximum }
Syntax Description
minimum
Specifies the minimum value for object sampling.
delta-value
The delta value to use during object sampling.
seconds
Minimum number of seconds between delta samples. The default is 1.
wildcard
Specifies the number of instances that can be wildcarded during object sampling.
maximum
Specifies the maximum value for object.
wildcard-instance
The maximum number of dynamic instance entries. The default is 0.
Command Default
The default value for minimum delta interval is 1 second.
The default wildcard maximum value is 0.
Usage Guidelines
Applications may use larger values for minimum delta interval to lessen the impact of constantly computing delta. The snmp mib expression delta minimum command enforces a lower overhead for all expressions created after it is set.
For every instance of a delta object, one dynamic instance entry is required to restrict the instance value from the previous sample. The snmp mib expression delta wildcard maximum command limits the maximum number of dynamic instance entries that the system supports for wildcarded delta objects in expressions. For a given delta expression, the number of dynamic instances is the number of delta value (that meet all criteria) multiplied by the number of delta values in the expression.
A value of 0 indicates no preset limit. There is a dynamic limit based on system operation and resources. However, changing this value will not eliminate the existing delta wildcard instance objects, but will prevent the creation of more such objects.
snmp mib expression owner
To specify the owner of an expression, use the snmp mib expression owner command in global configuration mode. To disable the expression configuration, use the no form of this command.
snmp mib expression owner expr-owner name expr-name
no snmp mib expression owner expr-owner name expr-name
Usage Guidelines
The snmp mib expression owner command enables expression configuration mode and configures expression information such as expression owner and name. You can configure expression properties by using commands such as expression, delta interval, and expression.
Examples
The following example shows how to specify an expression owner:
Router(config)# snmp mib expression owner owner1 name expression1 Router(config-expression)# endRelated Commands
Command
Description
delta interval
Specifies an interval for the delta sampling of objects used while evaluating an expression.
description (event)
Describes the function and use of an event.
enable (event)
Enables an event or event trigger.
expression
Specifies an expression for evaluation.
object
Specifies the objects to be used while evaluating an expression.
prefix object
Enables the application to determine the object based on the instance indexing.
value type
Specifies the type of expression value.
snmp mib flash cache
To enable the data collection process for Flash MIB, use the snmp mib flash cachecommand in global configuration mode. To set the command to its default interval, use the no form of this command.
snmp mib flowmon alarmhistorysize
To set the maximum number of entries maintained by the flow monitor alarm history log, use the snmp mib flowmon alarmhistorysizecommand in global configuration mode. To remove the setting for the maximum number of alarm history log entries, use the no form of this command.
snmp mib notification-log default
To create an unnamed Simple Network Management Protocol (SNMP) notification log, use the snmp mib notification-log default command in global configuration mode. To delete the log, use the no form of this command.
snmp mib notification-log default [ size number ]
no snmp mib notification-log default [ size number ]
Usage Guidelines
This command creates an unnamed default SNMP notification log. The default log has a zero length string as its name (appears in the output of the show snmp mib notification-log command asLog Name””).
Creation and removal of the default log can be performed using only the command-line interface (CLI). Creation of named logs using the CLI or SNMP tools (SET operations) is not currently supported. No filters (varbinds) can be associated with the default log.
SNMP notification logging is enabled by default, but logging does not start until either a specific log is created and defined using thiscommand or a named log is created using a SNMP Set operation from a network management station (NMS).
The no form of this command deletes the default notification log and removes the notifications that were a part of this log from the Notification Log MIB database (recursively deletes the log and all its entries).
Examples
The following example shows how to create and activate a default SNMP notification log with a size of 600:
Router(config)# snmp mib notification-log default size 600Related Commands
Command
Description
show snmp mib notification-log
Displays information about the state of local SNMP notification logging.
snmp mib notification-log globalageout
Sets the maximum age for a notification.
snmp mib notification-log globalsize
Sets the maximum number of notifications allowed in all logs.
snmp mib notification-log default disable
To disable Simple Network Management Protocol (SNMP) notification logging to the “default” log without deleting existing notification log entries, use the snmp mib notification-log default disable command in global configuration mode. To reenable logging, use the no form of this command.
Usage Guidelines
The “default” notification log is the null-named notification log.
This command disables SNMP notification logging. However, this command does not delete existing logs. To clear the existing “default” log, use the no snmp mib notification-log default command.
SNMP notification logging is enabled by default, but logging does not start until a specific log is created and defined using the snmp mib notification-log defaultcommand, or a named log is created using an SNMP Set operation from a network management station (NMS).
Examples
In the following example, SNMP notification logging is disabled, but existing logs are not deleted:
Router(config)# snmp mib notification-log default ? disable disable logging size size of the default log <cr> Router(config)# snmp mib notification-log default disable Router(config)#Related Commands
Command
Description
show snmp mib notification-log
Displays information about the state of local SNMP notification logging.
snmp mib notification-log default
Creates an SNMP notification log.
snmp mib notification-log globalageout
Sets the maximum age for a notification.
snmp mib notification-log globalsize
Sets the maximum number of notifications allowed in all logs.
snmp mib notification-log globalageout
To set the maximum amount of time Simple Network Management Protocol (SNMP) notification log entries remain in the system memory, use the snmp mib notification-log globalageoutcommand in global configuration mode. To restore the default value, use the no form of this command.
Usage Guidelines
The ageout value specifies the maximum time a notification log can remain in the Notification Log MIB database. This value applies to all logs (default log and named logs) in the Notification Log MIB database.
The no form of the command restores the default value.
snmp mib notification-log globalsize
To set the maximum number of entries that can be stored in all Simple Network Management Protocol (SNMP) notification Logs, use the snmp mib notification-log globalsizecommand in global configuration mode. To restore the default value, use the no form of this command.
Usage Guidelines
The size of the SNMP notification log database can be set globally (for all SNMP notification logs combined) or for each named log. The snmp mib notification-log globalsize command sets the maximum number of entries for all notification logs on the local system; in other words, this setting affects the whole Notification Log MIB database. This value is saved to the nlmConfigGlobalEntryLimit object in the SNMP Notification Log MIB.
The default global log size is 500 log entries. The default log size for each individual log (such as the “default log”) is 500 log entries. The maximum size for all logs combined is 15,000 log entries.
snmp mib persist
To enable MIB persistence, use the snmp mib persistcommand in global configuration mode. To disable MIB persistence, use the no form of this command.
snmp mib persist [ event | expression | circuit | cbqos | v3mibs ]
no snmp mib persist [ event | expression | circuit | cbqos | v3mibs ]
Command History
T Release
Modification
12.2(2)T
This command was introduced.
12.2(4)T3
The event and expression keywords were added.
12.4(4)T
The cbqos keyword was added.
12.4(20)T
The event and expression keywords were removed.
OS Release
Modification
12.0(32)S
This command was integrated into Cisco IOS Release 12.0(32)S. The event, expression, and cbqos keywords were added.
SB Release
Modification
12.2(31)SB
This command was integrated into Cisco IOS Release 12.2(31)SB. The v3mibs and cbqos keywords were added.
SX Release
Modification
12.2(33)SXI
This command was integrated into Cisco IOS Release 12.2(33)SXI. The cbqos keyword was added.
SR Release
Modification
12.2(33)SRB
This command was integrated into Cisco IOS Release 12.2(33)SRB. The cbqos keyword was added.
12.2(33)SRC
The v3mibs keyword was added.
Usage Guidelines
After entering the snmp mib persist command, you must enter the write mib-data command to save MIB persistence configuration data to NVRAM.
The Circuit Interface MIB provides a MIB object (cciDescr) that can be used to identify individual circuit-based interfaces for Simple Network Management Protocol (SNMP) monitoring. Circuit interface identification persistence maintains the user-defined name of the circuit across reboots by retaining the value of the cciDescr object in the Circuit Interface MIB (CISCO-CIRCUIT-INTERFACE-MIB). A consistent value for specific circuits is useful for network management applications that use SNMP. Circuit interface identification persistence is enabled using the snmp mib persist circuit global configuration command. This command is disabled by default because it uses NVRAM memory.
To enable MIB persistence for all available MIB types, use the snmp mib persistcommand without keywords.
Examples
The following example shows how to enable Event MIB persistence:
Router(config)# snmp mib persist cbqos Router(config)# end Router# write mib-dataRelated Commands
Command
Description
snmp ifindex persist
Enables SNMP interface index values that remain constant across reboots only on a specific interface.
snmp-server ifindex persist
Globally enables SNMP interface index values that remain constant across reboots.
write mib-data
Saves MIB persistence configuration data to NVRAM.
snmp mib target list
To create a list of target virtual private network (VPN) routing and forwarding (VRF) instance and hosts to associate with a Simple Network Management Protocol (SNMP) community, use the snmp mib target list command in global configuration mode. To delete the list of VRF instances and hosts or to delete a particular VRF or host from the list, use the no form of this command.
snmp mib target list vpn-list-name { vrf vrf-name | host ip-address }
no snmp mib target list vpn-list-name { vrf vrf-name | host ip-address }
Command History
Release
Modification
12.0(23)S
This command was introduced.
12.3(2)T
This command was integrated into Cisco IOS Release 12.3(2)T.
12.2(25)S
This command was integrated into Cisco IOS Release 12.2(25)S.
12.2(33)SRA
This command was integrated into Cisco IOS Release 12.2(33)SRA.
12.2(31)SB2
This command was integrated into Cisco IOS Release 12.2(31) SB2.
12.2(33)SXH
This command was integrated into Cisco IOS Release 12.2(33)SXH.
12.2SX
This command is supported in the Cisco IOS Release 12.2SX train. Support in a specific 12.2SX release of this train depends on your feature set, platform, and platform hardware.
12.2(33)SB
This command was integrated into Cisco IOS Release 12.2(33)SB.
Usage Guidelines
Use this command when using SNMPv1 or SNMPv2 in a VPN environment to configure a list of VRFs or hosts for source address validation. Configuring the target list ensures that the community is valid only if the incoming packet is received from a VRF or host on the target list.
- Currently, two SNMP variables in the IP-FORWARD-MIB can be polled: 1.3.6.1.2.1.4.24.3 (ipCidrRouteNumber - Scalar) and 1.3.6.1.2.1.4.24.4.1 (ipCidrRouteEntry - Table).
NoteIt is recommended that you use SNMPv3 with the authNoPriv or higher level of security when using SNMP in a VPN environment.
snmp trap link-status
To enable Simple Network Management Protocol (SNMP) link trap generation, use the snmp trap link-status command in either interface configuration mode or service instance configuration mode. To disable SNMP link trap generation, use the no form of this command.
Command History
Release
Modification
10.0
This command was introduced.
12.2(30)S
This command was modified. The permit duplicates keyword pair was added.
12.3(8)T
This command was integrated into Cisco IOS Release 12.3(8)T.
12.2(33)SRA
This command was integrated into Cisco IOS Release 12.2(33)SRA.
12.2SX
This command is supported in the Cisco IOS Release 12.2SX train. Support in a specific 12.2SX release of this train depends on your feature set, platform, and platform hardware.
12.2(33)SB
This command’s behavior was modified on the Cisco 10000 series router for the PRE3 and PRE4 as described in the Usage Guidelines.
12.2(33)SRD1
Support for this command was extended to service instance configuration mode.
12.2(33)SRE6
This command was modified. This command must be enabled on each subinterface from this release onwards.
15.1(3)S3
This command was integrated into Cisco IOS Release 15.1(3)S3.
Usage Guidelines
By default, SNMP link traps are sent when an interface goes up or down. For interfaces such as ISDN interfaces, expected to go up and down during normal usage, the output generated by these traps may not be useful. The no form of this command disables these traps.
The permit and duplicates keywords are used together and cannot be used individually. Use the permit duplicates keyword pair when an interface is not generating SNMP linkup traps, linkdown traps, or both. When the snmp trap link-status permit duplicates command is configured, more than one trap may be sent for the same linkup or linkdown transition.
The permit duplicates keyword pair does not guarantee that SNMP link traps will be generated nor should configuring these keywords be required to receive traps.
By default, in service instance configuration mode, SNMP link traps are not sent. Also, the permit duplicates keyword pair is not available in service instance configuration mode.
The snmp trap link-status command must be used in conjunction with the snmp-server enable traps atm subif command in order to enable SNMP trap notifications on ATM subinterfaces. The snmp-server enable traps atm subif command must be configured in global configuration mode, and then the snmp trap link-status command must be configured on each ATM subinterface for which you want to enable SNMP trap notifications.
Cisco 10000 Series Router
In Cisco IOS Release 12.2(33)SB, the virtual-template snmp command has a new default configuration. Instead of being enabled by default, no virtual-template snmp is the default configuration. This setting enhances scaling and prevents large numbers of entries in the MIB ifTable, thereby avoiding CPU Hog messages as SNMP uses the interfaces MIB and other related MIBs.
If you configure the no virtual-template snmp command, the device no longer accepts the snmp trap link-status command under a virtual-template interface. Instead, the device displays a configuration error message such as the following:
Device(config)# interface virtual-template 1 Device(config-if)# snmp trap link-status %Unable set link-status enable/disable for interfaceIf your configuration already has the snmp trap link-status command configured under a virtual-template interface and you upgrade to Cisco IOS Release 12.2(33)SB, the configuration error occurs when the device reloads even though the virtual template interface is already registered in the interfaces MIB.
Examples
The following example shows how to disable SNMP link traps related to the ISDN BRI interface 0:
Device(config)# interface bri 0 Device(config-if)# no snmp trap link-statusThe following example shows how to enable SNMP link traps for service instance 50 on Ethernet interface 0/1:
Device(config)# interface ethernet 0/1 Device(config-if)# service instance 50 ethernet Device(config-if-srv)# snmp trap link-status Device(config-if-srv)# endsnmp set
To set or modify the value of an object variable during the Simple Network Management Protocol (SNMP) set operation, use the snmp setcommand in privileged EXEC mode.
snmp set { v1 | v2c | v3 } ip-address [ vrf vrf-name ] community-string [ retry number ] [ timeout seconds ] oid oid-value oid-type oid-type-value
Syntax Description
Usage Guidelines
The SNMP set operation modifies the individual variables in the SNMP entity.
The community string for a set operation can be set to either of the following types:
- ro--Sets the read-only access to the SNMP entity. The default value for this community string is public.
- rw--Sets read-write access to the SNMP entity. The default value for this community string is private.
snmp-server cache
To enable the Simple Network Management Protocol (SNMP) cache and configure the SNMP cache expiry interval, use the snmp-server cache command in global configuration mode. To disable the cache for MIBs that are kept by the SNMP engine, use the no form of this command.
Command Default
By default, the SNMP cache is enabled. The default expiry interval value is 5 seconds .
Usage Guidelines
This command is used in distributed or modular environments. The SNMP engine cache maintains the cache for MIBs.
snmp-server chassis-id
To provide a message line identifying the Simple Network Management Protocol (SNMP) server serial number, use the snmp-server chassis-id command in global configuration mode. To restore the default value, if any, use the no form of this command.
Command Default
On hardware platforms where the serial number can be machine read, the default is the serial number. For example, a Cisco 7000 router has a default chassis-id value of its serial number.
Command History
Release
Modification
10.0
This command was introduced.
12.2(33)SRA
This command was integrated into Cisco IOS Release 12.2(33)SRA.
12.2SX
This command is supported in the Cisco IOS Release 12.2SX train. Support in a specific 12.2SX release of this train depends on your feature set, platform, and platform hardware.
Usage Guidelines
The Cisco MIB provides a chassis MIB variable that enables the SNMP manager to gather data on system card descriptions, chassis type, chassis hardware version, chassis ID string, software version of ROM monitor, software version of system image in ROM, bytes of processor RAM installed, bytes of NVRAM installed, bytes of NVRAM in use, current configuration register setting, and the value of the configuration register at the next reload. The following installed card information is provided: type of card, serial number, hardware version, software version, and chassis slot number.
The chassis ID message can be seen with the show snmp command.
snmp-server community
To set up the community access string to permit access to the Simple Network Management Protocol (SNMP), use the snmp-server community command in global configuration mode. To remove the specified community string, use the noform of this command.
snmp-server community string [ view view-name ] [ ro | rw ] [ ipv6 nacl ] [ access-list-number | extended-access-list-number | access-list-name ]
no snmp-server community string
Syntax Description
Command History
Release
Modification
10.0
This command was introduced.
12.0(14)ST
This command was integrated into Cisco IOS Release 12.0(14)ST.
12.0(17)S
This command was integrated into Cisco IOS Release 12.0(17)S.
12.2(14)S
This command was integrated into Cisco IOS Release 12.2(14)S.
12.3(2)T
The access list values were enhanced to support the expanded range of standard access list values and to support named standard access lists.
12.0(27)S
The ipv6 nacl keyword and argument pair was added to support assignment of IPv6 named access lists. This keyword and argument pair is not supported in Cisco IOS 12.2S releases.
12.3(14)T
The ipv6 nacl keyword and argument pair was integrated into Cisco IOS Release 12.3(14)T to support assignment of IPv6 named access lists. This keyword and argument pair is not supported in Cisco IOS 12.2S releases.
12.2(28)SB
This command was integrated into Cisco IOS Release 12.2(28)SB.
12.2(33)SRA
This command was integrated into Cisco IOS Release 12.2(33)SRA.
12.4(11)T
This command was integrated into Cisco IOS Release 12.4(11)T.
12.2(31)SB2
This command was integrated into Cisco IOS Release 12.2(31)SB2.
12.2(33)SXH
This command was integrated into Cisco IOS Release 12.2(33)SXH.
Cisco IOS XE Release 2.1
This command was introduced on Cisco ASR 1000 Aggregation Series Routers.
12.2(33)SB
This command was integrated into Cisco IOS Release 12.2(33)SB.
12.2(33)SRE
This command was modified. The automatic insertion of the snmp-server community command into the configuration, along with the community string specified in the snmp-server host command, is changed. The snmp-server community command has to be manually configured.
15.1(0)M
This command was modified. The automatic insertion of the snmp-server community command into the configuration, along with the community string specified in the snmp-server host command, is changed. The snmp-server community command has to be manually configured.
Usage Guidelines
The no snmp-server command disables all versions of SNMP (SNMPv1, SNMPv2C, SNMPv3).
The first snmp-server command that you enter enables all versions of SNMP.
To configure SNMP community strings for the MPLS LDP MIB, use the snmp-server community command on the host network management station (NMS).
NoteIn Cisco IOS Release 12.0(3) to 12.2(33)SRD, if a community string was not defined using the snmp-server community command prior to using the snmp-server host command, the default form of the snmp-server community command was automatically inserted into the configuration. The password (community string) used for this automatic configuration of the snmp-server community was same as specified in the snmp-server host command. However, in Cisco IOS Release 12.2(33)SRE and later releases, you have to manually configure the snmp-server community command.
The snmp-server community command can be used to specify only an IPv6 named access list, only an IPv4 access list, or both. For you to configure both IPv4 and IPv6 access lists, the IPv6 access list must appear first in the command statement.
NoteThe @ symbol is used as a delimiter between the community string and the context in which it is used. For example, specific VLAN information in BRIDGE-MIB may be polled using community@VLAN_ID (for example, public@100) where 100 is the VLAN number. Avoid using the @ symbol as part of the SNMP community string when configuring this command.
Examples
The following example shows how to set the read/write community string to newstring:
Router(config)# snmp-server community newstring rwThe following example shows how to allow read-only access for all objects to members of the standard named access list lmnop that specify the comaccess community string. No other SNMP managers have access to any objects.
Router(config)# snmp-server community comaccess ro lmnopThe following example shows how to assign the string comaccess to SNMP, allow read-only access, and specify that IP access list 4 can use the community string:
Router(config)# snmp-server community comaccess ro 4The following example shows how to assign the string manager to SNMP and allow read-write access to the objects in the restricted view:
Router(config)# snmp-server community manager view restricted rwThe following example shows how to remove the community comaccess:
Router(config)# no snmp-server community comaccessThe following example shows how to disable all versions of SNMP:
Router(config)# no snmp-serverThe following example shows how to configure an IPv6 access list named list1 and links an SNMP community string with this access list:
Router(config)# ipv6 access-list list1 Router(config-ipv6-acl)# permit ipv6 any any Router(config-ipv6-acl)# exit Router(config)# snmp-server community comaccess rw ipv6 list1Related Commands
Command
Description
access-list
Configures the access list mechanism for filtering frames by protocol type or vendor code.
show snmp community
Displays SNMP community access strings.
snmp-server enable traps
Enables the router to send SNMP notification messages to a designated network management workstation.
snmp-server host
Specifies the targeted recipient of an SNMP notification operation.
snmp-server view
Creates or updates a view entry.
snmp-server contact
To set the system contact (sysContact) string, use the snmp-server contact command in global configuration mode. To remove the system contact information, use the no form of this command.
Command History
Release
Modification
10.0
This command was introduced.
12.2(33)SRA
This command was integrated into Cisco IOS Release 12.2(33)SRA.
12.2SX
This command is supported in the Cisco IOS Release 12.2SX train. Support in a specific 12.2SX release of this train depends on your feature set, platform, and platform hardware.
snmp-server context
To create a Simple Network Management Protocol (SNMP) context, use the snmp-server context command in global configuration mode. To delete an SNMP context, use the no form of this command.
Command History
Release
Modification
12.0(23)S
This command was introduced.
12.3(2)T
This command was integrated into Cisco IOS Release 12.3(2)T.
12.2(25)S
This command was integrated into Cisco IOS Release 12.2(25)S.
12.2(33)SRA
This command was integrated into Cisco IOS Release 12.2(33)SRA.
12.2(31)SB2
This command was integrated into Cisco IOS Release 12.2(31)SB2.
12.2(33)SXH
This command was integrated into Cisco IOS Release 12.2(33)SXH.
12.2SX
This command is supported in the Cisco IOS Release 12.2SX train. Support in a specific 12.2SX release of this train depends on your feature set, platform, and platform hardware.
12.2(33)SB
This command was integrated into Cisco IOS Release 12.2(33)SB.
15.1(1)SY
This command was integrated into Cisco IOS Release 15.1(1)SY.
Usage Guidelines
When you use the no snmp-server context command, all SNMP instances in that context are deleted.
A route distinguisher (RD) is required when you configure an SNMP context. An RD creates routing and forwarding tables and specifies the default route distinguisher for a VPN. The RD is added to the beginning of a IPv4 prefix to make it globally unique. An RD is either ASN relative, which means it is composed of an autonomous system number and an arbitrary number, or it is IP address relative and composed of an IP address and an arbitrary number.
Examples
The following example shows how to create an SNMP context named contextA and associate it with a virtual private network (VPN) routing and forwarding (VRF) instance named CustomerA:
Router(config)# snmp-server context contextA Router(config)# ip vrf CustomerA Router(config-vrf)# rd 100:120 Router(config-vrf)# context contextAsnmp-server drop vrf-traffic
To configure a router to drop Simple Network Management Protocol (SNMP) packets coming from virtual routing and forwarding (VRF) interfaces, use the snmp-server drop vrf-traffic command in global configuration mode. To disable the configuration, use the no form of this command.
snmp-server enable informs
NoteEffective with Cisco IOS Release 12.2(33)SXI, the snmp-server enable informs command is not available in Cisco IOS software.
This command has no functionality. To enable the sending of Simple Network Management Protocol (SNMP) inform notifications, use one of the snmp-server enable trapsnotification-type commands in global configuration mode combined with the snmp-server hosthost-address informs command in global configuration mode.
