Cisco BPX 8620, BPX 8650, BPX 8680, BPX 8680-IP Installation And Configuration Manual

Download

Page 1

Cisco BPX 8600 Series Installation and Configuration

Release 9.3.30 August 2001

Corporate Headquarters

Cisco Systems, Inc. 170 West Tasman Drive San Jose, CA 95134-1706 USA http://www.cisco.com Tel: 408 526-4000

800 553-NETS (6387)

Fax: 408 526-4100

Customer Order Number: DOC-7812907= Text Part Number: 78-12907-01 Rev. E0

Page 2

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.

THE SOFTWARE LICENSE AND LIMITED WARRANTY FOR THE ACCOMPANYING PRODUCT ARE SET FORTH IN THE INFORMATION PACKET THAT SHIPPED WITH THE PRODUCT AND ARE INCORPORATED HEREIN BY THIS REFERENCE. IF YOU ARE UNABLE TO LOCATE THE SOFTWARE LICENSE OR LIMITED WARRANTY, CONTACT YOUR CISCO REPRESENTATIVE FOR A COPY.

The following information is for FCC compliance of Class A devices: This equipment has been tested and found to comply with the limits for a Class A digital device, pursuant to part 15 of the FCC rules. These limits are designed to provide reasonable protection against harmful interference when the equipment is operated in a commercial environment. This equipment generates, uses, and can radiate radio-frequency energy and, if not installed and used in accordance with the instruction manual, may cause harmful interference to radio communications. Operation of this equipment in a residential area is likely to cause harmful interference, in which case users will be required to correct the interference at their own expense .

The following information is for FCC compliance of Class B devices: The equipment described in this manual generates and may radiat e radio-frequency energy. I f it is not inst alled in accordance with Cisco’s installation instructions, it may cause interference with radio and television reception. This equipment has been teste d and found to comply with the limits for a Class B digital device in accordance with the specifications in part 15 of the FCC rules. These specifications are designed to provide reasonable protection against such interference in a residential installation. However, there is no guarantee that interference will not occur in a particular installa tion.

Modifying the equipment without Cisco’s written authorization may result in the equipment no longer complying with FCC requirements for Class A or Class B digital devices. In that event, your right to use the equipment may be limited by FCC regulations, and you may be required to correct any interference to radio or television communications at your own expense.

You can determine whether your equipment is causing interference by turning it off. If the interference stops, it was probably caused by the Cisco equipment or one of its peripheral devices. If the equipment causes interference to radio or television reception, try to correct the interference by using one or more of the following measures:

• Turn the television or radio antenna until the interference stops.

• Move the equipment to one side or the other of the television or radio.

• Move the equipment farther away from the television or radio.

• Plug the equipment into an outlet that is on a different circuit from the television or radio. (That is, make certain the equipment and the television or radio are on circuits controlled by different circuit breakers or fuses.)

Modifications to this product not authorized by Cisco Systems, Inc. could void the FCC approval and negate your authority to operate the product.

The Cisco implementation of TCP header compression is an adaptation of a program developed by the University of California, Berkeley (UCB) as part of UCB’s public domain version of the UNIX operating system. All rights reserved. Copyright © 1981, Regents of the University of California.

NOTWITHSTANDING ANY OTHER WARRANTY HEREIN, ALL DOCUMENT FILES AND SOFTWARE OF THESE SUPPLIERS ARE PROVIDED “AS IS” WITH ALL FAULTS. CISCO AND THE ABOVE-NAMED SUPPLIERS DISCLAIM ALL WARRANTIES, EXPRESSED OR IMPLIED, INCLUDING, WITHOUT LIMITATION, THOSE OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OR ARISING FROM A COURSE OF DEALING, USAGE, OR TRADE PRACTICE.

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.

AccessPath, AtmDirector, Browse with Me, CCIP, CCSI, CD-PAC, CiscoLink, the Cisco Powered Network logo, Cisco Systems Networking Academy, the Cisco Systems Networking Academy logo, Cisco Unity, Fast Step, Follow Me Browsing, FormShare, FrameShare, IGX, Internet Quotient, IP/VC, iQ Breakthrough, iQ Expertise, iQ FastTrack, the iQ Logo, iQ Net Readiness Scorecard, MGX, the Networkers logo, ScriptBuilder, ScriptShare, SMARTnet, TransPath, Voice LAN, Wavelength Router, and WebViewer are trademarks of Cisco Systems, Inc.; Changing the Way We Work, Live, Play, and Learn, and Discover All That’s Possible are service marks of Cisco Systems, Inc.; and Aironet, ASIST, BPX, Catalyst, CCDA, CCDP, CCIE, CCNA, CCNP, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, the Cisco IOS logo, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Empowering the Internet Generation, Enterprise/Solver, EtherChannel, EtherSwitch, FastHub, FastSwitch, GigaStack, IOS, IP/TV, LightStream, MICA, Network Registrar, Packet, PIX, Post-Routing, Pre-Routing, RateMUX, Registrar, SlideCast, StrataView Plus, Stratm, SwitchProbe, TeleRouter, and VCO are registered trademarks of Cisco Systems, Inc. and/or its affiliates in the U.S. and certain other countries.

All other trademarks mentioned in this document or Web site are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (0110R)

Cisco BPX 8600 Series Installation and Configuration

Page 3

Cisco Reader Comment Card

General Information

1 Years of networking experience Years of experience with Cisco products

2 I have these network types: LAN Backbone WAN

Other:

3 I have these Cisco products: Switches Routers

Other: Specify model(s)

4 I perform these types of tasks: H/W Install and/or Maintenance S/W Config

Network Management Other:

5 I use these types of documentation: H/W Install H/W Config S/W Config

Command Reference Quick Reference Release Notes Online Help Other:

6 I access this information through: Cisco Connection Online (CCO) CD-ROM

Printed docs Other:

% %

7 Which method do you prefer?

8 I use the following three product features the most:

% %

Document Information

Document Title: Cisco BPX 8600 Series Installation and Configuration

Part Number: 78-12907-01 Rev. E0 S/W Release (if applicable): Release 9.3.30

On a scale of 1–5 (5 being the best) please let us know how we rate in the following areas:

The document was written at my

The information was accurate.

technical level of understanding.

The document was complete. The information I wanted was easy to find.

The information was well organized. The information I found was useful to my job.

Please comment on our lowest score(s):

Mailing Information

Company Name Date

Contact Name Job Title

Mailing Address

City State/Province ZIP/Postal Code

Country Phone ( ) Extension

Fax ( ) E-mail

Can we contact you further concerning our documentation? Yes No

You can also send us your comments by e-mail to bug-doc@cisco.com, or fax your comments to us at (408) 527-8089.

Page 4

BUSINESS REPLY MAIL

FIRST-CLASS MAIL PERMIT NO. 4631 SAN JOSE CA

ATTN DOCUMENT RESOURCE CONNECTION

CISCO SYSTEMS INC

170 WEST TASMAN DRIVE

SAN JOSE CA 95134-9883

POSTAGE WILL BE PAID BY ADDRESSEE

UNITED STATES

IN THE

NO POSTAGE

NECESSARY

IF MAILED

Page 5

About This Guide xxxiii

Objectives xxxiii

Audience xxxiv

Organization xxxiv

Cisco WAN Switching Product Name Change xxxvi

Related Documentation xxxvi

Cisco WAN Manager Release 10.5 Documentation xxxvi

Cisco MGX 8850 Release 2.1 Documentation xxxvii

SES PNNI Release 1.1 Documentation xxxviii Cisco WAN Switching Software, Release 9.3 Documentation xxxviii

MGX 8850 Multiservice Switch, Release 1.1.40 Documentation xxxix

MGX 8250 Edge Concentrator, Release 1.1.40 Documentation xl MGX 8230 Multiservice Gateway, Release 1.1.40 Documentation xli

Conventions xli

Obtaining Documentation xliv

World Wide Web xliv

Documentation CD-ROM xliv Ordering Documentation xliv

Documentation Feedback xliv

Obtaining Technical Assistance xlv

Cisco.com xlv Technical Assistance Center xlv

Cisco TAC Web Site xlvi

Cisco TAC Escalation Center xlvi

PART

1 The BPX Switch

CHAPTER

1 The BPX Switch: Functional Overview 1-1

The BPX 8600 Series 1-1

BPX 8620 1-2

BPX 8650 1-3

BPX 8680 1-4 BPX 8680-IP 1-4

New with Release 9.3.30 1-5

Release 9.3.30, Part Number 78-12907-01 Rev. E0, May 2005

Cisco BPX 8600 Series Installation and Configuration

iii

Page 6

Contents

Discontinued 1-5

BPX Switch Operation 1-6

The BPX Switch with MGX 8220, MGX 8230, and MGX 8250 Shelves 1-6

Multiprotocol Label Switching 1-7

Private Network to Network Interface 1-8 Virtual Private Networks 1-9

MPLS Virtual Private Networks 1-9

Frame Relay to ATM Interworking 1-10

Network Interworking 1-11

Service Interworking 1-12

Tiered Networks 1-13

Routing Hubs and Interface Shelves 1-13

BPX Switch Routing Hubs 1-14

BPX Routing Hubs in a Tiered Network 1-15 Tiered Network Implementation 1-16

Upgrades 1-17

Network Management 1-18 Inverse Multiplexing ATM 1-18

Virtual Trunking 1-19

Traffic and Congestion Management 1-20

Advanced CoS Management 1-21 Automatic Routing Management 1-21

Cost-Based Routing Management 1-22

Priority Bumping 1-22

Concurrent Routing 1-22

ABR Standard with VS/VD Congestion Control 1-24

Optimized Bandwidth Management (ForeSight) Congestion Control 1-25

Network Management 1-26

Cisco WAN Manager 1-26

Network Interfaces 1-27

Service Interfaces 1-28 Statistical Alarms and Network Statistics 1-28

Node Synchronization 1-29

Switch Software Description 1-29

Connections and Connection Routing 1-30 Connection Routing Groups 1-30

Cost-Based Connection Routing 1-31

Major Features of Cost-Based Automatic Routing Management 1-32

Cost-Based Automatic Routing Management Commands 1-33

Cisco BPX 8600 Series Installation and Configuration

Release 9.3.30, Part Number 78-12907-01 Rev. E0, May 2005

Page 7

Network Synchronization 1-34

Switch Availability 1-34

Node Redundancy 1-34

Node Alarms 1-35

Contents

CHAPTER

2 BPX Switch Physical Overview 2-1

BPX Switch Enclosure 2-1

Node Cooling 2-2 Node DC Powering 2-3

Optional AC Power Supply Assembly 2-4

Card Shelf Configuration 2-5

BPX Switch Major Hardware Component Groups 2-6

Service Expansion Shelf PNNI 2-7

Optional Peripherals 2-8

3 BPX Switch Common Core Components 3-1

Broadband Controller Card 3-2

Features 3-3 Functional Description 3-4

Front Panel Description 3-5

Back Cards for the BCC-4V 3-7

Alarm/Status Monitor Card 3-10

Features 3-10

Functional Description 3-10

Front Panel Description 3-11 Line Module for the Alarm/Status Monitor Card 3-13

BPX Switch StrataBus 9.6 and 19.2 Gbps Backplanes 3-15

CHAPTER

4 BNI (Trunk) Cards 4-1

BPX Switch Network Interface Group 4-1

Broadband Network Interface Cards (BNI-T3 and BNI-E3) 4-2

Features 4-3

Functional Description 4-3

Bandwidth Control 4-5

Loopbacks and Diagnostics 4-5

Front Panel Indicators 4-6

T3 and E3 Line Modules (LM-3T3 and LM-3E3) 4-8

OC-3, Line Modules (SMF, SMFLR, & MMF) 4-11

Release 9.3.30, Part Number 78-12907-01 Rev. E0, May 2005

Cisco BPX 8600 Series Installation and Configuration

Page 8

Contents

Y-Cabling of BNI Back Card, SMF-2-BC 4-14

CHAPTER

5 BXM Card Sets: T3/E3, 155, and 622 5-1

Overview: BXM Cards 5-1

BXM Capabilities 5-5

ATM Layer 5-5

Service Types 5-6

Virtual Interfaces 5-7 Enhanced BXM 5-7

BXM Front Card Indicators 5-9

BXM Back card Connectors 5-12

Y-Cabling of SMF-622 Series Back Cards 5-19

Automatic Protection Switching Redundancy 5-20

BXM Functional Description 5-22

Operation in Port (UNI/NNI) Mode 5-22

Operation in Trunk Mode 5-24 Summary of Circuitry Functions 5-26

DRSIU 5-26

SONET/SDH UNI (SUNI) 5-26

Demultiplexing and Multiplexing 5-27

RCMP 5-27

SABRE 5-27

Ingress and Egress Queue Engines 5-28

SIMBA 5-28

ACP Subsystem Processor 5-28

PART

2 Installation

CHAPTER

6 Installation Overview 6-1

Cisco BPX 8600 Series Installation and Configuration

Fault Management and Statistics 5-29

Port Mode 5-29

Trunk Mode 5-30

Channel Statistics Level 5-30

Technical Specifications 5-32

Physical Layer 5-32

General Information 5-33

Summary of an Installation Procedure 6-1

Installation Sequence Flow 6-2

Release 9.3.30, Part Number 78-12907-01 Rev. E0, May 2005

Page 9

Lines, Trunks, and Connection Configuration 6-3

Contents

CHAPTER

7 Preliminary Steps Before Installing 7-1

Site Preparation 7-1

Parts Checklist 7-2

Safety Requirements 7-3

CEPT Requirements 7-3

EMI Requirements 7-3

Laser Safety Guidelines 7-3 Maintaining Safety with Electricity 7-4

Basic Guidelines 7-4

Power and Grounding 7-5

Mechanical Installation 7-6

Horizontal Positioning 7-6

Vertical Positioning 7-8

Installing a BPX Switch Shelf, Preliminary Steps 7-8

8 Installation with Cisco Cabinets including 7000 Series Routers 8-1

Installing a BPX Switch in a Cisco Cabinet 8-1

Preliminary Procedure 8-3

CHAPTER

Installing a 7200 or 7500 Router in a BPX 8650 Cabinet or Rack 8-7

Installing Router Assembly in a Cisco Cabinet 8-9

Installing Router Assembly in a 19-Inch Open Rack 8-10 Installing Router Assembly in a 23-Inch Open Rack 8-11

9 Installation in Customer Cabinet 9-1

Installing a BPX Switch, Rear Rail Setback at 30-inch 9-1

Preliminary Procedure 9-1

10 Installing the DC Shelf 10-1

Preparing for DC Power Installation 10-1

DC Power Input Connections 10-1

Card Slot Fuses 10-5

Fan Power Fuses 10-6

11 Installing the AC Shelf 11-1

Installing an AC Power Supply Tray 11-1

Installing an AC Power Supply 11-7

Release 9.3.30, Part Number 78-12907-01 Rev. E0, May 2005

Cisco BPX 8600 Series Installation and Configuration

vii

Page 10

Contents

AC Power Input Connections 11-9

Card Slot Fuses 11-11

Fan Power Fuses 11-12

CHAPTER

12 Installing the T3/E3 Cable Management Tray 12-1

Installation of Cable Management Tray 12-1

Installing Tray Brackets 12-1

Installing Tray 12-2

Raising Tray for Access to PEMs 12-4

Installing BXM T3/E3 Cable Bracket 12-4

Connecting Cables to BXM T3/E3 Cards 12-5

Routing Cables from Cards through Cable Management Tray 12-7

Tray Raised with Cables in Place 12-8

13 Installing the BPX Switch Cards 13-1

Installing the Cards 13-1

Installing Front Cards 13-4 Installing Back Cards 13-6

Verifying 9.6 or 19.2 Gbps Backplane 13-7

Upgrading to BCC-4 Cards 13-9

Specifying Card Redundancy 13-10

CHAPTER

viii

Installation of APS Redundant Frame Assembly and Back Cards 13-12

APS 1:1 Redundancy Installation 13-12

APS 1+1 Redundancy Installation 13-13

14 Connecting Cables 14-1

Making T3 or E3 Connections 14-1

Making a BXM OC-3 or OC-12 Connection 14-4

Making a BXM T3/E3 Connection 14-7

Setting up the BME OC-12 Port Loop 14-8

Alarm Output Connections 14-9

15 Connecting Temporary Terminal and Attaching Peripherals 15-1

Temporarily Connecting a Terminal or NMS to the Control Port 15-2

Powering Up the Control Terminal 15-4

Connecting a Network Printer to the BPX Switch 15-6

Auxiliary Port Parameters for Okidata 184 Local Printer 15-7

Cisco BPX 8600 Series Installation and Configuration

Release 9.3.30, Part Number 78-12907-01 Rev. E0, May 2005

Page 11

DIP Switch Settings for Okidata 184 15-7 Attaching a Local Printer 15-8

Connecting Dial-In and Dial-Out Modems 15-11

Motorola V.34R BPX Switch Dial-In Configuration 15-13

Enabling BPX Switch Auto-Answer (Dial-In to BPX switch) 15-13 Enabling Auto-Dial to Cisco Customer Service 15-15

Making External Clock Connections 15-17

Contents

CHAPTER

16 Checking and Powering-Up 16-1

BPX Switch Startup Diagnostic 16-2

Provisioning the BPX Switch 16-3

PART

3 Initial Configuration and Network Management

CHAPTER

17 Initial BPX 8600 Node Configuration 17-1

Summary of Configuration Procedures 17-2

Initial Node Configuration Summary 17-2

Command Sequences for Setting Up Nodes 17-4

Summary of Commands 17-5

CHAPTER

18 Configuring Trunks and Adding Interface Shelves 18-1

Configuring Trunks 18-1

Setting Up a Trunk 18-2

Reconfiguring a Trunk 18-3 Removing a Trunk 18-5

Displaying or Printing Trunk Configurations 18-6

Adding an Interface Shelf 18-6

CHAPTER

19 Configuring Circuit Lines and Ports 19-1

Setting Up a Circuit Line 19-1

Flow Diagram for ATM Line Setup 19-2 Line Commands 19-2

Setting Up Ports and Virtual Ports 19-3

Virtual Ports 19-4

Local Management Interface and Integrated Local Management Interface 19-5

Early Abit Notification with Configurable Timer on LMI/ILMI Interface 19-6 Configuring Early Abit Notification 19-6

Recommended Settings 19-7

Release 9.3.30, Part Number 78-12907-01 Rev. E0, May 2005

Cisco BPX 8600 Series Installation and Configuration

Page 12

Contents

Behavior with Previous Releases 19-8

Performance Considerations 19-8

ILMI Neighbor Discovery 19-9

Configuring the BPX for ILMI Neighbor Discovery 19-9

Publishing the BXM Interface Information 19-10

Configuring the ILMI Management IP address 19-11

Displaying Neighbors 19-11

CHAPTER

20 Configuring Network Management 20-1

LAN Connection for the Network Management Station 20-2

Configuring the BPX Switch LAN and IP Relay 20-3

Configuring the Cisco WAN Manager Workstation 20-5

Configuring the LAN Port 20-6

Controlling External Devices 20-10

PART

4 Configuring Connections

CHAPTER

21 Configuring ATM Connections 21-1

ATM Connection Services 21-1

Setting Up an ATM Connection 21-2

Traffic Management Overview 21-3

Standard Available Bit Rate 21-5

VS/VD Description 21-5

BXM Connections 21-6 ForeSight Congestion Control 21-6

ATM Connection Requirements 21-6

Overview of Procedure to add ATM Connections 21-7

Connection Routing 21-7 addcon Command Syntax 21-8

addcon Example 21-8

ATM Connection Flow 21-10

ATM Connection Flow through the BPX 21-10 Advanced CoS Management 21-10

Connection Flow Example 21-11

Ingress from CPE 1 to BXM 3 21-11

Egress to Network via BXM 10 21-12

Ingress from Network via BXM 5 21-12

Egress from BXM 11 to CPE 2 21-12

Cisco BPX 8600 Series Installation and Configuration

Release 9.3.30, Part Number 78-12907-01 Rev. E0, May 2005

Page 13

Traffic Shaping for CBR, rt-VBR, nrt-VBR, and UBR 21-13

Traffic Shaping Rates 21-14

Configuration 21-15

Configuring VBR Connections 21-16 Connection Criteria 21-18

Configuring Connection Policing 21-18

Configuring Resources 21-19

Trunk Queues for rt-VBR and nrt-VBR 21-19

Port Queues for rt-VBR and nrt-VBR 21-20

Related Switch Software Commands 21-20

ATM Connection Configuration 21-22

Minimum SCR and PCR 21-26

Constant Bit Rate Connections 21-27

Variable Bit Rate Connections 21-28

Connection Criteria for real-time VBR and nonreal-time VBR Connections 21-29

Available Bit Rate Connections 21-31

Available Bit Rate Standard Connections 21-32 Available Bit Rate Foresight Connections 21-33

Unspecified Bit Rate Connections 21-34

ATM-to-Frame Relay Network Interworking Connections 21-35 Frame Relay-to-ATM Foresight Network Interworking Connection 21-36

Frame Relay-to-ATM Transparent Service Interworking Connections 21-37

Frame Relay-to-ATM Foresight Transparent Service Interworking Connections 21-38 Frame Relay-to-ATM Translational Service Interworking Connections 21-39

Frame Relay-to-ATM Foresight Translational Service Interworking Connections 21-40

Contents

Traffic Policing Examples 21-41

Dual-Leaky Bucket (An Analogy) 21-42 CBR Traffic Policing Examples 21-42

Variable Bit Rate Dual-Leaky Bucket Policing Examples 21-45

Leaky Bucket 1 21-46 Leaky Bucket 2 21-47

Examples 21-47

ABR Connection Policing 21-51 UBR Connection Policing 21-51

Leaky Bucket 1 21-51

Leaky Bucket 2 21-52

ATM Command List 21-54

Release 9.3.30, Part Number 78-12907-01 Rev. E0, May 2005

Cisco BPX 8600 Series Installation and Configuration

Page 14

Contents

CHAPTER

22 Configuring Frame Relay to ATM Network and Service Interworking 22-1

Service Interworking 22-4

Networking Interworking 22-4

ATM Protocol Stack 22-7

OAM Cells 22-8

ATF Features 22-8

ATF Limitations 22-8 ATF Connection Criteria 22-9

ATF Connection Management 22-9

Structure 22-9 Channel Statistics 22-10

OAM Cell Support 22-10

Diagnostics 22-11

Commands 22-11

