BPX Routing Hubs in a Tiered Network

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 AIT trunk card on the IPX interface shelf and the BNI trunk card on the BPX 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.

Once an IPX switch has been converted to an interface shelf, it can be joined to the BPX routing hub, by executing the addshelf command at the BPX routing hub. The addshelf command has the following syntax:

Interface Shelf Management

addshelf <trunk> <shelf_type>

trunkslot.port

shelf_typeI (IPX/AF) or A (MGX 8220)

delshelf <trunk> <shelf_name> deletes interface shelf

dspnode:Displays feeder trunk status. BPX Hub nodes display the status of all attached Interface shelves. IPX interface shelves display a single status item, that of the attached BPX Hub node.

Alarm Management of Interface Shelf on the BPX Hub Node

dspalms

A new field, interface shelf alarms, shows a count of the number of interface

 

shelves which are Unreachable, in Minor Alarm, or in Major Alarm. The

 

nnn-A bit status failures for shelf connections are also shown.

Tiered Networks 13-7

Page 339
Image 339
Cisco Systems 8600 Series manual Configuration and Management, Interface Shelf Management