Cisco Systems 8600 Series manual Configuration and Management, Shelf Management

IGX Routing Hubs in a Tiered Network

•IP Relay

•Robust Object Updates

•Robust Alarm Updates

•Real-time Counters

•Event Logging

•Software/Firmware Downloads

•Configuration Save/Restore

•SNMP

Configuration and Management

The interface shelves attached to each hub must have unique names. Each interface shelf must also be assigned a unique IP address.

An interface shelf communicates with a routing hub over a new type of NNI. It is similar to the existing Frame Relay NNI in purpose and function, and is based on the ATM LMI message set described by Recommendation 2931, Annex G. A routing hub and interface shelf use this NNI to maintain a control session with each other. Any change to the status of the feeder trunk affects this control session.

Feeder trunks are the communication path between the routing hub and the Feeder. These feeder trunks are supported by the BTM trunk card on both the IGX interface shelf and the IGX routing hub. Feeder trunks are upped using the “uptrk” command. Feeder trunks must be upped on both the routing hub and the interface shelf before it can be joined to the routing network.

An IGX node must be converted to an interface shelf by entering the appropriate command at the node. Once an IGX switch has been converted to an interface shelf, it can be joined to the IGX routing hub, by executing the addshelf command at the IGX routing hub. The addshelf command has the following syntax:

Shelf Management

addshelf <trunk> <shelf_type>

trunkslot.port

shelf_type I (IGX/AF)

delshelf <trunk> <shelf_name> deletes interface shelf

dspnode:Displays feeder trunk status. IGX routing hubs display the status of all attached IGX interface shelves. IGX interface shelves display a single status item, that of the attached IGX hub node.

13-14Cisco BPX 8600 Series Reference