Virtual Circuit Features 22-11

Commands 22-12

Connection Management 22-12

Routing 22-12

Bandwidth Management 22-13

User Interface 22-13 Port Management 22-13

Signaling 22-13

Alarms 22-14

CHAPTER

xii

23 Configuring BXM Virtual Switch Interface 23-1

Virtual Switch Interface 23-2

Multiple Partitioning 23-2

Multiprotocol Label Switching 23-2

MPLS Terminology 23-3

Overview: How VSI Works 23-3

Virtual Switch Interfaces and Qbins 23-3

VSI Master and Slaves 23-4

Connection Admission Control 23-6 Partitioning 23-7

Multiple Partitioning 23-8

Compatibility 23-9

Resource Partitioning 23-9

Partitioning Between Automatic Routing Management and VSI 23-9

Multiple Partition Example 23-10

Cisco BPX 8600 Series Installation and Configuration

Release 9.3.30, Part Number 78-12907-01 Rev. E0, May 2005

Page 15

VSI Configuration Procedures 23-12

Adding a Controller 23-12

Viewing Controllers and Interfaces 23-13

Deleting a Controller 23-13 Configuring Partition Resources on Interfaces 23-14

Configuring Enhanced BXM Cards to Support 60K Connections 23-15

Soft and Dynamic Partitioning 23-15 Assigning a Service Template to an Interface 23-16

SCT Commands 23-17

Configuring the BXM Card’s Qbin 23-17 Enabling VSI ILMI Functionality for the PNNI Controller 23-18

VSIs and Virtual Trunking 23-19

VSI Master and Slave Redundancy 23-19

Master Redundancy 23-21 Slave Redundancy 23-21

VSI Slave Redundancy Mismatch Checking 23-22

What Happens When You Add a Controller 23-22 What Happens When You Delete a Controller 23-23

What Happens When a Slave Is Added 23-23

What Happens When a Slave is Deleted 23-24 Managing Resources 23-24

VSI Slave Redundancy (Hot Slave Redundancy) 23-24

Contents

Class of Service Templates and Qbins 23-25

How Service Class Templates Work 23-25 Structure of Service Class Templates 23-26

Extended Service Types Support 23-28

Supported Service Categories 23-29 Supported Service Types 23-29

VC Descriptors 23-30

VC Descriptor Parameters 23-34 Qbin Dependencies 23-35

Qbin Default Settings 23-36

Understanding MPLS VC Merge 23-39

VC Merge Characteristics 23-40 Displaying Card Support for VC Merge 23-41

Enabling VC Merge 23-41

Disabling VC Merge 23-42 Interpreting the Messages 23-44

Displaying the Status of VC Merge 23-44

Release 9.3.30, Part Number 78-12907-01 Rev. E0, May 2005

Cisco BPX 8600 Series Installation and Configuration

xiii

Page 16

Contents

Summary of VSI Commands 23-44

CHAPTER

24 Configuring BXM Virtual Trunks 24-1

Overview 24-1

Typical ATM Hybrid Network with Virtual Trunks 24-2

Benefits of Virtual Trunking 24-3

How Virtual Trunking Works 24-4

Virtual Trunks Across a Public ATM Cloud 24-5 Routing with Virtual Trunks 24-6

Handling VPC Failure Within the ATM Cloud 24-7

Connection Management 24-7

Cell Header Formats 24-7

Bit Shifting for Virtual Trunks 24-8

Virtual Trunk Bandwidth 24-8

Virtual Trunk Connection Channels 24-8 Cell Transmit Address Translation 24-9

Cell Receive Address Lookup 24-9

Selection of Connection Identifier 24-9 Routing VPCs over Virtual Trunks 24-9

VPC Configuration with the ATM Cloud 24-9

Virtual Trunk Interfaces 24-10 Virtual Trunk Traffic Classes 24-10

Virtual Trunk Transmit Queuing 24-10

CHAPTER

xiv

General Procedures to Set Up Virtual Trunking 24-12

Setting up the ATM Cloud 24-12 Setting up a Virtual Trunk through an ATM cloud 24-13

Virtual Trunk Across an ATM Network Example 24-14

Command Overview 24-16

Primary Configuration Commands 24-16

APS Redundancy 24-17 Virtual Trunk Commands 24-17

Virtual Trunk Commands Common to BXM and UXM 24-18

Virtual Trunk UXM Commands 24-19 Virtual Trunk BXM/BNI Commands 24-19

25 Configuring SONET Automatic Protection System 25-1

Introduction 25-1

Implementation for BXM Cards 25-2

Tiered Management Control 25-2

Cisco BPX 8600 Series Installation and Configuration

Release 9.3.30, Part Number 78-12907-01 Rev. E0, May 2005

Page 17

Manual Operation 25-3

Operation Criteria 25-4

APS Front Card Displays 25-5

APS 1+1 LED Displays 25-5

APS 1+1 (Card and Line Redundancy) 25-5

APS 1+1 Redundancy Criteria 25-7 Application Notes for APS 1+1 25-8

Using switchcdred/switchyred command 25-8

Notes on switchcdred 25-9 Notes on switchapsln 25-9

Configuring APS 1+1 25-9

APS 1:1 (Line Redundancy) 25-10

General Criteria 25-11 Configuration Criteria 25-11

Configuring APS 1:1 25-11

Contents

CHAPTER

APS 1 +1 Annex B Card and Line Redundancy 25-12

General Criteria 25-12 Configuring APS 1+1 Annex B 25-12

Test Loops 25-13

Notes on APS Messages 25-13

APS K1 Command Precedence 25-13

APS Command Summary 25-14

26 Configuring BME Multicasting 26-1

Introduction 26-1

BME Features 26-2

BME Requirements 26-2 BME Restrictions 26-2

Address Criteria 26-2

Connection Management Criteria 26-3 Connection Management with Cisco WAN Manager 26-3

BME Operation 26-3

BME Cell Replication 26-3

Cell Replication Stats 26-4 Adding Connections 26-4

Multisegment Multicast Connections 26-5

Multicast Statistics 26-6 Policing 26-6

Release 9.3.30, Part Number 78-12907-01 Rev. E0, May 2005

Cisco BPX 8600 Series Installation and Configuration

Page 18

Contents

Hot Standby Backup 26-7

Configuration 26-7

CHAPTER

27 Alarms and Statistics 27-1

Automatic Alarm Reporting to Cisco Customer Service 27-1

Network Statistics 27-2

APS Alarms 27-3

What APS Alarms Represent 27-6

Trunk Statistics 27-8

Trunk Alarms 27-11

Physical and Logical Trunk Alarm Summary 27-11

Event Logging 27-12

Error Messages 27-12

BME Alarms 27-13

OAM cells 27-13

AIS cells 27-13

Qbin Statistics 27-14

Interval Statistics 27-14

Summary and Counter Statistics 27-15

PART

5 Troubleshooting and Maintenance

CHAPTER

xvi

28 Troubleshooting 28-1

Preventive Maintenance 28-1

Software Error and Abort Tables 28-1

Troubleshooting the BPX Switch 28-2

General Troubleshooting Procedures 28-2

Displaying the Status of Cards in the Node 28-4 System Troubleshooting Tools 28-5

User-Initiated Tests 28-5

Loopback Tests 28-6

Connection Testing 28-8

External Device Window 28-8

Troubleshooting SONET Automatic Protection System 28-9

APS Configuration Problems 28-10

Not Able to Correctly Set Up APS 1+1 Line Redundancy Configuration 28-10 Unable to Set Up APS 1:1 Line Redundancy Configuration 28-10

Operator Information about APS Architectures 28-11

Cisco BPX 8600 Series Installation and Configuration

Release 9.3.30, Part Number 78-12907-01 Rev. E0, May 2005

Page 19

Operational Problems 28-11

Initial Investigation of APS Switch Operations 28-11

Unable to Perform APS External Switch After Forced or Manual APS Switch 28-12

APS Manual Switch to a Line Does Not Occur Right Away 28-12 Switch Occurs After Lockout Issued 28-12

APS Switch Made to a Line in Alarm 28-13

Reverse Switch 28-13 APS Switch Occurs at the Same Time as a Y-Red Switch 28-13

APS Switch Occurs After Issuing an APS Clear Switch 28-14

APS Switch Occurs Even Though APS Forced Switch in Effect 28-14 APS Line is Failing to Switch 28-14

Large Cell Loss When Performing a Front Card Switchover 28-14

APS Service Switch Description 28-14 APS Line Does Not Seem to Switch and Active Line is in Alarm 28-15

BXM Back Card LED Green and Yellow Indications 28-16

BXM Port LED States 28-16

Contents

BME Connection Diagnostics 28-16

Troubleshooting VSI Problems 28-16

How Channels Are Allocated and Deallocated 28-16

How Networking Channels Are Allocated 28-17

How Automatic Routing Management Channels Are Allocated/Configured 28-17 How SVC Channels are Allocated and Configured 28-17

How VSI Channels Are Assigned for VSI Master to Slave VCs 28-17

How VSI Channels Are Configured/Allocated 28-17 How Background Redundancy Channels Are Allocated 28-18

How IP Channels Are Allocated 28-18

How ILMI/LMI Channels Are Allocated 28-18 How ILMI Channels Are Allocated for VSI Partitions on Trunk Interfaces 28-18

How VSI Channels Are Assigned for Interslave VCs 28-18

mc_vsi_end_lcn 28-18 num chans 28-18

How Port Group Enters the Channel Assignment Picture 28-19

cnfrsrc Fails with “Available Channels is 0” 28-19 cnfrsrc Fails with “Automatic Routing Management is Currently Using the Channel

Space” 28-20

Troubleshooting Commands 28-20

CHAPTER

29 Replacing Parts 29-1

Replacing a Front Card 29-1

Release 9.3.30, Part Number 78-12907-01 Rev. E0, May 2005

Cisco BPX 8600 Series Installation and Configuration

xvii

Page 20

Contents

Replacing a Line Module 29-3

Replacing a DC Power Entry Module 29-5

Replacing an AC Power Supply 29-7

Field-Installing a Second AC Power Supply 29-8

Replacing the Fan Assembly 29-9

Replacing the Temperature Sensing Unit 29-10

Replacing Card Slot and Fan Fuses on the System Backplane 29-10

CHAPTER

30 BPX Node Specifications 30-1

ATM Trunk Interface (BXM-T3/E3 Cards) 30-3

ATM Trunk Interface (BXM-15zM-622 Cards) 30-3

ATM T3 Trunk Interface (BNI-T3, LM-3T3) 30-5

ATM E3 Trunk Interface (BNI-E3, LM-3E3) 30-5

ATM OC3 Trunk Interface (BNI-OC3, LM-OC3) 30-6

ATM Service Interface (BXM-T3/E3 Cards) 30-7

ATM Service Interface (BXM-155 Cards) 30-7

ATM Service Interface (BXM-622 Cards) 30-8

ATM Service Interface (ASI-1, LM-2T3) 30-8

ATM Service Interface (ASI-1, LM-2E3) 30-9

ATM Service Interface (ASI-2, LM-OC3) 30-9

PART

6 BPX Specifications

CHAPTER

31 BPX Switch Cabling Summary 31-1

Trunk Cabling 31-1

xviii

Power Cabling 31-2

AC Powered Nodes 31-2

DC Powered Nodes 31-2

LM-BCC Cabling 31-2

Auxiliary and Control Port Cabling 31-2 LAN Port Cabling 31-3

Modem Cabling 31-4

External Clock Input Cabling 31-4

T1 Clock Cabling 31-4

E1 Clock Cabling 31-5

External Alarm Cabling 31-6

Standard BPX Switch Cables 31-7

Cisco BPX 8600 Series Installation and Configuration

Release 9.3.30, Part Number 78-12907-01 Rev. E0, May 2005

Page 21

Redundancy “Y” Cable 31-8

Contents

CHAPTER

32 AT3-6ME (T3 to T2) Interface Adapter 32-1

Application 32-1

General Description 32-2

Equipment Description 32-2

Interface Connectors 32-2

Front Panel Indicators 32-3

DIP Switches 32-4

Installation 32-6

System Connections 32-6

AT3-6ME Configuration 32-6

BPX or IGX Port Configuration 32-7

Operation 32-8

Power-Up Sequence 32-8

Normal Operation 32-8

Remote Loop Operation 32-9 Terminal Operation 32-9

Commands 32-10

Specifications 32-11

PART

7 Appendices

APPENDIX

A Upgrade Information A-1

Upgrade BXM to BXM-E Cards A-1

Summary of Commands A-2

Upgrade Options A-3

Upgrade Protection from Release 9.3 to a Later Release A-4

Procedure A-5

Feature Mismatching A-6

Multiple VSI Partitions A-8

Functional Description of Feature Mismatch Checking A-9

Card Insertion/Mismatch Checking A-9

UI Commands and Enabling Feature Mismatch A-9

addyred/delyred Mismatch Checking A-9

Considerations for Feature Mismatch Checking A-10

Release 9.3.30, Part Number 78-12907-01 Rev. E0, May 2005

Cisco BPX 8600 Series Installation and Configuration

xix

Page 22

Contents

GLOSSARY

INDEX

Cisco BPX 8600 Series Installation and Configuration

Release 9.3.30, Part Number 78-12907-01 Rev. E0, May 2005

Page 23

Figure 1-1 BPX Switch General Configuration Example 1-3

Figure 1-2 IP VPN Service Example 1-9

Figure 1-3 MPLS VPNs Example 1-10

Figure 1-4 Frame Relay to ATM Network Interworking 1-12

Figure 1-5 Frame Relay to ATM Service Interworking 1-13

Figure 1-6 Tiered Network with BPX Switch and IGX Switch Routing Hubs 1-15

Figure 1-7 Tiered Network with BPX Routing Hubs 1-16

Figure 1-8 Virtual Trunking Example 1-19

Figure 1-9 Sequential Routing 1-23

Figure 1-10 Concurrent Routing 1-23

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 2-4

Figure 2-4 AC Power Supply Assembly Front View 2-4

Figure 2-5 BPX Switch Card Shelf Front View 2-5

FIGURES

Figure 2-6 Optional Peripherals Connected to BPX Switch 2-8

Figure 3-1 Common Core Group Block Diagram 3-2

Figure 3-2 BCC-4V Block Diagram 3-5

Figure 3-3 BCC Front Panel 3-6

Figure 3-4 BCC15-BC and BCC-3-BC Back Card Face Plate Connectors 3-9

Figure 3-5 ASM Front Panel Controls and Indicators 3-12

Figure 3-6 LMI-ASM Face Plate 3-14

Figure 4-1 BPX Switch Network Interface Group 4-2

Figure 4-2 Simplified BNI-T3, BNI-E3 Block Diagram 4-4

Figure 4-3 BNI-3T3 Front Panel (BNI-3E3 appears the same except for name) 4-7

Figure 4-4 LM-3T3 Faceplate, Typical 4-9

Figure 4-5 LM-3E3 Faceplate, Typical 4-10

Figure 4-6 LM-2OC-3-SMF Faceplate 4-12

Figure 4-7 LM-2OC-3-MMF Faceplate 4-13

Figure 4-8 Y-Cable (Model SMFY), LC-OC-3-SMF (Model SMF-2-BC) 4-14

Figure 5-1 A BPX Switch Network with BXM Cards 5-2

Release 9.3.30, Part Number 78-12907-01 Rev. E0, May 2005

Cisco BPX 8600 Series Installation and Configuration

xxi

Page 24

Figures

Figure 5-2 BXM-622 Front Panel, Two-Port Card Shown 5-10

Figure 5-3 BXM-155 Front Panel, Eight-Port Card Shown 5-11

Figure 5-4 BXM-T3/E3 Front Panel, 12-Port Card Shown 5-12

Figure 5-5 SMF-622-2, SMFLR-622-2, and SMFXLR-622-2 Back Card 5-13

Figure 5-6 BXM-155-8 Port back card, MMF, SMF, or SMFLR 5-14

Figure 5-7 BPX-STM1-EL-4 Back Card 5-16

Figure 5-8 BPX-T3/E3 Back Card, 12-Port Option Shown 5-18

Figure 5-9 Y-Cabling of SMF-622 Series Back Cards 5-19

Figure 5-10 BXM SMF-155-8R Back Card 5-21

Figure 5-11 BXM APS Redundant Frame Assembly 5-22

Figure 5-12 BXM Access Port Ingress Operation 5-23

Figure 5-13 BXM Port Egress Operation 5-24

Figure 5-14 BXM Trunk Ingress Operation 5-25

Figure 5-15 BXM Trunk Egress Operation 5-26

Figure 7-1 Laser Information Label 7-3

Figure 7-2 Cabinet Mounting Options for the BPX Shelf 7-7

Figure 7-3 BPX Shelf and T-Rail (Open Rack) or Equivalent Mounting Options 7-8

Figure 7-4 Rack Mounting Dimensions, DC Powered Shelf 7-9

Figure 7-5 Rack Mounting Dimensions, AC Powered Shelf 7-10

Figure 7-6 Removing an Air Intake Grille 7-13

Figure 7-7 Temporary Spacer Bar and Support Brackets Installation 7-14

Figure 7-8 BPX Switch Shelf Aligned with Temporary Support Brackets and Bar 7-14

Figure 8-1 Location of DC Power Entry Module(s), Cabinet Rear View 8-2

Figure 8-2 BPX Shelf Aligned with Temporary Support Brackets and Bar 8-3

Figure 8-3 BPX Shelf with Rear Rail Mounting at Setback of 19.86 inches 8-5

Figure 8-4 Rear Mounting Brackets, with 19.86 Inch Rear Rail Setback (DC Systems) 8-6

Figure 8-5 Rear Mounting Brackets, 19.86 Inch Rear Rail Setback (AC-Systems) 8-6

Figure 8-6 Assembly of Router in Router Enclosure 8-8

Figure 8-7 Installing the Router Enclosure Assembly in the Cisco BPX 7650 Cabinet 8-10

Figure 8-8 Installing the Router Enclosure Assembly in a 19-inch Open Rack 8-11

Figure 8-9 Installing the Router Enclosure Assembly in a 23-inch Open Rack 8-12

Figure 9-1 BPX Switch Aligned with Temporary Support Brackets and Spacer Bar 9-2

Figure 9-2 BPX Switch with Rear Rail Mounting at Setback of 30 Inches 9-3

Figure 9-3 Rear Mounting Brackets, Detail 9-4

Figure 9-4 Rear Mounting Brackets, with 30-inch Rear Rail Setback (DC Systems) 9-4

Cisco BPX 8600 Series Installation and Configuration

xxii

Release 9.3.30, Part Number 78-12907-01 Rev. E0, May 2005

Page 25

Figure 9-5 Rear Mounting Brackets, 30 Inch Rear Rail Setback (AC-Powered Systems) 9-5

Figure 10-1 DC Power 10-2

Figure 10-2 DC Power Connections—With Conduit Box 10-3

Figure 10-3 DC Power Connections—Without Conduit Box 10-4

Figure 11-1 Temporary Spacer Bracket and Support Bracket Installation 11-2

Figure 11-2 Power Supply Tray aligned with Temporary Support Brackets and Bar 11-3

Figure 11-3 Removing an Air Intake Grille 11-4

Figure 11-4 Securing AC Power Supply Tray, 30-Inch Rail Setback 11-5

Figure 11-5 Securing an AC Power Supply Tray, 19.86 inch Rear Rail Setback 11-6

Figure 11-6 AC Power Supply Tray with Redundant AC Inputs (view from rear) 11-7

Figure 11-7 Removing an Air Intake Grille 11-8

Figure 11-8 AC Power Supply Installation 11-9

Figure 11-9 AC Power Supply Connections (Dual and Single Versions Shown) 11-10

Figures

Figure 11-10 AC Power 11-11

Figure 12-1 Installation of Cable Management Tray Brackets 12-2

Figure 12-2 Sliding Cable Management Tray over Brackets 12-3

Figure 12-3 Cable Management Tray in Lowered Home Position 12-3

Figure 12-4 Cable Management Tray in Raised Position 12-4

Figure 12-5 Installing BXM T3/E3 Cable Bracket 12-5

Figure 12-6 Connecting Cables to T3/E3 Card 12-6

Figure 12-7 T3/E3 SMB Connector Detail 12-6

Figure 12-8 Cables Routed through Cable Management Tray in Lowered Position 12-7

Figure 12-9 Tray Raised with Cables in Place 12-8

Figure 13-1 BPX Shelf (front view) 13-3

Figure 13-2 BPX Shelf (rear view, DC shelf shown) 13-3

Figure 13-3 Removing an Air Intake Grille 13-5

Figure 13-4 Laser Information Label 13-6

Figure 13-5 Installing a Back Card 13-7

Figure 13-6 Card slot and fan fuses, identifying the 19.2 Gpbs backplane 13-8

Figure 13-7 Y-Cable Connection 13-11

Figure 13-8 Y-Cables on Multiple Ports 13-11

Figure 13-9 APS 1:1 Redundancy 13-13

Figure 13-10 APS 1+1 Redundancy 13-13

Figure 13-11 APS Redundant Frame Assembly 13-14

Figure 13-12 BPX Shelf, Rear View 13-15

Release 9.3.30, Part Number 78-12907-01 Rev. E0, May 2005

Cisco BPX 8600 Series Installation and Configuration

xxiii

Page 26

Figures

Figure 13-13 Installing APS Redundant Frame Assembly and Back Cards into Place 13-16

Figure 14-1 Connecting T3 Cables to BPX LM-T3 (BNI T3 back card) 14-2

Figure 14-2 Connecting Y-Cable Adapters to a T3 Port 14-4

Figure 14-3 Connecting Y-Cables to an OC-3-SMF Back Card 14-6

Figure 14-4 BXM T3/E3 Cable Connector Detail 14-7

Figure 14-5 Y-Cable for BXM T3/E3 Cards 14-8

Figure 14-6 Looping Ports 1 and 2 for BME on OC-12 Back Card 14-9

Figure 14-7 Alarm Output Connector 14-10

Figure 15-1 Temporary Connections to Bring up a New Node, LM-BCC Back Card 15-5

Figure 15-2 Temporary Connections to Bring up a New Node, LM-BCCs 15-6

Figure 15-3 Connections to a Network Printer, LM-BCC 15-10

Figure 15-4 Connecting Modems to the BPX Switch, LM-BCC 15-12

Figure 15-5 Dial-Modem Cabling for Auto Answer (Dial-In to BPX) 15-14

Figure 15-6 Dial Modem Cabling for Auto Dial (dial-out to customer service) 15-17

