cc/td/doc/product/dsl_prod/vrmgtsw/vr4ov/rel235
hometocprevnextglossaryfeedbacksearchhelp
PDF

Table of Contents

System Level Configuration

System Level Configuration

ViewRunner allows you to configure your system in several ways to allow for specific management and monitoring techniques. This chapter discusses the following:

7.1 Inband Management Channel

Using the inband management channel feature of the Cisco 6100 allows direct control/management of a 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. Throughput on the inband management channel is also significantly slower in this release of the Cisco 6100.

ViewRunner for HP OpenView supports software downloads and restores for Cisco 6100 nodes being managed via the inband management channel or the ethernet management channel. The menu option allowing this feature is active only if the SC supports the feature and the node is being managed through one of the management channels. Warnings will be issued if software download/restore is not supported by either the current of the target SC.

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 virtual channel (VC). The following figure illustrates how the inband management channel works.


Figure 7-1: Running IP over ATM


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.

7.1.1 Invoking the Inband Management Channel

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:


Figure 7-2: Inband Management Channel Menu


Step 3 Select 6100 Inband Management Channel and the following window appears.


Figure 7-3: Inband Management Channel Window


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 greyed out then unless you set the Administrative State back to Locked to change the information.

7.1.2 Special Considerations for Inband Management

The following are things that you should consider when using the inband management channel.


Note Clearing NVRAM will delete the provisioning information for the inband management channel.

7.1.3 Routing Table

It is not necessary to use the routing table if you are using Ethernet as the method for managing a Cisco 6100 as long as the Ethernet management system is running on the same subnet as the Cisco 6100s. 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 will be necessary.

In any case, a routing table is necessary with 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.

7.1.4 Establishing the Routing Table

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:


Figure 7-4: Routing Table Menu


Step 3 Select Routing Table and the following window appears.


Figure 7-5: Routing Table Window


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 will be automatically converted to network address).

Step 6 Enter the gateway IP address, and its submask. Then select Add Now.

Should you want to change the destination IP address, simply get 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 described above.

The ViewRunner allows you to configure routes for the local interface only. You cannot configure a routing table for a Cisco 6100 that is one hop away. The router to which the Cisco 6100 is connected must complete any required routing.

7.1.5 Special Considerations for the Routing Table

The following are things that you should consider when establishing the routing table.


Note The above feature will be available in a future release.

7.2 Multiple Trap Recipients

In releases prior to 2.2, the Cisco 6100 sent event/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 up to ten recipients. Each recipient can receive events/alarms filtered to a different severity level if desired.

7.2.1 Establishing Multiple Trap Recipients

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.


Figure 7-6: Multiple Trap Recipients Menu


Step 3 Select the 6100 Traps Recipients option, and the following window appears.


Figure 7-7: Multiple Trap Recipients Window


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).


Note ViewRunner for HP OpenView must be set as a trap recipient, and it must be configured to receive all traps. Intelligent configuration synchronization is predicated on the receipt of all traps, and alarm synchronization will discover any filtered traps anyway.

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 the 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.

7.2.2 Special Considerations for Multiple Trap Recipients

The following are things you should consider when establishing multiple trap recipients.


hometocprevnextglossaryfeedbacksearchhelp
Posted: Fri Oct 8 13:03:30 PDT 1999
Copyright 1989-1999©Cisco Systems Inc.