Configuring the System

"ViewRunner is currently using the in-band channel to communicate with the Cisco 6100 Series; modifying it will cause ViewRunner to lose communication with the Cisco 6100 Series."
 

• Cisco 6100 Series system software releases prior to Release 2.3.0 do not support restore and software download operations over an in-band management channel. ViewRunner Release 2.3.5 detects whether an in-band management channel can manage a Cisco 6100 Series system. ViewRunner Release 2.4.0 and later support in-band management channel enabling and disabling of restore and software download operations.

• ViewRunner prohibits changing the IP address of the in-band channel to that of the Cisco 6100 Series system out-of-band channel. If you attempt to do this, ViewRunner displays the following error message:

"IP address is already in use by the Cisco 6100 Series."
 

• You must ensure that the Administrative state of the channel is Locked before you modify any of the attributes. The attributes take effect when you change the Administrative state to Unlocked and apply the changes.

• At the in-band command line, ViewRunner sets the appropriate SNMP time-out internally. (In previous releases of ViewRunner, you had to set the SNMP time-out.)

• The Management Information Base (MIB) contains the required guidelines for setting the Administrative state to Unlocked.

• The IP address and subnet mask component numbers must be in the range from 0 to 255.

Step 3 Choose Inband Management Channel from the Chassis menu.

Note Make sure that the Administrative state is Locked before you enter the IP and VPI/VCI information.

Step 4 Enter the IP address of the in-band port in the IP Address of Node Inband port field.

Step 5 Enter the Subnet Mask number in the Subnet Mask field.

Step 6 Specify the VPI and the VCI, to be used for the communication channel, in the Network Side fields by using the down arrows to choose the correct number from the following choices:

• VPI---0 to 27

• VCI---1 to 399

Step 7 Click Apply to activate the configuration.

Step 8 Click Unlocked in the Administrative State field.

• The node supports a maximum of five route entries.

• The node does not support direct routes such as (IP AND Mask) ! = (Destination AND Mask).

• ViewRunner prohibits you from entering identical destination IP address or submask combinations.

• Value modification is not supported. You must delete the entry and add a new entry to modify a value.

• You cannot delete the default gateway route.

• IP address component numbers must be 0 to 255.

• The destination IP address must be a subnet address; it cannot be a host address. ViewRunner verifies this address against the subnet mask address that you entered in the Subnet Mask field, and displays an error message if you enter an invalid address.

• The destination IP address must be on a different subnet mask; it cannot be a direct route. If the destination IP address is a direct route, you do not need to enter an address in the Routing Table.

• If Ethernet management and in-band channel management are on the same subnet, you disable the Ethernet if you add the in-band route. Therefore, make sure that you configure the in-band channel and that it is operational before you add the route in the routing table.

• You must use separate subnets for Ethernet management and in-band channel management.

Step 3 Choose Routing Table from the Chassis menu.

Step 5 Enter the IP address of the packet destination in the Destination IP field.

Step 6 Enter the gateway IP address in the Gateway IP field.

Step 7 Enter the Subnet Mask address in the Subnet Mask field.

Step 2 Click Delete Now to delete an address.

Step 3 Choose Trap Recipients from the Chassis menu.

The event-level filter indicates that the recipient can receive traps of that severity or higher (or no traps at all). The choices include the following levels:

• Info---If you choose this level, the recipient server receives notification of any informational, minor, major, and critical events.

• Minor---If you choose this level, the recipient server receives notification of any minor, major, and critical events.

• Major---If you choose this level, the recipient server receives notification of any major and critical events.

• Critical---If you choose this level, the recipient server only receives notification of any critical events.

• None---If you choose this setting, the recipient server does not receive event notification at any level.

Step 6 Click the box next to the Enable standard SNMP traps field to enable this feature, or leave it unselected to disable it.

Enabling this option allows the recipient to receive the following standard SNMP traps:

• Cold start

• Link Up

• Link Down

Step 7 Click the box next to Enable authentication-failure traps to enable this feature, or leave it unselected to disable it.

Enabling the authentication-failure traps allows the recipient to receive traps when the software tries to access the 6100 MIB using an invalid community string.

---

Note You must enable the system-wide authentication traps Now field at the bottom of the Trap Recipients dialog box for an individual to receive an authentication trap.

---