Figure 15-7 External Clock Source Connections to Back Cards for BCCs 15-18

Figure 17-1 Setting Up Nodes 17-4

Figure 17-2 Viewing the Node Configuration 17-4

Figure 17-3 Configuring the Node Interface for a Local Control Terminal 17-5

Figure 17-4 Removing a Node From the Network 17-5

Figure 17-5 Add an Interface Shelf to the Network 17-5

Figure 19-1 Setting Up ATM Lines 19-2

Figure 19-2 Ports and Lines 19-3

Figure 19-3 Port Bandwidth 19-4

Figure 20-1 LAN Connections to BCC Back Cards, LM-BCCs Shown 20-3

Figure 20-2 Cisco WAN Manager Physical LAN and IP Relay Network 20-4

Figure 20-3 Cisco WAN Manager LAN Connection via Gateway Router to a BPX Switch 20-8

Figure 20-4 Cisco WAN Manager LAN Connection to a BPX Switch (no gateway) 20-9

Figure 21-1 ATM Connections over a BPX Switch Network 21-3

Figure 21-2 ABR VS/VD Flow Control Diagram 21-5

Figure 21-3 ATM Connection Flow via BPX Switches 21-13

Figure 21-4 Traffic Shaping Example 21-14

Figure 21-5 rt-VBR and nrt-VBR Connection Prompt Sequence 21-19

Figure 21-6 CBR Connection Prompt Sequence 21-28

Figure 21-7 rt-VBR and nrt-VBR Connection Prompt Sequence 21-30

Figure 21-8 ABR Standard Connection Prompt Sequence 21-32

Cisco BPX 8600 Series Installation and Configuration

xxiv

Release 9.3.30, Part Number 78-12907-01 Rev. E0, May 2005

Page 27

Figure 21-9 Meaning of VS/VD and Flow Control External Segments 21-33

Figure 21-10 ABR ForeSight Connection Prompt Sequence 21-34

Figure 21-11 UBR Connection Prompt Sequence 21-35

Figure 21-12 ATFR Connection Prompt Sequence 21-36

Figure 21-13 ATFST Connection Prompt Sequence 21-37

Figure 21-14 ATFT Connection Prompt Sequence 21-38

Figure 21-15 ATFTFST Connection Prompt Sequence 21-39

Figure 21-16 ATFX Connection Prompt Sequence 21-40

Figure 21-17 ATFXFST Connection Prompt Sequence 21-41

Figure 21-18 CBR Connection, UPC Overview 21-43

Figure 21-19 CBR.1 Connection with Bucket Compliant 21-44

Figure 21-20 CBR.1 Connection, with Bucket Discarding nonCompliant Cells 21-44

Figure 21-21 VBR Connection, UPC Overview 21-46

Figures

Figure 21-22 VBR Connection, Policing = 4, Leaky Bucket 1 Compliant 21-47

Figure 21-23 VBR Connection, Policing = 4, Leaky Bucket 1 nonCompliant 21-48

Figure 21-24 VBR.2 Connection, Policing = 2, with Buckets 1 and 2 Compliant 21-48

Figure 21-25 VBR.2 Connection, Leaky Bucket 2 Discarding CLP (0) Cells 21-49

Figure 21-26 VBR.1 Connection, Policing = 1, with Buckets 1 and 2 Compliant 21-50

Figure 21-27 VBR.3 Connection, Policing = 3, with Bucket 2 non-Compliant 21-51

Figure 21-28 UBR Connection, UPC Overview 21-53

Figure 22-1 Frame Relay to ATM Network Interworking 22-2

Figure 22-2 Frame Relay to ATM Service Interworking 22-2

Figure 22-3 Frame Relay to ATM Interworking Examples with UXM Card on IGX Switch 22-3

Figure 22-4 Frame Relay to ATM Service Interworking Detail 22-4

Figure 22-5 Frame Relay to ATM NW Interworking Detail 22-5

Figure 22-6 ATF Connections, Simplified Example 22-6

Figure 22-7 ATM Layers 22-7

Figure 23-1 BXM Virtual Interfaces and Qbins 23-4

Figure 23-2 VSI, Controller and Slave VSI 23-5

Figure 23-3 VSI Master and VSI Slave Example 23-5

Figure 23-4 Cross-Connects and Links between Switches 23-6

Figure 23-5 Graphical View of Resource Partitioning, Automatic Routing Management, and VSI 23-8

Figure 23-6 Resource Partitioning Between Automatic Routing Management and VSI 23-10

Figure 23-7 Virtual Switches 23-11

Figure 23-8 Switch with Redundant Controllers to Support Master Redundancy 23-20

Cisco BPX 8600 Series Installation and Configuration

Release 9.3.30, Part Number 78-12907-01 Rev. E0, May 2005

xxv

Page 28

Figures

Figure 23-9 Service Template Overview 23-27

Figure 23-10 Service Template and Associated Qbin Selection 23-28

Figure 23-11 VC Merge Example 23-40

Figure 24-1 Typical ATM Hybrid Network using Virtual Trunks 24-3

Figure 24-2 Virtual and Physical Trunks on a BXM 24-4

Figure 24-3 BXM Egress VIrtual Interfaces and Qbins 24-5

Figure 24-4 Virtual Trunks across a Public ATM Network 24-6

Figure 24-5 ATM Virtual Trunk Header Types 24-8

Figure 24-6 Addition of Virtual Trunks Across a Public ATM Network 24-14

Figure 25-1 SONET Section, Line, and Path 25-3

Figure 25-2 APS 1+1 Redundancy 25-4

Figure 25-3 APS 1:1 Redundancy 25-4

Figure 25-4 APS 1+1 Redundancy, Installing APS Back Cards in APS Redundant Backplane 25-6

Figure 25-5 SONET APS 1+1 Detail 25-7

Figure 25-6 SONET APS 1:1 Detail 25-10

Figure 26-1 Replication of a Root Connection into Three Leaves 26-4

Figure 26-2 Example of Traffic, One Root and Two Leaves 26-4

Figure 26-3 Adding Multicasting Connections 26-5

Figure 26-4 Multi-Segment Multicast Connections 26-6

Figure 26-5 Statistics Collection 26-6

Figure 27-1 Automatic Alarm Reporting 27-2

Figure 27-2 OAM Cells 27-13

Figure 27-3 Alarms 27-13

Figure 28-1 Network Loopback Paths 28-7

Figure 29-1 Unlatching the Air Intake Grille 29-3

Figure 29-2 Removing a Line Module 29-4

Figure 29-3 DC Power Entry Module with Conduit Box 29-6

Figure 29-4 AC Power Supply Assembly 29-7

Figure 29-5 Removing Blank Filler Panel (B side shown) 29-8

Figure 29-6 Card Slot and Fan Fuse Locations on System Backplane 29-11

Figure 32-1 Network Application 32-1

Figure 32-2 Front and Rear Panel Features 32-5

Cisco BPX 8600 Series Installation and Configuration

xxvi

Release 9.3.30, Part Number 78-12907-01 Rev. E0, May 2005

Page 29

Table 1 Cisco WAN Manager Release 10.5 Documentation xxxvi

Table 2 WAN CiscoView Release 10 Documentation xxxvii

Table 3 Cisco MGX 8850 Switch Release 2.1 Documentation xxxvii

Table 4 SES PNNI Controller Release 1.1 Documentation xxxviii

Table 5 Cisco WAN Switching Release 9.3 Documentation xxxix

Table 6 MGX 8850 Multiservice Gateway Documentation xxxix

Table 7 MGX 8250 Multiservice Gateway Documentation xl

Table 8 MGX 8230 Multiservice Gateway Documentation xli

Table 1-1 Tier Network Definitions 1-17

Table 1-2 Routing Group Configuration Example 1-31

Table 1-3 Commands Used for Cost-Based Route Selection 1-33

Table 2-1 BPX Switch Plug-In Card Summary 2-6

Table 3-1 BCC Front Panel Indicators 3-5

Table 3-2 BCC15-BC Back Card for BCC-32, Connectors 3-7

Table 3-3 BCC-3-BC Back Card for BCC-4V 3-8

TABLES

Table 3-4 ASM Front Panel Controls and Indicators 3-11

Table 3-5 LM-ASM Face Plate Connectors 3-13

Table 4-1 BNI Front Panel Status Indicators 4-6

Table 4-2 BNI Front Panel Card Failure Indications 4-8

Table 4-3 LM-3T3 and LM-3E3 Connectors 4-8

Table 4-4 LM-OC-3-SMF and LM-OC-3-SMFLR Connectors 4-11

Table 4-5 LM-OC-3-MMF Connectors 4-11

Table 5-1 BXM T3/E3, BXM-155, and BXM 622 Front Card Options 5-3

Table 5-2 BXM-T3/E3, BXM-155, and BXM-622 Back Cards 5-4

Table 5-3 BXM Front Panel Status Indicators 5-9

Table 5-4 BXM Front Panel Card Failure Indicators 5-9

Table 5-5 BXM-622 back cards 5-13

Table 5-6 BXM-155 Back Cards 5-15

Table 5-7 BXM-STM1-EL4 Back Card 5-15

Table 5-8 BXM-T3/E3 Back Cards 5-17

Table 5-9 BXM Sonet APS 5-20

Release 9.3.30, Part Number 78-12907-01 Rev. E0, May 2005

Cisco BPX 8600 Series Installation and Configuration

xxvii

Page 30

Tables

Table 5-10 Channel Statistics Levels and Supported Number of Connections 5-31

Table 5-11 Channel Statistics per Level 5-31

Table 5-12 Fiber Optic Characteristics OC-12 5-33

Table 5-13 Fiber Optic Characteristics OC-3 5-33

Table 13-1 BXM SONET APS 13-12

Table 15-1 Control Port Parameters for Local Control (PC or Workstation) 15-2

Table 15-2 Auxiliary Port Parameters for Okidata 184 Printer 15-7

Table 15-3 Switch A Settings—Okidata 184 Printer 15-7

Table 15-4 Switch 1 Settings—Okidata 184 Printer 15-8

Table 15-5 Switch 2 Settings—Okidata 184 Printer 15-8

Table 15-6 Modem Interface Requirements 15-11

Table 17-1 Commands for Setting Up a Node 17-5

Table 18-1 Supported Card Types 18-2

Table 18-2 Interface Types Supported on the Same Card 18-3

Table 18-3 Trunk Configuration Commands 18-6

Table 18-4 Interface Shelf Designations 18-7

Table 19-1 Line Commands 19-2

Table 19-2 ILMI Parameters 19-5

Table 19-3 LMI Parameters 19-6

Table 19-4 ILMI Neighbor Discovery Parameters 19-9

Table 19-5 Advertise Intf Info Parameter 19-10

Table 20-1 BPX Switch Commands 20-4

Table 20-2 Parameters for the cnflan Command 20-7

Table 21-1 Standard ATM Traffic Classes 21-3

Table 21-2 Traffic Parameters 21-4

Table 21-3 Quality of Service Parameters 21-4

Table 21-4 addcon Command Field Descriptions 21-8

Table 21-5 Standard ATM Type and addcon 21-10

Table 21-6 ATM to Frame Relay Network and Service Interworking 21-10

Table 21-7 Traffic Shaping Rates 21-14

Table 21-8 Traffic Policing Definitions 21-23

Table 21-9 Connection Parameters with Default Settings and Ranges 21-24

Table 21-10 Connection Parameter Descriptions 21-25

Table 21-11 Supported Cards and Performance Specifications 21-27

Table 21-12 CBR Policing Definitions 21-28

Cisco BPX 8600 Series Installation and Configuration

xxviii

Release 9.3.30, Part Number 78-12907-01 Rev. E0, May 2005

Page 31

Table 21-13 VBR Policing Definitions 21-30

Table 21-14 UBR Policing Definitions 21-35

Table 21-15 Policing Options for VBR Connections 21-45

Table 21-16 ATM Connection Commands 21-54

Table 23-1 ifci Parameters (Virtual Switch Interface) 23-7

Table 23-2 Partition Criteria 23-7

Table 23-3 Commands Used for Multiple Partitioning 23-10

Table 23-4 Partitioning Example 23-11

Table 23-5 cnfrsrc Parameters, Ranges/Values, and Descriptions 23-14

Table 23-6 Commands Used for the Service Class Template 23-17

Table 23-7 Service Category Listing 23-29

Table 23-8 Service Category Listing 23-30

Table 23-9 VSI Special Service Types 23-31

Tables

Table 23-10 ATM Forum Service Types, CBR, UBR, and ABR 23-31

Table 23-11 ATM Forum VBR Service Types 23-32

Table 23-12 MPLS Service Types 23-33

Table 23-13 Connection Parameter Descriptions and Ranges 23-34

Table 23-14 Service Template Qbn Parameters 23-36

Table 23-15 Qbin Default Settings 23-36

Table 23-16 Service Class Template Default Settings 23-37

Table 23-17 Messages for VC Merge 23-44

Table 23-18 Commands for Setting up a VSI Controller 23-44

Table 24-1 Virtual Trunk Parameters 24-4

Table 24-2 Virtual Trunk Traffic Types 24-11

Table 24-3 VPI Ranges 24-12

Table 24-4 Commands Used for Primary Configuration 24-16

Table 24-5 Virtual Trunk Commands Common to BXM and UXM (IGX) 24-18

Table 24-6 Virtual Trunk UXM Commands 24-19

Table 24-7 Virtual Trunk Commands BXM/BNI 24-19

Table 25-1 BXM SONET APS 25-2

Table 25-2 SONET Section, Line, and Path Descriptions 25-3

Table 25-3 Digital Hierarchies 25-3

Table 25-4 BXM Front Card LED Display 25-5

Table 25-5 BXM Back Card for APS 1+1 LED Display 25-5

Table 25-6 K1 Switching Conditions 25-13

Release 9.3.30, Part Number 78-12907-01 Rev. E0, May 2005

Cisco BPX 8600 Series Installation and Configuration

xxix

Page 32

Tables

Table 25-7 APS Commands 25-14

Table 27-1 Typical Statistics Collected 27-2

Table 27-2 APS Alarms 27-3

Table 27-3 APS Alarms Representation 27-7

Table 27-4 Trunk Statistics 27-9

Table 27-5 Physical and Logical Trunk Alarms 27-11

Table 27-6 IGX Log Messaging for Activating and Adding a VT 27-12

Table 27-7 BPX Log Messaging for Activating and Adding a VT 27-12

Table 27-8 Interval Statistics Commands 27-14

Table 27-9 Summary and Counter Statistics Commands 27-15

Table 28-1 Troubleshooting the BPX Switch 28-3

Table 28-2 Card Status for the BPX Switch 28-4

Table 28-3 System Troubleshooting Commands Available 28-5

Table 28-4 System Loopback Tests 28-6

Table 28-5 Troubleshooting Command List 28-20

Table 30-1 Ambient Temperature and Humidity Limits 30-2

Table 31-1 Trunk Cables 31-1

Table 31-2 AC Power Cables 31-2

Table 31-3 DC Power Wiring 31-2

Table 31-4 Auxiliary and Control Port Cabling 31-3

Table 31-5 Auxiliary and Control Port Pin Assignments 31-3

Table 31-6 LAN Port Cabling 31-3

Table 31-7 LAN Port Pin Assignments 31-4

Table 31-8 External Clock Cabling 31-4

Table 31-9 T1 Connection to XFER TMG on BCC-bc 31-5

Table 31-10 T1 Connection to EXT TMG on BCC-bc 31-5

Table 31-11 T1 Connection to EXT 1 or EXT 2 on BCC-3-bc 31-5

Table 31-12 E1 Connector Pin Assignments for External Clock 31-5

Table 31-13 E1 Connection 75 Ohm to EXT TMG on BCC-bc or BCC-3-bc 31-6

Table 31-14 E1 Connection 100/120 Ohm to EXT TMG on BCC-bc 31-6

Table 31-15 E1 Connection 100/120 Ohm to EXT 1 or EXT 2 on BCC-3-bc 31-6

Table 31-16 External Alarm Cabling 31-6

Table 31-17 Network Alarm Pin Assignments 31-7

Table 31-18 Standard Cables Available from Cisco 31-8

Table 31-19 Redundancy Y-Cables 31-8

Cisco BPX 8600 Series Installation and Configuration

xxx

Release 9.3.30, Part Number 78-12907-01 Rev. E0, May 2005

Page 33

Table 32-1 Rear Panel Connectors 32-3

Table 32-2 Front Panel Indicators 32-3

Table 32-3 DIP Switch SW-1 Selection Guide 32-6

Table 32-4 DIP Switch SW-2 Selection Guide 32-7

Table 32-5 Alarm Handling 32-8

Table 32-6 DIP Switch Settings 32-9

Table 32-7 Command Summary 32-10

Table 32-8 Status Display 32-10

Table 32-9 T3 Interface 32-11

Table 32-10 T2 Interface 32-11

Table 32-11 Power 32-11

Table 32-12 Mechanical 32-11

Table 32-13 Terminal Interface 32-12

Tables

Table A-1 BXM-BXM-E Upgrade Commands A-2

Table A-2 Upgrade Options A-3

Table A-3 Configuration Commands to Support Mismatch Verification A-6

Table A-4 Upgrading Firmware When Single Active Card and Y-Cable is in Use A-7

Table A-5 Mismatch Conditions if Number of Channels Changes A-8

Release 9.3.30, Part Number 78-12907-01 Rev. E0, May 2005

Cisco BPX 8600 Series Installation and Configuration

xxxi

Page 34

Tables

xxxii

Cisco BPX 8600 Series Installation and Configuration

Release 9.3.30, Part Number 78-12907-01 Rev. E0, May 2005

Page 35

Objectives

About This Guide

This chapter discusses the objectives, audience, organization, and conventions of the Cisco BPX 8600 Series Installation and Configuration.

This publication is the primary Cisco guide to install and configure the BPX 8600 Series wide-area switches. It provides:

• Description and specifications of the switch hardware, chassis, cards, cables, and peripherals

• Description of WAN switch software

• Procedures for the installation of the switch, cards, cables, control terminals

• Procedures for initial startup.

• Procedures for configuring the BPX cards

• Procedures for configuring lines and trunks

• Procedures for provisioning (making connections to your network).

The 8600 series of Broadband Packet Exchange switches include:

• BPX 8620 wide-area switch

• BPX 8650 IP + ATM switch

• BPX 8680 universal service switch

• BPX 8680-IP (BPX+MGX8800+7204LSC)

Instructions for configuring MPLS on BPX switches, refer to the Cisco MPLS Controller Software Configuration Guide.

Instructions for configuring PNNI on BPX switches, refer to the Cisco SES PNNI Controller Software Configuration Guide.

All terms are defined in the Glossary.

Refer to current Release Notes for additional supported features.

Release 9.3.30, Part Number 78-12907-01 Rev. E0, May 2005

Cisco BPX 8600 Series Installation and Configuration

xxxiii

Page 36

Audience

This publication is intended for those installing the BPX 8600 series broadband network switches. Installers should be familiar with electronic circuity and electrical wiring practices and should have experience as an electronic or electromechanical technician.

It is also intended for the network administrator performing initial BPX configuration. Both the installers and the network administrator should be familiar with BPX network operation. Administrators should be familiar with LAN and WAN protocols and current networking technologies such as Frame Relay and AT M.

Organization

This guide is organized as follows:

About This Guide

• Chapter 1, “The BPX Switch: Functional Overview,” introduces BPX 8600 Series broadband

switches and describes the main networking functions.

• Chapter 2, “BPX Switch Physical Overview,” describes the physical components of the BPX switch.

• Chapter 3, “BPX Switch Common Core Components,” describes the common core hardware

components for the BPX switch.

• Chapter 4, “BNI (Trunk) Cards,” describes the Broadband Network Interface (BNI) card and

associated back cards.

• Chapter 5, “BXM Card Sets: T3/E3, 155, and 622,” describes the physical BXM card sets, major

circuit functions, and technical specifications.

• Chapter 6, “Installation Overview,” describes an overview of the procedures used for configuration.

• Chapter 7, “Preliminary Steps Before Installing,” describes the preliminary steps to ensure safety

and reliability.

• Chapter 8, “Installation with Cisco Cabinets including 7000 Series Routers,” provides the

installation procedures for the Cisco cabinets along with the 7000 series routers.

• Chapter 9, “Installation in Customer Cabinet,” provides installation steps for the mechanical

placement of a BPX switch shelf in a standard 19-inch customer-supplied equipment cabinet or rack with a rear rail setback at 30 inches.

• Chapter 10, “Installing the DC Shelf,” explains how to connect the DC power supply to the BPX

switch.

• Chapter 11, “Installing the AC Shelf,” explains how to install the AC shelf.

• Chapter 12, “Installing the T3/E3 Cable Management Tray,” provides instructions for the

installation of the optional cable management tray that you can use to route cables in an open-rack, nonredundant configuration.

• Chapter 13, “Installing the BPX Switch Cards,” explains how to install the BPX switch cards, check

for a 9.6 or 19.2 Gbps backplane, connect line and trunk cables, connect peripherals, connect to a network management station, initial power up, and initial configuration.

xxxiv

• Chapter 14, “Connecting Cables,” explains how to connect trunk and circuit line cables.

• Chapter 15, “Connecting Temporary Terminal and Attaching Peripherals,” explains how to set up a

temporary terminal or network management station for initial power-up and to attach other peripherals.

Cisco BPX 8600 Series Installation and Configuration

Release 9.3.30, Part Number 78-12907-01 Rev. E0, May 2005

Page 37

About This Guide

Organization

• Chapter 16, “Checking and Powering-Up,” explains how to check that you are ready and then

perform the initial power-up.

• Chapter 17, “Initial BPX 8600 Node Configuration,” guides you through the initial node

configuration that must be done before you can set up network management.

• Chapter 18, “Configuring Trunks and Adding Interface Shelves,” describes how to configure trunks

and add interface shelves.

• Chapter 19, “Configuring Circuit Lines and Ports,” describes how to configure circuit lines and

ports.

• Chapter 20, “Configuring Network Management,” describes the initial procedures to set up a

permanent network management station.

• Chapter 21, “Configuring ATM Connections,” explains how to establish ATM connection services

by adding ATM connections between ATM service interface ports in the network using ATM standard UNI 3.1 and Traffic Management 4.0.

• Chapter 22, “Configuring Frame Relay to ATM Network and Service Interworking,” describes

Frame Relay to ATM interworking.

• Chapter 23, “Configuring BXM Virtual Switch Interface,” describes the BXM Virtual Switch

