|
|
ViewRunner allows you to configure your system in several ways to allow for specific management and monitoring techniques. This chapter discusses the following:
Using the inband management channel feature of the ViewRunner for Windows allows direct control/management of the Cisco 6100 through the ATM channel. The inband management channel is transparent to ViewRunner in that provisioning and operation of the system are identical whether through the ethernet port or the inband channel. The only difference is that instead of using conventional ethernet physical media to communicate to the Cisco 6100, ViewRunner will use ATM as the physical layer for communication.
To run IP over ATM, the system uses RCF 1483 "Multi-protocol over AAL5" in Logical Link Control (LLC) encapsulation mode. This encapsulation will allow transporting via multiple protocols over a single VC. The following figure illustrates how the inband management channel works.
To make sure the out-bound packets from the Cisco 6100 are sent to the right interface (ethernet or inband), a routing table for various IP addresses is also supported. A routing table entry is required for inband operation.
To use the inband management channel rather than ethernet, follow the procedures below.
Step 1 Access the main Chassis View.
Step 2 Move your cursor over the chassis, and click the right mouse button. The following pop-up menu appears:
Step 3 Select Inband Management Channel and the following window appears.
Step 4 Enter the IP address of the inband port and its submask. Then specify the VPI/VCI to be used for the communication channel.
The Administrative state must be Locked for you to enter the IP and VPI/VCI information. Once you have entered this information the note at the bottom of the window disappears and the buttons become active. Press Apply and then Unlocked to activate the configuration. All fields will be grayed out then unless you set the Administrative state back to Locked to change the information.
Consider the following when using the inband management channel.
It is not usually necessary to use the routing table if you are using ethernet as the method for managing a Cisco 6100. However, a routing table is required for inband management so that the Cisco 6100 can send the out-bound packets to the right interface. Otherwise, the return packets would never reach their destination.
To add IP addresses to the routing table when using the inband management channel rather than ethernet, follow the procedures below.
Step 1 Access the main Chassis View.
Step 2 Move your cursor over the chassis, and click the right mouse button. The following pop-up menu appears:
Step 3 Select Routing Table and the following window appears.
Step 4 Set the Interface to Inband Channel.
Step 5 Enter the IP address of the packet destination, its gateway IP address, and its submask. Then select Add Now.
Should you want to change the destination IP address, simply navigate back to this window, select a destination from the top field and select Delete Now to delete an address. Then add a different one following the procedures presented previously.
Consider the following when establishing the routing table.
In releases prior to Cisco 6100 2.2, the Cisco 6100 sent event/alarm traps to only one recipient, which had the same IP address as the server. If Cisco 6100 software supports multiple trap recipients, ViewRunner allows up to 10 trap recipients to be configured. Each recipient can receive events/alarms filtered to a different severity level if desired.
To establish multiple trap recipients, follow the procedures below.
Step 1 Access the main Chassis View.
Step 2 Move your cursor over the chassis, and press the right mouse button. The following pop-up menu appears.
Step 3 Select the Traps option, and the following window appears.
Step 4 Enter the IP address of the first trap recipient. Then choose the event level filter for that recipient. This filter indicates that the recipient will receive traps of that severity or higher (or no traps at all).
Step 5 Determine whether to enable or disable standard SNMP traps or authentication traps and check the appropriate boxes as shown in the window below. Note that if system-wide authentication traps are not enabled, you cannot set an individual recipient to receive authentication traps at all.
Step 6 Press Add Now to complete the process.
Should you want to delete a trap recipient from the list, simply get back to this window, select a recipient from the top field and select Remove Now to delete that address.
Consider the following when establishing multiple trap recipients.
Posted: Mon Oct 11 22:19:25 PDT 1999
Copyright 1989-1999©Cisco Systems Inc.