|
|
This chapter describes the tiered network architecture that supports interface shelves (non-routing nodes) connected to Cisco WAN switching routing network.
The chapter contains the following:
With Release 8.5 and beyond, tiered networks now support voice and data connections as well as frame relay connections. With this addition, a tiered network can now provide a multi-service capability (frame relay, circuit data, voice, and ATM). By allowing CPE connections to connect to a non-routing node (interface shelf), a tiered network is able to grow in size beyond that which would be possible with only routing nodes comprising the network.
In a tiered network, interface shelves at the access layer (edge) of the network are connected to routing nodes via feeder trunks (Figure 6-1). Those routing nodes with attached interface shelves are referred to as routing hubs. The interface shelves, sometimes referred to as feeders, are non-routing nodes. The routing hubs route the interface shelf connections across the core layer of the network.
The interface shelves do not need to maintain network topology nor connection routing information. This task is left to their routing hubs. This architecture provides an expanded network consisting of a number of non-routing nodes (interface shelves) at the edge of the network that are connected to the network by their routing hubs.
Voice and data connections originating and terminating on Cisco IGX 8400 series multiband switches configured as interface shelves (feeders) are routed across the routing network via their associated Cisco IGX 8400 series multiband switches configured as routing hubs. Intermediate routing nodes must be Cisco IGX 8400 series multiband switches.
Frame relay connections originating at IPX interface shelves and frame relay, ATM, CESM, and FUNI connections originating at Cisco MGX 8220 edge concentrator interface shelves are routed across the routing network via their associated Cisco BPX 8600 series broadband routing hubs.
 |