Interface (VSI) and provides configuration procedures.

• Chapter 24, “Configuring BXM Virtual Trunks,” describes the Broadband Switch Module (BXM)

virtual trunks.

• Chapter 25, “Configuring SONET Automatic Protection System,” contains a description and

configuration information for the SONET Automatic Protection System (APS).

• Chapter 26, “Configuring BME Multicasting,” presents an overview of multicasting, a description

of the BME card used on the BPX switch for multicasting for PVCs, and configuration instructions.

• Chapter 27, “Alarms and Statistics,” describes some of the tools provided for detecting and

identifying network and equipment problems that are available to the network operator.

• Chapter 28, “Troubleshooting,” describes periodic maintenance procedures and general

troubleshooting procedures.

• Chapter 29, “Replacing Parts,” describes the replacement of major BPX switch components.

• Chapter 30, “BPX Node Specifications,” lists information for the BPX system specifications.

• Chapter 31, “BPX Switch Cabling Summary,” specifies the cabling required to install the BPX

switch.

• Chapter 32, “AT3-6ME (T3 to T2) Interface Adapter,” describes the AT3-6ME Interface Adapter,

sometimes referred to as the T3-T2 Interface Adapter.

• Appendix A, “Upgrade Information,” provides special upgrade information.

A glossary and an index is also included.

Release 9.3.30, Part Number 78-12907-01 Rev. E0, May 2005

Cisco BPX 8600 Series Installation and Configuration

xxxv

Page 38

Cisco WAN Switching Product Name Change

The Cisco WAN Switching products were once known by older names.

Old Name New Name

Any switch in the BPX switch family (Cisco BPX® 8620 broadband switch and Cisco BPX® 8650 broadband switch)

The BPX Service Node switch The Cisco BPX® 8620 broadband switch

The BPX switch as a Label Switch Controller The Cisco BPX® 8650 broadband switch

The AXIS shelf The Cisco MGX™ 8220 edge concentrator

Any switch in the IGX switch family (IGX 8, IGX 16, and IGX 32 wide-area switches)

The IGX 8 switch The Cisco IGX™ 8410 multiband switch

The IGX 16 switch The Cisco IGX™ 8430 multiband switch.

Cisco StrataView Plus® Cisco WAN Manager® (CWM)

A Cisco BPX® 8600 series broadband switch

The Cisco IGX™ 8400 series multiband switch

About This Guide

Conventions

DOC-7813594=

Conventions

Command descriptions use these conventions:

• Commands and keywords are in boldface.

• Arguments for which you supply values are in italics.

• Elements in square brackets ([ ]) are optional.

• Alternative but required keywords are grouped in braces ({ }) and are separated by vertical bars ( | ).

Examples use these conventions:

• Terminal sessions and information the system displays are in screen font.

• Information you enter is in boldface screen font.

• Nonprinting characters, such as passwords, are in angle brackets (< >).

• Default responses to system prompts are in square brackets ([ ]).

Release 9.3.30, Part Number 78-12907-01 Rev. E0, May 2005

Cisco BPX 8600 Series Installation and Configuration

xli

Page 44

Conventions

About This Guide

Note Means reader take note. Notes contain helpful suggestions or references to materials not contained

in this manual.

Caution Means reader be careful. In this situation, you might do something that could result in equipment

damage or loss of data.

xlii

Cisco BPX 8600 Series Installation and Configuration

Release 9.3.30, Part Number 78-12907-01 Rev. E0, May 2005

Page 45

About This Guide

Conventions

Warning

Waarschuwing

Varoitus

Attention

Warnung

Avvertenza

Means danger. You are in a situation that could cause bodily injury. Before you work on any equipment, be aware of the hazards involved with electrical circuitry and be familiar with standard practices for preventing accidents.

Dit waarschuwingssymbool betekent gevaar. U verkeert in een situatie die lichamelijk letsel kan veroorzaken. Voordat u aan enige apparatuur gaat werken, dient u zich bewust te zijn van de bij elektrische schakelingen betrokken risico's en dient u op de hoogte te zijn van standaard maatregelen om ongelukken te voorkomen.

Tämä varoitusmerkki merkitsee vaaraa. Olet tilanteessa, joka voi johtaa ruumiinvammaan. Ennen kuin työskentelet minkään laitteiston parissa, ota selvää sähkökytkentöihin liittyvistä vaaroista ja tavanomaisista onnettomuuksien ehkäisykeinoista.

Ce symbole d'avertissement indique un danger. Vous vous trouvez dans une situation pouvant causer des blessures ou des dommages corporels. Avant de travailler sur un équipement, soyez conscient des dangers posés par les circuits électriques et familiarisez-vous avec les procédures couramment utilisées pour éviter les accidents.

Dieses Warnsymbol bedeutet Gefahr. Sie befinden sich in einer Situation, die zu einer Körperverletzung führen könnte. Bevor Sie mit der Arbeit an irgendeinem Gerät beginnen, seien Sie sich der mit elektrischen Stromkreisen verbundenen Gefahren und der Standardpraktiken zur Vermeidung von Unfällen bewußt.

Questo simbolo di avvertenza indica un pericolo. La situazione potrebbe causare infortuni alle persone. Prima di lavorare su qualsiasi apparecchiatura, occorre conoscere i pericoli relativi ai circuiti elettrici ed essere al corrente delle pratiche standard per la prevenzione di incidenti.

Advarsel

Dette varselsymbolet betyr fare. Du befinner deg i en situasjon som kan føre til personskade. Før du utfører arbeid på utstyr, må du vare oppmerksom på de faremomentene som elektriske kretser innebærer, samt gjøre deg kjent med vanlig praksis når det gjelder å unngå ulykker.

Aviso

Este símbolo de aviso indica perigo. Encontra-se numa situação que lhe poderá causar danos físicos. Antes de começar a trabalhar com qualquer equipamento, familiarize-se com os perigos relacionados com circuitos eléctricos, e com quaisquer práticas comuns que possam prevenir possíveis acidentes.

¡Atención!

Este símbolo de aviso significa peligro. Existe riesgo para su integridad física. Antes de manipular cualquier equipo, considerar los riesgos que entraña la corriente eléctrica y familiarizarse con los procedimientos estándar de prevención de accidentes.

Varning!

Denna varningssymbol signalerar fara. Du befinner dig i en situation som kan leda till personskada. Innan du utför arbete på någon utrustning måste du vara medveten om farorna med elkretsar och känna till vanligt förfarande för att förebygga skador.

Timesaver Means the described action saves time. You can save time with this action.

Release 9.3.30, Part Number 78-12907-01 Rev. E0, May 2005

Cisco BPX 8600 Series Installation and Configuration

xliii

Page 46

Obtaining Documentation

The following sections explain how to obtain documentation from Cisco Systems.

World Wide Web

You can access the most current Cisco documentation on the World Wide Web at the following URL:

http://www.cisco.com

Translated documentation is available at the following URL:

http://www.cisco.com/public/countries_languages.shtml

Documentation CD-ROM

Cisco documentation and additional literature are available in a Cisco Documentation CD-ROM package, which is shipped with your product. The Documentation CD-ROM is updated monthly and may be more current than printed documentation. The CD-ROM package is available as a single unit or through an annual subscription.

About This Guide

Ordering Documentation

Cisco documentation is available in the following ways:

• Registered Cisco Direct Customers can order Cisco product documentation from the Networking

Products MarketPlace:

http://www.cisco.com/cgi-bin/order/order_root.pl

• Registered Cisco.com users can order the Documentation CD-ROM through the online Subscription

Store:

http://www.cisco.com/go/subscription

• Nonregistered Cisco.com users can order documentation through a local account representative by

calling Cisco corporate headquarters (California, USA) at 408 526-7208 or, elsewhere in North America, by calling 800 553-NETS (6387).

Documentation Feedback

If you are reading Cisco product documentation on Cisco.com, you can submit technical comments electronically. Click Feedback at the top of the Cisco Documentation home page. After you complete the form, print it out and fax it to Cisco at 408 527-0730.

You can e-mail your comments to bug-doc@cisco.com.

xliv

Cisco BPX 8600 Series Installation and Configuration

Release 9.3.30, Part Number 78-12907-01 Rev. E0, May 2005

Page 47

About This Guide

To submit your comments by mail, use the response card behind the front cover of your document, or write to the following address:

Cisco Systems Attn: Document Resource Connection 170 West Tasman Drive San Jose, CA 95134-9883

We appreciate your comments.

Obtaining Technical Assistance

Cisco provides Cisco.com as a starting point for all technical assistance. Customers and partners can obtain documentation, troubleshooting tips, and sample configurations from online tools by using the Cisco Technical Assistance Center (TAC) Web Site. Cisco.com registered users have complete access to the technical support resources on the Cisco TAC Web Site.

Cisco.com

Obtaining Technical Assistance

Cisco.com is the foundation of a suite of interactive, networked services that provides immediate, open access to Cisco information, networking solutions, services, programs, and resources at any time, from anywhere in the world.

Cisco.com is a highly integrated Internet application and a powerful, easy-to-use tool that provides a broad range of features and services to help you to

• Streamline business processes and improve productivity

• Resolve technical issues with online support

• Download and test software packages

• Order Cisco learning materials and merchandise

• Register for online skill assessment, training, and certification programs

You can self-register on Cisco.com to obtain customized information and service. To access Cisco.com, go to the following URL:

http://www.cisco.com

Technical Assistance Center

The Cisco TAC is available to all customers who need technical assistance with a Cisco product, technology, or solution. Two types of support are available through the Cisco TAC: the Cisco TAC Web Site and the Cisco TAC Escalation Center.

Inquiries to Cisco TAC are categorized according to the urgency of the issue:

• Priority level 4 (P4)—You need information or assistance concerning Cisco product capabilities,

product installation, or basic product configuration.

• Priority level 3 (P3)—Your network performance is degraded. Network functionality is noticeably

impaired, but most business operations continue.

Release 9.3.30, Part Number 78-12907-01 Rev. E0, May 2005

Cisco BPX 8600 Series Installation and Configuration

xlv

Page 48

Obtaining Technical Assistance

• Priority level 2 (P2)—Your production network is severely degraded, affecting significant aspects

• Priority level 1 (P1)—Your production network is down, and a critical impact to business operations

Which Cisco TAC resource you choose is based on the priority of the problem and the conditions of service contracts, when applicable.

Cisco TAC Web Site

The Cisco TAC Web Site allows you to resolve P3 and P4 issues yourself, saving both cost and time. The site provides around-the-clock access to online tools, knowledge bases, and software. To access the Cisco TAC Web Site, go to the following URL:

http://www.cisco.com/tac

All customers, partners, and resellers who have a valid Cisco services contract have complete access to the technical support resources on the Cisco TAC Web Site. The Cisco TAC Web Site requires a Cisco.com login ID and password. If you have a valid service contract but do not have a login ID or password, go to the following URL to register:

About This Guide

of business operations. No workaround is available.

will occur if service is not restored quickly. No workaround is available.

http://www.cisco.com/register/

If you cannot resolve your technical issues by using the Cisco TAC Web Site, and you are a Cisco.com registered user, you can open a case online by using the TAC Case Open tool at the following URL:

http://www.cisco.com/tac/caseopen

If you have Internet access, it is recommended that you open P3 and P4 cases through the Cisco TAC Web Site.

Cisco TAC Escalation Center

The Cisco TAC Escalation Center addresses issues that are classified as priority level 1 or priority level 2; these classifications are assigned when severe network degradation significantly impacts business operations. When you contact the TAC Escalation Center with a P1 or P2 problem, a Cisco TAC engineer will automatically open a case.

To obtain a directory of toll-free Cisco TAC telephone numbers for your country, go to the following URL:

http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml

Before calling, please check with your network operations center to determine the level of Cisco support services to which your company is entitled; for example, SMARTnet, SMARTnet Onsite, or Network Supported Accounts (NSA). In addition, please have available your service agreement number and your product serial number.

xlvi

Cisco BPX 8600 Series Installation and Configuration

Release 9.3.30, Part Number 78-12907-01 Rev. E0, May 2005

Page 49

ART

The BPX Switch

Page 50

Page 51

CHAPT E R

The BPX Switch: Functional Overview

This chapter introduces the BPX 8600 Series broadband switches and describes the main networking functions.

Contents of this chapter include:

• The BPX 8600 Series

• New with Release 9.3.30

• Discontinued

• BPX Switch Operation

• Traffic and Congestion Management

• Network Management

• Switch Software Description

• Network Synchronization

• Switch Availability

Also, refer to the Cisco WAN Switching Command Reference publications.

Refer to Release Notes for additional supported features.

The BPX 8600 Series

Cisco BPX 8600 series wide-area switches offer a variety of service interfaces for data, video, and voice traffic, and support numerous connectivity options to address a broad range of diverse needs. Network interface options include broadband (T3/E3 to OC-12/STM-4) and narrowband (64 Kbps to n x T1/E1) through leased lines or public ATM services. Additionally, the BPX switch provides a cost-effective solution by offering a wide range of port densities through the MGX 8220 and MGX 8800 edge concentrators. Proven in the world's largest networks, the Cisco BPX 8620, 8650, and 8680 help you to anticipate and meet market demands while eliminating technology risk.

The Cisco BPX® 8600 series wide-area switches are standards-based high-capacity broadband ATM switches that provide backbone ATM switching, IP+ATM services including Multiprotocol Label Switching (MPLS) with trunk and CPU hot standby redundancy. The BPX 8600 series deliver a wide range of other user services (see Figure 1-1).

The BPX 8600 Series includes:

• BPX 8620 wide-area switch

• BPX 8650 IP+ATM switch

Release 9.3.30, Part Number 78-12907-01 Rev. E0, May 2005

Cisco BPX 8600 Series Installation and Configuration

1-1

Page 52

The BPX 8600 Series

BPX 8620

Chapter 1 The BPX Switch: Functional Overview

• BPX 8680 universal service node

• BPX 8680-IP (BPX + MGX 8850 + 7204 LSC)

The Cisco BPX 8620 switch is a scalable, standards-compliant unit, fully compatible with:

• Cisco MGX™ 8800 series wide-area edge switch

• Cisco MGX 8200 series edge concentrator

• Cisco IGX™ 8400 series wide-area switch

• Cisco Service Expansion Shelf

The BPX multishelf architecture integrates both IP and ATM services; therefore, enabling you to deploy widest range of value-added services in the industry. This architecture offer low-cost entry points for small sites up to unprecedented port density and scalability for the very largest sites. Finally, it supports both broadband services and narrowband services within a single platform.

The architecture supports both the broadband BPX switch and up to 16 edge concentrator shelves. The scalability results in full utilization of broadband trunks, and allows the BPX switch to be expanded incrementally to handle an almost unlimited number of subscribers.

The edge concentrators terminate traffic from a variety of interfaces, such as IP, Frame Relay, ATM, and circuit emulation, and adapt non-ATM traffic into ATM cells. This traffic is aggregated and sent to the BPX switch where it is switched on high-speed ATM links. This aggregation on a single platform maximizes the density of broadband and narrowband ports. High-density aggregation of low-speed services also optimizes the efficiency of the high-speed switching matrix and broadband card slots.

The multishelf view is a “logical” view. Physically, the edge concentrator shelves can be colocated with the BPX switch or they may be located remotely. The connection between a shelf and the BPX switch is a high-speed, optionally redundant ATM link.

The BPX switch consists of the BPX shelf with fifteen card slots that can be colocated with the MGX 8200 or MGX 8800 and Service Expansion Shelf (SES) as required.

Three of the slots on the BPX switch shelf are reserved for common equipment cards. The other twelve are general purpose slots used for network interface cards or service interface cards. The cards are provided in sets, consisting of a front card and its associated back card.

The BPX shelf can be mounted in a rack enclosure that provides mounting for a colocated SES and the MGX 8200 or MGX 8800 interface shelves.

1-2

Cisco BPX 8600 Series Installation and Configuration

Release 9.3.30, Part Number 78-12907-01 Rev. E0, May 2005

Page 53

Chapter 1 The BPX Switch: Functional Overview

Figure 1-1 BPX Switch General Configuration Example

The BPX 8600 Series

Cisco WAN Manager

Fr Rly, Voice, Data

T3/E3 ATM

Fr Rly, Voice, Data

LAN

Router

3810

Fr Rly

BPX

switch

T1/E1 T3/E3

T3/E3/OC3

IGX

switch

T3/E3

IGX

switch

Port concentrator

T3/E3

OC3/OC12

T3/E3

OC3/

OC12

BPX

8620

BPX

8620

WAN

T3/E3/OC3/OC12 (PVCs)

T3/E3/OC3

IMA, 1-8

T1/E1 Lines

WAN

MGX 8220

T3/E3

OC3/OC12

Virtual trunks (option)

MGX 8850

T3/E3/OC3

IGX

shelf

BPX

8650

MPLS

VPN

CPE (ATM)

MGX 8220

Fr Rly

ATM MPLS

network

MPLS

VPN

MPLS

VPN

Fr Rly T1/E1 ATM CES FUNI

MGX 8230

BPX

8620

WAN

BPX

8680

WAN

35745

BPX 8650

The BPX® 8650 is an IP+ATM switch that provides ATM-based broadband services and integrates Cisco IOS® software through Cisco 7200 series routers to deliver Multiprotocol Label Switching (MPLS) services.

The following are the core Internet requirements for the BPX 8650:

• Scalability

• Advanced IP services

Release 9.3.30, Part Number 78-12907-01 Rev. E0, May 2005

Cisco BPX 8600 Series Installation and Configuration

1-3

Page 54

The BPX 8600 Series

Chapter 1 The BPX Switch: Functional Overview

• Layer 2 virtual circuit switching advantages

• Layer 2/Layer 3 interoperability

The following are supported by the BPX 8650:

• Premium IP services—Specifies the Internet, intranets, extranets, and IP VPNs, which are now

available over an ATM infrastructure.

• Value-added services, such as content hosting, voice over IP, and video, as well as data-managed

services

• ATM Services—Specifies that standard-based ATM interfaces are offer broadband and narrowband

interconnection for routers, ATM LANs, and other ATM access devices

• The ATM Forum's available bit rate (ABR) virtual source/virtual destination (VS/VD) traffic

management capabilities

• Constant bit rate (CBR)

• Real time variable bit rate (rt-VBR)

• Non real-time VBR (nrt-VBR)

• Unspecified bit rate (UBR)

BPX 8680

BPX 8680-IP

The BPX 8680 universal service switch is a scalable IP+ATM WAN edge switch that combines the benefits of Cisco IOS® IP with the extensive queuing, buffering, scalability, and quality-of-service (QoS) capabilities provided by the BPX 8600 and MGX 8800 series platforms.

The BPX 8680 switch incorporates a modular, multishelf architecture that scales from small sites to very large sites and enables service providers to meet the rapidly growing demand for IP applications while cost-effectively delivering today's services.

The BPX 8680 consists of one or more MGX 8200 series connected as feeders to a BPX 8620. Designed for very large installations, the BPX 8680 can scale to 16,000 DS1s by adding up to 16 MGX 8200 series concentrator shelves while still being managed as a single node.

The BPX 8680-IP scalable Layer 2/Layer 3 WAN solution integrating the proven multiservice switching technology of the Cisco BPX 8650 switch with the flexibility and scalability of the Cisco MGX 8200 series. The MGX 8200 series switch serves as an edge concentrator to the BPX 8650, which employs the BPX 8600 series switch modular, multishelf architecture to enable scalability. The BPX 8650 switch includes a Cisco 7204 label switch controller (LSC) and supports multiprotocol label switching (MPLS) for New World integrated infrastructures.

1-4

Cisco BPX 8600 Series Installation and Configuration

Release 9.3.30, Part Number 78-12907-01 Rev. E0, May 2005

Page 55

Chapter 1 The BPX Switch: Functional Overview

New with Release 9.3.30

With Release 9.3.30, the BPX switch software supports a number of new features:

• Concurrent Routing—Allows the switch CPU to be more effectively utilized by allowing the routing

of multiple connection bundles to be in progress concurrently. The result is better overall reroute performance. If Concurrent Routing is not enabled, only one bundle at a time can be routed on a node.

• TFTP Configuration Save/Restore—Provides the option to use TFTP for communication between

the nodes and the network management system, and the ability to run more efficient configuration downloads on large networks. The use of the standard TFTP allows the backup and restoration of BPX configuration files to workstations or network servers running UNIX and standard TFTP software.

• Virtual Trunk Clock Source Synchronization—Makes network synchronization to a single ATM

service provider clock source more reliable by minimizing clock source switching when there is a single point failure.

• 60K Connections Support on BXM-E—Provides the ability to support a maximum of 60K per card

for VSI applications for the BPX 8600, for example, PNNI or MPLS, used on enhanced BXM-E cards.

New with Release 9.3.30

• F4 to F5 Mapping—Enhances end-to-end connection management and VPC failure notification,

• Trunk Incremental Cell Delay Variance—Allows more voice or NTS connections to be routed over

• Virtual Port ILMI Enhancement—Provides support of the ILMI link management protocol that is

• Virtual Trunk AIS OAM Recognition Enhancement—Provides the capability for virtual trunk

• 800 Part Number Support for BXM Back Cards—Extends the support for displaying Cisco 800-level

• VC Merge—Improves the scalability of MPLS networks and allows multiple incoming Virtual

Discontinued

mapping VPC-based OAM flows into the equivalent VCC OAM flows for each VCC within the VPC.

a trunk by providing a way to adjust the assumed transmission latency on the trunk. The Trunk Incremental Cell Delay Variance (CDV) improves the availability of a node or a network.

extended to BXM physical interfaces, which are configured with virtual ports. LMI continues to be supported on BXM physical ports only.

interfaces on BXM cards to recognize the receipt of end-to-end F4 AIS OAM cells as a virtual trunk path failure alarm condition.

part numbers (Top Assembly Numbers) to BXM back cards.

Circuit (VCs) to be merged into a single outgoing VC, which is called merged VC. While preserving AAL5 framing, the key to VC Merge is to switch cells from the merging Label Virtual Circuit (LVC) to the merged LVC that points to the destination.

The following are the older hardware components and technologies that are supported for five years from the time they are discontinued:

• The BNI-155 card

• All ASI cards

• The BCC-3 card

• The BCC-3-32 card

Release 9.3.30, Part Number 78-12907-01 Rev. E0, May 2005

Cisco BPX 8600 Series Installation and Configuration

1-5

Page 56

BPX Switch Operation

