|
|
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 for the Cisco 6100 Series system allows direct control and management of a Cisco 6100 Series system 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 with the Cisco 6100 Series system, ViewRunner uses ATM as the physical layer for communication. Throughput on the inband management channel is also significantly slower in this release of the Cisco 6100 Series system.
ViewRunner for HP OpenView supports software downloads and restores for Cisco 6100 Series system nodes being managed via the inband management channel or the Ethernet management channel. The menu option allowing this feature is active only if the system controller supports the feature and the node is being managed through one of the management channels. Warnings are issued if software download or restore is not supported by either the current or the target
system controller.
To run IP over ATM, the system uses RFC 1483 "Multiprotocol Encapsulation over ATM Adaptation Layer 5" in Logical Link Control (LLC) encapsulation mode. This encapsulation allows transporting via multiple protocols over a single virtual channel (VC). Figure 7-1 illustrates how the inband management channel works.
To make sure the outbound packets from the Cisco 6100 Series system are sent to the right interface (Ethernet or inband), a routing table for various IP addresses is also supported.
To use the inband management channel rather than Ethernet, follow these steps:
Step 1 Access the 6100 Chassis View
Step 2 Move your cursor over the chassis, and click the right mouse button. The menu in Figure 7-2 appears.
Step 3 Select 6100 Inband Management Channel and the dialog box shown in
Figure 7-3 appears.
Step 4 Enter the IP address of the inband port and its subnet mask. 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 dialog box disappears and the buttons become active. Press Apply and then Unlocked to activate the configuration. All fields are shaded then unless you set the Administrative State back to Locked to change the information.
Following are things that you should consider when using the inband management channel.
It is not necessary to use the routing table if you are using Ethernet as the method for managing a Cisco 6100 Series system as long as the Ethernet management system is running on the same subnet as the Cisco 6100 Series system. However, if ViewRunner for HP OpenView is running on a different subnet from the subnet on which the Ethernet management system is running, a routing table for Ethernet is necessary.
In any case, a routing table is necessary with inband management so that the Cisco 6100 Series system can send the outbound 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, use the following procedures:
Step 1 Access the 6100 Chassis View.
Step 2 Move your cursor over the chassis, and click the right mouse button. The menu in Figure 7-4 appears.
Step 3 Select Routing Table and the dialog box in Figure 7-5 appears.
Step 4 Set the Interface to Inband Channel.
Step 5 Enter the network IP address of the packet destination. (If the host address is added, it is automatically converted to a network address).
Step 6 Enter the gateway IP address, and its subnet mask. Then click Add Now.
If you want to change the destination IP address, simply return to the Routing Table dialog box, select a destination from the top field and select Delete Now to delete an address. Then add a different address using the procedures that were previously described.
ViewRunner allows you to configure routes for the local interface only. You cannot configure a routing table for a Cisco 6100 Series system that is one hop away. The router to which the Cisco 6100 Series system is connected must complete any required routing.
Following are things that you should consider when establishing the routing table:
In releases prior to 2.2, the Cisco 6100 Series system sent event or alarm traps to only one recipient, which had the same IP address as the server. In this release, you can have traps of various severities sent to as many as ten recipients. Each recipient can receive events or alarms filtered to a different severity level if desired.
To establish multiple trap recipients, use the following procedures:
Step 1 Access the 6100 Chassis View.
Step 2 Move your cursor over the chassis, and click the right mouse button. The menu in Figure 7-6 appears.
Step 3 Select 6100 Traps Recipients and the dialog box in Figure 7-7 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 receives traps of that severity or higher (or no traps at all).
Step 5 Determine whether to enable or disable standard Simple Network Management Protocol (SNMP) traps or authentication traps and check the appropriate boxes as shown in Figure 7-7. Note that if system-wide authentication traps are not enabled, you cannot set an individual recipient to receive authentication traps at all.
Step 6 Click Add Now to complete the process.
If you want to delete a trap recipient from the list, simply return to the Trap Recipients dialog box, select a recipient from the top field and click Remove Now to delete that address.
Following are things you should consider when establishing multiple trap recipients:
Posted: Tue Oct 5 13:09:43 PDT 1999
Copyright 1989-1999©Cisco Systems Inc.