Downloads |
Table Of Contents
DistributedDirector MIB Support
Related Features and Technologies
Supported Standards, MIBs, and RFCs
Enabling DistributedDirector SNMP Notifications
Specifying the Recipient of an SNMP Notification
Verifying DistributedDirector Notification Information
Enabling DistributedDirector SNMP Notifications Example
Specifying the Recipient of an SNMP Notification Example
snmp-server enable traps director
DistributedDirector MIB Support
Feature History
This document describes DistributedDirector MIB support and the enhancements and modifications made to the Cisco IOS Simple Network Management Protocol (SNMP) infrastructure in order to support DistributedDirector in Cisco IOS Release 12.2(8)T. It includes the following sections:
•
Supported Standards, MIBs, and RFCs
Feature Overview
Network management takes place between two major types of systems: those in control, called managing systems, and those observed and controlled, called managed systems. The most common type of managing system is called a network management system (NMS). Managed systems can include hosts, servers, or network components such as routers or intelligent repeaters.
To promote interoperability, cooperating systems must adhere to a common framework and a common language, called a protocol. In the Internet network management framework, that protocol is the SNMP.
In a managed device, specialized low-impact software modules, called agents, access information about the device and make it available to the NMS. Managed devices maintain values for a number of variables and report those, as required, to the NMS. For example, an agent might report such data as the number of bytes and packets passing in and out of the device, or the number of broadcast messages sent and received. In the Internet network management framework, each variable is referred to as a managed object, which is anything that an agent can access and report back to the NMS.
All managed objects are contained in the Management Information Base (MIB), which is a database of the managed objects. The managed objects, or variables, can be set or read to provide information on network devices and interfaces. An NMS can control a managed device by sending a message to an agent of that managed device requiring the device to change the value of one or more of its variables.
The Cisco DistributedDirector MIB provides MIB support for DistributedDirector. This MIB contains DistributedDirector statistics, configurations, and status.
The DistributedDirector MIB contains five groups of object type definitions:
•
•
•
•
•
The DistributedDirector MIB defines the following tables:
•
•
•
•
•
•
•
•
The DistributedDirector MIB defines the following notifications:
•
•
•
The ciscoDistDirEventServerUp and ciscoDistDirEventServerDown notifications can be enabled or disabled using the Cisco IOS snmp-server enable traps director and snmp-server host commands.
The snmp-server host command is used in conjunction with the snmp-server enable traps director command. Use the snmp-server enable traps director command to specify which DistributedDirector SNMP notifications are sent globally. For a host to receive most notifications, at least one snmp-server enable traps director command and the snmp-server host command for that host must be enabled.
Benefits
The DistributedDirector MIB provides network management functionality to DistributedDirector.
Restrictions
The DistributedDirector MIB implementation for Cisco IOS Release 12.2(8)T supports read-only capability to the objects defined in the MIB.
Related Features and Technologies
•
•
•
Related Documents
•
•
•
•
Supported Platforms
•
•
•
•
•
Determining Platform Support Through Cisco Feature Navigator
Cisco IOS software is packaged in feature sets that support specific platforms. To get updated information regarding platform support for this feature, access Cisco Feature Navigator. Cisco Feature Navigator dynamically updates the list of supported platforms as new platform support is added for the feature.
Cisco Feature Navigator is a web-based tool that enables you to quickly determine which Cisco IOS software images support a specific set of features and which features are supported in a specific Cisco IOS image. You can search by feature or release. Under the release section, you can compare releases side by side to display both the features unique to each software release and the features in common.
Cisco Feature Navigator is updated regularly when major Cisco IOS software releases and technology releases occur. For the most current information, go to the Cisco Feature Navigator home page at the following URL:
Supported Standards, MIBs, and RFCs
Standards
No new or modified standards are supported by this feature.
MIBs
•
•
To obtain lists of supported MIBs by platform and Cisco IOS release, and to download MIB modules, go to the Cisco MIB website on Cisco.com at the following URL:
http://www.cisco.com/public/sw-center/netmgmt/cmtk/mibs.shtml
RFCs
•
Prerequisites
DistributedDirector must be running on the router.
Configuration Tasks
See the following sections for configuration tasks for the DistributedDirector MIB support feature. Each task in the list is identified as either required or optional.
•
•
Enabling DistributedDirector SNMP Notifications
To enable DistributedDirector SNMP notifications, use the following command in global configuration mode:
Router(config)# snmp-server enable traps director
Enables DistributedDirector SNMP notifications.
To disable DistributedDirector SNMP notifications, use the following command in global configuration mode:
Router(config)# no snmp-server enable traps director
Disables DistributedDirector SNMP notifications.
Specifying the Recipient of an SNMP Notification
To specify the recipient of a DistributedDirector SNMP notification, use the following command in global configuration mode:
To remove the specified recipient, use the following command in global configuration mode:
Router(config)# no snmp-server host host-address director
Removes the recipient of a DistributedDirector SNMP notification.
Verifying DistributedDirector Notification Information
Enter the show running-config command to verify that DistributedDirector SNMP notification information is configured. Both server up and server down information is included, unless you specify one or the other.
Router# show running-configip host myhost 172.2.2.10 172.2.2.20 172.2.2.30...snmp-server enable traps director server-up server-downConfiguration Examples
This section provides the following configuration examples:
•
•
Enabling DistributedDirector SNMP Notifications Example
In the following example, both ciscoDistDirEventServerUp and ciscoDistDirEventServerDown notifications are enabled:
Router(config)# snmp-server enable traps directorRouter# show running-configip host myhost 172.2.2.10 172.2.2.20 172.2.2.30...snmp-server enable traps director server-up server-downSpecifying the Recipient of an SNMP Notification Example
In the following example, the ciscoDistDirEventServerUp and ciscoDistDirEventServerDown notifications are to be sent to the host 10.0.0.1 using the community string defined as "public":
Router(config)# snmp-server host 10.0.0.1 public directorRouter# show snmpChassis:87684900 SNMP packets input0 Bad SNMP version errors0 Unknown community name0 Illegal operation for community name supplied0 Encoding errors0 Number of requested variables0 Number of altered variables0 Get-request PDUs0 Get-next PDUs0 Set-request PDUs0 SNMP packets output0 Too big errors (Maximum packet size 1500)0 No such name errors0 Bad values errors0 General errors0 Response PDUs0 Trap PDUsSNMP logging:enabledLogging to 10.0.0.1.162, 0/10, 0 sent, 0 dropped.Command Reference
This section documents modified commands. All other commands used with this feature are documented in the Cisco IOS Release 12.2 command reference publications.
•
snmp-server enable traps director
To enable DistributedDirector Simple Network Management Protocol (SNMP) notifications, use the snmp-server enable traps director command in global configuration mode. To disable DistributedDirector SNMP notifications, use the no form of this command.
snmp-server enable traps director [server-up | server-down]
no snmp-server enable traps director [server-up | server-down]
Syntax Description
Defaults
SNMP notifications are disabled by default.
Command Modes
Global configuration
Command History
Usage Guidelines
SNMP notifications can be sent as traps or inform requests. This command enables both traps and inform requests.
This command controls (enables or disables) DistributedDirector status notifications for systems. If none of the optional keywords is specified, all available environmental notifications are enabled.
Examples
In the following example, both ciscoDistDirEventServerUp and ciscoDistDirEventServerDown notifications are enabled:
Router(config)# snmp-server enable traps directorRouter# show running-configip host myhost 172.2.2.10 172.2.2.20 172.2.2.30...ip director host myhostip dns primary myhost soa myhost myhost@comip director host myhost priority boomerang 1no ip director drp synchronizedsnmp-server enable traps director server-up server-downRelated Commands
snmp-server host
To specify the recipient of a Simple Network Management Protocol (SNMP) notification, use the snmp-server host command in global configuration mode. To remove the specified recipient, use the no form of this command.
snmp-server host host-address [traps | informs] [version {1 | 2c | 3 [auth | noauth | priv]}] community-string [udp-port port] [notification-type]
no snmp-server host host-address [traps | informs]
Syntax Description
Defaults
This command is disabled by default.
Command Modes
Global configuration
Command History
Usage Guidelines
SNMP notifications can be sent as traps or inform requests. Traps are unreliable because the receiver does not send acknowledgments when it receives traps. The sender cannot determine if the traps were received. However, an SNMP entity that receives an inform request acknowledges the message with an SNMP response protocol data unit. If the sender never receives the response, the inform request can be sent again. Thus, informs are more likely to reach their intended destinations.
However, informs consume resources in the agent and in the network. Unlike a trap, which is discarded as soon as it is sent, an inform request must be held in memory until a response is received or the request times out. Also, traps are sent only once, but an inform may be retried several times. The retries increase traffic and contribute to higher overhead on the network.
If you do not enter an snmp-server host command, no notifications are sent. In order to configure the router to send SNMP notifications, you must enter at least one snmp-server host command. If you enter the command with no keywords, all trap types are enabled for the host.
In order to enable multiple hosts, you must issue a separate snmp-server host command for each host. You can specify multiple notification types in the command for each host.
When multiple snmp-server host commands are given for the same host and kind of notification (trap or inform), each succeeding command overwrites the preceding command. Only the last-received snmp-server host command will be in effect. For example, if you enter an snmp-server host informs command for a host and then enter another snmp-server host informs command for the same host, the second command will replace the first.
The snmp-server host command is used in conjunction with the snmp-server enable traps director command. Use the snmp-server enable traps director command to specify which DistributedDirector SNMP notifications are sent globally. For a host to receive DistributedDirector notifications, the snmp-server enable traps director command and the snmp-server host command for that host must be enabled.
If no version keyword is present, the default is version 1. The no snmp-server host command with no keywords will disable traps, but not informs, to the host. In order to disable informs, use the no snmp-server host informs command.
Note
Examples
If you want to configure a unique SNMP community string for traps, but you want to prevent access to SNMP polling with this string, the configuration should include an access list. In the following example, the community string is defined as "comaccess", and the access list is numbered 10:
Router(config)# snmp-server community comaccess ro 10Router(config)# snmp-server host 172.20.2.160 comaccessRouter(config)# access-list 10 deny any!Router(config)# snmp-server community comaccess RO 10Router(config)# snmp-server enable traps director server-up server-downRouter(config)# snmp-server host 172.20.2.160 comaccessRouter(config)# snmp-server host 10.10.10.11 public directorIn the following example, all available SNMP traps are enabled to be sent to the host specified by the name "myhost.cisco.com". The community string is defined as "comaccess".
Router(config)# snmp-server enable trapsRouter(config)# snmp-server host myhost.cisco.com comaccess snmpIn the following example, DistributedDirector MIB traps are enabled to be sent to the host "nms.cisco.com" using the community string defined as "public":
Router(config)# snmp-server enable traps directorRouter(config)# snmp-server host nms.cisco.com public directorRelated Commands