• The IPX switch

• The Extended Services Processor (ESP)

However, PNNI is available on the BPX through the Service Expansion Shelf (SES) PNNI. For a brief description, see Chapter 2, “BPX Switch Physical Overview,” Service Expansion Shelf PNNI section.

• VSI 1.0

• The FastPAD

• The FTM card

• The BTM card

• No support for 3810

BPX Switch Operation

With the BCC-4 card, the BPX switch employs a nonblocking crosspoint switch matrix for cell switching that can operate at up to 19.2 Gbps peak. The switch matrix can establish up to 20 million point-to-point connections per second between ports.

The BXM cards support egress at up to 1600 Mbps and ingress at up to 800 Mbps. The enhanced egress rate enhances operations, such as multicast.

Chapter 1 The BPX Switch: Functional Overview

Access to and from the crosspoint switch matrix on the BCC is through multiport network and user access cards. It is designed to easily meet current requirements with scalability to higher capacity for future growth.

A BPX switch shelf is a self-contained chassis that may be rack-mounted in a standard 19-inch rack or open enclosure.

All control functions, switching matrix, backplane connections, and power supplies are redundant, and nondisruptive diagnostics continuously monitor system operation to detect any system or transmission failure. Hot-standby hardware and alternate routing capability combine to provide maximum system availability.

The BPX Switch with MGX 8220, MGX 8230, and MGX 8250 Shelves

Many network locations have increasing bandwidth requirements due to emerging applications and the confluence of voice, data, and video digital communications. To meet these requirements, you can overlay your existing narrowband networks with a backbone of BPX switches to utilize the high-speed connectivity of the BPX switch operating at up to 19.2 Gbps with its T3/E3/OC-3/OC-12 network and service interfaces.

The BPX switch service interfaces include BXM ports on the BPX switch and service ports on MGX 8220, MGX 8230, and MGX 8250 shelves.

The MGX 8220 shelves may be colocated in the same cabinet as the BPX switch, providing economical port concentration for T1/E1 Frame Relay, T1/E1 ATM, CES, and FUNI connections. Ten service module slots are supported for the MGX 8220.

1-6

As a BPX feeder, the MGX 8230 concentrates user ATM, Frame Relay (T1/E1 and T3/E3), T1/E1 ATM, and T1/E1 CES interfaces. Eight service module slots are supported for the MGX 8230.

Cisco BPX 8600 Series Installation and Configuration

Release 9.3.30, Part Number 78-12907-01 Rev. E0, May 2005

Page 57

Chapter 1 The BPX Switch: Functional Overview

The MGX 8250 can act as a stand-alone edge concentrator or as a feeder node for the BPX switch. Twenty-four service module slots are supported for the MGX 8250. The following interfaces are supported for user traffic:

• Frame Relay (T1/E1 and T3/E3)

• ATM UNI, FUNI, and optional inverse multiplexing for ATM (IMA)

• Frame Relay to ATM network interworking and service interworking

• CES (T1/E1 and T3/E3)

Both the MGX 8230 and MGX 8250 support FRSM-VHS, Voice Service Module (VISM), and Route Processor Module (RPM) cards. For information about VISM, refer to the Cisco Voice Interworking

Service Module Installation and Configuration Guide. For information about RPM, refer to the Cisco Route Processor Module Installation and Configuration Guide.

Multiprotocol Label Switching

The BPX 8650 MPLS switch combines a BPX switch with a separate MPLS controller (Cisco Series 7200 or 6400 router). By integrating the switching and routing functions, MPLS combines the reachability, scalability, and flexibility provided by the router function with the traffic engineering optimizing capabilities of the switch.

BPX Switch Operation

Multiprotocol Label Switching (MPLS) is a high-performance method for forwarding packets (frames) through a network. It enables routers at the edge of a network to apply simple labels to packets (frames). ATM switches or existing routers in the network core can switch packets according to the labels with minimal lookup overhead.

MPLS integrates the performance and traffic management capabilities of Data Link Layer 2 with the scalability and flexibility of Network Layer 3 routing. It is applicable to networks using any Layer 2 switching, but has particular advantages when applied to ATM networks. It integrates IP routing with ATM switching to offer scalable IP-over-ATM networks.

In contrast to label switching, conventional Layer 3 IP routing is based on the exchange of network reachability information. As a packet traverses the network, each router extracts all the information relevant to forwarding from the Layer 3 header. This information is then used as an index for a routing table lookup to determine the packet’s next hop. This is repeated at each router across a network. At each hop in the network, the optimal forwarding of a packet must be again determined.

The information in IP packets, such as IP Precedence information and information on Virtual Private Network membership, is usually not considered when forwarding packets. Thus, to get maximum forwarding performance, typically only the destination address is considered. However, because other fields can be relevant, a complex header analysis must be done at each router that the packet meets.

The main concept of MPLS is to include a label on each packet.

Packets or cells are assigned short, fixed length labels. Switching entities perform table lookups based on these simple labels to determine where data should be forwarded.

The label summarizes essential information about routing the packet:

• Destination

• Precedence

• Virtual Private Network membership

• Quality of Service (QoS) information from RSVP

• The route for the packet, as chosen by traffic engineering (TE)

Release 9.3.30, Part Number 78-12907-01 Rev. E0, May 2005

Cisco BPX 8600 Series Installation and Configuration

1-7

Page 58

BPX Switch Operation

Chapter 1 The BPX Switch: Functional Overview

With Label Switching the complete analysis of the Layer 3 header is performed only once: at the edge label switch router (LSR) which is located at each edge of the network. At this location, the Layer 3 header is mapped into a fixed length label, called a label.

At each router across the network, only the label need be examined in the incoming cell or packet in order to send the cell or packet on its way across the network. At the other end of the network, an edge LSR swaps the label out for the appropriate header data linked to that label.

A key result of this arrangement is that forwarding decisions based on some or all of these different sources of information can be achieved by means of a single table lookup from a fixed-length label. For this reason, label switching makes it feasible for routers and switches to make forwarding decisions based upon multiple destination addresses.

Label switching integrates switching and routing functions, combining the reachability information provided by the router function, plus the traffic engineering benefits achieved by the optimizing capabilities of switches.

For multiservice networks, the BPX 8650 switch provides 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 multiservice providers.

Cisco’s MPLS solution is described in detail in the Cisco MPLS Controller Software Configuration Guide.

Private Network to Network Interface

Private Network to Network Interface (PNNI) is a link-state routing protocol that provides standards-based dynamic ATM routing with QoS support as defined by the ATM Forum. PNNI supports aggregation for private ATM addresses and links between switches, and can scale the network and its performance by configuring PNNI peer groups and hierarchical levels.

A key feature of the PNNI hierarchy mechanism is its ability to automatically configure itself in networks in which the address structure reflects the topology. It is responsive to changes in network resources and availability.

PNNI is available on the BPX switch when an optional Cisco Service Expansion Shelf (SES) PNNI is installed. This controller is connected locally to a BPX 8600 series switch to provide PNNI signaling and routing for the establishment of ATM and Frame Relay switched virtual circuits (SVCs) and Soft Permanent Virtual Circuits (SPVCs) over a BPX 8600 wide area network. The network created with BPX SES PNNI nodes also supports traditional ATM and Frame Relay permanent virtual circuits (PVCs) in a separately partitioned Automatic Routing Management network.

ATM SVCs are ATM connections that are established and maintained by a standardized signaling mechanism between ATM CPE (ATM end systems) across a Cisco WAN switching network. ATM SVCs are set up in accordance with user demand and removed when calls are completed, thus freeing up network resources.

BPX SES PNNI node resources, such as port virtual path identifier (VPI) range and bandwidth and trunk bandwidth, are partitioned between SVCs/SVPCs and PVCs. Resource partitioning provides a firewall between PVCs and SVCs/SVPs so that problems with CPE or large bursts do not affect the robustness and availability of PVC services. Bursty data for either PVCs or SVCs/SPVCs can always use any unused link bandwidth, regardless of partitioning.

1-8

For a brief description of the SES PNNI, see the Service Expansion Shelf PNNI section. Refer to the Cisco SES PNNI Controller Software Configuration Guide for detailed information abut the SES.

For further information about PNNI and the SES, refer to the Cisco SES PNNI Controller Software

Configuration Guide.

Cisco BPX 8600 Series Installation and Configuration

Release 9.3.30, Part Number 78-12907-01 Rev. E0, May 2005

Page 59

Chapter 1 The BPX Switch: Functional Overview

Virtual Private Networks

This section is a brief description of the BPX switch’s support for Virtual Private Networks (VPN). For additional information, refer to the Cisco MPLS Controller Software Configuration Guide.

Conventional VPNs that use dedicated lease lines or Frame Relay Private Virtual Circuits (PVC) and a meshed network (see Figure 1-2) provide many advantages, but typically have been limited in efficiency and flexibility.

Instead of using dedicated leased lines or Frame Relay PVCs, and so on, for a VPN, an IP virtual private network uses the open connection less architecture of the Internet for transporting data as shown in Figure 1-2.

An IP virtual private network offers these benefits:

• Scalability

–

Avoids VC mesh configuration

–

Easy to add a new site since IP is connection less

–

Service provider handles router service management

• Efficiency

BPX Switch Operation

–

Rapid provisioning for networks

–

Supports any-to-any intranets

Figure 1-2 IP VPN Service Example

VPN C

VPN B

VPN A

VPN B

Conventional VPNs, Leased Lines, etc.

VPN D

MPLS Virtual Private Networks

VPN A

VPN D

VPN B

VPN C

VPN A

VPN B

VPN A

VPN C

VPN B

VPN A

VPN D

IP Based VPNs

VPN D

VPN C

adding

new site

VPN A

VPN B

24916

MPLS virtual private networks combine the advantages of IP flexibility and connection less operation with the QoS and performance features of ATM as shown in Figure 1-3.

The MPLS VPNs provide the same benefits as a plain IP Virtual Network plus:

• Scaling and Configuration

–

Existing BGP techniques can be used to scale route distribution

–

Each edge router needs only the information for the VPNs it supports

Release 9.3.30, Part Number 78-12907-01 Rev. E0, May 2005

Cisco BPX 8600 Series Installation and Configuration

1-9

Page 60

BPX Switch Operation

Chapter 1 The BPX Switch: Functional Overview

–

No VPN knowledge in core

–

No need for separate VC mesh per VPN

• Highly Scalability

• Ease of using new sites

Configure one site on one edge router or switch and network automatically does the rest.

• Traffic Separation in MPLS

Each packet has a label identifying the destination VPN and customer site, providing the same level of privacy as Frame Relay.

• Flexible Service Grouping

A single structure can support multiple services, such as voice VPNs, extranets, intranets, Internet, multiple VPNs.

Figure 1-3 MPLS VPNs Example

VPN A

VPN C

VPN B

VPN A

VPN B

VPN D

IP Based VPNs

Frame Relay to ATM Interworking

Interworking lets you retain your existing services and migrate to the higher bandwidth capabilities provided by BPX switch networks, as your needs expand. Frame Relay to ATM Interworking enables Frame Relay traffic to be connected across high-speed ATM trunks using ATM-standard Network and Service Interworking.

VPN D

VPN B

VPN C

VPN A

MPLS VPN Services

Customer sites connected to network with Frame Relay, ATM, xDSL, etc.

Customer sites have ordinary IP equipment, don't need MPLS or special VPN equipment.

Provides advantages of IP connectionless flexibility combined with QoS and performance advantages of ATM.

24915

1-10

Two types of Frame Relay to ATM interworking are supported:

• Network Interworking (see Figure 1-4.)

–

Performed by the UXM card on the IGX switch

–

Performed by the FRSM card on the MGX 8220

• Service Interworking (see Figure 1-5.)

–

Supported by the FRSM card on the MGX 8220

–

Supported by the UFM cards on the IGX switch

Cisco BPX 8600 Series Installation and Configuration

Release 9.3.30, Part Number 78-12907-01 Rev. E0, May 2005

Page 61

Chapter 1 The BPX Switch: Functional Overview

Network Interworking

Part A of Figure 1-4 shows typical Frame Relay to network interworking. In this example, a Frame Relay connection is transported across an ATM network, and the interworking function is performed by both ends of the ATM network.

These are typical configurations:

• IGX switch Frame Relay (shelf/feeder) to IGX switch Frame Relay (either routing node or

shelf/feeder).

• MGX 8200 series Frame Relay to MGX 8200 series Frame Relay.

• MGX 8200 series Frame Relay to IGX switch Frame Relay (either routing node or shelf/feeder).

Part B of Figure 1-4 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.

These are sample configurations:

• IGX switch Frame Relay (routing node, shelf, or feeder) to BPX switch or to MGX 8220 ATM port.

• MGX 8200 series Frame Relay to BPX switch or MGX 8200 series ATM port.

BPX Switch Operation

Network Interworking is supported by the FRM, UFM-C, and UFM-U on the IGX switch, and the FRSM on the MGX 8200 series. The Frame Relay Service Specific Convergence Sublayer (FR-SSCS) of AAL5 is used to provide protocol conversion and mapping.

Release 9.3.30, Part Number 78-12907-01 Rev. E0, May 2005

Cisco BPX 8600 Series Installation and Configuration

1-11

Page 62

BPX Switch Operation

Chapter 1 The BPX Switch: Functional Overview

Figure 1-4 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.

Frame Relay

Part B Network interworking connection from CPE Frame Relay port to CPE ATM port across an ATM network, where the network performs an interworking function only at the Frame Relay end of the network. The CPE receiving and transmitting ATM cells at its ATM port is responsible for exercising the applicable service specific convergence sublayer, in this case, (FR-SSCS).

Frame Relay

CPE

Frame Relay

CPE

Interworking function

B-ISDN

FR-SSCS

Interworking function

B-ISDN

FR-SSCS

ATM network

FR-SSCS

ATM network

Interworking function

B-ISDN

ATM

Frame Relay

exercises

appropriate

SSCS

B-ISDN

FR-SSCS

CPE

Frame Relay

H8225

Service Interworking

Figure 1-5 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.

Unlike Network Interworking, in a Service Interworking connection between an ATM port and a Frame Relay port, the ATM device does not need to be aware that it is connected to an interworking function.

The Frame Relay service user does not implement any ATM specific procedures. Also, the ATM service user does not need to provide any Frame Relay specific functions. All translational (mapping functions) are performed by the intermediate interworking function.

This is a typical configuration for service interworking:

• MGX 8220 Frame Relay (FRSM card) to BPX switch or MGX 8220 ATM port.

• IGX switch Frame Relay (FRM-U or FRM-C) to BPX switch or MGX 8220 ATM port.

Cisco BPX 8600 Series Installation and Configuration

1-12

Release 9.3.30, Part Number 78-12907-01 Rev. E0, May 2005

Page 63

Chapter 1 The BPX Switch: Functional Overview

Note The FRM-U or FRM-C cards for the IGX switch is supported only for network

interworking.

Figure 1-5 Frame Relay to ATM Service Interworking

BPX Switch Operation

Frame Relay

Tiered Networks

Networks may be configured as:

• Flat

• Tiered

By allowing CPE connections to connect to a nonrouting node (interface shelf), a tiered network is able to grow in size beyond that which would be possible with only routing nodes comprising the network.

Starting with Release 8.5, tiered networks support both BPX switch routing hubs and IGX switch routing hubs. Voice and data connections originating and terminating on IGX switch interface shelves (feeders) are routed across the routing network through the associated IGX switch routing hubs.

Tiered networks support multiservice connections, including Frame Relay, circuit data, voice, and ATM. By allowing the customer’s equipment to connect to a nonrouting node (interface shelf), a tiered network is able to grow in size beyond that which would be possible with only routing nodes.

CPE using a

standard, non-

service specific

convergence

protocol

H8226

CPE

Frame Relay

Service

interworking

function

ATM network

ATM

All nodes perform routing and communicate fully with one another, or

Interface shelves are connected to routing hubs, where the interface shelves are configured as nonrouting nodes.

Intermediate routing nodes must be IGX switches. IGX switch interface shelves are the only interface shelves that can be connected to an IGX switch routing hub. With this addition, a tiered network provides a multiservice capability (Frame Relay, circuit data, voice, and ATM).

Routing Hubs and Interface Shelves

In a tiered network, interface shelves at the access layer (edge) of the network are connected to routing nodes by means of the feeder trunks as shown in Figure 1-6.

• Routing hubs

Those routing nodes with attached interface shelves are referred to as routing hubs.

• Interface shelves

The interface shelves, sometimes referred to as feeders, are nonrouting nodes.

The routing hubs route the interface shelf connections across the core layer of the network.The interface shelves do not need to maintain network topology nor connection routing information. This task is left to their routing hubs.

This architecture provides an expanded network consisting of a number of nonrouting nodes (interface shelves) at the edge of the network that are connected to the network by their routing hubs.

Release 9.3.30, Part Number 78-12907-01 Rev. E0, May 2005

Cisco BPX 8600 Series Installation and Configuration

1-13

Page 64

BPX Switch Operation

BPX Switch Routing Hubs

T1/E1 Frame Relay connections originating at 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 through the 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.

• No direct trunking between interface shelves is supported.

• No routing trunk is supported between the routing network and interface shelves.

• The feeder trunks between BPX switch hubs and IGX switch interface shelves are either T3 or E3.

• The feeder trunks between BPX switch hubs and MGX 8220 interface shelves are T3, E3, or

OC-3-C/STM-1.

• Frame Relay connection management to an IGX switch interface shelf is provided by Cisco WAN

Manager.

• Frame Relay and ATM connection management to an MGX 8220 interface shelf is provided by

Cisco WAN Manager.

Chapter 1 The BPX Switch: Functional Overview

• Telnet is supported to an interface shelf; the vt command is not.

• Frame Relay connections originating at IGX switch interfaces shelves connected to IGX switch

routing hubs may also be routed across BPX switch intermediate nodes.

• Remote printing by the interface shelf through a print command from the routing network is not

supported.

1-14

Cisco BPX 8600 Series Installation and Configuration

Release 9.3.30, Part Number 78-12907-01 Rev. E0, May 2005

Page 65

Chapter 1 The BPX Switch: Functional Overview

Figure 1-6 Tiered Network with BPX Switch and IGX Switch Routing Hubs

Access

(Feeder)

Voice, Data,

and

Frame Relay

IGX

Shelf

IGX

Shelf

IGX Hub

Layer

Concentration

Layer

ATM

Core Layer

IGX

switch

IGX

switch

IGX

Shelf

IGX Hub

BPX Switch Operation

Voice, Data,

and

Frame Relay

IGX

Shelf

BPX

switch

Frame

Relay

IGX

Shelf

MGX 8220

Frame Relay

T1/E1 ATM

CES

FUNI

BPX

Hub

BPX Routing Hubs in a Tiered Network

Tiered networks with BPX routing hubs have the capability of adding interface shelves/feeders (nonrouting nodes) to an IGX/BPX routing network as shown in Figure 1-7. Interface shelves allow the network to support additional connections without adding additional routing nodes.

BPX

switch

BPX Hub

IGX

Shelf

Frame

Relay

IGX

Shelf

MGX 8220

Frame

Relay

Frame Relay

T1/E1 ATM

CES

FUNI

S6396

The MGX 8220 or MGX 8800 and IGX 8400 nodes configured as interface shelves are connected to BPX routing hubs.

The MGX 8220 and MGX 8800 support frame T1/E1, X.21 and HSSI Frame Relay, ATM T1/E1, and CES.

Release 9.3.30, Part Number 78-12907-01 Rev. E0, May 2005

Cisco BPX 8600 Series Installation and Configuration

1-15

Page 66

BPX Switch Operation

Figure 1-7 Tiered Network with BPX Routing Hubs

CISCO WAN MANAGER

(network management)

Frame Relay

ATM T1/E1

ICX

shelf

MGX 8220

IGX

shelf

IGX

BPX

(routing

hub)

IGX

Chapter 1 The BPX Switch: Functional Overview

Frame Relay

IGX

shelf

Frame Relay

MGX 8220

CES

ATM T1/E1

Frame Relay

CES

MGX 8220

Frame Relay

Tiered Network Implementation

The following requirements apply to BPX routing hubs and their associated interface shelves:

• MGX 8220 Release 4 level or above is required on all MGX 8220 interface shelves.

• Only one feeder trunk is supported between a routing hub and interface shelf.

• No direct trunking between interface shelves is supported.

• No routing trunk is supported between the routing network and interface shelves.

• The feeder trunks between BPX hubs and IGX interface shelves may be T3, E3, or OC-3 (since

Release 9.2.30).

• The feeder trunks between BPX hubs and MGX 8200 series or MGX 8200 series interface shelves

are T3, E3, or OC-3-C/STM-1.

• Frame Relay and ATM connection management to a MGX 8200 series or MGX 8200 series interface

shelf is provided by Cisco WAN Manager

IGX

shelf

BPX

(routing

hub)

IGX

shelf

(routing

hub)

Routing network

Frame Relay

BPX

IGX

shelf

MGX 8220

Frame Relay

ATM T1/E1

Frame Relay

35744

1-16

• Telnet is supported to an interface shelf; the vt command is not.

• Remote printing by the interface shelf through a print command from the routing network is not

supported.

The definitions for the tier network are listed in Table 1-1.

Cisco BPX 8600 Series Installation and Configuration

Release 9.3.30, Part Number 78-12907-01 Rev. E0, May 2005

Page 67

Chapter 1 The BPX Switch: Functional Overview

Table 1-1 Tier Network Definitions

Name Description

Annex G A bidirectional protocol, defined in Recommendation Q.2931. It is used

BPX Routing Hub A BPX node in the routing network that has attached interface shelves.

MGX 8200 Interface Shelf A standards-based service interface shelf that connects to a BPX routing

IGX Interface Shelf A special configuration of an IGX switch that is connected as a shelf to an

IGX Routing Hub An IGX node in the routing network that has attached IGX interface

Feeder Trunk Refers to a trunk that interconnects an interface shelf with the routing

IGX/AF Another name for the IGX interface shelf.

Routing Network The portion of the tiered network that performs automatic routing between

VPI Virtual Path Identifier.

VCI Virtual Connection Identifier.

BPX Switch Operation

for monitoring the status of connections across a UNI interface. Tiered Networks use the Annex G protocol to pass connection status information between a hub node and attached interface shelf.

Also referred to as a hub node or BPX hub.

hub, aggregates and concentrates traffic, and performs ATM adaptation for transport over broadband ATM networks.

