Cisco MGX 8800/8900 Series Software Configuration Guide Release 5.1 January 2005 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 Text Part Number: OL-6482-01 Rev.
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.
CONTENTS About This Guide Objectives Audience xxvii xxvii xxvii Organization xxvii Conventions xxviii Notes, Warnings, and Cautions xxix Documentation xxx Documentation Notes for these Product Releases xxx Related Documentation xxx Technical Manual Order of Use xxxi Technical Manual Titles and Descriptions xxxii Obtaining Documentation xliii Cisco.
Contents Unique Switch Name 1-12 IP Addressing Plan 1-12 ATM Addressing Plan 1-12 Administrator Data 1-13 Unique Device Identifier 1-13 MIB Field Names for UDI 1-14 Administrator Access Method 1-15 Network Clock Source Plan 1-15 Network Management Plan 1-15 Physical Location of Cards and Lines in the Switch Guidelines for Creating an IP Address Plan 1-15 1-16 Guidelines for Creating a Network Clock Source Plan 1-17 Planning for Manual Clock Synchronization 1-18 Planning for NCDP Synchronization 1-21 CH
Contents Setting the PNNI Node ID 2-27 Setting and Viewing the SPVC Prefix 2-28 Displaying PNNI Summary Addresses 2-29 Configuring the MPLS Controller 2-30 Configuring Clock Sources 2-30 Manually Configuring BITS Clock Sources Enabling NCDP on a Node 2-34 2-32 Setting the LAN IP Addresses 2-36 Setting the Boot IP Address 2-36 Setting the Disk IP Address 2-39 Starting a CLI Session Through the LAN Port 2-41 Configuring for Network Management 2-42 Configuring the SNMP Trap Source IP Address 2-43 Config
Contents Adding an IMA Link to an IMA Group 3-34 Configuring IMA Links 3-35 Adding an IMA Port 3-36 Establishing Redundancy Between Two Lines with APS 3-39 Configuring Intracard APS Lines 3-39 Configuring Intercard APS Lines 3-41 Adding ATM Ports 3-43 Modifying ATM Ports 3-46 Partitioning Port Resources Between Controllers 3-47 Selecting the Port Signaling Protocol 3-51 Defining Destination Addresses for Static Links 3-55 Assigning Static ATM Addresses to Destination Ports 3-57 Configuring ILMI on a Port 3
Contents CHAPTER 4 Preparing Service Modules for Communication Configuration Quickstart 4-1 4-2 Managing Firmware Version Levels for Service Modules Locating Cards that Need the Firmware Version Set Initializing Service Modules 4-4 Verifying Card Firmware Version Levels 4-5 4-3 4-3 Selecting MPSM Interfaces and Services 4-7 Configuring MPSM-8-T1E1 Interfaces and Services 4-7 Configuring MPSM-T3E3-155 and MPSM-16-T1E1 Interfaces and Services Establishing Redundancy Between Two Service Modules CHAPTE
Contents Managing SCTs 7-4 Locating SCT Files on a Switch 7-5 SCT File Naming Convention 7-5 Creating and Modifying SCT Files 7-6 Downloading SCT Files to the Switch 7-7 Registering SCT Files 7-7 Updating Registered SCT Files 7-9 Applying a New Major Version of an AXSM SCT to a Card or Port Deleting a Registered SCT 7-11 Deleting Unregistered SCTs 7-12 Displaying all Registered Card and Port SCTs on a Switch 7-12 Managing Card SCTs 7-10 7-13 Managing PXM1E Port SCTs 7-13 Displaying the SCT Assigned to a
Contents Creating a Preferred Route 8-13 Modifying a Preferred Route 8-17 Deleting a Preferred Route 8-18 Deleting a Node from the Network Node Table 8-19 Configuring Link Selection for Parallel Links 8-19 Configuring the Maximum Bandwidth for a Link 8-19 Configuring the Administrative Weight 8-20 Configuring the Aggregation Token 8-20 Configuring the Bandwidth Overbooking Factor 8-21 Configuring the Deroute Delay 8-22 Improving and Managing Rerouting Performance 8-23 Pure PXM45/C Networks 8-23 Hybrid Netw
Contents Enabling and Disabling the Soft Reroute IE 8-44 Displaying Node Configuration Information 8-45 Displaying the PNNI Node Table 8-45 Displaying the PNNI Summary Address 8-46 Displaying System Addresses 8-47 Displaying PNNI Interface Parameters 8-48 Displaying the PNNI Link Table 8-48 Displaying the PNNI Routing Policy 8-49 Displaying the SVCC RCC Timer 8-50 Displaying Routing Policy Parameters 8-51 Displaying the SVCC RCC Table 8-51 Managing CUGs 8-52 Assigning Address Prefixes and AESAs 8-52 Crea
Contents Displaying and Clearing ILMI Management Statistics Deleting ILMI Prefixes 9-11 Determining the Software Version Number from Filenames Displaying Software Revisions for Cards 9-14 Displaying Software Revisions in Use 9-14 Displaying Software Revisions for a Single Card 9-10 9-11 9-16 Managing Redundant Cards 9-16 Displaying Redundancy Status 9-16 Switching Between Redundant PXM Cards 9-17 Switching Between Redundant Service Modules 9-17 Removing Redundancy Between Two Cards 9-18 Switching Betwe
Contents Delete Manual Clock Sources 9-42 Restore a Manual Clock Source After Failure Displaying SVCs 9-42 9-43 Managing Controllers 9-43 Adding Controllers 9-43 Deleting a Controller 9-44 Viewing an ATM Port Configuration 9-45 Managing PXM1E Partitions 9-45 Displaying a PXM1E Resource Partition Configuration 9-46 Changing a PXM1E Resource Partition Configuration 9-47 Deleting a PXM1E Resource Partition 9-50 Removing Static ATM Addresses 9-51 Configuring VPI and VCI Ranges for SVCs and SPVCs 9-52
Contents Configuring FTP and SSH Messaging Format for AAA Servers 9-69 Displaying the TACACS+ Configuration 9-69 Displaying AAA Server Information 9-70 Displaying AAA Server Statistics 9-70 Avoiding Command Mode Authorization Issues with RPM 9-72 Verifying PXM Disk Data 9-72 Displaying the Contents of the Disk Verification Utility Log File 9-74 Troubleshooting Active and Standby Card Disk Discrepancies 9-77 Configuring a Line Loopback 9-77 Configuring Loopback Line Tests on PXM1E, AXSM, and MPSM Cards Conf
Contents Replacing Cards 10-6 Replacing PXM Cards 10-6 Automatic Response for Standalone PXM Installations 10-7 Automatic Response for Redundant PXM Installations 10-8 Manually Responding to Nativity Checks 10-9 Replacing PXM1E-4-155 Cards with PXM1E-8-155 Cards 10-9 Replacing PXM1E SC Cables with LC Cables via SC Conversion Cables 10-14 Replacing PXM45/A or PXM45/B Cards with PXM45/C Cards 10-16 Gracefully upgrade from a Redundant PXM45 Card Set to a Redundant PXM45/C Card Set 10-17 Non-gracefully Upgrade
Contents Graceful PXM Boot Upgrades from Releases Prior to Release 3.0.10 A-3 Graceful PXM Boot Upgrades from Release 3.0.
Contents Transferring Software Files to and from the Switch Clearing the Switch Configuration Initializing the PXM Hard Disk APPENDIX B-4 B-5 B-5 Supporting and Using Additional CLI Access Options C Setting Up CP Port Connections C-1 C-2 Setting Up Terminal Server Connections Setting Up Local LAN Connections C-4 C-6 Setting Up Dial-Up Connections C-6 Configuring the Switch C-8 Configuring the Router C-10 Starting a CLI Management Session Using a CP Port or Terminal Server Connection Starting a
Contents MPSM-T3E3-155 Configuration Worksheet MPSM-16-T1E1 Configuration Worksheet VISM Configuration Worksheet F MPSM Licensing E-19 E-20 VXSM Configuration Worksheet APPENDIX E-18 E-21 F-1 MPSM Licensing Information F-1 MPSM License Overview F-1 MPSM License Concepts and Terms F-4 PXM License Pool F-6 Displaying License Data F-7 Displaying All Node Licenses F-7 Displaying Licenses for a Specific MPSM Card Type F-7 Displaying the License Usage for All Cards F-8 Displaying the License Usage for
Contents Cisco MGX 8800/8900 Series Software Configuration Guide xviii Release 5.1, Part Number OL-6482-01, Rev.
F I G U R E S Figure 1-1 Core Switch Topology Figure 1-2 Multiservice Edge Aggregation Topology Figure 1-3 Virtual Trunk Topology Figure 1-4 DSL Edge Aggregation Topology Figure 1-5 Using Multiple IP Addresses for Switch Access Figure 1-6 Example Network Clock Source Topology with a Single Master Clock Source Figure 1-7 Example Network Clock Source Topology with Two Master Clock Sources Figure 1-8 Example NCDP Source Topology Figure 2-1 Workstation Connection to Console Port on a PXM-UI-S3
Figures Figure C-4 Terminal Server Connection to the Console Port on a PXM-UI-S3/B Back Card Figure C-5 Hardware Required for Dial-up Connection to a PXM45 UI-S3 Back Cards C-6 Figure C-6 Hardware Required for Dial-up Connections on a PXM-UI-S3/B Back Card C-7 Figure F-1 The Switch License Pool C-5 F-6 Cisco MGX 8800/8900 Series Software Configuration Guide xx Release 5.1, Part Number OL-6482-01, Rev.
T A B L E S Table 1 Conventions Used in this Manual Table 2 Technical Manuals and Release Notes for Cisco MGX and BPX Switches and Media Gateways (January 2005 Product Releases) xxxii Table 3 Documents that Ship with Multiservice Switch Products Table 4 Descriptions of Technical Manuals and Release Notes for Cisco Multiservice Switch Products Table 1-1 Card-specific Configuration Guides Table 1-2 Changes to This Guide Since Release 5 Table 1-3 Cisco MGX 8850 (PXM1E/PXM45), Cisco MGX 8850/B, Ci
Tables Table 3-13 ATM Address Configuration Parameters 3-56 Table 3-14 ATM Address Configuration Parameters 3-58 Table 3-15 cnfilmi Command Configuration Parameters Table 3-16 Parameter Descriptions for cnfclksrc Command when Used for PXM1E Table 3-17 Parameters for the addcon and cnfcon Commands Table 3-18 addparty Command Parameters Table 3-19 Optional Parameters for the dspcons Command Table 4-1 cnfcdmode Command Parameters Table 4-2 MPSM-8-T1E1 Card Names in the dspcd and dspcds Comm
Tables Table 8-4 Parameters for cnfpnni-timer Command Table 8-5 addnwnode Command Parameters Table 8-6 addpref Command Parameters Table 8-7 addcon and cnfcon Preferred Route Command Parameters Table 8-8 Parameters for cnfpref Command Table 8-9 cnfpri-routing Command Parameters Table 8-10 Parameters for cnfrteopt Command Table 8-11 Parameters for optrte Command 8-36 Table 8-12 Supported Grooming Thresholds 8-37 Table 8-13 Grooming Metric Selection Table 8-14 Parameters for cnfrteoptth
Tables Table 9-15 cnfncdpport Command Parameters Table 9-16 dspncdp Command Objects Table 9-17 dspncdpclksrc Command Objects Table 9-18 dspncdpclksrcs Command Objects Table 9-19 dspncdpports Command Objects Table 9-20 dspncdpport Command Objects Table 9-21 delncdpclksrc Command Objects Table 9-22 Parameters for the addcontroller Command Table 9-23 Parameters for the cnfpart Command Table 9-24 ATM Address Configuration Parameters Table 9-25 Parameters for the cnfpnportrange Command Tab
Tables Table D-3 PNNI 2.
Tables Cisco MGX 8800/8900 Series Software Configuration Guide xxvi Release 5.1, Part Number OL-6482-01, Rev.
About This Guide This preface describes the objectives, audience, organization, and conventions of the Cisco MGX 8800/8900 Series Software Configuration Guide. Objectives This guide describes how to configure the Cisco MGX 8850, Cisco MGX 8850/B, Cisco MGX 8950, Cisco MGX 8830, Cisco 8830/B switches and the Cisco MGX 8880 Media Gateway. This guide also describes how to perform some operating procedures after the switch begins operation.
About This Guide Organization • Chapter 7, “Managing Service Class Templates,” describes how to download and use service class templates for AXSM, PXM1E, and FRSM12 cards. • Chapter 8, “Managing PNNI Nodes and PNNI Routing,” provides information you can use to optimize PNNI routing. • Chapter 9, “Switch Operating Procedures,” describes how to manage your configuration after the switch is configured and during day-to-day operation.
About This Guide Organization Table 1 Conventions Used in this Manual Convention Definition Sample boldface font Commands and keywords are in boldface. This is similar to the UNIX route command. Also used for names of some elements in a graphical user interface (GUI). italic font Terminal sessions and information the system displays are in screen font. Are you ready to continue? [Y] Information you must enter is in boldface screen font.
About This Guide Documentation Tips Warning Means the following information will help you solve a problem. The tips information might not be troubleshooting or even an action, but could be useful information, similar to a Timesaver. This warning symbol means danger. You are in a situation that could cause bodily injury. Before you work on any equipment, you must be aware of the hazards involved with electrical circuitry and be familiar with standard practices for preventing accidents.
About This Guide Documentation Technical Manual Order of Use Use the technical manuals listed here in the following order: Step 1 Refer to the documents that ship with your product. Observe all safety precautions. • Regulatory Compliance and Safety Information for Cisco Multiservice Switch and Media Gateway Products (MGX, BPX, and SES)—This document familiarizes you with safety precautions for your product.
About This Guide Documentation Technical Manual Titles and Descriptions Table 2 lists the technical manuals and release notes that support the January 2005 multiservice switch product releases. Books and release notes in Table 2 are listed in order of use and include information about which multiservice switch or media gateway the document supports.
About This Guide Documentation Table 2 Technical Manuals and Release Notes for Cisco MGX and BPX Switches and Media Gateways (January 2005 Product Releases) (continued) Document Title and Part Number MGX BPX MGX MGX 8850 with SES 8230 Rel. 8250 Rel. (PXM1) Rel. 4 1.3 1.3 Rel. 1.3 MGX 8830 Rel. 5.1 MGX 8850 (PXM1E) Rel. 5.1 MGX 8850 (PXM45) Rel. 5.1 MGX 8950 Rel. 5.1 MGX 8880 Rel. 5.1.
About This Guide Documentation Table 2 Technical Manuals and Release Notes for Cisco MGX and BPX Switches and Media Gateways (January 2005 Product Releases) (continued) Document Title and Part Number Release Notes for Cisco MGX Route Processor Module (RPM-PR) IOS Release 12.3(7)T3 for MGX Releases 1.3.10 and 5.0.10 MGX BPX MGX MGX 8850 with SES 8230 Rel. 8250 Rel. (PXM1) Rel. 4 1.3 1.3 Rel. 1.3 MGX 8830 Rel. 5.1 MGX 8850 (PXM1E) Rel. 5.1 MGX 8850 (PXM45) Rel. 5.1 MGX 8950 Rel. 5.1 MGX 8880 Rel. 5.
About This Guide Documentation Table 2 Technical Manuals and Release Notes for Cisco MGX and BPX Switches and Media Gateways (January 2005 Product Releases) (continued) Document Title and Part Number MGX BPX MGX MGX 8850 with SES 8230 Rel. 8250 Rel. (PXM1) Rel. 4 1.3 1.3 Rel. 1.3 Cisco WAN Manager User’s Guide, x Release 15.1 MGX 8830 Rel. 5.1 MGX 8850 (PXM1E) Rel. 5.1 MGX 8850 (PXM45) Rel. 5.1 MGX 8950 Rel. 5.1 MGX 8880 Rel. 5.1.
About This Guide Documentation Table 2 Technical Manuals and Release Notes for Cisco MGX and BPX Switches and Media Gateways (January 2005 Product Releases) (continued) Document Title and Part Number MGX BPX MGX MGX 8850 with SES 8230 Rel. 8250 Rel. (PXM1) Rel. 4 1.3 1.3 Rel. 1.3 MGX 8830 Rel. 5.1 MGX 8850 (PXM1E) Rel. 5.1 MGX 8850 (PXM45) Rel. 5.1 MGX 8950 Rel. 5.1 MGX 8880 Rel. 5.1.
About This Guide Documentation Table 2 Technical Manuals and Release Notes for Cisco MGX and BPX Switches and Media Gateways (January 2005 Product Releases) (continued) Document Title and Part Number Cisco MGX 8230 Multiservice Gateway Command Reference, Release 1.1.31 MGX BPX MGX MGX 8850 with SES 8230 Rel. 8250 Rel. (PXM1) Rel. 4 1.3 1.3 Rel. 1.3 MGX 8830 Rel. 5.1 MGX 8850 (PXM1E) Rel. 5.1 MGX 8850 (PXM45) Rel. 5.1 MGX 8950 Rel. 5.1 MGX 8880 Rel. 5.1.
About This Guide Documentation Note For the January 2005 product release, there are no new features for the Service Expansion Shelf (SES) of the BPX switch and BPX WAN switching software. Therefore, documentation for these items was not updated. Table 2 lists the most recent technical manuals and release notes for these products. Table 2 also lists the latest documentation available for the Cisco MGX 8230, Cisco MGX 8250, and Cisco MGX 8850 (PXM1) switches. These switches use the PXM1 processor card.
About This Guide Documentation Table 4 Descriptions of Technical Manuals and Release Notes for Cisco Multiservice Switch Products Document Title Description Cisco ATM and Frame Relay Services (MPSM-T3E3-155 and Provides software configuration procedures for provisioning ATM and Frame Relay connections on the new MPSM-16-T1E1) Configuration Guide and Command MPSM-T3E3-155 multiprotocol service module. Also Reference for MGX Switches, Release 5.1 describes all MPSM-T3E3-155 commands.
About This Guide Documentation Table 4 Descriptions of Technical Manuals and Release Notes for Cisco Multiservice Switch Products (continued) Document Title Description Cisco MGX 8250 Edge Concentrator Overview, Release 1.1.3 Describes the system components and function of the Cisco MGX 8250 edge concentrator. DOC-7811576= Cisco MGX 8250 Multiservice Gateway Command Reference, Provides detailed information on the general command line Release 1.1.3 interface commands.
About This Guide Documentation Table 4 Descriptions of Technical Manuals and Release Notes for Cisco Multiservice Switch Products (continued) Document Title Description Cisco MGX 8850 Edge Concentrator Installation and Configuration, Release 1.1.3 Provides installation instructions for the Cisco MGX 8850 (PXM1) edge concentrator. DOC-7811223= Cisco MGX 8850 Multiservice Switch Overview, Release 1.1.3 Describes the system components and function of the Cisco MGX 8850 (PXM1) edge concentrator.
About This Guide Documentation Table 4 Descriptions of Technical Manuals and Release Notes for Cisco Multiservice Switch Products (continued) Document Title Description Cisco Voice Switch Services (VXSM) Configuration and Command Reference Guide for MGX Switches, Release 5.1 Describes the features and functions of the new Voice Switch Service Module (VXSM) in the Cisco MGX 8880 Media Gateway and in the Cisco MGX8850 (PXM45 and PXM1E) multiservice switches.
About This Guide Obtaining Documentation Table 4 Descriptions of Technical Manuals and Release Notes for Cisco Multiservice Switch Products (continued) Document Title Description Provides upgrade and compatibility information, as well as Release Notes for Cisco MGX Route Processor Module (RPM-XF) IOS Release 12.3(2)T5 for PXM45-based Switches, information about known and resolved anomalies. Release 5.0.00 OL-7059-01 Release Notes for the Cisco Voice Interworking Service Module (VISM), Release 3.3.
About This Guide Documentation Feedback Cisco Marketplace: http://www.cisco.com/go/marketplace/ Ordering Documentation You can find instructions for ordering documentation at this URL: http://www.cisco.com/univercd/cc/td/doc/es_inpck/pdi.htm You can order Cisco documentation in these ways: • Registered Cisco.com users (Cisco direct customers) can order Cisco product documentation from the Ordering tool: http://www.cisco.com/en/US/partner/ordering/ • Nonregistered Cisco.
About This Guide Obtaining Technical Assistance Reporting Security Problems in Cisco Products Cisco is committed to delivering secure products. We test our products internally before we release them, and we strive to correct all vulnerabilities quickly. If you think that you might have identified a vulnerability in a Cisco product, contact PSIRT: Tip • Emergencies — security-alert@cisco.com • Nonemergencies — psirt@cisco.
About This Guide Obtaining Technical Assistance or model name; by tree view; or for certain products, by copying and pasting show command output. Search results show an illustration of your product with the serial number label location highlighted. Locate the serial number label on your product and record the information before placing a service call. Submitting a Service Request Using the online TAC Service Request Tool is the fastest way to open S3 and S4 service requests.
About This Guide Obtaining Additional Publications and Information Obtaining Additional Publications and Information Information about Cisco products, technologies, and network solutions is available from various online and printed sources. • Cisco Marketplace provides a variety of Cisco books, reference guides, and logo merchandise. Visit Cisco Marketplace, the company store, at this URL: http://www.cisco.
About This Guide Obtaining Additional Publications and Information Cisco MGX 8800/8900 Series Software Configuration Guide xlviii Release 5.1, Part Number OL-6482-01, Rev.
C H A P T E R 1 Preparing for Configuration This document provides general configuration information and procedures for the MGX 8850 (PXM1E/PXM45), MGX 8950, and MGX 8830 switches. Use this document after you have installed your switch according to the instructions in the Cisco MGX 8800/8900 Hardware Installation Guide, Releases 2 - 5.1. Use this document in conjunction with the Cisco MGX 8800/8900 Series Command Reference, Release 5.1.
Chapter 1 Table 1-1 Preparing for Configuration Card-specific Configuration Guides Service Module Software Configuration Guide Title AUSM/B and MPSM Cisco ATM Services (AUSM/MPSM) Configuration Guide and Command cards Reference for MGX Switches, Release 5.1 AXSM cards Cisco ATM Services (AXSM) Configuration Guide and Command Reference for MGX Switches, Release 5 CESM and MPSM cards Cisco Circuit Emulation Services (CESM/MPSM) Configuration Guide and Command Reference for MGX Switches, Release 5.
Chapter 1 Preparing for Configuration Changes to this Document • Cisco MGX Release 5.1 software supports a number of single-height service modules (listed in Table 1-3) that were originally designed to operate in Cisco MGX 8850 (PXM1) switches. These service modules use the cell bus to transport traffic to other services modules or PXM uplinks and are commonly referred to as cell bus service modules (CBSMs). (The CBSMs have also been called Narrow Band Service Modules (NBSMs) in Cisco documentation.
Chapter 1 Preparing for Configuration Cisco MGX Switch Features Table 1-3 Cisco MGX 8850 (PXM1E/PXM45), Cisco MGX 8850/B, Cisco MGX 8950, Cisco MGX 8830, Cisco MGX 8830/B, and Cisco MGX 8880 Capabilities Cisco MGX Model Feature 8850 (PXM1E) 8850 (PXM45) 8850/B Total Number of Slots 2 double height slots and 28 single height slots. Slots Reserved for Processor Cards 2 double height slots.
Chapter 1 Preparing for Configuration Cisco MGX Switch Features Table 1-3 Cisco MGX 8850 (PXM1E/PXM45), Cisco MGX 8850/B, Cisco MGX 8950, Cisco MGX 8830, Cisco MGX 8830/B, and Cisco MGX 8880 Capabilities (continued) Cisco MGX Model Feature 8850 (PXM1E) 8850 (PXM45) 8850/B 8830 8830/B 8880 8950 Trunk/Port Interfaces T1/E1 AUSM-8E1/B AUSM-8T1/B CESM-8E1 CESM-8T1/B FRSM-8E1 FRSM-8E1-C FRSM-8T1 FRSM-8T1-C MPSM-8-T1E1 MPSM-16-T1E1 PXM1E-16-T1E1 VISM-PR-8E1 VISM-PR-8T1 AXSM-32-T1E1-E CESM-8E12 CESM-8T
Chapter 1 Preparing for Configuration Cisco MGX Switch Features Table 1-3 Cisco MGX 8850 (PXM1E/PXM45), Cisco MGX 8850/B, Cisco MGX 8950, Cisco MGX 8830, Cisco MGX 8830/B, and Cisco MGX 8880 Capabilities (continued) Cisco MGX Model Feature MPLS 8850 (PXM1E) 8850 (PXM45) 8850/B 8 8830 8830/B 8880 8950 — Yes Yes — — Yes Yes AUSM-8E1/B AUSM-8T1/B MPSM-8-T1E1 MPSM-16-T1E1 MPSM-T3E3-155 PXM1E All AXSM MPSM-T3E3-155 MPSM-16-T1E1 All AXSM MPSM-T3E3-155 AUSM-8E1/B AUSM-8T1/B MPSM-8-T1E1 MPSM-1
Chapter 1 Preparing for Configuration Typical Topologies Table 1-3 Cisco MGX 8850 (PXM1E/PXM45), Cisco MGX 8850/B, Cisco MGX 8950, Cisco MGX 8830, Cisco MGX 8830/B, and Cisco MGX 8880 Capabilities (continued) Cisco MGX Model Feature 8850 (PXM1E) 8850 (PXM45) 8850/B SPVCs All PXM1E All AUSM All AXSM All CESM All FRSM All MPSM All PXM1E All RPM All AUSM All AXSM All CESM All FRSM All MPSM All PXM1E All RPM All AUSM All AXSM All CESM All FRSM All MPSM All PXM1E All RPM All AUSM All AXSM All CESM All
Chapter 1 Preparing for Configuration Typical Topologies Release 5.1 of the MGX 8850 (PXM1E), MGX 8830, and Cisco 8830/B switches supports the following topologies: • Multiservice edge aggregation • DSL edge aggregation Core Switch Figure 1-1 shows the switch operating in a core switch topology.
Chapter 1 Preparing for Configuration Typical Topologies Multiservice Edge Aggregation Figure 1-2 shows an MGX switch operating in a multiservice edge aggregation topology. Figure 1-2 Multiservice Edge Aggregation Topology ATM router (Cisco or third-party) Cisco MGX 8850 (PXM1E) Core ATM network ATM edge devices (Cisco or third-party) UNI or NNI Voice ATM data Cisco MGX 8850 (PXM1) Broadband trunks 38411 Frame data The MGX 8850 (PXM1) node in Figure 1-2 is called a feeder node.
Chapter 1 Preparing for Configuration Typical Topologies Figure 1-3 Virtual Trunk Topology Private switch B A Edge switch 2 Edge switch 1 Core ATM network Private switch A A Private switch C SPVP B B Edge switch 3 Legend Physical line 46508 Virtual trunk SPVP A virtual trunk provides a private virtual network path through an independent network such as a public ATM network.
Chapter 1 Preparing for Configuration Configuration Overview DSL Aggregation Figure 1-4 shows an MGX switch operating in a Digital Subscriber Line (DSL) edge aggregation topology. Figure 1-4 DSL Edge Aggregation Topology DSL lines 38412 Core ATM network DSLAMs In the DSL edge aggregation topology, the switch is colocated with Digital Subscriber Line Access Multiplexers (DSLAMs) and communicates with one or more core switches at remote locations.
Chapter 1 Preparing for Configuration Collecting Information Collecting Information During configuration, you will need to enter general configuration data that describes the switch, enables administrator access, and enables switch participation in the network.
Chapter 1 Preparing for Configuration Collecting Information Administrator Data In most cases, more than one administrator will manage the switch. The MGX switches support multiple administrators and several different administration levels. As part of the planning process, you might identify who will manage the switch and at what level. You can learn more about managing administrators by reading the “Configuring User Access” section in Chapter 2, “Configuring General Switch Features.
Chapter 1 Preparing for Configuration Collecting Information NAME: "3" , DESCR: "1 OC-48c/STM-16c single height back card, SMF-SR, SC" PID: SMFSR-1-2488 , VID: N/A, SN: SAK03300012 NAME: "5" , DESCR: "Double-height ATM SM, 16 OC-3c/STM-1" PID: AXSM-16-155 , VID: N/A, SN: SAK03420006 NAME: "5" , DESCR: "8 OC-3c/STM-1c single height BC, MMF, MT-RJ connectors" PID: MMF-8-155-MT , VID: N/A, SN: SAK04020096 NAME: "7" , DESCR: "45 Gbps processor/fabric" PID: PXM45 , VID: P01, SN: SAG07147Y04 NAME: "7" , DESCR:
Chapter 1 Preparing for Configuration Collecting Information Administrator Access Method Beginning in Release 5, the Cisco MGX switch supports secure access for CLI management sessions. In prior releases the switch supported insecure Telnet access. The secure access feature encrypts the administrator’s user ID and password, and all session activity. As an administrator, you can now disable Telnet access to force all CLI management sessions to use the secure access method.
Chapter 1 Preparing for Configuration Guidelines for Creating an IP Address Plan • The software for each switch expects to find each card type in specific slots. • Redundant card configurations can require that redundant cards be placed in a specific relationship to each other. • Redundant line configurations can require additional hardware and require that redundant lines be be placed in a specific relationship to each other.
Chapter 1 Preparing for Configuration Guidelines for Creating a Network Clock Source Plan Using Multiple IP Addresses for Switch Access Slot 1 PXM Slot 2 PXM Boot IP address: A.A.A.A Boot IP address: A.A.A.A Disk IP address: B.B.B.B 66395 Figure 1-5 The configuration shown in Figure 1-5 provides the following results: • Direct access to the active PXM using address B.B.B.B. • Direct access to the standby PXM card using address A.A.A.A.
Chapter 1 Preparing for Configuration Guidelines for Creating a Network Clock Source Plan Note Manual clock configuration and NCDP configuration operate independently of one another. In other words, you can configure both versions of network clock sourcing on your network. However, only one version can be enabled at a time. You cannot run your manual network clock configuration on your network while NCDP is running, and vice-versa. However, both configurations are stored in the disk database.
Chapter 1 Preparing for Configuration Guidelines for Creating a Network Clock Source Plan Figure 1-6 Example Network Clock Source Topology with a Single Master Clock Source Switch 2 Switch 3 P S BITS clock sources NNI trunks with clocks P P S Switch 1 – master clock source S P S Switch 6 NNI trunks with clocks P S S P Switch 5 P = Primary clock source S = Secondary clock source 80146 Switch 4 In Figure 1-6, Switch 1 provides the master network clock source to the rest of the network a
Chapter 1 Preparing for Configuration Guidelines for Creating a Network Clock Source Plan Figure 1-7 shows an example network clock source topology that uses master clock sources on different switches.
Chapter 1 Preparing for Configuration Guidelines for Creating a Network Clock Source Plan Note In releases prior to Release 5, the revertive option applied BITS clock sources and not to clock sources from trunks. Tertiary clock sources revert to a recovered primary or secondary clock in all releases. To develop a network clock source plan, create a topology drawing and identify which switches serve as active and standby master clock sources.
Chapter 1 Preparing for Configuration Guidelines for Creating a Network Clock Source Plan enabled, a root clock source is automatically selected and distributed to all nodes in the network that have NCDP enabled. NCDP automatically selects an internal oscillator on one of the NCDP nodes to be the root clock source. Each NCDP node in the network is synchronized to this root clock reference.
Chapter 1 Preparing for Configuration Guidelines for Creating a Network Clock Source Plan • On every port with NCDP enabled, NCDP establishes a control VC to carry configuration and network topology information between the connected nodes. On non-virtual trunks, the control VC is established by default on VPI 0, VCI 34. If you change the VPI/VCI within the limits of the minimum or maximum range, then the control VC will be established on the new VPI/VCI.
Chapter 1 Preparing for Configuration Guidelines for Creating a Network Clock Source Plan Cisco MGX 8800/8900 Series Software Configuration Guide 1-24 Release 5.1, Part Number OL-6482-01, Rev.
C H A P T E R 2 2 Configuring General Switch Features This chapter describes how to set up general switch features that apply to multiple switch interfaces, beginning with a configuration quickstart procedure, which introduces the configuration tasks. The following sections provided detailed information on how to complete the configuration tasks. Before you begin this chapter, keep the following statements in mind: • The generic term “PXM” refers to both the PXM1E and the PXM45.
Chapter 2 Configuring General Switch Features Configuration Quickstart Table 2-1 Step 1 Configuration Quickstart Command Purpose sysVersionSet version Select the runtime firmware version the switch will use on the PXM card and restart the switch with that firmware. For example: reboot sysVersionSet "004.000.000.000" Note These commands must be entered at the PXM backup boot prompt. On PXM1E cards, the backup boot prompt is pxm1ebkup>. On PXM45 cards, the backup boot prompt is pxm45bkup>.
Chapter 2 Configuring General Switch Features Configuration Quickstart Table 2-1 Step 6 Configuration Quickstart (continued) Command Purpose addcontroller cnfpnni-node cnfspvcprfx Configure basic PNNI node parameters which include the PNNI controller, PNNI level, peer group ID, ATM address, node ID, and SPVC prefix. Related commands: See the “Configuring PNNI Node Parameters” section later in this chapter.
Chapter 2 Configuring General Switch Features Initializing the Switch Initializing the Switch After you assemble a new switch, as described in the Cisco MGX 8800/8900 Hardware Installation Guide, Releases 2 - 5.1, you must initialize the switch before you can configure it. Although PXM cards ship with the latest version of boot firmware on the front card, the runtime firmware cannot be loaded until both front and back cards have been installed.
Chapter 2 Configuring General Switch Features Initializing the Switch Figure 2-2 Workstation Connection to Console Port on a PXM-UI-S3/B Back Card PXM-UI-S3/B back card PXM UI-S3/B C P P2 P1 S P Serial cable L A N 1 L A N 2 E X T C L K 1 Workstation E X T C L K 2 89880 A L A R M To initialize the switch, use the following procedure. Step 1 Physically connect a terminal or workstation to the PXM-UI-S3 or PXM-UI-S3/B back card as shown in Figure 2-1 or Figure 2-2.
Chapter 2 Configuring General Switch Features Initializing the Switch Step 5 If the switch does not display any messages or a prompt, press Return. When startup is complete for an uninitialized switch, it will display the PXM backup boot prompt. PXMbkup> Step 6 Locate and write down the version number for the runtime firmware provided with your switch. You need this version number to complete the next step.
Chapter 2 Configuring General Switch Features Initializing the Switch Note If the switch has not fully started and is operating in init state (which is also called stage 1 CLI mode), an i appears in the switch prompt: unknown.7.PXM.i>. In this mode, you can only log in as user cisco, password cisco, and a limited set of commands are available for troubleshooting.
Chapter 2 Configuring General Switch Features Starting a CLI Management Session After Initialization After initialization, the PXM in the initialized slot becomes active. If a second PXM resides in the other slot, the active PXM initiates a runtime firmware load on the other slot. After the runtime firmware loads on the nonactive PXM, the card enters standby mode, ready to take control if the active card fails.
Chapter 2 Configuring General Switch Features Starting a CLI Management Session After Initialization Step 3 When the Login prompt appears, enter the login name supplied with your switch, then enter the password for that login name. For example: Login: superuser password: unknown.7.PXM.a > Note The default configured username and password sets are: user cisco, password cisco; user service, password serviceuser; and user superuser, password superuser.
Chapter 2 Configuring General Switch Features Ending a CLI Management Session Ending a CLI Management Session CLI management sessions automatically terminate after the configured idle time. The default idle time is 600 seconds (10 minutes) and can be changed with the timeout command. To manually end a CLI management session, enter the bye or exit command. Note The bye and exit commands end the CLI session. They do not terminate the terminal session.
Chapter 2 Configuring General Switch Features Entering Commands at the Switch Prompt The default switch configuration allows you to enter command abbreviations on PXM cards and most service modules. Because the help command is the only command that begins with he, you can use the abbreviated he command to display help. The following example demonstrates that the switch recognizes your partial entry of the help command because it proceeds to list commands. mgx8850a.7.PXM.
Chapter 2 Configuring General Switch Features Getting Command Help In the example above, dspc is entered at an AUSM card prompt. Because there are several possible commands that start with dspc, the switch lists all supported commands that start with those letters. AUSM cards are older cards. Newer cards such as the PXM45 produce a different display for the same scenario: M8850_LA.8.PXM.
Chapter 2 Configuring General Switch Features Getting Command Help To display a list of commands that include a common set of characters, enter a question mark and the common set of characters, as shown in the following example: M8850_LA.8.PXM.a > ? ip Available commands -----------------cnfifip cnfilmiproto cnftrapip delifip dspifip dspipconntask dspipif dspipifcache dsptrapip ipifconfig pntracevsipkt setipconndebug zip M8850_LA.8.PXM.
Chapter 2 Configuring General Switch Features Getting Command Help After you enter this command, you can display detailed command lists by entering the help command as shown in the following example: mgx8850a.7.PXM.
Chapter 2 Configuring General Switch Features Configuring User Access Displaying Command Syntax and Parameters To display the syntax of a command, enter the command without any parameters. The following example shows the syntax report provided by the switch when the cnfifip command is entered without any parameters. M8850_LA.8.PXM.
Chapter 2 Configuring General Switch Features Configuring User Access • If usernames and passwords become common knowledge during the switch installation and configuration, change the passwords. • If additional users need access to the switch, create usernames and passwords below the top levels so that these users cannot access or modify the top-level user information.
Chapter 2 Configuring General Switch Features Configuring User Access Table 2-3 User Access Levels (continued) Access Level Descriptions SUPER_GP This access level allows users to configure switch level parameters such as the node name, date, and interface IP addresses. Users at this level can also enable traces. This access level also provides access to all commands in all lower access levels: GROUP1 and ANYUSER. The default username is superuser, and the default password is superuser.
Chapter 2 Configuring General Switch Features Configuring User Access Step 5 To display the new user in a list of all users, enter the dspusers command. Tip Step 6 To determine which commands are available at a particular access level, log in to the switch as a user at that access level, then enter the help or ? command. To test the username, enter the bye command, then log in as the new user. Tip If you forget which username you used to log in, enter the whoami command.
Chapter 2 Configuring General Switch Features Configuring User Access To change the user level or password of a switch user, use the following procedure. Step 1 Log in to the switch. Use either the username for which you want to change the password, or a username with privileges at least one level higher than those of the user whose password you want to change. Step 2 Enter the following command after the switch prompt: mgx8850a.7.PXM.
Chapter 2 Configuring General Switch Features Configuring User Access Enter the username using from 1 to 12 alphanumeric characters. This completes the deletion of a user. Step 3 To verify the user has been deleted, enter the dspusers command. Resetting the User cisco Password If you lose or forget your password for switch access, you should ask a user with a higher access level to reset your password using the cnfuser command.
Chapter 2 Configuring General Switch Features Setting and Viewing the Node Name Step 3 To enable password reset, enter the cnfpswdreset on command. Step 4 To view the status of this feature, enter the dsppswdreset command. Setting and Viewing the Node Name The switch name identifies the switch you are working on, which is important when you are managing multiple switches. The current switch name appears in the CLI prompt when you are managing PXM cards and service modules.
Chapter 2 Configuring General Switch Features Configuring PNNI Node Parameters Step 4 To change the time zone, enter the following command: mgx8850a.7.PXM.a> cnftmzn Replace timezone with one of the parameter values listed in Table 2-4. If your switch is located outside the Western Hemisphere, select GMT (see Table 2-4) and use the next step to specify an offset from GMT. If your switch is located in the Western Hemisphere choose the appropriate option from Table 2-4.
Chapter 2 Configuring General Switch Features Configuring PNNI Node Parameters information for the older SPVCs as well as the new ATM address information. To keep PNNI running at maximum efficiency, set the PNNI node parameters to the proper values before creating SPVCs, or delete and recreate old SPVCs after making PNNI node parameter updates. Adding the PNNI Controller The PNNI controller simplifies switch configuration by using PNNI protocol to discover call routes in an ATM network.
Chapter 2 Configuring General Switch Features Configuring PNNI Node Parameters To display the PNNI controller configuration, enter the dspcontrollers command: mgx8850a.7.PXM.a> dspcontrollers pxm1e System Rev: 03.00 MGX8850 Number of Controllers: 1 Controller Name: Controller Id: 2 Controller Location: Internal Controller Type: PNNI Controller Logical Slot: 7 Controller Bay Number: 0 Controller Line Number: 0 Controller VPI: 0 Controller VCI: 0 Controller In Alarm: NO Controller Error: May.
Chapter 2 Configuring General Switch Features Configuring PNNI Node Parameters The switch displays a report similar to the following example: mgx8850a.7.PXM.a> dsppnni-node node index: 1 node name: mgx8850a Level............... 56 Lowest.............. true Restricted transit.. off Complex node........ off Branching restricted on Admin status........ up Operational status.. up Non-transit for PGL election.. off Node id...............56:160:47.00918100000000001a531c2a.00001a531c2a.01 ATM address...........
Chapter 2 Configuring General Switch Features Configuring PNNI Node Parameters Note Tip Step 4 The ATM address in the example above shares the same seven most-significant bytes (level 56 peer groups use the first 7 bytes) as the peer group ID example in the previous section, so PNNI can advertise only the peer group ID outside of the peer group. If the ATM address and peer group ID used different prefixes, PNNI would have to advertise the node ATM address and the peer group ID.
Chapter 2 Configuring General Switch Features Configuring PNNI Node Parameters Setting the PNNI Node ID The PNNI node ID appears in many CLI displays, including the dsppnni-node command display. The default node ID is PNNIlevel:160:defaultATMaddress. If you change the PNNI level or the node ATM address, you should also change the node ID so that the node ID represents the correct PNNI level and ATM address.
Chapter 2 Configuring General Switch Features Configuring PNNI Node Parameters Step 5 To display the PNNI node configuration, enter the command: mgx8850a.7.PXM.a> dsppnni-node The switch displays a report similar to the following example: mgx8850a.7.PXM.a> dsppnni-node node index: 1 node name: 8850_LA Level............... 56 Lowest.............. true Restricted transit.. off Complex node........ off Branching restricted on Admin status........ up Operational status.. up Non-transit for PGL election..
Chapter 2 Configuring General Switch Features Configuring PNNI Node Parameters Step 3 To change the SPVC prefix, enter the following command: mgx8850a.7.PXM.a> cnfspvcprfx -prfx Replace prefix with the 13-byte prefix you want to use. For example: mgx8850a.7.PXM.a> cnfspvcprfx -prfx 47.
Chapter 2 Configuring General Switch Features Configuring the MPLS Controller mgx8850a.7.PXM.a> dsppnni-node node index: 1 node name: 8850_LA Level............... 56 Lowest.............. true Restricted transit.. off Complex node........ off Branching restricted on Admin status........ up Operational status.. up Non-transit for PGL election.. off Node id...............56:160:47.00918100000000001a531c2a.00001a531c2a.01 ATM address...........47.00918100000000001a531c2a.00001a531c2a.01 Peer group id........
Chapter 2 Configuring General Switch Features Configuring Clock Sources Note When NCDP is enabled, your manual configuration is disabled, and vice versa. When you disable NCDP, your node reverts back to any manual clock configuration that was previously done on the node. If you re-enable NCDP after disabling it, your switch will remember your last NCDP configuration and use that unless you change it.
Chapter 2 Configuring General Switch Features Configuring Clock Sources Figure 2-4 BITS Clock Source Ports on PXM-UI-S3/B Back Card PXM UI-S3/B C P P2 P1 S P L A N 1 L A N 2 port 35 E X T C L K 1 port 36 E X T C L K 2 89881 A L A R M Note When using an external clock source and redundant PXM cards, use a Y-cable to connect that clock source to the same clock port on both PXM cards. Otherwise, the clock source is available to only one of the PXM cards.
Chapter 2 Configuring General Switch Features Configuring Clock Sources Table 2-6 Parameter Descriptions for cnfclksrc Command on the PXM Parameter Values Descriptions priority primary or secondary Replace with the type of clock source that is either primary or secondary. The default is primary. shelf 1 The value is always 1 and is optional. slot 7 For the BITS clock, the number is 7 for a MGX 8850 (PXM1E/PXM45) or MGX 8950 switch, or slot 1 for a MGX 8830 switch.
Chapter 2 Configuring General Switch Features Configuring Clock Sources Note Manual clock distribution provides a revertive function that can apply when the primary clock source fails and is subsequently restored. A failure is a loss of the primary clock source after the switch has locked on to that clock source.
Chapter 2 Configuring General Switch Features Configuring Clock Sources Table 2-7 cnfncdp Command Parameters (continued) Parameter Description -holdtime Specifies the time interval, in milliseconds, between each PDU configuration. The range is 47 through 60000 milliseconds. Default = 500 milliseconds -topoChangeTimer Time interval, in milliseconds, for which the topology change notification bit will be sent in the the configuration PDUs. The range is from 47 through 60000 milliseconds.
Chapter 2 Configuring General Switch Features Setting the LAN IP Addresses Setting the LAN IP Addresses The switch uses two types of IP addresses for Ethernet LAN access: • Boot IP addresses • Disk IP addresses The following sections describe how to set these addresses. For information on how the switch uses these addresses and how to choose the addresses, see the “Guidelines for Creating an IP Address Plan” section in Chapter 1, “Preparing for Configuration.
Chapter 2 Configuring General Switch Features Setting the LAN IP Addresses mgx8850a.7.PXM.a> bootChange '.' = clear field; '-' = go to previous field; ^D = quit boot device : lnPci processor number : 0 host name : file name : inet on ethernet (e) : 172.29.52.6 inet on backplane (b): host inet (h) : 0.0.0.0 gateway inet (g) : 172.29.52.
Chapter 2 Configuring General Switch Features Setting the LAN IP Addresses Table 2-8 bootChange Command Option Descriptions Option Description boot device The lnPci value selects an external server as the boot source when the boot or runtime software is not found on the PXM hard disk. processor number Do not change this option. host name The host name identifies an external server that has switch boot and runtime software.
Chapter 2 Configuring General Switch Features Setting the LAN IP Addresses If you used the bootChange command to enter a network mask for the first time, the new network mask should be operable and visible using the dspipif command. If you are changing the network mask, you must reset the active PXM to begin using the new network mask. For a redundant PXM configuration, use the switchcc command to switch control to the standby PXM and reset the formerly active card.
Chapter 2 Configuring General Switch Features Setting the LAN IP Addresses Figure 2-6 Hardware Required for Local LAN Connections to PXM-UI-S3/B Back Cards PXM-UI-S3/B back card Hub or router PXM UI-S3/B C P P2 P1 S P L A N 1 Ethernet cable L A N 2 E X T C L K 1 Workstation E X T C L K 2 89882 A L A R M Before you can manage the switch through the PXM LAN port, you must first assign an IP address to the LAN port.
Chapter 2 Configuring General Switch Features Setting the LAN IP Addresses In the IP Interface Configuration Table, look for an Internet address entry under the lnPci entry. If an IP address is configured, you can use that address and skip the rest of this procedure. However, if the address has not been entered or is incompatible with your network, you must configure a valid disk IP address as described in the next step. Note Step 3 If you are using CWM to manage your network, the IP address 10.0.
Chapter 2 Configuring General Switch Features Configuring for Network Management After the disk IP interface has been configured and a physical path established to the Cisco MGX switch, you can start a CLI session using a workstation with a Telnet client program. To establish a CLI management session, use the following procedure.
Chapter 2 Configuring General Switch Features Configuring for Network Management The following tasks are described in this section: • Configuring the SNMP Trap Source IP Address • Configuring the SNMP Manager Destination IP Address • Configuring the Community String and General Switch Information Configuring the SNMP Trap Source IP Address The SNMP trap source IP address is sent to SNMP managers, such as CWM, in the SNMP trap Packet Data Unit (PDU).
Chapter 2 Configuring General Switch Features Configuring for Network Management Configuring the Community String and General Switch Information To configure information about a switch in the local SNMP agent, use the following procedure. Step 1 Establish a configuration session using a user name with SUPER_GP privileges or higher. Step 2 To define the SNMP passwords for network management, enter the following command: mgx8850a.7.PXM.
Chapter 2 Configuring General Switch Features Verifying the Hardware Configuration Verifying the Hardware Configuration Before you can configure your switch, you need to collect information about the cards and software installed on the switch. The primary reason for collecting this information is to verify that the correct cards are installed in the correct slots, and that the back cards installed are indeed compatible with the front cards they serve.
Chapter 2 Configuring General Switch Features Verifying the Hardware Configuration A Cisco MGX 8850 switch displays a report similar to the following example: M8850_LA.8.PXM.a > dspcds M8850_LA System Rev: 04.00 Chassis Serial No: SAA03230375 Chassis Rev: B0 Card Slot --- Front/Back Card State ---------- Card Type -------- Alarm Status -------- May.
Chapter 2 Configuring General Switch Features Verifying the Hardware Configuration A Cisco MGX 8950 switch displays a report similar to the following example: M8950_DC.8.PXM.a > dspcds M8950_DC System Rev: 04.00 Chassis Serial No: SCA0504043H Chassis Rev: A0 Card Slot --- Front/Back Card State ---------- Card Type -------- Alarm Status -------- May.
Chapter 2 Configuring General Switch Features Verifying the Hardware Configuration The dspcd command displays information that is unique to a particular card. For PXM1E cards, the switch displays a report similar to the following example: mgx8830b.1.PXM.a> dspcd 2 mgx8830b System Rev: 03.00 MGX8830 Slot Number 2 Redundant Slot: 1 Front Card ---------Inserted Card: PXM1E-4-155 Reserved Card: PXM1E-4-155 State: Standby Serial Number: S1234567890 Prim SW Rev: 3.0(0.39)A Sec SW Rev: 3.0(0.39)A Cur SW Rev: 3.
Chapter 2 Configuring General Switch Features Verifying the Hardware Configuration For service modules, the switch displays a report similar to the report displayed on the PXM cards. The following example shows the dspcd report for a CESM-8T1 card: mgx8830b.1.PXM.a> dspcd 6 mgx8830b System Rev: 03.00 MGX8830 Slot Number: 6 Redundant Slot: NONE Front Card ---------CESM_8T1 UnReserved Active A79907 20.0(0.106)D 20.0(0.106)D 20.0(0.106)D 1.0(2.
Chapter 2 Configuring General Switch Features Verifying the Hardware Configuration mgx8830 MGX8830 Crossbar Slot Status: System Rev: 03.00 Apr. 25, 2002 23:10:08 GMT Node Alarm: MAJOR No Crossbar Alarm Causes -----------NO ALARMS Note b. You can not run the dspcd command on the SRM itself, because all SRM card configuration is done from the PXM card. Enter dspcd at the PXM to display information about the SRM cards in your switch.
C H A P T E R 3 Provisioning PXM1E Communication Links This chapter describes how to prepare PXM1E lines for physical connectivity to other switches. It describes how to add ports and connections that support ATM communications over the PXM1E lines to other devices. This chapter provides a quickstart procedure for configuring PXM1E cards and lines and describes how to provision the link and connection types listed in Table 3-1.
Chapter 3 Provisioning PXM1E Communication Links Quickstart Provisioning Procedures Table 3-1 PXM1E Link and Connection Types (continued) PXM1E Link or Connection Type Description IISP4 links IISP links enable connectivity between two independent PNNI networks and block the PNNI database exchange so the two networks remain independent. IISP is the predecessor to AINI and should be used only when AINI is not supported on one or both ends of the link.
Chapter 3 Provisioning PXM1E Communication Links Quickstart Provisioning Procedures Step 1 Step 1 Command Purpose username Start a configuration session. Note cnfcdmode Configure the operational mode of all lines on PXM1E cards that support T1, E1, T3 or E3 lines. This step selects either T1 or E1, or either T3 or E3, depending on the card type. Note Step 2 upln
Chapter 3 Provisioning PXM1E Communication Links Quickstart Provisioning Procedures Step 3 Command Purpose addport Add and configure ATM ports. This step establishes ATM layer two communications between two ATM devices. or addimagrp Note addimalnk addimaport The PNNI or MPLS controller must be added before adding ports for ATM trunks. Procedures for adding controllers can be found in Chapter 2, “Configuring General Switch Features.
Chapter 3 Provisioning PXM1E Communication Links Quickstart Provisioning Procedures Step 7 Command Purpose dsppnni-link When both ends of the link are configured, verify the PNNI communications between the two ends. In the dsppnni-link report, there should be an entry for the port for which you are verifying communications. The Hello state reported should be twoWayInside, and the Remote node ID should display the remote node ATM address after the second colon.
Chapter 3 Provisioning PXM1E Communication Links Quickstart Provisioning Procedures Step 3 Command Purpose addport Add and configure ATM ports. This step establishes ATM layer two communications between two ATM devices. or addimagrp Note addimalnk addimaport The PNNI or MPLS controller must be added before adding UNI ports. Procedures for adding controllers can be found in Chapter 2, “Configuring General Switch Features.
Chapter 3 Provisioning PXM1E Communication Links Quickstart Provisioning Procedures Command Purpose Step 9 uppnport Bring up the port after configuration is complete. Step 10 upilmi Configure and start ILMI on the port. This step is required for dynamic addressing and the ILMI automatic configuration feature. Otherwise, it is optional. cnfilmi See the “Configuring ILMI on a Port” section later in this chapter.
Chapter 3 Provisioning PXM1E Communication Links Quickstart Provisioning Procedures It is beyond the scope of this guide to describe how to configure each model of the CPE to communicate with the switch. To complete this configuration, you will need to learn the capabilities of the CPE and the switch and define a set of communications parameters that are supported by both devices. For example, the Cisco MGX switches support UNI 3.
Chapter 3 Provisioning PXM1E Communication Links Quickstart Provisioning Procedures Step 5 Command Purpose addcon Configure the slave side of the connection. See “Configuring the Slave Side of SPVCs and SPVPs,” which appears later in this chapter. Related commands: dspcons dspcon Step 6 addcon Configure the master side of the connection. See “Configuring the Master Side of SPVCs and SPVPs,” which appears later in this chapter.
Chapter 3 Provisioning PXM1E Communication Links Quickstart Provisioning Procedures Figure 3-1 shows an example of configuration data that you can use when following the quickstart procedure below. Note that the single trunk between Private Switch A and Edge Switch 1 hosts two virtual trunks, which terminate at Virtual Network-to-Network Interface (VNNI) ports 10:1.2:2 and 10:1.2:7. The switch supports up to 32 VNNI ports on the node.
Chapter 3 Provisioning PXM1E Communication Links Quickstart Provisioning Procedures Step 4 Command Purpose addpart Configure the virtual trunk partitions at the private switches. Related commands: For a VNNI port, enter the same VPI number for the minVpi and maxVpi parameters. This number becomes the VPI number for the virtual trunk. dspparts dsppart cnfpart For an EVNNI port, enter the same minimum and maximum VPI numbers you entered when creating the port.
Chapter 3 Provisioning PXM1E Communication Links Quickstart Provisioning Procedures Step 8 Command Purpose dnpnport Configure the virtual trunk signaling at each core edge node. Select no trunk signaling by setting the -univer option to none. cnfpnportsig uppnport See the “Selecting the Port Signaling Protocol” section later in this chapter.
Chapter 3 Provisioning PXM1E Communication Links Quickstart Provisioning Procedures Step 3 Command Purpose addport Add and configure ATM ports. This step establishes ATM communications between two ATM devices. Related commands: dspports Step 4 addpart Related commands: Specify NNI for interswitch trunks. See the “Adding ATM Ports”section later in this chapter. Add and configure a PNNI partition for the trunk. This step reserves trunk resources for the PNNI controller.
Chapter 3 Provisioning PXM1E Communication Links Quickstart Provisioning Procedures AINI Link Configuration Quickstart The quickstart procedure in this section provides a summary of the tasks required to configure ATM Inter-Network Interface (AINI) links on Cisco MGX switches. This procedure is provided as an overview and as a quick reference for those who have previously configured these types of connections. Step 1 Command Purpose username Start a configuration session.
Chapter 3 Provisioning PXM1E Communication Links Quickstart Provisioning Procedures Step 6 Command Purpose cnfpnportsig At one end of the AINI trunk, VPI and VCI allocation must be disabled. VPI and VCI allocation is enabled by default on a PXM1E trunks. To disable this feature, enter the command: 8850_LA.7.PXM.a > cnfpnportsig 1:1.1:1 -vpivcialloc disable Step 7 uppnport When signaling configuration is complete, bring up the port.
Chapter 3 Provisioning PXM1E Communication Links Quickstart Provisioning Procedures Step 3 Command Purpose addport Add a port to the IISP trunk. This step establishes ATM communications between two ATM devices. or addimagrp addimalnk addimaport Related commands: dspports Specify NNI for interswitch trunks. For standard port configuration, see the “Adding ATM Ports” section later in this chapter.
Chapter 3 Provisioning PXM1E Communication Links Quickstart Provisioning Procedures XLMI Link Configuration Quickstart An Extended Link Management Interface (XLMI) link joins a PNNI network with an AutoRoute network. After you establish an XLMI link, you can configure connections that link CPE in the PNNI network with CPE in the AutoRoute network.
Chapter 3 Provisioning PXM1E Communication Links Quickstart Provisioning Procedures Step 3 Command Purpose addport Add and configure ATM ports. This step establishes ATM communications between two ATM devices. or addimagrp addimalnk addimaport Related commands: dspports The PXM1E cards supports XLMI on UNI or NNI ports. For standard port configuration, see the “Adding ATM Ports” section later in this chapter.
Chapter 3 Provisioning PXM1E Communication Links Quickstart Provisioning Procedures Step 8 Command Purpose uppnport Bring up the configured port. Related commands: dsppnports dsppnport Step 9 Step 10 If you are using CWM to manage your networks, the XLMI link should be ready to use. Use CWM to add a connection from a destination in the AutoRoute network to a destination in the PNNI network.
Chapter 3 Provisioning PXM1E Communication Links Quickstart Provisioning Procedures Step 1 Command Purpose username Start a configuration session with the active PXM1E card on a MGX 8850 (PXM1E) or MGX 8830 switch. Note Step 2 Step 3 To perform all the steps in this quickstart procedure, you must log in as a user with SUPER_GP privileges or higher. Bring up a PXM1E line that is connected to a UXM card on a Cisco IGX 8400.
Chapter 3 Provisioning PXM1E Communication Links General PXM1E Configuration Procedures General PXM1E Configuration Procedures This section describes the following general procedures for configuring PXM1E card communications: • Configuring the Card Mode • Setting Up Lines • Configuring Inverse Multiplexing for ATM • Establishing Redundancy Between Two Lines with APS • Adding ATM Ports • Partitioning Port Resources Between Controllers • Selecting the Port Signaling Protocol • Defining Destin
Chapter 3 Provisioning PXM1E Communication Links General PXM1E Configuration Procedures Setting Up Lines The first step in configuring PXM1E lines is to define the physical lines that are connected to the switch. The following sections describe how to do the following tasks: • Bring up lines • Configure lines • Verify the configuration of lines Bringing Up Lines Installing an PXM1E card can add from 1 to 16 lines to your switch.
Chapter 3 Provisioning PXM1E Communication Links General PXM1E Configuration Procedures Tip Step 4 If the upln command fails for a line that requires a field replaceable unit (FRU) transceiver, enter the dsplns command and verify that the Line Type column for the specified line has an entry that indicates what type of FRU transceiver is installed. If no transceiver is installed, the line cannot be brought up. To verify that a line has been brought up, enter the following command: mgx8830b.2.PXM.
Chapter 3 Provisioning PXM1E Communication Links General PXM1E Configuration Procedures Table 3-2 Parameters for cnfln Command (continued) Parameter Line Types Supported Description clockSource T1 E1 T3 E3 SONET The -clk option selects the source timing for transmitting messages over the line. Replace with 1 to use the clock signal received over this line from a remote node, or specify 2 to use the local timing defined for the local switch.
Chapter 3 Provisioning PXM1E Communication Links General PXM1E Configuration Procedures mgx8830b.2.PXM.a > cnfln -ds1 -len -clk Table 3-2 describes the all parameters for configuring lines. Be sure to use only the parameters listed for T1 lines. Step 5 To verify your configuration changes, enter the dspln command. Configuring E1 Lines At the physical level, you can configure the line clock source for E1 lines.
Chapter 3 Provisioning PXM1E Communication Links General PXM1E Configuration Procedures mgx8830b.2.PXM.a > dsplns Remember that you cannot configure a line until you have brought it up as described in the previous section, “Bringing Up Lines.” Step 3 To display the configuration for a line, enter the dspln command. For example: mgx8830b.2.PXM.
Chapter 3 Provisioning PXM1E Communication Links General PXM1E Configuration Procedures Line Coding Line Length(meters) OOFCriteria AIS c-Bits Check Loopback Xmt. Clock source Rcv FEAC Validation : : : : : : : ds3B3ZS Number 0 Number 3Of8Bits Number Check Number NoLoop localTiming 4 out of 5 FEAC codes of of of of partitions: SPVC : SPVP : SVC : 0 0 0 0 For more information, see the “Verifying Line Configuration” section later in this chapter.
Chapter 3 Provisioning PXM1E Communication Links General PXM1E Configuration Procedures Step 3 To display the configuration of a single line, enter the following command: mgx8830b.2.PXM.a > dspln -type Table 3-3 describes the dspln command parameters. The line configuration appears as follows: mgx8830b.2.PXM.
Chapter 3 Provisioning PXM1E Communication Links General PXM1E Configuration Procedures Each combination of multiple links is called an IMA group. IMA groups are comprised of IMA links. Note During PXM1E-16-T1E1 switchovers, traffic loss on an IMA group can be around 3 seconds, and connections on the IMA group may be re-routed. Configuring IMA ports on PXM1E cards is a three-step process. 1. Create and configure an IMA group 2. Add IMA links to the IMA group 3.
Chapter 3 Provisioning PXM1E Communication Links General PXM1E Configuration Procedures Table 3-4 addimagrp Command Parameters group Enter an IMA group number using the format bay.line. On a PXM1E, the bay number is always 2 and the range for lines is 1-16. version IMA version. Enter one of the following values: • Version 1.0 = 1 • Version 1.1 = 2 minLinks Minimum number of links required for group operation.
Chapter 3 Provisioning PXM1E Communication Links General PXM1E Configuration Procedures Len Len Mode (ms) -------------------------------------------------------------------------------2.1 1 128 128 CTC 100 StartUp StartUp 1.0 2.2 3 128 128 CTC 100 StartUp StartUp 1.1 2.3 3 128 128 CTC 100 StartUp StartUp 1.1 Configuring an IMA Group Once you have added an IMA group on your PXM1E, you can configure that IMA group’s parameters. Use the following procedure to configure IMA group parameters.
Chapter 3 Provisioning PXM1E Communication Links General PXM1E Configuration Procedures Group Running Secs Alpha Val Beta Val Gamma Val Tx OAM Label Rx OAM Label Test Pattern Procedure Status Test Link Test Pattern Stuff Cell Indication (frames) Version Fallback Enabled Auto-Restart Mode Rx IMA ID Expected Auto-Restart Sync State Step 4 : : : : : : : : : : : : : : 3999077 2 2 1 1 1 Disabled Unknown 255 1 true disable -1 disable To configure an IMA group, enter the cnfimagrp command, as shown in the f
Chapter 3 Provisioning PXM1E Communication Links General PXM1E Configuration Procedures Table 3-5 cnfimagrp Command Parameters (continued) -vfb -mode Version fallback enable. The available options are: • True = 1 • False = 2 The -mode parameter is optional and configures the IMA autorestart feature.
Chapter 3 Provisioning PXM1E Communication Links General PXM1E Configuration Procedures Diff Delay Max (msecs) Diff Delay Max Observed (msecs) Accumulated Delay (msecs) Clear Accumulated Delay Status GTSM Up Integ Time (msecs) : : : : : Type to continue, Q to stop: GTSM Dn Integ Time (msecs) : Num Tx Cfg Links : Num Rx Cfg Links : Num Act Tx Links : Num Act Rx Links : Least Delay Link : Tx Timing Ref Link : Rx Timing Ref Link : Group Running Secs : Alpha Val : Beta Val : Gamma Val : Tx OAM Lab
Chapter 3 Provisioning PXM1E Communication Links General PXM1E Configuration Procedures Step 3 To verify that the link has been added, enter the dspimalnks command. Configuring IMA Links Once you have added an IMA link, you can configure that link. Use the following procedure to configure an IMA link. Step 1 To display a list of IMA links that can be configured, enter the dspimalnks command as follows: M8830_CH.1.PXM.
Chapter 3 Provisioning PXM1E Communication Links General PXM1E Configuration Procedures Table 3-6 cnfimalnk Command Parameters (continued) -dnlif LIF integration down time. Range 0-25000 milliseconds. -uplods Link Out of Delay Synchronization (LODS) integration up time. The LODS is a link event indicating that the link is not synchronized with the other links within the IMA group. Range 0-25000 milliseconds. -dnlods LODS integration down time.
Chapter 3 Provisioning PXM1E Communication Links General PXM1E Configuration Procedures Table 3-7 Parameters for addimaport Command Parameter Description ifNum Specify a port number for the new IMA port. The port number must be available (not already configured) and in the range of 1 to 31. To view the configured port numbers, use the dspports command. group Enter the group number of an existing IMA group. To display a list of IMA groups, enter the dspimagrps command.
Chapter 3 Provisioning PXM1E Communication Links General PXM1E Configuration Procedures Table 3-7 Parameter Description vpi Virtual path identifier for a virtual port of VUNI or VNNI type. The ranges are as follows: minvpi maxvpi Step 5 Parameters for addimaport Command (continued) • VNNI Range: 1-4095 • VUNI Range: 1-255 Minimum virtual path identifier for a virtual port of EVUNI or EVNNI type.
Chapter 3 Provisioning PXM1E Communication Links General PXM1E Configuration Procedures Establishing Redundancy Between Two Lines with APS Cisco MGX switches use Automatic Protection Switching (APS) to provide line fault tolerance. APS is a component of SONET and is therefore available only on optical interfaces and STM-1 interfaces (which are the electrical equivalent of SONET OC-3). The Cisco MGX 8800/8900 Hardware Installation Guide, Releases 2 - 5.
Chapter 3 Provisioning PXM1E Communication Links General PXM1E Configuration Procedures • The working line must be assigned to a lower numbered port than the protection line. For example, the working line could be on port 3 and the protection line on port 4. If the protection line is on port 2, do not assign the working line to port 3. • The switches at both ends of the APS lines must be configured for APS, and the role of each line (working or protection) must be the same at both ends of the line.
Chapter 3 Provisioning PXM1E Communication Links General PXM1E Configuration Procedures Step 4 To display a list of all APS lines on a PXM1E, enter the dspapslns command on the active PXM1E card. Step 5 To display information on a specific APS line, enter the dspapsln command on the active PXM1E card. For information on managing APS lines, see the “Managing Redundant APS Lines” section in Chapter 9, “Switch Operating Procedures.
Chapter 3 Provisioning PXM1E Communication Links General PXM1E Configuration Procedures • The working line must be defined on the primary card, and the protection line must be defined on the secondary card. The primary and secondary cards are predefined for PXM1E. In an MGX 8830 switch, slot 1 hosts the primary card and slot 2 hosts the secondary card. In an MGX 8850 (PXM1E) switch, slot 7 hosts the primary card and slot 8 hosts the secondary card.
Chapter 3 Provisioning PXM1E Communication Links General PXM1E Configuration Procedures Step 7 To display information on a specific APS line, enter the dspapsln command on the active PXM1E card. For information on managing APS lines, see the “Managing Redundant APS Lines” section in Chapter 9, “Switch Operating Procedures.” Adding ATM Ports The previous chapter described how to bring up physical lines by specifying the correct line port number.
Chapter 3 Provisioning PXM1E Communication Links General PXM1E Configuration Procedures Step 4 To add an ATM port to a line, enter the following command: mgx8830a.1.PXM.a > addport [vpi ] [-minvpi ] [-maxvpi ] Table 3-9 lists the parameter descriptions for adding ports. Figure 3-4 shows the relationship between logical interface numbers and physical lines.
Chapter 3 Provisioning PXM1E Communication Links General PXM1E Configuration Procedures Table 3-9 Parameters for addport and cnfport Commands (continued) Parameter Description ifType Enter a number that indicates the interface type as follows: 1—UNI, one UNI port allowed per physical line 2—NNI, one NNI port allowed per physical line 3—VNNI, multiple virtual NNI ports supported over one VPI 4—VUNI, multiple virtual UNI ports supported over one VPI 5—EVUNI, multiple enhanced virtual UNI ports supporte
Chapter 3 Provisioning PXM1E Communication Links General PXM1E Configuration Procedures Step 5 To display a list of the ports configured on the PXM1E card, enter the following command: mgx8830a.1.PXM.a > dspports This command displays all configured ports on the PXM1E card. Port numbers are listed in the ifNum (interface number) column. If you want to view information on a particular port, note the number of that port. Step 6 To display the port configuration, enter the following command: mgx8830a.1.
Chapter 3 Provisioning PXM1E Communication Links General PXM1E Configuration Procedures Step 3 To prepare for the configuration change, enter the dnport command to bring down the port as shown in the following example: M8830_CH.2.PXM.a > dnport 1 Traffic loss will result on all connections on this port. Do you want to proceed (Yes/No) ? y Step 4 To change an ATM port configuration, enter the following command: mgx8830a.1.PXM.
Chapter 3 Provisioning PXM1E Communication Links General PXM1E Configuration Procedures Figure 3-5 Relationship of Port Controller, Controller Partition, and Resource Partitions PXM1E card Port controller ID Resource partition port (interface number and partition ID) Controller partition ID Resource partitions for additional ports 89883 Resource partition port (interface number and partition ID) Figure 3-5 shows that the single controller partition connects to the port controller and to the reso
Chapter 3 Provisioning PXM1E Communication Links General PXM1E Configuration Procedures Table 3-10 Parameters for the addpart Command Parameter Description ifNum Interface number or port number. This number identifies the port this resource partition configures. Enter the interface number that was assigned to the port when it was configured (see the “Adding ATM Ports” section earlier in this chapter). partId Partition identification number. Enter a number in the range of 1 to 20.
Chapter 3 Provisioning PXM1E Communication Links General PXM1E Configuration Procedures Table 3-10 Parameters for the addpart Command (continued) Parameter Description minConns Specifies the guaranteed number of connections. On the PXM1E UNI/NNI, the ranges vary according to the line types, as follows: maxConns Step 4 • For OC3, T3, and E3 lines, the range is 10-27000. • For T1 and E1 lines, the range is 10-13500. Specifies the guaranteed number of connections.
Chapter 3 Provisioning PXM1E Communication Links General PXM1E Configuration Procedures Selecting the Port Signaling Protocol The default signaling protocol for all new ports is UNI Version none. If you plan to use this protocol on a line, you can accept this default and skip this section. However, if you plan to use a different protocol on the line, such as NNI or PNNI, you must select the correct protocol using the following procedure.
Chapter 3 Provisioning PXM1E Communication Links General PXM1E Configuration Procedures DSPPNPORTS EndPoint Grand Total = Per-port status summary PortId Step 5 LogicalId 3/54000 IF status Admin status ILMI state #Conns 1.35 16845603 up up NotApplicable 0 1.36 16845604 up up NotApplicable 0 1.37 16845605 up up NotApplicable 0 1.38 16845606 up up NotApplicable 0 4.1 16851713 up up NotApplicable 1 1:2.1:3 16845571 up up NotApplicable 0 1:2.
Chapter 3 Provisioning PXM1E Communication Links General PXM1E Configuration Procedures Table 3-12 Port Signaling Configuration Parameters Parameter Description Port identifier in the format slot:bay.line:ifnum. These parameters are described in Table 3-11. -univer When configuring PNNI signaling for a UNI port, you can use this option to specify which version of UNI signaling you want the port to use. You can select UNI version 3.0 (uni30), UNI version 3.1 (uni31), UNI version 4.
Chapter 3 Provisioning PXM1E Communication Links General PXM1E Configuration Procedures Table 3-12 Port Signaling Configuration Parameters (continued) Parameter Description -passalongcap Pass-along capability: type enable or disable. With this capability, the port has the ability to pass along unrecognized information elements (IEs) or messages. Enabling or disabling the pass-along capability applies to AINI, IISP, and public UNI.
Chapter 3 Provisioning PXM1E Communication Links General PXM1E Configuration Procedures Step 9 To display the configuration of the PNNI port, enter the following command: mgx8830a.1.PXM.a > dsppnport Replace using the format slot:bay.line:ifNum. Table 3-11 describes these parameters. The following example shows the report for this command. mgx8830a.1.PXM.a > dsppnport 1.
Chapter 3 Provisioning PXM1E Communication Links General PXM1E Configuration Procedures Note The addaddr command is used to define destination addresses for static links and to specify static addresses for links to CPE. The command format above shows the options as they apply when defining destination addresses for static links. Table 3-13 describes the parameters used with the addaddr command.
Chapter 3 Provisioning PXM1E Communication Links General PXM1E Configuration Procedures Replace with the port address using the format slot:bay.line:ifnum. These parameters are described in Table 3-11. For example: mgx8830a.1.PXM.a > dspaddr 2:1.2:2 47.0091.8100.0000.0003.6b5e.30cd.0003.6b5e.30cd.
Chapter 3 Provisioning PXM1E Communication Links General PXM1E Configuration Procedures Table 3-14 ATM Address Configuration Parameters Parameter Description portid Port identifier in the format slot:bay.line:ifnum. These parameters are described in Table 3-11. atm-address Enter the ATM address using up to 40 nibbles. The ATM address can include up to 20 bytes, which is 40 nibbles or 160 bits. length Enter the length, in bits, of the address you specified with the parameter.
Chapter 3 Provisioning PXM1E Communication Links General PXM1E Configuration Procedures Step 5 To verify that the new address has been assigned, enter the dspatmaddr command as shown in the following example: mgx8830a.1.PXM.a > dspatmaddr 2:2.2:1 Port Id: 2:2.2:1 Configured Port Address(es) : 47.1111.1111.1111.1111.1111.1111.1111.1111.1111.11 length: 160 type: internal proto: local scope: 0 plan: nsap_icd redistribute: false Configuring ILMI on a Port ILMI is optional on most ports.
Chapter 3 Provisioning PXM1E Communication Links General PXM1E Configuration Procedures Step 1 Establish a configuration session using a user name with GROUP1 privileges or higher. Step 2 If you want to preview the current ILMI configuration for a port, enter the dspilmis command. The following example shows the dspilmis command report: mgx8830a.1.PXM.a > dspilmis Sig.
Chapter 3 Provisioning PXM1E Communication Links General PXM1E Configuration Procedures Table 3-15 cnfilmi Command Configuration Parameters (continued) Parameter Description vci ILMI signaling VCI. If you need to change the default, enter a VCI number in the range of 0 to 65535. Note that changing this value disables ILMI communications until the device at the remote end of the line has been configured for the same ILMI VCI. Default = 16. ilmiTrapEnable ILMI trap distribution.
Chapter 3 Provisioning PXM1E Communication Links General PXM1E Configuration Procedures Step 1 Establish a configuration session using a user name with GROUP1 privileges or higher. Step 2 To display the automatic configuration status of a port, use the dsppnport command. For example: mgx8830a.1.PXM.a > dsppnport 1:2.3:1 Port: 1:2.
Chapter 3 Provisioning PXM1E Communication Links General PXM1E Configuration Procedures The default ILMI prefix matches the PNNI node prefix and the SPVC prefix, both of which are described in the Cisco PNNI Network Planning Guide for MGX and SES Products. If you change the PNNI node prefix, the SPVC prefix and the ILMI prefix remain unchanged. If you change the SPVC prefix, the ILMI prefix will change with it, as long as no ILMI prefix is assigned directly to the port.
Chapter 3 Provisioning PXM1E Communication Links General PXM1E Configuration Procedures Step 5 To enable or disable dynamic address registration, enter the following command: mgx8830a.1.PXM.a > cnfaddrreg Enter yes to enable dynamic address configuration or enter no to disable it. The default is yes. Step 6 Enter the following command to define an ATM prefix for a port: mgx8830a.1.PXM.a > addprfx Replace portid using the format slot:bay.line:ifNum.
Chapter 3 Provisioning PXM1E Communication Links General PXM1E Configuration Procedures Note Step 3 Partition ID 1 is reserved for PNNI. To start ILMI on a port, enter the upilmi command as follows: mgx8830a.1.PXM.a > upilmi Replace ifNum with the interface number for the port, and replace partId with the partition number assigned to the port. For example: mgx8830a.1.PXM.a > upilmi 2 1 Step 4 To display the ILMI status of all the ports on an PXM1E card, enter the dspilmis command.
Chapter 3 Provisioning PXM1E Communication Links General PXM1E Configuration Procedures Tip To get the correct slot:bay.line:ifnum specification, use the port ID displayed by the dsppnports command. Table 3-16 Parameter Descriptions for cnfclksrc Command when Used for PXM1E Parameter Values Descriptions priority primary or secondary Replace priority with the type of clock source, which is either primary or secondary. The default is primary.
Chapter 3 Provisioning PXM1E Communication Links General PXM1E Configuration Procedures Verifying PNNI Trunk Communications After you configure both ends of a PNNI trunk, it should be ready to support SVCs and any SPVCs or SPVPs that are configured. To verify that the trunk is functioning, use the following procedure. Step 1 Establish a CLI session using a user name at any access level.
Chapter 3 Provisioning PXM1E Communication Links General PXM1E Configuration Procedures Verifying End-to-End PNNI Communications When connections between two nodes travel over multiple trunks, use the following steps to verify that the PNNI communications path is operational. Step 1 Establish a CLI session using a user name at any access level. When both ends of the communications path are connected to MGX 8850 (PXM1E/PXM45) switches, you can start the CLI session at either end.
Chapter 3 Provisioning PXM1E Communication Links General PXM1E Configuration Procedures Tip If you cannot verify communications with a remote node, try verifying communications across each of the links between the nodes as described in the previous section, “Verifying PNNI Trunk Communications.
Chapter 3 Provisioning PXM1E Communication Links General PXM1E Configuration Procedures Single-ended SPVCs are non-persistent. Double-ended SPVCs and SPVPs require separate configuration of the master and slave endpoints. The slave endpoint must be configured first because this step generates a slave address that must be entered during master endpoint configuration. The following sections describe how to configure slave and master SPVC and SPVP connections.
Chapter 3 Provisioning PXM1E Communication Links General PXM1E Configuration Procedures Table 3-17 Parameters for the addcon and cnfcon Commands (continued) Parameter Commands Description vci addcon, cnfcon Enter the VCI for the slave side of the SPVC or SPVP. SPVC Range: 32 to 65535. SPVP Range: 0. Note serviceType addcon Cisco recommends setting the minimum VCI to 35 or higher. Future products will use VCI 32 through 34 for other services.
Chapter 3 Provisioning PXM1E Communication Links General PXM1E Configuration Procedures Table 3-17 Parameters for the addcon and cnfcon Commands (continued) Parameter Commands Description -lpcr addcon, cnfcon Local peak cell rate (PCR). Specifies the PCR from a local endpoint to a remote endpoint. PCR is the maximum cell rate for the connection at any time.
Chapter 3 Provisioning PXM1E Communication Links General PXM1E Configuration Procedures Table 3-17 Parameters for the addcon and cnfcon Commands (continued) Parameter Commands Description -lmbs addcon, cnfcon Specifies the MBS from a local endpoint to a remote endpoint, in the range from 1-5000000 cells. MBS is the maximum number of cells that can burst at the PCR and still be compliant.
Chapter 3 Provisioning PXM1E Communication Links General PXM1E Configuration Procedures Table 3-17 Parameters for the addcon and cnfcon Commands (continued) Parameter Commands Description -rmcr addcon, cnfcon Remote minimum cell rate. OC3: 50 – 353207 cps T3: 50 – 96000 (PLCP) cps or 104268 (ADM) cps E3: 50 – 80000 cps T1: 50-3622 cps E1: 50-4528 cps -cdvt addcon, cnfcon Local cell delay variation tolerance (CDVT).
Chapter 3 Provisioning PXM1E Communication Links General PXM1E Configuration Procedures Table 3-17 Parameters for the addcon and cnfcon Commands (continued) Parameter Commands Description -lputil addcon, cnfcon The local percentage utilization option specifies a percentage utilization factor (which is also called an overbooking factor) that enables or disables overbooking for a connection. This is a Cisco proprietary feature that was introduced in Release 3.
Chapter 3 Provisioning PXM1E Communication Links General PXM1E Configuration Procedures Table 3-17 Parameters for the addcon and cnfcon Commands (continued) Parameter Commands Description -prefrte addcon, cnfcon This option selects a preferred route ID for the connection. To disassociate a connection from a route, select preferred route ID=0. Note An SPVC can be associated with one preferred route. For an XPVC, you can associate the preferred route with only the SPVC portion of the XPVC.
Chapter 3 Provisioning PXM1E Communication Links General PXM1E Configuration Procedures The following command example defines a port as the slave side of an SPVC. Note the slave id shown in the command response. PXM1E_SJ.8.PXM.a > addcon 11 125 125 1 2 slave endpoint added successfully slave endpoint id : 4700918100000000001A533377000001073B0B00.125.125 Step 3 Write down the slave ID (which includes the NSAP address, VPI, and VCI) the switch displays when the addcon command is complete.
Chapter 3 Provisioning PXM1E Communication Links General PXM1E Configuration Procedures Configuring the Master Side of SPVCs and SPVPs To configure the master side of an SPVC, use the following procedure. Step 1 Establish a configuration session using a user name with GROUP1 privileges or higher. Tip Step 2 During this procedure, you will have to enter the ATM address for the slave end of the connection.
Chapter 3 Provisioning PXM1E Communication Links General PXM1E Configuration Procedures The switch displays a report showing all connections as shown in the following example: PXM1E_SJ.8.PXM.a > dspcons Local Port Vpi.Vci Remote Port Vpi.Vci State Owner Pri Persistency ----------------------+------------------------+---------+-------+---+----------4.1 4 35 Routed 26 35 OK MASTER 8 Persistent Local Addr: 47.00918100000000001a533377.000001072301.00 Remote Addr: 47.009181000000000164444b61.00000107d301.
Chapter 3 Provisioning PXM1E Communication Links General PXM1E Configuration Procedures ---------- Traffic Values: Configured Tx PCR: 50 Tx CDVT: 250000 Tx CDV: -1 Tx CTD: -1 Parameters ---------(Signalled) (50 ) Rx PCR: (250000 ) (-1 ) Rx CDV: (-1 ) Rx CTD: 50 (50 ) -1 -1 (-1 (-1 ) ) -------------------- Preferred Route Parameters-----------------Currently on preferred route: N/A -------------------- Others ------------------------------------SM: Record Number: 2, ATM -------------------- Soft R
Chapter 3 Provisioning PXM1E Communication Links General PXM1E Configuration Procedures • For a P2MP connection, the root can be on any port that supports slot multicasting. The port that is the root of the connection does not need to support port multicasting. A port on which multiple parties are assigned must support port multicasting. For example, if you add a second party on a port that does not support port multicasting, the connection will not route.
Chapter 3 Provisioning PXM1E Communication Links General PXM1E Configuration Procedures The addparty command parameters are described in Table 3-18. Table 3-18 addparty Command Parameters Parameter Description port Root endpoint port identifier, in the format [shelf.]slot[:subslot].port[:subport]. To display a list of the available ports using port numbers in the correct format, enter the dsppnports command. vpi Root endpoint VPI. Enter the VPI specified when the root endpoint was created.
Chapter 3 Provisioning PXM1E Communication Links General PXM1E Configuration Procedures To display all configured parties for a specific connection, enter the dsppartiespercon command. Replace with the Port identifier whose parties you want to view, in the format. Replace with the appropriate VPI of the connection, and with the appropriate VCI of the connection. pswpop6.1.PXM.a > dsppartiespercon 5.
Chapter 3 Provisioning PXM1E Communication Links General PXM1E Configuration Procedures Displaying a List of Connections To display a list of connections on the current PXM1E card, enter the dspcons command as follows: PXM1E_SJ.8.PXM.
Chapter 3 Provisioning PXM1E Communication Links General PXM1E Configuration Procedures The following example shows what appears when you enter the dspcons command without parameters. PXM1E_SJ.8.PXM.a > dspcons Local Port Vpi.Vci Remote Port Vpi.Vci State Owner Pri Persistency ----------------------+------------------------+---------+-------+---+----------4.1 4 35 Routed 26 35 OK MASTER 8 Persistent Local Addr: 47.00918100000000001a533377.000001072301.00 Remote Addr: 47.009181000000000164444b61.
Chapter 3 Provisioning PXM1E Communication Links General PXM1E Configuration Procedures OAM Segment Ep: Enabled Pref Rte Id: 0 Cur Rte Id: 6785 Priority: 8 Directed Route: No Num Parties: - ---------- Traffic Parameters ---------Values: Configured (Signalled) Tx Tx Tx Tx Tx Tx PCR: SCR: MBS: CDVT: CDV: CTD: 50 50 1024 250000 N/A N/A (50 ) (50 ) (1024 ) (250000 ) Rx CDV: Rx CTD: Rx PCR: Rx SCR: Rx MBS: 50 50 1024 (50 (50 (1024 ) ) ) N/A N/A -------------------- Preferred Route Parameters-------
Chapter 3 Provisioning PXM1E Communication Links General PXM1E Configuration Procedures Bringing Up a Connection Bringing up a connection routes a P2P connection or all parties on a P2MP connection. To bring up a connection, enter the upcon command using the following format: PXM1E_SJ.8.PXM.a > upcon Replace the portid, vpi and vci parameters with the values that uniquely identify the connection to be brought up. You can locate these parameters by entering the dspcons command.
Chapter 3 Provisioning PXM1E Communication Links General PXM1E Configuration Procedures pswpop6.1.PXM.a > dspparties 5.3 100 100 Port Vpi Vci Owner State Persistency ---------------------------------------------------------------------------5.3 100 100 OK MASTER Persistent Local Addr: 47.009181000000001029300121.000000050300.00 Remote Party 100 101 OK PARTY Persistent Remote Addr: 47.00918100000000c043002de1.000000050300.00 Endpoint Reference: 10 Remote Party 100 110 OK PARTY Persistent Remote Addr: 47.
Chapter 3 Provisioning PXM1E Communication Links General PXM1E Configuration Procedures Deleting a P2MP Party Before you can delete a P2MP connection, you must first delete all parties associated with that connection. A P2MP connection will remain in service as long as there are parties configured on that connection. For example, a P2MP connection that has 100 parties will remain in service, even if 99 of those parties are down.
Chapter 3 Provisioning PXM1E Communication Links General PXM1E Configuration Procedures Step 1 Establish a configuration session with the MGX 8850 (PXM1E) or the MGX 8830 using a user name with GROUP1 privileges or higher. Step 2 Enter the upln command to create an interface between the PXM1E card on the Cisco MGX 8850 or Cisco MGX 8830 switch, and the UXM card on the IGX switch. Step 3 If you are creating a non-IMA interface, enter the addport command.
Chapter 3 Provisioning PXM1E Communication Links General PXM1E Configuration Procedures Step 1 Establish a configuration session with the MGX 8850 (PXM1E) or the MGX 8830 using a user name with GROUP1 privileges or higher. Step 2 At the active PXM1E, enter the delcon or delcons command to delete all connections to the IGX feeder. Note Step 3 If you use the delcon command, you must enter the command once for each connection to the IGX feeder.
Chapter 3 Provisioning PXM1E Communication Links General PXM1E Configuration Procedures Cisco MGX 8800/8900 Series Software Configuration Guide 3-92 Release 5.1, Part Number OL-6482-01, Rev.
C H A P T E R 4 Preparing Service Modules for Communication This chapter describes how to prepare service modules for operation in an MGX switch. All MGX switch cards except PXM, SRM, XM-60, and RPM are service modules. Service modules add ATM, circuit emulation and Frame Relay services to a switch. Table 1-3 in Chapter 1, “Preparing for Configuration,” lists service module services and the service modules that provide them. This table also lists the interfaces supported on the service modules.
Chapter 4 Preparing Service Modules for Communication Configuration Quickstart Configuration Quickstart The quickstart procedure in this section provides a summary of the tasks required to prepare service modules for operation in an MGX switch. This procedure is provided as an overview and as a quick reference for those who already have configured Cisco MGX switches. Step 1 Step 2 Command Purpose username Start a configuration session.
Chapter 4 Preparing Service Modules for Communication Managing Firmware Version Levels for Service Modules Managing Firmware Version Levels for Service Modules The service modules within the switch run two types of firmware: boot firmware and runtime firmware. The boot firmware provides the startup information the card needs. The boot firmware is installed on the board at the factory. The runtime firmware controls the operation of the card after startup.
Chapter 4 Preparing Service Modules for Communication Managing Firmware Version Levels for Service Modules Note If any service module displays the Active/Active card state, you do not have to set the runtime firmware version for that card. Initializing Service Modules Before a service module can operate, it must be initialized in a switch slot. The initialization process defines the runtime software version that will run on the card and identifies the slot in which the card operates.
Chapter 4 Preparing Service Modules for Communication Managing Firmware Version Levels for Service Modules After you enter the setrev command, the System status LED blinks red until the firmware load is complete, and then it changes to non-blinking green. Step 4 To verify the activation of a card for which the status was previously listed as Failed/Active, enter the dspcds command. The status should appear as follows: • All service modules except the MPSM-8-T1E1 card should display Active/Active.
Chapter 4 Preparing Service Modules for Communication Managing Firmware Version Levels for Service Modules 26 27 28 29 30 31 32 26 27 28 29 30 31 31 CESM_8T1/B MPSM-16-T1E1-PPP MPSM-8T1-FRM --CESM_8E1 SRM_3T3 SRM_3T3 22.0(28.17)A 5.0(29.102)A 30.0(28.17)A --22.0(28.17)A ----- 1.0(2.0) 5.0(29.102)A 30.0(28.17)A 1.0(2.0) 1.0(2.0) ----- M8850_SF.8.PXM.a > Step 2 To see the software revision levels for a single card, enter the dspversion command as follows: 8850_NY.1.AXSM.
Chapter 4 Preparing Service Modules for Communication Selecting MPSM Interfaces and Services Selecting MPSM Interfaces and Services MPSM cards are designed to support multiple interface types (T1, E1, T3, E3, and OC3) and multiple services (ATM, Frame Relay, circuit emulation, and PPP), depending on the card.
Chapter 4 Preparing Service Modules for Communication Establishing Redundancy Between Two Service Modules Unknown line module back card present cnfcdmode: Do you want to proceed (Yes/No)? y After you set the interface type and service, the card resets. You can check the status with the dspcd command. You can verify that the cnfcdmode command has been run by looking at the Inserted Card row of the dspcd display.
Chapter 4 Preparing Service Modules for Communication Establishing Redundancy Between Two Service Modules Step 2 If you have not done so already, set the firmware version for both cards, as described in the “Initializing Service Modules” section. Step 3 Enter the dspcds command to verify that both service modules are in the Active state. Step 4 Enter the addred command as follows: pop20one.7.PXM.
Chapter 4 Preparing Service Modules for Communication Selecting a Card SCT The secondary state for the card in the secondary slot changes to Standby only when the secondary card is ready to take over as active card. After you enter the addred command, the switch resets the secondary card. When you first view the redundancy status, the state may be Empty Resvd or Init. The secondary card may require one or two minutes to transition to standby.
Chapter 4 Preparing Service Modules for Communication Selecting a Card SCT pop20two.1.AXSM.a > cnfcdsct Replace sctID with the number of the SCT that you want to assign to the card. Table 7-1 in Chapter 7, “Managing Service Class Templates,”describes the SCTID options. Note Step 5 When a service module is powered up for the first time, the default card SCT file is used. You must run the cnfcdsct command in order to use another SCT file. The default SCT file s 0.
Chapter 4 Preparing Service Modules for Communication Selecting a Port SCT Selecting a Port SCT A port SCT defines queue parameters that apply to egress queues on a port. Port SCTs are configured when provisioning ports. For more information on provisioning service module ports and configuring port SCTs, refer to the configuration and command reference guide for the service module. These guides are listed in Table 1-1 in Chapter 1, “Preparing for Configuration.
C H A P T E R 5 Preparing SRM Cards for Communications To prepare SRM cards for communication, you need to know which SRM features will be used. Because SRM cards operate as extensions of the PXM cards, they are initialized when you initialize the PXM card, so the initialization procedure required for most service modules is not required for SRM.
Chapter 5 Preparing SRM Cards for Communications Configuration Quickstart for Bulk Distribution on SRMs Configured for SONET/SDH When planning for bulk distribution, consider the following guidelines: • Bulk distribution works with T1 and E1 service modules. Refer to the Cisco MGX 8800/8900 Hardware Installation Guide, Releases 2 - 5.1, to see which service modules support bulk distribution. • The Cisco MGX 8800/8900 Hardware Installation Guide, Releases 2 - 5.
Chapter 5 Preparing SRM Cards for Communications Configuration Quickstart for Bulk Distribution on SRMs Configured for T3 Interfaces Step 1 Step 2 Command Purpose username Start a configuration session. Note upln At the active PXM prompt, bring up and activate the SONET/SDH line. This step establishes physical layer connectivity between the SRM and the CPE.
Chapter 5 Preparing SRM Cards for Communications Setting Up SRM Lines Step 3 Command Purpose cnfln At the active PXM prompt, configure the T3 lines if you want to change the default values. Related commands: dsplns See the “Configuring T3 Lines” section later in this chapter. dspln -type Step 4 addlink Map service module lines to the SRM channels they will use. See the “Linking Service Module Lines to SRM Channels, VTs, or VCs” section later in this chapter.
Chapter 5 Preparing SRM Cards for Communications Setting Up SRM Lines Step 3 Enter the dsplns command to verify that the appropriate line is up and to display all available lines on an SRM. Replace logical slot with the slot number of the SRM for which you are displaying lines. The Line State column shows whether a line is up or down as shown in the following example: PXM1E_SJ.8.PXM.
Chapter 5 Preparing SRM Cards for Communications Setting Up SRM Lines mgx8830b.1.PXM.a > cnfln -sonet -slt -clk -lpb -sfs -rdiv -rdip -tt -tm -tf -st -tg Remember that you cannot configure a line until you have brought it up as described in the previous section, “Bringing Up Lines.
Chapter 5 Preparing SRM Cards for Communications Setting Up SRM Lines Table 5-1 Parameters for SONET Line Configuration (continued) Parameter Description -tt The TributaryType selects a tributary type for either SONET or SDH. SONET references virtual tributary (VT) types, and SDH references virtual container (VC) types.
Chapter 5 Preparing SRM Cards for Communications Setting Up SRM Lines Lampoon.1.PXM.a > dsplns 7 Line Line Line Line Num State Type Lpbk ---- ----- ----------- ----------7.1 Down dsx3CbitPar NoLoop 7.2 Down dsx3CbitPar NoLoop 7.3 Down dsx3CbitPar NoLoop Step 3 Length OOF AIS (meters) Criteria cBitsCheck -------- --------- ---------00000001 3Of8Bits Check 00000001 3Of8Bits Check 00000001 3Of8Bits Check To display the current configuration of a line, enter the dspln -ds3 command.
Chapter 5 Preparing SRM Cards for Communications Establishing Redundancy Between SONET/SDH Lines with APS Table 5-2 Parameters for T3 Line Configuration (continued) Parameter Description -clk The -clk option selects the source timing for transmitting messages over the line. Replace with 1 to use the clock signal received over this line from a remote node, or specify 2 to use the local timing defined for the local switch.
Chapter 5 Preparing SRM Cards for Communications Establishing Redundancy Between SONET/SDH Lines with APS Step 2 Verify that the switch has redundant SRM back cards installed in all bays that will support bulk distribution and line redundancy (redundant SRM back cards can support a standalone PXM/SRM installation). For more information, refer to the Cisco MGX 8800/8900 Hardware Installation Guide, Releases 2 - 5.1.
Chapter 5 Preparing SRM Cards for Communications Establishing Redundancy Between SONET/SDH Lines with APS Table 5-4 APS Line Architecture Modes (continued) Option Description 4 Selects 1+1 Y-cable signaling without K1 and K2. Note 5 This option is not supported in this release. Selects 1+1 straight cable signaling without K1 and K2. Note This option is not supported in this release. 1. G.841 has superceded G.783. Cisco MGX switches are in full compliance with G.841 however, as they were with G.
Chapter 5 Preparing SRM Cards for Communications Linking Service Module Lines to SRM Channels, VTs, or VCs Table 5-5 cnfapsln Command Parameters (continued) Option Description -wtr Replace Wait To Restore with the number of minutes to wait after the working line has become functional again, before switching back to the working line from the protection line. The range is 5-12. Example: -wtr 5 -dr Determines whether the line is unidirectional or bidirectional. • 1 = Unidirectional.
Chapter 5 Preparing SRM Cards for Communications Linking Service Module Lines to SRM Channels, VTs, or VCs Step 1 Establish a configuration session with the active PXM using a user name with GROUP1_GP privileges or higher. Step 2 Enter the addlink command on the active PXM to bring up a link between a service module line and an SRM channel, VT, or VC. mgx8830b.1.PXM.a > addlink Table 5-6 describes the command parameters.
Chapter 5 Preparing SRM Cards for Communications Linking Service Module Lines to SRM Channels, VTs, or VCs Step 3 Enter the dsplink command to verify your configuration. Replace with the slot number of the SRM card and the line number you wish to view. In the following example, the user displays the configuration for line 1 on the SRM card represented by logical slot 15. M8850_LA.8.PXM.a > dsplink 15.
Chapter 5 Preparing SRM Cards for Communications Linking Service Module Lines to SRM Channels, VTs, or VCs Table 5-7 SRM SONET Virtual Tributary Mapping (continued) SRME Link Number VTG No. VT No. SRME Link Number VTG No. VT No.
Chapter 5 Preparing SRM Cards for Communications Linking Service Module Lines to SRM Channels, VTs, or VCs Table 5-8 SRM SDH AU3 TUG-2 and TU/VC Mapping (continued) SRME Link Number TUG-2 No. TU-12/VC-12 SRME Link No. Number TUG-2 No. TU-12/VC-12 No.
Chapter 5 Preparing SRM Cards for Communications Linking Service Module Lines to SRM Channels, VTs, or VCs Table 5-9 shows how each SRM link is mapped to a tributary unit group 3 (TUG-2), TUG-2, and a TU or VC within an SDH line when the AU4 tributary group type is selected. Note You cannot mix T1 and E1 signals in a single TUG-2. Table 5-9 SRM SDH AU4 TUG-3, TUG-2, and TU/VC Mapping SRME Link Number TUG-3 No. TUG-2 No. TU-12/VC-1 SRME Link 2 No. Number TUG-3 No. TUG-2 No. TU-12/VC-1 2 No.
Chapter 5 Preparing SRM Cards for Communications Where To Go Next Table 5-9 SRM SDH AU4 TUG-3, TUG-2, and TU/VC Mapping (continued) SRME Link Number TUG-3 No. TUG-2 No. TU-12/VC-1 SRME Link 2 No. Number TUG-3 No. TUG-2 No. TU-12/VC-1 2 No. 31 2 3 2 3 3 32 2 4 2 63 3 Where To Go Next When your line configuration is complete and links have been established (if using bulk distribution), you are ready to start provisioning connections.
C H A P T E R 6 Preparing RPM Cards for Operation This chapter describes how to do the following tasks: Note • Determine which slots host the RPM cards • Initialize RPM cards that are installed in the switch • Verify the software version used on the RPM cards • Configure backup cards for RPM cards • Where to find additional information on configuring RPM cards Some of the procedures in this chapter require you to enter Cisco IOS commands that run on the RPM cards.
Chapter 6 Preparing RPM Cards for Operation Locating RPM Cards in the Switch Step 3 Command Purpose boot system x: Initialize RPM cards by identifying a runtime software file and storing the configuration on the PXM hard disk. boot config e:auto_config_slot copy run start See the “Initializing RPM Cards” later in this chapter. cc 7 resetcd slot Related commands: dspcds Step 4 show version Verify the software version for each RPM card.
Chapter 6 Preparing RPM Cards for Operation Understanding dspcds and dspcd Displays for RPM The following example shows the dspcd command display for an RPM-PR card: M8850_LA.8.PXM.a > dspcd 9 M8850_LA System Rev: 04.09 MGX8850 Slot Number: 9 Redundant Slot: NONE Front Card ---------Inserted Card: RPM_PR Reserved Card: RPM_PR State: Active Serial Number: SAK0419001H Prim SW Rev: --Sec SW Rev: --Cur SW Rev: 12.3(1.7)T1 Boot FW Rev: 12.2(7.
Chapter 6 Preparing RPM Cards for Operation Initializing RPM Cards The next example shows the dspcd command display for an RPM-XF: M8850_SF.7.PXM.a > dspcd 1 M8850_SF System Rev: 04.00 MGX8850 Slot Number: 1 Redundant Slot: NONE Front Card ---------- Apr. 23, 2003 05:27:37 GMT Node Alarm: CRITICAL Upper Card ---------- Inserted Card: RPM_XF MGX-XF-POS-2-OC12 Reserved Card: RPM_XF UnReserved State: Active Active Serial Number: SAG054578LL SAG06300JUC Prim SW Rev: ----Sec SW Rev: ----Cur SW Rev: 12.
Chapter 6 Preparing RPM Cards for Operation Initializing RPM Cards To initialize an RPM card, use the following procedure. Step 1 Establish a configuration session with the switch using a user name at any access level. Note Step 2 Access to the RPM configuration is secured by the Cisco IOS software running on the card. To display the files that can be used to start RPM cards, enter the cd command to select the C:FW directory, and enter the ll command to display the directory contents.
Chapter 6 Preparing RPM Cards for Operation Initializing RPM Cards Note Step 3 If the runtime file is missing, you can transfer the correct file to the switch. This procedure is described in Appendix A, “Downloading and Installing Software Upgrades.” Enter the cc command to select the card slot in which the RPM card is installed. For example: mgx8850a.7.PXM.a> cc 9 (session redirected) Router> As shown in the example, the switch displays the prompt for the Cisco IOS software on the RPM card.
Chapter 6 Preparing RPM Cards for Operation Initializing RPM Cards Step 8 Enter global configuration mode. For example: Router#configure terminal Enter configuration commands, one per line. Step 9 End with CNTL/Z. Enter the boot system command using the format: Router(config)# boot system x: For example: Router(config)#boot system x:rpm-js-mz.122-4.
Chapter 6 Preparing RPM Cards for Operation Verifying the Software Version in Use Caution Step 12 If you do not save the configuration changes, you will have to repeat this procedure. To begin using the new configuration, reset the card from the active PXM card. For example: Router#cc 7 (session redirected) mgx8850a.7.PXM.a> resetcd 9 The card in slot number 9, will be reset.
Chapter 6 Preparing RPM Cards for Operation Establishing Redundancy Between RPM Cards The system image file line indicates which file was used to load the software currently in use. In this example, the software was loaded from the x: drive, which corresponds to C:FW on the switch. The filename shown identifies the source file for the running image. This filename is configured in Cisco IOS global configuration mode with the boot system command.
Chapter 6 Preparing RPM Cards for Operation Configuring SNMP on the RPM Card Step 7 Configure the RPM card to store its configuration on the PXM hard disk by entering the boot config command as follows: Router>boot config e:auto_config_slot# Note Step 8 This step is required. When switchover occurs, the secondary RPM card must be able to load the configuration from the auto_config file on the PXM hard disk.
Chapter 6 Preparing RPM Cards for Operation Where to Go Next Step 6 Enter the copy run start command to save the configuration for use at startup. RPM-PR_mgx8850a_9#copy run start Destination filename [startup-config]? Building configuration...
Chapter 6 Preparing RPM Cards for Operation Where to Go Next Cisco MGX 8800/8900 Series Software Configuration Guide 6-12 Release 5.1, Part Number OL-6482-01, Rev.
C H A P T E R 7 Managing Service Class Templates A Service Class Template (SCT) is a file that contains default configuration data for switch connections and for configuring the hardware to support connections. When you configure a connection, or when an SVC is established, the switch analyzes the connection setup request data, any local configuration data, and the SCTs that apply to the port and to the card.
Chapter 7 Managing Service Class Templates Cisco SCTs Each PXM1E and service module contains default SCT parameters that you can use for communications. Cisco also supplies additional SCTs that you can use to better support communications. If none of the Cisco supplied SCTs meet your needs, you can use Cisco WAN Manager (CWM) to create your own custom SCTs.
Chapter 7 Managing Service Class Templates Cisco SCTs Table 7-1 Card Type AXSM-E Cisco Provided SCTs (continued) SCT Type Card 2 Port AXSM-XG Card2 Port SCT ID PNNI 4 N/A N/A 5 N/A N/A 52 N/A N/A 4 On Off 5 On Off Use for UNI ports on interfaces faster than T1 or E1. There is no difference between port SCTs 4 and 5. 6 Off Off Use for NNI ports on interfaces faster than T1 or E1. 52 On Off Use on AXSM-32-T1-E1-E UNI ports. 53 Off Off Use on AXSM-32-T1-E1-E NNI ports.
Chapter 7 Managing Service Class Templates Managing SCTs Table 7-1 Cisco Provided SCTs (continued) Card Type SCT ID PNNI 4 N/A N/A This is the only card SCT for this card. 4 On On This is the only port SCT for this card. 1 N/A — This is the only card SCT for this card. Port 3 On — Use for UNI ports less than or equal to 4 T1 in bandwidth. For UNI ports greater than 4 T1 in bandwidth, create a new custom SCT. Port 4 Off — Use for NNI ports less than or equal to 4 T1 in bandwidth.
Chapter 7 Managing Service Class Templates Managing SCTs • Downloading SCT Files to the Switch • Registering SCT Files • Updating Registered SCT Files • Deleting a Registered SCT • Deleting Unregistered SCTs Locating SCT Files on a Switch SCT files are stored in two locations on a switch. Unregistered files are stored in the C:/SCT/TEMP directory, which is used to store unregistered files until they are registered using the CLI (as described later in this chapter) or CWM.
Chapter 7 Managing Service Class Templates Managing SCTs -rwxrwxrwx -rwxrwxrwx -rwxrwxrwx -rwxrwxrwx -rwxrwxrwx -rwxrwxrwx -rwxrwxrwx 1 1 1 1 1 1 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 8025 8025 8025 8028 8025 8028 8028 Jun Jun Jun Jun Jun Jun Jun 17 17 17 17 17 17 17 21:35 21:35 21:35 21:35 21:35 21:35 21:35 FRSM12_SCT.CARD.5.V1 FRSM12_SCT.CARD.6.V1 FRSM12_SCT.CARD.7.V1 FRSM12_SCT.PORT.4.V1 FRSM12_SCT.PORT.5.V1 FRSM12_SCT.PORT.6.V1 FRSM12_SCT.PORT.7.
Chapter 7 Managing Service Class Templates Managing SCTs Downloading SCT Files to the Switch When you want to download a new or modified SCT file, you can download the file using CWM or by using an FTP program. If you have used CWM to create or modify an SCT or if you are using CWM to manage your SCTs, it is best to use CWM to download and to register the file. For more information, refer to the Cisco WAN Manager User’s Guide, Release 15.1.
Chapter 7 Managing Service Class Templates Managing SCTs Use the following procedure to manually register SCT files. Step 1 Check the SCT temporary directory on the switch to see if the SCT file you want to register is available. The directory path is C:SCT/TEMP. For information on viewing directories, see the “Browsing the File System” section in Appendix A, “Downloading and Installing Software Upgrades.
Chapter 7 Managing Service Class Templates Managing SCTs Table 7-3 addsct and cnfsct Command Parameters (continued) sct id Enter the SCT identification number, which appears in the file name. major ver Enter the major version number of the SCT file as it appears in the filename. This number changes when a new parameter is added to a MIB. Only Cisco can generate a new major version of a file.
Chapter 7 Managing Service Class Templates Managing SCTs In the following example, the user overwrites and old MPSM card SCT with a new one: M8830_CH.2.PXM.a > cnfsct mpsm155 1 2 1 0xbc8cd86c The cnfsct command does not cause a new SCT to become active on the card type you specify with this command.
Chapter 7 Managing Service Class Templates Managing SCTs Step 6 To verify that the new SCT version has been applied to the appropriate card, enter the dspcd command. Step 7 To verify that a new port SCT is in use on a card, enter the dspportsct gen command. Deleting a Registered SCT When you delete a registered SCT, the SCT is removed from the list of available SCTs and the switch. The SCT is no longer available to cards that match the SCT card type.
Chapter 7 Managing Service Class Templates Managing SCTs Deleting Unregistered SCTs Unregistered SCTs are stored as files in the temporary storage directory, C:SCT/TEMP/. Cisco recommends that you register all SCTs in this directory and delete any SCT files that you do not want to register. If you want to save SCT files that you do not want to register, Cisco recommends that you store these files on external media.
Chapter 7 Managing Service Class Templates Managing Card SCTs Table 7-5 dspscts Command Display Components (continued) Object Description checksum An SCT identification number between 0 and 65535 that matches the checksum embedded in the SCT file. The checksum number for all new SCT files is advertised to the user through the Release Notes for Cisco MGX 8850 (PXM1E/PXM45), Cisco MGX 8950, and Cisco MGX 8830 Switches, Release 5.1.
Chapter 7 Managing Service Class Templates Managing PXM1E Port SCTs mgx8830a.1.PXM.a > dspports ifNum Line Admin Oper. Guaranteed Maximum Port SCT Id ifType VPI State State Rate Rate (VNNI only) ----- ---- ----- ----- ---------- --------- ----------------- ------ ---------1 1.1 Up Up 1412830 1412830 2 NNI 0 2 1.2 Up Up 1412830 1412830 2 NNI 0 3 2.1 Up Up 1412830 1412830 2 NNI 0 Selecting a Port SCT A port SCT defines queue parameters that apply to egress queues on a port.
Chapter 7 Managing Service Class Templates Managing PXM1E Port SCTs Table 7-6 Options for dspportsct Command Option Description abr Displays ABR parameters. bw Displays bandwidth and policing parameters. gen Displays general SCT parameters. cosb Displays COSB parameters. vcThr Displays virtual circuit threshold parameters. cosThr Displays COSB threshold parameters. The SCT parameters are divided within SCT files into two groups: VC descriptors and COSB parameters.
Chapter 7 Managing Service Class Templates Managing PXM1E Port SCTs Table 7-7 describes the SCT ABR Parameters shown in the example. Table 7-7 Parameter SCT ABR Descriptions Description SERV-TYPE The service type (for example, CBR, VBR, ABR) to which the parameters in this table apply (for example, COSB_NUM, CAC_TYPE, UPC_ENB). CI CTRL Congestion indicator (CI) control. When enabled, this parameter specifies that the CI field is an RM1 cell that is used to cause the source to decrease the ACR.
Chapter 7 Managing Service Class Templates Managing PXM1E Port SCTs | ATMF_VBRrt3(259)| 250000 | 100 | 100 | |ATMF_VBRnrt1(260)| 250000 | 100 | 100 | |ATMF_VBRnrt2(261)| 250000 | 100 | 100 | |ATMF_VBRnrt3(262)| 250000 | 100 | 100 | | ATMF_UBR1(263)| 250000 | 100 | 100 | | ATMF_UBR2(264)| 250000 | 100 | 100 | | ATMF_ABR(265)| 250000 | 0 | 100 | | ATMF_CBR2(266)| 250000 | 100 | 100 | | ATMF_CBR3(267)| 250000 | 100 | 100 | | TAG_COS0(512)| 250000 | 100 | 100 | | TAG_COS1(513)| 250000 | 100 | 100 | | TAG_COS2
Chapter 7 Managing Service Class Templates Managing PXM1E Port SCTs 3. MBS = maximum burst size 4. CDVT = cell delay variation tolerance 5. ICR = initial cell rate 6. MFS = maximum frame size Port SCT General Parameters (dspportsct gen) The following report appears when you enter the dspportsct gen command: M8830_CH.1.PXM.
Chapter 7 Managing Service Class Templates Managing PXM1E Port SCTs | TAG_COS7(519)| CLP01_CLP0| DISCARD| DISCARD| +--------------------------------------------------------------------+ Table 7-9 describes the SCT General Parameters shown in the example. Table 7-9 SCT General Parameter Descriptions Parameter Description SERV-TYPE The service type (for example, CBR, VBR, ABR) to which the parameters in this table apply (for example, COSB_NUM, CAC_TYPE, UPC_ENB).
Chapter 7 Managing Service Class Templates Managing PXM1E Port SCTs Table 7-9 SCT General Parameter Descriptions (continued) Parameter Description GCRA1_PLCY Generic Cell Rate Algorithm – Bucket 1 policy. If UPC-Enable is set to disabled, the configured policy is ignored and no cells are discarded or tagged.
Chapter 7 Managing Service Class Templates Managing PXM1E Port SCTs Table 7-10 describes the SCT COSB parameters shown in the example. Table 7-10 SCT COSB Parameter Descriptions Label Range and Units Description COSB N.A. COSB number. MIN-RATE 1–1000000 This field is no longer used and is currently always set to its default value (0). MAX-RATE 1–1000000 This field is no longer used and is currently always set to its default value (100).
Chapter 7 Managing Service Class Templates Managing PXM1E Port SCTs +---------------------------------------+ | SERV TYPE(DEC) | SCALING |PKT DISCARD| | | CLASS | ENABLE | +---------------------------------------+ | VSI_SIGNAL( 2)| 2 | DISABLED | | ATMF_CBR1(256)| 1 | DISABLED | | ATMF_VBRrt1(257)| 2 | DISABLED | | ATMF_VBRrt2(258)| 2 | DISABLED | | ATMF_VBRrt3(259)| 2 | DISABLED | |ATMF_VBRnrt1(260)| 2 | DISABLED | |ATMF_VBRnrt2(261)| 2 | DISABLED | |ATMF_VBRnrt3(262)| 2 | DISABLED | | ATMF_UBR1(263)| 4
Chapter 7 Managing Service Class Templates Managing PXM1E Port SCTs Table 7-11 SCT VC Threshold Parameter Descriptions (continued) Label Description SCALING CLASS Logical Port Scaling Class. Indicates which of the four Scaling Class Tables (see Table 7-13, 1–4) to use on a logical port. Each table is for a specific service category and has an index of 16 entries. Each index entry contains a percentage by which to scale traffic on a connection on a logical port to reduce congestion.
Chapter 7 Managing Service Class Templates Managing PXM1E Port SCTs Table 7-13 Logical Interface Scaling Table (continued) Index Scaling Class Table #1 (CBR) Scaling Class Table #2 (VBR) Scaling Class Table #3 (ABR) Scaling Class Table #4 (UBR) 3 100.00% 100.00% 100.00% 100.00% 4 100.00% 100.00% 100.00% 100.00% 5 100.00% 100.00% 100.00% 100.00% 6 100.00% 100.00% 100.00% 67.00% 7 100.00% 100.00% 100.00% 34.00% 8 100.00% 100.00% 50.00% 20.00% 9 100.00% 50.00% 25.
Chapter 7 Managing Service Class Templates Managing PXM1E Port SCTs Table 7-14 SCT COSB Threshold Parameter Descriptions Label Description COSB COSB number. MAX_THR The maximum threshold, in cells, beyond which all CLP (0+1) cells must be dropped. EFCI Explicit Forward Congestion Indication. The threshold level, in cells, for congestion indication for ABR traffic using CI control. CLP_LO /EPD1 Cell Loss Priority Low/ Early Packet Discard 1.
Chapter 7 Managing Service Class Templates Managing PXM1E Port SCTs Cisco MGX 8800/8900 Series Software Configuration Guide 7-26 Release 5.1, Part Number OL-6482-01, Rev.
C H A P T E R 8 2 Managing PNNI Nodes and PNNI Routing This chapter provides procedures that you can use to manage Private Network-to-Network Interface (PNNI) nodes and routes.
Chapter 8 Managing PNNI Nodes and PNNI Routing Managing PNNI Nodes Creating Upper Level Peer Groups Upper level peer groups enable routing from one PNNI peer group to another. If you are managing a single peer group WAN, you do not need to create upper level peer groups. Note The “Configuring PNNI Node Parameters” section in Chapter 2, “Configuring General Switch Features,” describes how to configure the lowest level peer group parameters, which many upper level peer group parameters are based on.
Chapter 8 Managing PNNI Nodes and PNNI Routing Managing PNNI Nodes Add the upper level PNNI logical node that will participate in the higher level PNNI group using the addpnni-node command. Replace level with the PNNI level for the higher level peer group. The PNNI level value must be smaller than the level value for the lower level peer groups. The following example creates a logical PNNI node at PNNI level 40. PXM1E_SJ.7.PXM.
Chapter 8 Managing PNNI Nodes and PNNI Routing Managing PNNI Nodes Pref PGL node name .....PXM1E_SJ PGL.....................56:160:47.00918100000000036b5e31b3.00036b5e31b3.01 PGL node name ..........M8850_NY Active parent node id...0:0:00.000000000000000000000000.000000000000.00 Active parent node name node index: 2 PGL state...... Priority....... Starting 0 Init time(sec)....... 15 Override delay(sec).. 30 Re-election time(sec) 15 Pref PGL................0:0:00.000000000000000000000000.000000000000.
Chapter 8 Managing PNNI Nodes and PNNI Routing Managing PNNI Nodes Enabling and Disabling the Complex Node Feature The complex node feature applies to PGL parent LGNs in MPG networks. When this feature is disabled, parent LGNs present other peer groups to the child peer group using simple node representation. With simple node representation, each external peer group is presented as a simple node with a single cost for routing through the peer group.
Chapter 8 Managing PNNI Nodes and PNNI Routing Managing PNNI Nodes To view the status of the -transitRestricted option, enter the dsppnni-node command as shown in the following example: mgx8830a.1.PXM.a > dsppnni-node node index: 1 node name: 8850_LA Level............... 56 Lowest.............. true Restricted transit.. on Complex node........ off Branching restricted on Admin status........ up Operational status.. up Non-transit for PGL election.. off Node id...............56:160:47.
Chapter 8 Managing PNNI Nodes and PNNI Routing Managing PNNI Nodes Table 8-1 Parameters for addpnni-summary-addr Command Parameter Description node-index The node index assigned to a PNNI logical node on a network. Range = 1 – 65535 address-prefix The ATM address prefix assigned to the network. prefix-length The length of the summary address-prefix in number of bits, equal or less than 152 bits. Currently, the zero-length summary address is not supported. -type The type of the summary address.
Chapter 8 Managing PNNI Nodes and PNNI Routing Managing PNNI Nodes You can use the cnfpnni-routing-policy command to control which SPTs are created, how often they are updated, and other SPT related features. To display the current routing policies for a node, enter the dsppnni-routing-policy command as follows: M8830_CH.1.PXM.a > dsppnni-routing-policy SPT epsilon......... SPT holddown time... bn path holddown time CTD Background Table 0 1 2 on Load balance........ random On demand routing...
Chapter 8 Managing PNNI Nodes and PNNI Routing Managing PNNI Nodes Table 8-3 Parameters for cnfpnni-routing-policy Command (continued) Parameter Description -bnPathHolddown The border node holddown timer defines the node’s minimum time interval between two consecutive calculations of the border node path tables. If a network is stable, it may not be necessary to generate border node route tables 10 times per second.
Chapter 8 Managing PNNI Nodes and PNNI Routing Managing PNNI Routes Table 8-4 Parameters for cnfpnni-timer Command Parameter Description nodeindex Logical node’s node index. -ptseholddown This is the holddown time between two consecutive originations of PTSEs on the node. Range: (0.1 through 10) second Default = 1 -helloholddown Value for the Hello hold down timer that limits the rate at which it sends Hellos. -hellointerval Initial value for the Hello timer.
Chapter 8 Managing PNNI Nodes and PNNI Routing Managing PNNI Routes To configure the route selection method, enter the cnfpnni-routing-policy command as follows: mgx8830a.1.PXM.a > cnfpnni-routing-policy -onDemand firstfit|bestfit Enter firstfit to select the first route discovered, or enter bestfit to select the optimum route. To display the route selection method, enter the dsppnni-routing-policy command as follows: mgx8830a.1.PXM.a > dsppnni-routing-policy SPT SPT SPT CTD epsilon.........
Chapter 8 Managing PNNI Nodes and PNNI Routing Managing PNNI Routes Preferred routes can be configured to be directed or non-directed. A directed route only attempts a connection on the preferred route. If the connection cannot route over the preferred route, that connection will go into a failed state. A non-directed route first attempts to route over the preferred route. If the preferred route is not available, the connection will be attempted over other routes.
Chapter 8 Managing PNNI Nodes and PNNI Routing Managing PNNI Routes Step 1 Establish a configuration session using a user name with GROUP1 privileges or higher. Step 2 Enter the addnwnode command as follows to add the a node to the network node table: U1.8.PXM.a > addnwnode [-name ] Table 8-5 describes the parameters you can configure through the addnwnode command. Table 8-5 addnwnode Command Parameters nodeId This 22-octet uniquely identifies a PNNI node.
Chapter 8 Managing PNNI Nodes and PNNI Routing Managing PNNI Routes Step 1 Enter the dspnwnodes command to see the nodes in this database. These are the nodes you can use to set up your preferred route. U1.8.PXM.a > dspnwnodes Total Number of Network Nodes : 14 Node Identifier PXM Node name --------------- --- --------56:160:47.0091810000000004c113ba39.0004c113ba39.01 56:160:47.00918100000000001a531c41.00001a531c41.01 56:160:47.009181000000000142266086.000142266086.01 56:160:47.00918100000000001a531c01.
Chapter 8 Managing PNNI Nodes and PNNI Routing Managing PNNI Routes Table 8-6 -dstNEpos addpref Command Parameters This integer identifies the position of the destination node in the NE sequence. For instance, an NE of 4 indicates that the fourth NE represents the destination node. Range: 1–20 Default: none -ne1 through -ne20 Including the local node, you can specify up to 20 NEs in the preferred route. Each NE is defined by a pairing of a node and a port.
Chapter 8 Managing PNNI Nodes and PNNI Routing Managing PNNI Routes Note There are other optional parameters that you can set using the addcon and cnfcon commands, but they do not appear in Table 8-7 because you do not need to set them when you are associating an SPVC or SPVP with a preferred route. For information on all the command parameters for PXM1E cards, see Chapter 4, “Preparing Service Modules for Communication.
Chapter 8 Managing PNNI Nodes and PNNI Routing Managing PNNI Routes Modifying a Preferred Route Use the cnfpref command to modify a preferred route. The cnfpref command lets you re-specify existing NEs in a route, or add one or more NEs to an existing route. You can also change an NE to indicate that it is the destination node. A new destination node must have the highest NE number in the route. (See the detailed usage guidelines for the addpref command for details.
Chapter 8 Managing PNNI Nodes and PNNI Routing Managing PNNI Routes Table 8-8 Parameters for cnfpref Command (continued) -dstNEpos This integer identifies the position of the destination node in the NE sequence. For instance, an NE of 4 indicates that the fourth NE represents the destination node. Range: 1–20 Default: none -ne1 through -ne20 Including the local node, you can specify up to 20 NEs in the preferred route. Each NE is defined by a pairing of a node and a port.
Chapter 8 Managing PNNI Nodes and PNNI Routing Managing PNNI Routes Deleting a Node from the Network Node Table Before you can delete a node from the network node table, enter the dspnwnode command to ensure that the node is not part of a preferred route. Note You can not delete a node from the network node table if it is currently being used by a preferred route.
Chapter 8 Managing PNNI Nodes and PNNI Routing Managing PNNI Routes Configuring the Administrative Weight The link administrative weight (AW) is used to calculate the total cost of a route and can be used by the PNNI controller when it has to choose between multiple parallel links. You can assign different AW values for each ATM class of service. Note The role of AW in route and link selection is described in more detail in the Cisco PNNI Network Planning Guide for MGX and SES Products.
Chapter 8 Managing PNNI Nodes and PNNI Routing Managing PNNI Routes Replace pnportid with the port ID in the format slot[:subslot].port[:subport]. (This is the same format that appears when you display ports with the dsppnport command.) Replace token with the value you want to assign to the link. The range is 0 to 4294967295, and the default value is 0. The token value of 0 disables link aggregation for the link.
Chapter 8 Managing PNNI Nodes and PNNI Routing Managing PNNI Routes Configuring the Deroute Delay The deroute delay feature establishes a wait time between the time when the switch detects an interface failure and the time when connections are released (derouted). This feature provides time for the condition that caused the interface failure to recover. If the interface recovers, an unnecessary deroute is avoided.
Chapter 8 Managing PNNI Nodes and PNNI Routing Managing PNNI Routes The following example sets the deroute delay to 20 seconds and uses the dsppnportloscallrel command to verify the configuration change: PXM1E_SJ.7.PXM.a > cnfpnportloscallrel 7:2.10:10 yes -delay 30 PXM1E_SJ.7.PXM.a > dsppnportloscallrel 7:2.
Chapter 8 Managing PNNI Nodes and PNNI Routing Managing Priority Routing For better call performance on PXM45/B cards, the following commands need to be issued after the upgrading to Release 3.0.
Chapter 8 Managing PNNI Nodes and PNNI Routing Managing Priority Routing Because the bandwidth groups are node-level, they apply to all priorities. The same ranges exist for priority 0, priority 1, priority 2, and so on down to the lowest priority. Connections requiring the least bandwidth are grouped at the low end of the range, and connections requiring the most bandwidth are grouped at the top end of the range.
Chapter 8 Managing PNNI Nodes and PNNI Routing Managing Priority Routing Table 8-9 cnfpri-routing Command Parameters (continued) Parameter Description -bwincr The increment for the cell rate between the upper and lower bounds of each intermediate bandwidth group. For example, an increment of 2000 means that a range starting at 10000 cps ends at 12000 cps.
Chapter 8 Managing PNNI Nodes and PNNI Routing Managing Priority Routing Note If you are setting up priority routing on a node that already has established SPVCs, their routing priority is set to 8 by default. You can change the routing priority on an established connection with the cnfcon command. (See the next section “Modifying SPVC Priority Routing Configuration.
Chapter 8 Managing PNNI Nodes and PNNI Routing Managing Priority Bumping 0 P2MP Details: 0 0 1 Type to continue, Q to stop: DSPPNPORT (P=Persistent, NP=Non-Persistent, Pa = Party, Act=Active) Type #Root: #Leaf: #Party: svcc: 0 0 0 svpc: 0 0 0 #Spvc-P: #Spvc-NP: #SpvcAct: #Spvp-P: #Spvp-NP: #SpvpAct: 0 0 0 0 0 0 #SpvcPa-P:#SpvcPaAct:#SpvpPa-P: #SpvpPaAct: 0 0 0 0 Managing Priority Bumping Release 5.0 introduces a new feature called priority bumping.
Chapter 8 Managing PNNI Nodes and PNNI Routing Managing Priority Bumping When you enable connection bumping, you can specify a maximum number of bumpable connections and a maximum number of concurrent bumps. The maximum number of bumpable connections specifies how many lower priority connections can be bumped for a single higher priority connection. The range is 1 to 10, and the default is 10.
Chapter 8 Managing PNNI Nodes and PNNI Routing Managing Priority Bumping 6 7 8 9 10 11 12 13 14 15 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 The Priority column lists the available connection priorities. The Bumping Conns column shows how many connections at each priority level have bumped other connections, and the Bumped Conns column shows how many connections have been bumped to support the bumping connections.
Chapter 8 Managing PNNI Nodes and PNNI Routing Managing Connection Grooming The Priority column lists the available connection priorities. The usedCR Xmt and usedCR Rcv columns show the bandwidth in use at each priority level in the transmit and receive directions, respectively. The # of Conns column shows the number of logical connection numbers reserved at each priority level.
Chapter 8 Managing PNNI Nodes and PNNI Routing Managing Connection Grooming Figure 8-2 Soft Reroute Method of Connection Grooming Slave endpoint Master endpoint B C D E A A F B C D E B1 C1 ‘D 1 F E1 After sending release D E A F B 1 C 1 D 1 E 1 ‘ After receiving release F A 1 B 1 C 1 D 1 E The first panel in Figure 8-2 show the incumbent connection. The master endpoint is A and the slave endpoint is F. Endpoints B, C, D, and E are NNI endpoints.
Chapter 8 Managing PNNI Nodes and PNNI Routing Managing Connection Grooming Softrerouting is disabled by default. For soft rerouting to work properly, you must enable soft rerouting and the nodes that host the master and slave endpoints must run Cisco MGX software Release 5 or later. The first time a connection is rerouted, the master endpoint queries the slave endpoint to determine if it supports soft rerouting.
Chapter 8 Managing PNNI Nodes and PNNI Routing Managing Connection Grooming Table 8-10 Parameters for cnfrteopt Command Parameter Description portid Root endpoint port identifier, in the format [shelf.]slot[:subslot].port[:subport]. To display a list of the available ports, enter the dsppnports command. flag The flag parameter enables or disables automatic grooming. To enable automatic grooming, replace the flag variable with enable.
Chapter 8 Managing PNNI Nodes and PNNI Routing Managing Connection Grooming Absolute Cost CDV CBR: 0 Absolute Cost CDV RTVBR: 0 Port Enable VPI/VCI Range 6:1.3:13 yes all Interval 60 Time Range anytime Weekday(s) all The next example disables the configuration completed in the previous example: M8850_LA.7.PXM.a > cnfrteopt 6:1.3:13 disable M8850_LA.7.PXM.a > dsprteoptcnf 6:1.
Chapter 8 Managing PNNI Nodes and PNNI Routing Managing Connection Grooming Manually Grooming Connections Manual grooming, which is also called on-demand grooming, grooms one or more port connections immediately. You can groom a specific connection by specifying the port ID, VPI, and VCI, groom a range of connections, or groom all connections on the port. To manually groom the connections on an port, enter the optrte command as follows: M8850_LA.7.PXM.
Chapter 8 Managing PNNI Nodes and PNNI Routing Managing Connection Grooming The threshold gains can be defined for all applicable ATM service types as shown in Table 8-12.
Chapter 8 Managing PNNI Nodes and PNNI Routing Managing Connection Grooming Negotiated Slave Soft Reroute Capability: DISABLE Soft Reroute Last Cause: N/A. Soft Reroute is not performed yet. In the example above, the transmit and receive values for CDV and CTD are -1. Also the Max Cost value is set to -1. The Max Cost of a connection is defined during connection configuration and specifies the maximum permissible sum of the administrative weight (AW) on each line along that connection.
Chapter 8 Managing PNNI Nodes and PNNI Routing Managing Connection Grooming Table 8-14 Parameters for cnfrteoptthresh Command Parameter Description type Grooming threshold parameter type to be set. You can set either the grooming percentage (enter per) or the absolute value (enter abs). To change both the percentage and absolute value, you must enter the cnfrteoptthresh command twice, specifying a different threshold parameter type each time.
Chapter 8 Managing PNNI Nodes and PNNI Routing Managing Connection Grooming Absolute Absolute Absolute Absolute Absolute Absolute Absolute Absolute Port 7.35 7.36 7.37 7.38 13.1 30.1 30.2 6:1.
Chapter 8 Managing PNNI Nodes and PNNI Routing Managing Connection Grooming Table 8-15 Parameters for cnfndrteopt Command (continued) -trkutil Use the -trkutil option to set a maximum trunk utilization limit for grooming. Enter a number in the range of 5 to 100 percent. The default setting is 100 percent. -softrerout Use the -softreroute option to enable or disable soft rerouting during grooming. To enable e soft rerouting, enter enable. To disable soft rerouting, enter disable.
Chapter 8 Managing PNNI Nodes and PNNI Routing Managing Connection Grooming Nodal Route Optimization Parameters: -----------------------------------Orderly Grooming Feature: Orderly Grooming Batch Size: Orderly Grooming Timeout: Trunk Util Threshold Percent: Soft Reroute: Enabled 20 300 85 Disabled Displaying Grooming Configuration Parameters Two different commands display grooming configuration parameters. These commands are described in the following sections.
Chapter 8 Managing PNNI Nodes and PNNI Routing Managing Connection Grooming 28.1 7:2.11:11 7:2.12:12 no no no all all all 60 60 60 anytime anytime anytime all all all The next example shows the dsprteoptcnf command display for a specific port. PXM1E_SJ.7.PXM.a > dsprteoptcnf 7:2.
Chapter 8 Managing PNNI Nodes and PNNI Routing Managing Connection Grooming 9.2 done 0 0 0 0 0 0 11.1 done 0 0 0 0 0 0 11.5 done 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 The grooming statistics column head abbreviations are described above the command display. Configuring the AIS Delay An alarm indication signal (AIS) is sent to CPE at each end of a connection when the switch detects a connection alarm.
Chapter 8 Managing PNNI Nodes and PNNI Routing Displaying Node Configuration Information Step 1 Establish a configuration session using a user name with GROUP1 privileges or higher. Step 2 Enter the dsppnportie command as follows to display the current configuration for the soft reroute IE feature. Replace with the appropriate port identifier in the format slot:bay.line:ifnum.(You can use the dsppnports command to display port numbers in use.) PXM1E_SJ.7.PXM.a > dsppnportie 7:2.
Chapter 8 Managing PNNI Nodes and PNNI Routing Displaying Node Configuration Information The significant information that will display is as follows: • Node index • Node name • Node level (56 for all nodes until multiple peer groups are supported) • Restricted transit—a flag that can prevent PNNI routing from transmitting this node • Branching restricted—a flag that can prevent cpu-intensive branching at this node • Admin status—up/down • Operational status—up/down • Nontransit for PGL ele
Chapter 8 Managing PNNI Nodes and PNNI Routing Displaying Node Configuration Information Table 8-16 Objects Displayed for dsppnni-summary-addr Command (continued) Parameter Description -suppress true = summary address is not advertised. -state The summary address state can be advertising, notadvertised, or inactive. This example shows the dsppnni-summary-addr command line that displays the PNNI address prefixes. mgx8830a.1.PXM.a > dsppnni-summary-addr node index: 1 Type..............
Chapter 8 Managing PNNI Nodes and PNNI Routing Displaying Node Configuration Information 47.0091.8100.0000.0030.ff0f.ef38.0030.ff0f.ef38.99/160 Type: host Port id: 17251106 47.0091.8100.0000.0030.ff0f.ef38.1111.1101.0001.01/160 Type: host Port id: 17251106 47.0091.8100.0000.0050.0fff.e0b8/104 Type: static Port id: 17635339 39.6666.6666.6666.6666.6666.6666.6666.6666.6666/152 Type: uni Port id: 17504267 mgx8830a.1.PXM.
Chapter 8 Managing PNNI Nodes and PNNI Routing Displaying Node Configuration Information The final option allows you to see all communication lines in the PNNI network. The following example shows the report for this command: mgx8830a.1.PXM.a > dsppnni-link node index : 1 Local port id: 17504278 Remote port id: 17176597 Local Phy Port Id: 11:2.2:22 Type. lowestLevelHorizontalLink Hello state....... twoWayInside Derive agg........... 0 Intf index........... 17504278 SVC RCC index........ 0 Hello pkt RX..
Chapter 8 Managing PNNI Nodes and PNNI Routing Displaying Node Configuration Information Table 8-18 describes the objects displayed for the dsppnni-routing-policy command. Table 8-18 Objects Displayed for the dsppnni-routing-policy Command Parameter Description SPT epsilon The tolerance used during route calculation to determine which paths qualify as equal-cost. The range is from 0 – 20. SPT holddown The interval between two consecutive calculations for generating routing tables.
Chapter 8 Managing PNNI Nodes and PNNI Routing Displaying Node Configuration Information Table 8-19 Objects Displayed for the dsppnni-svcc-rcc-timer Command Parameter Description node-index The node index assigned to a PNNI logical node on a network. The range is from 1 to 65535. Init time The amount of time (in seconds) this node will delay advertising its choice of preferred an SVCC to a neighbor with a numerically lower ATM address, after determining that such an SVCC should be established.
Chapter 8 Managing PNNI Nodes and PNNI Routing Managing CUGs Geneva.7.PXM.a > dsppnni-svcc-rcc node index: 1 svc index: 33 Hello pkt RX........ 34 SVCC VPI............ 34 Hello pkt TX........ 34 SVCC VCI............ 128 Hello state........... 2wayOutside Remote node id.........56:160:39.840f80113744000000400202.00107b0efe01.00 Remote node ATM addr...39:840f.8011.3744.0000.0040.0102.4000.0c80.8030.00 node index: 2 svc index: 33 Hello pkt RX........ 34 SVCC VPI............ 34 Hello pkt TX........
Chapter 8 Managing PNNI Nodes and PNNI Routing Managing CUGs Step 1 Establish a configuration session using a user name with GROUP1 privileges or higher. Step 2 Enter the dsppnports command to locate the port to which you want to add the address,.
Chapter 8 Managing PNNI Nodes and PNNI Routing Managing CUGs If a prefix or address is not assigned to any CUG, it can still communicate with a CUG member only when that member is configured to communicate with non-CUG members. This is described in “Managing Access between a CUG Member and Non-Members or Members of Other CUGS,” which appears later in this chapter. To create a CUG or assign a new user to a CUG, use the following procedure.
Chapter 8 Managing PNNI Nodes and PNNI Routing Managing CUGs Step 3 Note To verify a new CUG assignment, enter the dspcug command as described in the “Displaying CUG Configuration Data” section that follows. After a CUG is assigned to an interface address or prefix, the rules change for adding or deleting that address or prefix on other interfaces. Displaying CUG Configuration Data The following procedure describes how to display CUG configuration information.
Chapter 8 Managing PNNI Nodes and PNNI Routing Managing CUGs Table 8-21 setcugdefaddr Command Parameters Parameter or Option Description atm-address Replace this parameter with the NSAP or E.164 address or prefix of a local UNI interface. length If the AESA or prefix you are assigning to a CUG uses the NSAP format, specify the address length in bits. A full AESA is 160 bits (20 bytes times 8 bits).
Chapter 8 Managing PNNI Nodes and PNNI Routing Managing CUGs Step 3 To change a CUG access configuration, enter the cnfcug command using the following format: mgx8830a.1.PXM1.a > cnfcug [-callsbarred {none|incoming|outgoing}] The cnfcug command parameters are described in Table 8-20. You must enter the CUG parameters that were defined when the CUG was assigned with the addcug command.
Chapter 8 Managing PNNI Nodes and PNNI Routing Managing CUGs Step 4 To change the configuration for access outside of CUG membership, enter the cnfaddrcug command using the following format: mgx8830a.1.PXM1.a > cnfaddrcug [-pref ] [-oa {disallowed|percall|permanent}] [-ia {disallowed|allowed}] The cnfaddrcug command parameters are described in Table 8-22.
Chapter 8 Managing PNNI Nodes and PNNI Routing Managing CUGs You can use the cnfaddrcug command to assign a preferential CUG to a user. A preferential CUG is applied to calls when the user does not specify a CUG index. A user with a preferential CUG does not need to signal a CUG index to establish connections to other members of the preferential CUG. A preferential CUG assignment is ignored when the user explicitly requests a CUG during call setup.
Chapter 8 Managing PNNI Nodes and PNNI Routing Managing CUGs Note When you delete a CUG assignment, all active connections that have been validated with that CUG are unaffected by the change. To completely delete a CUG from a network, you must delete all CUG assignments on all switches. Step 1 Establish a configuration session using a user name with SUPER_GP privileges or higher.
Chapter 8 Managing PNNI Nodes and PNNI Routing Maintaining a Persistent Network Topology for CWM Step 3 Enter the cnfpnportie command as follows to block the CUG IE. mgx8830a.1.PXM1.a > cnfpnportie -cugie disallowed Replace with the port identifier in the format slot:bay.port:interface. The disallowed option always blocks the CUG IE. Step 4 Note To verify your change, enter the dsppnportie command as described in Step 2 of this procedure. Refer to Q.2955.
Chapter 8 Managing PNNI Nodes and PNNI Routing Maintaining a Persistent Network Topology for CWM Step 3 Enter the dsptopogw command to verify that the current node is functioning as a gateway, as shown in the following example. 8830_CH.1.PXM.a > dsptopogw Admin State : ENABLED Operational State ENABLED The following two states are associated with the topology database: • the admin state is set by CLI or CWM, and can be either enabled or disabled.
Chapter 8 Managing PNNI Nodes and PNNI Routing Maintaining a Persistent Network Topology for CWM Note The topology database in Release 3 and later supports only those feeder nodes that are connected to MGX 8850 nodes. Feeder nodes that are connected to other types of nodes do not appear in the persistent topology database.
Chapter 8 Managing PNNI Nodes and PNNI Routing Maintaining a Persistent Network Topology for CWM Table Index: 2 Node Name: PXM1E_SJ Node ID: 56:160:47.00918100000000001a533377.00001a533377.01 Primary IP: 10.10.10.122 Primary IP Type: atm0 Secondary IP: 172.29.52.122 Secondary IP Type: lnPci0 SysObjId: 1.3.6.1.4.1.9.1.
Chapter 8 Managing PNNI Nodes and PNNI Routing Maintaining a Persistent Network Topology for CWM Table 8-24 Topology Database Feeder Node Information (continued) Note Object Description Feeder Port The feeder’s port numbers, which identify the port on the feeder itself. Feeder model number The feeder’s model number. This integer is used to differentiate between feeder platforms.
Chapter 8 Managing PNNI Nodes and PNNI Routing Maintaining a Persistent Network Topology for CWM Persistent Topo Link Index: 2 Local Node Id : 56:160:47.00918100000000001a538943.00001a538943.01 Remote Node Id : 56:160:47.00918100000000036b5e2bb2.00036b5e2bb2.01 Local Port Id : 1:2.
Chapter 8 Managing PNNI Nodes and PNNI Routing Maintaining a Persistent Network Topology for CWM Node Topo Index: 6 Node Name: M8850_LA Node ID: 56:160:47.00918100000000036b5e2bb2.00036b5e2bb2.01 Local IfIndex: 17176589 Local IfName: atmVirtual.06.1.3.13 Feeder ATM IP: 10.10.10.111 Feeder LAN IP: 172.29.52.
Chapter 8 Managing PNNI Nodes and PNNI Routing Maintaining a Persistent Network Topology for CWM Disabling a Gateway Node To disable a node’s status as a gateway node, use the following procedure: Step 1 Establish a configuration session on the switch you want to become the gateway node, using a user name with SUPER_GP privileges or higher.
Chapter 8 Managing PNNI Nodes and PNNI Routing Maintaining a Persistent Network Topology for CWM Step 4 Enter the deltopond command to delete the appropriate node from the node topology database. Replace with index number of the node you want to delete, as shown in the following example: M8830_CH.1.PXM.a > deltopond 1 Step 5 Note Enter the dsptopondlist command to verify that the appropriate node was deleted from the node topology database.
Chapter 8 Managing PNNI Nodes and PNNI Routing Maintaining a Persistent Network Topology for CWM Cisco MGX 8800/8900 Series Software Configuration Guide 8-70 Release 5.1, Part Number OL-6482-01, Rev.
C H A P T E R 9 Switch Operating Procedures This chapter describes procedures you can use to manage the MGX 8850 (PXM1E/PXM45), MGX 8850/B, MGX 8950, MGX 8830, MGX 8830/B switches and the MGX 8880 Media Gateway. Managing the Configuration Files The following sections describe how to save a switch configuration in a single zipped file, clear or erase a configuration, and restore a configuration from a file.
Chapter 9 Switch Operating Procedures Managing the Configuration Files configuration exactly as it was when the configuration file was saved. If the boot and runtime files have been removed from the switch, they must be transferred to the switch before the restored configuration can start. Note If you have upgraded software on the switch since the last time the configuration was saved, a configuration restore will restore the non-upgraded software versions and configuration data.
Chapter 9 Switch Operating Procedures Managing the Configuration Files The 'saveallcnf' command can be time-consuming. The shelf must not provision new circuits while this command is running. Do not run this command unless the shelf configuration is stable or you risk corrupting the saved configuration file. ATTENTION PLEASE NOTE: -> If you want to abort the save, please use abortallsaves CLI.
Chapter 9 Switch Operating Procedures Managing the Configuration Files M8950_SF.7.PXM.a > ll Listing Directory .: drwxrwxrwx 1 0 drwxrwxrwx 1 0 drwxrwxrwx 1 0 -rwxrwxrwx 1 0 -rwxrwxrwx 1 0 0 0 0 0 0 16384 16384 16384 15065924 15065919 Jan Jan Jan Jan Jan 24 23 24 24 24 18:12 04:38 18:12 18:12 17:50 ./ ..
Chapter 9 Switch Operating Procedures Managing the Configuration Files To clear the configuration for a service module, use the following procedure. Step 1 Establish a configuration session using a user name with SERVICE_GP privileges or higher. Step 2 If the card is configured for redundancy, remove card redundancy with the delred command. For more information, see the “Removing Redundancy Between Two Cards” section later in this chapter.
Chapter 9 Switch Operating Procedures Managing the Configuration Files To restore a saved switch configuration, use the following procedure. Step 1 Establish a configuration session using a user name with SERVICE_GP privileges or higher. Step 2 Verify that the file from which you want to restore configuration data is located in the C:/CNF directory. Note The C:/CNF directory is the only location from which you can restore a configuration file.
Chapter 9 Switch Operating Procedures Managing ILMI Managing ILMI The following sections describe how to • Enable and disable the integrated local management interface (ILMI) feature on a port • Display ILMI port configuration data • Display and clear ILMI management statistics • Delete ILMI prefixes Enabling and Disabling ILMI on a Port The Cisco MGX switches provide several commands that you can use to enable or disable ILMI on a port.
Chapter 9 Switch Operating Procedures Managing ILMI Displaying the ILMI Port Configuration The following procedure describes some commands you can use to view the ILMI port configuration. Step 1 Establish a configuration session using a user name with access privileges at any level. Step 2 To display the ILMI configuration for all ports on a PXM1E or AXSM card, enter the dspilmis command. The following example shows the dspilmis command report: mgx8830a.1.PXM.a > dspilmis Sig.
Chapter 9 Switch Operating Procedures Managing ILMI 1 Step 4 1 On 0 16 On 1 5 4 To display the operational state of ILMI on all ports, enter the dsppnports command at the PXM prompt as shown in the following example: mgx8830a.1.PXM.
Chapter 9 Switch Operating Procedures Managing ILMI Peer Peer Peer ILMI ILMI INFO: Addressreg: enable Ip Address : 0.0.0.0 Interface Name : atmVirtual.01.1.1.01 Link State : UpAndNormal Version : ilmi40 No Prefix registered Displaying and Clearing ILMI Management Statistics The following procedure describes some commands you can use to view ILMI management statistics. Step 1 To display ILMI management statistics for a port, enter the dspilmicnt command as follows: mgx8830a.1.PXM.
Chapter 9 Switch Operating Procedures Determining the Software Version Number from Filenames Deleting ILMI Prefixes The following procedure describes how to delete an ILMI address prefix from a port. Note The procedure for adding ILMI prefixes is described in “Configuring ILMI Dynamic Addressing” in Chapter 3, “Provisioning PXM1E Communication Links.” Step 1 Establish a configuration session using a user name with GROUP1 privileges or higher.
Chapter 9 Switch Operating Procedures Determining the Software Version Number from Filenames In most cases, you will find the correct firmware version numbers in the Release Notes for Cisco MGX 8850 (PXM1E/PXM45), Cisco MGX 8950, and Cisco MGX 8830 Switches, Release 5.1.00 and the Release Notes for the Cisco MGX 8880 Media Gateway, Release 5.0.02. If the release notes are not available, you can use the firmware filename to determine the version number as described in the following procedure.
Chapter 9 Switch Operating Procedures Determining the Software Version Number from Filenames Filename Format for Released Software Version number: Filename: Card designator 2 . 0 (1.1) pxm 45_002.000.001.001_mgx.fw Major version Minor Maintenance Patch version level level Image description 42937 Figure 9-1 Filenames that include “_mgx” are for runtime PXM firmware, and filenames that include “_bt” are for boot firmware.
Chapter 9 Switch Operating Procedures Displaying Software Revisions for Cards The first example, 2.0(1), is for released firmware version 2.0, maintenance release 1. The second example, 2.0(1.255), is for patch 255 to version 2.0, maintenance release 1. The other examples are for prerelease firmware. Prerelease firmware does not include patches; the maintenance release number is increased for each software change.
Chapter 9 Switch Operating Procedures Displaying Software Revisions for Cards ---- ---- -------- -------- -------- 01 01 02 03 04 05 06 07 08 09 10 11 12 13 14 02 04 04 05 06 07 07 09 10 11 12 13 14 RPM_XF IOSver IOSver Cur SW Rev: 12.3(20040916:060502) Boot FW Rev: 12.3(20040916:060502) RPM 12.3(7)T3 12.3(3.9)T2 AXSME_8OC3 5.0(28.65)A 5.0(28.65)A AXSME_8OC3 5.0(28.65)A 5.0(28.65)A AXSM_4OC12_B 5.0(28.65)A 5.0(28.65)A AXSM-32-T1E1-E 5.0(28.65)A 5.0(28.65)A PXM45B 5.0(29.102)P1 5.0(29.
Chapter 9 Switch Operating Procedures Managing Redundant Cards Displaying Software Revisions for a Single Card To display the boot and runtime software revisions in use on a single card, enter the dspcd command as shown in the following example: mgx8830a.1.PXM.a > dspcd 2 Unknown System Rev: 03.00 MGX8830 Slot Number 2 Redundant Slot: 1 Front Card ---------Inserted Card: PXM1E-4-155 Reserved Card: PXM1E-4-155 State: Active Serial Number: S1234567890 Prim SW Rev: 3.0(0.26)P4 Sec SW Rev: 3.0(0.
Chapter 9 Switch Operating Procedures Managing Redundant Cards After you enter the command, the switch displays a report similar to the following example: PXM1E_SJ.7.PXM.a > dspred PXM1E_SJ System Rev: 05.00 Dec.
Chapter 9 Switch Operating Procedures Managing Redundant APS Lines The dspcds command should list one card as active and one card as standby. If the cards are not in their proper states, the switchover cannot take place. Step 3 To switch cards, enter the following command after the switch prompt: mgx8830a.1.PXM.a > switchredcd Replace with the card number of the active card, and replace with the card number to which you want to switch control.
Chapter 9 Switch Operating Procedures Managing Redundant APS Lines The following sections describe how to • Prepare for Intercard APS • Display APS line information • Modify APS lines • Switch APS lines • Remove the redundancy between two lines Note An APS connector is required for line redundancy on SRME cards that are installed in MGX 8850 (PXM1E) switches, and for line redundancy on PXM1E-8-155 cards in MGX 8850 (PXM1E) and MGX 8830 switches.
Chapter 9 Switch Operating Procedures Managing Redundant APS Lines The following example shows the results displayed by the dspapsbkplane command when the APS connector is not place: mgx8830a.1.PXM.a > dspapsbkplane Line-ID 1.1 1.2 2.1 2.
Chapter 9 Switch Operating Procedures Managing Redundant APS Lines Line failures are always detected at the receive end of the line. This is where a switchover occurs when a failure is detected. Two different types of switchovers can occur, depending on whether the APS was configured as unidirectional or bidirectional in the cnfapsln command: • When a failure occurs on a line configured for unidirectional switching, the switch changes lines at the receive end only.
Chapter 9 Switch Operating Procedures Managing Redundant APS Lines Table 9-4 cnfapsln Command Parameters (continued) Parameter Description -w Slot number, bay number, and line number of the active line to configure, in the following format: slot.bay.line Example: -w 1.1.1 -dr Determines whether the line is unidirectional or bidirectional. • 1 = Unidirectional. The line switch occurs at the receive end of the line. • 2 = Bidirectional.
Chapter 9 Switch Operating Procedures Managing Redundant APS Lines Table 9-5 switchapsln Command Parameters Parameter Description bay Working bay number to switch. line Working line number to switch. switchOption Method of performing the switchover. The possible methods are as follows: service switch • 1 = Clear previous user switchover requests. Return to working line only if the mode is revertive. • 2 = Lockout of protection.
Chapter 9 Switch Operating Procedures Managing Redundant APS Lines mgx8830a.1.PXM.a > dspapsln 9.1.1 Working Prot. Conf Index Index Arch ------- ----- ---9.1.1 9.1.2 1+1 9.2.1 9.2.
Chapter 9 Switch Operating Procedures Managing Redundant APS Lines Table 9-6 Options for cnfapsln Command (continued) Option Description -dr The direction option, which specifies the communication paths to be switched when a failure occurs. The options are unidirectional or bidirectional. When the unidirectional option is selected, only the affected path, either transmit or receive, is switched. When the bidirectional option is selected, both paths are switched.
Chapter 9 Switch Operating Procedures Managing Redundant APS Lines Removing APS Redundancy Between Two Lines To remove the redundant APS line relationship between two lines, enter the delapsln command as described in the following procedure. Step 1 Establish a configuration session using a user name with GROUP1_GP privileges or higher. Step 2 To remove redundancy between the two lines, enter the following command after the switch prompt: mgx8830a.1.PXM.
Chapter 9 Switch Operating Procedures Managing Redundant APS Lines Step 1 Enter the dsplns command to determine if the line in alarm is an APS line. The dsplns command shows which lines are enabled for APS. mgx8830a.1.PXM.a > dsplns Medium Medium Sonet Line Line Line Frame Line Line Line State Type Lpbk Scramble Coding Type ----- ----- ------------ ------ -------- ------ ------1.1 Up sonetSts12c NoLoop Enable Other ShortSMF 1.2 Up sonetSts12c NoLoop Enable Other ShortSMF 2.
Chapter 9 Switch Operating Procedures Managing the Time of Day Across the Network Using SNTP Step 3 If one or both lines appear to be bad, determine whether the working or protection line is in alarm. Troubleshoot and correct the standby line first. Replace the components along the signal path until the problem is resolved. • If the dspapslns command at either end of the line indicates a front or back card problem, resolve that problem first. (See Table 9-9 to troubleshoot card problems.
Chapter 9 Switch Operating Procedures Managing the Time of Day Across the Network Using SNTP An SNTP server can reside on an active PXM in an MGX and in and SES switch. An SES switch an be an SNTP server, but not an SNTP client. To set synchronized network clocks, you need to perform the following task in order: 1. Set up a primary server for the network client. 2.
Chapter 9 Switch Operating Procedures Managing the Time of Day Across the Network Using SNTP Table 9-11 cnfsntprmtsvr Command Parameters Parameter Description server IP address The IP address of the switch you want to be a remote SNTP server. version The SNTP version you are using. Possible options are 3 and 4. Default: 3 -primary This parameter lets you identify the switch as the primary SNTP server. Type -primary yes to make the primary server.
Chapter 9 Switch Operating Procedures Managing NCDP Clock Sources Table 9-12 Objects Displayed for dspsntp Command (continued) Parameter Description rollback When a client switches over to the secondary server for TOD requests, the rollback timer takes affect and continues polling the primary server for TOD each time the rollback timer expires. The rollback timer continues polling the primary server until it comes back up. Default = 1024 stratum (default) Shows the default stratum level.
Chapter 9 Switch Operating Procedures Managing NCDP Clock Sources Enabling NCDP on a Switch By default, NCDP is disabled on all nodes and all NNI ports. To enable NCDP on a switch, enter the cnfncdp command as follows: M8850_LA.8.PXM.a > cnfncdp [-distributionMode 1|2] [-maxNetworkDiameter diameter] [-hello time] [ -holdtime time] [ -topoChangeTimer time] Note NCDP must be enabled at each switch that will participate in NCDP clock distribution.
Chapter 9 Switch Operating Procedures Managing NCDP Clock Sources Table 9-14 cnfncdpclksrc Command Parameters Parameter Description port-id Port identifier. For clocking ports on MGX 8850 (PXM1E/PXM45) and MGX 8950 switches, the port identifier is 7.35 or 7.36. For clocking ports on MGX 8830 switches, the port identifier is 1.35 or 1.36. For an internal oscillator, the port identifier is 255.255. prs -id Determines the primary reference source.
Chapter 9 Switch Operating Procedures Managing NCDP Clock Sources Table 9-15 describes the cnfncdpport command options. Table 9-15 cnfncdpport Command Parameters Parameter Description portid Port identifier in the format slot:bay.line:ifnum. These parameters are described in Table 9-1. -ncdp Enter -ncdp enable to enable NCDP on the current port. To disable NCDP on the port, enter -ncdp disable.
Chapter 9 Switch Operating Procedures Managing NCDP Clock Sources Ncdp Vc status Network clock vpi Network clock vci Admin cost Service Category PCR SCR MBS : : : : : : : : up 0 34 10 sig 250 150 100 M8850_LA.8.PXM.a > Displaying NCDP Information The following sections describe how to display information about NCDP configuration in your network. Display the Current NCDP Root Clock Enter the dspncdp command to display the current NCDP root clock source on the network. M8850_LA.8.PXM.
Chapter 9 Switch Operating Procedures Managing NCDP Clock Sources Table 9-16 dspncdp Command Objects (continued) Parameter Description Holddown time interval Number of milliseconds the switch waits before it transmits the next configuration PDU. Topology change time interval Time interval for which the topology change detection field in the configuration pdu bit will be set.
Chapter 9 Switch Operating Procedures Managing NCDP Clock Sources Table 9-17 dspncdpclksrc Command Objects Parameter Description Best clock source Describes whether the specified clock source is currently the best clock source in the node. Priority Displays the specified clock source’s priority. Stratum Level Stratum level of the specified clock source. Possible levels are 1, 2E, 2, 3E, 3, 4E, or 4. Primary reference src id Displays the specified clock sources ID.
Chapter 9 Switch Operating Procedures Managing NCDP Clock Sources Table 9-18 dspncdpclksrcs Command Objects (continued) Parameter Description Prs id Primary source ID (prs-id) is either 0 for external or 255 for internal.The internal primary source is the free-running oscillator on the PXM back card. (Even though the syntax line and the CLI help indicates a range, the only choice in the current release is 0 or 255.
Chapter 9 Switch Operating Procedures Managing NCDP Clock Sources U1.8.PXM.a > dspncdpport 6:1.1:1 Network clock mode : disable Ncdp Vc status : down Network clock vpi : 0 Network clock vci : 34 Admin cost : 10 Service Category : sig PCR : 250 SCR : 150 MBS : 100 Table 9-20 describes the objects displayed by the dspncdpport command. Table 9-20 dspncdpport Command Objects Parameter Description Network clock mode Displays whether NCDP is enabled or disabled on each port.
Chapter 9 Switch Operating Procedures Managing Manually Configured Clocks Sources Table 9-21 delncdpclksrc Command Objects Parameter Description portid The format of the PNNI physical port identifier can vary, as follows: • On a PXM45: slot:subslot.port:subport • On a PXM1E for UNI/NNI back card: slot:subslot.port:subport. On the UNI/NNI back card, the subslot is always 2, but the slot depends on the chassis, as follows: – In an MGX 8850 chassis, slot is always the logical slot 7.
Chapter 9 Switch Operating Procedures Managing Manually Configured Clocks Sources mgx8830a.1.PXM.a > dspclksrcs The following example shows a display with neither primary nor secondary clocks configured. This is the default configuration of a switch, which uses the internal clock as the network clock source. Whenever the active clock is listed as null, the switch is using the internal clock. mgx8830a.1.PXM.a > dspclksrcs Primary clock type: null Primary clock source: 0.
Chapter 9 Switch Operating Procedures Managing Manually Configured Clocks Sources Delete Manual Clock Sources Deleting a clock source deletes the definition of the clock source, not the clock source itself. You might want to delete a primary or secondary clock source definition so that you can reassign the clock source to another line. To delete a clock source, use the following procedure. Step 1 Establish a configuration session using a user name with SUPER_GP privileges or higher.
Chapter 9 Switch Operating Procedures Displaying SVCs Displaying SVCs To display active SVCs, use the following procedure. Step 1 Establish a CLI management session at any user access level. Step 2 Enter the following command: mgx8830a.1.PXM.a > dsppncons The following is an example report for the dsppncons command. mgx8830a.1.PXM.a > dsppncons Port VPI VCI CallRef:Flag X-Port VPI VCI CallRef:Flag 9:1.1:1 0 32 1: 0 9:1.2:2 0 36 5: 0 Calling-Addr:47.666666666666666666666666.666666666666.
Chapter 9 Switch Operating Procedures Managing Controllers Table 9-22 Parameters for the addcontroller Command Parameter Description Number that identifies a network controller. The numbers are reserved as follows: • 2 = PNNI • 3 = Label Switch Controller (LSC), also known as Multiprotocol Label Switch Controller (MPLS). This option is not supported on PXM1E cards. Note i Keyword indicating that this controller is internal. Number that identifies a network controller.
Chapter 9 Switch Operating Procedures Viewing an ATM Port Configuration mgx8830a.1.PXM.a > delcontroller Replace with 2 to identify PNNI controller, or 3 to identify an LSC controller. Caution Do not enter the delcontroller command on a card with existing connections. If you do, those connections cannot be recovered until the controller is re-added using the addcontroller command, and the cards or the entire node is reset. Otherwise, ports remain in the provisioning state.
Chapter 9 Switch Operating Procedures Managing PXM1E Partitions Note Resource partitions can be managed on AXSM, FRSM12, MPSM, and PXM1E cards. This section describes how to manage partitions on PXM1E cards. For instructions on managing resource partitions on other types of cards, see the service module documentation listed in Table 1-1. Displaying a PXM1E Resource Partition Configuration To display a list of resource partitions or a resource partition configuration, use the following procedure.
Chapter 9 Switch Operating Procedures Managing PXM1E Partitions Changing a PXM1E Resource Partition Configuration To change the configuration of a resource partition, use the following procedure. Step 1 Establish a configuration session using a user name with GROUP1 privileges or higher. Step 2 To display a list showing the partitions for this card, enter the dspparts command. Note Step 3 You can change a resource partition only when the partition is not in use.
Chapter 9 Switch Operating Procedures Managing PXM1E Partitions Table 9-23 Parameters for the cnfpart Command (continued) Parameter Description egrmaxbw Egress maximum bandwidth. Enter the maximum percentage of the outgoing port bandwidth that you want assigned to the controller. One percent is equal to 0.00001 units. For example, an of 1000000 = 100%. The sum of the maximum egress bandwidth settings for PNNI can exceed 100%, and must be more than the sum of the egrminbw settings.
Chapter 9 Switch Operating Procedures Managing PXM1E Partitions Table 9-23 Parameters for the cnfpart Command (continued) Parameter Description minConns Specifies the guaranteed number of connections. On the PXM1E UNI/NNI, the ranges vary according to the line types, as follows: • For OC3, T3, and E3 lines, the range is 10-27000. • For T1 and E1 lines, the range is 10-13500. On the AXSM series of cards, the range is 10 through the maximum number of connections in the port group.
Chapter 9 Switch Operating Procedures Managing PXM1E Partitions mgx8830a.1.PXM.a > dspcontrollers Step 6 Enter the delcontroller command to delete the controller that corresponds to the resource partition you modified. For example: pop20two.7.PXM.a > delcontroller 3 All Ports and Connections on this controller will be deleted. delcontroller: Do you want to proceed (Yes/No)? y Step 7 To register the resource partition changes, add the deleted controller with the addcontroller command.
Chapter 9 Switch Operating Procedures Removing Static ATM Addresses mgx8830a.1.PXM.a > dnport Step 8 Delete the resource partition by entering the following command: mgx8830a.1.PXM.a > delpart Replace ifnum with the interface number of the port, and replace partitionID with the partition number assigned to the port. Step 9 To verify that the partition is deleted, enter the dspparts command to display a list of partitions for the card.
Chapter 9 Switch Operating Procedures Configuring VPI and VCI Ranges for SVCs and SPVCs Configuring VPI and VCI Ranges for SVCs and SPVCs When you add a partition to a port, you define the minimum and maximum VPIs and VCIs for that port. These VPIs and VCIs become available for all services unless you make additional configuration changes. If this configuration is acceptable for your installation, you can skip this section. You are not required to configure VPI and VCI ranges for SVCs and SPVCs.
Chapter 9 Switch Operating Procedures Managing Path and Connection Traces Table 9-25 Parameters for the cnfpnportrange Command (continued) Parameter Description max-svcc-vci Maximum VCI value for SVCC. Range: 32 to 65535. Default = 65535. min-svpc-vpi Minimum VPI value for SVPC. Range: 1 to 4095. Default = 1. max-svpc-vpi Maximum VPI value for SVPC. Range: 1 to 4095. Default = 4095. Step 5 Enter the following command to bring up the PNNI port you just configured: mgx8830a.1.PXM.
Chapter 9 Switch Operating Procedures Managing Load Sharing Table 9-26 Path and Connection Trace Commands Command Description dsppathtracenode Displays the nodal configuration for the path and connection trace. dsppathtraceport Displays the port configuration for the path and connection trace. dsppathtraceie Displays whether or not TTL 1E is included in the specified port’s configuration.
Chapter 9 Switch Operating Procedures Managing Load Sharing pop20two MGX8850 Load Sharing: Enable Auto Shutdown: Disable Plane Alarm Threshold: 3 System Rev: 02.01 Dec. 07, 2000 18:36:47 GMT Node Alarm: MAJOR The Load Sharing and Auto Shutdown lines fields show the option status as Enable or Disable. The Plane Alarm Threshold line displays a number from 1 to 32. On PXM cards, the maximum number of slots to which each plane can connect is 14.
Chapter 9 Switch Operating Procedures Managing Telnet Access Features Step 4 To verify your configuration change, enter the dspxbarmgmt command. Managing Telnet Access Features The Cisco MGX switches include Telnet client and server software. The Telnet server software allows you to establish CLI management sessions with a switch using a Telnet client. The Telnet client software allows you to log into a switch and then establish a Telnet session with another switch.
Chapter 9 Switch Operating Procedures Managing Telnet Access Features Login: cisco password: The -E option allows you to specify an escape character that takes you back to the previous session. For example, if you have Telnetted from Switch A to Switch B to Switch C, you can use this escape character to return to Switch B. The default escape character is Q. To change this, specify an alternate escape character with the -E option when you start a Telnet session.
Chapter 9 Switch Operating Procedures Managing Telnet Access Features Login: password: mgx8830a.1.PXM.a > -> local IP 172.29.52.56, next hop at 172.29.52.88 -> local IP 172.29.52.88, connected to server at 172.29.52.56 mgx8830b.1.PXM.a > Enabling and Disabling Telnet Access The Cisco MGX switches include a Telnet server that enables easy, insecure access from Telnet client software running on a workstation or on another Cisco MGX switch.
Chapter 9 Switch Operating Procedures Starting and Managing Secure (SSH) Access Sessions Between Switches NODE CONFIGURATION OPTIONS Opt# Value Type ---- -------14 Yes Boolean Description ----------Telnet Access To Node Disabled To test whether Telnet access is disabled, try to establish a session with the switch.
Chapter 9 Switch Operating Procedures Starting and Managing Secure (SSH) Access Sessions Between Switches Further, MGX switches support an ssh client. This client allows the MGX server to connect to any ssh server. Of course, one example of an ssh server is the MGX switch.
Chapter 9 Switch Operating Procedures Starting and Managing Secure (SSH) Access Sessions Between Switches Table 9-28 Command Parameters for ssh (continued) Parameter Description -p The port option specifies the port to connect to at the remote server. The default value for the client and the server is 22. If you change the port number at the remote switch, you must specify the correct port number when entering the ssh command.
Chapter 9 Switch Operating Procedures Managing Remote (TACACS+) Authentication and Authorization PXM1E_SJ.7.PXM.a > ssh 172.29.52.88 cisco@172.29.52.88's password: M8850_LA.8.PXM Returning to the Previous Session After you create a secure session between two switches, enter the bye command or the exit command to close the current session and return to the previous session. The following example shows the switch response to the bye command: M8850_LA.8.PXM.a > bye (session ended) Connection to 172.29.52.
Chapter 9 Switch Operating Procedures Managing Remote (TACACS+) Authentication and Authorization Configuring AAA Servers To configure a Cisco MGX switch for remote TACACS+ authentication and authorization, you must have an IP address for the remote AAA server. For encrypted authentication and authorization, you must also have an encrypted key to apply at the AAA server and at the Cisco MGX switch.
Chapter 9 Switch Operating Procedures Managing Remote (TACACS+) Authentication and Authorization Table 9-29 describes the parameters for this command. Table 9-29 Parameters for cnfaaa-server Command Parameter Description ServerIp This required parameter identifies the IP address of a target AAA server. ServerPort When the target AAA server does not use the default port number for TACACS+ communications, you can use this optional parameter to specify the correct port. The default port number is 49.
Chapter 9 Switch Operating Procedures Managing Remote (TACACS+) Authentication and Authorization After you enter the cnfaaa-server command, the switch prompts you to enter a encryption key. The encryption key is a text string that can contain any combination of letters, numbers, spaces, and characters. This key is required for encrypted communications with the server and must also be entered at the AAA server. To enter an encryption key, respond to the prompts as shown in the following example: M8830_SF.
Chapter 9 Switch Operating Procedures Managing Remote (TACACS+) Authentication and Authorization Configuring the Default Privilege Level The default privilege level applies when the AAA server authenticates a user and no privilege level has been configured for or is available for that user. To set the default privilege level, enter the cnfaaa-priv command using the following format: M8850_LA.7.PXM.
Chapter 9 Switch Operating Procedures Managing Remote (TACACS+) Authentication and Authorization Table 9-30 Keywords for cnfaaa_authen and cnfaaa-author Commands Keyword Description cisco The cisco keyword selects the local database for authentication or authorization and limits access only to the user cisco. Note default User cisco access method is always enabled and is used for authentication and authorization when all other methods fail.
Chapter 9 Switch Operating Procedures Managing Remote (TACACS+) Authentication and Authorization Authentication Methods Authorization Methods Authorization Type Default Privilege Level Prompt Display SSH/FTP Message Type IOS Exclusion List : : : : : : : tacacs+ cisco local cisco group NOUSER_GP acs Inbound ASCII Login WARNING: The newly configured authentication/authorization methods will apply to new session. This configuration has no impact on existing sessions.
Chapter 9 Switch Operating Procedures Managing Remote (TACACS+) Authentication and Authorization Replace the authorType variable with group to select group mode or with command to select command mode. As with the cnfaaa-authen command, you can specify up to three methods (see Table 9-30) for authorization, and the switch will use these methods in the configured order.
Chapter 9 Switch Operating Procedures Managing Remote (TACACS+) Authentication and Authorization Authorization Type Default Privilege Level Prompt Display SSH/FTP Message Type IOS Exclusion List TACACS+ SERVERS: IP Address ---------------172.29.52.111 172.29.52.
Chapter 9 Switch Operating Procedures Managing Remote (TACACS+) Authentication and Authorization Last bad login authen: Last good grp priv: Last bad grp priv: Last failed cmd: local local-database 04/11/2004 19:48:27 (GMT) NONE cisco telnet.01 10.21.98.
Chapter 9 Switch Operating Procedures Verifying PXM Disk Data Avoiding Command Mode Authorization Issues with RPM Cisco Route Processor Module (RPM) cards are router cards that can be installed in Cisco MGX switches. The switch has its own operating system and so does each RPM card installed in the switch. When command mode authorization is enabled, RPM login names, passwords, and commands must be authorized by the AAA server and the RPM operating system, which is IOS.
Chapter 9 Switch Operating Procedures Verifying PXM Disk Data Table 9-31 verifydiskdb check Command Parameters Parameter Description slot Slot number of the card on which you want to run the disk verification task. level Level on verification for the current task. The levels of verification are as follows: 1 = control information 2 = actual data Default = 2 application Number of times the verification utility will pass through the disk if a discrepancy is found.
Chapter 9 Switch Operating Procedures Verifying PXM Disk Data Table 9-32 verifydiskdb status Command Display Note Parameter Description Slot Current slot whose databases on active and standby PXM hard drives are being compared. Databases Number of databases detected for the current slot. Tables Total number of tables detected for all databases for the slot. DB Index Index number of the current database being compared. DB Name Name of the database currently being compared.
Chapter 9 Switch Operating Procedures Verifying PXM Disk Data If no discrepancies are found on a card, the log file contains only the slot number, timestamp of the verification task, and a message stating that no discrepancies were found.
Chapter 9 Switch Operating Procedures Verifying PXM Disk Data If a firmware upgrade did not finish (the commitrev command was not issued on the slot), the display indicates that the verification utility skipped that slot because a REV_CHG is in progress.
Chapter 9 Switch Operating Procedures Configuring a Line Loopback Record: 1791 ActvComdID: 0 StdbyComID: 7 ============================================================= dbInd: 1 - dbName: sm_mib_v21 tblInd: 5 - tblName: mib29 Record: 1792 ActvComdID: 0 StdbyComID: 7 ============================================================= Note The disk verification utility only logs discrepancies. It does not synchronize the differences.
Chapter 9 Switch Operating Procedures Configuring a Line Loopback • Far-end payload loopback- Loopback is similar to FarEnd loopback, except that the payload portion of the data is re-transmitted. Framing is done by the Far end again. • Remote line loopback - Loopback returns the remote data back to the far end. The received data stream is looped back into the transmit path, overriding the data stream created internally by the framer.
Chapter 9 Switch Operating Procedures Managing Bit Error Rate Tests Managing Bit Error Rate Tests BERT commands can help you analyze and resolve problems on a physical interface. To conduct a BERT on a line, a user sends a specified pattern over a line that is configured in loopback mode at the far end. The local end receives the loopback pattern, and the user compares the local end pattern to the original pattern sent from the far end.
Chapter 9 Switch Operating Procedures Managing Bit Error Rate Tests Unknown.7.PXM.a > cnfbert -cbif -pat -lpbk -sbe -cir -en Table 9-34 cnfbert Command Parameters Parameter Description LSMnum Where LSMnum = LSMslot.Line.Port LSMslot = 1-6,9-14,17-22,25-30 Line = 1 - MAX_LINES Port = 1 - MAX_PORTS for Port Test, 0 for Line Test bertPattern Test pattern to be generated.
Chapter 9 Switch Operating Procedures Managing PXM1E and AXSM Card Diagnostics Bit Bit Bit Bit Bit Count Count Received Error Count Error Rate (BER) Counter Overflowed : : : : : 3091031099 3091031099 0 0 6 BERT is in sync. Deleting a Configured Bit Error Rate Test There are two ways to terminate a configured BERT. 1. Enter the delbert command. Replace with the service module interface number in the format slot.line.port.
Chapter 9 Switch Operating Procedures Managing PXM1E and AXSM Card Diagnostics AXSM cards run offline diagnostics in the following areas: • Processor subsystem: NVRAM and BRAM • ASIC tests: Atlas (register test, ingress memory, egress memory) and framer (register test) PXM1E cards run registered offline diagnostics on UI- S3 or UI-S3/B back cards. Both control path and data path must to be tested in order to have complete test coverage on the entire connection path within a card.
Chapter 9 Switch Operating Procedures Managing PXM1E and AXSM Card Diagnostics Example 9-2 Configuring offline diagnostics only In the following example, the user enables online diagnostics for the PXM1E in slot 7. A medium online diagnostics coverage test is scheduled to run every Wednesday at 11:30 (11:30 AM). MGX.7.PXM.
Chapter 9 Switch Operating Procedures Managing PXM1E and AXSM Card Diagnostics Example 9-5 Configuring offline diagnostics only In the following example, the user enables online diagnostics for all cards in the switch. A medium online diagnostics coverage test is scheduled to run every Wednesday at 11:30 (11:30 AM). Unknown.7.PXM.
Chapter 9 Switch Operating Procedures Managing PXM1E and AXSM Card Diagnostics Type to continue, 20 disable disable 21 disable disable 22 disable disable 23 disable disable 24 disable disable 25 disable disable 26 disable disable 27 disable disable 28 disable disable 29 disable disable 30 disable disable 31 disable disable 32 disable disable Q to stop: light 00:00 light 00:00 light 00:00 light 00:00 light 00:00 light 00:00 light 00:00 light 00:00 light 00:00 light 00:00 light 00:00 light 00:00 l
Chapter 9 Switch Operating Procedures Managing PXM1E and AXSM Card Diagnostics 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 ---------------- ---------------- Type to continue, Q to stop: 21 -- -- Enter the dspdiagstat command to display the number of times that the diagnostics has run. The output shows the number of attempts and the number of failures for both offline and online diagnostics. Unknown.7.PXM.
Chapter 9 Switch Operating Procedures Managing PXM1E and AXSM Card Diagnostics Enter the dspdiagstatus command as shown in the following example: Unknown.7.PXM.
Chapter 9 Switch Operating Procedures Managing IMA Table 9-37 cnfatmimagrp Command Parameters Parameter Description -grp The bay number and the IMA group number. • bay: Enter 2 for the lower bay. • grp: 1-16 Note sps ais On the PXM1E, the bay number is always 2. Enable of disable payload scrambling. Default: enabled. • 1 = enable • 2 = disable Enables or disables the alarm indication signal (AIS) mode.
Chapter 9 Switch Operating Procedures Managing IMA Displaying IMA Groups To display general information about all configured IMA groups on the current PXM1E-16-T1E1, AXSM-32-T1E1-E, AUSM/B, or MPSM cards, enter the dspimagrps command, as shown in the following example: Unknown.7.PXM.a > dspimagrps Ima Grp Min Tx Rx Tx Diff NE-IMA FE-IMA IMA Lnks Frm Frm Clk Delay state state Ver Len Len Mode (ms) -------------------------------------------------------------------------------2.
Chapter 9 Switch Operating Procedures Managing IMA Gamma Val Tx OAM Label Rx OAM Label Test Pattern Procedure Status Test Link Test Pattern Stuff Cell Indication (frames) Version Fallback Enabled Auto-Restart Mode Rx IMA ID Expected Auto-Restart Sync State : : : : : : : : : : : 1 1 1 Disabled Unknown 255 1 true disable -1 disable Displaying IMA Links Enter the dspimalnk command to display configuration information for the specified IMA link.
Chapter 9 Switch Operating Procedures Managing IMA Enter the dspimalnks command to ensure that the correct IMA link is deleted. Satire.2.PXM.a > dspimalnks Link Grp Rel NE NE NE Rx Tx Rx Num Num Dly Tx Rx Fail LID LID (ms) State State Status -----------------------------------------------------------------------------2.1 2.1 0 Unusable-Failed Not In Grp LIF Fail 0 255 2.2 2.1 0 Unusable-Failed Not In Grp LIF Fail 0 255 2.4 2.
Chapter 9 Switch Operating Procedures Managing IMA Note A restart will correct the problem in all three of the previously described situations if a different IMA group ID is configured for the near and far ends. If the same IMA group ID is configured at both ends, it is possible that the links in loopback will respond first and the IMA group will not communicate with the far end. Cisco MGX switches allow you to manually restart an IMA group to correct communications problems.
Chapter 9 Switch Operating Procedures Managing IMA Step 4 To display the autorestart feature configuration for a specific IMA group, enter the dspimagrp command as described in the “Displaying the Status of a Single IMA Group” section, which appears earlier in this chapter. For more information on autorestart information in the dspimagrp command display, see “Displaying the IMA Group Autorestart Configuration and State” section, which appears later in this chapter.
Chapter 9 Switch Operating Procedures Managing IMA The Auto-Restart Mode row displays the mode configured with the cnfimagrp command -mode option, which is described in the previous section. The Rx IMA ID Expected row displays the far end ID configured with the cnfimagrp command -rxid option, which is also described in the previous section. The Auto-Restart Sync State row displays one of the following states: • disable—Autorestart is disabled for this IMA group.
C H A P T E R 10 Switch Maintenance Procedures This chapter describes the configuration changes that are needed after a switch has been initialized, started, and configured, and you want to do any of the following tasks: • Manual reset of the PXM • Add cards • Replace cards • Upgrade cards • Decommission a card slot • Decommission an RPM slot Service module and SRM slots must be decommissioned when you want to change the type of card that runs in the slot.
Chapter 10 Switch Maintenance Procedures Adding Cards Adding Cards After the initial installation and configuration of a MGX 8850 (PXM1E/PXM45), Cisco MGX 8850/B, MGX 8830, or Cisco MGX 8830/B switch, you can add additional cards to empty slots in the chassis. When you add a card, as opposed to replacing a card, you must configure the switch to recognize the new card.
Chapter 10 Switch Maintenance Procedures Adding Cards Note This procedure applies to any of the following service modules: AUSM, AXSM, CESM, FRSM, VISM, and VXSM. Step 1 Before installing the hardware, enter the dspcd command to verify that the slot in which you want to add the card is not configured. In the following example, the dspcd report shows that slot 3 is not configured. M8950_DC.7.PXM.a > dspcd 3 M8950_DC System Rev: 05.
Chapter 10 Switch Maintenance Procedures Adding Cards Step 4 When prompted to confirm the command and reset the card, type y and press Return. After you confirm the command, the slot initializes, the runtime firmware loads on the service module card, and the card resets. Be patient. The card reset takes a couple of minutes. While the card is resetting, you can enter the dspcds command to display the status of the service module card.
Chapter 10 Switch Maintenance Procedures Adding Cards Step 1 Before installing the hardware, enter the dspcd command to verify that the slot in which you want to add the card is not configured. In the following example, the dspcd report shows that slot 14 is not configured. pop20one.7.PXM.a > dspcd 14 ERR: The slot specified, has no card configured in it.
Chapter 10 Switch Maintenance Procedures Replacing Cards Replacing Cards The procedures in this section describe how to replace cards with another card of the same type.
Chapter 10 Switch Maintenance Procedures Replacing Cards If one or more cards are replaced, the nativity check identifies which cards are new to the switch chassis and uses the nativity check results to determine which cards hold the valid configuration. This feature can automatically respond to most configuration mismatches, but some mismatches do require a manual response.
Chapter 10 Switch Maintenance Procedures Replacing Cards Table 10-1 Automatic Response to Nativity Checks in Standalone Installations (continued) Event PXM Type Nativity Check Results Response PXM front card and hard disk card are replaced with a set that was configured in another switch. PXM45 Non-native front card and non-native hard disk card. The standalone PXM enters the failed state.
Chapter 10 Switch Maintenance Procedures Replacing Cards 1. The primary PXM slot is Slot 1 on MGX 8830 switches, Slot 7 on MGX 8850 and MGX 8950 switches, and slot 7 on the MGX 8880 Media Gateway. 2. The secondary PXM slot is Slot 2 on MGX 8830 switches, Slot 8 on MGX 8850 and MGX 8950 switches, and slot 8 on the MGX 8880 Media Gateway.
Chapter 10 Switch Maintenance Procedures Replacing Cards • MCC-8-155 STM1 electrical back card—.Supports APS redundancy. • SFP-8-155 optical back card— Supports APS and Y-cable redundancy. Physical interfaces require installation field replaceable units (FRUs). Consider the following information when replacing an existing PXM1E-4-155 card set with a PXM1E-8-155 card set: • The switch must be running software Release 4.0 or later before you can replace a PXM1E-4-155 card with a PXM1E-8-155 card.
Chapter 10 Switch Maintenance Procedures Replacing Cards Gracefully Replacing a Redundant PXM1E-4-155 Card Set with a Redundant PXM1E-8-155 Card Set A graceful upgrade is an upgrade that upgrades hardware or software without interrupting established calls. The following conditions must be met before you can gracefully upgrade to a PXM1E-8-155 card set: • The PXM1E-4-155 is running Release 4.0 or later. • Intercard APS is configured on the PXM1E-4-155 card set you want to replace.
Chapter 10 Switch Maintenance Procedures Replacing Cards Step 7 Remove any Y-cables and straight cables connected to the removed standby PXM1E-4-155 back card. If there are no cables attached to the removed standby PXM1E-4-155 back card, proceed to Step 9. Step 8 Replace SC cables that will be connected to the FRUs in the installed PXM1E-8-155 card with SC-conversion cables. Connect one end of the LC cable to the appropriate FRU on the installed PXM1E-8-155 card.
Chapter 10 Switch Maintenance Procedures Replacing Cards Step 18 Enter the dspcds command and verify that the standby PXM1E-8-155 comes up in the standby-ready state. Step 19 At the active PXM1E-8-155, enter the commithw 1 command to commit the hardware upgrade on the switch. Replace with the slot number for the active PXM1E-8-155 card. In a Cisco MGX 8850 (PXM1E) switch, the parameter can be 7 or 8.
Chapter 10 Switch Maintenance Procedures Replacing Cards Step 8 Replace SC cables that will be connected to the FRUs in the installed PXM1E-8-155 card with appropriate LC cables or SC conversion cables. Note If the LC cable will be linked to an SC cable on the far-end, you will need a cable with and LC connector on one end and SC connector on the other end. If the LC cable will be linked to another LC connector on the far end, you will need a cable with an LC connector on both ends.
Chapter 10 Switch Maintenance Procedures Replacing Cards Figure 10-1 PXM1E-4-155 Back Cards with SC Cable PXM1E-4-155 back card PXM1E-4-155 back card SC SC 93338 SC cable Step 2 After you have installed the first standby SFP-8-155 back card, you need to install the SC conversion cable or cables into the appropriate FRU or FRUS. Connect the LC end of the cable into the proper FRU on the SFP-8-155 card.
Chapter 10 Switch Maintenance Procedures Replacing Cards Figure 10-3 Both SFP-8-155 Back Cards with SC Conversion Cables SFP-8-155 back card SFP-8-155 back card LC LC SC conversion cable SC SC 93340 SC cable If the upgraded SFP-8-155 back cards connect to CPE that is already using LC cables, you still need to use SC conversion cables. Without the SC conversion cables, you can not do a graceful upgrade and traffic will be interrupted.
Chapter 10 Switch Maintenance Procedures Replacing Cards Gracefully upgrade from a Redundant PXM45 Card Set to a Redundant PXM45/C Card Set To gracefully upgrade from a redundant PXM45 card set to a redundant PXM45/C card set, use the following procedure: Step 1 Enter the dspcds command to verify that the current PXM45 card is running Release 4 or later. Step 2 If you are running CWM on your network, ensure that all workstations are running CWM Release 12.
Chapter 10 Switch Maintenance Procedures Replacing Cards After you replace the PXM45 card, enter the dspcd or dsprev command to view the boot software version. If the boot software version is not correct for your switch, upgrade it as described in Appendix A, “Downloading and Installing Software Upgrades.” Note When replacing PXM45 cards with PXM45/C cards, the switch performs the same nativity check described earlier in this chapter.
Chapter 10 Switch Maintenance Procedures Replacing Cards If intracard APS is configured, the card will operate as an AXSM card. To upgrade to the AXSM/B operating mode, you must enter the enableaxsmbaps command at the PXM. Once the AXSM/B starts operating in AXSM/B mode, the card can no longer return to AXSM operating mode.
Chapter 10 Switch Maintenance Procedures Replacing Cards • Replacing Eight-Port T1 and E1 Service Modules with MPSM-8-T1E1 • Replacing Service Modules with a Different Type of Service Module Replacing Service Modules with the Same Type of Service Module If a service module front or back card fails, remove the old card and insert a new card of the same type in the same slot. If the card is a standalone card, all communications are interrupted.
Chapter 10 Switch Maintenance Procedures Replacing Cards Upgrading Standalone Configurations When upgrading a standalone service module to MPSM-8-T1E1, you must upgrade both the software and the hardware. The software configuration and feature licenses remain intact during the upgrade, but all active connections are terminated.
Chapter 10 Switch Maintenance Procedures Replacing Cards Step 7 Insert the MPSM-8-T1E1 card in the slot used in the previous steps. The MPSM-8-T1E1 will cycle through the Boot, Init, and Standby states, and become Active. If the software version specified in the loadrev and runrev commands is already stored in the flash memory on the MPSM, this process is faster than the start up time for the replaced service module.
Chapter 10 Switch Maintenance Procedures Replacing Cards After redundancy has been added to all primary service modules, the redundant configuration is restored and the MPSM-8-T1E1 now serves at the secondary card for all protected cards. To upgrade primary cards to MPSM-8-T1E1, use the procedure in the next section.
Chapter 10 Switch Maintenance Procedures Replacing Cards M8850_SF.7.PXM.a > runrev 13 30.0(0.85)A mpsm one or more card(s) in the logical slot may be reset. runrev: Do you want to proceed (Yes/No)? y After you enter the runrev command, the primary card will reset and the card state, which you can view with the dspcds command, will change to mismatch. The secondary card will become active and take over the run-time operations for the primary card.
Chapter 10 Switch Maintenance Procedures Decommissioning an AXSM Slot Note The SRME/B line configuration parameters (which are used only for bulk distribution) are similar to that of the SRM-3T3, but there are some differences. Replacing a SRM-3T3 with an SRME/B sets all parameters to the defaults assigned to the SRME/B. If this is a redundant configuration, the SRME/B will start up in standby state.
Chapter 10 Switch Maintenance Procedures Decommissioning an AXSM Slot If you want to use a previously configured AXSM slot for a different type of AXSM card, you must first decommission the slot to remove the existing configuration. Otherwise, the switch will attempt to run the old configuration on the new card, and the new card will not operate correctly. Note If you enter the cnfpnportsig command to change default port values, you must run the delpnport command to delete the port from the PXM45.
Chapter 10 Switch Maintenance Procedures Decommissioning an RPM Slot Step 12 Write down the interface number for each port on the card. You need this information to complete the next step. Step 13 Delete all ports by entering the following command for each port: mgx8850a.10.AXSM.a > delport Replace ifnum with the interface number of the port. Step 14 To verify that the ports have been deleted, enter the dspports command.
Chapter 10 Switch Maintenance Procedures Decommissioning an RPM Slot Cisco MGX 8800/8900 Series Software Configuration Guide 10-28 Release 5.1, Part Number OL-6482-01, Rev.
C H A P T E R 11 2 Viewing and Responding to Alarms Cisco MGX switches display alarm information about the switch cards and store this information inside the switch. This chapter describes how to interpret the alarm LEDs on the switch and how to obtain alarm reports through the CLI. Viewing and Responding to Alarms Using Physical Switch Controls All cards have LEDs for viewing alarm status and switches for responding to alarms.
Chapter 11 Viewing and Responding to Alarms Displaying Alarm Reports in the CLI Note The procedures in the following sections can be completed by users at all access levels. Displaying Node Alarms A node alarm report displays a summary report of all alarms on the node. To display node alarms, enter the following command: M8830_CH.1.PXM.a > dspndalms The following example shows the node alarm report display. M8830_CH.1.PXM.
Chapter 11 Viewing and Responding to Alarms Displaying Alarm Reports in the CLI Note PXM1E do not support switching alarms. Therefore, the commands in this section do not apply to MGX 8850 (PXM1E) and MGX 8830 switches. To display a report of all switching alarms, enter the following command: M8850_LA.8.PXM.a > dspswalms The following example is a sample report showing no switching alarms. M8850_LA.8.PXM.a > dspswalms XBAR SWITCHING FABRIC ALARMS SUMMARY Slot No.
Chapter 11 Viewing and Responding to Alarms Displaying Alarm Reports in the CLI The following display is an example xbar alarm report. M8850_LA.8.PXM.a > dspdevalms XBARCORE -pslot * M8850_LA System Rev: 05.00 MGX8850 Slot ---01 02 03 04 05 06 07 08 09 10 11 12 13 14 7/0 ------------------ Apr.
Chapter 11 Viewing and Responding to Alarms Displaying Alarm Reports in the CLI Table 11-1 Crossbar Alarm Troubleshooting Commands (continued) Command Purpose dspxbarerrthresh Displays the thresholds for crossbar errors.
Chapter 11 Viewing and Responding to Alarms Displaying Alarm Reports in the CLI Bottom Bottom Bottom Bottom Bottom Bottom Bottom Bottom Bottom Fan Fan Fan Fan Fan Fan Fan Fan Fan Tray Tray Tray Tray Tray Tray Tray Tray Tray 1 2 3 4 5 6 7 8 9 +5V Input +3.3V Input >= >= >= >= >= >= >= >= >= 2000 2000 2000 2000 2000 2000 2000 2000 2000 4.850^ to 5.150^ 3.200^ to 3.
Chapter 11 Viewing and Responding to Alarms Displaying Alarm Reports in the CLI The next example shows a card alarm report for an MPSM-T3E3-155 card in slot 12: M8830_CH.1.PXM.
Chapter 11 Viewing and Responding to Alarms Displaying Alarm Reports in the CLI Displaying Line Alarms on Service Modules The service modules generate line alarms when a loss of signal (LOS) alarm occurs. Table 11-3 lists commands that you can enter to display information about line alarms on service modules. Table 11-3 Line Alarm Information Commands Alarm Type Description dspalm Display the active alarms associated with a specific line on the current service module.
Chapter 11 Viewing and Responding to Alarms Displaying Alarm Reports in the CLI Enter the dspimalnkalms command to display alarm state information for all IMA links on the current PXM1E-16-T1E1 or AXSM-32-T1E1-E, as shown in the following example. Unknown.7.PXM.a > dspimalnkalms Link Number Alarm State : 2.5 : Lif Fail Enter the dspimalnkalm command to display alarm state information for a specific IMA link. Replace bay with the 2 to specify the lower bay.
Chapter 11 Viewing and Responding to Alarms Displaying Alarm Reports in the CLI To display license information on all cards, enter the dspliccds command as shown in the following example: M8830_CH.1.PXM.a > dspliccds M8830_CH System Rev: 04.09 Mar.
Chapter 11 Viewing and Responding to Alarms Displaying Log File Information Displaying Log File Information Log files record switch events such as operator login and command entry. To view the contents of the current log, enter the following command at the PXM1E or PXM45 switch prompt: mgx8830a.2.PXM.
Chapter 11 Viewing and Responding to Alarms Displaying Log File Information Cisco MGX 8800/8900 Series Software Configuration Guide 11-12 Release 5.1, Part Number OL-6482-01, Rev.
A P P E N D I X A 2 Downloading and Installing Software Upgrades This appendix describes how to locate, download, and install software updates for the switch. Because software updates are stored in the switch file system, this appendix includes a section on browsing the file system.
Appendix A Downloading and Installing Software Upgrades Quickstart Procedures for Software Upgrades When you upgrade the software in a switch, you should refer to the Release Notes for Cisco MGX 8850 (PXM1E/PXM45), Cisco MGX 8950, and Cisco MGX 8830 Switches, Release 5.1.00 and the Release Notes for the Cisco MGX 8880 Media Gateway, Release 5.1.00 for the latest information. Each type of switch card runs boot and runtime software.
Appendix A Downloading and Installing Software Upgrades Quickstart Procedures for Software Upgrades Graceful PXM Boot Upgrades from Releases Prior to Release 3.0.10 When performed properly, graceful upgrades have minimal impact on connections in progress and do not interrupt any established connections. All releases prior to Release 3.0.10 require entry into shellcon mode to complete a PXM boot upgrade. The PXM boot upgrade takes a little more time and a few more commands for these early releases.
Appendix A Downloading and Installing Software Upgrades Quickstart Procedures for Software Upgrades Command Purpose Step 5 sysPxmRemove At the backup boot prompt, enter the sysPxmRemove command: This step prevents the active card from resetting the standby card while you are working with it. Step 6 sysFlashBootBurn “path/filename” Burn the boot code. Remember to enter quotation marks before and after the boot software filename, and specify the complete path.
Appendix A Downloading and Installing Software Upgrades Quickstart Procedures for Software Upgrades Command Purpose Step 10 sysPxmRemove At the backup boot prompt, enter the sysPxmRemove command. This step prevents the active card from resetting the standby card while you are working with it. Step 11 sysFlashBootBurn “path/filename” Burn the boot code. For example, reboot 21 sysFlashBootBurn "C:FW/pxm1e_004.000.000.201_bt.
Appendix A Downloading and Installing Software Upgrades Quickstart Procedures for Software Upgrades This process ensures a smooth transition to the new software and preserves all established calls. During the short period when the roles of the active and standby cards are switched, all calls that are not established are lost. Note Avoid making configuration changes while upgrading PXM software. Configuration changes can be lost when the PXM is reset during the upgrade.
Appendix A Downloading and Installing Software Upgrades Quickstart Procedures for Software Upgrades Non-Graceful PXM Boot Upgrades Non-graceful upgrades disrupt all switch traffic and are usually used in lab installations where the use of standalone cards provides no opportunity for a graceful upgrade. The quickstart procedure provides an overview and quick reference for those who have already performed ungraceful upgrades on the switch.
Appendix A Downloading and Installing Software Upgrades Quickstart Procedures for Software Upgrades Note If you plan to upgrade PXM cards and service modules, upgrade the PXM cards first. Wait until the PXM cards are operating in active and standby modes with the correct software before upgrading service modules. The software version used by the PXM cards should be equal to or later than the version used on the service modules.
Appendix A Downloading and Installing Software Upgrades Quickstart Procedures for Software Upgrades Step 6 Command Purpose loadrev Load the new runtime software on the standby PXM or service module. dspcd Step 7 runrev dspcd Switch over to the standby PXM or service module and load the new runtime software on the new standby (non-upgraded) card.
Appendix A Downloading and Installing Software Upgrades Quickstart Procedures for Software Upgrades Step 1 Command Purpose ftp Copy the boot and runtime files you want to use to the switch. See the “Copying Software Files to the Switch”section, which appears later in this appendix. Step 2 Step 3 Step 4 If the Release Notes for Cisco MGX 8850 (PXM1E/PXM45), Cisco MGX 8950, and Cisco MGX 8830 Switches, Release 5.1.00 or the Release Notes for the Cisco MGX 8880 Media Gateway, Release 5.1.
Appendix A Downloading and Installing Software Upgrades Quickstart Procedures for Software Upgrades Graceful Service Module Boot Software Upgrades When performed properly, graceful upgrades have minimal impact on connections in progress and do not interrupt any established connections. This quickstart procedure applies to all service modules except the RPM family of cards and provides an overview and quick reference for those who have already performed graceful boot software upgrades on the switch.
Appendix A Downloading and Installing Software Upgrades Quickstart Procedures for Software Upgrades Non-Graceful Service Module Boot Software Upgrades Non-graceful upgrades disrupt all switch traffic and are usually used in lab installations where the use of standalone cards provides no opportunity for a graceful upgrade.
Appendix A Downloading and Installing Software Upgrades Quickstart Procedures for Software Upgrades Graceful RPM Boot and Runtime Software Upgrades The RPM cards support graceful boot software upgrades when 1:N redundancy is established in the switch between RPM cards. Boot software is generally upgraded less often than runtime software, so be sure to compare the recommended boot software version with the boot software running on your RPM cards before starting an upgrade.
Appendix A Downloading and Installing Software Upgrades Quickstart Procedures for Software Upgrades Step 9 Command Purpose config terminal Configure the BOOTLDR variable to specify the new boot software. boot bootldr bootflash:filename ^Z show bootvar Step 10 copy bootflash:filename x:filename del bootflash:filename show flash: squeeze flash: Reorganize files in bootflash. The switch always attempts to load the first bootable file in bootflash.
Appendix A Downloading and Installing Software Upgrades Quickstart Procedures for Software Upgrades Step 21 Command Purpose enable password dir x: show flash: copy filename bootflash: dir bootflash: Repeat Steps 5 through 10 to move the upgraded boot software into bootflash.
Appendix A Downloading and Installing Software Upgrades Quickstart Procedures for Software Upgrades Note Step 1 Redundancy must be established before you use this procedure. If redundancy has not been configured between two RPM cards, upgrade each RPM card using the procedure in the “Non-Graceful RPM Boot Software Upgrades” section later in this chapter. To add redundancy to an RPM card, see the “Establishing Redundancy Between RPM Cards” section in Chapter 6, “Preparing RPM Cards for Operation.
Appendix A Downloading and Installing Software Upgrades Quickstart Procedures for Software Upgrades Step 12 Command Purpose enable password dir x: show flash: copy filename bootflash: dir bootflash: Repeat Steps 4 through 9 to move the upgraded boot software into bootflash.
Appendix A Downloading and Installing Software Upgrades Quickstart Procedures for Software Upgrades Step 1 Command Purpose ftp Copy the boot and runtime files you want to use to the switch (C:FW). See the “Copying Software Files to the Switch” section later in this appendix. Step 2 copy Optional: Copy and rename the runtime file to a generic name for easy updates. See the “Upgrading RPM Runtime Software” section later in this chapter.
Appendix A Downloading and Installing Software Upgrades Quickstart Procedures for Software Upgrades Step 15 Command Purpose switchredcd This step makes the upgraded primary card active and resets the secondary RPM-PR card. When the secondary card resets, it loads the upgraded boot software from bootflash. Both primary and secondary cards should now be using upgraded runtime software.
Appendix A Downloading and Installing Software Upgrades Quickstart Procedures for Software Upgrades Step 8 Command Purpose config terminal Configure the BOOTLDR variable to specify the new boot software. boot bootldr bootflash:filename ^Z show bootvar Step 9 copy bootflash:filename x:filename del bootflash:filename show flash: squeeze flash: Reorganize files in bootflash. The switch always attempts to load the first bootable file in bootflash.
Appendix A Downloading and Installing Software Upgrades Quickstart Procedures for Software Upgrades Step 1 Command Purpose ftp Copy the boot and runtime files you want to use to the switch (C:FW). See the “Copying Software Files to the Switch” section later in this appendix. Step 2 copy Copy and rename the runtime file to a generic name for easy updates. See the “Non-Graceful RPM Runtime Software Upgrades” section later in this chapter.
Appendix A Downloading and Installing Software Upgrades Quickstart Procedures for Software Downgrades Quickstart Procedures for Software Downgrades Cisco Systems, Inc. recommends that you avoid software downgrades, which replace a current software release with another that has a lower version number. However, there are some situations in which you might want to downgrade the software.
Appendix A Downloading and Installing Software Upgrades Quickstart Procedures for Software Downgrades Step 1 Command Purpose username Establish a CLI session with the active PXM card using a user name with SERVICE_GP privileges. password Step 2 saveallcnf Save the current switch configuration. y See the “Saving a Configuration”section in Chapter 9, “Switch Operating Procedures.
Appendix A Downloading and Installing Software Upgrades Browsing the File System Step 1 Command Purpose ftp Copy the boot and runtime files you want to use to the switch. See “Copying Software Files to the Switch,” which appears later in this appendix. Step 2 Refer to “Configuration Quickstart” Chapter 4, “Preparing Service Modules for Communication.” The setrev command in the quickstart procedure clears the card configuration and assigns the downgrade software version to the card.
Appendix A Downloading and Installing Software Upgrades Locating Software Updates Table A-1 File System Commands at Switch Prompt (continued) Command Description pwd Display the present working directory. Syntax: pwd Access level required: ANYUSER or above. rename Renames a file. Syntax: rename Access level required: GROUP1 or above. whoami Lists the login name for the current session. Syntax: whoami Access level required: ANYUSER or above.
Appendix A Downloading and Installing Software Upgrades Upgrade Procedures for PXM Cards and Service Modules Step 1 Refer to the Release Notes for Cisco MGX 8850 (PXM1E/PXM45), Cisco MGX 8950, and Cisco MGX 8830 Switches, Release 5.1.00 or the Release Notes for the Cisco MGX 8880 Media Gateway, Release 5.1.00 to locate a server from which you can download the files.
Appendix A Downloading and Installing Software Upgrades Upgrade Procedures for PXM Cards and Service Modules Step 1 If you have not done so already, establish a CLI session with the PXM card using the CP port on the PXM-UI-S3 or PXM-UI-S3/B back card and a user name with CISCO_GP privileges. Step 2 If you have not done so already, change to PXM Backup Boot mode as described in the “Changing to PXM Backup Boot Mode” section in Appendix B, “PXM Backup Boot Procedures.
Appendix A Downloading and Installing Software Upgrades Upgrade Procedures for PXM Cards and Service Modules Step 7 To confirm that the PXM card is now using the correct boot code, enter the dspcd command. The Boot FW Rev row in the display should show the new revision as shown in the following example: 8850_NY.7.PXM.a > dspcd 8850_NY System Rev: 02.
Appendix A Downloading and Installing Software Upgrades Upgrade Procedures for PXM Cards and Service Modules Caution If the card is removed or reset, or if switch power is interrupted during the boot software upgrade, the upgrade will not complete, the card will not operate, and the card must be returned to Cisco for repair. Replace with the slot number of a standalone PXM card, or a PXM card operating in standby mode.
Appendix A Downloading and Installing Software Upgrades Upgrade Procedures for PXM Cards and Service Modules Step 1 Copy the new boot software files for the service module to the switch as described in the “Copying Software Files to the Switch” section, which appears earlier in this appendix. Step 2 Establish a CLI session with the switch using a user name with SERVICE_GP privileges or higher. Step 3 To burn the new service module boot code, enter the burnboot command as follows: pop20one.7.PXM.
Appendix A Downloading and Installing Software Upgrades Upgrade Procedures for PXM Cards and Service Modules Loading the Runtime Upgrade Software This section describes how to load the runtime upgrade software in preparation for running it. Production switches should have redundant cards installed, so that upgrades can occur without interrupting traffic.
Appendix A Downloading and Installing Software Upgrades Upgrade Procedures for PXM Cards and Service Modules Table A-2 Software Versions Reported During Graceful Upgrades Upgrade Status Before Upgrade After loadrev After runrev MGX 8850, MGX 8880, MGX 8950 Slot 7 Slot 8 Slot 7 Slot 8 Slot 7 Slot 8 Slot 7 Slot 8 MGX 8830 Slot 1 Slot 2 Slot 1 Slot2 Slot 1 Slot 2 Slot 1 Slot 2 Slot State Active Standby Active Standby Standby Active Active Standby Primary software version 3.
Appendix A Downloading and Installing Software Upgrades Upgrade Procedures for PXM Cards and Service Modules Step 3 Note To verify that the load command was processed correctly, enter the dspcd command and check the status of the software revision levels. You can also view the revision levels with the dsprevs command. In a standalone configuration, the switch does not start the upgraded software until the runrev command is entered.
Appendix A Downloading and Installing Software Upgrades Upgrade Procedures for PXM Cards and Service Modules Keep the following in mind when you use the abortrev command to abort the new runtime software during an upgrade: Caution • If you enter the abortrev command on a redundant card set after the loadrev command was entered, and while the cards are in the Loadrev Done-U state, only the standby card will be reset.
Appendix A Downloading and Installing Software Upgrades Upgrade Procedures for RPM-PR and RPM-XF Cards Once you are sure that an upgrade is stable, you can use the commitrev command commit to that software version. Committing to the current software version prevents other administrators from inadvertently reverting to the previous version. You must also commit to the current software version before you can upgrade to another software version.
Appendix A Downloading and Installing Software Upgrades Upgrade Procedures for RPM-PR and RPM-XF Cards The boot software is stored in bootflash memory on the RPM card. To manage the software in bootflash, you access it as if it were a hard disk. For example, in copy and delete file commands, files are identified as bootflash:filename (which is similar to x:filename).
Appendix A Downloading and Installing Software Upgrades Upgrade Procedures for RPM-PR and RPM-XF Cards If you do need to upgrade the boot software, you can copy the new boot file to the PXM disk, and then copy it to the bootflash. The following procedure describes how to upgrade the boot software. Step 1 Tip Copy the new boot software file for the RPM card to the switch (C:FW) as described in the “Copying Software Files to the Switch” section earlier in this appendix.
Appendix A Downloading and Installing Software Upgrades Upgrade Procedures for RPM-PR and RPM-XF Cards 0 0 0 0 0 0 0 0 0 0 0 0 -rw-rw-rw-rw-rw-rw-rw-rw-rw-rw-rw-rw- 2490064 3674368 838840 742168 297988 264592 3111904 744600 3267520 248686 4135448 4135000 May May May May May May May May May May May May 11 11 11 11 11 11 11 11 11 11 11 11 2004 2004 2004 2004 2004 2004 2004 2004 2004 2004 2004 2004 15:37:14 15:36:54 15:36:46 15:36:44 15:46:40 15:46:26 15:36:38 15:36:32 15:36:22 15:32:56 15:32:52 15:32
Appendix A Downloading and Installing Software Upgrades Upgrade Procedures for RPM-PR and RPM-XF Cards Step 10 To reorganize the bootflash so that the new boot software is loaded first when the BOOTLDR variable is not set, complete the following steps: a. Because all files that precede the new boot image in bootflash have to be deleted, copy bootflash files you want to save to the PXM hard disk using the following command. Router#copy b.
Appendix A Downloading and Installing Software Upgrades Upgrade Procedures for RPM-PR and RPM-XF Cards Tip If the bootflash contains bootable images and the sequence is such that the card will not start, you can enter rommon mode and load the bootable image. To get into rommon mode, establish a console connection to the RPM card, reset the RPM card using the resetcd command from the active PXM card, then quickly enter the CTRL-[, Break sequence at the RPM console.
Appendix A Downloading and Installing Software Upgrades Upgrade Procedures for RPM-PR and RPM-XF Cards To configure the RPM to load upgraded runtime software from the PXM hard disk, you need to do the following: • Copy the upgraded file to the PXM hard disk • Update the boot system variable in the router startup-config file to load the new file. • Reset the RPM card so that it loads the new file. RPM cards can be configured for 1:N redundancy as well as for non-redundant configurations.
Appendix A Downloading and Installing Software Upgrades Upgrade Procedures for RPM-PR and RPM-XF Cards Note Step 6 This procedure assumes that you are familiar with Cisco IOS commands (which are a topic that is beyond the scope of this book). This procedure details only those commands that are unique to setting up RPM on the switch. For general Cisco IOS commands, examples are given to show how to complete the task. Enter Enable mode for the router.
Appendix A Downloading and Installing Software Upgrades Upgrade Procedures for RPM-PR and RPM-XF Cards Step 12 To verify the change, enter the show bootvar or show run commands. Step 13 Switch to the active PXM card and reset the RPM card. For example: Router#cc 8 (session redirected) 8850_LA.8.PXM.a > resetcd 9 The card in slot number 9, will be reset.
Appendix A Downloading and Installing Software Upgrades Upgrade Procedures for RPM-PR and RPM-XF Cards Step 2 If you are using a generic filename for your runtime images, copy the file on the PXM hard disk and rename the copy. For example: 8850_LA.8.PXM.a > copy rpm-js-mz_122-4.T rpm-js-mz Step 3 Establish a configuration session using any valid user name. Step 4 If your RPM is already configured to use a file with a generic name, skip to Step 13.
Appendix A Downloading and Installing Software Upgrades Troubleshooting Upgrade Problems Replace the filename variable with the name of the new runtime file that was previously transferred to the C:FW directory on the switch. For example: Router(config)# boot system x:rpm-js-mz If you want to enter additional boot system commands, enter them in the order in which you want the RPM card to use them.
Appendix A Downloading and Installing Software Upgrades Troubleshooting Upgrade Problems Table A-4 Troubleshooting Upgrade Problems Primary Symptom Secondary Symptom Suggested Action loadrev or runrev command fails — The loadrev command is blocked when a previous upgrade has not been completed with the commitrev command. Enter the dsprevs command to locate the cards that are still being upgraded.
Appendix A Downloading and Installing Software Upgrades Troubleshooting Upgrade Problems Table A-4 Troubleshooting Upgrade Problems (continued) Primary Symptom Secondary Symptom Suggested Action Standby PXM continually reboots. — The active PXM card cannot bring up the standby card. The following procedure assumes that this card has just been installed in the switch and that you have given the standby card sufficient time to synchronize with the Active card.
Appendix A Downloading and Installing Software Upgrades Troubleshooting Upgrade Problems Cisco MGX 8800/8900 Series Software Configuration Guide A-48 Release 5.1, Part Number OL-6482-01, Rev.
A P P E N D I X B 2 PXM Backup Boot Procedures When a PXM card starts up, it first loads the boot software on the card. If the PXM cannot load the runtime firmware, the card continues to run the boot software in what is called backup boot mode. The backup boot prompt is as follows: • pxm1ebkup> for PXM1E • pxm45bkup> for PXM45 Some switch procedures, such as PXM card initialization and boot software upgrades, must be performed in backup boot mode.
Appendix B PXM Backup Boot Procedures Browsing the File System in Backup Boot Mode Step 3 At the shell prompt, enter the sysBackupBoot command pxm1e> sysBackupBoot Note This command and all commands that you enter in shell mode are case sensitive. The PXM card reboots after you enter this command. Tip If you are accessing the CP port through a terminal server, rebooting the PXM may disrupt your connection. Random characters may appear on the display or the display may appear to “hang.
Appendix B PXM Backup Boot Procedures Browsing the File System in Backup Boot Mode Table B-1 File System Commands at Backup Boot Prompt Command Description cd Change directories. Syntax: cd “” Example: cd “C:FW” copy Copies a file from one location to another. Syntax: copy “”, “” Example: copy “C:FW/pxm1e_002.001.000.000_bt.fw”, “C:FW/test” remove Deletes a file.
Appendix B PXM Backup Boot Procedures Locating Software Updates Locating Software Updates For information on locating software updates, refer to the Release Notes for Cisco MGX 8850 (PXM1E/PXM45), Cisco MGX 8950, and Cisco MGX 8830 Switches, Release 5.1.00 and the Release Notes for the Cisco MGX 8880 Media Gateway, Release 5.1.00.
Appendix B PXM Backup Boot Procedures Clearing the Switch Configuration Clearing the Switch Configuration To clear the entire switch configuration, use the sysClrallcnf command. This command clears all the provisioning data and most of the general switch configuration parameters, such as the switch name and SNMP configuration.
Appendix B PXM Backup Boot Procedures Initializing the PXM Hard Disk Note The switch prompt might initially display the letter i for initialization. Press Return to display an updated switch prompt or enter the dspcds command several times until the switch prompt or the dspcds command display shows the card is operating in standby mode. The card must complete initialization before entering standby mode. Cisco MGX 8800/8900 Series Software Configuration Guide B-6 Release 5.
A P P E N D I X C 2 Supporting and Using Additional CLI Access Options The command line interface (CLI) management tool allows you to configure the MGX switches and display the switch status. When a switch starts up for the first time, the only CLI access available is through the console port (CP).
Appendix C Supporting and Using Additional CLI Access Options Setting Up CP Port Connections Setting Up CP Port Connections The Console Port (CP) connection requires no configuration on the switch. Figure C-1 shows the hardware required for a console port connection to a PXM-UI-S3 back card.
Appendix C Supporting and Using Additional CLI Access Options Setting Up CP Port Connections Figure C-2 shows the hardware required for a console port connection to a PXM-UI-S3/B back card. Figure C-2 Workstation Connection to Console Port on a PXM-UI-S3/B Back Card PXM-UI-S3/B back card PXM UI-S3/B C P P2 P1 S P Serial cable L A N 1 L A N 2 E X T C L K 1 Workstation E X T C L K 2 89880 A L A R M The terminal you use should emulate a VT-100 terminal.
Appendix C Supporting and Using Additional CLI Access Options Setting Up Terminal Server Connections Setting Up Terminal Server Connections A terminal server connection allows remote access to the CP port. Figure C-3 shows the hardware required for a terminal server connection.
Appendix C Supporting and Using Additional CLI Access Options Setting Up Terminal Server Connections Figure C-4 shows the hardware required for a terminal server connection.
Appendix C Supporting and Using Additional CLI Access Options Setting Up Local LAN Connections Setting Up Local LAN Connections The procedure for setting up local LAN connections is described in Chapter 2, “Configuring General Switch Features” in the following sections: • “Setting the Boot IP Address” • “Setting the Disk IP Address” Setting Up Dial-Up Connections A dial-up connection extends switch management to all workstations that have access to the Public Switched Telephone Network.
Appendix C Supporting and Using Additional CLI Access Options Setting Up Dial-Up Connections Figure C-6 Hardware Required for Dial-up Connections on a PXM-UI-S3/B Back Card PXM-UI-S3/B back card Modem PXM UI-S3/B C P P2 P1 S P L A N 1 L A N 2 Modem E X T C L K 1 E X T C L K 2 A L A R M 116355 Workstation Before you can manage the switch using the dial-up interface, you must first assign an IP address to the maintenance port on the switch.
Appendix C Supporting and Using Additional CLI Access Options Setting Up Dial-Up Connections Tip Cisco recommends that you use the same subnet for all IP addresses defined on all MGX 8850 switches. This simplifies router configuration. Note There are other options for the ipifconfig command, and you can set one or more options simultaneously. Any options you do not define in a command remain unchanged.
Appendix C Supporting and Using Additional CLI Access Options Setting Up Dial-Up Connections Step 4 Note Use a subnet mask that is different from the network mask used for LAN port communications. If you use the same subnet for both ATM and LAN port communications, there will be two entries for the same subnet in the routing table and all egress IP communications will take place through the atm0 port.
Appendix C Supporting and Using Additional CLI Access Options Setting Up Dial-Up Connections The following example shows commands that you can use to configure a Cisco Cisco MGX 8850 (PXM1E/PXM45) or Cisco MGX 8830 for IP communications over ATM. Example C-1 Switch Commands for IP Communications over ATM mgx8850a.7.PXM.a> ipifconfig atm0 A.B.E.F # Replace A.B.E.F with IP Address mgx8850a.7.PXM.a> svcifconfig atm0 local 47.0091.8100.0000.0010.7b65.f258.0010.7b65.1111.01 mgx8850a.7.PXM.
Appendix C Supporting and Using Additional CLI Access Options Starting a CLI Management Session Using a CP Port or Terminal Server Connection To configure the IP interface to the LAN, you need to do the following: • If the router IP address for the ATM interface is not on the same subnet as the IP address on the switch ATM interface, you must manually configure on IP host-route for each MGX switch to which the interface will connect.
Appendix C Supporting and Using Additional CLI Access Options Starting a CLI Telnet Session The following example shows the commands that accomplish this on a Cisco 2509-RJ Router. User Access Verification Password: router>telnet 10.1.1.1 2001 Trying 10.1.1.1, 2001 ... Open Login: In the example above, the user first logs into the terminal server and then establishes a Telnet session to the terminal server using port 2001.
Appendix C Supporting and Using Additional CLI Access Options Starting a Secure (SSH) CLI Session After the appropriate interface has been configured and a physical path established to the MGX switch, you can start a CLI session using a workstation with a Telnet client program and the switch IP address. To establish a CLI management session, use the following procedure. Step 1 If you are dialing into the switch, establish a dial-up connection to the switch.
Appendix C Supporting and Using Additional CLI Access Options Starting a Secure (SSH) CLI Session Tip • Support for RSA (SSHv1) and DSA (SSHv2) key authentication algorithms • Support for AES, 3DES, and Blowfish encryption methods • Support for hmac-sha1 and hmac-md5 hashing methods • SSH server support for accessing MGX CLI • SSH client support for accessing remote SSH servers For instructions on establishing a secure session between switches, see “Starting and Managing Secure (SSH) Access Se
Appendix C Supporting and Using Additional CLI Access Options Ending a CLI Management Session When you have successfully established a secure CLI session, the SSH client will display information similar to the following: SSH Secure Shell 3.2.0 (Build 267) Copyright (c) 2000-2002 SSH Communications Security Corp - http://www.ssh.com/ This copy of SSH Secure Shell is a commercial version licensed to Cisco IT, Cisco Systems. PXM1E_SJ.7.PXM.a > Step 3 If the switch prompt does not appear, press Enter.
Appendix C Supporting and Using Additional CLI Access Options Ending a CLI Management Session Cisco MGX 8800/8900 Series Software Configuration Guide C-16 Release 5.1, Part Number OL-6482-01, Rev.
A P P E N D I X D Standards Compliance This appendix lists the relevant technical and compliance specifications for Release 5.1 of the , Cisco MGX 8850 (PXM1E/PXM45), Cisco MGX 8850/B, Cisco MGX 8950, Cisco MGX 8830, and Cisco MGX 8830/B switches, and the Cisco MGX 8880 Media Gateway in the following sections: Note • PNNI Compliance • ATM Signaling Compliance • Processor Switching Module Specifications • UNI 4.0 • AINI 3.0 and 3.
Appendix D Standards Compliance ATM Signaling Compliance ATM Signaling Compliance The following ATM Forum signaling specifications are supported: Note • UNI 3.0/3.1 Signaling • IISP Signaling • PNNI Signaling • ATM Signaling Interworking ITU recommendations for B-ISDN DSS2 signaling is not currently supported. UNI 3.0/3.1 Signaling UNI 3.x signaling is supported. Table D-1 UNI 3.x Signaling Capability Reference Network Equipment Mandatory/Optional Support Point-to-Point calls 5.
Appendix D Standards Compliance ATM Signaling Compliance PNNI Signaling PNNI signaling is supported. Table D-2 PNNI Signaling Capability Reference Network Equipment Mandatory//Optional Support Point-to-Point calls 6.5.2 M x Associated signaling 6.5.2.2.1 O x Non-associated signaling 6.5.2.2.2 O x ATM Parameter Negotiation 6.5.2.3.4 O — QoS Parameter Selection 6.5.2.3.5 O x ABR Signaling 6.5.2.3.6 O x Switched Virtual Path 6.5.2.2.2.2 O x Crankback 8.
Appendix D Standards Compliance ATM Signaling Compliance ATM Signaling Interworking Interworking between all combinations of signaling protocol is supported at all interfaces types: UNI to UNI, UNI to NNI and NNI to NNI. Table D-4 ATM Signaling Interworking Protocol UNI 3.0 UNI 3.1 UNI 4.0 IISP 1.0 PNNI 1.0 AINI UNI 3.0/3.1 x x x x x x UNI 4.0 x x x x x x IISP 1.0 x x x x x x PNNI 1.0 x x x x x x AINI 3.0 x x x x x x AINI 3.
A P P E N D I X E Hardware Survey and Software Configuration Worksheets The worksheets in this chapter serve as a place to record the hardware installed in your switch and the configuration planning decisions you make as you plan your software configuration. Instructions for filling out the Hardware Survey worksheets appear in the “Verifying the Hardware Configuration” section of Chapter 2, “Configuring General Switch Features.
Appendix E Hardware Survey and Software Configuration Worksheets Hardware Survey Worksheets Note The hardware survey worksheets do not contain all the information you need to configure the switch. Use the hardware survey worksheets to identify the hardware and validate the hardware installation. Use the software configuration worksheets in this chapter to plan the configuration for each card. You can validate the hardware first, or complete your configuration plan first.
Appendix E Hardware Survey and Software Configuration Worksheets Hardware Survey Worksheets Table E-2 Slot Cisco MGX 8850 (PXM1E/PXM45) or Cisco 8850/B Hardware Survey Worksheet Reserved For Front Card Type Upper Back Card Lower Back Card Redundant Slot Redundancy Type 1 2 3 4 5 6 7 PXM 8 Primary 8 PXM 7 Secondary 15 SRM 16 Primary 16 SRM 15 Secondary 9 10 11 12 13 14 17 18 19 20 21 22 23 PXM — — — — — 24 PXM — — — — — 25 26 27 28 29 30 31 SRM 32 Primary 32 SRM
Appendix E Hardware Survey and Software Configuration Worksheets Hardware Survey Worksheets Table E-3 Slot Cisco MGX 8950 Hardware Survey Worksheet Reserved For Front Card Type Upper Back Card Lower Back Card Redundant Slot Redundancy Type 1 2 3 4 5 6 7 PXM 8 Primary 8 PXM 7 Secondary 9 XM-60 — — — — 10 XM-60 — — — — 11 12 13 14 15 16 17 18 19 20 21 22 23 PXM — — — — — 24 PXM — — — — — 25 XM-60 — — — — 26 XM-60 — — — — 27 28 29 30 31 32 Cisco MGX 88
Appendix E Hardware Survey and Software Configuration Worksheets General MGX Switch Configuration Worksheet (PXM45, PXM1E, and SRM) General MGX Switch Configuration Worksheet (PXM45, PXM1E, and SRM) Table E-4 lists general switch parameters you can configure in each new switch.
Appendix E Hardware Survey and Software Configuration Worksheets General MGX Switch Configuration Worksheet (PXM45, PXM1E, and SRM) Table E-4 General Switch Configuration Parameters (continued) Feature Parameter Information Value to Configure User cisco Password User service Password User superuser Password Additional user User name Password Access level Additional user User name Password Access level Additional user User name Password Access level Network Clock Source Plan Manual clock c
Appendix E Hardware Survey and Software Configuration Worksheets Additional PXM1E Information Configuration Worksheet Table E-4 General Switch Configuration Parameters (continued) Feature Parameter Information Value to Configure Time zone Enter a zone Time zone offset Hours to offset PXM and SRM1 Redundancy Options Standalone configuration Primary or secondary card set installed? Upper bay SRM SRM-3T3 or SRME? Bulk distribution? Lower bay SRM SRM-3T3 or SRME? Bulk distribution? Redundant confi
Appendix E Hardware Survey and Software Configuration Worksheets Additional PXM1E Information Configuration Worksheet Table E-5 Additional PXM1E Card Configuration Parameters (continued) Feature Line 1 Redundancy Options Parameter Information Value to Configure Working index2 slot.2.1 Protection index2 slot.2.2 1 Intracard APS Mode 3 Working index4 Intercard APS Protection index Mode Line 2 Redundancy Options slot.2.1 5 slot.2.
Appendix E Hardware Survey and Software Configuration Worksheets Additional PXM1E Information Configuration Worksheet Table E-5 Additional PXM1E Card Configuration Parameters (continued) Parameter Information Feature Line 6 Redundancy Options Value to Configure 1 Intracard APS Configured while configuring line 5 Intercard APS Working index4 Protection index Mode Line 7 Redundancy Options Working index2 Protection index Mode Intercard APS slot.2.7 2 slot.2.8 3 Working index4 slot.2.
Appendix E Hardware Survey and Software Configuration Worksheets Additional PXM1E Information Configuration Worksheet Table E-5 Additional PXM1E Card Configuration Parameters (continued) Feature Line 11 Redundancy Options Parameter Information Value to Configure Working index2 slot.2.11 Protection index2 slot.2.12 1 Intracard APS Mode 3 Working index4 Intercard APS Protection index Mode Line 12 Redundancy Options slot.2.11 5 slot.2.
Appendix E Hardware Survey and Software Configuration Worksheets AUSM/B Configuration Worksheet AUSM/B Configuration Worksheet Table E-6 lists general switch parameters you will need to configure on each AUSM/B card. Note AUSM/B cards operate only on MGX 8850 (PXM1E) and Cisco MGX 8830 switches.
Appendix E Hardware Survey and Software Configuration Worksheets AXSM Configuration Worksheet AXSM Configuration Worksheet Table E-7 lists general switch parameters you will need to configure on each AXSM card. Note AXSM cards operate only on MGX 8850 (PXM45) and Cisco MGX 8950 switches, and on the Cisco MGX 8880 Media Gateway. AXSM-E cards operate on Cisco MGX 8850/B and Cisco MGX 8830/B. The Cisco MGX 8800/8900 Series Hardware Installation Guide, Releases 2 - 5.
Appendix E Hardware Survey and Software Configuration Worksheets CESM Configuration Worksheet CESM Configuration Worksheet Table E-8 lists general switch parameters you will need to configure on each CESM card. Note CESM cards do not operate in Cisco MGX 8950 switches. If you are configuring a Cisco MGX 8950 switch, or if you do not have CESM cards installed in your switch, you do not need to complete the worksheet in Table E-8.
Appendix E Hardware Survey and Software Configuration Worksheets FRSM-12-T3E3 Configuration Worksheet FRSM-12-T3E3 Configuration Worksheet Table E-9 lists general switch parameters you will need to configure on each FRSM-12-T3E3 card. Note FRSM12 cards operate only on MGX 8850 (PXM45) switches. If you are configuring a MGX 8850 (PXM1E), Cisco MGX 8830, or Cisco MGX 8950 switch, or if you do not have FRSM12 cards installed in your switch, you do not need to complete the worksheet in Table E-9.
Appendix E Hardware Survey and Software Configuration Worksheets FRSM-2CT3, FRSM-2T3E3, and FRSM-HS2/B Configuration Worksheet FRSM-2CT3, FRSM-2T3E3, and FRSM-HS2/B Configuration Worksheet Table E-11 lists general switch parameters you will need to configure the FRSM-2CT3, FRSM-2T3E3, and FRSM-HS2/B cards.
Appendix E Hardware Survey and Software Configuration Worksheets FRSM-8T1 and FRSM-8E1 Configuration Worksheet FRSM-8T1 and FRSM-8E1 Configuration Worksheet Table E-11 lists general switch parameters you will need to configure channelized and non-channelized 8-port FRSM cards. Note If you are configuring a Cisco MGX 8950 switch, or if you do not have 8-port FRSM cards installed in your switch, you do not need to complete the worksheet in Table E-11.
Appendix E Hardware Survey and Software Configuration Worksheets MPSM-8-T1E1 Configuration Worksheet MPSM-8-T1E1 Configuration Worksheet Table E-12 lists general switch parameters you will need to configure channelized and non-channelized 8-port MPSM cards. Note If you are configuring a Cisco MGX 8880 Media Gateway or a Cisco MGX 8950 switch, or if you do not have 8-port MPSM cards installed in your switch, you do not need to complete the worksheet in Table E-12.
Appendix E Hardware Survey and Software Configuration Worksheets MPSM-T3E3-155 Configuration Worksheet MPSM-T3E3-155 Configuration Worksheet Table E-13 lists general switch parameters you will need to configure on each MPSM-T3E3-155 card.
Appendix E Hardware Survey and Software Configuration Worksheets MPSM-16-T1E1 Configuration Worksheet MPSM-16-T1E1 Configuration Worksheet Table E-14 lists general switch parameters you will need to configure on each MPSM-16-T1E1 card.
Appendix E Hardware Survey and Software Configuration Worksheets VISM Configuration Worksheet VISM Configuration Worksheet Table E-15 lists general switch parameters you will need to configure on each VISM card. Note VISM cards do not operate in Cisco MGX 8950 switches. If you are configuring a Cisco MGX 8950 switch, or if you do not have VISM cards installed in your switch, you do not need to complete the worksheet in Table E-15.
Appendix E Hardware Survey and Software Configuration Worksheets VXSM Configuration Worksheet VXSM Configuration Worksheet Table E-16 lists general switch parameters you will need to configure on each VXSM card. Note VXSM cards operate only on MGX 8850 (PXM45) and Cisco MGX 8950 switches. If you are configuring a MGX 8850 (PXM1E) or Cisco MGX 8830 switch, or if you do not have VXSM cards installed in your switch, you do not need to fill out Table E-16.
Appendix E Hardware Survey and Software Configuration Worksheets VXSM Configuration Worksheet Cisco MGX 8800/8900 Series Software Configuration Guide E-22 Release 5.1, Part Number OL-6482-01, Rev.
A P P E N D I X F MPSM Licensing MPSM Licensing Information The multiprotocol service module (MPSM) family of cards includes MPSM-T3E3-155, MPSM-16-T1E1, and MPSM-8-T1E1 service modules. With proper licensing, these cards can provide multiple services or features. The MPSM provides these services and features with the same hardware and same runtime firmware image using License Management. License Management is a software component that grants and enforces the use of licensed services.
Appendix F MPSM Licensing MPSM Licensing Information • You need to have MPSM licenses that are in an alarm state rekeyed. Note You can purchase MGX systems, spares, and MPSM licenses from www.cisco.com, specifically, http://www.cisco.com/order/apollo/configureHome.html. Tip Licensed services are new for MGX switches. Although available licenses are summarized in Table F-1, please read this whole appendix to become familiar with the terms and processes used for MPSM licensing.
Appendix F MPSM Licensing MPSM Licensing Information Table F-1 Available Licensed Services for MPSM Cards (continued) Name of Licensed Service Product ID of Licensed Service for... MPSM-8-T1E1 Point-to-Point — Protocol (PPP) MPSM-T3E3-155 MPSM-16-T1E1 Description — MPSM-PPP-HS-LIC(=) Point-to-Point Protocol (PPP). This includes PPP Multiplexing (PPPMux) and Multilink PPP (MLPPP) features. One license of this type is required by a licensable service module.
Appendix F MPSM Licensing MPSM Licensing Information These licenses can be installed in the PXM license pool. In a shelf, there may be different MPSM cards that can support the licensed services and features. Licenses for one type of card cannot be used on another type of card. For the MPSM-T3E3-155 or MPSM-16-T1E1 cards, if no license is allocated to the service module, only the default single service functionality is available on that service module.
Appendix F MPSM Licensing MPSM Licensing Information Table F-3 MPSM License Concepts and Terms (continued) Concept or Term Description Spare License A license managed by the PXM but not needed by MPSM at a given time. This is the same as an “Available” license. Transfer Authorization Key (TAK) An encrypted key generated by the License Keycutter when the customer requests transferring licenses from one node to another. This key is then used on the source MGX node to initiate the transfer.
Appendix F MPSM Licensing MPSM Licensing Information PXM License Pool Figure F-1 illustrates the license pool and the types of items that are stored in it. Figure F-1 The Switch License Pool Licenses stored on MPSM cards Encrypted keys Switch License Pool MPSM card features Transferred licenses 111441 License files The switch license pool serves as a depository for all licenses installed on a switch.
Appendix F MPSM Licensing MPSM Licensing Information Displaying License Data Display commands allow you to view node license data, card license data, or license history data. The following sections describe ways to view the license data. Displaying All Node Licenses To display all node licenses, enter the dsplics command as follows: M8830_CH.1.PXM.a > dsplics M8830_CH MGX8830 Node License Alarm Licensed Card Type ----------------MPSM-T3E3-155 System Rev: 04.
Appendix F MPSM Licensing MPSM Licensing Information Displaying the License Usage for All Cards Note Redundant cards require the same licenses as the primary cards they protect. For 1:N redundancy, a redundant card needs one of each type of licence used by the primary cards it protects. The dspliccds command displays the total licenses allocated or programmed on all cards. The dspliccds command is a non-privileged command and is available on the PXM45 and PXM1E cards.
Appendix F MPSM Licensing MPSM Licensing Information 6 9 10 11 12 13 ... ... ... MPSM-T3E3-155 -MPSM-8T1E1 MPSM-8T1E1 MPSM-8T1E1 MPSM-16T1E1 RateControl --RateControl -RateControl -- N/A -No N/A Yes N/A 1 --1 0 1 0 Displaying the License Usage for a Specific Card To display the license usage for a single card within a switch, enter the dspliccd command on either the PXM or the MPSM. The following example shows how the display appears when the command is run from a PXM card: M8830_CH.11.PXM.
Appendix F MPSM Licensing MPSM Licensing Information In the next example, the dspliccd command is run from an MPSM card, so you do not have to enter the slot number: M8830_CH.12.MPSM155[FR].
Appendix F MPSM Licensing MPSM Licensing Information 5 6 7 0 0 0 0 0 0 0 0 0 || || || 12 13 14 0 0 0 0 0 0 0 0 0 Adding Licenses Purchased from Cisco.com Purchased licenses are delivered in the form of an encrypted key, which appear within an E-mail message or within a text file attached to an E-mail. When ordering additional licenses, you must provide the output generated by the command dsplicnodeid on the switch that will host the licenses.
Appendix F MPSM Licensing MPSM Licensing Information Step 5 To install a license using a license file, FTP that file to the C:/LICENSE directory on the destination switch. Enter the cnflic command using the following syntax: M8850_SF.7.PXM.a > cnflic -f filename Replace filename with the name of the file provided by Cisco.com as shown in the following example: M8850_SF.7.PXM.a > cnflic -f Lmpsmoc3_20040615113118099.
Appendix F MPSM Licensing MPSM Licensing Information Caution Step 8 To avoid losing licenses during a configuration restoration, save the switch configuration after installing the new licenses by using the saveallcnf command. Enter the saveallcnf command. Moving Licenses from an MPSM Card to the Switch To move programmed licenses from an MPSM card to the switch license pool, use the cc command to move to the CLI prompt for the MPSM card. Then enter the movelic command as follows: M8250_SJ.1.22.MPSM8T1.
Appendix F MPSM Licensing MPSM Licensing Information Recovering Feature Licenses That are Not In Use Feature licenses are automatically returned to the license pool when the card configuration no longer requires them. The following actions can be used to remove the configuration for featured licenses: • Use the CLI commands to remove the feature configuration.
Appendix F MPSM Licensing MPSM Licensing Information NodeID=SCA062300GF:000001:004:009:015 Step 3 To display the switch serial number used for licensing on the destination switch, enter the dsplicnodeid command. M8850_SF.7.PXM.a > dsplicnodeid NodeID=SCA062300GF:000001:004:009:020 Step 4 To request a transfer license from Cisco.com, go to the URL specified in the URL in the “MPSM License Overview” section on page F-1.
Appendix F MPSM Licensing MPSM Licensing Information This step also generates a new license key and a new license file, which can be used to install the removed licenses on the destination switch. The license key appears in the command output. The license file is stored in the C:/LICENSE directory. Note Step 6 Go to Step 7. To apply the transfer license using the key in the license file attached to the E-mail from Cisco.
Appendix F MPSM Licensing MPSM Licensing Information Step 7 To install the new license(s) on the destination switch using the key displayed on the source switch, copy the key and enter the cnflic command with the key generated from the source switch: M8850_SF.7.PXM.
Appendix F MPSM Licensing MPSM Licensing Information Caution To avoid losing licenses during a configuration restoration, save the switch configuration at the source and destination switches by using the saveallcnf command. MPSM License Alarms MPSM feature license alarms can occur at the node level or the slot level of the switch.
Appendix F MPSM Licensing MPSM Licensing Information Slot License Alarms Slot license alarms are raised under the following conditions: • When a node license alarm is raised, all cards that are using feature licenses go into the slot license alarm state. Slot license alarms raised under this condition can be cleared by rekeying the PXM license pool. For the procedure to rekey feature licenses, see “Rekeying Feature Licenses”.
Appendix F MPSM Licensing MPSM Licensing Information ========================================================= Programmed License Type Quantity --------------------------RateControl 1 ========================================================= Programmed License Registered: Yes License Registeration Node: M8850_SF License Registeration Chassis Serial No: SCA062300GF M8850_SF.8.PXM.a > On PXM1E and PXM45 platforms, the dspcd command will indicate if a card is in slot license alarm.
Appendix F MPSM Licensing MPSM Licensing Information Service Module Serial Number: SAG07208RRA Provisioning (addcon) Allowed: YES ========================================================= Needed License Type Needed Licenses --------------------------------RateControl 1 ========================================================= Allocated License Type Allocated licenses --------------------------------------RateControl 1 ========================================================= Programmed License Type Progra
Appendix F MPSM Licensing MPSM Licensing Information The following procedure describes how to obtain and install a rekey license: Step 1 Log in to the node. Step 2 To display the node ID used for licensing, enter the dsplicnodeid command as follows: M8850_SF.8.PXM.a > dsplicnodeid NodeID=SCA062300GF:000006:005:000:004 To generate a rekey license, contact Cisco TAC and provide the output collected in Step 2.
Appendix F MPSM Licensing MPSM Licensing Information Please confirm the above licence information. cnflic:Do you want to proceed (Yes/No)? y M8850_SF.8.PXM.a > Step 5 To verify that the feature licenses have been rekeyed, enter the dspndalms command as follows: M8850_SF.8.PXM.a > dspndalms Node Alarm Summary Alarm Type ---------Clock Alarms Switching Alarms Environment Alarms Card Alarms Node License Alarm Critical -------0 0 0 0 0 Major ------0 0 0 0 0 Minor ------0 0 0 0 0 M8850_SF.8.PXM.
Appendix F MPSM Licensing MPSM Licensing Information Cisco MGX 8800/8900 Series Software Configuration Guide F-24 Release 5.1, Part Number OL-6482-01, Rev.
A P P E N D I X G Reliability, Availability, and Serviceability Both the PXM45 and the PXM1E support the following reliability, availability, and serviceability (RAS) features: • Power On Self Test (POST) • Hardware Monitoring Module (HMM) • Online diagnostics • Offline diagnostics • Enhanced alarm reporting The POST and HMM features are transparent to the user. However, the dsppostresults command can be used to display the POST results. POSTs are a set of tests that run at boot-up time.
Appendix G Reliability, Availability, and Serviceability Diagnostics Step 7 Display diagnostics results. MGX8850.7.PXM.a>dspdiagresults Table G-1 shows some of the other commands that can be used to isolate and troubleshoot problems. For details about these commands refer to the Cisco MGX 8800/8900 Series Command Reference, Release 5.1.
Appendix G Reliability, Availability, and Serviceability Diagnostics 9 10 11 12 13 14 15 Ethernet Ping QE RAM Access HDsk PCI Access HDsk Rd/Wr CBC RAM Access BRAM checksum Control Path Y Y Y Y Y Y Y 2868 2868 2868 95 2868 2868 28680 0 0 0 0 0 0 0 2868 2868 2868 95 2868 2868 28680 None None None None None None None Pass Pass Pass Pass Pass Pass Pass The following example shows the display output for the dsppostresults command: MGX8850.7.PXM.
Appendix G Reliability, Availability, and Serviceability Diagnostics -------------- ----------- ---------- ----Error Type ------------Rx HW Err DTE ProcErr RAM ERR ------------ ------------- Total Errors -------- ------0 0 0 The following example shows the display output for the dspdeverrhist command: MGX8850.7.PXM.a>dspdeverrhist QE1210 PXM System Rev: 04.00 Dec.
Appendix G Reliability, Availability, and Serviceability Diagnostics PXM1E Diagnostics Tests The following tests are valid on the PXM1E.
Appendix G Reliability, Availability, and Serviceability Diagnostics • CBC RAM • Ethernet Register • PCI/IDE Register Access • Clock Mux Validation • Hard Disk Access PXM45 Path Tests • Utopia Loopback • Path Test • Crossbar test • Device Tests • QE RAM Access • CBC RAM Access • Flash Checksum • HDD R/W • HDD PCI Access • Trap Frequency Monitor • Ethernet Ping • BRAM checksum • Memory Access Cisco MGX 8800/8900 Series Software Configuration Guide G-6 Release 5.
INDEX addlmi command Symbols 3-18, 3-20 addlnloop command ? command 2-13 9-78 addnwnode command addpart command 3-4, 3-6, 3-11, 3-13, 3-14, 3-16, 3-18, 3-48 addparty command A 8-13, 8-19 3-81 addpnni-node command addpnni-summary-addr command AAA server configuring switch access to server configuration abortrev command 9-63 9-11, A-34 ANYUSER 2-17 2-18 3-4, 3-6, 3-10, 3-11, 3-13, 3-14, 3-16, 3-18, 3-20, 3-44, 7-14 addpref command 8-14 addprfx command 3-6, 3-64 addred command 4-2, 4-
Index displaying switching alarms software upgrades 11-2 ANYUSER access privileges testing loopback lines 2-17 APS AXSM-E SCTs connector, displaying A-2 AXSM SCTs 9-19 9-77 7-3 7-2 intercard configuration 3-41 AXSM slot, decommissioning intracard configuration 3-39 AXSM software files backup boot access lines configuring AXSM-XG SCTs 9-20 displaying 9-23 modifying 9-24 removing redundancy switching between troubleshooting preparing for B-4 7-3 B 9-26 9-22 backup boot 9-26,
Index bye command See CISCO_GP 2-10, 9-57, 9-62, C-15 class of service buffer CLI C connections C:CNF C:FW CP port setup B-4 MP port setup B-4 C-6 C-6 terminal server setup 7-1 C-4 ending Telnet session cards displaying card alarms introduction 11-6 displaying redundancy status managing redundancy card SCT 9-17 clidbxlevel command C-12, C-13 2-13 clock alarms, displaying 11-2 clock ports 2-7 PXM45 UI-S3 caution symbol, defined C-bit checking 2-41 C-13 starting Telnet session
Index cnfaaa-priv command cnfaaa-prompt command 9-66 cnfaaa-server command cnfabr command 9-63 3-76 cnfabrtparmdft command cnfaddrcug cnfncdpport command 9-66 3-76, 7-6 cnfaddrreg command 3-6, 3-57, 3-64 cnfaisdelaytimer command cnfatmimagrp command 9-87 3-62 9-79, 9-81 cnfcdmode command cnfcdsct command 3-3, 3-21, 4-2, 4-7 4-2, 4-11 cnfclkparms command cnfclksrc command 2-33 2-3, 3-66, 9-41, 9-42 8-13 cnfndparms command 9-58 cnfndrteopt command 8-33, 8-40, 8-41 cnfoamsegep comma
Index cnftrapip command core switch topology 2-43 cnftrk command (on IGX) cnfuser command 3-91 command entry guidelines C-2 CUG 9-55 getting runtime help 7-1 CP port connection setup 2-2, 2-19 cnfxbarmgmt command COSB 1-8 2-12 2-10 command line interface See CLI creating 8-53 deleting 8-59 explicit 8-53 implicit 8-53 managing commithw command 10-14 preferential commitrev command 9-11, A-35 selection complex node CUG IE 8-5 config terminal command 8-53 8-60 CWM 6-10
Index delprfx command DSL 9-11 1-11 delred command 9-18 DSLAM delsct command 7-11 dspaaa command delsntprmtsvr command deltopolink command deluser command deroute delay dspaaa-stats command dspaddr command 8-69 G-1 9-81, 9-82, 9-83, 9-84, 9-85, 9-86 on PXM1E cards 9-81, 9-82, 9-83, 9-84, 9-85, 9-86 11-8 dspalmcnt command 11-8 Digital Subscriber Line Access Multiplexers See DSLAM dspalms command 11-7, 11-8 dspapsbkplane command dspapslns command 3-3, 3-42, 5-12, 9-20, 9-23, 9-27, 9-2
Index dspdiagerr online command dspdiagstat command 9-86 dspenvalms command 11-11 9-33, 9-36 dspncdpclksrcs command dspncdp command 11-5 9-34, 9-38 dspncdpports command 11-7 9-37 2-35, 9-35 dspncdpport command 11-7 dspfdrs command dsplogs command dspncdpclksrc command 9-86 dspdiagstatus command dspfdr command 9-85 9-38 dspHwAlms command 11-7 dspndalms command dspilmiaddr command 3-64 dspndconnpribump command dspilmicnt command dspilmi command 9-10 9-8 dspilmis command 3-5, 3-7
Index dsppnport command 3-4, 3-6, 3-11, 3-12, 3-13, 3-14, 3-16, 3-18, 3-19, 3-20, 3-55, 3-62 dsppnportie command 8-45, 8-60 dsppnportpribumprsrc command dsppnportrange command 9-53 3-4, 3-6, 3-11, 3-12, 3-13, 3-14, 3-16, 3-18, 3-19, 3-20, 3-51, 9-9, 11-7 3-4, 3-6, 3-11, 3-12, 3-13, 3-14, 3-16, dsppnsysaddr command 8-47, C-9 3-4, 3-46, 9-45 dspports command 3-4, 3-5, 3-6, 3-7, 3-10, 3-11, 3-13, 3-14, 3-16, 3-18, 3-20, 3-43, 3-46, 4-10, 7-14, 11-7 dspportsct abr command 7-15 dspportsct bw comma
Index trunk 3-1 H filenames, case sensitive A-24, B-2 hardware configuration worksheet file system help command backup boot browsing commands 2-11 backup boot B-2 B-2 runtime operation B-3 E-2, E-3, E-4 2-12 runtime browsing A-24 commands I A-24 File Transfer Protocol IGX feeder See FTP configuring firmware deleting See software 3-89 3-90 IISP first fit PNNI routing link configuration 8-10 FRSM (CBSM) card link introduction supported interfaces 1-5 FRSM-12-T3E3 SCTs
Index interface addresses Load Sharing assigning address prefixes interface number 8-52 Interim Inter-Switch Protocol 8-54 intracard APS 3-39 IP address log files backup boot access 3-44 interlock code 9-54 3-2 directory 11-11 displaying information log out, automatic 11-11 2-8, 2-9 loopback 1-16 configuring IP addressing address plan B-4 testing 1-16 IP Address Plan, creating 1-16 ipifconfig atm0 command C-8 ipifconfig command ipifconfig lnPci0 command ipifconfig sl0 command
Index allocating feature licenses concepts and terms general information network clock sources changing F-2 deleting F-3 1-21 management F-1 F-11 restoring recovering licenses F-14 viewing rekeying feature licenses transferring licenses 9-28 9-42 9-28, 9-40 network management F-21 saving and restoring licenses 2-30 9-42 guidelines F-13 purchasing licenses services 9-41 configuring BITS sources F-6 managing licenses overview See NCDP F-18 moving licenses 9-35 Network Clock Di
Index deleting a party PGL priority configuration 3-89 displaying a party 3-88 obtaining an NSAP for a party rerouting a party 3-83 8-7, 8-50 route selection 8-10 service category-based token and AW 3-87, 3-88 partition timers See resource partitions trunk changing for other users changing your own 8-6 ports 2-20 ATM 9-54 selecting the signaling protocol PCR viewing configuration 7-17 peer group 3-51 9-45 PNNI creating upper levels ID configuration configuring port range 8-2
Index privileges, users lines and cards 2-16 prompt PXMbkup switch PVC 2-6 2-7, 2-9 3-8 pwd command runtime software downgrades A-22 software upgrades A-2 SPVCs and SPVPs 3-8 3-7 R PXM1E card configuring loopback lines supported interfaces 9-77 1-5 testing loopback lines verifying disk data RAS See reliability, availability, and serviceability 9-77 9-72 RcvFEACValidation reboot command 7-4 adding standby cards 10-2 redundancy 3-26 2-2, 2-6, A-27, B-5 displaying status 9-16 o
Index restoreallcnf command deleting unregistered SCTs 9-1, 9-6 restoring, configuration 9-5 revertive function, BITS clock RM 2-34 7-16 rommon mode A-40 RPM-PR card displaying a card SCT 7-13 displaying a port SCT 7-13 displaying card SCT settings 7-14 displaying port SCT settings 7-14 displaying registered SCTs booting from a TFTP server downloading A-40 6-1 filename conventions configuring redundancy 6-9 general SCT parameters introduction 6-10 dspcd command display dspcds c
Index setcugdefaddr command runtime 8-55 A-25 seteng command 2-13 determining versions from filenames setrev command 4-2, 4-4, 9-11, 10-3 downloading and installing updates sh command filename format for released firmware 10-9 shmFailRecoveryHelp command locating updates 10-9 shmRecoverIgRbldDisk command 10-9 show bootflash show flash command standards A-36, A-38 6-10 show inventory command 1-13 show run command SPVC A-26, B-4 4-5 D-4 2-17, 3-1 configuring slave side double-en
Index starting a session ssh command sysFlashBootBurn command 9-60, C-13 sysPxmRemove command 9-60 standards A-27 A-4, A-5, B-2 system addresses, displaying compliance SONET addresses D-1 displaying system addresses D-4 standby card state 2-7, 2-14 sysVersionSet command startup-config file A-40 sysVersionShow command 8-47 2-2, 2-6 A-46 static ATM addresses adding 3-57 removing T 9-51 summary address, display 2-29 Table SUPER_GP TACACS+ access privileges 2-17 9-62 Telnet d
Index AINI link configuration verifydiskdb display command 3-14 BPX PNNI trunk configuration bringing up 3-12 version file 3-22, 5-4 configuration verifydiskdb status command 3-25, 3-26, 3-27, 5-5 IISP link configuration MPLS configuration 3-15, 3-19 3-1 PNNI configuration 3-1 See also lines version levels, software determining from filenames managing 3-22, 4-3 verifying 4-5 XLMI link 9-11 5-14 virtual tributary group 3-27 9-73 A-46 virtual tributary viewing configuration 9-74