Note The Cisco IGX 8400 series multiband switch may also be configured as an interface shelf feeding frame relay connections to a Cisco BPX 8600 series broadband routing hub. |
With tiered networks, Cisco IGX 8400 series multiband switches on the edge of the network are configured as interface shelves and are connected to Cisco IGX 8400 series multiband switches configured as router hubs. The interface shelves allow the network to support additional voice, data and frame relay connections without adding additional routing nodes. An example of 3-segment voice and data connections via a Cisco IGX 8400 series multiband switch configured as an interface shelf and Cisco IGX 8400 series multiband routing hubs is shown in Figure 6-2. An example of a frame relay connection via Cisco IGX 8400 series multiband switches configured as interface shelves and routing hubs is shown in Figure 6-3.
The following applies to Cisco IGX 8400 series multiband routing hubs and interface shelves:
The following applies to voice and data connections over Cisco IGX 8400 series multiband interface shelves:
The following applies to frame relay connections over Cisco IGX 8400 series multiband interface shelves via a Cisco IGX 8400 series multiband hub.
Annex G, a bi-directional protocol, defined in Recommendation Q.2931, is used for monitoring the status of connections across a UNI interface. Tiered Networks use the Annex G protocol to pass connection status information between a hub node and attached shelf.
Cisco IGX 8400 Series Multiband Routing Hub | A Cisco IGX 8400 series multiband switch in the routing network which has attached Cisco IGX 8400 series multiband switches configured as interface shelves. Also referred to as a hub node or IGX hub. |
IGX Interface Shelf | A special configuration of a Cisco IGX 8400 series multiband switch that is connected as a shelf to an Cisco IGX 8400 series multiband switch configured as a routing hub. A Cisco IGX 8400 series multiband interface shelf is sometimes referred to as IGX A/F or feeder. The Cisco IGX 8400 series multiband interface shelf does not perform routing functions nor keep track of network topology. |
Feeder Trunk | Refers to a trunk which interconnects a Cisco IGX 8400 series multiband interface shelf with the routing network via a Cisco IGX 8400 series multiband routing hub. A feeder trunk is sometimes referred to as an interface shelf trunk. |
IGX/AF | Another name for the IGX interface shelf |
Routing Network | The portion of the tiered network which performs automatic routing between connection endpoints. |
VPI | Virtual Path Identifier |
VCI | Virtual Connection Identifier |
Converting an Cisco IGX 8400 series multiband switch to an interface shelf requires re-configuring connections on the node, as no upgrade path is provided in changing a routing node to an interface shelf.
Only Cisco IGX 8400 series multiband switches are able to act hub nodes for IGX interface shelves for voice and data transport over the IGX tiered network. A Cisco IGX 8400 series multiband switch, acting as a hub node, is not restricted from providing any other feature which is normally available on IGX nodes. An IGX hub supports up to 4 IGX interface shelves.
Connections within tiered networks consist of three distinct segments within each tier. A routing segment traverses the routing network, with an interface shelf segment at each end providing connectivity to the interface shelf end-point. Each of these segments are added, configured and deleted independently of the other segments. The Cisco WAN Manager Connection Manager provides management of these individual segments as a single end-to-end connection.
Interface shelves are attached to the routing network via an IGX node using a BTM E1 trunk. The connection segments within the routing network are terminated on IGX feeder trunks.
The feeder trunk between an interface shelf and the routing network is a single point of failure, therefore, the interface shelves should be co-located with their associated hub node. Card level redundancy is supported by the Y-Cable redundancy for the CVM, LDM, and HDM.
Communication between CPE devices and the routing network is provided in accordance with Annex G of Recommendation Q.2931. This is a bidirectional protocol for monitoring the status of connections across a UNI interface.
Communication includes the real time notification of the addition or deletion of a connection segment and the ability to pass the availability (active state) or unavailability (inactive state) of the connections crossing this interface.
A proprietary extension to the Annex G protocol is implemented which supports the exchange of node information between an interface shelf and the routing network. This information is used to support the IP Relay feature and the Robust Update feature used by network management.
Network Management access to the interface shelves is through the IP Relay mechanism supported by the SNMP and TFTP or by direct attachment to the interface shelf. The IP Relay mechanism relays traffic from the routing network to the attached interface shelves. No IP Relay support is provided from the interface shelves into the routing network.
IGX routing hubs are the source of the network clock for its associated feeder nodes. Feeders synchronize their time and date to match their routing hub.
Robust Object and Alarm Updates are sent to a network manager which has subscribed to the Robust Updates feature. Object Updates are generated whenever an interface shelf is added or removed from the hub node and when the interface shelf name or IP Address is modified on the interface shelf. Alarm Updates are generated whenever the alarm state of the interface shelf changes between Unreachable, Major, Minor and OK alarm states.
An interface shelf is displayed as a unique icon in the SV+ Network Management topology displays. The colors of the icon and connecting trunks indicate the alarm state of each. Channel statistics are supported by CVM, HDM, and LDM endpoints. Trunk Statistics are supported for the feeder trunk and are identical to the existing IGX trunk statistics.
Preferred routing within the routing network can be used on all connections. Priority bumping is supported within the routing network, but not in the interface shelves. All other connection features such as conditioning, rrtcon, upcon, dncon, etc. are also supported.
Connection local and remote loopbacks are managed at the user interface of the voice or data endpoint Routing Node or interface shelf. The existing IGX voice and data port loopback features are supported on the IGX interface shelf.
Tstcon is supported at the voice and data endpoints in a non-integrated fashion and is limited to a pass/fail loopback test. Fault isolation is not performed. Intermediate endpoints at the BTM cards do not support the tstcon feature. Tstdelay is also supported for the in a non-integrated fashion similar to that of the tstcon command.
The IGX interface shelf supports the termination of voice and data connection segments to a BTM. The IGX interface shelf connects to the routing network via a BTM and associated BMT-E1 back card on both the interface shelf and the IGX routing hub.
IGX interface shelves support the following network management features:
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 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:
addshelf <trunk> <shelf_type>
trunk slot.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.
dspalms | The 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 interface shelf connections are also shown. |
dspalms | The field, routing network Alarms, shows a count of major and minor alarms in the routing network. Feeder A-bit connection status reported by feeder NNI is shown in the "Connection A-Bit Alarms" field. |
dspnode: | Shows if the routing network is reachable and the attached IGX hub node. |
Uses existing commands.
Parameters entered at the Cisco WAN Manager workstation when adding connections.
Parameters entered at the Cisco WAN Manager workstation when adding connections. Bandwidth performance is monitored by viewing selected statistics at the Cisco WAN Manager NMS.
Since voice traffic is time sensitive, and low-speed voice connections can result in SGW cells being sent with only a single packet placed in the cell in order to avoid excessive delay between cells. It may be necessary to use the cnfcmb command on the interface shelves in order to configure the packet combining timeout rate for a particular application.
Enabled and monitored via Cisco WAN Manager.
Refer to the Command Reference manual for additional information on commands associated with tiered networks. The following is a list of most often used commands with IGX routing hubs and IGX interface shelves supporting voice and data connections.
addshelf
delshelf
dspnode
dspalms
dsptrks
addcon
dspcon
dspcons
cnfchdfm
cnfcheia
cnfcldir
cnfdchtp
cnfdclk
cnfict
addcon
cnfchadv
cnfchutil
cnfchkdl
cnfcos
cnfechec
cnfchgn
cnfcond
cnfrcvsig
cnfvchtp
cnfxmtisig
cnfcmb
Tiered networks with Cisco BPX 8600 series broadband routing hubs have the capability of adding interface shelves/feeders (non-routing nodes) to an IPX/IGX/Cisco BPX 8600 series broadband routing network (Figure 6-4). The Cisco MGX 8220 edge concentrator interface shelf, and IPX or IGX nodes configured as interface shelves are connected to Cisco BPX 8600 series broadband routing hubs. Interface shelves allow the network to support additional connections without adding additional routing nodes.
The Cisco MGX 8220 edge concentrator supports frame T1/E1, X.21 and HSSI frame relay, ATM T1/E1, and CES, and is designed to support additional interfaces in the future. The IPX interface shelf supports frame relay ports, as does the IGX (option is available to configure as an interface shelf).
The following requirements apply to Cisco BPX 8600 series broadband routing hubs and their associated interface shelves:
Annex G, a bi-directional protocol, defined in Recommendation Q.2931, is used for monitoring the status of connections across a UNI interface. Tiered Networks use the Annex G protocol to pass connection status information between a hub node and attached interface shelf.
Cisco BPX 8600 series broadband Routing Hub | A Cisco BPX 8600 series broadband switch in the routing network which has attached interface shelves. Also referred to as a hub node or Cisco BPX 8600 series broadband hub. |
Cisco MGX 8220 edge concentrator Interface Shelf | A standards based service interface shelf that connects to a Cisco BPX 8600 series broadband routing hub, aggregrates and concentrates traffic, and performs ATM adapation for transport over broadband ATM networks. |
IPX Interface Shelf | A special configuration of the Cisco IPX narrow band node designated as a interface shelf that supports frame relay connections. |
IGX Interface Shelf | A special configuration of the IGX multiband node designated as a interface shelf that supports frame relay connections. |
Feeder Trunk | Refers to a trunk which interconnects an interface shelf with the routing network via a Cisco BPX 8600 series broadband switch configured as a routing hub. A feeder trunk is sometimes referred to as an interface shelf trunk. |
IPX/AF | Another name for the IPX interface shelf |
IGX/AF | Another name for the IGX interface shelf |
Routing Network | The portion of the tiered network which performs automatic routing between connection endpoints. |
VPI | Virtual Path Identifier |
VCI | Virtual Connection Identifier |
Converting an IPX or IGX node to an interface shelf requires re-configuring connections on the node, as no upgrade path is provided in changing a routing node to an interface shelf.
A Cisco BPX 8600 series broadband switch, acting as a hub node, is not restricted from providing any other feature which is normally available on Cisco BPX 8600 series broadband switches. A Cisco BPX 8600 series broadband switch configured as a routing hub supports up to 16 interface shelves.
Connections within tiered networks consist of distinct segments within each tier. A routing segment traverses the routing network, and an interface shelf segment provides connectivity to the interface shelf end-point. Each of these segments are added, configured and deleted independently of the other segments. The SV+ Connection manager provides management of these individual segments as a single end-to-end connection.
Interface shelves are attached to the routing network via a Cisco BPX 8600 series broadband switch configured as a routing hub using a BXM trunk (T3/E3 or OC3) or BNI trunk (T3/E3). The connection segments within the routing network are terminated on the BNI feeder trunks.
All frame relay connection types which can terminate on the Cisco BPX 8600 series broadband ASI card are supported on the BNI feeder trunk (currently VBR, CBR, ABR, and ATF types). No check is made by the routing network to validate whether the connection segment type being added to a BNI feeder trunk is actually supported by the attached interface shelf.
The trunk between an interface shelf and the routing network is a single point of failure, therefore, the interface shelves should be co-located with their associated hub node. Card level redundancy is supported by the Y-Cable redundancy for the BXM, BNI, AIT, and BTM.
Communication between CPE devices and the routing network is provided in accordance with Annex G of Recommendation Q.2931. This is a bidirectional protocol for monitoring the status of connections across a UNI interface. (Note: the feeder trunk uses the STI cell format to provide the ForeSight rate controlled congestion management feature.)
Communication includes the real time notification of the addition or deletion of a connection segment and the ability to pass the availability (active state) or unavailability (inactive state) of the connections crossing this interface.
A proprietary extension to the Annex G protocol is implemented which supports the exchange of node information between an interface shelf and the routing network. This information is used to support the IP Relay feature and the Robust Update feature used by network management.
Network Management access to the interface shelves is through the IP Relay mechanism supported by the SNMP and TFTP projects or by direct attachment to the interface shelf. The IP Relay mechanism relays traffic from the routing network to the attached interface shelves. No IP Relay support is provided from the interface shelves into the routing network.
The Cisco BPX 8600 series broadband switch configured as a routing hub is the source of the network clock for its associated feeder nodes. Feeders synchronize their time and date to match their routing hub.
Robust Object and Alarm Updates are sent to a network manager which has subscribed to the Robust Updates feature. Object Updates are generated whenever an interface shelf is added or removed from the hub node and when the interface shelf name or IP Address is modified on the interface shelf. Alarm Updates are generated whenever the alarm state of the interface shelf changes between Unreachable, Major, Minor and OK alarm states.
An interface shelf is displayed as a unique icon in the SV+ Network Management topology displays. The colors of the icon and connecting trunks indicate the alarm state of each. Channel statistics are supported by FRP, FRM, ASI, and Cisco MGX 8220 edge concentrator endpoints. BNIs, AITs, and BTMs do not support channel statistics. Trunk Statistics are supported for the feeder trunk and are identical to the existing BNI trunk statistics.
Foresight for an IPX interface shelf terminated Frame Relay connections is provided end-to-end between Frame Relay ports, regardless as to whether these ports reside on an IPX interface shelf or within the routing network.
Preferred routing within the routing network can be used on all connections. Priority bumping is supported within the routing network, but not in the interface shelves. All other connection features such as conditioning, rrtcon, upcon, dncon, etc. are also supported.
Connection local and remote loopbacks are managed at the user interface of the FRP endpoint routing node or interface shelf. The existing IPX Frame Relay port loopback feature is supported on the IPX interface shelf. Remote loopbacks are not supported for DAX connections. A new command addlocrmtlp is added to support remote loopbacks at FRP DAX endpoints.
The tstcon command is supported at the FRP endpoints in a non-integrated fashion and is limited to a pass/fail loopback test. Fault isolation is not performed. This is the same limitation currently imposed on inter-domain connections. Intermediate endpoints at the AIT and BNI cards do not support the tstcon command. The tstdelay command is also supported for the FRP and ASI in a non-integrated fashion similar to that of the tstcon command.
The IPX interface shelf supports the termination of Frame Relay connection segments to an AIT. DAX voice and low speed data connections are also supported, but they can't terminate on an AIT. The IPX interface shelf connects to the routing network via an AIT card on the IPX and a BNI card on the Cisco BPX 8600 series broadband switch configured as a routing hub.
Admission control and ForeSight rate control for IPX interface shelf terminated Frame Relay connections is performed at the FRP port on the IPX interface shelf. Only a single trunk line is supported between the IPX interface shelf and the routing network. Trunks on the IPX interface shelf linking other nodes are not supported.
Frame Relay type connections, remotely or locally terminated are supported on IPX interface shelves. Interface shelf connections for which both endpoints reside on the same interface shelf are not known to the routing network and will not route through the routing network.
IPX interface shelves support the following network management features:
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 Cisco BPX 8600 series broadband switch configured as a 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 has been converted to an interface shelf, it can be joined to the Cisco BPX 8600 series broadband routing hub, by executing the addshelf command at the Cisco BPX 8600 series broadband routing hub. The addshelf command has the following syntax:
addshelf <trunk> <shelf_type>
trunk slot.port
shelf_type I (IPX/AF) or A (Cisco MGX 8220 edge concentrator)
delshelf <trunk> | <shelf_name> deletes interface shelf
dspnode: | Displays feeder trunk status. Cisco BPX 8600 series broadband switches configured as hub nodes display the status of all attached interface shelves. IPX interface shelves display a single status item, that of the attached Cisco BPX 8600 series broadband switch. |
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. |
dspalms | A new field, routing network Alarms, shows a count of major and minor alarms in the routing network. Feeder A-bit connection status reported by Feeder NNI is shown in the "Connection A-Bit Alarms" field. |
dspnode: | Shows if the routing network is reachable and the attached Cisco BPX 8600 series broadband hub node. |
Uses existing commands
Parameters entered at the Cisco WAN Manager workstation when adding connections.
Parameters entered at the Cisco WAN Manager workstation when adding connection. Bandwidth performance monitored by viewing selected statistics at the Cisco WAN Manager workstation.
Enabled and monitored via Cisco WAN Manager.
Interface shelf and feeder trunk information is reported to Cisco WAN Manager by the routing hub and interface shelf. Cisco WAN Manager can virtually connect to any node in the network via a TCP/IP connection. The Cisco WAN Manager Connection Manager is used to add, delete, and monitor voice and data connections for tiered networks with IGX 8400 series multiband switches configured as hubs. It is also used to add, delete and monitor frame relay connections for tiered networks with Cisco BPX 8600 series broadband switches. A sample of the Connection Manager GUI is shown in Figure 6-5.
Posted: Tue Jan 16 11:22:44 PST 2001
All contents are Copyright © 1992--2001 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.