IGX routing hub. An IGX interface shelf is sometimes referred to as an IGX A/F or feeder. The IGX interface shelf does not perform routing functions nor keep track of network topology.

shelves. Also referred to as a hub node or IGX hub.

network through a BPX routing hub. A feeder trunk is sometimes referred to as an interface shelf trunk.

connection endpoints.

Upgrades

Converting an IGX node to an interface shelf requires reconfiguring connections on the node because no upgrade path is provided in changing a routing node to an interface shelf.

A BPX node, acting as a Hub Node, is not restricted from providing any other feature normally available on BPX nodes. A BPX Hub supports up to 16 interface shelves.

Connections within tiered networks consist of distinct segments within each tier. A routing segment traverses the routing network, and an interface shelf segment provides connectivity to the interface shelf end-point. Each of these segments are added, configured and deleted independently of the other segments.

Use the Cisco WAN Manager Connection Manager to configure and control these individual segments as a single end-to-end connection.

Interface shelves are attached to the routing network through a BPX routing hub using a BXM trunk (T3/E3 or OC-3) or BNI trunk (T3/E3). The connection segments within the routing network are terminated on the BNI feeder trunks.

All Frame Relay connection types that can terminate on the BPX are supported on the BNI feeder trunk (VBR, CBR, ABR, and ATF types). No check is made by the routing network to validate whether the connection segment type being added to a BNI feeder trunk is actually supported by the attached interface shelf.

Release 9.3.30, Part Number 78-12907-01 Rev. E0, May 2005

Cisco BPX 8600 Series Installation and Configuration

1-17

Page 68

BPX Switch Operation

Colocating Routing Hubs and Interface Shelves

The trunk between an interface shelf and the routing network is a single point of failure; therefore, the interface shelves can be colocated with their associated hub node. Card level redundancy is supported by the Y-Cable redundancy for the BXM, BNI, and UXM.

Network Management

Communication between CPE devices and the routing network is provided in accordance with Annex G of Recommendation Q.2931. This is a bidirectional protocol for monitoring the status of connections across a UNI interface. (Note: the feeder trunk uses the STI cell format to provide the ForeSight rate controlled congestion management feature.)

Communication includes the real-time notification of the addition or deletion of a connection segment and the ability to pass the availability (active state) or unavailability (inactive state) of the connections crossing this interface.

A proprietary extension to the Annex G protocol is implemented that supports the exchange of node information between an interface shelf and the routing network. This information is used to support the IP Relay feature and the Robust Update feature used by network management.

Network Management access to the interface shelves is through the IP Relay mechanism using SNMP or TFTP or by direct attachment to the interface shelf. The IP Relay mechanism relays traffic from the routing network to the attached interface shelves. No IP Relay support is provided from the interface shelves into the routing network.

Chapter 1 The BPX Switch: Functional Overview

The BPX routing hub is the source of the network clock for its associated feeder nodes. Feeders synchronize their time and date to match their routing hub.

Robust Object and Alarm Updates are sent to a network manager that has subscribed to the Robust Updates feature. Object Updates are generated whenever an interface shelf is added or removed from the hub node and when the interface shelf name or IP Address is modified on the interface shelf. Alarm Updates are generated whenever the alarm state of the interface shelf changes between Unreachable, Major, Minor, and OK alarm states.

An interface shelf is displayed as a unique icon in the Cisco WAN Manager topology displays. The colors of the icon and connecting trunks indicate the alarm state of each.

Channel statistics are supported by FRM, ASI, UXM, and MGX 8220 endpoints. The Broadband Network Interface (BNI) card does not support channel statistics. Trunk Statistics are supported for the feeder trunk and are identical to the existing BNI trunk statistics.

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 eight T1 or E1 trunks provided by an IMATM module on an MGX 8220 shelf. A BNI or BXM port on each BPX switch is directly connected to an IMATM module in an MGX 8220 by a T3 or E3 trunk. The IMATM modules are then linked together by any of the eight T1 or E1 trunks. IMA is also configurable on lines.

1-18

Refer to the Cisco MGX 8220 Reference and the Cisco WAN Switching Command Reference publications for further information.

Cisco BPX 8600 Series Installation and Configuration

Release 9.3.30, Part Number 78-12907-01 Rev. E0, May 2005

Page 69

Chapter 1 The BPX Switch: Functional Overview

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 OC-3 bandwidths.

• Utilization of the full mesh capability of the public carrier to reduce the number of leased lines

needed between nodes in the Cisco WAN switching networks.

• Choice of keeping existing leased lines between nodes, but using virtual trunks for backup.

• Ability to connect BNI or BXM trunk interfaces to a public network using standard ATM UNI cell

format.

• Virtual trunking is provisioned through either a Public ATM Cloud or a Cisco WAN switching ATM

cloud.

A virtual trunk may be defined as a “trunk over a public ATM service.” The trunk really doesn’t exist as a physical line in the network. Rather, an additional level of reference, called a virtual trunk number, is used to differentiate the virtual trunks found within a physical trunk port.

BPX Switch Operation

Figure 1-8 shows four Cisco WAN switching networks, each connected to a Public ATM Network through a physical line. The Public ATM Network is shown linking all four of these subnetworks to every other one with a full meshed network of virtual trunks. In this example, each physical line is configured with three virtual trunks.

Figure 1-8 Virtual Trunking Example

Cisco

sub-network

Cisco

sub-network

ATM-UNI ATM-UNI

Public ATM

ATM-UNI ATM-UNI

Network

Virtual trunk Leased line

Cisco

sub-network

Leased line

(backup)

Cisco

sub-network

H8227

Release 9.3.30, Part Number 78-12907-01 Rev. E0, May 2005

Cisco BPX 8600 Series Installation and Configuration

1-19

Page 70

Traffic and Congestion Management

The BPX switch provides ATM standard traffic and congestion management per ATM Forum TM 4.0 using BXM cards.

The Traffic Control functions include:

• Usage Parameter Control (UPC)

• Traffic Shaping

• Connection Management Control

• Selective Cell Discarding

• Explicit Forward Congestion Indication (EFCI)

• Priority Bumping

In addition to these standard functions, the BPX switch provides advanced traffic and congestion management features including:

• Support for the full range of ATM service types per ATM Forum TM 4.0 by the BXM-T3/E3,

BXM-155, and BXM-622 cards on the BPX Service Node.

Chapter 1 The BPX Switch: Functional Overview

• Advanced CoS Management (formerly Fairshare and Opticlass features) Class of Service

management delivers the required QoS to all applications.

–

The BPX provides per virtual circuit (VC) queuing and per-VC-scheduling provided by rate controlled servers and multiple class-of-service queuing at network ingress.

–

On egress, up to 16 queues with independent service algorithms for each trunk in the network.

• Automatic Routing Management (formerly Automatic Routing Management feature), end-to-end

connection management that automatically selects the optimum connection path based upon the state of the network and assures fast automatic alternate routing in the event of intermediate trunk or node failures.

• Cost-Based Routing Management

• ABR Standard with VS/VD; congestion control using RM cells and supported by BXM cards on the

BPX Switch.

• Optimized Bandwidth Management (formerly ForeSight), an end-to-end closed loop rate based

congestion control algorithm that dynamically adjusts the service rate of VC queues based on network congestion feedback.

• Dynamic Buffer Management, Cisco’s Frame Relay and ATM service modules are equipped with

large buffers and a dynamic buffer management technique for allocating and scaling the buffers on a per VC basis to traffic entering or leaving a node. The switch dynamically assigns buffers to individual virtual circuits based on the amount of traffic present and service level agreements. The large queues readily accommodate large bursts of traffic into the node.

• PNNI, a standards-based routing protocol for ATM and Frame Relay SVCs.

1-20

• Early and partial packet discard for AAL5 connections.

Cisco BPX 8600 Series Installation and Configuration

Release 9.3.30, Part Number 78-12907-01 Rev. E0, May 2005

Page 71

Chapter 1 The BPX Switch: Functional Overview

Advanced CoS Management

Advanced Class of Service (CoS) management provides per-VC queueing and per-VC scheduling. CoS management provides fairness between connections and firewalls between connections. Firewalls prevent a single noncompliant connection from affecting the QoS of compliant connections. The noncompliant connection simply overflows its own buffer.

The cells received by a port are not automatically transmitted by that port out to the network trunks at the port access rate. Each VC is assigned its own ingress queue that buffers the connection at the entry to the network. With ABR with VS/VD or with Optimized Bandwidth Management (ForeSight), the service rate can be adjusted up and down depending on network congestion.

Network queues buffer the data at the trunk interfaces throughout the network according to the connection’s Class of Service. Service classes are defined by standards-based QoS. Classes can consist of the five service classes defined in the ATM standards as well as multiple sub-classes to each of these classes. Classes can range from constant bit rate services with minimal cell delay variation to variable bit rates with less stringent cell delay.

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.

CoS management provides an 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. This is especially important when there are multiple user services on one network. The BPX switch provides separate queues for each traffic class.

Traffic and Congestion Management

Rather than limiting the user to the five broad classes of service defined by the ATM standards committees, CoS management can provide up to 16 classes of service (service subclasses) that you can further define and assign to connections. Some of the COS parameters that may be assigned include:

• Minimum bandwidth guarantee per subclass to assure that one type of traffic will not be preempted

by another.

• Maximum bandwidth ceiling to limit the percentage of the total network bandwidth that any one

class can utilize.

• Queue depths to limit the delay.

• Discard threshold per subclass.

These class of service parameters are based on the standards-based Quality of Service parameters and are software programmable by the user.

Automatic Routing Management

With Automatic Routing Management, connections in Cisco WAN switching networks are added if there is sufficient bandwidth across the network and are automatically routed when they are added.

You need enter only the endpoints of the connection at one end of the connection and the IGX switch and BPX switch software automatically set up a route based on a sophisticated routing algorithm. This feature is called Automatic Routing Management. It is a standard feature on the IGX and BPX switches.

System software automatically sets up the most direct route after considering the network topology and status, the amount of spare bandwidth on each trunk, as well as any routing restrictions entered by the user (for example, avoid satellite links). This avoids having to manually enter a routing table at each node in the network. Automatic Routing Management simplifies adding connections, speeds rerouting around network failures, and provides higher connection reliability.

Release 9.3.30, Part Number 78-12907-01 Rev. E0, May 2005

Cisco BPX 8600 Series Installation and Configuration

1-21

Page 72

Traffic and Congestion Management

Cost-Based Routing Management

You can selectively enable cost-based route selection as the route selection per node. With cost-based routing management, a trunk cost is assigned to each trunk (physical and virtual) in the network. The routing algorithm then chooses the lowest-cost route to the destination node. The lowest cost routes are stored in a cache to reduce the computation time for on-demand routing.

Cost-based routing can be enabled or disabled at anytime. There can be a mixture of cost-based and hop-based nodes in a network.

For more detailed information about cost-based Automatic Routing Management, see the Cost-Based Connection Routing section.

Priority Bumping

Priority Bumping (PB) allows BPX and IGX switch connections classified as more important (through the CoS value) to “bump” (that is, set aside) existing connections of lesser importance. While the Automatic Routing Management feature is capable of automatically redirecting all failed connections onto other paths, priority bumping lets you prioritize and sustain more important connections when network resources are diminished to a point that all connections cannot be sustained. Network resources are reclaimed for the more important connections by bumping (derouting) the traffic on less important connections.

Chapter 1 The BPX Switch: Functional Overview

Priority bumping is triggered by insufficient resources (such as bandwidth), resulting from any number events, including changes to the network made by using the commands addcon, upcon, cnfcon, cnnfcos, cnfpref, cnftrk, and deltrk. Other triggers include trunk line/card failure, node failure, and communication failure. The most prominent event is a trunk failure.

For information on setting up Priority Bumping, refer to the Cisco WAN Switching Command Reference, Release 9.3.30.

Concurrent Routing

CR is an enhancement to the Automatic Routing Management feature and does not alter the Automatic Routing Management messaging protocol. The Automatic Routing Management functionality is operational whether or not CR is enabled on a node. If CR is disabled, the node exhibits preswitch software Release 9.3.30 behavior, which includes collisions and back off. When CR is enabled, collisions occur less frequently.

Concurrent Routing (CR) allows multiple routing requests to be processed simultaneously on a node. For example, a node can initiate (master node) one or more routes while simultaneously accepting other routes that pass through it (via node) or terminate at it (slave node).

If CR is not enabled on a node, routing requests received while a connection is in the process of being routed, is routed sequentially. As a result, only one bundle at a time can be routed on a node. This sequential routing algorithm under utilizes the computational power of the switch. Sequential routing is illustrated in Figure 1-9.

CR allows the processor of the switch to be more effectively utilized by allowing multiple routes to be in progress concurrently. The result is better overall reroute performance. Performance improvement is not realized for individual or topologically disjoint reroutes. The key performance metric that is improved by CR is network settling time. Network settling time is defined by the longest settling time for any single node, assuming all of the nodes start routing at the same time. The number of nodes and connections in the network, network topology, and other configureable routing parameters all affect network settling time. CR is illustrated in Figure 1-10.

1-22

Cisco BPX 8600 Series Installation and Configuration

Release 9.3.30, Part Number 78-12907-01 Rev. E0, May 2005

Page 73

Chapter 1 The BPX Switch: Functional Overview

Figure 1-9 Sequential Routing

Traffic and Congestion Management

Node D

Node BNode A Node C

Node E

Node in routing

Node blocked in routing

Figure 1-10 Concurrent Routing

Node D

Node BNode A Node C

Node E

Node in routing

Blocked routing request

Routing

Trunks

Routing

Trunks

57102

57103

The CR Feature provides the following benefits:

• Allows a node to initiate multiple simultaneous route requests

• Allows multiple route requests to be accepted and serviced by a node

• Allows the degree of route concurrency to be configured on a node-by-node basis, which provides

the user the ability to tailor the application of CR to a specific network topology

• Implements a CPU throttling mechanism; whereas, route concurrency is limited if CPU usage

becomes too high

• Includes new statistics on CR-related quantities and CPU-based route throttling

• Includes a mechanism to automatically measure nodal settling time and maintain a history of settling

time measurements

• Increases network availability

• Reduces network settling time

Release 9.3.30, Part Number 78-12907-01 Rev. E0, May 2005

Cisco BPX 8600 Series Installation and Configuration

1-23

Page 74

Traffic and Congestion Management

Note The extent to which CR reduces network settling time will vary with network topology, traffic

conditions and the number of CR enabled nodes in the network.

Before CR can be enabled on any node in the network, all of the nodes in a network must be upgraded to switch software Release 9.3.30. The cnfcmparm command sets the route concurrency level to an integer value greater than 1 but not greater than 8. Once CR has been enabled, it operates automatically. However, it is not necessary for CR to be enabled on every node in a network for CR to function on those nodes that are CR enabled. CR can be turned off by specifying a concurrency level of 1. For a detailed discussion of the cnfcmparm command and other commands pertinent to the CR feature, refer to the Cisco WAN Switching Command Reference, Release 9.3.30.

A maximum of eight concurrent routes can be configured on a node. However, a node is able only to master two routes concurrently, any remaining concurrent routing capacity is used for routes or as a slave. Allowing more than eight concurrent routes would have diminishing returns, because processor utilization would become excessive. A node continues to master new route requests (provided route candidates exist), or serve as a via node or slave node for new routes, until it reaches the route concurrency level that is configured on the node.

CR has the potential to dramatically reduce CPU idle time. To preserve enough CPU time for other switch features or for users to interact effectively with a node, a mechanism is implemented to limit (throttle) route concurrency. When CPU utilization exceeds a defined threshold (throttle level), new route activity is temporarily suspended to preserve node responsiveness. Throttling continues until CPU utilization drops below a second threshold (resume level), which is less than or equal to the throttle level. Allowing the resume level to be less than the throttle level provides a hysteresis mechanism to avoid oscillation around the throttling point. The default CPU throttling values for master, via and slave routes are set at 80 percent of CPU capacity for throttling and 60 percent of CPU capacity to resume new route activity. Separate throttle and resume points can be set for master, via, and slave routes to allow tailoring of route behavior. However, if you need to change the settings, contact TAC for configuring the levels.

Chapter 1 The BPX Switch: Functional Overview

If a node masters two or more routes that share the same via node or slave node, the routes have overlapping paths. Due to messaging protocol limitations, a node is able only to master concurrent routes that do not have overlapping paths. The Path Blocking algorithm checks each master route candidate that a node might initiate to see if it overlaps with another route in progress that is mastered by the node. If there is any overlap, the candidate is rejected and candidate selection continues. The degree to which Path Blocking limits concurrent master routes on a node is a function of network topology and connection provisioning. Path blocking does not affect nodes that are serving only as a via node or a slave node.

PB is a computation-intensive process, which allows switch connections classified as more important (based on CoS value) to “bump” connections of lesser importance. CR may be restricted if the PB feature is enabled on a network. Both PB and CR are processor intensive. To avoid excessive processor utilization, no new route requests are initiated or accepted on a node that participates in a PB route, until that PB route is complete.

ABR Standard with VS/VD Congestion Control

This section describes Standard ABR with VS/VD. The BPX/IGX switch networks provide a choice of two dynamic rate based congestion control methods, ABR with VS/VD and Optimized Bandwidth Management (ForeSight).

When an ATM connection is configured between BXM cards for Standard ABR with VS/VD per ATM Forum TM 4.0, Resource Management (RM) cells are used to carry congestion control feedback information back to the connection source from the connection destination.

1-24

Cisco BPX 8600 Series Installation and Configuration

Release 9.3.30, Part Number 78-12907-01 Rev. E0, May 2005

Page 75

Chapter 1 The BPX Switch: Functional Overview

Traffic and Congestion Management

The 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.

The RM cells contain fields to increase or decrease the rate (the CI and NI fields) or set it at a particular value (the explicit rate ER field). The intervening switches may adjust these fields according to network conditions. When the source receives an RM cell, it must adjust its rate in response to the setting of these fields.

When spare capacity exists with the network, ABR with VS/VD permits the extra bandwidth to be allocated to active virtual circuits.

Optimized Bandwidth Management (ForeSight) Congestion Control

This section describes Optimized Bandwidth Management (ForeSight). The BPX/IGX switch networks provide a choice of two dynamic rate-based congestion control methods, ABR with VS/VD and Cisco Optimized Bandwidth Management (ForeSight).

Optimized Bandwidth Management (ForeSight) can be used for congestion control across BPX/IGX switches for connections that have one or both endpoints terminating on cards other than BXM. The ForeSight feature is a dynamic closed-loop, rate-based congestion management feature that yields bandwidth savings compared to non-ForeSight equipped trunks when transmitting bursty data across cell-based networks.

When there is unused network bandwidth available, ForeSight permits users to burst above their committed information rate for extended periods of time. This enables users to maximize the use of network bandwidth while offering superior congestion avoidance by actively monitoring the state of shared trunks carrying Frame Relay traffic within the network.

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.

If the network reaches full utilization, ForeSight detects this and quickly acts to reduce the extra bandwidth allocated to the active PVCs. ForeSight reacts quickly to network loading to prevent dropped packets. Periodically, each node automatically measures the delay experienced along a Frame Relay PVC. This delay factor is used in calculating the ForeSight algorithm.

With basic Frame Relay service, only a single rate parameter can be specified for each PVC. With ForeSight, the virtual circuit rate can be specified based on a minimum, maximum, and initial transmission rate for more flexibility in defining the Frame Relay circuits.

ForeSight provides effective congestion management for traversing broadband ATM for the PVC. ForeSight operates at the cell-relay level that lies below the Frame Relay services provided by the IGX switch. With the queue sizes utilized in the BPX switch, the bandwidth savings is approximately the same as experienced with lower speed trunks. When the cost of these lines is considered, the savings offered by ForeSight can be significant.

Release 9.3.30, Part Number 78-12907-01 Rev. E0, May 2005

Cisco BPX 8600 Series Installation and Configuration

1-25

Page 76

Network Management

BPX switches provide one high-speed and two low-speed data interfaces for data collection and network management:

• High-speed interface—Provides an Ethernet 802.3 LAN interface port to communicate with a Cisco

WAN Manager NMS workstation. TCP/IP provides the transport and network layer, Logical Link Control 1 is the protocol across the Ethernet port.

• Low-speed interface—Provides two RS-232 ports: one for a network printer and the second for

either a modem connection or a connection to an external control terminal. These low-speed interfaces are the same as provided by the IGX switch.

Each BPX switch can be configured to use optional low-speed modems for inward access by the Cisco Technical Response Team for network troubleshooting assistance or to autodial Cisco Customer Service to report alarms remotely. If desired, another option is remote monitoring or control of customer premise equipment through a window on the Cisco WAN Manager workstation.

A Cisco WAN Manager NMS workstation connects through the Ethernet to the LAN port on the BPX and provides network management through SNMP. Statistics are collected by Cisco WAN Manager using the TFTP protocol.

Chapter 1 The BPX Switch: Functional Overview

You can also use the Cisco WAN Manager’s Connection Manager to manage:

• Frame Relay connections on IGX switch shelves

• Frame Relay and ATM connections on MGX 8220 shelves

• MGX 8220 shelf configuration.

The following are the Network Management software applications:

• Cisco WAN Manager (formerly StrataView Plus)—Provides a single unified management platform

utilizing HP OpenView® to manage BPX, IGX, and SES devices.

• SNMP Service Agent—Provides an interface for automated provisioning and fault management to

customers or Operations Support Systems (OSS).

For further information on network management, refer to the Cisco WAN Manager User’s Guide.

Cisco WAN Manager

Cisco WAN Manager, a standards-based multiprotocol management architecture, is a single unified management platform that utilizes HP OpenView® to manage BPX, IGX, and SES devices. Regardless of the size or configuration of your network, Cisco WAN Manager collects extensive service statistics, tracks resource performance, and provides powerful remote diagnostic and control functions for WAN maintenance.

Online help screens, graphical displays, and easy command line mnemonics make Cisco WAN Manager user-friendly. Plentiful hard disk storage is provided to allow accumulating time of day statistics on many network parameters simultaneously. The data is accumulated by the node's controller card and transmitted to the Cisco WAN Manager workstation where it is stored, processed, and displayed on a large color monitor.

1-26

Cisco WAN Manager connects to the network over an Ethernet LAN connection. With Ethernet, you can establish Cisco WAN Manager connectivity to remote nodes through Frame Relay over TCP/IP to the LAN connector on the local node, or through inband ILMI.

Cisco BPX 8600 Series Installation and Configuration

Release 9.3.30, Part Number 78-12907-01 Rev. E0, May 2005

