Cisco BPX 8600 Series Reference Release 9.1 May 1998 Corporate Headquarters Cisco Systems, Inc. 170 West Tasman Drive San Jose, CA 95134-1706 USA http://www.cisco.
THE SPECIFICATIONS AND INFORMATION REGARDING THE PRODUCTS IN THIS MANUAL ARE SUBJECT TO CHANGE WITHOUT NOTICE. ALL STATEMENTS, INFORMATION, AND RECOMMENDATIONS IN THIS MANUAL ARE BELIEVED TO BE ACCURATE BUT ARE PRESENTED WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED. USERS MUST TAKE FULL RESPONSIBILITY FOR THEIR APPLICATION OF ANY PRODUCTS.
IN NO EVENT SHALL CISCO OR ITS SUPPLIERS BE LIABLE FOR ANY INDIRECT, SPECIAL, CONSEQUENTIAL, OR INCIDENTAL DAMAGES, INCLUDING, WITHOUT LIMITATION, LOST PROFITS OR LOSS OR DAMAGE TO DATA ARISING OUT OF THE USE OR INABILITY TO USE THIS MANUAL, EVEN IF CISCO OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
TABLE About This Manual Objectives Audience xxv xxv Organization Introduction xxv xxvi Related Documentation Chapter 1 CONTENTS xxv Cisco WAN Switching Product Name Change Conventions OF xxviii xxviii 1-1 General Description 1-1 BPX Capabilities 1-1 Extended Services Processor New with Release 9.1 BPX Switch 1-3 MGX 8220 1-3 IGX Switch 1-3 1-2 1-3 Continuing Features with Release 9.
Network Management 1-17 Network Interfaces 1-17 Service Interfaces 1-18 Statistical Alarms and Network Statistics Node Synchronization 1-18 1-18 Switch Software Description 1-19 Connections and Connection Routing 1-19 Connection Routing Groups 1-20 Cost-Based Connection Routing 1-21 Major Features of Cost-Based AutoRoute 1-21 Cost-Based AutoRoute Commands 1-23 Network Synchronization 1-23 Switch Availability 1-24 Node Redundancy 1-24 Node Alarms 1-24 Chapter 2 General Description 2-1 Physical Descrip
Front Panel Description 3-12 Line Module for the Alarm/Status Monitor Card 3-15 BPX Switch StrataBus 9.6 and 19.
ASI-155 Line Module, LM-2OC3-SMFLR ASI-155 Line Module, LM-2OC3-MMF 5-17 Y-Cabling of ASI Backcard, SMF-2-BC 5-17 BXM Cards, Access (UNI) Mode Chapter 6 5-17 BXM T3/E3, 155, and 622 Tag Switching 5-17 6-1 6-1 Dynamic Resource Partitioning for SPVCs BXM Cards 6-2 6-2 BXM Capabilities 6-5 Features 6-5 ATM Layer 6-6 Service Types 6-7 Card Operation 6-8 BXM Front Card Indicators 6-8 BXM, Backcard Connectors 6-12 Y-Cabling of SMF-622 Series Backcards 6-16 BXM Functional Description 6-17 Overview,
Statistics 6-28 Configuring Connections 6-29 Configuration Management 6-29 Command Line Interface Examples 6-31 Configuring the BPX Switch for SVCs Configuring the MGX 8220 6-40 6-40 Resource Partitioning 6-41 Tag Switching 6-41 Dynamic Resource Partitioning for SPVCs 6-41 Summary 6-41 ASI SVC Resource Partitioning 6-42 BXM SVC Resource Partitioning 6-44 NNI Trunk SVC Resource Partitioning 6-45 BNI Trunk SVC Resource Partitioning 6-46 BXM Trunk SVC Resource Partitioning 6-47 Chapter 7 ATM Connection
UBR Connection Policing Leaky Bucket 1 7-35 Leaky Bucket 2 7-35 7-35 Traffic Shaping for CBR, VBR, and UBR Configuration 7-37 Traffic Shaping Rates 7-38 LMI and ILMI Parameters Chapter 8 7-37 7-38 ATM and Frame Relay SVCs, and SPVCs 8-1 ATM and Frame Relay SVCs and SPVCs PVCs and SVCs 8-2 PVCs 8-2 SPVCs 8-2 SVCs 8-3 BPX Switch and ESP Interfaces 8-4 Interim Inter-switch Protocol Routing PNNI 8-4 Signaling Plane 8-5 UNI Signaling Channel NNI Signaling Channel 8-1 8-4 8-5 8-6 Network Interworking Be
Virtual Switch Interfaces 9-9 Tag Switching Resource Configuration Parameters Summary 9-11 Configuring VSI LCNS 9-12 Useful Default Allocations 9-13 Details of More Rigorous Allocations 9-14 Requirements 9-15 List of Terms 9-15 Related Documents 9-11 9-16 Configuration Management 9-16 Configuration Criteria 9-17 The cnfqbin Command 9-17 The cnfrsrc Command 9-17 Configuration Example 9-19 Checking and Troubleshooting 9-25 Provisioning and Managing Connections Statistics 9-29 9-29 Command Re
Standards 10-2 Multicasting Benefits 10-2 Multicasting Overview 10-2 BME Features: 10-2 BME Requirements 10-2 BME Restrictions 10-3 Address Criteria 10-3 Connection Management Criteria 10-3 Connection Management with Cisco StrataView Plus BME Operation 10-4 BME Cell Replication 10-4 Cell Replication Stats 10-5 Adding Connections 10-5 Multi-Segment Multicast Connections Multicast Statistics 10-6 Policing 10-7 10-3 10-6 Alarms 10-7 OAM cells 10-7 AIS cells 10-8 Hot Standby Backup Configuration 10-8
Chapter 12 Frame Relay to ATM Network and Service Interworking 12-1 Service Interworking 12-3 Networking Interworking ATM Protocol Stack 12-4 12-7 AIT/BTM Interworking and the ATM Protocol Stack AIT/BTM Control Mapping, Frames and Cells Management, OAM Cells 12-8 12-10 12-11 Functional Description 12-11 ATF Summary 12-11 Features 12-11 Limitations 12-11 Some ATF Connection Criteria 12-12 Connection Management 12-12 Port Management 12-12 Structure 12-13 Channel Statistics 12-13 OAM Cell Support 12
Testcon and Testdly 13-6 IPX Interface Shelf Description 13-6 Configuration and Management 13-7 Interface Shelf Management 13-7 Alarm Management of Interface Shelf on the BPX Hub Node Alarm Management on the IPX Interface Shelf 13-8 Port Management 13-8 Connection Management 13-8 Bandwidth Management 13-8 Statistics 13-8 IGX Routing Hubs in a Tiered Network 13-9 Tiered Network Implementation 13-10 General 13-11 Definitions 13-12 Upgrades 13-12 Co-locating Routing Hubs and Shelves 13-12 Network Management 13
Cisco WAN Switching Proprietary MIB Structure Switch Service Objects 14-6 Switch Connections 14-6 Bandwidth Class 14-7 Endpoint Statistics 14-7 Endpoint Mapping 14-7 Appendix A BPX Node Specifications General A-1 A-1 ATM Trunk Interface (BXM-T3/E3 Cards) A-3 ATM Trunk Interface (BXM-155 Cards) A-3 ATM Trunk Interface (BXM-622 Cards) A-5 ATM T3 Trunk Interface (BNI-T3, LM-3T3) A-6 ATM E3 Trunk Interface (BNI-E3, LM-3E3) A-7 ATM OC3 Trunk Interface (BNI-OC3, LM-OC3) ATM Service Interface (BXM-T
Control Port, Local Control C-1 Printer C-2 DIP Switch Settings for Okidata 184 C-2 Modems, Dial-In and Dial-Out C-4 Motorola V.
L I S T Figure 1-1 BPX Switch General Configuration Example 1-2 Figure 1-2 Frame Relay to ATM Network Interworking 1-8 Figure 1-3 Frame Relay to ATM Service Interworking Figure 1-4 Tiered Network with BPX Switch and IGX Switch Routing Hubs Figure 1-5 Virtual Trunking Example Figure 2-1 BPX Switch Exterior Front View 2-2 Figure 2-2 BPX Switch Exterior Rear View 2-3 Figure 2-3 DC Power Entry Module Shown with Conduit Box Removed Figure 2-4 AC Power Supply Assembly Front View Figure 2-5
Figure 4-9 Figure 4-10 xviii LM-2OC3-MMF Face Plate 4-18 Y-Cable (Model SMFY), LC-OC3-SMF (Model SMF-2-BC) Figure 5-1 BPX Switch Service Interface Group Figure 5-2 ASI-1 Simplified Block Diagram Figure 5-3 ATM Connection via ASI Ports Figure 5-4 ASI-1 Front Panel Figure 5-5 Line Module, ASI, 2T3 5-9 Figure 5-6 Line Module, ASI, 2E3 5-11 Figure 5-7 ASI-155 Simplified Block Diagram Figure 5-8 ASI-155 Front Panel Figure 6-1 A BPX Switch Network with BXM Cards Figure 6-2 BXM-622 Front
Figure 7-12 CBR.1 Connection with Bucket Compliant 7-25 Figure 7-13 CBR.1 Connection, with Bucket Discarding non-Compliant Cells Figure 7-14 VBR Connection, UPC Overview Figure 7-15 VBR Connection, Policing = 4, Leaky Bucket 1 Compliant Figure 7-16 VBR Connection, Policing = 4, Leaky Bucket 1 Non-Compliant Figure 7-17 VBR.2 Connection, Policing = 2, with Buckets 1 and 2 Compliant Figure 7-18 VBR.2 Connection, Leaky Bucket 2 Discarding CLP (0) Cells Figure 7-19 VBR.
xx Figure 10-5 Statistics Collection 10-7 Figure 10-6 OAM Cells Figure 10-7 Alarms Figure 11-1 Unlatching the Air Intake Grille Figure 11-2 Removing a Line Module Figure 11-3 DC Power Entry Module with Conduit Box Figure 11-4 AC Power Supply Assembly Figure 11-5 Removing Blank Filler Panel (B side shown) Figure 11-6 Card Slot and Fan Fuse Locations on System Backplane Figure 12-1 Frame Relay to ATM Network Interworking Figure 12-2 Frame Relay to ATM Service Interworking Figure 12-3
L I ST Table 1-1 Routing Group Configuration Example Table 2-1 Classes of Traffic and Associated AAL Layers Table 2-2 ATM Cell Addressing Modes Table 2-3 BPX Switch Plug-In Card Summary Table 3-1 BCC Front Panel Indicators Table 3-2 Backcard (Line Module) for BCC-32, Connectors Table 3-3 Back Card (Line Module) for BCC-3 & 4, Connectors Table 3-4 ASM Front Panel Controls and Indicators Table 3-5 LM-ASM Face Plate Connectors 3-15 Table 4-1 BNI Front Panel Status Indicators 4-6 Table 4-
xxii Table 7-6 VBR Policing Definitions 7-15 Table 7-7 UBR Policing Definitions 7-22 Table 7-8 Traffic Shaping Rates Table 7-9 ILMI Parameters Table 7-10 LMI Parameters 7-38 7-38 7-38 Table 9-1 BXM Port Groups 9-12 Table 9-2 Port Connection Allocations Table 9-3 Port Connection Allocations, Useful Default Values Table 9-4 cnfrsrc Parameter Summary Table 9-5 Port Connection Allocations, Useful Default Values Table 9-6 LCN Allocations for 8-port OC3 BXM, Ports Configured in Trunk Mo
Table C-1 Control Port Parameters for Local Control (pc or workstation) C-2 Table C-2 Auxiliary Port Parameters for OkiData 184 Printer Table C-3 Switch A Settings—Okidata 184 Printer C-2 Table C-4 Switch 1 Settings—Okidata 184 Printer C-3 Table C-5 Switch 2 Settings—Okidata 184 Printer C-3 Table C-6 Modem Interface Requirements Table C-7 V.34R Modem Configuration for Auto-Answer (Dial-in to BPX) Table C-8 V.34R Auto-Dial Configuration (dial-out to customer service)* Table C-9 V.
xxiv Cisco BPX 8600 Series Reference
About This Manual This publication provides an overview of the operation of the BPX 8600 Series wide-area switches which include the BPX 8620 switch and the BPX 8650 tag switch. Cisco documentation and additional literature are available in a CD-ROM package, which ships with your product. The Documentation CD-ROM, a member of the Cisco Connection Family, is updated monthly. Therefore, it might be more current than printed documentation.
Organization Organization This publication is organized as follows: Chapter 1 Introduction Describes the overall operation of the BPX 8600 Series wide-area switches and associated peripherals. Chapter 2 General Description Provides an overall physical and functional description of the BPX switch. The physical description includes the BPX enclosure, power, and cooling subsystems. The functional description includes an overview of BPX switch operation.
Organization Chapter 9 Tag Switching Provides a summary of tag switching on the BPX 8650 where the BPX switch and associated series 7200 or 7500 router comprise a BPX 8650 Tag Switch. Also provides configuration examples. Chapter 10 BME Multicasting Provides a description of BME multicasting and configuration examples. Chapter 11 Repair and Replacement Describes periodic maintenance procedures, troubleshooting procedures, and the replacement of major BPX switch components.
Related Documentation Related Documentation The following Cisco WAN Switching publications contain additional information related to the installation and operation of the BPX switch and associated equipment in a BPX, IGX, IPX network: • Cisco StrataView Plus Operations Guide provides procedures for using the Cisco StrataView Plus network management system. • • Cisco WAN Design Tools User Guide provides procedures for modeling networks. Release 9.
Conventions Note Means reader take note. Notes contain helpful suggestions or references to materials not contained in this manual. Means reader be careful. In this situation, you might do something that could result in equipment damage or loss of data. Caution Warning This warning symbol means danger. You are in a situation that could cause bodily injury.
Conventions xxx Cisco BPX 8600 Series Reference
CHAPTER 1 Introduction This chapter contains an overall description of the BPX 8600 Series. For installation information, refer to the Cisco BPX 8600 Series Installation and Configuration publication. Also, refer to the Cisco WAN Switching Command Reference publications. This chapter contains the following: • • • • • • • General Description New with Release 9.1 Continuing Features with Release 9.
General Description Figure 1-1 BPX Switch General Configuration Example IMA, 1-8 T1/E1 Lines WAN T3/E3 OC3/ OC12 Cisco StrataView Plus NMS WAN MGX 8220 MGX 8220 VNS DAS BPX 8620 Fr Rly, Voice, Data T3/E3 IPX switch FastPAD T3/E3 OC3/OC12 BPX 8620 WAN Virtual trunks (option) Fr Rly, Voice, Data T1/E1 T3/E3 T3/E3 ATM T3/E3 OC3/OC12 BPX 8650 Fr Rly, Voice, Data IGX switch LAN T3/E3/OC3 BPX 8620 T3/E3/OC3/OC12 (PVCs, SVCs) ATM Tag network CPE (ATM) Router T3/E3/OC3 MGX 8220 3810 F
New with Release 9.1 New with Release 9.1 BPX Switch • • • Tag Switching with the BXM • Extended Services Processor (ESP) Release 2.2 BME Multicasting Release 9.1 adds traffic shaping for BXM for UBR, VBR, and CBR per VC scheduling policies. This was previously supported for ABR only. — Support for SPVCs, including auto-grooming of SPVCs — Dynamic resource partitioning for migration of PVCs to SPVCs — Interworking with the LS1010 ATM switch to provide point-to-multipoint SVC connections.
Continuing Features with Release 9.1 • • SNMP Enhancements for connection management and monitoring • • Support for IGX switch hubs and associated interface shelves in tiered network • • Inverse Multiplexing ATM (IMA) • • • • • • Frame Relay to ATM Service interworking (Supported by FRSM on MGX 8220) • The BXM cards provide a range of trunk and service interfaces and support ATM Forum Standards UNI 3.1 and ATM Traffic Management 4.0 including ABR connections with VS/VD congestion control.
Continuing Features with Release 9.1 — de-route delay timer — connection routing groups by cell loading • ATM and Frame Relay SVCs, and Soft Permanent Virtual Circuits (SPVCs) with Extended Services Processor ESP is an adjunct processor that is co-located with a BPX switch shelf. The ESP provides the signaling and Private Network to Network Interface (PNNI) routing for ATM and Frame Relay SVCs via BXM cards in the BPX switch and AUSM and FRSM cards in the MGX 8220.
BPX Switch Operation • • Easy integration into existing IPX switch and IGX switch networks. • Collection of many ATM and other network statistics and transfer of the data collected to Cisco StrataView Plus over high-speed Ethernet LAN interface. • Integration with the Cisco StrataView Plus Network Management System to provide configuration, control, and maintenance. • Conformation to recommendations from all current ATM standards bodies: ATM Forum, ITU, ETSI, and ANSI.
BPX Switch Operation The BPX Switch with MGX 8220 Shelves Many network locations have increasing bandwidth requirements due to emerging applications. To meet these requirements, users can overlay their existing narrowband networks with a backbone of BPX switches to utilize the high-speed connectivity of the BPX switch operating at 19.2 Gbps with its T3/E3/OC3/OC12 network and service interfaces.
BPX Switch Operation • MGX 8220 frame relay to IGX switch or IPX switch frame relay (either routing node or shelf/feeder) Part B of Figure 1-2 shows a form of network interworking where the interworking function is performed by only one end of the ATM network, and the CPE connected to the other end of the network must itself perform the appropriate service specific convergence sublayer function.
BPX Switch Operation Service Interworking Figure 1-3 shows a typical example of Service Interworking. Service Interworking is supported by the FRSM on the MGX 8220 and the UFM-C and UFM-U on the IGX switch. Translation between the Frame Relay and ATM protocols is performed in accordance with RFC 1490 and RFC 1483.
BPX Switch Operation Routing Hubs and Interface Shelves In a tiered network, interface shelves at the access layer (edge) of the network are connected to routing nodes via feeder trunks (Figure 1-4). 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.
BPX Switch Operation BPX Switch Routing Hubs T1/E1 Frame Relay connections originating at IPX switch and IGX switch interface shelves and T1/E1 Frame Relay, T1/E1 ATM, CES, and FUNI connections originating at MGX 8220 interface shelves are routed across the routing network via their associated BPX switch routing hubs. The following requirements apply to BPX switch routing hubs and their associated interface shelves: • • • • Only one feeder trunk is supported between a routing hub and interface shelf.
BPX Switch Operation Figure 1-4 Tiered Network with BPX Switch and IGX Switch Routing Hubs Inverse Multiplexing ATM Where greater bandwidths are not needed, the Inverse Multiplexing ATM (IMA) feature provides a low cost trunk between two BPX switches. The IMA feature allows BPX switches to be connected to one another over any of the 8 T1 or E1 trunks provided by an AIMNM module on an MGX 8220 shelf. A BNI port on each BPX switch is directly connected to an AIMNM module in an MGX 8220 by a T3 or E3 trunk.
BPX Switch Operation Virtual Trunking Virtual trunking provides the ability to define multiple trunks within a single physical trunk port interface. Virtual trunking benefits include the following: • Reduced cost by configuring the virtual trunks supplied by the public carrier for as much bandwidth as needed instead of at full T3, E3, or OC3 bandwidths.
Traffic and Congestion Management Traffic and Congestion Management The BPX switch provides ATM standard traffic and congestion management per ATM Forum TM 4.0 using BXM cards.
Traffic and Congestion Management When cells are received from the network for transmission out a port, egress queues at that port provide additional buffering based on the service class of the connection. OptiClass OptiClass provides a simple but effective means of managing the quality of service defined for various types of traffic. It permits network operators to segregate traffic to provide more control over the way that network capacity is divided among users.
Traffic and Congestion Management PNNI The Private Network to Network Interface (PNNI) protocol provides a standards-based dynamic routing protocol for ATM and frame relay SVCs. PNNI is an ATM-Forum-defined interface and routing protocol which is responsive to changes in network resources, availability, and will scale to large networks. PNNI is available on the BPX switch when an ESP is installed.
Network Management ForeSight monitors each path in the forward direction to detect any point where congestion may occur and returns the information back to the entry to the network. When spare capacity exists with the network, ForeSight permits the extra bandwidth to be allocated to active virtual circuits. Each PVC is treated fairly by allocating the extra bandwidth based on each PVC's committed bandwidth parameter.
Network Management The design of the BPX switch permits it to support network interfaces up to 622 Mbps in the current release while providing the architecture to support higher broadband network interfaces as the need arises. Optional redundancy is on a one-to-one basis. The physical interface can operate either in a normal or looped clock mode. And as an option, the node synchronization can be obtained from the DS3 extracted clock for any selected network trunk.
Switch Software Description Since the BPX switch is designed to be part of a larger communications network, it is capable of synchronizing to higher-level network clocks as well as providing synchronization to lower-level devices. Any network access input can be configured to synchronize the node. Any external T1 or E1 input can also be configured to synchronize network timing. A clock output allows synchronizing an adjacent IPX or IGX switch or other network device to the BPX switch and the network.
Switch Software Description • Alternate Routing—the system software automatically reroutes a failed connection. The system software uses the following criteria when it establishes an automatic route for a connection: • • • Selects the most direct route between two nodes. Selects unloaded lines that can handle the increased traffic of additional connections.
Switch Software Description Table 1-1 Routing Group Configuration Example Routing group Connection cell loading 0 0-59 1 60-69 2 70-79 3 80-89 4 90-99 5 101-109 6 110-119 7 120-129 8 130-139 9 140 and up Cost-Based Connection Routing Release 9.1 includes a cost-based route selection method to Cisco StrataCom’s standard AutoRoute. This feature is referred to as cost-based AutoRoute.
Switch Software Description • Cache vs. On-Demand Routing–In previous releases Hop-Based Route Selection always requires on-demand routing. On-demand routing initiates an end-to-end route search for every connection. Due to the computation time required for Dijkstra’s algorithm in cost-based route selection, a route cache is used to reduce the need for on-demand routing. This cache contains lowest cost routes as they are selected.
Network Synchronization Cost-Based AutoRoute Commands The following switched software Command Line Interface (CLI) commands are used for cost-based route selection: • cnfcmparm - enables cost-based route selection. This is a super-user command used to configure all AutoRoute parameters. By default cost-based route selection is disabled. Enabling or disabling cost-based route selection can be done at any time. Each connection routing cycle uses whichever algorithm is enabled when the cycle begins.
Switch Availability Switch Availability Hardware and software components are designed to provide a switch availability in excess of 99.99%. Network availability will be impacted by link failure, which has a higher probability of occurrence, than equipment failure. Because of this, Cisco WAN network switches are designed so that connections are automatically rerouted around network trunk failures often before users detect a problem.
Switch Availability BPX switches are completely compatible with the network status and alarm display provided by the Cisco StrataView Plus NMS workstation. In addition to providing network management capabilities, it displays major and minor alarm status on its topology screen for all nodes in a network.
Switch Availability 1-26 Cisco BPX 8600 Series Reference
CHAPTER 2 General Description This chapter contains an overall physical and functional description of the BPX switch. The physical description includes the BPX switch enclosure, power, and cooling subsystems. The functional description includes an overview of BPX switch operation. This chapter contains the following: Physical Description Functional Description BPX Switch Major Groups Optional Peripherals Physical Description The BPX switch is supplied as a stand-alone assembly.
Physical Description Figure 2-1 BPX Switch Exterior Front View 17 3/4" 27" Slot #1 1 2 Slot #15 22 3/4" 3 4 5 6 7 8 9 10 11 12 13 14 15 Extractor handles Air intake H8018 19" 2-2 Cisco BPX 8600 Series Reference
Physical Description Figure 2-2 BPX Switch Exterior Rear View Fans Air Exhaust Slot #15 Back Cards Slot #1 LM– 3/T3 LM– 3/T3 15ASM LM– 3/T3 14 LM– 3/T3 13 LM– 3/T3 12 LM– 3/T3 11 LM– 3/T3 10 LM– 3/T3 9 LM– 3/T3 8BCC-B LM– 3/T3 7BCC-A LM– 3/T3 6 LM– 3/T3 5 LM– 3/T3 4 LM– 3/T3 3 LM– 3/T3 2 H8017 1 Node Cooling A fan assembly, with three six-inch 48 VDC fans is mounted on a tray at the rear of the BPX switch shelf (see Figure 2-2).
Physical Description Nodes may be equipped with either a single PEM or dual PEMs for redundancy. They are mounted at the back of the node below the backplane. A conduit hookup box or an insulated cover plate is provided for terminating conduit or wire at the DC power input. It is recommended that the source of DC for the node be redundant and separately fused.
Physical Description Figure 2-4 AC Power Supply Assembly Front View Indicator LEDS DC H8145 AC Card Shelf Configuration There are fifteen vertical slots in the front of the BPX switch enclosure to hold plug-in cards (see Figure 2-5). The middle two slots, slots number 7 and number 8, are used for the primary and secondary Broadband Controller Cards (BCC). The right-most slot, number 15, is used to hold the single Alarm/Status Monitor Card.
Physical Description Figure 2-5 BPX Switch Card Shelf Front View General purpose card slots 1 2 status port 3 status 1 2 3 port 4 status 1 2 3 port 5 status 1 BCC/ PRI 2 3 port status 1 2 3 port BCC-A 6 7 8 LAN LAN BCC-B status 1 2 3 port General purpose card slots BCC/ SEC 9 10 status 1 2 3 port 11 status 1 2 3 port 12 status 1 2 3 port 13 status 1 2 3 port ASM 14 15 status 1 2 3 port status 1 2 3 port ASM status 1 2 3
Functional Description Functional Description ATM ATM transmits broadband information using fixed length, relatively small, 53-byte cells which are suitable for carrying both constant rate data (e.g., voice and video) as well as bursty data. ATM evolved from the Broadband Integrated Services Digital Network (B-ISDN) standard, which in turn is an extension of ISDN. ISDN defines service and interfaces for public telecommunications networks.
Functional Description ATM Cell Format header y H81 Figure 2-7 ATM Cell Headers There are two basic header types defined by the standards committees, a UNI header and a NNI header; both are quite similar. Cisco has expanded on these header types to provide additional features beyond those proposed for basic ATM service. Usage of each of the various cell header types is described as follows: • The UNI header (see Figure 2-8) must be specified for each User-to-Network Interface.
Functional Description Figure 2-8 8 7 6 5 4 3 2 1 Byte 1 Flow control Virtual path identifier Byte 2 Virtual path identifier Virtual circuit identifier Byte 3 Virtual circuit identifier Byte 4 Virtual circuit identifier Byte 5 Byte 1 Byte 2 Byte 3 Byte 4 Byte 5 Cell loss priority H8147 Header Error Control (HEC) Figure 2-9 Bit — Payload type NNI Header 8 7 6 5 4 3 2 1 Virtual path identifier Virtual path identifier Virtual circuit identifier Virtual circuit identifier Vi
Functional Description Figure 2-10 STI Header STI Header 8 7 6 5 4 HCF CC 3 2 1 VPI VPI VCI VCI Payload class F R PTI CLP HCS HCF: Header Control Field, a 01 indicates an STI Cell VPI/VCI: Virtual Path/Virtual Channel Identifiers, same as UNI and NNI.
Functional Description In the STI header (see Figure 2-10), the Payload Class is used to indicate various classes of service and BPX switch queues, e.g., Opticlass, the enhanced class of service feature of the BPX switch. The ForeSight Forward Congestion Indication, the F bit, is used by ForeSight for congestion status. The Cell Loss Priority (CLP) bit follows the PTI bits in all header types. When set, it indicates that the cell is subject to discard if congestion is encountered in the network.
Functional Description Initially, four different adaptation layers (AAL1 through AAL4) were envisioned for the four classes of traffic. However, since AAL3 and AAL4 both could carry Class C as well as Class D traffic and since the differences between AAL3 and AAL4 were so slight, the two have been combined into one AAL3/4. AAL3/4 is quite complex and carries a considerable overhead.
Functional Description Figure 2-12). To allow the IPX switch or IGX switch to be used in mixed networks with other ATM switches, there are two other addressing modes available, Cloud Addressing Mode (CAM) and Simple Addressing Mode (SAM). BAM In the BPX switch Addressing Mode (BAM), used for all Cisco WAN switching networks, the system software determines VPI and VCI values for each connection that is added to the network.
Functional Description Table 2-2 ATM Cell Addressing Modes Addressing Mode Hdr. Type Derivation of VPI/VCI Where Used BAM-BPX switch Addressing Mode STI VPI/VCI = Node Derived Address Between IPX switch (or IGX switch) and BPX switches, or between IPX switch (or IGX switch) nodes. CAM— Cloud Addressing Mode UNI VPI = User Programmed VCI = Node Derived Address IPX switch to IPX switch (or IGX switch) connections over networks using ATM switches that switch on VPI only.
Functional Description Simple Gateway With the Simple Gateway protocol, the AIT card in the IPX switch (or BTM in the IGX switch) loads 24-byte FastPacket cells into ATM cells in ways that are consistent with each application. (Each of the two FastPacket cells loaded into the ATM Cell is loaded in its entirety, including the FastPacket header.) For example, two FastPackets can be loaded into one ATM cell provided they both have the same destination.
BPX Switch Major Groups BPX Switch Major Groups There are four major groups in the BPX switch. These are listed in Table 2-3. • • • • Common Core Network Interface Service Interface Power Supplies Table 2-3 lists these groups and their components along with a brief description of each. Table 2-3 BPX Switch Plug-In Card Summary Card Card Name Where Common Core Group BCC-32 Broadband Controller Card, operates with all versions of System Software Rel. 7.0 and above, and requires 32 Mbyte RAM for 8.
BPX Switch Major Groups Table 2-3 BPX Switch Plug-In Card Summary (Continued) Card Card Name Where BXM-622 OC-12 card with 1or 2 OC-12/STM-4ports. Card is configured for use in either network interface or service access (UNI) mode. Front BXM-622-2 BME Used for multicast connections. Used with SMF-622-2 backcard with port 1 looped to port 2, transmit to receive, and receive to transmit. SMF-622 Backcards for BXM-622.
Optional Peripherals Optional Peripherals At least one node in the network (or network domain if a structured network) must include a Strata-View Plus network management station (see Figure 2-14). A Y-cable may be used to connect the LAN ports on the primary and secondary BCC Line Modules, through an AUI to the LAN network, as only one BCC is active at a time. The serial Control port may be connected to a dial-in modem for remote service support or other dial-up network management access.
CHAPTER 3 BPX Switch Common Core This chapter contains a description of the common core group, comprising the Broadband Controller Cards (BCCs), the Alarm/Status Monitor (ASM) card, associated backcards, and the StrataBus backplane. This chapter contains the following: • • • • BPX Switch Common Core Group Broadband Controller Card (BCC-32, BCC-3, BCC-4) Alarm/Status Monitor Card BPX Switch StrataBus 9.6 and 19.
Broadband Controller Card (BCC-32, BCC-3, BCC-4) Broadband Controller Card (BCC-32, BCC-3, BCC-4) The Broadband Controller Card is a microprocessor-based system controller and is used to control the overall operation of the BPX switch. The controller card is a front card that is usually equipped as a redundant pair. Slots number 7 and number 8 are reserved for the primary and secondary (standby) broadband controller cards. Each broadband controller front card requires a corresponding back card.
Broadband Controller Card (BCC-32, BCC-3, BCC-4) The BCC-3 and BCC-32 are functionally equivalent and the BCC-4 is similar except for some additional features such as support of 19.6 Gbps operation. The term BCC is used in this manual to refer to the functional operation of the Broadband Controller Card. When a difference in operation does occur, the specific type of BCC is specified.
Broadband Controller Card (BCC-32, BCC-3, BCC-4) Functional Description The BPX switch is a space switch. It employs a crosspoint switch for individual data lines to and from each port. The switching fabric in each BPX switch consists of three elements for the BCC-32, BCC-3 and for the BCC-4 (see Figure 3-2 and Figure 3-3): • • Central Arbiter on each BCC. Crosspoint Switch. — 16 X 16 Crosspoint Switching Matrix on each BCC (12 X 12 used) for BCC-32 and BCC-3.
Broadband Controller Card (BCC-32, BCC-3, BCC-4) Figure 3-2 BCC-32 and BCC-3 Block Diagram I/O module 1 I/O module 2 I/O module 12 SIU SIU SIU TX data-1A SIU SIU RX data-2A TX data-12A Arbiter TX data-2A BCC-A Arbiter Xpoint switch RX data-1A RX data-12A Polling bus-A RX data-1B TX data-2B RX data-2B TX data-12B RX data-12B Xpoint switch TX data-1B BCC-A H8151 Polling bus-B BPX Switch Common Core 3-5
Broadband Controller Card (BCC-32, BCC-3, BCC-4) Figure 3-3 BCC-4 Block Diagram I/O module 1 I/O module 2 I/O module 12 DRSIU DRSIU DRSIU TX data-1A SIU SIU RX data-2A TX data-12A Arbiter TX data-2A BCC-A Arbiter S 16 x 32 Xpoint switch RX data-1A RX data-12A s6392 Polling bus-A RX data-1B TX data-2B RX data-2B TX data-12B BCC-A RX data-12B Front Panel Description The BCC front panel has four Led, three card status LEDs, and a LAN LED. (See Figure 3-4 and Table 3-1.
Broadband Controller Card (BCC-32, BCC-3, BCC-4) Figure 3-4 BCC Front Panel LAN LAN card act stby fail card act stby fail H8024 BC C BPX Switch Common Core 3-7
Broadband Controller Card (BCC-32, BCC-3, BCC-4) The BCC runs self-tests continuously on internal functions in the background and if a failure is detected, the fail LED is lighted. If the BCC is configured as a redundant pair, the off-line BCC is indicated by the lighted stby LED. The stby LED also flashes when a software download or standby update is in progress. The LAN LED indicates activity on the Ethernet port. 19.2 Gbps Operation with the BCC-4 In order to operate the BPX switch at 19.
Broadband Controller Card (BCC-32, BCC-3, BCC-4) backcards). The BCC-3 and the BCC-32 are functionally interchangeable, while the BCC-4 provides additional features such as support for 19.2 Mbps operation by the BXM cards. Both BCCs in a node should be of the same type. The backcard provides the following interfaces: • • • • An 802.3 AIU (Ethernet) interface for connecting the node to a StrataView Plus NMS. A serial RS-232 Control Port for connecting to a VT100-compatible terminal or modem.
Broadband Controller Card (BCC-32, BCC-3, BCC-4) Table 3-3 Back Card (Line Module) for BCC-3 & 4, Connectors BCC-3-C Connector BCC-3-C Function CONTROL A DB25 connector for a VT100 or equivalent terminal for a basic terminal connection using command line interface commands. Can also be connected to a dial-in modem for remote service support or other network management dial-up access. This is a bidirectional RS232 communications port.
Broadband Controller Card (BCC-32, BCC-3, BCC-4) Figure 3-5 BCC-3-bc or BCC-c Face Plate Connectors C O N T R O L A U X I L I A R Y X F E R T M G E X T T M G E X T T M G Control Port (DB25) C O N T R O L Auxiliary Port (DB25) A U X I L I A R Y L A N T1 or E1 External timing out (DB15) E X T External timing (E1, BNC) T M G E X T T1 or E1 External timing in (DB15) 1 T M G E X T L A N Ethernet for Cisco WAN Manager (DB15) 2 T M G C-3 BC C B C BC BCC15-BC BCC-3-BC Another function of
Alarm/Status Monitor Card the secondary Broadband Control Card becomes primary (active), then its LAN port becomes active. The SV+ workstation will automatically try to restore communications over the LAN and will interface with the newly active Broadband Controller Card. For small networks, one SV+ workstation is adequate to collect statistics and provide network management. For larger networks additional SV+ workstations may be required.
Alarm/Status Monitor Card Table 3-4 ASM Front Panel Controls and Indicators No Controls/ Indicator 1 alarms LEDs A red major alarm and a yellow minor alarm indicator to display the status of the local node. In general, a major alarm is service-affecting whereas a minor alarm is a non-service affecting failure. 2 dc LEDs Two green LEDs displaying the status of the two dc power busses on the Stratabus backplane. On–indicates voltage within tolerance. Off–indicates an out-of-tolerance voltage.
Alarm/Status Monitor Card Figure 3-6 ASM Front Panel Controls and Indicators statu s alarm s majo r DC o statu k A s alarm DC o mino r B s major k minor ACO A B ACO hist hist AC O ACO histo ry cle card ar act stby fail histo ry cle card ar act stby fail H8026 ASM 3-14 Cisco BPX 8600 Series Reference
Alarm/Status Monitor Card Line Module for the Alarm/Status Monitor Card The Line Module for the Alarm/Status Monitor Card (LM-ASM) is a back card to the ASM card. It provides a simple connector panel for interfacing to the customer alarm system. It is not required for system and ASM operation and must be installed in back slot number 15. Figure 3-7 illustrates the face plate of the LM-ASM which contains a single subminiature connector (see Table 3-5).
Alarm/Status Monitor Card Figure 3-7 LMI-ASM Face Plate A L A R M Alarm Relays (DB15) ASM 3-16 Cisco BPX 8600 Series Reference H8027 R E L A Y S
BPX Switch StrataBus 9.6 and 19.2 Gbps Backplanes BPX Switch StrataBus 9.6 and 19.2 Gbps Backplanes The BPX switch may be equipped with a backplane that supports either a 9.6 or 19.2 Gbps operation. The 19.2 Gbps backplane can physically be identified by the card slot fuses on the bottom rear of the backplane. Further information is provided in the Cisco BPX 8600 Series Reference.
BPX Switch StrataBus 9.6 and 19.
CHAPTER 4 Network Interface (Trunk) Cards This chapter contains a description of the BPX switch network interface (trunk) cards, including the Broadband Network Interface (BNI) and associated backcards. The BXM cards are briefly described in this chapter and covered in full in a later chapter.
Broadband Network Interface Cards (BNI-T3 and BNI-E3) Figure 4-1 EXT/INT clock BPX Switch Network Interface Group Alarm outputs NMS port Line moduleBCC Line moduleBCC Line moduleASM Broadband controller card primary Broadband controller card redundant Alarm/ status monitor StrataBus backplane Interface card BNI-155 Back card LM 3T3 or LM 3E3 Back card LM-2OC3-SMF, LM-2OC3-SMFLR, LM-2OC3-MMF, or BXM-622-SMF Interface card BXM-T3/E3 8 or 12 port or BXM-155 4 or 8 port Back card 8 or 12 port BPX
Broadband Network Interface Cards (BNI-T3 and BNI-E3) Features A summary of features for the BNI cards include: • BNI-T3 provides three broadband data ports operating at 44.736 Mbps. BNI-E3 provides three broadband data ports operating at 34.368 Mbps. • BNI T3 trunks can transmit up to 96,000 cells per second. BNI E3 trunks can transmit up to 80,000 cells per second. • BNI-T3 utilizes the Switched Megabit Data Service (SMDS) Physical Layer Convergence Protocol (PLCP).
Broadband Network Interface Cards (BNI-T3 and BNI-E3) Ingress In the receive direction (from the transmission facility towards the BPX switching matrix, sometimes referred to as ingress), the BNI performs the following functions: • Receives incoming ATM cells from the DS3 transmission facility, stripping the framing and overhead from the received bit stream. • Determines the address of the incoming cells by scanning the Virtual Path Identifier (VPI)/Virtual Circuit Identifier (VCI) in the cell header.
Broadband Network Interface Cards (BNI-T3 and BNI-E3) Some of the functions performed by the PLPP in the BNI-3T3 include: • PLPP— Receiver Side — Provides frame sync for either the M23 or C-bit parity frame format. — Provides alarm detection and accumulates B3ZS code violations, framing errors, parity errors, C-bit parity errors, and far end bit error (FEBE) events. — Detects far end alarm channel codes, yellow alarm, and loss of frame.
Broadband Network Interface Cards (BNI-T3 and BNI-E3) Loopbacks and Diagnostics There are two types of self-tests that may be performed. A non-disruptive self test is automatically performed on a routine basis. A more complete, disruptive test may be initiated manually when a card failure is suspected. If the card self-test detects a failure, the card status LEDs displays an indication of the failure type. Several loopback paths are provided.
Broadband Network Interface Cards (BNI-T3 and BNI-E3) Figure 4-3 BNI-3T3 Front Panel (BNI-3E3 appears the same except for name) statu s port 1 statu 2 s port 1 card 2 act stby fail card 2T3 H8028 ASI- act stby fail Network Interface (Trunk) Cards 4-7
T3 and E3 Line Modules (LM-3T3 and LM-3E3) Table 4-2 BNI Front Panel Card Failure Indications act stby fail Failure Description on off on Non-fatal error detected; card is still active. off on on Non-fatal error detected; card is in standby mode. off blinking on Fatal error detected; card is in a reboot mode. on on on Card failed boot load and operation is halted.
T3 and E3 Line Modules (LM-3T3 and LM-3E3) LM-3T3 Face Plate, Typical R X PO RT Port 1 RX TX 1 T X R X PO RT Port 2 RX TX 2 T X R X PO RT Port 3 RX TX 3 T X – LM3 3/T H8030 Figure 4-4 Network Interface (Trunk) Cards 4-9
T3 and E3 Line Modules (LM-3T3 and LM-3E3) Figure 4-5 LM-3E3 Face Plate, Typica R X PO RT Port 1 RX TX 1 T X R X PO RT Port 2 RX TX 2 T X R X PO RT Port 3 RX TX 3 – LM 3 3/E 4-10 Cisco BPX 8600 Series Reference H8031 T X
Broadband Network Interface Cards, BNI-155 Broadband Network Interface Cards, BNI-155 The BNI-155 interfaces the BPX switch with ATM OC3/STM-1 broadband trunks. The ATM trunk may connect to either another BPX switch or customer CPE equipped with an ATM OC3/STM-1 interface. There are three BNI-155 back cards, the LM-2OC3-SMF for single-mode fiber intermediate range, the LM-2OC3-SMFLR for single-mode fiber long range, and the LM-2OC3-MMF for multi-mode fiber.
Broadband Network Interface Cards, BNI-155 Functional Description In the egress direction, the BNI-155 has 2 Queue Service Engine (QSEs) which provide each of the ports with 12 programmable queues with selectable parameters such as minimum bandwidth, priority, and maximum bandwidth. The BNI queues are based on a class of service algorithm.
Broadband Network Interface Cards, BNI-155 The Line Interface Unit (LIU) performs the following egress functions: • • • • • Inserts the appropriate framing into the outgoing bit stream. Inserts any alarm codes for transmission to the far end. Provides optional cell scrambling, HEC generation, and idle cell insertion. Provides a small FIFO buffer outing cells. Provides electrical to optical conversion.
Broadband Network Interface Cards, BNI-155 Table 4-4 BNI-155 Front Panel Status Indicators Status LED color port off Trunk is inactive and not carrying data. green Trunk is actively carrying data. yellow Trunk is in remote alarm. card Status Description red Trunk is in local alarm. green (act) Card is on-line and one or more trunks on the card have been upped. If off, card may be operational but is not carrying traffic.
Broadband Network Interface Cards, BNI-155 BNI-155 Front Panel Figure 4-7 statu s port statu s 1 port 1 2 2 card act stby fail card act stby fail BNI- H8032 1 55 Network Interface (Trunk) Cards 4-15
OC3, Line Modules (SMF, SMFLR, & MMF) OC3, Line Modules (SMF, SMFLR, & MMF) The Line Modules for the OC3 BNI cards are back cards used to provide a physical interface to the transmission facility. There are three types, a single-mode fiber intermediate range, single-mode fiber long range, and a multi-mode fiber backcard. The Line Modules connect to the BNI through the StrataBus midplane.
OC3, Line Modules (SMF, SMFLR, & MMF) LM-2OC3-SMF Face Plate H8033 Figure 4-8 Network Interface (Trunk) Cards 4-17
OC3, Line Modules (SMF, SMFLR, & MMF) LM-2OC3-MMF Face Plate PORT 1 PORT 2 H8034 Figure 4-9 4-18 Cisco BPX 8600 Series Reference
Y-Cabling of BNI Backcard, SMF-2-BC Y-Cabling of BNI Backcard, SMF-2-BC The LM-OC3-SMF (Model SMF-2-BC) backcards may be Y-cabled for redundancy using the Y-Cable splitter shown in Figure 4-10. The cards must be configured for Y-Cable redundancy using the addyred command.
Y-Cabling of BNI Backcard, SMF-2-BC 4-20 Cisco BPX 8600 Series Reference
CHAPTER 5 Service Interface (Line) Cards This chapter contains a description of the BPX switch service interface (line) cards, including the ATM Service Interface (ASI) and associated backcards.The BXM cards are briefly described in this chapter and covered in full in a later chapter.
ASI-1, ATM Service Interface Card A BXM port may be configured to operate as either a trunk or UNI port. The BXM OC-12 back cards support Single Mode Fiber (SMF), Single Mode Fiber Long Reach (SMFLR), or Single Mode Fiber Extra Long Range (SMFXLR). The BXM OC-3 back cards support either Multi-Mode Fiber (MMF), Single Mode Fiber (SMF), or Single Mode Fiber Long Reach (SMFLR). For a further description of the BXM cards refer to Chapter 6, BXM T3/E3, 155, and 622.
ASI-1, ATM Service Interface Card Features A summary of features for the ASI card include: • • Two 45 Mb T3 ATM UNI/NNI ports per card for connection of user devices. • • • • • • Maximum of 1000 connections per card. Allows connections between UNI ports on a single node, between nodes, and NNI connections between networks. Aggregate transport rate of 96,000 cps per port (T3) or 80,000 cps (E3). VCC and/or VPC addressing. Ingress to ASI, each PVC is assigned a separate input queue.
ASI-1, ATM Service Interface Card Some of the functions performed by the PLPP in the ASI-1 include: PLPP—Receiver Side • Provides frame sync for the C-bit parity frame format. 1 Provides alarm detection and accumulates B3ZS code violations framing errors, parity errors, C-bit parity errors, and far end bit error (FEBE) events. • • Detects far end alarm channel codes, yellow alarm, and loss of frame. • Small receive FIFO buffer for incoming cells.
ASI-1, ATM Service Interface Card ATM Connection via ASI Ports alpha beta CPE BNI BNI BCC Crosspoint switch ATM T3 BNI ATM T3 (UNI) ASI-1 BPX BNI alpha 4.1.1.1 BPX ASI-1 Figure 5-3 ATM T3 (UNI) CPE BNI ATM T3 ATM T3 gamma 6.1.1.1 ATM T3 (UNI) CPE H8156 Crosspoint switch ASI-1 ATM T3 (UNI) ASI-1 CPE BNI BCC BPX gamma at alpha: addcon 4.1.1.1 gamma 6.1.1.1 [connection parameters…] Monitoring Statistics Port, line, and channel statistics are collected by the ASI-1.
ASI-1, ATM Service Interface Card Table 5-1 ASI-1 Status Indicators Status LED color Status Description port off Line is inactive and not carrying data. green Line is actively carrying data. yellow Line is in remote alarm. card red Line is in local alarm. green (act) Card is on-line and one or more ports on the card have been upped. If off, card may be operational but is not carrying traffic. yellow (stby) Card is off-line and in standby mode (for redundant card pairs).
ASI-1, ATM Service Interface Card Figure 5-4 ASI-1 Front Panel statu s port 1 statu 2 s port 1 card 2 act stby fail card 2T3 H8028 ASI- act stby fail Service Interface (Line) Cards 5-7
LM-2T3 Module LM-2T3 Module The T3 Line Module for the ASI-1 Front Card is a backcard used to provide a physical interface to the service interface (see Figure 5-5). The Line Module connects to the ASI-1 through the StrataBus midplane. Two adjacent cards of the same type can be made redundant by using a Y-cable at the port connectors. Except for using two ports instead of three, the LM-2T3 back card operates similarly to the BNI back cards, described previously.
LM-2T3 Module Line Module, ASI, 2T3 R X PO RT Port 1 RX TX 1 T X R X PO RT Port 2 RX TX 2 T X R X PO RT Port 3 RX TX 3 T X – LM3 3/T H8030 Figure 5-5 Service Interface (Line) Cards 5-9
LM-2E3 Module LM-2E3 Module The E3 Line Module for the ASI-1 Front Card is a backcard used to provide a physical interface to the service interface (see Figure 5-6). The Line Module connects to the ASI-1 through the StrataBus midplane. Two adjacent cards of the same type can be made redundant by using a Y-cable at the port connectors. Except for using two ports instead of three, the LM-2E3 back card operates similarly to the BNI back cards, described previously.
LM-2E3 Module Line Module, ASI, 2E3 R X PO RT Port 1 RX TX 1 T X R X PO RT Port 2 RX TX 2 T X R X PO RT Port 3 RX TX 3 T X – LM 3 3/E H8031 Figure 5-6 Service Interface (Line) Cards 5-11
ASI-155, ATM Service Interface Card ASI-155, ATM Service Interface Card The ATM Service Interface Card for OC3/STM-1, the ASI-155, is a BPX switch front card used to interface with an ATM user device e.g., CPE. The ASI provides an industry-standard ATM User-to-Network Interface (UNI) or ATM Network-to-Network Interface (NNI) over OC3 lines to the BPX switching fabric.
ASI-155, ATM Service Interface Card Configuring Connections Connections are routed between CPE connected to ASI ports. Before adding connections, an ASI line is upped with the upln command and configured with the cnfln command. Then the associated port is configured with the cnfport command and upped with the upport command. Following this, the ATM connections are added via the addcon command with the syntax: slot.port.vpi.vci. The slot number is the ASI card slot on the BPX switch.
ASI-155, ATM Service Interface Card • • • Provides optional cell descrambling, header error check (HEC), and idle cell filtering. Provides a small FIFO buffer for incoming cells. Provides optical to electrical conversion. The Line Interface Unit (LIU) performs the following egress functions: • • • • • Inserts the appropriate framing into the outgoing bit stream. Inserts any alarm codes for transmission to the far end. Provides optional cell scrambling, HEC generation, and idle cell insertion.
ASI-155, ATM Service Interface Card Table 5-2 ASI-155 Status Indicators Status LED color Status Description port off Line is inactive and not carrying data. green Line is actively carrying data. yellow Line is in remote alarm. card red Line is in local alarm. green (act) Card is on-line and one or more ports on the card have been upped. If off, card may be operational but is not carrying traffic. yellow (stby) Card is off-line and in standby mode (for redundant card pairs).
ASI-155, ATM Service Interface Card Figure 5-8 ASI-155 Front Panel POR T PO R STA T TU S 1 1 2 2 act stby fail STA TUS act stby fail ASI- H8035 1 55 5-16 Cisco BPX 8600 Series Reference
ASI-155 Line Module, LM-2OC3-SMF ASI-155 Line Module, LM-2OC3-SMF The LM- 2OC3 -SMF (Model SMF-2-BC) line module for the ASI-155 Front Card is a backcard that provides a SMF intermediate range service interface. The line module connects to the ASI-155 through the StrataBus midplane. Two adjacent cards of the same type can be made redundant by using a Y-cable at the port connectors. This is the same LM-2OC3-SMF backcard (Figure 4-8) that is used for the BNI-155.
BXM Cards, Access (UNI) Mode 5-18 Cisco BPX 8600 Series Reference
CHAPTER 6 BXM T3/E3, 155, and 622 This chapter describes the BXM card sets which include the BXM T3/E3, BXM-155, and BXM-622. The BXM cards may be configured for either trunk or service (port UNI) mode. In trunk mode they provide BPX network interfaces and in service (port UNI) mode they provide service access to CPE.
Dynamic Resource Partitioning for SPVCs Dynamic Resource Partitioning for SPVCs Also, for switch software Release 9.1, the BXM card supports dynamic resource partitioning to support the conversion of PVCs to soft permanent virtual circuits (SPVCs). This feature is described in the: Cisco WAN Service Node Extended Services Processor Installation and Operations for Release 2.2 document.
BXM Cards A BXM card set consists of a front and back card. The BXM T3/E3 is available with a universal BPX-T3/E3 backcard in 8 or 12 port versions. The BXM-OC3 is available with 4 or 8 port multi-mode fiber (MMF), single mode fiber (SMF), or single mode fiber long reach (SMFLR) back cards. The BXM-OC12 is available with 1 or 2 port SMF or SMFLR back cards, Any of the 12 general purpose slots can be used for the BXM cards. The same backcards are used whether the BXM ports are configured as trunks or lines.
BXM Cards Table 6-1 BXM T3/E3, BXM-155, and BXM 622 Front Card Options Front Card Model Number No. of Ports Cell Buffer (ingress/egress) Connections per card Back Cards T3/E3 (45 Mbps/34Mbps) BXM-T3-8 8 100k/130k 16k/32k BPX-T3/E3-BC BXM-E3-8 8 100k/130k 16k/32k BPX-T3/E3-BC BXM-T3-12 12 100k/230k 16k/32k BPX-T3/E3-BC BXM-E3-12 12 100k/230k 16k/32k BPX-T3/E3-BC OC3/STM-1 (155.
BXM Capabilities Table 6-2 BXM-T3/E3, BXM-155, and BXM-622 Back Cards Back Card Model Number No. of Ports Optical Range (less than or equal to) Description T3/E3 (45 Mbps/34 Mbps) BPX-T3/E3-BC 8/12 Universal T3/E3 backcard for 8 or 12 port card configurations n/a OC3/STM-1 (155.
BXM Capabilities • • • • ATM cell structure and format per ATM Forum UNI v3.1. • • • • UNI port option conforming to ATM Forum UNI v3.1 specification. • Provides up to 16 CoS’s with the following configurable parameters: Loopback support. 1:1 card redundancy using Y-cable configuration. A BXM card may be configured for either network or port (access) operation. ATM Layer ATM cell structure and format supported per ATM UNI v3.1 and ITU I.361.
BXM Capabilities Service Types The BXM cards support the full range of ATM service types per ATM Forum TM 4.0. CBR Service: • • Usage Parameter Control (UPC) and Admission Control. UPC: Ingress rate monitoring and discarding per I.371 for: — Peak Cell Rate (PCR). — Cell Transfer Delay Variation (CTDV). VBR Service: • • Usage Parameter Control (UPC) and Admission Control. UPC: Ingress rate monitoring and cell tagging per ITU-T I.371 for: — Sustained Cell Rate (SCR). — Peak Cell Rate (PCR).
Card Operation Virtual Interfaces • • • VPI/VCI used to identify virtual connection. Support for up to 32 virtual interfaces per card, each with 16 CoS queues. Virtual Interface parameters: — Physical port (trunk or access). — Peak Service Rate (PSR). — Minimum Service Rate (MSR). — Maximum resource allocation. Card Operation BXM Front Card Indicators The BXM front panel has a three-section, multi-colored “card” LED to indicate the card status.
Card Operation Figure 6-2 BXM-622 Front Panel, Two-Port Card Shown statu s port 1 2 status port 1 2 card act stby -622 card act stby fail H9890 BXM fail BXM T3/E3, 155, and 622 6-9
Card Operation Figure 6-3 BXM-155 Front Panel, Eight-Port Card Shown statu s port 1 4 2 3 5 6 status 7 port 1 4 7 2 3 5 6 8 8 card act stby BXM fail -155 card stby fail H9876 act 6-10 Cisco BPX 8600 Series Reference
Card Operation Figure 6-4 BXM-T3/E3 Front Panel, 12-Port Card Shown statu s port 1 4 2 3 5 6 8 9 status 7 port 1 4 7 10 2 3 5 6 8 10 11 1 2 9 11 12 card act stby fail BXM -T3/E 3-12 card stby fail H9885 act BXM T3/E3, 155, and 622 6-11
Card Operation BXM, Backcard Connectors The BXM backcards connect to the BXM front cards through the StrataBus midplane. The BXM-622 is available in one or two port versions in either a single-mode fiber intermediate range (SMF) or a single-mode fiber long range (SMFLR) backcard. Connector information is listed in Table 6-5 and a 2-port SMF card is shown in Figure 6-5. Table 6-5 BXM-622 Backcards No.
Card Operation SMF-622-2, SMFLR-622-2, and SMFXLR-622-2 Back Card SMF 622-2 H9891 Figure 6-5 BXM T3/E3, 155, and 622 6-13
Card Operation Figure 6-6 BXM-155-8 Port Backcard, MMF, SMF, or SMFLR RX 1 TX RX 2 TX RX 3 TX RX 4 TX RX 5 TX RX 6 TX RX 7 TX RX 8 SMF 155 -8 6-14 Cisco BPX 8600 Series Reference H9875 TX
Card Operation BPX-T3/E3 Back Card, 12-Port Option Shown RX1 TX1 RX2 TX2 RX3 TX3 RX4 TX4 RX5 TX5 RX6 TX6 RX7 TX7 RX8 TX8 RX9 TX9 RX10 TX10 RX11 TX11 RX12 TX12 BXM T3-12 H9883 Figure 6-7 BXM T3/E3, 155, and 622 6-15
Card Operation Y-Cabling of SMF-622 Series Backcards The SMF-622 series backcards may be Y-cabled for redundancy using the Y-Cable splitter shown in Figure 6-8. The cards must be configured for Y-Cable redundancy using the addyred command.
BXM Functional Description BXM Functional Description This functional description provides an overview of BXM operation. Overview, Port (UNI) Mode The following provides an overview of the operation of the BXM card when the ports are configured in port (access) mode for connection to customer equipment (CPE). Ingress The ingress flow of ATM cells into the BXM when the card is configured for port (access) operation is shown in Figure 6-9.
BXM Functional Description Figure 6-9 BXM Port (Access UNI) Ingress Operation 6-18 Cisco BPX 8600 Series Reference
BXM Functional Description Egress The egress flow of ATM cells out of the BXM when the card is configured for port (access) operation is shown in Figure 6-10.
BXM Functional Description Overview, Trunk Mode This provides an overview of the operation of the BXM when the card is configured in the trunk mode for connection to another node or network. Ingress The ingress flow of ATM cells into the BXM when the card is configured for trunk operation is shown in Figure 6-11.
BXM Functional Description Egress The egress flow of ATM cells out of the BXM when the card is configured for trunk operation is shown in Figure 6-12. ATM cells are routed to the BXM from the BPX crosspoint switch, applied to the DRSIU, then to an egress queue per class of service, and then served out to the SUNI (OC3/OC12) or Demux/Mux (T3/E3).
BXM Functional Description Detailed Description, Port (UNI) and Trunk Modes The following provides a summary of the principal functions performed by the major functional circuits of the BXM. DRSIU The DRSIU provides a total egress capacity from the BPX switch fabric of 1.6 Gbps. SONET/SDH UNI (SUNI) The SUNI ASIC implements the BXM physical processing for OC3 and OC12 interfaces. The SUNI provides SONET/SDH header processing, framing, ATM layer mapping and processing functions for OC12/STM-4 (622.
BXM Functional Description SABRE The Scheduling and ABR Engine (SABRE) includes both VS/VD and Foresight dynamic traffic transfer rate control and other functions: • ATM Forum Traffic Management 4.0 compliant ABR Virtual Source/Virtual Destination (VS/VD). • • • Terminates ABR flows for VS/VD and Foresight control loops. • • Supports OAM flows for internal loopback diagnostic self-tests and performance monitoring. Performs explicit rate (ER) and EFCI tagging if enabled.
Fault Management and Statistics Fault Management and Statistics Note This is a preliminary listing.
Fault Management and Statistics Fault Management and Statistics, Trunk Mode Compliant to Bellcore GR-253-CORE Alarms: • • • • • • • Loss Of Signal (LOS) Loss Of Pointer (LOP) Loss Of Frame (LOF) Loss Of Cell delineation (LOC) Alarm Indication Signal (AIS) Remote Defect Indication (RDI) Alarm Integration Up/down Count Performance Monitoring: • • • • • • • Performance monitoring provided for Line, Section and Path Bit Interleaved Parity (BIP) error detection Far End Block Error (FEBE) count Unavailable
Technical Specifications Technical Specifications Physical Layer • • Trunk or port (access) interface mode. Compliant to SONET standards. — *Bellcore GR-253-CORE, TR-TSY-000020 — *ANSI T1.105, T1E1.2/93-020RA • Compliant to SDH standards. — *ITU-T G.707, G.708 and G.709 — *ITU-T G.957, G.958 • • Table 6-8 1:1 BXM redundancy supported using ‘Y’ redundancy. Fiber optic interface characteristics are listed in Table 6-8 and Table 6-9.
General SONET Notes • • • • IEC 801-2, EN55022 Safety: EN 60950, UL 1950 Bellcore NEBS:Level 3 compliant Optical Safety: — Intermediate Reach IEC 825-1 (Class 1) — Long Reach IEC 825-1 (Class 36) General SONET Notes SONET is defined across three elements, section, line, and path as shown in Figure 6-13 and described in Table 6-10. An advantage of this tiered approach is that management control can be exercised at each level, for example at the section level independent of the line or path level.
User Commands User Commands This section provides a preliminary summary of configuration, provisioning, and monitoring commands associated with the BXM cards. These commands apply to initial card configuration, line and trunk configuration and provisioning, and connection configuration and provisioning.
Configuring Connections — clrslotalm-clear slot alarm — dspsloterrs-display slot errors • Statistical Trunk/Line Alarms — cnflnalm-configure line alarm threshold — dsplnerrs-display line errors — dsplnalmcnf- display line alarm configuration — clrlnalm-clear line alarm Configuring Connections Connections are typically provisioned and configured using Cisco StrataView Plus. However, the connections can also be added using the BPX switch command line interface (CLI).
Configuring Connections Field Value Description local/remote_addr slot.port.vpi.vci card slot, port, and desired VCC or VPI connection identifier node slave end of connection traffic_type type of traffic, chosen from CBR, VBR, ABR, and UBR extended parameters parameters associated with each connection type Note The range of VPIs and VCIs reserved for PVC traffic and SVC traffic is configurable using the cnfport command.
Command Line Interface Examples Command Line Interface Examples The following pages have a number of command examples, including configuring BXM lines and trunks and adding connections terminating on BXM cards. An example of the uptrk command for trunk 1 on a BXM in slot 4 of a BPX switch follows: pubsbpx1 TRK 1.1 1.3 4.1 TN Type T3 T3 OC3 SuperUser Current Clear Clear Clear - BPX 15 Line Alarm Status OK OK OK 9.1 Jan. 11 1998 18:52 GMT Other End pubsaxi1(AXIS) pubsipx1/8 - Last Command: uptrk 4.
Command Line Interface Examples An example of the cnftrk command for trunk 4.1 of a BXM card follows: pubsbpx1 TN SuperUser BPX 15 TRK 4.1 Config OC3 [353207cps] Transmit Rate: 353208 Subrate interface: -Subrate data rate: -Line DS-0 map: -Pass sync: Yes Loop clock: No Statistical Reserve: 1000 cps Idle code: 7F hex Max Channels/Port: 256 Connection Channels: 256 Valid Traffic Classes: V,TS,NTS,FR,FST,CBR,VBR,ABR SVC Channels: -SVC Bandwidth: -cps 9.1 Jan.
Command Line Interface Examples An example of the upln command for UNI port access on a BXM card follows: pubsbpx1 Line 3.1 3.2 3.3 5.1 5.2 TN Type OC3 OC3 OC3 T3 T3 YourID:1 Current Clear Clear Clear Clear Clear - BPX 15 9.1 Jan. 11 1998 02:18 GMT Line Alarm Status OK OK OK OK OK Last Command: upln 3.3 Next Command: The initial command to up a trunk (uptrk) or to up a line (upln) on the BXM card configures all the ports of the card to be either trunks or lines (UNI port access).
Command Line Interface Examples An example of the cnfport command for port 3 of a BXM card in slot 3 follows: pubsbpx1 TN YourID:1 BPX 15 9.1 Port: 3.3 Interface: Type: Speed: Shift: VBR Queue Depth: [INACTIVE] LM-BXM UNI %Util Use: 353208 (cps) SHIFT ON HCF (Normal Operation) 5000 Protocol: SVC Channels: SVC VPI Min: SVC VPI Max: SVC Bandwidth: NONE Jan. 11 1998 02:25 GMT Disabled 0 0 0 0 (c/s) This Command: cnfport 3.
Command Line Interface Examples An example of the upport command follows: pubsbpx1 TN YourID:1 BPX 15 9.1 Port: 3.3 Interface: Type: Speed: Shift: VBR Queue Depth: [ACTIVE ] LM-BXM UNI %Util Use: 353208 (cps) SHIFT ON HCF (Normal Operation) 5000 Protocol: SVC Channels: SVC VPI Min: SVC VPI Max: SVC Bandwidth: NONE Jan. 11 1998 02:28 GMT Disabled 0 0 0 0 (c/s) Last Command: upport 3.3 Next Command: An example of the cnfcls command for class 1 follows: pubsbpx1 TN YourID:1 BPX 15 9.1 Jan.
Command Line Interface Examples An example of the cnfcls command for class 2 follows: pubsbpx1 TN YourID:1 BPX 15 9.1 Jan. 11 1998 02:33 GMT ATM Connection Classes Class: 2 PCR(0+1) 1000/1000 Type: VBR % Util 100/100 MBS 1000/1000 CDVT(0+1) 10000/10000 AAL5 FBTC n SCR 1000/1000 Policing 3 Description: "Default VBR 1000 " This Command: cnfcls 2 Enter class type (VBR, CBR, UBR, ABR, ATFR): An example of the addcon command for a VBR connection 3.1.105.
Command Line Interface Examples An example of the cnfcon command for a VBR connection 3.1.105.55 follows. pubsbpx1 TN YourID:1 Conn: 3.1.105.55 Description: PCR(0+1) 50/50 pubsbpx1 % Util 100/100 MBS 1000/1000 BPX 15 9.1 Jan. 11 1998 02:41 GMT 3.2.205.65 CDVT(0+1) 250000/250000 vbr AAL5 FBTC n SCR 50/50 Policing 3 This Command: cnfcon 3.1.105.55 PCR(0+1) [50/50]: An example of the addcon command for an ABR connection follows.
Command Line Interface Examples An example of the cnfcon command for an ABR connection follows: pubsbpx1 TN YourID:1 Conn: 3.1.104.54 Description: PCR(0+1) 100/100 FCES n pubsbpx1 % Util 95/95 SCR 70/70 ADTF 1000 Trm 100 9.1 Jan. 11 1998 01:10 GMT 3.2.204.
Command Line Interface Examples An example of the dsplns command follows: pubsbpx1 Line 3.1 3.2 3.3 3.4 5.1 5.2 TN Type OC3 OC3 OC3 OC3 T3 T3 YourID Current Clear Clear Clear Clear Clear Clear - BPX 15 9.1 Feb.
Configuring the BPX Switch for SVCs Configuring the BPX Switch for SVCs During the configuration of BPX switch interfaces, you must make sure that the BPX switch IP address, SNMP parameters, and Network IP address are set consistent with your local area network (Ethernet LAN). Use the following BPX switch commands to set these parameters: • cnflan—This is a Super User level command and must be used to configure the BPX switch BCC LAN port IP address and subnet mask.
Resource Partitioning Resource Partitioning Starting with switch software Release 8.4, resources on BPX switch UNI ports and NNI trunks can be divided between SVCs and PVCs. This is known as resource partitioning and is done through the Command Line Interface for the BPX switch and the MGX 8220. These resources for BXM, ASI, and BNI cards can be partitioned appropriately between SVCs or PVCs. Tag Switching Starting with switch software release 9.1, the BXM also supports tag switching.
Resource Partitioning ASI SVC Resource Partitioning A BPX switch ATM Service Interface (ASI) card which will support ATM SVCs will have to be added and upped like a standard PVC port. Before adding connections, an ASI line is upped with the upln command and configured with the cnfport command and upped with the upport command. Complete details on using the BPX switch command line interface and applicable commands are described in the Cisco WAN Switching Command Reference manuals.
Resource Partitioning Note The preceding example displays a screen with the Protocol parameter set to None. If Protocol had been set to LMI or ILMI, the LMI parameters would also appear on the screen. The SVC parameters that need to be configured will remain the same, however. Step 5 Configure the desired SVC Channels, SVC VPI Min, SVC VPI Max, and SVC Bandwidth as desired.
Resource Partitioning BXM SVC Resource Partitioning A BXM card used as a UNI port can be configured to support ATM SVCs. The BXM will have to be added and upped like a standard PVC port. The BXM port will have to upped as a line (upln) to function as a UNI port. Note The initial command to up a trunk (uptrk) or to up a line (upln) on the BXM configures all the physical ports on a BXM card to be either trunks or ports. They can not be inter-mixed.
Resource Partitioning Step 5 Configure the SVC Channels, SVC VPI Min, SVC VPI Max, and SVC Bandwidth as desired. Step 6 Next you need to configure the SVC Port Queue depth with the cnfportq command shown in the following example. Example: BXM cnfportq Command ins-bpx6 Port: Interface: Type: Speed: SVC CBR CBR CBR CBR VBR VBR VBR VBR Queue Queue Queue Queue Queue Queue Queue Queue Queue TN 13.1 SuperUser BPX 15 9.1 Sep.
Resource Partitioning BNI Trunk SVC Resource Partitioning When the BNI is used as a trunk in a BPX switch network, it will have to have its resources partitioned to support SVCs. Complete details on using the BPX switch command line interface and applicable commands are described in the Cisco BPX 8600 Series Reference and WAN Switching Command Reference manuals. These procedures will concentrate on those commands that are specific to SVC resource partitioning.
Resource Partitioning Example: BNI cnftrkparm Command swong135 VT SuperUser TRK 5.
Resource Partitioning Example: BXM cnftrk Command ins-bpx6 TN SuperUser BPX 15 TRK 3.1 Config OC3 [304301cps] Transmit Rate: 353208 Subrate data rate: -Line DS-0 map: -Statistical Reserve: 1000 cps Idle code: 7F hex Max Channels/Port: 256 Connection Channels: 256 Traffic: V,TS,NTS,FR,FST,CBR,VBR,ABR SVC Vpi Min: 0 SVC Channels: 2000 SVC Bandwidth: 300000 cps Restrict CC traffic: No Link type: Terrestrial Routing Cost: 10 9.1 Sep.
CHAPTER 7 ATM Connections This chapter describes how ATM connection services are established by adding ATM connections between ATM service interface ports in the network using ATM standard UNI 3.1 and Traffic Management 4.0.
SVCs Figure 7-1 ATM Connections over a BPX Switch Network .
Traffic Management Overview Traffic Management Overview The ATM Forum Traffic Management 4.
Traffic Management Overview Standard ABR notes: Standard ABR uses RM (Resource Management) cells to carry feedback information back to the connection’s source from the connection’s destination. ABR sources periodically interleave RM cells into the data they are transmitting. These RM cells are called forward RM cells because they travel in the same direction as the data. At the destination these cells are turned around and sent back to the source as Backward RM cells.
ATM Connection Requirements Figure 7-2 ABR VSVD Flow Control Diagram Forward flow data cells Node Node Node NE NE NE Source Destination Forward RM cells RM cell control loop for forward flow data Backward RM cells NE = Network element S6156 Only the flows for forward data cells and their associated RM cell control loop are shown in this diagram.
ATM Connection Requirements When adding ATM connections, first the access port and access service lines connecting to the customer CPE need to be configured. Also, the trunks across the network need to configured appropriately for the type of connection. Following that the addcon command may be used to add a connection, first specifying the service type and then the appropriate parameters for the connection.
ATM Connection Configuration ATM Connection Configuration The following figures and tables describe the parameters used to configure ATM connections: • Table 7-2, Traffic Policing Definitions. — This table describes the policing options that may be selected for ATM connection types: CBR, UBR, and VBR. The policing options for ABR are the same as for VBR. • Table 7-3, Connection Parameters with Default Settings and Ranges — This table specifies the ATM connection parameter ranges and defaults.
ATM Connection Configuration Table 7-2 Traffic Policing Definitions Connection Type ATM Forum TM spec. 4.0 conformance definition PCR Flow (1st leaky bucket) CLP tagging (for PCR flow) SCR Flow (2nd leaky bucket) CLP tagging (for SCR flow) CBR CBR.1 CLP(0+1) no off n/a when policing set to 4 (PCR Policing only) CBR When policing set to 5 (off) off n/a off n/a UBR UBR.
ATM Connection Configuration Table 7-3 Connection Parameters with Default Settings and Ranges PARAMETER WITH [DEFAULT SETTING] BXM T3/E3, OC3 & OC12 RANGE ASI T3/E3 RANGE ASI-155 RANGE PCR(0+1)[50/50] 50- T3/E3 cells/sec T3: MCR – 96000 OC3 (STM1): 0 – 353200 50 - OC3 E3: MCR – 80000 50 - OC12 Limited to MCR – 5333 cells/sec for ATFR connections.
ATM Connection Configuration Table 7-3 Connection Parameters with Default Settings and Ranges (Continued) PARAMETER WITH [DEFAULT SETTING] BXM T3/E3, OC3 & OC12 RANGE ASI T3/E3 RANGE ASI-155 RANGE ICR: MCR - PCR cells/sec MCR - PCR cells/sec N/A ADTF[1000] 62 - 8000 msec 1000 – 255000 msecs. N/A Trm[100] ABRSTD: 1 - 100 msec 20 – 250 msecs.
ATM Connection Configuration Table 7-4 Connection Parameter Descriptions Parameter Description PCR Peak cell rate: The cell rate which the source may never exceed %Util % Utilization; bandwidth allocation for: VBR, CBR, UBR it’s PCR*%Util, for ABR it’s MCR*%Util MCR Minimum Cell Rate: A minimum cell rate committed for delivery by network CDVT Cell Delay Variation Tolerance: Controls time scale over which the PCR is policed FBTC (AAL5 Frame Basic Traffic Control) To enable the possibility of di
ATM Connection Configuration Table 7-4 Connection Parameter Descriptions (Continued) Parameter Description Nrm (ATM Forum TM 4.0 term), BXM only. Nrm FRTT (ATM Forum TM 4.0 term), Fixed Round Trip Time: the sum of the fixed and propagation delays from the source to a destination and back BXM only. Maximum number of cells a source may send for each forward RM cell, i.e. an RM cell must be sent for every Nrm-1 data cells TBE (ATM Forum TM 4.0 term), BXM only.
ATM Connection Configuration CBR Connections The CBR (constant bit rate) category is a fixed bandwidth class. CBR traffic is more time dependent, less tolerant of delay, and generally more deterministic in bandwidth requirements. CBR is used by connections that require a specific amount of bandwidth to be available continuously throughout the duration of a connection. Voice, circuit emulation, and high-resolution video are typical examples of traffic utilizing this type of connection.
ATM Connection Configuration VBR and ATFR Connections VBR Connections VBR (variable bit rate) connections may be classified as rt-VBR or nrt-VBR connections. The rt-VBR (real-time variable bit rate) category is used for connections that transmit at a rate varying with time and that can be described as bursty, often requiring large amounts of bandwidth when active. The rt-VBR class is intended for applications that require tightly constrained delay and delay variation.
ATM Connection Configuration Table 7-6 VBR Policing Definitions ATM Forum TM spec. 4.0 conformance definition PCR Flow (1st leaky bucket) CLP tagging (for PCR flow) SCR Flow (2nd leaky bucket) CLP tagging (for SCR flow) VBR, ABR, ATFR, ATFST VBR.1 CLP(0+1) no CLP(0+1) no VBR, ABR, ATFR, ATFST VBR.2 CLP(0+1) no CLP(0) no VBR, ABR, ATFR, ATFST VBR.
ATM Connection Configuration Figure 7-5 ATFR Connection Prompt Sequence ATFR PCR(0+1) %Util CDVT(0+1) SCR MBS Policing (1, 2, 3, 4, or 5) VC QDepth EFCI IBS 1 2 For policing prompt: 1 = VBR.1 2 = VBR.2 3 = VBR.3 4 = PCR policing only 5 = policing off 2 VC QDepth maps to VC Queue Max for frame relay EFCI maps to ECN for frame relay IBS maps to Cmax for frame relay Note: FBTC (Frame based traffic control - AAL5, same as FGCRA) is automatically set to yes.
ATM Connection Configuration ABR Notes The term ABR is used to specify one of the following: • ABR standard without VSVD (This is ABR standard without congestion flow control.) — Supported by BXM, ASI-T3 (& ASI-E3), and ASI OC3 cards. • ABR standard with VSVD. (This is ABR standard with congestion flow control as specified by the ATM Traffic Management, Version 4.0) — Also, referred to as ABR.1 — Supported only by BXM cards — Feature must be ordered.
ATM Connection Configuration Figure 7-6 ABR Standard Connection Prompt Sequence ABRSTD PCR(0+1) %Util MCR CDVT(0+1) FBTC (Frame based traffic control - AAL5, enable/disable) VSVD (enable/disable) Set policing = 4 ABR Standard without VSVD means without VSVD congestion flow control. • ABR Standard without VSVD is supported for BXM, ASI T3/E3, and ASI OC3. Trunk cell routing restrict (Y/N) [Y] 1 For policing prompt: 1 = VBR.1 2 = VBR.2 3 = VBR.
ATM Connection Configuration Figure 7-7 Meaning of VSVD and Flow Control External Segments ABR Standard 5 No VSVD ABR with ForeSight 1 No Yes 2 No Flow control external segment Yes Flow control external segment 3 Yes 4 VS and VD shown below are for traffic flowing in direction of arrow. For the other direction of traffic, VS and VD are in the opposite direction.
ATM Connection Configuration ATFST Connections The ABRFST connection uses the propriety ForeSight congestion control and is useful when configuring connections on which both ends do not terminate on BXM cards. The parameters for an ABRFST connection are shown in Figure 7-8 in the sequence in which they occur during the execution of the addcon command.
ATM Connection Configuration An ATFST connection is a frame relay to ATM connection that is configured as an ABR connection with ForeSight. ForeSight congestion control is automatically enabled when connection type ATFST is selected. A number of the ATM and frame relay connection parameters are mapped between each side of the connection. The parameters for an ATFST connection are shown in Figure 7-9 in the sequence in which they occur during the execution of the addcon command.
ATM Connection Configuration UBR Connections The unspecified bit rate (UBR) connection service is similar to the ABR connection service for bursty data. However, UBR traffic is delivered only when there is spare bandwidth in the network. This is enforced by setting the CLP bit on UBR traffic when it enters a port. Therefore, traffic is served out to the network only when no other traffic is waiting to be served first.
Traffic Policing Examples Traffic Policing Examples Traffic Policing, also known as Usage Parameter Control (UPC), is implemented using either an ATM Forum single or dual-leaky bucket algorithm. The buckets represent a GCRA (Generic Cell Rate Algorithm) defined by two parameters: • • Rate (where I, expected arrival interval is defined as 1/Rate) Deviation (L) If the cells are clumped too closely together, they are non-compliant and are tagged or discarded as applicable.
Traffic Policing Examples Figure 7-11 CBR Connection, UPC Overview CBR Traffic Verify VPIs, VCIs Multiple PVCs CPE Cells per sec. To UPC for each individual PVC For CBR connections, Leaky Bkt 1 ensures that the combined CLP=0 and CLP=1 cell traffic stays in PCR compliance within the CDVT limits. Leaky Bkt 1 admits compliant CLP cells to the network, and discards non-compliant CLP cells. Policing PCR Time Clumping (Cells arriving early, i.
Traffic Policing Examples Figure 7-12 shows a CBR.1 connection policing example, with policing set to 4, where the CDVT depth of the single leaky bucket is not exceeded, and all cells, CLP(0) and CLP(1) are admitted to the network. Figure 7-12 CBR.1 Connection with Bucket Compliant Connection setup and compliance status: CBR.
Traffic Policing Examples VBR Dual-Leaky Bucket Policing Examples The contract for a variable bit rate connection is set up based on an agreed upon sustained cell rate (SCR) with allowance for occasional data bursts at a Peak Cell Rate (PCR) as specified by maximum burst size MBS. When a connection is added, a VPI.VCI address is assigned, and UPC parameters are configured for the connection. For each cell in an ATM stream, the VPI.
Traffic Policing Examples Figure 7-14 VBR Connection, UPC Overview VBR Traffic Multiple PVCs CPE Cells per sec. Verify VPIs, VCIs To UPC for each individual PVC Policing For VBR connections, the first bucket polices PCR compliance within the CDVT(0+1) limits. The second bucket polices compliance in terms of sustained cell rate and data bursts within the BT + CDVT limits. PCR MBS= PCR x BT SCR Time Clumping (Cells arriving early, i.
Traffic Policing Examples Leaky Bucket 1 Leaky bucket 1 polices for the PCR compliance of all cells seeking admission to the network, both those with CLP = 0 and those with CLP =1. For example, cells seeking admission to the network with CLP set equal to 1 may have either encountered congestion along the user’s network or may have lower importance to the user and have been designated as eligible for discard in the case congestion is encountered.
Traffic Policing Examples Examples Figure 7-15 shows a VBR connection policing example, with policing set to 4, leaky bucket 1 compliant, and all cells being admitted to the network Figure 7-15 VBR Connection, Policing = 4, Leaky Bucket 1 Compliant .
Traffic Policing Examples Figure 7-16 shows a VBR connection policing example, with the policing set to 4, and leaky bucket 1 non-compliant which indicates that the connection has exceeded the PCR for a long enough interval to exceed the CDVT (0+1) limit. Non-compliant cells with respect to leaky bucket 1 are discarded.
Traffic Policing Examples Figure 7-17 shows a VBR.2 connection policing example, with policing = 2, and both buckets compliant. Leaky bucket two is policing the CLP(0) cell stream for conformance with maximum burst size MBS (as specified by BT), and for compliance with the SCR sustained cell rate. Figure 7-17 VBR.2 Connection, Policing = 2, with Buckets 1 and 2 Compliant Connection setup and compliance status: VBR.
Traffic Policing Examples Figure 7-18 shows a VBR.2 connection policing example, with policing set to 2, and leaky bucket 2 non-compliant. Leaky bucket 2 is shown policing the CLP(0) cell stream for conformance with maximum burst size MBS (as specified by BT), and for compliance with SCR (sustained cell rate). In this example (policing set to 2), CLP tagging is not enabled, so the cells that have exceeded the BT + CDVT limit are discarded.
Traffic Policing Examples Figure 7-19 shows a VBR.1 connection policing example, with policing set to 1, and both buckets compliant. Leaky bucket 1 is policing the CLP (0+1) cell stream for conformance with the PCR limit. Leaky bucket 2 is policing the CLP (0+1) cell stream for conformance CDVT plus maximum burst size MBS (as specified by BT), and for compliance with SCR sustained cell rate. Figure 7-19 VBR.
Traffic Policing Examples Figure 7-20 shows a VBR.3 connection policing example, with policing set to 3, and Leaky bucket 2 shown as non-compliant. Leaky bucket 2 is shown policing the CLP(0) cell stream for conformance with maximum burst size MBS (as specified by BT), and for compliance with SCR sustained cell rate. For the policing = 3 selection, CLP tagging is enabled, so the cells that have exceeded the BT + CDVT(0+1) limit are tagged as CLP=1 cells and admitted to the network.
Traffic Policing Examples ABR Connection Policing Available Bit Rate (ABR) connections are policed the same as the VBR connections, but in addition use either the ABR Standard with VSVD congestion flow control method or the ForeSight option to take advantage of unused bandwidth when it is available. UBR Connection Policing The contract for a unspecified bit rate connection is similar to the ABR connection service for bursty data.
Traffic Policing Examples Figure 7-21 UBR Connection, UPC Overview UBR Traffic To UPC for each individual PVC Verify VPIs, VCIs Multiple PVCs CPE For UBR connections, the first bucket polices PCR compliance within the CDVT(0+1) limits. The second bucket, used when CLP is set to Yes, tags all CLP(0) cells. Policing PCR Cells per sec. SCR=0 when CLP=Yes (UBR.2) Time Clumping (Cells arriving early, i.
Traffic Shaping for CBR, VBR, and UBR Traffic Shaping for CBR, VBR, and UBR With the introduction of traffic shaping for CBR, VBR, and UBR, the user has the option to provide traffic shaping for these connections types on the BXM. Previously, only ABR utilized traffic shaping. Traffic shaping involves passing CBR, VBR, or UBR traffic streams through VC queues for scheduled rate shaping. Traffic shaping is performed on a per port basis.
LMI and ILMI Parameters Traffic Shaping Rates Traffic shaping rates are listed in Table 7-8. Table 7-8 Traffic Shaping Rates Service Type MCR PCR CBR PCR PCR VBR SCR * %Util PCR UBR 0 PCR ABR MCR * %Util PCR LMI and ILMI Parameters The following is a listing of the LMI and ILMI parameters for the ASI and BXM: For ILMI information, refer to Table 7-9. Table 7-9 ILMI Parameters Parameter Description VPI.VCI VCCI for ILMI signaling channel equal 0.
CHAPTER 8 ATM and Frame Relay SVCs, and SPVCs This chapter provides a brief overview of switched virtual circuits and soft permanent virtual circuits with respect to the BPX switch and co-located Extended Services Processor. For additional information, refer to the Cisco WAN Service Node Extended Services Processor Installation and Operation Release 2.2 document.
ATM and Frame Relay SVCs and SPVCs The ESP provides the BPX switch with the ATM or Frame Relay signaling function. It interprets industry-standard signaling messages from ATM or Frame Relay CPE to provide the call setup and tear down for switched virtual circuits across the ATM network. In addition to SVC signaling, the ESP also performs PNNI routing, collects statistics, and processes alarms and billing records for SVC connections through the BPX switch.
ATM and Frame Relay SVCs and SPVCs Refer to the Cisco WAN Service Node Extended Services Processor Installation and Operation for Release 2.2 document for detailed information about SPVCs. SVCs A switched virtual circuit (SVC) only exists when there is data to send and a calling process has been initiated. With a switched virtual circuit, there must be some signaling mechanism to build a connection each time the user (ATM or Frame Relay device in this case) needs it.
BPX Switch and ESP Interfaces BPX Switch and ESP Interfaces The BPX switch supports the UNI and NNI interfaces for SVC operations as described in the following: • UNI, that is the User Network Interface, is the interface for either ATM or Frame Relay customer premise equipment (CPE) to the BPX switch. The UNI is defined as any interface between a user device and an ATM network (i.e., an ATM switch).
Signaling Plane Signaling Plane To support ATM and Frame Relay SVCs, the BPX switches essentially overlay a signaling network over a traditional (that is PVC-based) network. This signaling network, indicated by the dashed lines in Figure 8-2, connects all of the BPX switches with ESP and extends to the CPE. The signaling plane establishes and maintains SVCs between the CPE, that is, end users, across a Cisco StrataCom wide-area ATM network.
Signaling Plane Figure 8-3 UNI Signaling Channels WAN Service Node ESP ATM NIC Local VPI/VCI BXM Remote VPI/VCI AUSM ATM CPE (VPI 0, VCI 5) ASC BNM BXM Remote FRSM Frame Relay CPE DLCI = 0 MGX 8220 Remote VPI/VCI BXM/ ATM CPE (VPI 0, VCI 5) 10612 BPX 8620 User-to-Network Interface (UNI) NNI Signaling Channel There is also a signaling channel established between each adjacent pair of BPX switches. This NNI signaling channel shown in Figure 8-4 is configured for either IISP or PNNI protocol.
Network Interworking Between Frame Relay and ATM Figure 8-4 ESP Signaling PVC WAN Service Node ESP 1 WAN Service Node Network-to-Network Interface (NNI) ATM NIC ESP 2 ATM NIC Local VPI/VCI BXM BXM Trunk BPX switch 1 BNI Remote VPI/VCI BPX switch 2 S6363 BNI Network Interworking Between Frame Relay and ATM Because the BPX switch is an ATM switch, Frame Relay SVCs that are setup and established across the Cisco StrataCom network must be translated into an ATM format to be carried across the net
Extended Services Processor Extended Services Processor The Extended Services Processor (ESP) is an adjunct processor shelf integrated into the BPX switch. The basic ESP features include: • • • 140 MIPS CPU, with a 143Mhz clock 128 Megabytes of memory 4 Gigabyte hard disk Available in either AC- or DC-powered models (ESP-AC or ESP-DC), the ESP is an orderable option for the BPX switch. The ESP can be configured in both non-redundant and redundant configurations.
Extended Services Processor The ESP also provides the following application interfaces: • • SNMP to configure and monitor the ESP. • Telnet for accessing the ESP remotely, such as from the Cisco StrataView Plus Workstation. TFTP (trivial file transfer protocol) for uploading statistics, Call Detail Records (CDRs), and downloading configuration files and new software releases and revisions.
Extended Services Processor Figure 8-6 ESP Redundant Pair Ethernet ESP 2 ESP 1 ATM NIC Ethernet 10BaseT ATM NIC Ethernet A/B 10BaseT OC-3 A/B OC-3 SV+ ASC BXM LAN BXM BXM BNM BXM MGX 8220 10614 BPX 8620 WAN Service Node Y-Cable Redundancy The WAN Service Node provides another form of ESP redundancy protection through the use of Y-cables. With Y-cables, the ESP ATM NIC can be connected to two BXM cards or two BXM ports, as shown in Figure 8-7.
Network Management Other Redundancy Options Figure 8-7 illustrates only a single ESP-to-BXM redundancy option. There are four ESP-to-BXM redundancy options possible: 1 A single ESP with a Y-cable to redundant BXMs. 2 Two ESPs (a redundant pair), each attached to a single port on a single BXM. 3 Two ESPs (a redundant pair), each attached to a single port on two separate (redundant) BXMs. 4 Two ESPs (a redundant pair), each attached to different ports with Y-cables on two separate (redundant) BXMs.
Resource Partitioning MGX 8220 AUSM port resources to be partitioned are: • • LCN range VPI range MGX 8220 FRSM port resources to be partitioned are: • • LCN range DLCI range 8-12 Cisco BPX 8600 Series Reference
CHAPTER 9 Tag Switching This chapter contains an overview of tag switching and instructions for configuring the BPX 8650 for the tag switching feature: This chapter contains the following: • • • • • • • • • • • • • • • • • Introduction Tag Switching Benefits Tag Switching Overview Elements in a Tag Switching Network Tag Switching Operation at Layer 3 Tag Switching in an ATM WAN Tag Switching and the BPX 8650 Tag Switching Resource Configuration Parameters Requirements List of Terms Related Documents Con
Tag Switching Benefits Tag Switching Benefits For multi-service networks, tag switching enables the BPX switch to provide ATM, frame relay, and IP Internet service all on a single platform in a highly scalable way. Support of all these services on a common platform provides operational cost savings and simplifies provisioning for multi-service providers.
Elements in a Tag Switching Network Elements in a Tag Switching Network The basic elements in a tag switching network are tag edge routers, tag switches, and a tag distribution protocol as defined in the following: • Tag edge routers Tag edge routers are located at the boundaries of a network, performing value-added network layer services and applying tags to packets. These devices can be either routers, such as the Cisco 7500, or multilayer LAN switches, such as the Cisco Catalyst 5000.
Tag Switching in an ATM WAN Control The control component consists of tag allocation and maintenance procedures. The control component is responsible for creating tag bindings between a tag and IP routes, and then distributing these tag bindings to the tag switches. The tag distribution protocol (TDP) is a major part of the control component. TDP establishes peer sessions between tag switches and exchanges the tags needed by the forwarding function.
Tag Switching in an ATM WAN Figure 9-2 Tag Forwarding Information Base (TFIB) in an ATM Environment Control ATM-TSRs use the downstream-on-demand allocating mechanism. Each ATM-TSR maintains a forwarding information base (FIB) that contains a list of all IP routes that the ATM-TSR uses. This function is handled by the routing engine function which is either embedded in the switch or runs on an outside controller.
Tag Switching in an ATM WAN Figure 9-3 shows an example of conservative allocation. ATM edge TSR RTA is an IP routing peer to ATM-TSR RTB. In turn, ATM-TSR RTB is an IP routing peer to ATM-TSR-RTC. IP routing updates are exchanged over VPI/VCI 0/32 between RTA-RTB and RTB-RTC. For example: 1 RTA sends a tag binding request toward RTB in order to bind prefix 128.89.0.0/16 to a specific VCI. 2 RTB allocates VCI 40 and creates an entry in its TFIB with VCI 40 as the incoming tag.
Tag Switching and the BPX 8650 Tag Switching and the BPX 8650 With tag switching the router function can be accomplished by either integrating the routing engine into the switch or by using a separate routing controller (associated router). The BPX 8650 tag switch combines a BPX switch with a separate router controller (Cisco Series 7200 or 7500 router). This has the advantage of separating the various services (e.g.
Tag Switching and the BPX 8650 Figure 9-4 BPX Tag Switching 128.89.25.4 Data 128.89.25.4 Data Network BPX 8650 TS-C 60 BPX 8650 TS-A 60 40 40 7500 TER-U 70 70 BPX 8650 TS-B 7500 TER-S 50 50 128.72.30.9 Data CPE Fr Rly PVC ATM PVC BPX 8620 switch-F Note 1: Fr Rly PVC 12 12 BPX 8650 TS-H Label Switch Controller (7200 or 7500) Note 2: 128.72.30.
Tag Switching and the BPX 8650 Virtual Switch Interfaces Figure 9-5 shows how virtual switch interfaces are implemented by the BPX switch in order to facilitate tag switching. A virtual switch interface (VSI) provides a standard interface so that a resource in the BPX switch can be controlled by additional controllers other than the BPX controller card such as a tag switch controller.
Tag Switching and the BPX 8650 Figure 9-6 Connection Setup, End Points on same VSI Slave Master 1. Connection request 3. Confirmation sent to master Note: Both connection end points on same slave Figure 9-7 2. End points set up and enabled S6876 Slave Connection Setup, End Points on Different VSI Slaves Master 7. Confirmation sent to Master 1. Connection request Slave Slave 6. End point enabled at near end 9-10 Cisco BPX 8600 Series Reference 5. Confirmation sent to near end 4.
Tag Switching Resource Configuration Parameters Tag Switching Resource Configuration Parameters This section describes resource partitioning for tag switching. It includes the following: • • • • Summary Configuring VSI LCNS Useful Default Allocations Details of More Rigorous Allocations Summary Most tag switching configuration, including the provisioning of connections, is performed directly by the Tag Switch Controller.
Tag Switching Resource Configuration Parameters Configuring VSI LCNS In the first release of tag switching, each BXM card supports 16k connections in total, including PVCs, tag switching VSI connections, and connections used for internal signaling. On the BXM, the ports are grouped into port groups, and a certain number of connections is available to each port group. For example, an 8-port-OC3 BXM has two port groups, consisting of ports 1-4 and 5-8, respectively.
Tag Switching Resource Configuration Parameters Table 9-2 Port Connection Allocations Connection Type cnfrsrc cmd parameter Variable Description AutoRoute LCNs maxpvclcns a(x) Represents the number of AutoRoute (PVC) LCNs configured for a port. Minimum VSI LCNs for partition 1 minvsilcns n1(x) Represents the guaranteed minimum number of LCNs configured for the port VSI partition. This value is not necessarily always available.
Tag Switching Resource Configuration Parameters Details of More Rigorous Allocations More rigorous allocations are possible as may be desired when the default values are not applicable.
Requirements Requirements • BCC cards of one of the following versions: — BCC-3-64 — BCC-4-64 — BCC-4-128 • BPX switches require BXM cards to originate, terminate, or transfer tag switching connections. List of Terms The following terms are defined for a tag switching context only, not for general situations: ATM edge TSR—A tag switching router that is connected to the ATM-TSR cloud through TC-ATM interfaces. The ATM edge TSR adds tags to untagged packets and strips tags from tagged packets.
Related Documents Tag switch controller (TSC)—An IOS platform that runs the generic tag switching software and is capable of controlling the operation of an external ATM (or other type of) switch, making the interfaces of the latter appear externally as TC-ATM interfaces. tag switching router (TSR)—A Layer 3 router that forwards packets based on the value of a tag encapsulated in the packets.
Configuration Criteria Configuration Criteria Tag switching for VSIs on a BXM card is configured using the cnfrsrc and cnfqbin commands. Qbin 10 is assigned to tag switching. The cnfqbin Command The cnfqbin command is used to adjust the threshold for the traffic arriving in Qbin 10 of a given VSI interface as away of fine tuning traffic delay. If the cnfqbin command is used to set an existing Qbin to disabled, the egress of the connection traffic to the network is disabled.
Configuration Criteria A detailed description of the cnfrsrc parameters is provided later in this chapter in the Command Reference section under the heading cnfrsrc. A brief summary of the parameters and their use is provided in Table 9-4. Table 9-4 cnfrsrc Parameter Summary Parameter (cnfrsrc) Example Value Description slot.port 4.1 Specifies the slot and port number for the BXM maxpvclcns 256 The maximum number of LCNs allocated for AutoRoute PVCs for this port.
Configuration Example Configuration Example The following initial configuration example for a BPX tag switching router is with respect to a BXM OC3 card located in slot 4 of the BPX switch, a Tag Switch Controller (e.g., 7500 or 7200 series router) connected to BXM port 4.1, and with connections to two tag switching routers in the network at BXM ports 4.2 and 4.3, respectively, as shown in Figure 9-9. Whether a BXM card operates in trunk or port mode is determined by how the first port is brought up.
Configuration Example Step 4 Enter the dspcd command to check the port group max that can be entered for the maxvsilcn parameter of the cnfrsrc command. In this example, the maximum value for a port group is 7048.
Configuration Example Step 5 On the BXM in slot 4, bring up the ports 4.1, 4.2, and 4.3, as follows: Note The following example enables ports 4.1, 4.2, and 4.3 in trunk mode with the uptrk command, they could also all be upped in port mode using the upport command. This is because tag switching and the VSI make no distinction between a “port” and a “trunk”. uptrk 4.1 uptrk 4.2 uptrk 4.3 Sample Display: n4 TRK 2.1 3.1 5.1 5.2 5.3 6.1 6.2 4.
Configuration Example Sample Display: n4 TN SuperUser BPX 15 9.1 Apr. 4 1998 16:40 PST Port/Trunk : 4.1 Maximum PVC LCNS: 256 Maximum PVC Bandwidth:26000 Min Lcn(1) : 0 Min Lcn(2) : 0 Partition 1 Partition State : Minimum VSI LCNS: Maximum VSI LCNS: Start VSI VPI: End VSI VPI : Minimum VSI Bandwidth : Enabled 512 7048 2 15 26000 Maximum VSI Bandwidth : 100000 Last Command: cnfrsrc 4.
Configuration Example If the interfaces require other than a max PVC bandwidth of 10 Mbps or require other than a PVC LCN configuration of 256, adjust the configuration accordingly. Step 8 For this release, Class of Service buffer 10 is used for tag switching connections. Check the queue buffer 10 configurations for port 4.1 as follows: dspqbin 4.1 10 The qbin configuration should be as shown in the following example: VC connections are grouped into large buffers called qbins.
Configuration Example Sample Display: Sample Display: n4 TN SuperUser BPX 15 9.1 Apr. 4 1998 16:41 PST Qbin Database 4.1 on BXM qbin 10 Qbin State: Minimum Bandwith: Qbin Discard threshold: Low CLP/EPD threshold: High CLP/EPD threshold: EFCI threshold: Enabled 0 65536 95% 100% 40% Last Command: cnfqbin 4.1 10 e 0 65536 95 100 40 Next Command: Step 9 Configure the Qbin 10 for ports 4.2 and 4.3 by performing the procedures in the previous step, but entering port 4.2 and 4.3 where applicable.
Checking and Troubleshooting Checking and Troubleshooting Use the following procedure as a quick checkout of the tag switching configuration and operation with respect to the BPX switch. Step 1 Wait a while, and check whether the controller sees the interfaces correctly; on the TSC, enter the following command: tsc# show controllers VSI descriptor and the an example output is: Note Check the TSC on-line documentation for the most current information.
Checking and Troubleshooting Step 3 Check the trunk status with the following command: dsptrks The dsptrks screen should show 4.1, 4.2 and 4.3, with the “Other End” of 4.1 reading “VSI (VSI)”. A typical dsptrks screen example follows: Sample Display n4 TRK 2.1 3.1 5.1 5.2 5.3 6.1 6.2 4.1 4.2 4.3 TN Type OC3 E3 E3 E3 E3 T3 T3 OC3 OC3 OC3 SuperUser Current Clear Clear Clear Clear Clear Clear Clear Clear Clear Clear - BPX 15 9.1 Line Alarm Status OK OK OK OK OK OK OK OK OK OK Apr.
Checking and Troubleshooting Step 5 Enter the dsprsrc command as follows: dsprsrc 4.1 1 The resulting screen should show the settings shown in the following example: Sample Display: n4 TN SuperUser BPX 15 9.1 Apr. 4 1998 16:47 PST Port/Trunk : 4.
Checking and Troubleshooting Step 8 Try a ping on the tag switch connections. If the ping doesn't work, but all the tag switching and routing configuration looks correct, check that the TSC has found the VSI interfaces correctly by entering the following command at the TSC: tsc# show tag int Step 9 If the interfaces are not shown, re-check the configuration of port 4.1 on the BPX switch as described in the previous steps.
Provisioning and Managing Connections Provisioning and Managing Connections Instructions for configuration of the BPX switch including the setting of VSI partitions for tag switching are provided in this document. Adding (provisioning) and administering connections is performed from the Tag Switch Controller. For further information on the Tag Switch Controller, refer to: Tag Switching for the Cisco 7500/7200 Series Routers Statistics Statistics are monitored via the Tag Switch Controller.
Command Reference Command Reference This section provides a description of the BPX switch and TSC commands referenced in this chapter on tag switching. They are presented in the following order: BPX Switch Commands A summary of the following commands is provided in this section. For complete descriptions of user and superuser commands, refer to the Cisco WAN Switching Command Reference and the Cisco WAN Switching SuperUser Command Reference documents.
addshelf addshelf Adds an ATM link between a hub node and an interface shelf such as an MGX 8220, IPX shelf, or IGX shelf in a tiered network, or an ATM link between a BXM card on a BPX node and a tag switch controller such as a series 7200 or 7500 router. Syntax Tag switch controller: addshelf Interface shelf: addshelf Examples Tag switch controller: addshelf 4.1 vsi 1 1 Interface shelf: addshelf 12.
addshelf Description for Tag Switching For tag switching, before it can carry traffic, the link to a tag switch controller must be “upped” (using either uptrk or upport) at the BPX node. The link can then be “added” to the network (using addshelf). Also, the link must be free of major alarms before you can add it with the addshelf command.
addshelf Description for Interface Shelves An interface shelf can be one of the following: • • • An MGX 8220 connected to a BPX node An IPX or IGX node connected to a BPX node that serves as a hub for the IPX/AF or IGX/AF. An IGX node connected to an IGX routing node that serves as a hub for the IGX/AF The signaling protocol that applies to the trunk on an interface shelf is Annex G. Each IPX/AF, IGX/AF, or MGX 8220 has one trunk that connects to the BPX or IGX node serving as an access hub.
cnfqbin cnfqbin Tag switched VC connections are grouped into large buffers called Qbins. This command configures the Qbins. For the EFT release of tag switching, Qbin 10 is used for tagged switch connections. Syntax cnfqbin Example cnfqbin 13.4 10 E 0 65536 6095 80100 40 Attributes Privilege Jobs Log Node Lock BPX switch Related Commands dspqbin Parameters-cnfqbin Parameter Description slot.port slot.
cnfqbin Description The following example shows the configuration of a BXM Qbin on port 4.1 for tag switching Example Configure a Qbin by enabling it and accepting the defaults for the other parameters: cnfqbin 4.1 10 e 0 65536 95 100 40 Sample Display: n4 TN SuperUser BPX 15 9.1 Apr. 4 1998 16:40 PST Qbin Database 4.
cnfrsrc cnfrsrc This command configures resources among AutoRoute PVCs and VSI partitions. Syntax cnfrsrc slot.port maxpvclcns maxpvcbw partition e/d minvsilcns maxvsilcns vsistartvpi vsiendvpi vsiminbw vsimaxbw Example cnfrsrc 4.1 256 26000 1 e 512 7048 2 15 26000 100000 Attributes Privilege Jobs Log Node Lock BPX switch Related Commands Parameters-cnfrsrc Parameter (cnfrsrc) Description slot.
cnfrsrc Parameter (cnfrsrc) Description minvsilcns The minimum number of LCNs guaranteed for this partition. The VSI controller guarantees at least this many connection endpoints in the partition, provided that there are sufficient free LCNs in the common pool to satisfy the request at the time the partition is added. When a new partition is added or the value is increased, it may be that existing connections have depleted the common pool so that there are not enough free LCNs to satisfy the request.
cnfrsrc Description The following paragraphs describe various configurations of BXM port resources for tag switching. The first allocation example is using default allocations. The second allocation example describes more rigorous allocations where default allocations are not applicable. Useful Default Allocations Reasonable default values for all ports on all cards are listed in Table 9-5. If these values are not applicable, then other values may be configured using the cnfrsrc command.
cnfrsrc Details of More Rigorous Allocations More rigorous allocations are possible when default values are not applicable.
cnfrsrc When a port partition has exhausted its configured guaranteed LCNs (min LCNs), it may draw LCNs for new connections on a FIFO basis from the unallocated LCNs, “z1”, until its maximum number of LCNs, “m1(x)”, is reached or the pool, “z1”, is exhausted. No limit is actually placed on what may be configured for “m1 (x)”, although “ m1 (x)” is effectively ignored if larger than “z1 + n1”.
cnfrsrc The values shown in Table 9-6 for the port group containing ports 1-4 may be summarized as follows: — Port 1 is guaranteed to be able to support 120 AutoRoute connections (PVCs) and 3000 tag VCs (TVCs). It will not support more than 120 PVCs. It may be able to support up to 3500 TVCs, subject to availability of unallocated LCNs “z1” on a FIFO basis. Since “m1 (1)” of 3500 is less than “z1“ of 3827, the most TVCs that can be supported are 3500. — Port 2 will support up to 50 PVCs, and no more.
cnfrsrc Table 9-6 LCN Allocations for 8-port OC3 BXM, Ports Configured in Trunk Mode a(x) n1(x) m1(x) unallocated LCNs Total LCNS available to Port VSI Partition = min ( z1 + n1(x), max m1 (x) ) 1 120 3000 3500 3827 3500 2 50 0 0 3827 0 3 15 0 7048 3827 3827 4 0 100 100 3827 100 Sum, for x =1 through 4 185 3100 N/A N/A 5 6000 10 7048 702 712 6 0 0 100 702 100 7 100 200 200 702 200 8 0 100 2100 702 802 Sum for x = 5 6100 310 N/A N/A z1 = Port
cnfrsrc Example 2, 8-Port OC3 BXM Configured in Port Mode BXM ports configured for port mode rather than trunk mode have more connection spaces available for use by the TVC connections as it is not necessary to provide connection spaces for use by the AutoRoute trunks. This example is for an 8-port OC3 BXM configured for port mode and therefore, in Release 9.1, with all ports configured as ports.
cnfrsrc — Port 3 is guaranteed to support up to 15 PVCs, and no more. It is not guaranteed to support any TVCs, but will support up to: 4907 TVCs, subject to availability of unallocated LCNs “z1” on a FIFO basis. The configured maximum limit “m1(3)” of 7588 LCNs is ignored, as it is greater than the unallocated LCNs, “z1”, of 4907. — Port 4 supports no PVCS. It is guaranteed to support 100 TVCs, and no more.
cnfrsrc Table 9-7 Port (x) LCN Allocations for 8-Port OC3 BXM, Ports Configured in Port Mode a(x) n1(x) m1(x) z1 = unallocated LCNs Total LCNS available to Port VSI Partition = min ( z1 + n1(x), max m1 (x) ) Port Group 1 1 120 3000 3500 4907 3500 2 50 0 0 4907 0 3 15 0 7588 4907 4907 4 0 100 100 4907 100 Sum, for x =1 through 4 185 3100 N/A N/A Port Group 2 5 6000 10 6 0 0 100 1782 100 7 100 200 200 1782 200 8 0 100 2100 1782 1882 Sum for x = 5 thro
dspcd dspcd Displays the status, revision, and serial number of a card. If a back card is present, its type, revision, and serial number appear. The displayed information can vary with different card types. Syntax dspcd Example dspcd 5 Attributes Privilege Jobs Log Node Lock 1-6 No No IPX switch, IGX switch, BPX switch No Related Commands dncd, dspcds, resetcd, upcd Parameters-dspcd Parame ter Description slot slot number of card.
dspcds dspcds Displays the cards in a shelf, front and back, with their type, revision, and status. Syntax dspcds [l] Example dspcds Attributes Privilege Jobs Log Node Lock 1-6 No No IPX switch, IGX switch, BPX switch No Related Commands dncd, dspcd, resetcd, upcd Parameters-dspcds Parameter Description l Directs the system to display status of the cards on just the lower shelf of an IPX 32 or IGX 8430. If not entered, dspcds displays the top shelf by default.
dspcds • Standby—T Card idle, background test in progress. • Standby—F-T Card idle, failure(s) detected, background test in progress. • Failed Card failed. • Down Card downed by user. • Down—F Card downed, failure(s) detected. • Down—T Card downed, failure(s) detected, background test in progress. • Mismatch Mismatch between front card and back card. • Update * Configuration RAM being updated from active control card.
dspnode dspnode Displays a summary of interface devices connected to a routing node, or when executed from an IPX or IGX interface shelve shows the name of its hub node and trunk number. Syntax: dspnode Related Commands addshelf, delshelf, dsptrk Attributes Privilege Jobs Log Node Lock 1-6 No No BPX switch, IGX switch Yes Description The command displays tag switch controller devices connected to a BPX node and interface shelves connected to an IGX switch or BPX node.
dspnode Example Displays information about tag switch controllers and interface shelves (executed on the BPX hub node). Sample Display: n4 TN SuperUser BPX 15 9.1 BPX Interface Shelf Information Trunk 3.1 5.3 4.1 4.2 4.3 Name j6c j5c VSI VSI VSI Type AXIS IPX/AF VSI VSI VSI Last Command: dspnode Next Command: 9-50 Cisco BPX 8600 Series Reference Alarm MIN MIN OK OK OK Apr.
dspqbin dspqbin Displays the configuration of the specified Qbin on a BXM. Syntax dspqbin Example dspqbin 4.1 10 Attributes Privilege Jobs Log Node Lock BPX switch Related Commands cnfqbin Parameters-dspqbin Parameter Description slot.port The slot and port number of interest qbin number The qbin number. For EFT tag switching, this is Qbin number 10. Description The following example shows configuration of Qbin 10 on port 4.1 of a BXM card.
dspqbin Example dspqbin 4.1 10 Sample Display: n4 TN SuperUser BPX 15 Qbin Database 4.1 on BXM qbin 10 Qbin State: Minimum Bandwith: Qbin Discard threshold: Low CLP/EPD threshold: High CLP/EPD threshold: EFCI threshold: This Command: dspqbin 4.1 10 Next Command: 9-52 Cisco BPX 8600 Series Reference Enabled 0 65536 95% 100% 40% 9.1 Apr.
dsprsrc dsprsrc Displays the tag switching resource configuration of the specified partition on a BXM card. Syntax dsprsrc Example dsprsrc 4.1 1 Attributes Privilege Jobs Log Node Lock BPX switch Related Commands cnfrsrc Parameters-dspcds Parameter Description slot.port Specifies the BXM slot and port partition Specifies the vsi partition. Description The following example shows configuration of vsi resources for partition 1 at BXM port 4.1.
dsptrks dsptrks Display information on the trunk configuration and alarm status for the trunks at a node. The trunk numbers with three places represent virtual trunks. Syntax dsptrks Related Commands addtrk, deltrk, dntrk, uptrk Attributes Privilege Jobs Log Node Lock 1-6 No No IPX switch, IGX switch, BPX switch No Description Displays basic trunk information for all trunks on a node. This command applies to both physical only and virtual trunks.
dsptrks Example Enter the dsptrks command as follows to display the trunks on a BPX switch: dsptrks Sample Display: n4 TRK 2.1 3.1 5.1 5.2 5.3 6.1 6.2 4.1 4.2 4.3 TN Type OC3 E3 E3 E3 E3 T3 T3 OC3 OC3 OC3 SuperUser Current Clear Clear Clear Clear Clear Clear Clear Clear Clear Clear - BPX 15 Line Alarm Status OK OK OK OK OK OK OK OK OK OK 9.1 Apr. 4 1998 16:40 PST Other End j4a/2.1 j6c(AXIS) j6a/5.2 j3b/3 j5c(IPX/AF) j4a/4.
resetcd resetcd The reset card command resets the hardware and software for a specified card. Syntax resetcd Example resetcd 5 H Attributes Privilege Jobs Log Node Lock 1-3 Yes Yes IPX switch, IGX switch, BPX switch Yes Related Commands dspcd Parameters-resetcds Parameter Description slot number Specifies the card number to be reset. H/F Specifies whether the hardware or failure history for the card is to be reset.
upport upport Displays the cards in a shelf, front and back, with their type, revision, and status. Syntax upport Example upport 4.2 Attributes Privilege Jobs Log Node Lock 1-2 Yes Yes BPX switch Yes Related Commands dnport, cnfport, upln Parameters-dspcds Parameter Description slot.port Specifies the slot number and port number of the port to be activated.
upport Description The following example shows the screen that is displayed when the following command is entered to up a port on an ASI card: upport 4.2 System Response Sample Display: n4 TN Port: Interface: Type: Speed: CBR CBR CBR CBR VBR VBR VBR VBR Queue Queue Queue Queue Queue Queue Queue Queue 4.2 SuperUser Last Command: upport 4.2 9-58 Cisco BPX 8600 Series Reference 9.1 Apr.
uptrk uptrk Activates (or “ups”) a trunk. Syntax uptrk [.vtrk] Example uptrk 4.1 Related Commands addtrk, dntrk Attributes Privilege Jobs Log Node Lock 1-2 Yes Yes IPX switch, IGX switch, BPX switch Yes Parameters-uptrk Parameter Description slot.port Specifies the slot and port of the trunk to activate. If the card has only one port, the port parameter is not necessary. An NTM, for example, has one port.
uptrk Tag Switch Controller: For a tag switch controller, the delshelf command is also used to deactivate the link between the BPX routing node and the tag switch controller. In the case of tag switching, this is a link between a port on the BXM card and the tag switch controller. This link can be connected to a port that has been upped by either the upport or uptrk command, as the tag switching operation does not differentiate between these modes on the BXM.
CHAPTER 10 BME Multicasting This chapter contains an overview of multicasting and a description of the BME card used on the BPX switch for multicasting.
Standards • • • Video distribution, e.g., IP multicast video networks to the desktop • • UNI 3.1 Multicast Server Remote learning Medical imaging Standards UNI 4.
Connection Management Criteria BME Restrictions • BMEs can function in the following two BPX node configurations: — BCC-4s and BXMs only — BCC-3 control cards and legacy cards only, including BNIs and ASIs • VC frame merge is not currently supported Address Criteria • The VPI of a multicast connection indicates the multicast group to which it belong. • The VPI.VCI assigned to a multicast connection is unique for that card. • If the VCI = 0 for a multicast connection, this indicates a root connection.
BME Operation BME Operation Cables are connected between port 1 and port 2 of the backcard, transmit to receive and receive to transmit. Note Removing the physical loopback cables or placing line 1 or 2 into loopback will prevent the cells from the root reaching the leaves. BME Cell Replication Figure 10-1 shows a BME with a single root input multicasting with 3 leaves.
BME Operation Cell Replication Stats As an example of how traffic appears on the BME, if there is one root at port 1 with two leaves at port 2, and traffic is passed on the root at 500 cells/sec, then one should see an egress port stat of 1000 cell/sec on port 1 and an ingress port stat of 1000 cells/sec on port 2, as shown in Figure 10-2.
BME Operation Figure 10-3 Adding Multicasting Connections 13.1.78.900 (leaf 1) 3.4.55.75 (leaf 3) 14.1.100.40 (leaf 2) BPX Switch G BPX Switch E BPX Switch A BPX Switch F 1.1.80.100 (root) BME BPX Switch D 6.1.100.50 (leaf 1) BPX Switch B 4.3.50.60 (leaf 2) 10.1.233.400 (root) 11736 BPX Switch C Multi-Segment Multicast Connections Figure 10-4 shows an example of a multi-segment multicast connection where a leaf connection from one BME can become a root connection for another BME.
Alarms • • dspchstats 5.2.75.40 on BPX switch 2 (available) dspchstats 11.9.123.432 on BPX switch 3 (available) Figure 10-5 Statistics Collection 5.1.75.0 12.1.50.75 BME leaf 5.2.75.40 BPX Switch 1 leaf 1 BPX Switch 2 12141 root 11.9.123.432 BPX Switch 3 Policing Policing is supported on all leaf connections on the BME end. All policing types available on the BXM are available on the BME leaves No policing functionality is available on the root connection on the BME end.
Hot Standby Backup AIS cells AIS cells are automatically generated on the leaves, as shown in Figure 10-7, when: • • • There is a loss of signal (LOS) on the far end of the root There is a trunk failure When the root connection is downed using the dncon command. Figure 10-7 Alarms LOS or root down BPX Switch 1 leaf 1 AIS cells leaf 2 BPX Switch 2 BPX Switch 3 Hot Standby Backup BME cards can be set up to provide hot standby backup.
Configuration Configuration If the multicast tree has a large number of leaf connections, for example, 3000, then the cnfportq command should be used to configure the Qbin threshold to be greater than needed for half the number of leaves so as to assure that the multicast group will have no discards. The Qbin default depth is about 1200 cells. Qbin example using cnfportq command: j4b VT SuperUser ~ BPX 15 Port: 3.
Configuration Management 10-10 Cisco BPX 8600 Series Reference
CHAPTER 11 Repair and Replacement This chapter describes periodic maintenance procedures, troubleshooting procedures, and the replacement of major BPX switch components. The chapter contains the following: • • • Preventive Maintenance Troubleshooting the BPX switch Replacing Parts Preventive Maintenance Most monitoring and maintenance of the BPX switch is done via the BPX switch operating system software.
Troubleshooting the BPX Switch The FAIL indicators on the cards indicate that the system has found these cards defective in some mode, and now considers them as failed cards. Use Table 11-1 to find the cause and obtain the information on replacing the failed component. When using Table 11-1 for troubleshooting, call Customer Service before performing any disruptive testing or attempting to repair the BPX switch. This ensures that you have isolated the correct problem area.
Troubleshooting the BPX Switch Table 11-1 Troubleshooting the BPX Switch (Continued) Symptom Probable Cause Remedy BXM Port LED is red or orange (BXM configured for trunk mode). Trunk is in local or remote alarm. Use NMS dsptrk screen to confirm trouble. BNI Port LED is red or orange. Trunk is in local or remote alarm. Use NMS dsptrk screen to confirm trouble. Use short BNC loopback cable at LM-BNI connectors for local test of trunk. Loop trunk at DSX-3 crossconnect to check cable.
Troubleshooting the BPX Switch Displaying the Status of Cards in the Node When a card indicates a failed condition on the alarm summary screen, use the Display Cards (dspcds) command to display the status of the circuit cards on a node. The information displayed for each card type includes the card slot number, software revision level, and the status of the card. The possible status description for each card type are listed in Table 11-2.
Replacing Parts Replacing Parts After an alarm occurs, use the BPX switch software to isolate the problem. If an BPX switch part has failed, then it must be replaced. Caution Only authorized personnel should remove and replace parts on the BPX switch system. Parts should be replaced only by qualified personnel who have taken the Cisco training courses or been trained by a qualified system manager. For assistance in diagnosing or replacing a failed part, call Customer Service.
Replacing Parts Step 5 Unlatch the Air Intake Grille. Locate the small access hole in the top, center of the Air Intake Grille. Step 6 Fully insert a medium, flat-bladed screwdriver in the access hole. Step 7 Rotate the screwdriver to release the spring latch holding the grille. (Figure 11-1). The top of the grille should pop out. Step 8 Tilt the grille forward to approximately a 45 angle. Step 9 Put on a wrist strap to discharge any static.
Replacing Parts Figure 11-1 Unlatching the Air Intake Grille Power supply Latch Released air intake grill H7997 Access hole Replacing a Line Module The configuration of the back card may be slightly different depending on whether it is a single card or redundant card configuration. A standby card in a redundant card configuration may be removed without disrupting system operation even if it is a BCC. Removing a single card, however, will cause a system outage.
Replacing Parts Step 6 Loosen the two captive screws on the back card faceplate and, pulling on the top and bottom card extractors, slide the card straight out of the shelf slot. (See Figure 11-2.) To install a line module, perform the following steps: Step 1 Insert the line module (e.g., LM-3T3) into the slot from which the defective card was removed (see Figure 11-2). Step 2 Tighten the two captive screws. (Tighten securely, but do not overtighten.
Replacing Parts Figure 11-2 Removing a Line Module Captive screws (2) Upper extractor R X POR T1 T X R X POR T2 LM-3T3 (Typical) T X R X LM– POR T3 3/T3 15ASM LM– 3/T3 T X LM– 3/T3 14 LM– 3/T3 13 LM– 3/T3 12 11 Lower extractor LM– 3/T3 10 LM– 3/T3 9 LM– 3/T3 8BCC-B LM– 3/T3 7BCC-A LM– 3/T3 6 LM– 3/T3 LM– 3/T3 5 LM– 3/T3 4 LM– 3/T3 3 LM– 3/T3 2 H8001 1 Replacing a DC Power Entry Module DC Power Entry Modules (PEMs) contain few active components so they should rarely n
Replacing Parts Figure 11-3 DC Power Entry Module with Conduit Box ON CB1 OFF U CON SE CO DUC PPER TOR S ON L Y U CON SE CO DUC PPER TOR S ON L Y 0 Conduit cover screws Conduit box cover Conduit connection (customer supplied) ON CB1 OFF 0 +RT N –48V H8005 90° terminal lug (3 places) Step 6 If a conduit box is used, remove it. Remove the ground screw above the middle terminal block connector (see Figure 11-3).
Replacing Parts Replacing an AC Power Supply BPX switches are powered by redundant power supplies; either power supply can supply the current requirements of the node. The AC Power Supply is part of an assembly which is replaced as a single unit. Access to the AC Power Supply assembly is from the front, but first, the Air Intake Grille must be removed.
Replacing Parts Step 8 There are two power supply securing fasteners, one on each side of the power supply assembly (Figure 11-4). The one on the left of each supply is a spring-loaded pin, the one on the right of each supply is a normal thumb-screw. Loosen the thumb-screw on the right. Step 9 With the right hand, grip the power supply under the front panel. With the left hand, pull out the spring-loaded pin on the left side of the supply and hold it out as you pull out the power supply assembly.
Replacing Parts Step 5 Screw in the thumb-screw on the right side of the power supply assembly until it is finger tight. Step 6 Flip the retaining bracket up and tighten its thumbscrew. Step 7 Reinstall the Air Intake Grille and press firmly on the top, center of the Air Intake Grille until the latch snaps into place. Step 8 Check the status and output voltage of the replacement power supply using the dspasm command. Make sure the status is OK and the output voltage is 48V.
Replacing Parts Replacing the Temperature Sensing Unit The temperature sensing unit is located on the ASM card. If the temperature indication using the dspasm command does not appear to be correct, try a replacement ASM card. Replacing Card Slot and Fan Fuses on the System Backplane There is a separate fuse provided on the System Backplane for each card slot. These fuses are numbered F4 through F18, corresponding to card slots F15 down through F1 (see Figure 11-6).
Replacing Parts Figure 11-6 Fan Fuses F1 F2 F3 Card Slot and Fan Fuse Locations on System Backplane 15 14 13 12 11 10 F5 F6 F7 F8 Card slots 9 8 7 6 5 4 3 2 1 F9 F10 F11 F12 F13 F14 F15 F16 F17 F18 H8037 F4 (F4, for card slot 15) (F18, for card slot 1) Repair and Replacement 11-15
Replacing Parts 11-16 Cisco BPX 8600 Series Reference
CHAPTER 12 Frame Relay to ATM Network and Service Interworking This chapter describes Frame Relay to ATM interworking. Frame Relay to ATM Interworking allows users to retain their existing Frame Relay services, and as their needs expand, migrate to the higher bandwidth capabilities provided by BPX switch ATM networks.
Figure 12-1 Frame Relay to ATM Network Interworking Part A Network interworking connection from CPE Frame Relay port to CPE Frame Relay port across an ATM Network with the interworking function performed by both ends of the network.
Service Interworking Figure 12-3 Frame Relay to ATM Interworking Examples with AIT Card on IPX Switch IPX to BPX Frame Relay IPX BPX FRP AIT CPE BNI ASI Frame relay IPX to frame relay IPX Frame Relay One of these must be an IPX interface shelf IPX BPX FRP IPX interface AIT shelf BPX AIT BNI BNI Fr Rly FRP IPX cloud to BPX Frame Relay IPX IPX BPX CPE FRP AIT BNI IPX to (IPX - BPX cloud) to BPX IPX FRP The AIT-BNI trunks are always CGW BPX CPE BPX BPX IPX AIT BNI Frame R
Networking Interworking interface supported by the MGX 8220, e.g., ASI, AUSM. Translation between the Frame Relay and ATM protocols is performed in accordance with RFC 1490 and RFC 1483.
Networking Interworking Figure 12-5 Frame Relay to ATM NW Interworking Detail IPX MUX BUS FRP AIT Frame Relay Frame Relay CPCS CPCS Fast Packet Fast Packet AAL-5 SAR AAL-5 SAR Physical ATM Physical ATM Physical ATM Physical FR-SSCS ATM Physical Frame Relay Frame Relay Fast Packet Fast Packet Physical Physical Physical Q.922 ATM T3/E3 feeder trunk ATM T3/E3 Upper layers FRP BNI FR-SSCS Physical Physical MUX BUS AIT BNI Q.922 IPX shelf BPX Fr Rly Upper layers Fr Rly Q.
Networking Interworking The frame relay to ATM networking interworking function is available as follows: • IPX switch frame relay (shelf/feeder) to IPX switch frame relay (either routing node or shelf/feeder). • • • MGX 8220 frame relay to MGX 8220 frame relay. • • MGX 8220 frame relay to BPX switch or MGX 8220 ATM port. MGX 8220 frame relay to IPX switch frame relay (either routing node or shelf/feeder).
ATM Protocol Stack Discard selection is based upon the standard CLP bit in the cells. When the routing path enters an IPX/IGX switch, an AIT/BTM card which supports Interworking traffic is required to convert the connection data from cells to frames (frames to fastpackets out onto MuxBus to FRP/cell bus to FRM), and visa versa. Additionally, the AAL-5 framing is removed upon conversion to frames, and added upon conversion to cells.
AIT/BTM Interworking and the ATM Protocol Stack AIT/BTM Interworking and the ATM Protocol Stack ATM to Frame Relay interworking (ATF) performs various tasks including the following: • Conversion of PDUs between the frame relay and ATM virtual circuits of the frame relay and ATM user devices. • • Conversion between frame relay traffic service and ATM quality of service parameters. Mapping of management status, including connection, port, line, and trunk status and events.
AIT/BTM Interworking and the ATM Protocol Stack Figure 12-8 Protocol Stack Operation 8 7 6 5 4 3 2 1 CR EA DE EA 2 1 CR EA DE EA FLAG DLCI upper DLCI lower FECN BECN Q.922 Fr Rly PDU Data field FLAG 8 7 6 5 DLCI upper 4 FLAG DLCI lower FR-SSCS PDU 3 FECN BECN Data Trailer AAL5 PDU payload PAD Length of user data CRC32 N byte (1-65535) 0-47 byte 2 byte 4 byte CPCS PDU 48-byte PDU 8 48-byte PDU 7 6 5 ...........
AIT/BTM Control Mapping, Frames and Cells AIT/BTM Control Mapping, Frames and Cells In addition to performing DLCI to PVC/VCC conversion, the network interworking feature provided by the AIT card in the IPX switch or BTM in the IGX switch maps cell loss priority, congestion information, and management information between frame relay and ATM formats as follows: CELL LOSS PRIORITY, Frame Relay to ATM Direction Each frame relay to ATM network interworking connection can be configured as one of the following
Management, OAM Cells Management, OAM Cells OAM cell processing: • • • • F5 OAM loopback AIS FERF Cisco WAN switching Internal OAM Functional Description ATF Summary Features • • • • • • Interworking: ATM to Frame Relay connections • • • • • • • • • BCM (Backward Congestion Messages) • Priority Bumping is not supported across the interface shelves, but is supported across the routing network. • • Statistical Line Alarms per Software Functional Specification (i.e., Bellcore standards).
Functional Description • • • Test tstcon not supported at BPX switch endpoints; it is supported at IPX switch endpoints Gateway terminated inter-domain connections Via connections through IPX switch Some ATF Connection Criteria ATF connections are allowed between any combination of ATM and Frame Relay UNI and NNI ports. Virtual circuit connections are allowed. Virtual path connections are not. ATF connections can be mastered by the IPX switch or BPX switch end.
Functional Description Structure • NNI The NNI format supports a 12-bit VPI. A-bit status changes are passed to the remote end of the connection. • ILMI The ILMI MIB and protocol was implemented in release 7.2. The additional support in consists of an activation and configuration interface, collection of statistics, and end-to-end status updates. • LMI Annex G The LMI Annex G protocol was implemented in release 7.2.
Functional Description OAM Cell Support OAM cells are detected and transmitted by the ASI-1 firmware. System software displays alarm indications detected by the firmware. Additionally, loopbacks between the ATM-UNI and the ATM-CPE can be established. ForeSight round-trip delay cells are generated by firmware upon software request. System software deals with the following OAM cell flows: • • End-to-End AIS/FERF—software displays on a per-connection basis.
Functional Description User Commands The following user commands are associated with diagnostics changes: • • • • • • • • addloclp addrmtlp cnftstparm dellp dspalms dspcd dspcds tstdly Virtual Circuit Features The following virtual circuit features are supported by the ASI-1: • Connection Groups Connection groups are supported for ASI-1 ATM and interworking connection types, allowing termination of up to 5000 (grouped) virtual circuits per BPX switch.
Management User Commands The following user commands are associated with virtual circuit feature changes: • • • • • • • • • addcon addcongrp cnfcon cnfatmcls delcon delcongrp dspatmcls dspcongrps grpcon AUser Commands The following user commands are modified to support ASI-1 E3: • • • • • • • • • • cnfln cnflnstats dspcd dspcds dsplncnf dsplns dsplnstatcnf dsplnstathist dspyred prtyred Management Connection Management Interworking connections may be added from either the BPX switch, the IPX switch, t
Management Routing Interworking connections use the complex gateway feature of the AIT trunk card to repackage data from frames to ATM cells, and vice-versa. All BPX switch-IPX switch hops these connections route over must provide the complex gateway function. IPX switch-IPX switch hops (frame relay connections) can be any trunk card type. This requirement simplifies the routing mechanism when dealing with structured networks, as software does not know the type of trunks in remote domains.
Management Connection Management The NNI cell format has 12 bits for the VPI, so addcon allows specification of VPI 0-4095 on NNI ports. Signaling System software supports the following LMI/ILMI signaling actions: • Internal network failure: software informs LMI/ILMI to set A bit = 0 for failed connections. Software informs ASI-1 to transmit AIS to port for failed connections. • Port failure/LMI Comm Failure: software informs remote nodes terminating all affected connections.
CHAPTER 13 Tiered Networks This chapter describes the tiered network architecture that supports interface shelves (non-routing nodes) connected to an IPX/IGX/BPX routing network. The chapter contains the following: • • • • • Routing Hubs and Interface Shelves BPX Routing Hubs in a Tiered Network IGX Routing Hubs in a Tiered Network User Interface Commands Cisco StrataView Plus NMS With Release 8.5, tiered networks now support voice and data connections as well as frame relay connections.
Routing Hubs and Interface Shelves Frame relay connections originating at IPX interface shelves and frame relay, ATM, CESM, and FUNI connections originating at MGX 8220 interface shelves are routed across the routing network via their associated BPX routing hubs. Note The IGX switch may also be configured as an interface shelf feeding frame relay connections to a BPX routing hub.
BPX Routing Hubs in a Tiered Network BPX Routing Hubs in a Tiered Network Tiered networks with BPX routing hubs have the capability of adding interface shelves/feeders (non-routing nodes) to an IPX/IGX/BPX routing network (Figure 13-2). The MGX 8220 interface shelf, and IPX or IGX nodes configured as interface shelves are connected to BPX routing hubs. Interface shelves allow the network to support additional connections without adding additional routing nodes. The MGX 8220 supports frame T1/E1, X.
BPX Routing Hubs in a Tiered Network • Frame Relay and ATM connection management to an MGX 8220 interface shelf is provide by Cisco StrataView Plus • • Telnet is supported to an interface shelf; the vt command is not. Remote printing by the interface shelf via a print command from the routing network is not supported. General Annex G, a bi-directional protocol, defined in Recommendation Q.2931, is used for monitoring the status of connections across a UNI interface.
BPX Routing Hubs in a Tiered Network 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.
BPX Routing Hubs in a Tiered Network ForeSight 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 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.
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.
BPX Routing Hubs in a Tiered Network Alarm Management on the IPX Interface Shelf 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 BPX hub node. Port Management Uses existing commands Connection Management Parameters entered at SV+ when adding connection.
IGX Routing Hubs in a Tiered Network IGX Routing Hubs in a Tiered Network With tiered networks, IGX nodes on the edge of the network are configured as interface shelves and are connected to IGX nodes 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 an IGX interface shelf and IGX routing hubs is shown in (Figure 13-3).
IGX Routing Hubs in a Tiered Network Figure 13-4 IGX Shelves and Routing Hubs, Frame Relay Connections SV+ SNMP ATM routing network IGX IGX hub IGX IGX BPX --ATFR conn for middle segment IGX hub BTM-E1 --Frame relay conns on interface shelves 2 or 3 segment Frame relay connections BTM-E1 IGX IGX IGX The IGX Frame Relay Cards are the FRM, UFM-U, UFM-C. The Trunk card on both ends of IGX feeder trunk is the BTM-E1, T3, or E3.
IGX Routing Hubs in a Tiered Network • Remote printing by the interface shelf via a print command from the routing network is not supported. The following applies to voice and data connections over IGX interface shelves: • 3-segment connections are supported, that is: originating IGX interface shelf data or voice card to IGX routing hub, across IGX intermediate nodes, as applicable, to IGX routing hub, to terminating IGX interface shelf data or voice card.
IGX Routing Hubs in a Tiered Network Definitions IGX Routing Hub An IGX node in the routing network which has attached IGX interface shelves. Also referred to as a hub node or IGX hub. IGX Interface Shelf A special configuration of an IGX switch that is connected as a shelf to an IGX routing hub. An IGX interface shelf is sometimes referred to as IGX A/F or feeder. The IGX interface shelf does not perform routing functions nor keep track of network topology.
IGX Routing Hubs in a Tiered Network 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.
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.
User Interface Commands Alarm Management of Interface Shelf on the 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. Alarm Management on the IGX Interface Shelf dspalms The field, routing network Alarms, shows a count of major and minor alarms in the routing network.
User Interface Commands dspalms dsptrks Data Connection Commands addcon dspcon dspcons Data Channel Commands cnfchdfm cnfcheia cnfcldir cnfdchtp cnfdclk cnfict Voice Connection Commands addcon Voice Channel Commands cnfchadv cnfchutil cnfchkdl cnfcos cnfechec cnfchgn cnfcond cnfrcvsig cnfvchtp cnfxmtisig cnfcmb 13-16 Cisco BPX 8600 Series Reference
Cisco StrataView Plus NMS Cisco StrataView Plus NMS Interface shelf and feeder trunk information is reported to Cisco StrataView Plus by the routing hub and interface shelf. Cisco StrataView Plus can virtually connect to any node in the network via a TCP/IP connection. The Cisco StrataView Plus Connection Manager is used to add, delete, and monitor voice and data connections for tiered networks with IGX hubs.
Cisco StrataView Plus NMS 13-18 Cisco BPX 8600 Series Reference
CHAPTER 14 BPX SNMP Agent This chapter introduces the functions of the Simple Network Management Protocol (SNMP) agent that is embedded in each BPX node. To benefit from this chapter, readers should have a general knowledge of SNMP, IP protocols, and MIBs. The chapter contains the following: • • • • • Introduction SNMP Overview SNMP Functions MIB II Support Cisco WAN Switching Proprietary MIB Structure Introduction An SNMP agent is embedded in each BPX node.
SNMP Overview Figure 14-1 shows an SNMP manager and the nodes within a domain. Figure 14-1 SNMP Manager and Agents in a BPX Domain SV+ workstation (SNMP manager) SNMP management platform BPX node 3 BPX node 4 SNMP agent SNMP responses Prop. MIB SNMP agent SNMP requests STD MIB II Prop. MIB SNMP responses ATM UNI 3.1 MIB ATM UNI 3.1 MIB BPX node 1 BPX node 2 SNMP agent Prop. MIB STD MIB II SNMP agent STD MIB II ATM UNI 3.1 MIB Prop. MIB STD MIB II ATM UNI 3.
SNMP Functions SNMP Functions The SNMP protocol provides a basic query-response model for network management. The network manager has access to Get (Get-Next) and Set functions. A Get request lets the manager read variables in the BPX switch. The request consists of a single variable or a list of variables. The BPX database subsequently returns the requested values. The Get-Next request lets the manager obtain the successor to the given variable’s object identifier.
SNMP Functions Responses to Get (Get-Next) Requests When an SNMP manager workstation sends an SNMP Get request packet to a BPX agent, it utilizes the IP protocol for addressing. The request packet can use either a LAN interface for a locally attached management workstation or a network interface for remote access. Each packet is in ASN.1 format, which is suitable for transmission via the UDP protocol. Once it arrives, the packet is decoded to a Protocol Data Unit (PDU).
MIB II Support Responses to Set Requests When an SNMP manager workstation sends an SNMP Set request packet to a BPX agent, it utilizes the IP protocol for addressing. The request packet can use either a LAN interface for a locally attached management workstation or a network interface for remote access. Each packet has the ASN.1 format, which is suitable for transmission via the UDP protocol. Once it arrives, the packet is decoded to a Protocol Data Unit (PDU).
Cisco WAN Switching Proprietary MIB Structure Cisco WAN Switching Proprietary MIB Structure This section is an overview of the Cisco WAN Switching proprietary MIB. The proprietary MIB resides under the enterprises branch of the SNMP tree structure (1.3.6.1.4.1.StrataCom (351)). For detailed information on the structure and contents of the MIB, refer to the actual MIB that is included on the release tape. The MIB is in ASN.1 format.
Cisco WAN Switching Proprietary MIB Structure The ATM endpoint-specific information (last item in the previous list) provides the mechanism for the manager to provision and configure ATM connections. The available endpoint-specific information is: • • • • • • • Local description (e.g., domain.node.slot.port.vpi.vci) (read-write) Remote description (e.g., domain.node.slot.port.vpi.
Cisco WAN Switching Proprietary MIB Structure 14-8 Cisco BPX 8600 Series Reference
A P P E N D I X A BPX Node Specifications This appendix lists information for the BPX system specifications. (Refer to on-line documents for latest information). General System Capacity: 1 shelf with 15 card slots. Requires 1 or 2 dedicated slot(s) for BCC card. Requires 1 dedicated slot for ASM card. Network Interface: T3, E3, OC3, and OC12. Network Trunks: 32 per node max. Network Interface Protocol: ATM layer using 53-byte cell. Cell Switching: Crosspoint switch matrix, non-blocking.
General Weight, approx: 73 lb. (33.2 kg.) empty BPX shelf, w/fans but no PS. 6 lb. (2.7 kg.) each card. 18 lb. (8.2 kg.) empty AC Power Supply Tray. 16 lb. (7.3 kg.) each AC Power Supply. 2 lb. (0.9 kg.) each DC Power Entry module. Clearance Requirement: At least 30 inches front and rear clearance; nominal 12 inch side clearance. Power Source: AC system: 180 – 264 VAC, 47 to 63 Hz. DC system: –42 to –56 VDC. Power Requirements: AC BPX-15: 13 A at 180 VAC (2300 VA).
ATM Trunk Interface (BXM-T3/E3 Cards) ATM Trunk Interface (BXM-T3/E3 Cards) Characteristic T3 (DS3) E3 Line Rate: 44.736 Mbps +/- 20 ppm 34.368 Mbps +/- 20 ppm Line Code: B3ZS HDB3 Cell Transfer Rate: 96,000 cells per second (PLCP mode) 80,000 cells per second 104268 cells per second (HEC/Direct mode) Framing: ANSI T1.107, T1.107a ITU T G804, G.832 Signal Level: TA-TSY-000773 (PLCP) ITU-T G.703 Transmission Convergence Sublayer: DS3 PLCP frame format G.
ATM Trunk Interface (BXM-155 Cards) ATM Cell Rate: 353,208 cells/sec. Jitter: ATM Forum UNI 3.1 ATM Layer Protocol: LMI, ILMI Port Alarm Processing: LOS, LOF, LOP, Path AIS, Path Yellow Line Errors Counted: Connector: SC for MMF, SMF (IR) and SMF (LR) Max.
ATM Trunk Interface (BXM-622 Cards) ATM Trunk Interface (BXM-622 Cards) Line Rate: 622.08 Mbps Line Code: NRZ Signal Level: Min dBm Max dBM SMF IR TX -15 -8 SMF IR RX -28 -8 SMF LR TX -2 +2 SMF LR RX -28 -8 Framing Format: STS-12c, STM-4 Port Interface: LMI, ILMI ATM Cell Rate: 1,412,830 cells/sec. Jitter: ATM Forum UNI 3.1 ATM Layer Protocol: LMI, ILMI Port Alarm Processing: LOS, LOF, LOP, Path AIS, Path Yellow Line Errors Counted: Connector: SMF-FC Max.
ATM T3 Trunk Interface (BNI-T3, LM-3T3) ATM T3 Trunk Interface (BNI-T3, LM-3T3) Line Rate: 44.736 Mbps Line Code: B3ZS. Signal Level: DSX-3. Framing Format: C-bit parity is monitored. No other framing or control bits in the DS3 frame are either altered or monitored. Protocol: Physical Layer Convergence Protocol per AT&T Publication TA-TSY-000772 and 000773. ATM Cell Rate: 96,000 cells/sec. Limited to 80,000 cells/sec. when interfacing with the IPX. Alarms Sent: Remote. Alarms Received: AIS.
ATM E3 Trunk Interface (BNI-E3, LM-3E3) ATM E3 Trunk Interface (BNI-E3, LM-3E3) Line Rate: 34.368 Mbps 20 ppm, asynchronous Line Code: HDB3 Signal Level: CCITT G.703 Framing Format: CCITT G.804, G.832 Port Interface: 75 ohm unbalanced Barrier: Fully barriered per EN 41003 ATM Cell Rate: 80,000 cells/sec Jitter: per CCITT G.823 ATM Layer Protocol: per CCITT I.
ATM OC3 Trunk Interface (BNI-OC3, LM-OC3) ATM OC3 Trunk Interface (BNI-OC3, LM-OC3) Line Rate: 155.52 Mbps Line Code: NRZ Signal Level: Max Min MMF TX –8 dBm –15 dBm MMF RX –8 dBm –28 dBm SMF LR TX 0 dBm –5 dBM SMF LR RX –10 dBm –34 dBm Framing Format: STS-3c, STM1 Port Interface: LMI, ILMI ATM Cell Rate: 353,208 cells/sec. Jitter: < 0.1 UI p-p, < 0.
ATM Service Interface (BXM-T3/E3 Cards) ATM Service Interface (BXM-T3/E3 Cards) Capacity: 8 or 12 ports per card Interface: DS3/T3/E3 Line Rate: DS3 44.736 Mbs, E3 34.368 Mbps No. of channels per card: 16,000 No. of channels per node: VPI Addressing Range: ATM UNI 3.1 compliant VCI Addressing Range: ATM UNI 3.1 compliant Queues: 16 COS with 32 Virtual Interface (VI) queues ATM Service Interface (BXM-155 Cards) Capacity: 4 or 8 ports per card Interface: OC-3c/STM-1 Line Rate: 155.52.
ATM Service Interface (ASI-1, LM-2T3) ATM Service Interface (ASI-1, LM-2T3) Capacity: 2 ports per card Interface: T3 Line Rate: 96,000 cells/sec. No. of channels per card: 1000 No. of channels per node: 1000 or 5000 (grouped) VPI Addressing Range: 0–255 (UNI), 0-1023 (NNI_7 VCI Addressing Range: 1–4095 Queues: 32, 16 per line (port) includes CBR, VBR, and ABR queues ATM Service Interface (ASI-1, LM-2E3) Capacity: 2 ports per card Interface: E3 Line Rate: 80,000 cells/sec. No.
ATM Service Interface (ASI-2, LM-OC3) ATM Service Interface (ASI-2, LM-OC3) Capacity: 2 ports per card Interface: OC3 Line Rate: 353,208 cells/sec. No. of channels per card: 1000 No.
ATM Service Interface (ASI-2, LM-OC3) A-12 Cisco BPX 8600 Series Reference
A P P E N D I X B BPX Switch Cabling Summary This appendix provides details on the cabling required to install the BPX switch. Note In all cable references, the transmit direction is from the BPX switch, receive is to the BPX switch. Trunk Cabling Trunk cables connect the customer DSX-3 crossconnect point or T3-E3 Interface Module to the BPX switch at the LM-3T3 back card. Refer to Table B-1 for details.
LM-BCC Cabling Table B-2 AC Power Cables Cable Parameter Description Cable: Provided with 8 feet (2.3 m.) of 3-conductor wire with plug. Plug: customer end 20 A NEMA L620, 3-prong plug (domestic) or 13 A 250 Vac BS1363, 3-prong fused plug (UK, Ireland) CEE 7/7 (Continental Europe) AS3112 (Australia/New Zealand) CEI23-16/VII (Italy) DC Powered Nodes DC wiring (Table B-3) is generally provided by the customer.
LM-BCC Cabling Table B-5 Auxiliary and Control Port Pin Assignments Pin# Name Source Description 1 FG both Frame Ground 2 TxD DTE Transmit Data 3 RxD DCE Receive Data 4 RTS DTE Request to Send 5 CTS DCE Clear to Send 6 DSR DCE Data Set Ready 7 SG both Signal Ground 8 CD DCE Carrier Detect 20 DTR DTE Data Term Ready LAN Port Cabling The LAN connection is used to connect one of the nodes in the network to a StrataView Plus NMS workstation.
LM-BCC Cabling External Clock Input Cabling This cabling is for making external clock connections for use by the BCC-32, BCC-3, and BCC-4 backcards. The BCC-32 uses the BCC-bc backcard, and the BCC-3 and BCC-4 both use the BCC-3-bc backcard. T1 Clock Cabling Table B-8 through Table B-11 lists T1 clock cabling details. Table B-8 External Clock Cabling Cable Parameter Description Cable Type: 22 AWG, ABAM individually shielded twisted pair. Two pair per T1 line (1 transmit and 1 receive).
LM-BCC Cabling E1 Clock Cabling Table B-12 through Table B-15 lists E1 clock cabling details. Table B-12 E1 Connector Pin Assignments for External Clock Connector Description Cable Type: 75-ohm coax cable for unbalanced connection or 100–120-ohm twisted pair for balanced connection. Two cables/pairs (1 transmit, 1 receive) per E1 line. Cable Connector: Two female BNC for unbalanced connection; male DB15 for balanced connection. See Table B-13 and Table B-15 for pinouts. Max. Cable Length: Approx.
External Alarm Cabling External Alarm Cabling This cable (Table B-16) is for connecting network alarm outputs to the LM-ASM ALARM OUTPUT connector only. Table B-17 lists the pinouts for the network alarm outputs. Table B-16 External Alarm Cabling Cable Parameter Description Interface: Dry-contact relay closure. Wire: 24 AWG, shielded, 6-pair.
Redundancy “Y” Cable Table B-18 Standard Cables Available from Cisco Model# Description Usage T3-E3-10 T3-E3-25 T3-E3-50 T3-E3-75 T3-E3-xx 75 coax/BNC-BNC, 10' 75 coax/BNC-BNC, 25' 75 coax/BNC-BNC, 50' 75 coax/BNC-BNC, 75' length to be specified T3 or E3 trunk interface 5620 RS-232/M25-F25 Control port to control terminal, StrataView, or ext. window device 5621 RS-232/M25-M25 special Control or Aux. port to modem 5623 RS-232/M25-M25 Aux. port to ext.
Redundancy “Y” Cable B-8 Cisco BPX 8600 Series Reference
A P P E N D I X C BPX Switch Peripherals This appendix provide details on BPX switch peripheral equipment, including printers and modems. The appendix includes the following sections: • • • Network Management Printer Modems, Dial-In and Dial-Out Network Management Cisco StrataView Plus Terminal A Cisco StrataView Plus workstation is recommended for managing a network containing IPX, IGX, and BPX switch.
Printer Table C-1 Control Port Parameters for Local Control (pc or workstation) Parameter Setting BPX switch Port Used: Serial CONTROL port, located on a BCC back card, is used to interface to a local terminal. Code: Standard 7 or 8-bit ASCII; 1 or 2 stop-bits; even, odd or no parity. Interface: RS-232 DCE. Data Rate: All standard asynchronous data rates from 300 to 19200 bps, independently software-selectable. Supported Terminals: Any terminal compatible with DEC VT-100.
Printer The High Speed Serial Interface DIP Switch consists of two DIP switches, SW1 and SW2, located on a serial-board that is attached to the printer's main board. Set switches 1 and 2 as indicated in Table C-4 and Table C-5. Table C-4 Switch 1 Settings—Okidata 184 Printer Switch 1 Setting Description 1 On Odd parity. 2 On No parity. 3 On 8 data bits. 4 On Ready/busy protocol. 5 On Test select circuit. 6 On Print mode. 7 On Busy line selection. 8 On DTR pin 2 enabled.
Modems, Dial-In and Dial-Out Modems, Dial-In and Dial-Out Customer service uses modems for diagnosing and correcting customer problems with installed BPX switches. The modem that is currently recommended for use with the BPX switch is the Codex Model V.34R. A dial-in connection to a BPX switch RS-232 from customer service via a modem uses the CONTROL port of the BPX switch. A dial-out connection from a BPX switch via a modem to customer service uses the AUXILIARY port of the BPX switch.
Modems, Dial-In and Dial-Out Step 6 Connect the modem to the BPX CONTROL port using a null-modem cables Figure C-1. A null modem cable is used, as the connection is essentially a DCE to DCE rather than a DTE to DCE connection. Step 7 Ask customer service to assist in testing the operation of the modem setup. Table C-7 V.34R Modem Configuration for Auto-Answer (Dial-in to BPX) Step Command Function 1. AT & F Reset to factory default. 2 ATL1 Set modem loudness, modem speaker at low volume. 3.
Modems, Dial-In and Dial-Out IPX Auto-Dial to Customer Service The following is a setup procedure for the customer’s BPX to dial up customer service. Step 1 Using the cnfterm command, set the BPX AUXILIARY port speed to 9600 bps and enable XON/XOFF flow control. Step 2 Using the cnftermfunc command, select option 7, “Autodial Modem” and enter the customer service-designated Network ID, and the customer service modem phone number.
Modems, Dial-In and Dial-Out Table C-9 Step V.34R with talk/data, Auto-Dial Configuration (dial-out to customer service)* Command Function These configuration commands are for a V.34R modem that has a talk/data pushbutton. 1. AT&F Initializes factory defaults. 2. ATL1 Modem speaker at minimum volume. 3 AT\N3 To enable MNP error correction 4 AT%C To disable data compression 5 AT\J Enables DTE speed conversion 6 AT\Q1 Enables flow control 7 AT\T3 Enables 3-minute inactivity timer 8.
Modems, Dial-In and Dial-Out C-8 Cisco BPX 8600 Series Reference
A P P E N D I X D AT3-6ME Interface Adapter This appendix describes the AT3-6ME Interface Adapter, sometimes referred to as the T3-T2 Interface Adapter, that is used with the BPX switch to provide a 6 Mbps ATM network interface to T2 transmission facilities.
Equipment Description ATM cells from one interface are mapped to the other interface enabling users with ATM node equipment with North American T3 ATM ports to operate in a T2 network. The ATM cell throughput on a T2 digital trunk using this adapter is limited to 14,490 cells per second. The cell transfer rate for T2 is greatly reduced from the T3 cell rate out of a T3 port on an IPX using the ATMT card or from a BPX port. It is very important to restrict the cell rate from the node when using a T2 trunk.
Equipment Description Table D-1 Rear Panel Connectors Connector Type Description T3 RX BNC Receive T3 input from BPX, IGX, or IPX ATM port. T3 TX BNC Transmit T3 output to BPX, IGX, or IPX ATM port. T2 RX BNC Receive 6 MB input from T2 facility. T2 TX BNC Transmit 6 MB input to T2 facility. RS-232 DB9 Control terminal connection. Primary Power IEC AC power input with fuse.
Equipment Description Front Panel Indicators The front panel of the system provides LED indicators for the alarm status of the transmit and the receive T3 and the T2 interfaces (refer to Table D-2 and Figure D-2). Also on the front panel are indications for power and for operating status (Fail/Active). The Overflow LED indicates that the cell rate coming from the T3 interface exceeds the bandwidth of the T2 facility and that the Interface Adapter buffer has overflowed.
T3-RX T3-TX T2-RX T2-TX AIS RAI LOS LOF RS-232 AIS RAI LOS Overflow T2/T3 Loop 90 TO 250 VAC 50-60 Hz Fuse: 1A / 250 V FT2 SW-1 1 0 Configuration Fail/Active Power SW-2 Figure D-2 H8187 AT3-6M AIS RAI LOS LOF AIS RAI LOS T3 Recieve Status T3 Transmit Status T2 Recieve Status T2 Transmit Status Equipment Description Front and Rear Panel Features AT3-6ME Interface Adapter D-5
Installation Installation Install the AT3-6ME in a rack adjacent to the BPX enclosure (allowing room for any AC Power Supply Assembly that may also need to be mounted) or in the IPX enclosure wherever there is space for the AT3-6ME adapter. System Connections Two short BNC-BNC cables are required to connect the AT3-6ME to the BPX or IPX node.
Operation Table D-4 DIP Switch SW-2 Selection Guide Switches Position Function 1 2 Up Up Internal synchronization source for the T2 transmitter 1 2 Up Down Slave T2 transmitter to T3 line 1 2 Down Down Slave T2 transmitter to T2 receiver 3 4 Up Up Long length T3 cable 3 4 Up Down Medium length T3 cable 3 4 Down Down Short length T3 cable; system is co located to IPX/IGX/BPX1 (default) 5, 6 don’t care Unused 7 Up ATM converter mode 7 Down Test Mode 8 Up Enable BPV relay fro
Operation Through the self test, all LEDs light up. When the test is completed successfully the Active/Fail LED turns green. If the system fails self test, it will repeat the self-test twice more. If it continues to fail, the Active/Fail LED turns red. Normal Operation In standard operation the AT3-6ME system relays ATM cells from the T2 6M to the T3 interface. To accommodate for the difference in the transmission rate, the AT3-6ME removes all null cells from the T3 interface.
Operation Upon power up, the system goes through power up diagnostics. The terminal displays the diagnostics sequence. Upon successful self test the unit is available for operation. The terminal will display the actual set up of the system represented by the DIP switches (see Table D-6). If the configuration was overwritten through the TTY, the terminal will display the actual set up that could be different then the dip switch setting.
Specifications Table D-8 Status Display T31 T21 BPV NNN NNN Parity Errors NNN X Framing Errors NNN NNN Status PLCP Framing Errors NNN X HEC Errors NNN NNN RX Cells NNN NNN TX Cells NNN NNN AIS 1/0 1/0 1/0 1/0 1/0 LOF 1/0 1/0 Overflow X 1/0 1. X = not available Specifications The following are the specifications for the AT3-6ME Interface Adapter: T3 interface Line rate: 44.
Specifications T2 Interface Line rate: 6.312 Mbps Line code: B8ZS Synchronization: Internal 6.312 Mbps 30 ppm or Slave to the incoming 6 Mbps line or Slave to the T3 PLCP frame Framing format: ITU-T G.703 ATM Layer: Per NTT UNI specification dated 1993 Queue: 75 cell FIFO Cell Rate: Up to 14,490 cells/sec.
Specifications D-12 Cisco BPX 8600 Series Reference
A P P E N D I X E Glossary A A-bit (active bit) The bit in the frame relay frame header that indicates the status of the far end user device and the status of the PVC segment in the foreign network. A-law An analog to digital encoding scheme used to convert voice samples to an 8-bit data word used in CEPT E1 multiplex equipment. (See also -law.) ABR (Available Bit Rate) ATM connection type for bursty traffic, such as data.
AIT-T3 (ATM Interworking Trunk T3 Interface Card) The AIT-T3 backcard provides a T3 interface for the AIT (IPX switch) or BTM (IGX switch) ATM. alternate routing An automatic rerouting of a failed connection by a node to a new route through the network to maintain service. AMI (Alternate Mark Inversion) The line code used for T1 and E1 lines where the “1s” or “marks” on the line alternate between positive polarity and negative polarity.
B8ZS (Bipolar with Eight Zero Suppression) A T1 line protocol that converts a channel word with eight consecutive zeros into a code which, at the far end, is converted back to eight zeros. Allows 64 Kbps clear channel operation while assuring the ones density required on the T1 line. bandwidth reservation An IPX software feature that allows circuits to automatically become active (or “upped”) at a specified time and date and downed at some later time and date.
BNI (BPX Network Interface Card) The front card used to network BPX switches together and to connect to AXIS shelves, and IPX and IGX nodes configured as shelves. Supports T-3, E-3, and OC3 trunks carrying ATM cells. BPX Switch A high-speed broadband, high-capacity ATM cell relay network switch from for private and public networks. BRI (Basic Rate Interface) ISDN interface composed of two B channels and one D channel for circuit-switched communication of voice, video, and data. Compare with PRI.
Cell A unit of data with a fixed number of bytes. For ATM the cell size is 53 bytes. cell relay A form of digital communications using fixed length cells consisting of data and a small header IPX FastPacket was an early implementation of cell relay. The 53 byte ATM cell consists of data and a small header. CEPT CEPT is the European Conference of Posts and Telecommunications Administrations.
control port An RS-232 port on the face plate of a back card for a controller card (BCC, NPC, NPM.) that may used for connecting a control terminal. This port is bi-directional. COS (Class of Service) The priority assigned each user connection. Defines which circuits get rerouted first during a network failure. courtesy downing A software feature that is used to conserve network bandwidth by automatically “downing” a voice connection when the signalling status indicates an inactive (on-hook) circuit.
DDS (Digital Data Service) An AT&T dial-up data service offering for 2.4 to 56 Kbps over subscriber loop cable. Requires a Data Service Unit, DSU, at customer premise for interface to the DDS trunk. Device Code The first 8 bits of a FastPacket Address. DFM (Data Frame Multiplexing) An optional feature that saves data channel bandwidth by analyzing data channel content and suppressing repetitive data patterns. Dial Access Switching Another name for the INS Dial-Up Frame Relay application.
DSI (Digital Speech Interpolation) An algorithm that analyzes DS0 voice bits for non-speech codes. Suppresses these bits to conserve packet line bandwidth and inserts a code to indicate to the far end that these bits have been removed. Similar to DFM for data channels. Also, referred to as VAD (Voice Activity Detection). DTE (Data Terminal Equipment) As defined by the RS-232 standard, any device that generates or utilizes information. (See also, DCE.) E E1 European transmission service at the rate of 2.
frame forwarding A software feature allowing point-to-point frame relay type connection for various data applications that do not conform to the Frame Relay Interface Specification. FPC (FastPAD Back Card) The FPC is used with an FTC (IPX switch) or FTM (IGX switch) card. The FPC provides either a T1, E1, V.35, or X.21 interface. frame relay connection class A tag for a frame relay circuit which indicates the class of service to be provided for this connection.
FTC (FastPAD Trunk Card) An IPX frame relay front card that provides an interface to a FastPAD. The FTC is used with an FPC backcard. that provides either a T1, E1, V.35, or X.21 interface. FTM (FastPAD Trunk Module) An IPX frame relay front card that provides an interface to a FastPAD. G gateway A node that is configured to handle both T1 and E1 packet and circuit lines for direct interface international circuits. (See also Seamless International IPX Network.
IPX Switch A narrowband cell relay network switch from for private and public networks. ISDN (Integrated Services Digital Network) A service provided by the telephone company or OCC that supports combined customer voice and data connections over the twisted pair subscriber loop. Requires special equipment at the customer premise and a connecting central office switch that is capable of providing ISDN. J J1 A.
local addressing A frame relay addressing convention that uses the DLCI to identify the IPX frame relay port at the interface between the user device and the frame relay network. In local addressing, a particular DLCI is used only at the local FR connection. The DLCI may be reused at any other IPX node in the network. local alarm An IPX alarm indicating that the associated T1 line is down due to a local failure of its receive path.
node An IPX/IGX/BPX switch serving as a connection point to the network. At a node, connections from service lines are routed to trunks for transmission to other nodes in the network. NPC (Network Processor Card) Micro-processor based system controller front card that contains the software used to operate the IPX switch. NPM (Network Processor Module) Micro-processor based system controller front card that contains the software used to operate the IGX switch.
partially-interleaved EIA One control lead in each direction, generally RTS-CTS, is transmitted in same byte as seven data bits. For fast control lead response to data being turned on and off. PBX (private branch exchange) Digital or analog telephone switchboard, classified as customer premise equipment (CPE), used to connect private and public telephone networks. PCM (Pulse Code Modulation) The system for transmitting telephone signals digitally.
Q Q.921/Q.931 ITU-T specifications for the ISDN use network interface (UNI) data link layer. QSIG A common-channel message-oriented signalling protocol, defined by the European Telecommunications Standard Institute (ETSI), commonly used by private branch exchanges (PBXes). The INS Dynamic Network Switching application supports QSIG signalling to the Cisco WAN switching network. queue A buffer that is used to temporarily hold data while it waits to be transmitted to the network or to the user.
RS-449 The physical interface for the RS422 and R423 electrical interfaces. Contains the Processor Controller Card and the PCC utility bus, and provides system timing and control via the system bus. S SAR (Segmentation and Reassembly) The process of breaking a dataframe containing data from a number of virtual paths or circuits apart so that the individual paths/circuits can be switched by reassembling the data into a new frame with a different sequence.
speech detection Determining the presence or absence of speech for Digital Speech Interpolation. Performed in either the CDP card or VDP card in an IPX node. split clock A data clocking configuration where the timing for the transmit data is obtained from one source (e.g. user device) and the timing for the receive data is obtained from another source (e.g. IPX switch). Status Enquiry A message transmitted by a FR NNI port requesting an updated status from the attached foreign network.
timestamp A field in certain FastPacket formats that indicates the amount of time the packet has spent waiting in queues during the transmission between its source and destination nodes. Used to control the delay experienced by the packet. Trm An upper bound on the time between RM cells for an active source, i.e., RM cell must be sent at least once every Trm msec. trunk A physical link between two nodes.
V.35 A data communications interface standard adopted by the CCITT. Often used for data circuits operating at 56 Kbps and above. VAD (Voice Activity Detection) Used to statistically compress voice by not sending packets in the absence of speech. VBR (Variable Bit Rate) Connection type for variable bit rate traffic such as bursty data. Compare with CBR and ABR. VC_Q Frame relay buffer allocation parameter that specifies the maximum queue size reserved in the FRP card for the FR connection.
XON/XOFF A simple communications protocol for controlling the flow of data from one device to another. An XON sent from a receiving device indicates it is ready to accept data and the transmitting device may begin to output data. An XOFF from the receiving device indicates that it can no longer store any more data and the transmitting device should temporarily cease transmitting.
IN DEX A AAL 2-11 classes of traffic 2-11 AAL5 Frame Base Traffic Control 7-9 ABR 5-4 ABR (Available Bit Rate) 7-3 ABR and ATFST Connections 7-17 ABR Connection Policing 7-35 ABR STD 7-10 AC Power Supplies 2-4 adaptation FastPacket to ATM 2-14 adaptation layers and traffic classes 2-12 addshelf command 8-11 ADTF 7-10 air intake grille 2-3 AIT card 2-15 Alarm/Status Monitor 3-12 arbiter 3-3, 3-4 ASI features 5-3, 5-12 Line Module 5-8, 5-10 line statistics 5-14 ASM (see Alarm/Status Monitor) ASM controls 3-1
D DC Power input 2-4 Power Entry Module 2-3, 11-9 diagnostics 1-6, 1-24 Dijkstra’s Shortest Path Algorithm 1-21 display card status 11-4 DLCI 0 8-5 DNS Installation and Operation manual overview xxvi documentation conventions xxviii E e PNNI signali 8-5 EFCI 7-10 Egress from ASI 5-3 ER 7-4 ESP 8-1, 8-8 Application interfaces 8-9 redundant pairs 8-9 Y cables 8-10 Ethernet LAN port 3-3 Ethernet port 8-8 explicit rate 7-4 Extended Services Processor 8-1 See ESP F FAIL lights 11-2 fans 2-3 FastPacket to ATM 2
redundancy options 1-24 Synchronization 1-18 non-blocking 3-4 Nrm 7-10 nrt-VBR (Non-Real Time Variable Bit Rate) Role Resolution protocol 8-9 rt-VBR (Real-Time Variable Bit Rate) 7-3 O OptiClass 1-15, 1-19 P PCR 7-9 PEM (DC Power Entry Module) 11-9 PEM (see DC Power Entry Module) physical description 2-1 Physical Layer Convergence Protocol 4-3 Physical Layer Protocol Processor 4-3 PLCP (see Physical Layer Convergence Protocol) 4-3 PLPP (see Physical Layer Protocol Processor) 4-5 PLPP functions 4-5 PNNI
TFTP 8-9 throttled 4-5 Topolog 8-4 Traffic 7-23 traffic classes and adaptation layers 2-12 Traffic Policing 7-23 Traffic Policing Definitions 7-8 Trm 7-10 troubleshooting the BPX 11-1 TSR 9-16 U UBR (Unspecified Bit Rate) 7-3 UBR Connection Policing 7-35 UBR Connections 7-22 UNI 8-4 UNI header 2-8 User Service Interfaces 1-18 V VBR 5-4, 5-12 VBR and ATFR Connections 7-14 VBR Dual-Leaky Bucket Policing 7-26 VC Qdepth 7-10 VCI 4-5, 5-4, 5-12 VCI/VPI, description 2-11 Virtual circuit connections (VCCs) 1-17
Feedback on the Cisco BPX 8600 Series Reference, 78-5391-01 Release 9.1, May 1998 Documentation Response Card Feedback on the Cisco BPX 8600 Series Reference, Release 9.1, May 1998 Please respond to the following statements by checking a number from 1 to 5: 5 Strongly agree 4 Somewhat agree 3 Neutral 2 Somewhat disagree 1 Strongly disagree Overall, I am satisfied with this document.
FIRST-CLASS MAIL PERMIT NO.