|
|
This MIB is primarily oriented toward management of Multiprotocol Label Switching (MPLS) systems. As such, the MIB resides in routers that are also label switch controllers (LSCs). These are routers that are VSI capable, and whose network control application is MPLS.
VSI Masters and Slaves
A controller application uses a VSI master to control one or more VSI slaves. For the BPX, the controller application and master VSI reside in an external 7200 or 7500 series router and the VSI slaves are resident in BXM cards on the BPX node (Figure 1).
The controller sets up the following types of connections:
Control virtual connections (VCs)
User Connection
This document includes the following major sections:
The VSI Master MIB supports the following VSI components:
The VSI Master MIB provides a standardized vehicle for monitoring the operation of the VSI protocol within an LSC. It also displays the results of the operations of the protocol. Specifically, the VSI Master MIB allows you to monitor
The following is a partial list of the supported MIB objects
The VSI Master MIB is for MPLS controllers only.
See the following documents for more information:
http://www.cisco.com/public/mibs/v2/CISCO-VSIMASTER-MIB.my
http://www.cisco.com/univercd/cc/td/doc/product/software/ios121/121newft/121t/121t3/index.htm
This feature is supported on the following platforms:
Standards
No new or modified standards are supported by this feature.
MIBs
Virtual Switch Interface Master MIB
http://www.cisco.com/public/mibs/v2/CISCO-VSIMASTER-MIB.my
For descriptions of supported MIBs and how to use MIBs, see the Cisco MIB web site on Cisco Connection Online (CCO) at http://www.cisco.com/public/sw-center/netmgmt/cmtk/mibs.shtml.
RFCs
No new or modified RFCs are supported by this feature.
See the following sections for configuration tasks for the VSI Master MIB feature. Each task in the list indicates if the task is optional or required.
The SNMP agent for the VSI Master MIB is disabled by default. To enable the SNMP agent, perform the following steps:
| Command | Purpose | |
|---|---|---|
Step 1 | prompt# telnet 10.10.10.1 | Accesses the router through a Telnet session. |
Step 2 | router# enable | Enters the privileged mode. |
Step 3 | router# show running-configuration | Displays the running configuration to see if the SNMP agent is already running. If no SNMP information is present, continue with the steps below. If any SNMP commands are listed, you can modify them or leave them as they are. |
Step 4 | router# configure terminal | Enters the configuration mode. |
Step 5 | router(config)# snmp-server community xxxxxx RO | Enables the read-only community string, where xxxxxx is the read-only community string |
Step 6 | router(config)# exit | Exits the configuration mode and returns to the main prompt. |
Step 7 | router# write memory | Writes the modified configuration to nonvolatile memory (NVRAM) so the settings stay permanently. |
To verify that the SNMP agent has been enabled, perform the following steps:
prompt# telnet 10.10.10.1
Step 2 Enter the privileged mode:
router# enable
Step 3 Display the running configuration and look for SNMP information:
router# show running-configuration ... ... snmp-server community public RO
If you see any "snmp-server" statements, SNMP has been enabled on the router.
In the following example, the SNMP agent is enabled:
snmp-server community
In the following example, SNMPv1 and SNMPv2C are enabled. The configuration permits any SNMP manager to access all objects with read-only permissions using the community string public.
snmp-server community public
In the following example, read-only access is granted for all objects to members of access list 4 that specify the comaccess community string. No other SNMP managers have access to any objects.
snmp-server community comaccess ro 4
This section documents new or modified commands. All other commands used with this feature are documented in the Cisco IOS Release 12.1 command reference publications.
Use the snmp-server community global configuration command to configure read-only or read-write Simple Network Management Protocol (SNMP) community strings. Use the no snmp-server community command to change the community string to its default value.
snmp-server community string [view view-name] [ro | rw] [number]
Syntax Description
string Community string of 1 to 32 alphanumeric characters. The community string acts like a password and permits access to the SNMP protocol. No blank character spaces are allowed. view view-name (Optional) Name of a previously defined view. The view defines the objects available to the community. ro (Optional) Configures read-only access. Authorized management stations can only retrieve MIB objects. rw (Optional) Configures read-write access. Authorized management stations can both retrieve and modify MIB objects. number (Optional) Integer from 1 to 99 that specifies an access list of IP addresses that are allowed to use the community string to gain access to the SNMP v.1 agent.
Defaults
Read-only (ro)
The default value of the read-only community string is public, and the default value of the read-write community string is private.
Command Modes
Global configuration
Command History
Cisco IOS Release 10.0 This command was introduced.
Release
Modification
Usage Guidelines
The no snmp-server command disables both versions of SNMP (SNMPv1 and SNMPv2).
The first snmp-server command that you enter enables both versions of SNMP.
Examples
In this example, the read-write community string is set to newstring:
hostname (config)# snmp-server community newstring rw
In the following example, the string comaccess is assigned to SNMPv1 allowing read-only access. Only IP access list 4 can use the community string.
snmp-server community comaccess ro 4
In the following example, the string mgr is assigned to SNMPv1 allowing read-write access to the objects in the restricted view:
snmp-server community mgr view restricted rw
In the following example, the community comaccess is removed:
no snmp-server community comaccess
In the following example, both versions of SNMP are disabled:
no snmp-server
Related Commands
snmp-server host Specifies the recipient of an SNMP trap operation. snmp-server enable-trap Enables the router to send SNMP traps.
Command
Description
inform request—A message sent by an SNMP agent to a network management station, console, or terminal to indicate that a significant event occurred. SNMP inform requests are more reliable than traps because an inform request sends an SNMP response protocol data unit (PDU). If the manager does not receive an inform request, it does not send a response. If the sender never receives a response, the inform request can be sent again. Thus, inform requests are more likely to reach their intended destination.
Management Information Base—See MIB.
MIB—Management Information Base. A database of network management information that is used and maintained by a network management protocol such as SNMP. The value of a MIB object can be changed or retrieved through the use of SNMP commands, usually through a network management system. MIB objects are organized in a tree structure that includes public (standard) and private (proprietary) branches.
Simple Network Management Protocol—See SNMP.
SNMP—Simple Network Management Protocol. A management protocol used almost exclusively in TCP/IP networks. SNMP provides a means to monitor and control network devices, and to manage configurations, statistics collection, performance, and security.
trap—A message sent by an SNMP agent to a network management station, console, or terminal to indicate that a significant event occurred. Traps are less reliable than inform requests, because the receiver does not send an acknowledgment when it receives a trap. The sender cannot determine if the trap was received.
VSI Master—A VSI master process implementing the master side of the VSI protocol in a VSI controller. Sometimes the whole VSI controller might be referred to as a "VSI Master," but this is not strictly correct.
1. A device that controls a VSI switch, for example, a VSI Label Switch Controller
2. A process implementing the master side of the VSI protocol
VSI Slave—A VSI slave is either of the following:
1. A switch (in the "Single Slave model") or a port card (in the "Multiple Slave Model") that implements the VSI
2. A process implementing the slave side of the VSI protocol
Posted: Tue Sep 19 17:37:45 PDT 2000
Copyright 1989-2000©Cisco Systems Inc.