Page 77

Chapter 1 The BPX Switch: Functional Overview

Cisco WAN Manager provides inband management of network elements through SNMP agent interfaces and MIBs embedded in each node and interface shelf. The SNMP agent allows a user to manage a StrataCom network or subnetwork from any SNMP-based integrated network management system (INMS).

The following are the functions of Cisco WAN Manager:

• Connection Management—Enables you to perform connection provisioning such as adding,

configuring, and deleting Frame Relay, ATM, and Frame Relay-to-ATM interworking connections.

• Network Topology—Provides a map of the network that is generated at system installation to

graphically display all nodes, trunks, circuit lines, and access devices in the network. Various colors are used to indicate the status of each network item. You can zoom in to display specific network details while a small overview map remains displayed as a locator. The Network Topology can also display other connected ATM devices that support the ILMI 4.0 Neighbor Discovery procedure.

• Network Performance—Collects statistics that are temporarily stored by each node in the network

and released to Cisco WAN Manager when you enable polling, and in accordance with your configuration for specific information within reports. Cisco WAN Manager then stores statistics in a relational database; you retrieve and view these statistics by invoking a statistics display window from the Cisco WAN Manager GUI. From data gathered throughout the network, you can quickly view the operational integrity and deployment of installed network devices and communication media by activating and invoking statistics displays.

• Equipment Management—Provides the ability to perform equipment management functions such as

adding lines and ports on a Cisco MGX 8220 edge concentrator shelf.

Network Management

• Alarm Reporting/Event Log—Displays major and minor alarm status on its topology screen for all

nodes in a network. It also provides an event log with configurable filtering of the log events by node name, start time, end time, alarm type, and user-specified search string.

• Software Updates—Provides system software and software updates that are supplied on magnetic

tape or floppy disk. You can then load the system software files onto the Cisco WAN Manager workstation where they can be downloaded to a buffer memory in each node in the network in a background mode without disturbing network operation. When the loading is complete for all nodes, you issue a command to switch all nodes over to the new software. The previous software is preserved and can be recalled at any time.

• Backup—Allows you to obtain all network configuration files from the network and store them on

the Cisco WAN Manager workstation for backup purposes. In the event of a system update or a node failure, you can download the configuration files to one or all nodes for immediate system restoration.

Network Interfaces

Network interfaces connect the BPX switch to other BPX or IGX switches to form a wide-area network. The following are the trunk interfaces for the BPX switch:

• T3

• E3

• OC-3/STM-1

• OC-12/STM-4

The T3 physical interface utilizes DS3 C-bit parity and the 53-byte ATM physical layer cell relay transmission using the Physical Layer Convergence Protocol.

The E3 physical interface uses G.804 for cell delineation and HDB3 line coding.

Release 9.3.30, Part Number 78-12907-01 Rev. E0, May 2005

Cisco BPX 8600 Series Installation and Configuration

1-27

Page 78

Network Management

The following are the physical interfaces for the BXM-622 cards:

• SMF

• SMFLR

• SMFXLR

The BPX switch supports network interfaces up to 622 Mbps and provides 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. As an option, the node synchronization can be obtained from the DS3 extracted clock for any selected network trunk.

Service Interfaces

Service interfaces connect ATM customer equipment to the BPX switch. ATM User-to-Network Interfaces (UNI) and ATM Network-to-Network Interfaces (NNI) terminate on the ATM Service Interface (ASI) cards and on BXM T3/E3, OC-3, and OC-12 cards configured for the service interfaces (UNI access mode).

–

Supports 1550nm lasers

Chapter 1 The BPX Switch: Functional Overview

The BXM T3/E3 card supports the standard T3/E3 interfaces.

The BXM-155 cards support SMF, SMFLR, and MMF physical interfaces.

The BXM-622 cards support SMF, SMFLR, and SMFXLR physical interfaces.

Note The SMFXLR physical interface supports 1550nm lasers.

The BXM cards support cell relay connections that are compliant with both the physical layer and ATM layer standards.

The MGX 8220 interfaces to a BNI or BXM card on the BPX, through a T3, E3, or OC-3 interface. The MGX 8220 provides a concentrator for T1 or E1 Frame Relay and ATM connections to the BPX switch with the ability to apply Optimized Bandwidth Management (ForeSight) across a connection from end-to-end. The MGX 8220 also supports CES and FUNI (Frame-based UNI over ATM) connections.

Statistical Alarms and Network Statistics

The BPX Switch system manager can configure alarm thresholds for all statistical type error conditions. Thresholds are configureable for conditions such as frame errors, out of frame, bipolar errors, dropped cells, and cell header errors. When an alarm threshold is exceeded, the NMS screen displays an alarm message.

Graphical displays of collected statistics information, a feature of the Cisco WAN Manager NMS, are a useful tool for monitoring network usage. The following are the four general categories used for collecting statistics:

1-28

• Node statistics

• Network trunk statistics

• Network Service, line statistics

• Network Service, port statistics

Cisco BPX 8600 Series Installation and Configuration

Release 9.3.30, Part Number 78-12907-01 Rev. E0, May 2005

Page 79

Chapter 1 The BPX Switch: Functional Overview

The statistics are collected in real-time throughout the network and forwarded to the Cisco WAN Manager workstation for logging and display. The link from the node to the Cisco WAN Manager workstation uses a protocol to acknowledge receipt of each statistics data packet.

For more details on statistics and statistical alarms, refer to the Cisco WAN Manager User’s Guide.

Node Synchronization

A BPX service switch network provides network-wide, intelligent clock synchronization. It uses a fault-tolerant network synchronization architecture recommended for Integrated Services Digital Network (ISDN). The BPX switch internal clock operates as a Stratum 3 clock per ANSI T1.101.

Because 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. You can configure any network access input 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 IGX switch or other network device to the BPX switch and the network. In nodes equipped with optional redundancy, the standby hardware is locked to the active hardware to minimize system disruption during system switchovers.

Switch Software Description

The following are the sources used to configure the BPX Service Node to select the clock:

• External (T1/E1)

• Line (DS3/E3)

• Internal

Switch Software Description

The Cisco WAN switching cell relay system software shares most core system software, as well as a library of applications, between platforms. System software provides basic management and control capabilities to each node.

BPX node system software manages its own configuration, fault-isolation, failure recovery, and other resources. Because no remote resources are involved, rapid response to local problems. This distributed network control, rather than centralized control, provides increased reliability.

Software among multiple nodes cooperates to perform network-wide functions such as trunk and connection management. The multiprocessor approach ensures rapid response with no single point of failure. System software applications provide advanced features that you can install and configure as required.

The following are the software features:

• Automatic routing of connections (Automatic Routing Management feature).

• Various Classes of Service that may be assigned to each connection type (Advanced CoS

Management).

• Bandwidth reservation on a time-of-day basis.

• Detection and control of network congestion with ABR with VS/VD or Optimized Bandwidth

Management (ForeSight) algorithms.

Release 9.3.30, Part Number 78-12907-01 Rev. E0, May 2005

Cisco BPX 8600 Series Installation and Configuration

1-29

Page 80

Switch Software Description

• Automatic self-testing of each component of the node.

• Automatic collecting and reporting of many network-wide statistics, such as trunk loading,

connection usage, and trunk error rates, as specified.

The system software, configuration database, and the firmware that controls the operation of each card type is resident in programmable memory and can be stored off-line in the Cisco WAN Manager NMS for immediate backup if necessary. This software and firmware is easily updated remotely from a central site or from Cisco Customer Service, which reduces the likelihood of early obsolescence.

Connections and Connection Routing

The routing software supports the establishment, removal and rerouting of end-to-end channel connections. The following are the three routing modes:

• Automatic routing—Allows the system software to compute the best route for a connection.

• Manual routing—Specifies the route for a connection.

• Alternate routing—Allows the system software to automatically reroute a failed connection.

The system software uses the following criteria when it establishes an automatic route for a connection:

Chapter 1 The BPX Switch: Functional Overview

• Selects the most direct route between two nodes.

• Selects unloaded lines that can handle the increased traffic of additional connections.

• Takes into consideration user-configured connection restrictions, for example, whether or not the

connection is restricted to terrestrial lines or can include satellite hops or routes configured for route diversity.

When a node reroutes a connection, it uses these criteria and also looks at the priority that has been assigned and any user-configured routing restrictions. The node analyzes trunk loading to determine the number of cells or packets the network can successfully deliver. Within these loading limits, the node can calculate the maximum combination allowed on a network trunk of each type of connection, for example, synchronous data, ATM traffic, Frame Relay data, multimedia data, voice, and compressed voice.

Network-wide T3, E3, OC-3, or OC-12 connections are supported between BPX switches terminating ATM user devices on the BPX switch UNI ports. The connections are routed using the virtual path or virtual circuit addressing fields in the ATM cell header.

Narrowband connections are routed over high-speed ATM backbone networks built on BPX broadband switches. FastPacket addresses are translated into ATM cell addresses that are then used to route the connections between BPX switches, and to ATM networks with mixed vendor ATM switches. Routing algorithms select broadband links only, which avoids narrowband nodes that could create a choke point.

Connection Routing Groups

1-30

The rerouting mechanism ensures that connections are presorted in order of cell loading when they are added. Each routing group contains connections with loading in a particular range. The group containing the connections with the largest cell loadings is rerouted first, and subsequent groups are then rerouted on down to the last group that contains connections with the smallest cell loadings.

Cisco BPX 8600 Series Installation and Configuration

Release 9.3.30, Part Number 78-12907-01 Rev. E0, May 2005

Page 81

Chapter 1 The BPX Switch: Functional Overview

The following are three configurable parameters to configure the rerouting groups:

• Total number of rerouting groups

• Starting load size of first group

• Load size range of each group

You configure the three routing group parameters by using the cnfcmparm command.

For example, there might be 10 groups, with the starting load size of the first group at 50, and the incremental load size of each succeeding group being 10 cells. Then group 0 would contain all connections requiring 0 to 59 cell load units, group 1 would contain all connections requiring from 60 to 69 cell load units, on up through group 9 which would contain all connections requiring 140 or more cell load units.

An example of the routing group configuration is listed in Table 1-2.

Table 1-2 Routing Group Configuration Example

Routing Group Connection Cell Loading

00 to 59

160 to 69

270 to 79

380 to 89

490 to 99

5 101 to 109

6 110 to 119

7 120 to 129

8 130 to 139

9 140 and up

Switch Software Description

Cost-Based Connection Routing

In standard Automatic Routing Management, the path with the fewest number of hops to the destination node is chosen as the best route. Cost-based route selection uses an administrative trunk cost routing metric. The path with the lowest total trunk cost is chosen as the best route.

Cost-based route selection is based on Dijkstra’s Shortest Path Algorithm, which is widely used in network routing environments. You can use cost-based route selection, such as cost-based Automatic Routing Management to give preference to slower privately owned trunks over faster public trunks that charge based on usage time. While providing a more standard algorithm for route selection, network operators more have control over the usability of the network trunks.

Release 9.3.30, Part Number 78-12907-01 Rev. E0, May 2005

Cisco BPX 8600 Series Installation and Configuration

1-31

Page 82

Switch Software Description

Major Features of Cost-Based Automatic Routing Management

The following are major functional elements of Cost-Based Route Selection:

• Enabling Cost-Based Route Selection—Enables cost-based route selection at any time and does not

require special password access. The default algorithm is the hop-based algorithm.

• Configuring Trunk Cost—Assigns a trunk cost to each trunk, such as physical and virtual in the

network. One cost is assigned per trunk; no separate costs are used for different connection or service types. The valid range of trunk costs is 1 (lowest cost) to 50 (highest cost). A trunk has a default cost of 10 upon activation. The cost of a trunk is changed before or after the trunk is added to the network topology.

The cost can also be changed after connections have been routed over the trunk. Such a change does not initiate automatic connection rerouting, nor does it cause any outage to the routed connections. If the new trunk cost causes the allowable route cost for any connections to be exceeded, the connections must be manually rerouted to avoid the trunk. Large-scale simultaneous network-wide rerouting is avoided and gives you control over the connection reroute outage.

• Cache vs. On-Demand Routing—Specifies that Hop-Based Route Selection always requires

on-demand routing in previous releases. 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.

Chapter 1 The BPX Switch: Functional Overview

The cache contains lowest cost routes as they are selected. Subsequent routing cycles use these existing routes if the routing criteria are met. Otherwise, on-demand routing is initiated. This caching greatly benefits environments where routing criteria is very similar among connections.

Enabling cost-based route selection automatically enables cache usage. Enabling Hop-Based Route Selection automatically disables cache usage. Cache usage can also be independently enabled or disabled for both types of route selection.

• On-Demand Lowest Cost Route Determination—Specifies that on-demand routing selects the

current lowest cost route to the destination node. This lowest cost route is bounded by the maximum route length of 10 hops. If more than one route of similar cost and distance is available, the route with most available resources is chosen. No route grooming occurs after the initial routing. A connection does not automatically reroute if the route cost changes over time. A connection also does not automatically reroute if a lower cost route becomes available after the initial routing. However, a forced reroute or a preferred route can be used to move the connection to a lower cost route.

• Delay-Sensitive Routes—Specifies that the delay-sensitive IGX connection types, such as voice and

nontimestamped data is configured to use the worst case queueing delay per trunk, rather than the configured trunk cost, in the lowest-cost route determination. The trunk delay acts as the cost attribute in the Dijkstra algorithm. The default mode for the delay sensitive connections is to use the trunk cost. All other connection types always use the trunk cost in the route determination.

Automatic Routing Management does not use the worst case end-to-end queueing delay in route selection for delay sensitive BPX connection types (ATM CBR). Cost-based route selection does not change this.

• Cost Cap—Determines a maximum allowable cost value, such as cost cap that is used during route

determination to prevent selection of a route, which exceeds an acceptable cost. For routing based on delay, the cost cap is the acceptable end-to-end delay for the connection type. This cap is configured network-wide per delay sensitive connection type.

1-32

For routing based on trunk cost, the cost cap is the acceptable end-to-end cost. This cap is configured per connection. The default cost cap is 100, which is derived from the maximum hops per route (10) and default cost per trunk (10). You can change the cost cap at any time. If the cost cap is decreased

Cisco BPX 8600 Series Installation and Configuration

Release 9.3.30, Part Number 78-12907-01 Rev. E0, May 2005

Page 83

Chapter 1 The BPX Switch: Functional Overview

below the current route cost, the connection is not automatically rerouted. A manual reroute is required to route the connection to fit under the new cost cap. This gives you more control over the connection reroute outage.

• Hop-Based Route Selection—Specifies that Automatic Routing Management is used in the

hop-based route selection. The cost of all trunks is set to the default cost (10). The cost cap of all connections is set to the maximum allowable cost (100). All other new cost-based routing parameters are set to regular default values.

• Automatic Routing Management Interoperability—Because Automatic Routing Management is

source-based, nodes can interoperate using different route selection algorithms. The originating node computes the full end-to-end route based on its own knowledge of the network topology. The route is then passed to the subsequent nodes on the route. Source routing allows a mix of Cost-Based and Hop-Based Route Selection to run in a network.

Cost-Based Automatic Routing Management Commands

You use these switch software Command Line Interface (CLI) commands for cost-based route selection as described in Table 1-3. For detailed information about the use of BPX switch commands, refer to the Cisco WAN Switching Command Reference.

Switch Software Description

Table 1-3 Commands Used for Cost-Based Route Selection

Name Description

cnfcmparm Enables cost-based route selection. This is a SuperUser command to configure all Automatic Routing

Management 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. The configuration is node-based, not network-based, which allows each node to have its own route selection algorithm.

Enabling cost-based route selection automatically enables cache usage. Disabling cost-based route selection automatically disables cache usage. Cache usage may also be independently enabled or disabled.

cnftrk Configures the administrative cost for a trunk. Both physical and virtual trunks have the cost attribute. Each

trunk has a cost ranging from 1 (lowest) to 50 (highest). The default cost is 10 upon trunk activation.

The cost can be configured from either end of the trunk. The cost can be changed before or after the trunk has been added to the network. The cost can also be changed after connections have been routed over the trunk. Any cost change is updated network-wide. Every node in the network stores the cost of every trunk in the network. This knowledge is required for successful source-based routing.

cnfrtcost Configures the cost cap for a connection. This command is valid only at the node where the connection is

added.

cnfsysparm Configures the delay cost cap for all delay sensitive connections in the network.

dspcon Displays the maximum and current costs for a connection route.

dspload Displays the administrative cost and queue delay for a network trunk.

dsprts Displays the current costs for all connection routes.

dsptrkcnf Displays the configured cost of a trunk.

Release 9.3.30, Part Number 78-12907-01 Rev. E0, May 2005

Cisco BPX 8600 Series Installation and Configuration

1-33

Page 84

Network Synchronization

Cisco WAN switching cell relay networks use a fault-tolerant network synchronization method of the type recommended for Integrated Services Digital Network (ISDN). You can select any circuit line, trunk, or an external clock input to provide a primary network clock. Any line can be configured as a secondary clock source in the event that the primary clock source fails.

All nodes are equipped with a redundant, high-stability internal oscillator that meets Stratum 3 (BPX) or Stratum 4 requirements. Each node keeps a map of the network's clocking hierarchy. The network clock source is automatically switched in the event of failure of a clock source.

There is less likelihood of a loss of data resulting from reframes that occur during a clock switchover or other momentary disruption of network clocking with cell-based networks than there is with traditional TDM networks. Data is held in buffers and packets are not sent until a trunk has regained frame synchronism to prevent loss of data.

Switch Availability

This section describes some of the features that contribute to network availability. Cisco WAN hardware and software components are designed to provide a switch availability in excess of 99.99 percent. Network availability is impacted by link failure, which has a higher probability of occurrence than equipment failure.

Chapter 1 The BPX Switch: Functional Overview

Cisco WAN network switches are designed so that connections are automatically rerouted around network trunk failures, often before users detect a problem. System faults are detected and corrective action taken often before they become service affecting.

Node Redundancy

System availability is a primary requirement with the BPX switch. The designed availability factor of a BPX switch is 99.99 percent based on a node equipped with optional redundancy and a network designed with alternate routing available. The system software, as well as firmware for each individual system module, incorporates various diagnostic and self-test routines to monitor the node for proper operation and availability of backup hardware.

For protection against hardware failure, a BPX switch shelf can be equipped with the following redundancy options:

• Redundant common control modules

• Redundant crosspoint switch matrixes

• Redundant high-speed data and control lines

• Redundant power supplies

• Redundant high-speed network interface cards

• Redundant service interface cards

If redundancy is provided for a BPX switch, when a hardware failure occurs, a hot-standby module is automatically switched into service, replacing the failed module. All cards are hot-pluggable, so replacing a failed card in a redundant system can be performed without disrupting service.

1-34

Cisco BPX 8600 Series Installation and Configuration

Release 9.3.30, Part Number 78-12907-01 Rev. E0, May 2005

Page 85

Chapter 1 The BPX Switch: Functional Overview

Since the power supplies share the power load, redundant supplies are not idle. All power supplies are active; if one fails, then the others pick up its load. The power supply subsystem is sized so that if any one supply fails, the node continues to be supplied with adequate power to maintain normal operation of the node. The node monitors each power supply voltage output and measures cabinet temperature to be displayed on the NMS terminal or other system terminal.

Node Alarms

Each BPX switch shelf within the network runs continuous background diagnostics to verify the proper operation of all active and standby cards, backplane control, data, and clock lines, cabinet temperature, and power supplies. Background tests are transparent to normal network operation.

Each card in the node has front-panel LEDs to indicate active, failed, or standby status.

Each power supply has green LEDs to indicate proper voltage input and output.

An Alarm, Status, and Monitor card collects all the node hardware status conditions and reports it using front panel LED indicators and alarm closures. Indicators are provided for major alarm, minor alarm, ACO, power supply status, and alarm history. Alarm relay contact closures for major and minor alarms are available from each node through a 15-pin D-type connector for forwarding to a site alarm system.

Switch Availability

BPX switches are completely compatible with the network status and alarm display provided by the Cisco WAN Manager NMS workstation. In addition to providing network management capabilities, major and minor alarm status are displayed on the topology screen for all nodes in a network.

The Cisco WAN Manager NMS also provides a maintenance log capability with configurable filtering of the maintenance log output by node name, start time, end time, alarm type, and user-specified search string.

Release 9.3.30, Part Number 78-12907-01 Rev. E0, May 2005

Cisco BPX 8600 Series Installation and Configuration

1-35

Page 86

Switch Availability

Chapter 1 The BPX Switch: Functional Overview

1-36

Cisco BPX 8600 Series Installation and Configuration

Release 9.3.30, Part Number 78-12907-01 Rev. E0, May 2005

Page 87

CHAPT E R

BPX Switch Physical Overview

This chapter describes the physical components of the BPX switch.

Contents of this chapter include:

• BPX Switch Enclosure

• Card Shelf Configuration

• BPX Switch Major Hardware Component Groups

• Service Expansion Shelf PNNI

• Optional Peripherals

The BPX switch is supplied as a stand-alone assembly. It may be utilized as a stand-alone ATM switch, or it may be integrated at customer sites with one or more multiband IGX switches, MGX 8220 or MGX 8800 shelves, SES PNNI shelves, and other access devices to provide network access to broadband backbone network links for narrowband traffic. Cisco and CPE service interface equipment can also be collocated with the BPX switch and connect to its ATM service interfaces.

BPX Switch Enclosure

The BPX switch enclosure is a self-contained chassis, which may be rack mounted in any standard 19-inch rack or enclosure with adequate ventilation. It contains a single shelf that provides fifteen slots for vertically mounting the BPX switch cards front and rear.

At the front of the enclosure (see Figure 2-1) are 15 slots for mounting the BPX switch front cards. Once inserted, the cards are locked in place by the air intake grille at the bottom of the enclosure.

To remove or insert cards, a mechanical latch on the air intake grille must be released by using a screwdriver and the grille must be tilted forward in order.

At the rear of the enclosure (see Figure 2-2) is another series of card slots for mounting the rear plug-in cards. These are held in place with two thumbscrews, top and bottom. A mid-plane, located between the two sets of plug-in cards, is used for interconnect and is visible only when the cards are removed.

Warning

Release 9.3.30, Part Number 78-12907-01 Rev. E0, May 2005

To provide proper cooling, it is essential that blank faceplates be installed in all unused slots. Failure to do so will degrade node cooling and circuit card damage will result. The blank faceplates also provide RFI shielding.

