|
Table Of Contents
Prerequisites for Multicast VPN MIB
Restrictions for Multicast VPN MIB
Information About Multicast VPN MIB
MVPN Information Retrieval Using SNMP and the MVPN MIB
How to Configure Multicast VPN MIB
Configuring the Router to Send MVRF Trap Notifications
Configuration Examples for Multicast VPN MIB
Configuring the Router to Send MVRF Trap Notifications: Example
Feature Information for Multicast VPN MIB
Multicast VPN MIB
First Published: August 9, 2004Last Updated: August 21, 2007The Multicast VPN MIB feature introduces the capability for Simple Network Management Protocol (SNMP) monitoring of a Multicast VPN (MVPN) using the MVPN MIB (CISCO-MVPN-MIB).
Finding Feature Information in This Module
Your Cisco IOS software release may not support all of the features documented in this module. To reach links to specific feature documentation in this module and to see a list of the releases in which each feature is supported, use the "Feature Information for Multicast VPN MIB" section.
Finding Support Information for Platforms and Cisco IOS and Catalyst OS Software Images
Use Cisco Feature Navigator to find information about platform support and Cisco IOS and Catalyst OS software image support. To access Cisco Feature Navigator, go to http://www.cisco.com/go/cfn. An account on Cisco.com is not required.
Prerequisites for Multicast VPN MIB
•Before performing the tasks in this module, you must configure MVPN. For information, see the "Configuring Multicast-VPN" chapter in the Cisco IOS Multicast Configuration Guide.
•You must configure SNMP on the routers on which the MVPN MIB is to be used. See the "Configuring the Router to Send MVRF Trap Notifications" task for more information. For more information about configuring an SNMP server, see the "Configuring SNMP Support" chapter in the Cisco IOS Network Management Configuration Guide.
Restrictions for Multicast VPN MIB
•Currently only IPv4 is supported.
•For all MIB objects with "read-create" access privileges, currently only "read-only" access is supported.
Information About Multicast VPN MIB
To configure the Multicast VPN MIB feature, you should understand the following concepts:
•MVPN Information Retrieval Using SNMP and the MVPN MIB
Overview of the MVPN MIB
In an MVPN network, a Provider Edge (PE) router has a multicast routing table and a Protocol Independent Multicast (PIM) instance associated with every VPN routing and forwarding (VRF) table that is used to define the VPN membership of customer sites attached to the router. There is one global multicast routing table and a table per multicast VRF (MVRF) used to route multicast packets received from a Customer Edge (CE) router. A set of MVRFs form a multicast domain (MD) when they are connected to potential sources and receivers of multicast traffic. A distinct group address, also known as the Multicast Distribution Tree (MDT) group address, obtained from an administrative pool, is assigned to each multicast domain. MDT groups are used by Provider Edge (PE) routers to encapsulate and transport multicast traffic within an MD through multicast tunnel interfaces (MTIs).
Initially all multicast data is forwarded using preconfigured MDT default groups. When certain multicast streams exceed a configured bandwidth threshold on the PE router, the multicast data is moved to an MDT data group that is dynamically chosen from an available pool of multicast addresses.
Using the MVPN MIB, network administrators can access MVRF information from PE routers for VPN traffic across multiple CE sites in real time. SNMP operations can be performed to monitor the MVRFs on the PE routers using get and set commands entered on the network management system (NMS) workstation for which SNMP has been implemented. The NMS workstations is also known as the SNMP manager.
MVPN Information Retrieval Using SNMP and the MVPN MIB
SNMP has historically been used to collect network information. SNMP permits retrieval of critical information from network elements such as routers, switches, and workstations. The MVPN MIB uses SNMP to configure MVRF trap notifications and to gather useful MVPN information in real time.
The MVPN MIB allows MVPN data for the managed devices on your system to be retrieved by SNMP. You can specify the retrieval of MVPN information from a managed device (for example, a router) either by entering commands on that managed device or by entering SNMP commands from the NMS workstation to gather MVPN information. MVPN MIB requests for information are sent from an NMS workstation to the router using SNMP and is retrieved from the router. This information can then be stored or viewed, thus allowing MVPN information to be easily accessed and transported across a multivendor programming environment.
MVPN MIB Objects
The MVPN MIB defines managed objects that enable a network administrator to remotely monitor the following MVPN information:
•The state of the MVRFs including the name of the MVRF, whether they are active, and the number of active multicast-enabled interfaces
•MDT default group address and encapsulation information
•Next hop information used to receive Border Gateway Protocol (BGP) MDT updates for Source Specific Multicast (SSM) mode
•Traffic threshold that determines switchover to an MDT data group
•Type of MDT group being used for a given (S, G) multicast route entry that exists on each configured MVRF, source address, and group address of the multicast route entry
•Source and group address used for encapsulation
•Information on MDT data groups currently joined
•Information on MVPN-specific MDT tunnels present in the device
•Trap notifications enabled on the router
Note For a complete description of the objects supported by the MVPN MIB, see the CISCO_MVPN_MIB.my file, available on Cisco.com at http://www.cisco.com/go/mibs.
MVRF Trap Notifications
An MVPN router can be configured to send MVRF (ciscoMvpnMvrfChange) trap notifications. A ciscoMvpnMvrfChange trap notification signifies a change about an MVRF in the device. The change event can be the creation of an MVRF, the deletion of an MVRF, or an update on the default or data multicast distribution tree (MDT) configuration of an MVRF. The change event is indicated by the ciscoMvpnGenOperStatusChange object embedded in the trap notification.
How to Configure Multicast VPN MIB
This section contains the following required procedure:
•Configuring the Router to Send MVRF Trap Notifications (required)
Configuring the Router to Send MVRF Trap Notifications
Perform this task to configure the router to use SNMP to send MVRF trap notifications.
Note Before the MVPN MIB can be used, the SNMP server for the router must be configured. To enable the SNMP server on the router, perform Steps 3 and 4. If an SNMP server is already available, omit Steps 3 and 4 and proceed to Step 5.
SUMMARY STEPS
1. enable
2. configure terminal
3. snmp-server community string ro
4. snmp-server host {hostname | ip-address} version 2c community-string
5. snmp-server enable traps mvpn
6. end
DETAILED STEPS
Configuration Examples for Multicast VPN MIB
This section provides the following configuration example:
•Configuring the Router to Send MVRF Trap Notifications: Example
Configuring the Router to Send MVRF Trap Notifications: Example
The following example shows how to configure a router to use SNMP to send MVRF trap notifications:
!snmp-server community public RWsnmp-server enable traps mvpnsnmp-server host 10.3.32.154 version 2c public!Additional References
The following sections provide references related to the Multicast VPN MIB feature.
Related Documents
Standards
MIBs
MIB MIBs Link•CISCO-MVPN-MIB.my
To locate and download MIBs for selected platforms, Cisco IOS releases, and feature sets, use Cisco MIB Locator found at the following URL:
RFCs
Technical Assistance
Feature Information for Multicast VPN MIB
Table 1 lists the release history for this feature.
Not all commands may be available in your Cisco IOS software release. For release information about a specific command, see the command reference documentation.
Use Cisco Feature Navigator to find information about platform support and software image support. Cisco Feature Navigator enables you to determine which Cisco IOS and Catalyst OS software images support a specific software release, feature set, or platform. To access Cisco Feature Navigator, go to http://www.cisco.com/go/cfn. An account on Cisco.com is not required.
Note Table 1 lists only the Cisco IOS software release that introduced support for a given feature in a given Cisco IOS software release train. Unless noted otherwise, subsequent releases of that Cisco IOS software release train also support that feature.
CCDE, CCSI, CCENT, Cisco Eos, Cisco HealthPresence, the Cisco logo, Cisco Lumin, Cisco Nexus, Cisco Nurse Connect, Cisco Stackpower, Cisco StadiumVision, Cisco TelePresence, Cisco WebEx, DCE, and Welcome to the Human Network are trademarks; Changing the Way We Work, Live, Play, and Learn and Cisco Store are service marks; and Access Registrar, Aironet, AsyncOS, Bringing the Meeting To You, Catalyst, CCDA, CCDP, CCIE, CCIP, CCNA, CCNP, CCSP, CCVP, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Cisco Unity, Collaboration Without Limitation, EtherFast, EtherSwitch, Event Center, Fast Step, Follow Me Browsing, FormShare, GigaDrive, HomeLink, Internet Quotient, IOS, iPhone, iQuick Study, IronPort, the IronPort logo, LightStream, Linksys, MediaTone, MeetingPlace, MeetingPlace Chime Sound, MGX, Networkers, Networking Academy, Network Registrar, PCNow, PIX, PowerPanels, ProConnect, ScriptShare, SenderBase, SMARTnet, Spectrum Expert, StackWise, The Fastest Way to Increase Your Internet Quotient, TransPath, WebEx, and the WebEx logo are registered trademarks of Cisco Systems, Inc. and/or its affiliates in the United States and certain other countries.
All other trademarks mentioned in this document or website are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (0903R)
Any Internet Protocol (IP) addresses and phone numbers used in this document are not intended to be actual addresses and phone numbers. Any examples, command display output, network topology diagrams, and other figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses or phone numbers in illustrative content is unintentional and coincidental.
© 2004-2007 Cisco Systems, Inc. All rights reserved.