Cisco BPX 8600 Series Installation and Configuration

2-1

Page 88

BPX Switch Enclosure

Chapter 2 BPX Switch Physical Overview

Figure 2-1 BPX Switch Exterior Front View

17 3/4"

27"

Node Cooling

Air intake

Slot #1

1 2 3

4 5 6 7 8 9 10 11 12 13 14

19"

Slot #15

22 3/4"

Extractor handles

H8018

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). Air for cooling the cards is drawn through an air intake grille located at the bottom in the front of the enclosure. Air passes up between the vertically-mounted cards and exhausts at the top, rear of the chassis.

2-2

All unused slots in the front are filled with blank faceplates to channel airflow properly.

Cisco BPX 8600 Series Installation and Configuration

Release 9.3.30, Part Number 78-12907-01 Rev. E0, May 2005

Page 89

Chapter 2 BPX Switch Physical Overview

Figure 2-2 BPX Switch Exterior Rear View

Fans

Air Exhaust

Slot #15

Back Cards

–

3/T

–

3/T

A S

14 13 12 11 10

BPX Switch Enclosure

Slot #1

L M

–

3/T3

–

3/T3

L M

–

3/T

–

3/T

–

3/T

–

3/T3

–

3/T

–

C C

3/T3

–

3/T

–

3/T3

–

3/T3

5432

–

3/T3

–

Node DC Powering

The primary power for a BPX switch node is -48 VDC, which is bused across the backplane for use by all card slots. DC-to-DC converters on each card convert the -48V to lower voltages for use by the card.

The -48 VDC input connects directly to the DC Power Entry Module (PEM). The DC Power Entry Module (see Figure 2-3) provides a circuit breaker and line filter for the DC input.

Nodes may be equipped with either a single PEM or dual PEMs for redundancy. PEMs 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.

H8017

Release 9.3.30, Part Number 78-12907-01 Rev. E0, May 2005

Cisco BPX 8600 Series Installation and Configuration

2-3

Page 90

BPX Switch Enclosure

Chapter 2 BPX Switch Physical Overview

Figure 2-3 DC Power Entry Module Shown with Conduit Box Removed

CB1

OFF

USE COPPER

CONDUCTORS ONLY

SAFETY

GROUND

+RTN

–48V

Plastic Cover

DC Terminal Block

Optional AC Power Supply Assembly

For applications requiring operation from an AC power source, an optional AC Power Supply Assembly and shelf is available. It provides a source of –48 VDC from 208/240 VAC input. A shelf, separate from the BPX switch shelf, houses one or two AC Power Supplies and mounts directly below the node cabinet. This provides a secure enclosure for the power supply assemblies (supplies cannot be removed without the use of tools).

Two of these supplies are usually operated in parallel for fail-safe redundant operation. The front of the AC Power Supplies for the BPX switch includes two green LEDs to indicate correct range of the AC input and the DC output for each individual supply (see Figure 2-4).

H8019

2-4

Figure 2-4 AC Power Supply Assembly Front View

Indicator

LEDS

H8145

Cisco BPX 8600 Series Installation and Configuration

Release 9.3.30, Part Number 78-12907-01 Rev. E0, May 2005

Page 91

Chapter 2 BPX Switch Physical Overview

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.

The other twelve slots, number 1 through number 6 and number 8 through number 14, can be used for the Network Interface and Service Interface cards.

Figure 2-5 BPX Switch Card Shelf Front View

Card Shelf Configuration

General

act failstby

BCC/

PRI

status

port

act failstby

card

BNI-3/T3

81234

purpose

card slots

1234567

status

port

act failstby

card

BNI-3/T3 81234

status

port

act failstby

card

BNI-3/T3

81234

BCC-A8BCC-B

LAN

act failstby

card

BNI-3/T3

BCC-15 81234

81236

BCC/

SEC

LAN

act failstby

card

BCC-15 81236

status

port

card

BNI-3/T3 81234

purpose

card slots

9 101112131415

status

act failstby

status

port

act failstby

card

BNI-3/T3

81234

act failstby

22222222222

port

card

BNI-3/T3 81234

General

ASM

status

major minor

port

alarms

DC ok

ACO hist

ACO

history clear

act failstby

card

BNI-3/T3 81234

act failstby

card

BNI-3/T3

ASM

81234

81237

Release 9.3.30, Part Number 78-12907-01 Rev. E0, May 2005

H8020

Cisco BPX 8600 Series Installation and Configuration

2-5

Page 92

Chapter 2 BPX Switch Physical Overview

BPX Switch Major Hardware Component Groups

The following are the four major groups of hardware components in the BPX switch:

• Common Core Components

• Network Interface Components

• Service Interface Components

• Power Supply Components

Table 2-1 lists these groups and their components along with a brief description of each.

Table 2-1 BPX Switch Plug-In Card Summary

Card Card Name Location

Common Core Component Group

BPX-

BPX-BCC-32 Broadband Controller Card, operates with versions of System Software

Release 7.0 and above, and requires 32 Mbyte RAM for 8.1 and later software. For redundancy configuration, installed as a pair of BCC-32s. (System operation equivalent to BCC-3.)

BPX-BCC-bc Back card (also known as LM-BCC) used only with the BCC-32. Back

BPX-BCC-3-64 Broadband Controller Card, enhanced BCC-3.

Front

Note BCC-3-64 or BCC-4 is required to support VSI and MPLS.

BPX-BCC-4 Broadband Controller Card, operates with 8.4 software and above. For redundancy

Front configuration, installed as a pair of BCC-4s. Provides 64 Mbyte of RAM and above. Supports up to 19.2 Gbps performance of BXM cards.

Note BCC-3-64 or BCC-4 is required to support VSI and MPLS

BPX-BCC-3-bc Back card (also known as LM-BCC) used with BCC-4. Back

BPX-ASM Alarm/Status Monitor Card. Front

BPX-ASM-BC Line Module - Alarm/Status Monitor. Back

Network Interface Component Group

BPX-BXM-T3-8 BPX-BXM-E3-8

T3/E3 card with 8 or 12 ports. Card is configured for use in either network interface or service access (UNI) mode and with either a T3 or E3 interface.

Front

BP:X-BXM-T3-12 BPX-BXM-E3-12

BPX-T3/E3-BC Back card for use with a BXM-T3/E3-8 or BXM-T3/E3-12 Back

BPX-BXM-155-4 BPX-BXM-155-8

BPX-MMF-155-4-BC

BXM OC-3 cards with 4 or 8 OC-3/STM-1ports, respectively. Card is configured

Front for use in either network interface or service access (UNI) mode.

Back cards for BXM-155-4. Back

BPX-SMF-155-4-BC BPX-SMFLR-155-4-BC

BPX-MMF-155-8-BC

Back cards for BXM-155-8. Back

BPX-SMF-155-8-BC BPX-SMFLR-155-8-BC

2-6

Cisco BPX 8600 Series Installation and Configuration

Release 9.3.30, Part Number 78-12907-01 Rev. E0, May 2005

Page 93

Chapter 2 BPX Switch Physical Overview

Service Expansion Shelf PNNI

Table 2-1 BPX Switch Plug-In Card Summary (continued)

Card Card Name Location

BPX-BXM-622 BPX-BXM-622-2

OC-12 card with 1or 2 OC-12/STM-4 ports. Card is configured for use in either network interface or service access (UNI) mode.

Front

BPX-BME Used for multicast connections. Used with SMF-622-2 back card with port 1

looped to port 2, transmit to receive, and receive to transmit.

BPX-SMF-622

Back cards for BXM-622. The XLR card supports a 1500nm interface. Back BPX-SMFLR-622 BPX-XLR-622-BC

BPX-SMF-622-2-BC

Back cards for BXM-622-2 and BME (BME typically would use SMF-622-2). Back BPX-SMFLR-622-2-BC BPX-SMFLR-622-2-BC

BPX-BME Used for multicast connections. Used with SMF-622-2 back card with port 1

Back

looped to port 2, transmit to receive, and receive to transmit.

BPX-BNI-3-T3 Broadband Network Interface Card (with 3 T3 Ports). Front

BPX-T3-BC Line Module, used with BNI-T3 for 3 physical T3 ports. (Configured for 3 ports) Back

BPX-BNI-3-E3 Broadband Network Interface Card (with 3 E3 Ports). Front

BPX-E3-BC Line Module, used with BNI-E3 for 3 physical E3 ports. (Configured for 3 ports). Back

APS Back Cards and APS Redundant Backplane

The APS 1+1 feature requires two BXM front cards, an APS redundant frame assembly, and two redundant type BXM back cards. The following are the types of redundant back card and backplane sets:

• BPX-RDNT-LR-155-8 (8 port, long reach, SMF, SC connector)

• BPX-RDNT-LR-622 (single port, long reach, SMF, FC connector)

• BPX-RDNT-SM-155-4 (4 port, medium reach, SMF, SC connector)

• BPX-RDNT-SM-155-8 (8 port, medium reach, SMF, SC connector)

• BPX-RDNT-SM-622 (single port, medium reach, SMF, FC connector)

• BPX-RDNT-SM-622-2 (2 port, medium reach, SMF, FC connector)

Each of the listed model numbers includes two single back cards and one mini-backplane.

Service Interface Component Group

BPX-E3-BC Line Module, used with BNI-E3 for 2 physical E3 ports. (Configured for 2 ports) Back

Power Supply Group

48 Volt DC Power Supply

Optional AC Power Supply

Service Expansion Shelf PNNI

The Cisco BPX SES PNNI Controller is an optional Service Expansion Shelf (SES) controller connected directly to a BPX 8600 series switch to provide Private Network to Network Interface (PNNI) signaling and routing for the establishment of ATM switched virtual circuits (SVCs) and Soft Permanent Virtual Circuits (SPVCs) over a BPX 8600 wide area network. However, the SES can be used in several WAN switching applications and is not limited to function only as a BPX SES PNNI Controller.

Release 9.3.30, Part Number 78-12907-01 Rev. E0, May 2005

Cisco BPX 8600 Series Installation and Configuration

2-7

Page 94

Optional Peripherals

Every BPX 8600 series switch that deploys PNNI signaling and routing is collocated and attached to a BPX SES PNNI Controller. The BPX SES PNNI Controller uses the Cisco Virtual Switch Interface (VSI) protocol to control the BPX switch for the networking application.

The BPX SES PNNI Controller is a 7-slot chassis that contains two Processor Switch Modules (PXMs), which run the PNNI and SVC software. One of the PXMs serves as the active processor, while the other serves as the standby. The PNNI controller is mounted directly atop the BPX switch and cabled to it through either the OC-3 ATM interface (see Figure 1-3) or the DS3 interfaces (see Figure 1-4).

For instructions on installing a Service Expansion Shelf in a BPX 8620 rack and initially powering up, refer to the Cisco Service Expansion Shelf (SES) Hardware Installation Guide. To configure an SES PNNI for a BPX 8620, refer to the Cisco SES PNNI Controller Software Configuration Guide.

Optional Peripherals

At least one node in the network (or network domain if a structured network) must include a Cisco WAN Manager network management station (see Figure 2-6).

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, because only one BCC is active at a time.

Chapter 2 BPX Switch Physical Overview

The serial control port may be connected to a dial-in modem for remote service support or other dial-up network management access. The serial auxiliary port can be used for incoming and outgoing data as well as the Autodial feature to report alarms to Cisco TAC.

Figure 2-6 Optional Peripherals Connected to BPX Switch

Corporate network

AUI

BCC-LM

* *

StrataView plus

Modem

active

Stratabus

BCC-LM

standby

2-8

BCC

Printer

H8157

Two ports on BCC-LM can be used to connect up to two (2) of the peripherals shown.

Cisco BPX 8600 Series Installation and Configuration

Release 9.3.30, Part Number 78-12907-01 Rev. E0, May 2005

Page 95

CHAPT E R

BPX Switch Common Core Components

This chapter describes the common core hardware components for the BPX switch.

Contents of this chapter include:

• Broadband Controller Card

• Alarm/Status Monitor Card

• BPX Switch StrataBus 9.6 and 19.2 Gbps Backplanes

The BPX switch Common Core group includes the components shown in Figure 3-1:

• Broadband Controller Cards:

–

BCC-4 back card

–

BCC-32 and associated BCC15-BC back card

Note The BCC-4 is required for the Virtual Switch Interface (VSI) and Multiprotocol Label

Switching (MPLS) features operation

• Alarm/Status Monitor (ASM), a Line Module for the ASM card (LM-ASM).

• StrataBus backplane.

The BCC-4V provides a 16 x 32 crosspoint switch architecture to extend the BPX peak switching capability from 9.6 up to 19.2 Gbps peak. The BCC-4V also provides 4 MBytes of BRAM and 128 MBytes of DRAM.

The following are the functions of the common core components shown in Figure 3-1:

• ATM cell switching.

• Internal node communication.

• Remote node communication.

• Node synchronization.

• Network management communications (Ethernet), local management (RS-232).

• Alarm and status monitoring functions.

Release 9.3.30, Part Number 78-12907-01 Rev. E0, May 2005

Cisco BPX 8600 Series Installation and Configuration

3-1

Page 96

Broadband Controller Card

The Broadband Controller Card (BCC) is a microprocessor-based system controller, which 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.

For nonredundant nodes, a single BCC is used in front slot number 7 with its appropriate back card.

For redundant nodes, a pair of BCCs of matching type, are used in front slot numbers 7 and 8.

Note The three types of BCCs with their proper back cards may be operated together temporarily for

maintenance purposes, for example, replacing a failed controller card. Throughout a network, individual BPX switches may have either a single BCC-4V controller card or a pair of the identical type of BCC.

Figure 3-1 Common Core Group Block Diagram

Chapter 3 BPX Switch Common Core Components

EXT/INT

clock

Broadband

Line

module-

BCC

controller

card

primary

NMS

port

Line

module-

BCC

Broadband

controller

card

redundant

Common

core

group

StrataBus backplane

Alarm

outputs

Line

module-

ASM

Alarm/

status

monitor

3-2

Interface

card

The term BCC refers to the functional operation of the Broadband Controller Card. When a difference in operation does occur, the specific type of BCC is specified.

Cisco BPX 8600 Series Installation and Configuration

Interface

card

Interface

card

H8023

Release 9.3.30, Part Number 78-12907-01 Rev. E0, May 2005

Page 97

Chapter 3 BPX Switch Common Core Components

The BCC-4V provides a 16 x 32 cross-point architecture that increases the peak switching capacity of the BPX switch to 19.2 Gbps, with a sustained nonblocking throughput of 9.6 Gbps.

For information to operate the BPX at 19.2 Gbps with the BCC-4V and to program the NOVRAM, see the Verifying 9.6 or 19.2 Gbps Backplane section of Chapter 13, “Installing the BPX Switch Cards.”

Features

The Broadband Controller Card performs the following major system functions:

• Runs the system software for controlling, configuring, diagnosing, and monitoring the BPX switch.

• Contains the crosspoint switch matrix operating at 800 Mbps per serial link or up to 1600 Mbps

(BCC-4V).

• Contains the arbiter which controls the polling each high-speed data port and grants the access to

the switch matrix for each port with data to transfer.

• Generates Stratum-3 system clocking and can synchronize it to either a selected trunk or an external

clock input.

• Communicates configuration and control information to all other cards in the same node over the

backplane communication bus.

Broadband Controller Card

• Communicates with all other nodes in the network.

• Provides a communications processor for an Ethernet LAN port plus two low-speed data ports. The

BCC15-BC provides the physical interface for the BCC-32. The BCC-3-BC provides the physical interface for the BCC-3-32M, BCC-3-64M, and BCC-4V.

The following are the features for the Broadband Controller Card:

• 68EC040 processor operating at 33 MHz.

• 32 Mb or 64 MB option for BCC-4.

• 4 Mb of Flash EEPROM for downloading system software.

• 512 Kbytes of BRAM for storing configuration data.

• EPROM for firmware routines.

• 68302 Utility processor.

• SAR engine processor operating at 33 MHz.

• Communication bus interface.

• HDLC processor for the LAN connection interface.

• Two RS-232 serial port interfaces.

Release 9.3.30, Part Number 78-12907-01 Rev. E0, May 2005

Cisco BPX 8600 Series Installation and Configuration

3-3

Page 98

Broadband Controller Card

Functional Description

The BPX switch is a space switch, which 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 BCCs (see Figure 3-2):

• Central Arbiter on each BCC.

• Crosspoint Switch.

–

16 X 32 Crosspoint Switching Matrix on each BCC (2 X [12 X 12]) used for BCC-4V.

• Serial Interface and LAN Interface Modules on each BCC and on each Function Module.

The arbiter polls each card to see if it has data to transmit. It then configures the crosspoint switching matrix to make the connection between the two cards. Each connection is unidirectional and has a capacity of 800 Mbps (616.7 Mbps for cell traffic plus the frame overhead).

Only one connection at a time is allowed to an individual card.

Each card contains a Switch Interface Module (SIM), which provides a standardized interface between the card and the data lines and polling buses. The SIM responds to queries from the BCC indicating whether it has data ready to transmit.

Chapter 3 BPX Switch Common Core Components

With the BPX switch equipped with two BCCs, the cell switching is completely redundant in that there are always two arbiters, two crosspoint switches, two completely independent data buses, and two independent polling buses.

The BCC incorporates nonvolatile flash EEPROM, which permits new software releases to be downloaded over the network and battery-backup RAM (BRAM) for storing user system configuration data. The memory features maintain system software and configuration data even during power failures, eliminating the need to download software or reconfigure after the power returns.

The BPX switch cell switching is not synchronized to any external clocks; it runs at its own rate. No switch fabric clocks are used to derive synchronization nor are these signals synchronized to any external sources.

Node clocking is generated by the BCC. Because the BPX switch resides as an element in a telecommunications network, it is capable of synchronizing to higher-stratum clocking devices in the network and providing synchronization to lower stratum devices. The BCC can be synchronized to any one of three different sources under software control:

• An internal, high-stability oscillator.

• Derived clock from a BNI module.

• An external clock source connected directly to the BPX.

The BCC clock circuits provide clocking signals to every other card slot. If a function card needs to synchronize its physical interface to the BPX switch clock, it can use this timing signal to derive the proper reference frequency. These reference frequencies include DS1, E1, DS3, and E3.

3-4

Cisco BPX 8600 Series Installation and Configuration

Release 9.3.30, Part Number 78-12907-01 Rev. E0, May 2005

Page 99

Chapter 3 BPX Switch Common Core Components

Figure 3-2 BCC-4V Block Diagram

Broadband Controller Card

I/O

module 1

DRSIU

I/O

module 2

DRSIU

TX data-2A

RX data-2A

TX data-12A

RX data-12A

s6392

I/O

module 12

DRSIU

TX data-1B

RX data-1B

TX data-2B

TX data-1A

RX data-1A

Polling bus-A

Polling bus-B

BCC-A

Arbiter

SIU

Front Panel Description

The BCC front panel has four Led, three card status LEDs, and a LAN LED (see Figure 3-3 and Table 3-1).

Table 3-1 BCC Front Panel Indicators

Number Indicator Function

1 LAN Indicates there is data activity over the Ethernet LAN port.

2 card - act Card active LED indicates this BCC is online and actively controlling

3 card - stby Card standby LED indicates this BCC is offline but is ready to take over

4 card - fail Card fail LED indicates this BCC has failed the internal self-test routine

RX data-2B

TX data-12B

RX data-12B

the node.

control of the node at a moments notice.

and needs to be reset or replaced.

BCC-A

16 x 32 Xpoint switch 16 x 32 Xpoint switch

S6393

Release 9.3.30, Part Number 78-12907-01 Rev. E0, May 2005

Cisco BPX 8600 Series Installation and Configuration

3-5

Page 100

Broadband Controller Card

Figure 3-3 BCC Front Panel

Chapter 3 BPX Switch Common Core Components

LAN

act failstby

card

act failstby

H8024

3-6

Cisco BPX 8600 Series Installation and Configuration

Release 9.3.30, Part Number 78-12907-01 Rev. E0, May 2005

Cisco BPX 8620, BPX 8650, BPX 8680, BPX 8680-IP Installation And Configuration Manual

Cisco BPX 8600 Series Installation and Configuration

CONTENTS

Objectives

About This Guide

Audience

Organization

Cisco WAN Switching Product Name Change

Related Documentation

Cisco WAN Manager Release 10.5 Documentation

Cisco MGX 8850 Release 2.1 Documentation

SES PNNI Release 1.1 Documentation

Cisco WAN Switching Software, Release 9.3 Documentation

MGX 8850 Multiservice Switch, Release 1.1.40 Documentation

MGX 8250 Edge Concentrator, Release 1.1.40 Documentation

MGX 8230 Multiservice Gateway, Release 1.1.40 Documentation

Conventions

Obtaining Documentation

World Wide Web

Documentation CD-ROM

Ordering Documentation

Documentation Feedback

Obtaining Technical Assistance

Cisco.com

Technical Assistance Center

Cisco TAC Web Site

Cisco TAC Escalation Center

The BPX Switch: Functional Overview

The BPX 8600 Series

BPX 8620

BPX 8650

BPX 8680

BPX 8680-IP

New with Release 9.3.30

Discontinued

BPX Switch Operation

The BPX Switch with MGX 8220, MGX 8230, and MGX 8250 Shelves

Multiprotocol Label Switching

Private Network to Network Interface

Virtual Private Networks

MPLS Virtual Private Networks

Frame Relay to ATM Interworking

Network Interworking

Service Interworking

Tiered Networks

Routing Hubs and Interface Shelves

BPX Switch Routing Hubs

BPX Routing Hubs in a Tiered Network

Tiered Network Implementation

Upgrades

Network Management

Inverse Multiplexing ATM

Virtual Trunking

Traffic and Congestion Management

Advanced CoS Management

Automatic Routing Management

Cost-Based Routing Management

Priority Bumping

Concurrent Routing

ABR Standard with VS/VD Congestion Control

Optimized Bandwidth Management (ForeSight) Congestion Control

Network Management

Cisco WAN Manager

Network Interfaces

Service Interfaces

Statistical Alarms and Network Statistics

Node Synchronization

Switch Software Description

Connections and Connection Routing

Connection Routing Groups

Cost-Based Connection Routing

Major Features of Cost-Based Automatic Routing Management

Cost-Based Automatic Routing Management Commands

Network Synchronization

Switch Availability

Node Redundancy

Node Alarms

BPX Switch Physical Overview

BPX Switch Enclosure

Node Cooling