Cisco MGX 8850 (PXM1E/PXM45), Cisco MGX 8950, Cisco MGX 8830, and Cisco MGX 8880 Configuration Guide Release 5 August 16, 2004 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-3845-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 Documentation xxix Documentation Notes for the April 2004 Product Releases xxix Related Documentation xxx Technical Manual Order of Use xxx Technical Manual Titles and Descriptions xxxi Obtaining Documentation xliii Cisco.
Contents Unique Device Identifier 1-15 MIB Field Names for UDI 1-16 Administrator Access Method 1-16 Network Clock Source Plan 1-16 Network Management Plan 1-16 Physical Location of Cards and Lines in the Switch Guidelines for Creating an IP Address Plan 1-17 1-17 Guidelines for Creating a Network Clock Source Plan 1-19 Planning for Manual Clock Synchronization 1-19 Planning for NCDP Synchronization 1-22 CHA PTER 2 Configuring General Switch Features Configuration Quickstart Initializing the Switch
Contents 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 Configuring the SNMP Manager Destination IP Address 2-43 Configuring the Community String and General Switch Information Verifying the Hardware Configurati
Contents Configuring Intracard APS Lines 3-40 Configuring Intercard APS Lines 3-42 Adding ATM Ports 3-44 Modifying ATM Ports 3-47 Partitioning Port Resources Between Controllers 3-48 Selecting the Port Signaling Protocol 3-52 Defining Destination Addresses for Static Links 3-56 Assigning Static ATM Addresses to Destination Ports 3-58 Configuring ILMI on a Port 3-60 Configuring ILMI Traps and Signaling 3-60 Configuring ILMI Automatic Configuration 3-62 Configuring ILMI Dynamic Addressing 3-63 Starting ILMI
Contents 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 Selecting MPSM Interfaces and Services 4-3 4-3 4-6 Establishing Redundancy Between Two Service Modules CHA PTER 5 Selecting a Card SCT 4-9 Selecting a Port SCT 4-11 Preparing SRM Cards for Communications 4-8 5-1 Configuration Quickstart for Bulk Distribution on SRMs Configured for SONET/SDH 5-2 Configuratio
Contents Downloading SCT Files to the Switch 7-6 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 Port 7-14 Selecting a Port SCT 7-14 Changing a Port SCT 7-14 Displaying Port SCT Settings 7-15 Port SCT ABR Parameters (
Contents Configuring Link Selection for Parallel Links 8-20 Configuring the Maximum Bandwidth for a Link 8-20 Configuring the Administrative Weight 8-21 Configuring the Aggregation Token 8-21 Configuring the Bandwidth Overbooking Factor 8-22 Configuring the Deroute Delay 8-23 Improving and Managing Rerouting Performance 8-24 Pure PXM45/C Networks 8-24 Hybrid Networks with PXM45/C and PXM45/B 8-24 Pure PXM45/B Networks Running Version 3.0.
Contents Displaying System Addresses 8-50 Displaying PNNI Interface Parameters 8-51 Displaying the PNNI Link Table 8-52 Displaying the PNNI Routing Policy 8-53 Displaying the SVCC RCC Timer 8-54 Displaying Routing Policy Parameters 8-55 Displaying the SVCC RCC Table 8-55 Managing CUGs 8-56 Assigning Address Prefixes and AESAs 8-56 Creating Closed User Groups 8-57 Displaying CUG Configuration Data 8-59 Setting a Default Address for CUG Validation 8-59 Deleting a Default CUG Address 8-60 Managing Access Betw
Contents Displaying Software Revisions in Use 9-15 Displaying Software Revisions for a Single Card 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 Between Redundant RPM Cards 9-18 Managing Redundant APS Lines 9-18 Preparing for Intercard APS 9-19 Configuring Intercard APS Lines 9-20 Displaying APS Line Information 9-23 Modifying APS Lines 9-
Contents Adding Controllers 9-44 Deleting a Controller 9-45 Viewing an ATM Port Configuration 9-45 Managing PXM1E Partitions 9-46 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 Managing Path and Connection Traces 9-54 Displaying Path and Connection Traces 9-54 Clearing a Call at the Destination Node 9-54 Man
Contents Verifying PXM Disk Data 9-73 Displaying the Contents of the Disk Verification Utility Log File 9-75 Troubleshooting Active and Standby Card Disk Discrepancies 9-78 Configuring a Line Loopback 9-79 Configuring Loopback Line Tests on PXM1E and AXSM Cards Configuring a Line Loopback on a Service Module 9-80 Managing Bit Error Rate Tests 9-80 Configuring a Bit Error Rate Test 9-80 Deleting a Configured Bit Error Rate Test 9-79 9-83 Managing PXM1E and AXSM Card Diagnostics 9-83 Configuring Offline a
Contents Replacing PXM1E-4-155 Cards with PXM1E-8-155 Cards 10-10 Replacing PXM1E SC Cables with LC Cables via SC Conversion Cables 10-15 Replacing PXM45/A or PXM45/B Cards with PXM45/C Cards 10-17 Gracefully upgrade from a Redundant PXM45 Card Set to a Redundant PXM45/C Card Set 10-17 Non-gracefully Upgrade a Single PXM45 to a PXM45/C 10-18 Replacing AXSM Cards with AXSM/B Cards 10-18 Upgrading a Standalone AXSM 10-18 Upgrading an AXSM in a Redundant Card Set 10-19 Replacing Service Modules 10-20 Replacin
Contents Graceful Service Module Boot Software Upgrades A-11 Non-Graceful Service Module Boot Software Upgrades A-12 Graceful RPM Boot and Runtime Software Upgrades A-13 Graceful RPM Boot Software Upgrades A-15 Graceful RPM Runtime Software Upgrades A-17 Non-Graceful RPM Boot Software Upgrades A-19 Non-Graceful RPM Runtime Software Upgrades A-20 Quickstart Procedures for Software Downgrades A-22 PXM and AXSM Boot Downgrades A-22 Non-Graceful PXM Runtime Software Downgrades A-22 Non-Graceful AXSM Runtime So
Contents APPENDIX 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 CLI Telnet Session C-12 Starting a Secure (SSH) CLI Session Ending a CLI Management Session APPENDIX D Standards Compliance PN
Contents APPENDIX F MPSM Licensing 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-7 Displaying Licenses for All Cards F-8 Displaying the License Usage for a Specific Card F-9 Displaying a History of License Updates F-10 Displaying License Alarms F-11 Adding Licenses Purchased
Contents xviii Cisco MGX 8850 (PXM1E/PXM45), Cisco MGX 8950, Cisco MGX 8830, and Cisco MGX 8880 Configuration Guide Release 5.0.10, OL-3845-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 PXM1E UI-S3/B Back Card Figure C-5 Hardware Required for Dial-up Connection to a PXM45 UI-S3 Back Cards Figure C-6 Hardware Required for Dial-up Connections on a PXM1E UI-S3/B Back Card Figure F-1 The Switch License Pool xx C-5 C-6 C-7 F-6 Cisco MGX 8850 (PXM1E/PXM45), Cisco MGX 8950, Cisco MGX 8830, and Cisco MGX 8880 Configuration Guide Release 5.0.10, OL-3845-01 Rev.
T A B L E S Table 1 Technical Manuals and Release Notes for Cisco MGX and BPX Switches and Media Gateways (April 2004 Product Releases) xxxii Table 2 Documents that Ship with Multiservice Switch Products Table 3 Descriptions of Technical Manuals and Release Notes for Cisco Multiservice Switch Products Table 4 Changes to This Book Since the Previous Release Table 1-1 Card-specific Configuration Guides Table 1-2 Cisco MGX 8830, Cisco MGX 8850 (PXM1E/PXM45), Cisco MGX 8880, and Cisco MGX 8950 Capab
Tables Table 3-14 ATM Address Configuration Parameters 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 Command Displays Table 5-1 Parameters for SONET Line Configurati
Tables 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-38 Table 8-12 Supported Grooming Thresholds 8-39 Table 8-13 Grooming Metric Selection Table 8-14 Parameters for cnfrteoptthresh Command Table 8-15 Parameters for cnfndrte
Tables 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 Table 9-26 Path and Connection Trace Commands
Tables Table D-4 ATM Signaling Interworking Table E-1 Cisco MGX 8830 Hardware Survey Worksheet Table E-2 Cisco MGX 8850 (PXM1E/PXM45) Hardware Survey Worksheet Table E-3 Cisco MGX 8950 Hardware Survey Worksheet Table E-4 General Switch Configuration Parameters Table E-5 Additional PXM1E Card Configuration Parameters Table E-6 General AUSM/B Configuration Parameters Table E-7 General AXSM, AXSM-E, and AXSM-XG Card Configuration Parameters Table E-8 General CESM Configuration Parameters Tab
Tables xxvi Cisco MGX 8850 (PXM1E/PXM45), Cisco MGX 8950, Cisco MGX 8830, and Cisco MGX 8880 Configuration Guide Release 5.0.10, OL-3845-01 Rev.
About This Guide This preface describes the objectives, audience, organization, and conventions of the Cisco MGX 8850 (PXM1E/PXM45), Cisco MGX 8950, Cisco MGX 8830, and Cisco MGX 8880 Configuration Guide. Objectives This guide describes how to configure the Cisco MGX 8830, Cisco MGX 8850 (PXM1E/PXM45), and Cisco MGX 8950 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 Documentation Caution Tips Warning Means reader be careful. In this situation, you might do something that could result in equipment damage or loss of data. 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.
About This Guide Documentation Related Documentation This section describes the technical manuals and release notes that support the April 2004 release of Cisco Multiservice Switch products. 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.
About This Guide Documentation Step 8 Additional books, such as command reference guides and error message books, can help with the daily operation and maintenance of your switch. Note Manual titles may be different for earlier software releases. The titles shown in Table 1 are for the April 2004 release. Technical Manual Titles and Descriptions Table 1 lists the technical manuals and release notes that support the April 2004 multiservice switch product releases.
About This Guide Documentation Table 1 Technical Manuals and Release Notes for Cisco MGX and BPX Switches and Media Gateways (April 2004 Product Releases) Document Title and Part Number MGX MGX BPX with SES 8230 Rel. 8250 Rel. 1.3 1.3 Rel. 4 MGX 8850 (PXM1) Rel. 1.3 MGX 8830 Rel. 5 MGX 8850 (PXM1E) Rel. 5 MGX 8850 (PXM45) Rel. 5 MGX 8950 Rel. 5 MGX 8880 Rel. 5.
About This Guide Documentation Table 1 Technical Manuals and Release Notes for Cisco MGX and BPX Switches and Media Gateways (April 2004 Product Releases) (continued) Document Title and Part Number MGX MGX BPX with SES 8230 Rel. 8250 Rel. 1.3 1.3 Rel. 4 — Release Notes for Cisco MGX Route Processor Module (RPM-XF) IOS Release 12.3(2)T5 for PXM45-based Switches, Release 5.0.00 MGX 8850 (PXM1) Rel. 1.3 MGX 8830 Rel. 5 MGX 8850 (PXM1E) Rel. 5 MGX 8850 (PXM45) Rel. 5 MGX 8950 Rel. 5 MGX 8880 Rel. 5.
About This Guide Documentation Table 1 Technical Manuals and Release Notes for Cisco MGX and BPX Switches and Media Gateways (April 2004 Product Releases) (continued) MGX MGX BPX with SES 8230 Rel. 8250 Rel. 1.3 1.3 Rel. 4 MGX 8850 (PXM1) Rel. 1.3 MGX 8830 Rel. 5 MGX 8850 (PXM1E) Rel. 5 MGX 8850 (PXM45) Rel. 5 MGX 8950 Rel. 5 MGX 8880 Rel. 5.
About This Guide Documentation Table 1 Technical Manuals and Release Notes for Cisco MGX and BPX Switches and Media Gateways (April 2004 Product Releases) (continued) Document Title and Part Number MGX MGX BPX with SES 8230 Rel. 8250 Rel. 1.3 1.3 Rel. 4 MGX 8850 (PXM1) Rel. 1.3 MGX 8830 Rel. 5 MGX 8850 (PXM1E) Rel. 5 MGX 8850 (PXM45) Rel. 5 MGX 8950 Rel. 5 MGX 8880 Rel. 5.
About This Guide Documentation Table 1 Technical Manuals and Release Notes for Cisco MGX and BPX Switches and Media Gateways (April 2004 Product Releases) (continued) MGX MGX BPX with SES 8230 Rel. 8250 Rel. 1.3 1.3 Rel. 4 MGX 8850 (PXM1) Rel. 1.3 MGX 8830 Rel. 5 MGX 8850 (PXM1E) Rel. 5 MGX 8850 (PXM45) Rel. 5 MGX 8950 Rel. 5 MGX 8880 Rel. 5.
About This Guide Documentation Table 1 Technical Manuals and Release Notes for Cisco MGX and BPX Switches and Media Gateways (April 2004 Product Releases) (continued) Document Title and Part Number Cisco WAN Manager Database Interface Guide, Release 15 MGX MGX BPX with SES 8230 Rel. 8250 Rel. 1.3 1.3 Rel. 4 MGX 8850 (PXM1) Rel. 1.3 MGX 8830 Rel. 5 MGX 8850 (PXM1E) Rel. 5 MGX 8850 (PXM45) Rel. 5 MGX 8950 Rel. 5 MGX 8880 Rel. 5.
About This Guide Documentation Table 2 Documents that Ship with Multiservice Switch Products Document Title Description Guide to Cisco Multiservice Switch and Media Gateway Documentation Describes how to find the manuals and release notes that support multiservice switches and network management products. These documents are available only online. This guide ships with product.
About This Guide Documentation Table 3 Descriptions of Technical Manuals and Release Notes for Cisco Multiservice Switch Products (continued) Document Title Description Cisco MGX 8230 Edge Concentrator Installation and Configuration, Release 1.1.3 Provides installation instructions for the Cisco MGX 8230 edge concentrator. DOC-7811215= Cisco MGX 8230 Edge Concentrator Overview, Release 1.1.3 Describes the system components and function of the Cisco MGX 8250 edge concentrator.
About This Guide Documentation Table 3 Descriptions of Technical Manuals and Release Notes for Cisco Multiservice Switch Products (continued) Document Title Description Cisco MGX 8850 (PXM1E/PXM45), Cisco MGX 8950, Cisco MGX 8830, and Cisco MGX 8880 Hardware Installation Guide, Releases 2 Through 5 Describes how to install the Cisco MGX 8950, the Cisco MGX 8850 (PXM1E/PXM45), and the Cisco MGX 8830 switches. Also describes how to install the MGX 8880 Media Gateway.
About This Guide Documentation Table 3 Descriptions of Technical Manuals and Release Notes for Cisco Multiservice Switch Products (continued) Document Title Description Cisco MGX Route Processor Module (RPM-PR) Installation and Configuration Guide, Release 2.1 Describes how to install and configure the Cisco MGX Route Processor Module (RPM/B or RPM-PR) in the Cisco MGX 8850 (PXM1), the Cisco MGX 8250, and the Cisco MGX 8230 edge concentrators.
About This Guide Documentation Table 3 Descriptions of Technical Manuals and Release Notes for Cisco Multiservice Switch Products (continued) Document Title Description Cisco WAN Manager User’s Guide, Release 15 Describes how to use the CWM Release 15 software, which consists of user applications and tools for network management, connection management, network configuration, statistics collection, and security management.
About This Guide Documentation Obtaining Documentation Cisco provides several ways to obtain documentation, technical assistance, and other technical resources. These sections explain how to obtain technical information from Cisco Systems. Cisco.com You can access the most current Cisco documentation on the World Wide Web at this URL: http://www.cisco.com/univercd/home/home.htm You can access the Cisco website at this URL: http://www.cisco.
About This Guide Documentation Changes to This Document Table 4 summarizes the changes made to this guide since the previous release. Table 4 Changes to This Book Since the Previous Release Chapter Changes Chapter 1, “Preparing for Configuration” Added information about new manuals and features and made minor revisions. Chapter 2, “Configuring General Switch Features” Added coverage for new hardware and made minor revisions.
About This Guide Documentation Table 4 Changes to This Book Since the Previous Release Chapter Changes Chapter 7, “Managing Service Class Templates” This chapter has been completely rewritten. A master table provide guidance for selecting SCTs, and the rest of the chapter describes SCT management and shows display command examples for PXM1E cards. For display command examples for service modules, refer to the appropriate service module guide, all of which are listed in Table 1-1.
About This Guide Obtaining Technical Assistance Table 4 Changes to This Book Since the Previous Release Chapter Changes Appendix D, “Standards Compliance” Minor revisions. Appendix E, “Hardware Survey and Software Configuration Worksheets” Added the following worksheet sections: • MPSM-8-T1E1 Configuration Worksheet • MPSM-T3E3-155 Configuration Worksheet • VXSM Configuration Worksheet Documentation Feedback You can submit e-mail comments about technical documentation to bug-doc@cisco.com.
About This Guide Obtaining Additional Publications and Information Opening a TAC Case Using the online TAC Case Open Tool is the fastest way to open P3 and P4 cases. (P3 and P4 cases are those in which your network is minimally impaired or for which you require product information.) After you describe your situation, the TAC Case Open Tool automatically recommends resources for an immediate solution.
About This Guide Obtaining Additional Publications and Information • Cisco Press publishes a wide range of general networking, training and certification titles. Both new and experienced users will benefit from these publications. For current Cisco Press titles and other information, go to Cisco Press online at this URL: http://www.ciscopress.
C H A P T E R 1 Preparing for Configuration This document provides general configuration information and procedures for the Cisco MGX 8850 (PXM1E/PXM45), Cisco MGX 8950, and Cisco MGX 8830 switches. Use this document after you have installed your switch according to the instructions in the Cisco MGX 8850 (PXM1E/PXM45), Cisco MGX 8950, Cisco MGX 8830, and Cisco MGX 8880 Hardware Installation Guide, Releases 2 Through 5.
Chapter 1 Table 1-1 Preparing for Configuration Card-specific Configuration Guides Service Module Software Configuration Guide Title AUSM/B and MPSM cards Cisco ATM Services (AUSM/MPSM) Configuration Guide and Command Reference for MGX Switches, Release 5 AXSM cards Cisco ATM Services (AXSM) Configuration Guide and Command Reference for MGX Switches, Release 5 CESM and MPSM Cisco Circuit Emulation Services (CESM/MPSM) Configuration Guide and cards Command Reference for MGX Switches, Release 5 FRSM
Chapter 1 Preparing for Configuration Cisco MGX Switch Features Narrow Band Service Modules (NBSMs) in Cisco documentation.) The CBSM term is used to refer to this class of cards as a whole. CBSM cards include the AUSM, CESM, FRSM, 8-port MPSM, RPM, RPM-PR, and VISM card families. Note The AXSM and FRSM-12-T3E3 cards are not CBSMs. They are full-height cards that communicate with the PXM45 and other service modules through the serial bus.
Chapter 1 Preparing for Configuration Cisco MGX Switch Features Table 1-2 Cisco MGX 8830, Cisco MGX 8850 (PXM1E/PXM45), Cisco MGX 8880, and Cisco MGX 8950 Capabilities Cisco MGX 8850 (PXM1E) Cisco MGX 8830 (PXM1E) Cisco MGX 8850 (PXM45) Cisco MGX 8880 (PXM45/C) Cisco MGX 8950 (PXM45) Height 29.75 inches 14 inches 29.75 inches 29.75 inches 29.75 inches Width 17.72 inches 17.72 inches 17.72 inches 17.72 inches 17.72 inches Depth 21.5 inches 21.5 21.5 inches 21.5 inches 21.
Chapter 1 Preparing for Configuration Cisco MGX Switch Features Table 1-2 Cisco MGX 8830, Cisco MGX 8850 (PXM1E/PXM45), Cisco MGX 8880, and Cisco MGX 8950 Capabilities Feature Cisco MGX 8850 (PXM1E) Cisco MGX 8830 (PXM1E) Cisco MGX 8850 (PXM45) Cisco MGX 8880 (PXM45/C) Cisco MGX 8950 (PXM45) AUSM-8E1/B - 8 ports AUSM-8E1/B - 8 ports AXSM-32-T1E1-E AXSM-32-T1E1-E — - 32 ports - 32 ports AUSM-8T1/B - 8 ports AUSM-8T1/B - 8 ports CESM-8E1 2 - 8 ports VISM-PR-8E1 - 8 ports CESM-8E1 - 8 ports C
Chapter 1 Preparing for Configuration Cisco MGX Switch Features Table 1-2 Cisco MGX 8830, Cisco MGX 8850 (PXM1E/PXM45), Cisco MGX 8880, and Cisco MGX 8950 Capabilities Cisco MGX 8850 (PXM1E) Feature T3/E3 Cisco MGX 8830 (PXM1E) Cisco MGX 8850 (PXM45) Cisco MGX 8880 (PXM45/C) Cisco MGX 8950 (PXM45) FRSM-2CT3 - 2 FRSM-2CT3 - 2 AXSM-16-E3 - 16 ports (channelized) ports (channelized) ports AXSM-16-E3/B 16 ports AXSM-16-T3/B 16 ports FRSM-2T3E3 - 2 ports FRSM-2T3E3 - 2 ports AXSM-16-E3/B 16 ports
Chapter 1 Preparing for Configuration Cisco MGX Switch Features Table 1-2 Cisco MGX 8830, Cisco MGX 8850 (PXM1E/PXM45), Cisco MGX 8880, and Cisco MGX 8950 Capabilities Feature Cisco MGX 8850 (PXM1E) Cisco MGX 8830 (PXM1E) Cisco MGX 8850 (PXM45) Cisco MGX 8880 (PXM45/C) Cisco MGX 8950 (PXM45) OC-12c/STM-4 — — AXSM-4-622 - 4 ports AXSM-2-622-E 2 ports AXSM-4-622/B 4 ports AXSM-2-622-E 2 ports AXSM-4-622/B 4 ports AXSM-4-622/B 4 ports OC-48c/STM-16 — — AXSM-1-2488 - 1 port AXSM-1-2488/B 1
Chapter 1 Preparing for Configuration Cisco MGX Switch Features Table 1-2 Cisco MGX 8830, Cisco MGX 8850 (PXM1E/PXM45), Cisco MGX 8880, and Cisco MGX 8950 Capabilities Cisco MGX 8850 (PXM1E) Feature Cisco MGX 8830 (PXM1E) Cisco MGX 8850 (PXM45) Cisco MGX 8880 (PXM45/C) Cisco MGX 8950 (PXM45) CESM-8E1 CESM-8E1 2 No No CESM-8T1/B CESM-8T1/B CESM-8T1 3 MPSM-8-T1E1 MPSM-8-T1E1 CESM-8T1/B 2 No Circuit Emulation CESM-8E1 MPSM-8-T1E1 Voice IP VISM-PR-8E1 VISM-PR-8E1 VISM-PR-8E1 VISM-PR-
Chapter 1 Preparing for Configuration Cisco MGX Switch Features Table 1-2 Cisco MGX 8830, Cisco MGX 8850 (PXM1E/PXM45), Cisco MGX 8880, and Cisco MGX 8950 Capabilities Feature Cisco MGX 8850 (PXM1E) Cisco MGX 8830 (PXM1E) Cisco MGX 8850 (PXM45) Cisco MGX 8880 (PXM45/C) Cisco MGX 8950 (PXM45) Supported on SRME, SRME/B, and select service modules as listed in the Cisco MGX 8850 (PXM1E/PXM45), Cisco MGX 8950, Cisco MGX 8830, and Cisco MGX 8880 Hardware Installation Guide, Releases 2 Through 5.
Chapter 1 Preparing for Configuration Typical Topologies Table 1-3 illustrates the differences between the PXM45/A, PXM45/B, and PXM45/C cards. .
Chapter 1 Preparing for Configuration Typical Topologies Core Switch Figure 1-1 shows the switch operating in a core switch topology. Figure 1-1 Core Switch Topology Core ATM network 38410 Cisco MGX 8850 (PXM45) In the core switch topology, the switch works with other ATM switches to transfer broadband ATM traffic from one ATM edge device to another. The core acts like a freeway, and the edge devices act like freeway on-ramps.
Chapter 1 Preparing for Configuration Typical Topologies The Cisco MGX 8850 (PXM1) node in Figure 1-2 is called a feeder node. In the multiservice edge aggregation topology, the feeder node is co-located with other ATM equipment and communicates with one or more core switches at remote locations. The switch aggregates the traffic from local ATM devices and packages it for high-speed communications over the core.
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 DSLAMs 38412 Core ATM network 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 MIB Field Names for UDI The MIB field names that contain the UDI information are as follows: Table 1-5 MIB Field Names for UDI UDI Field MIB Field Name NAME: Entity-MIB.entPhysicalName (Product Name) DESCR: Entity-MIB.entPhysicalDescr (Product Description) PID: Entity-MIB.entPhysicalModelName (PID) VID: Entity-MIB.entPhysicalHardwareRev (VID) SN: Entity-MIB.
Chapter 1 Preparing for Configuration Guidelines for Creating an IP Address Plan CiscoView is a CWM component that can be used independently of CWM to provide limited monitoring and management capabilities. To determine which versions of CWM and CiscoView are compatible with this release, refer to the following release note documents: • Release Notes for Cisco MGX 8850 (PXM1E/PXM45), Cisco MGX 8950, and Cisco MGX 8830 Switches, Release 5.0.00.
Chapter 1 Preparing for Configuration Guidelines for Creating an IP Address Plan MGX switches provide two IP addresses for LAN connections. The boot IP address enables switch management when a PXM is in boot mode, which means that it has only loaded the boot software. The disk IP address enables switch management only after the switch has loaded and is running the runtime software. A typical switch configuration requires either one or two IP addresses for LAN access.
Chapter 1 Preparing for Configuration Guidelines for Creating a Network Clock Source Plan Guidelines for Creating a Network Clock Source Plan Clock synchronization in an ATM network is very important. If two switches have trouble synchronizing their communications, traffic between the switches may have excessive errors or line failures.
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
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 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.
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 Step 1 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 Step 6 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 8850 (PXM1E/PXM45), Cisco MGX 8950, Cisco MGX 8830, and Cisco MGX 8880 Hardware Installation Guide, Releases 2 Through 5, you must initialize the switch before you can configure it.
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 PXM1E 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.
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 CESM8T1 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.
Chapter 2 Configuring General Switch Features Verifying the Hardware Configuration Table 2-9 Valid Card Installation Options (continued) Front Card Type Valid Back MGX 8830 MGX 8850 MGX 8880 MGX 8950 Card Bay Valid Slot Valid Slot Valid Slot Valid Slot Locations Numbers Numbers Numbers Numbers Description Back Card Types 1 port SMFSR-1-2488 SMFLR-1-2488 SMFXLR-1-2488 Upper — 1–6, 9–14 — SMFSR-1-2488/B SMFLR-1-2488/B SMFXLR-1-2488/B Upper — 1–6, 9–14 1–6, 9–14 1-6, 11-16 SMFSR-1-9953 Upper
Chapter 2 Configuring General Switch Features Verifying the Hardware Configuration Table 2-9 Valid Card Installation Options (continued) Front Card Type AXSM-16-155/B 4 AXSM-16-155XG 4 Valid Back MGX 8830 MGX 8850 MGX 8880 MGX 8950 Card Bay Valid Slot Valid Slot Valid Slot Valid Slot Locations Numbers Numbers Numbers Numbers Description Back Card Types 16-port OC-3 SMB-4-155 MMF-8-155-MT/B SMFIR-8-155-LC/B SMFLR-8-155-LC/B Upper and — lower 1–6, 9–14 1–6, 9–14 1-6, 11-16 16-port OC-3 MCC-8-1
Chapter 2 Configuring General Switch Features Verifying the Hardware Configuration Table 2-9 Valid Card Installation Options (continued) Valid Back MGX 8830 MGX 8850 MGX 8880 MGX 8950 Card Bay Valid Slot Valid Slot Valid Slot Valid Slot Locations Numbers Numbers Numbers Numbers Front Card Type Description Back Card Types FRSM-8E1-C 8 port channelized Frame Relay Service Module with E1 interfaces RJ48-8E1 MGX-RJ48-8E11 R-RJ48-8E1 SMB-8E1 R-SMB-8E1 Upper and 3-6, 10-13 1-6, 9-14, — lower 17-22, 25-
Chapter 2 Configuring General Switch Features Verifying the Hardware Configuration Table 2-9 Valid Card Installation Options (continued) Front Card Type Description SFP-2-155 Upper and 3-6, 10-13 1-6, 9-14, — lower 17-22, 25-30 — 2 port service module for ATM and Frame Relay services over OC-3 electrical interfaces. SMB-2-155-EL Upper and 3-6, 10-13 1-6, 9-14, — lower 17-22, 25-30 — 3 port service module for ATM and Frame Relay services over T3 and E3 electrical interfaces.
Chapter 2 Configuring General Switch Features Verifying the Hardware Configuration Table 2-9 Valid Card Installation Options (continued) Front Card Type Description Back Card Types Valid Back MGX 8830 MGX 8850 MGX 8880 MGX 8950 Card Bay Valid Slot Valid Slot Valid Slot Valid Slot Locations Numbers Numbers Numbers Numbers PXM1ECOMBO 4 Processor Switch Module PXM-UI-S3/B Upper MGX-T3E3-155 Lower 1 and 2 7 and 8 — — — 7 and 8 — — — 7 and 8 — 7 and 8 — 7 and 8 7 and 8 7 and 8 4-por
Chapter 2 Configuring General Switch Features Verifying the Hardware Configuration Table 2-9 Valid Card Installation Options (continued) Valid Back MGX 8830 MGX 8850 MGX 8880 MGX 8950 Card Bay Valid Slot Valid Slot Valid Slot Valid Slot Locations Numbers Numbers Numbers Numbers Front Card Type Description Back Card Types SRME/B 1 or 3 port Service Redundancy Module with T3, SONET, or SDH interfaces MGX-SMFIR-1-155 MGX-STM1-EL-1 BNC-3T3-M Upper and 7 and 14 lower VISM-PR-8E1 8-port E1 Voice Int
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 IISP 4 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 addimalnk addimaport Note 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 addimalnk addimaport Note 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. Related commands: 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 Cisco MGX 8850 (PXM1E) or Cisco 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) 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 Step 4 To configure a T1 (DS1) line, enter the following commands: 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.
Chapter 3 Provisioning PXM1E Communication Links General PXM1E Configuration Procedures Configuring SONET Lines At the physical level, you can configure the line clock source for SONET lines. The following procedure describes how to configure SONET lines. Step 1 Establish a configuration session using a user name with GROUP1 privileges or higher. Step 2 If you do not know the line number you want to configure, enter the dsplns command to display a list of the lines: mgx8830b.2.PXM.
Chapter 3 Provisioning PXM1E Communication Links General PXM1E Configuration Procedures The following procedure describes how to configure T3 lines. Step 1 Establish a configuration session using a user name with GROUP1 privileges or higher. Step 2 If you do not know the line number you want to configure, enter the dsplns command to display a list of the lines. mgx8830b.2.PXM.
Chapter 3 Provisioning PXM1E Communication Links General PXM1E Configuration Procedures Table 3-2 lists the parameter descriptions for configuring SONET, DS3 and E3 lines. Be sure to use only the parameters listed for E3 lines. Step 5 To verify your configuration changes, enter the dspln command. Verifying Line Configuration To display the configuration of a line, use the following procedure. Step 1 Establish a CLI management session at any user access level.
Chapter 3 Provisioning PXM1E Communication Links General PXM1E Configuration Procedures IMA is supported on the PXM1E-16-T1E1 and AUSM-8-T1E1/B cards. On Cisco MGX 8850 (PXM45) switches, IMA is supported on AXSM-32-T1-E and AXSM-32-E1-E cards. IMA is not supported on Cisco MGX 8950 switches. Note The procedures in this chapter apply only to the PXM1E card. To configure IMA on AUSM/B cards, refer to the Cisco ATM Services (AUSM/MPSM) Configuration Guide and Command Reference for MGX Switches, Release 5.
Chapter 3 Provisioning PXM1E Communication Links General PXM1E Configuration Procedures MGXswitch.7.PXM.a > dsplns Line Line Line Line Length Num State Type Lpbk (meters) ---- ----- --------- ----------- -------2.1 Up dsx1ESF NoLoop 40 2.2 Down dsx1ESF NoLoop 40 2.3 Down dsx1ESF NoLoop 40 2.4 Down dsx1ESF NoLoop 40 2.5 Down dsx1ESF NoLoop 40 2.6 Down dsx1ESF NoLoop 40 2.7 Down dsx1ESF NoLoop 40 2.8 Down dsx1ESF NoLoop 40 2.9 Down dsx1ESF NoLoop 40 2.10 Down dsx1ESF NoLoop 40 2.
Chapter 3 Provisioning PXM1E Communication Links General PXM1E Configuration Procedures Table 3-4 addimagrp Command Parameters (continued) txFrameLen txclkMode Transmit frame length. The optional values for each IMA version are: • Version 1.0 = 128 • Version 1.1 = 32, 64, 128, 256 Transmit clock mode.
Chapter 3 Provisioning PXM1E Communication Links General PXM1E Configuration Procedures M8830_CH.1.PXM.a > dspimagrps Ima Min Tx Rx Tx Diff NE-IMA FE-IMA IMA Grp Lnks Frm Frm Clk Delay State State Ver Len Len Mode (ms) -------------------------------------------------------------------------------2.1 1 128 128 CTC 275 Operational Operational 1.0 Step 3 To display the configuration information for the particular IMA group that you want to configure, enter the dspimagrp command.
Chapter 3 Provisioning PXM1E Communication Links General PXM1E Configuration Procedures Step 4 To configure an IMA group, enter the cnfimagrp command, as shown in the following example: M8830_CH.1.PXM.a > cnfimagrp <-grp [-ver ] [-txm ] [-txid ] [-txfl ] [-dd ] [-uptim] [-dntim ] [-vfb ] [-mode ] [-rxid ] Table 3-5 describes the parameters for the cnfimagrp command.
Chapter 3 Provisioning PXM1E Communication Links General PXM1E Configuration Procedures Table 3-5 cnfimagrp Command Parameters (continued) -mode The -mode parameter is optional and configures the IMA autorestart feature.
Chapter 3 Provisioning PXM1E Communication Links General PXM1E Configuration Procedures 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 Label : Rx OAM Label : Test Pattern Procedure Status : Test Link : Test Pattern : Stuff Cell Indication (frames) : Version Fallback Enabled : Auto-Restart
Chapter 3 Provisioning PXM1E Communication Links General PXM1E Configuration Procedures 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) -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. Range 0-25000 milliseconds. In the following example, the user configures link 2.
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).
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 support
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 resou
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 Cisco MGX 8850 (PXM1E/PXM45) switches, you can start the CLI session at either end.
Chapter 3 Provisioning PXM1E Communication Links General PXM1E Configuration Procedures Provisioning and Managing SPVCs and SPVPs The following sections describe the following tasks: • Configuring Point-to-Point Connections • Configuring Point-to-Multipoint Connections • Adding Parties to a P2MP Root Connection • Obtaining the NSAP for a Party • Displaying a List of Connections • Displaying the Status of a Single Connection • Modifying P2P and P2MP Connections • Bringing Down a Connection
Chapter 3 Provisioning PXM1E Communication Links General PXM1E Configuration Procedures Tip The configuration of SPVCs and SPVPs is very similar. The difference is that SPVPs are assigned VCI 0 and do not use nonzero VCI numbers. An SPVC requires a nonzero VCI. Configuring the Slave Side of SPVCs and SPVPs To configure the slave side of an SPVC or SPVP, use the following procedure. Step 1 Establish a configuration session using a user name with GROUP1 privileges or higher.
Chapter 3 Provisioning PXM1E Communication Links General PXM1E Configuration Procedures Table 3-17 Parameters for the addcon and cnfcon Commands (continued) Parameter Commands Description serviceType addcon Replace with the number that corresponds to the requested service type for this SPVC (this value must be identical on master and slave sides).
Chapter 3 Provisioning PXM1E Communication Links General PXM1E Configuration Procedures Table 3-17 Parameters for the addcon and cnfcon Commands (continued) Parameter Commands Description -rscr addcon, cnfcon Remote sustained cell rate (SCR). Specifies the SCR from a remote endpoint to a local endpoint (3-5651328 cells per second). SCR is the maximum cell rate that a connection can sustain for long periods.
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 • All configuration for P2MP connections is done at the root.You can not do any configuration on the remote (slave) end of the connection. Any attempt to specify parameters for the remote end will be blocked. • An overview of P2MP, specifications for P2MP connection limits, and multicast support information is published in the Cisco PNNI Network Planning Guide for MGX and SES Products.
Chapter 3 Provisioning PXM1E Communication Links General PXM1E Configuration Procedures 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 -------------------- Provisioning Parameters -------------------Connection Type: VCC Cast Type: Point-to-Point Service Category: CBR Conformance: CBR.
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 Cisco MGX 8850 (PXM1E) or the Cisco 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 Cisco MGX 8850 (PXM1E) or the Cisco 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 3-92 Cisco MGX 8850 (PXM1E/PXM45), Cisco MGX 8950, Cisco MGX 8830, and Cisco MGX 8880 Configuration Guide Release 5.0.10, OL-3845-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-2 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 To bring MPSM cards up to the Active/Active status, you must configure an interface type. For MPSM-8-T1E1 cards, you must also configure a service. For more information, see the “Selecting MPSM Interfaces and Services” section, which appears later in this chapter.
Chapter 4 Preparing Service Modules for Communication Selecting MPSM Interfaces and Services Step 3 Another way to see the software revision levels for a single card is to enter the dspcd command as follows: M8850_LA.7.PXM.a > dspcd 1 M8850_LA System Rev: 02.01 MGX8850 Slot Number: 1 Redundant Slot: NONE Front Card ---------Inserted Card: AXSM_4OC12 Reserved Card: AXSM_4OC12 State: Active Serial Number: SAK0350007N Prim SW Rev: 2.1(60) Sec SW Rev: 2.1(60) Cur SW Rev: 2.1(60) Boot FW Rev: 2.
Chapter 4 Preparing Service Modules for Communication Selecting MPSM Interfaces and Services Active/Active state, you must specify only the interface type because this card can simultaneously support ATM and Frame Relay services on different ports. To configure MPSM interfaces and services, use the cnfcdmode command as described in the following procedure. Step 1 Establish a configuration session using a user name with SERVICE_GP privileges or higher.
Chapter 4 Preparing Service Modules for Communication Establishing Redundancy Between Two Service Modules Table 4-2 MPSM-8-T1E1 Card Names in the dspcd and dspcds Command Displays Card Name Description MPSM-8T1E1 No service configured on card. MPSM-8E1-ATM Configured for ATM services and E1 interfaces. MPSM-8E1-CES Configured for circuit emulation services and E1 interfaces. MPSM-8E1-FRM Configured for Frame Relay services and E1 interfaces.
Chapter 4 Preparing Service Modules for Communication Selecting a Card SCT Note Step 5 When MPSM cards are installed on the switch, the addred command will fail if there are not enough licenses on the secondary card (1:N redundant configurations) or in the license pool to match the licenses already in use on the primary card.
Chapter 4 Preparing Service Modules for Communication Selecting a Card SCT To select an SCT for a card, use the following procedure. Step 1 Establish a configuration session using a user name with GROUP1 privileges or higher. Step 2 Enter the cc command to change to an active service module for which you will select an SCT. M8850_LA.8.PXM.a > cc 1 (session redirected) M8850_LA.2.AXSM.a > Note Step 3 In a redundant pair, you must specify the SCT on the active card.
Chapter 4 Preparing Service Modules for Communication Selecting a Port SCT M8850_LA.1.AXSM.a > dspcd Front Card ---------Card Type: State: Serial Number: Boot FW Rev: SW Rev: 800-level Rev: Orderable Part#: PCA Part#: CLEI Code: Reset Reason: Upper Card ---------- AXSM-4-622 Active SAK0350007N 3.0(0.171)P2 3.0(0.
Chapter 4 Preparing Service Modules for Communication Selecting a Port SCT 4-12 Cisco MGX 8850 (PXM1E/PXM45), Cisco MGX 8950, Cisco MGX 8830, and Cisco MGX 8880 Configuration Guide Release 5.0.10, OL-3845-01 Rev.
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 8850 (PXM1E/PXM45), Cisco MGX 8950, Cisco MGX 8830, and Cisco MGX 8880 Hardware Installation Guide, Releases 2 Through 5, to see which service modules support bulk distribution.
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 1 Step 2 Command Purpose username Start a configuration session. Note upln At the active PXM prompt, bring up and activate the lines on the SRM card. This step establishes physical layer connectivity between the SRM and the CPE. Related commands: To perform all the procedures in this quickstart procedure, you must log in as a user with GROUP1 privileges or higher.
Chapter 5 Preparing SRM Cards for Communications Setting Up SRM Lines To bring up a line on the SRM, use the following procedure. Step 1 Establish a configuration session on the PXM card using a user name with GROUP1 privileges or higher. Step 2 Enter the upln command at the switch prompt. mgx8830b.1.PXM.a > upln Replace with the logical slot number of the SRM.
Chapter 5 Preparing SRM Cards for Communications Setting Up SRM Lines If you are configuring a Cisco MGX 8850 (PXM1E/PXM45) switch, replace X with 15 for an SRME in the upper bay, or 31 for an SRME in the lower bay. If you are configuring a Cisco MGX 8830 switch, replace X with 7. SRME provides one line, so the line number is always one as shown in the following example: PXM1E_SJ.8.PXM.
Chapter 5 Preparing SRM Cards for Communications Setting Up SRM Lines Table 5-1 Parameters for SONET Line Configuration (continued) Parameter Description -lpb Enables one of two loopback types or disables an active loopback, as follows: • 1: No loopback • 2: Local loopback • 3: Remote loopback A loopback circulates OAM cells between the card and the CPE in a local loopback or between the card and the network in a remote loopback.
Chapter 5 Preparing SRM Cards for Communications Setting Up SRM Lines Table 5-1 Parameters for SONET Line Configuration (continued) Parameter Description -st The signaling transport mode applies only if you have selected byte-synchronous tributary mapping (-tm 2). Replace SignallingTranportMode with either a 2 to specify transfer mode, or a 3 to specify clear mode. With transfer mode, the framing bit is transferred to the VT header. With clear mode, the signaling bit is transferred to the VT header.
Chapter 5 Preparing SRM Cards for Communications Setting Up SRM Lines In the following example, the user displays the configuration for the T3 line connected to line 1 on the SRM card in slot 7. Lampoon.1.PXM.a > dspln Line Number : Admin Status : Line Type : Line Coding : Line Length(meters) : OOFCriteria : AIS c-Bits Check : Loopback : Xmt. Clock source : Rcv FEAC Validation : Step 4 -ds3 7.1 7.
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 1 Establish a configuration session with the active PXM using a user name with GROUP1_GP privileges or higher. Note All SRM configuration is done from the active PXM card. 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).
Chapter 5 Preparing SRM Cards for Communications Establishing Redundancy Between SONET/SDH Lines with APS Table 5-4 APS Line Architecture Modes Option Description 1 Selects 1+1 Bellcore GR-253 APS protocol signaling (transmission on both working and protection lines). 2 Selects 1:1 Bellcore GR-253 APS protocol signaling (transmission on either the working line or the protection line) for intracard APS. Note This option is not supported in this release. 3 Selects 1+1 ITU-T 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 -sd Replace with one of the following numbers to indicate the Signal Degrade Bit Error Rate (BER), in negative powers of ten: • 5 = 10 -5 • 6 = 10 -6 • 7 = 10 -7 • 8 = 10 -8 • 9 = 10 -9 Example: -sd 5 -wtr Replace Wait To Restore with the number of minutes to wait after the working line has become
Chapter 5 Preparing SRM Cards for Communications Linking Service Module Lines to SRM Channels, VTs, or VCs Once you establish a link for a service module line, bulk distribution is enabled for the entire service module and all lines must use bulk distribution. Although bulk distribution will work with a service module back card installed, the service module cannot use the back card once bulk distribution is enabled on any line.
Chapter 5 Preparing SRM Cards for Communications Linking Service Module Lines to SRM Channels, VTs, or VCs Table 5-6 addlink Command Parameters (continued) Option Description NumberOfLinks The number of links you want to configure with this command. Replace NumberOfLinks with a number from 1 through 8. If you specify 1, you will create one link. If you specify 8, you can configure links for all 8 lines on a service module at the same time. TargetIF Targeted starting line in the format slot.line.
Chapter 5 Preparing SRM Cards for Communications Linking Service Module Lines to SRM Channels, VTs, or VCs Table 5-7 5-16 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-7 SRM SONET Virtual Tributary Mapping (continued) SRME Link Number VTG No. VT No. SRME Link Number VTG No. VT No. 41 6 2 83 6 4 42 7 2 84 7 4 Table 5-8 shows how each SRM link is mapped to a tributary unit group 2 (TUG-2) and a tributary unit (TU) or VC within a SDH line when the administrative unit 3 (AU3) tributary group type is selected.
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 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.
Chapter 5 Preparing SRM Cards for Communications Where To Go Next 5-20 Cisco MGX 8850 (PXM1E/PXM45), Cisco MGX 8950, Cisco MGX 8830, and Cisco MGX 8880 Configuration Guide Release 5.0.10, OL-3845-01 Rev.
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 6-12 Cisco MGX 8850 (PXM1E/PXM45), Cisco MGX 8950, Cisco MGX 8830, and Cisco MGX 8880 Configuration Guide Release 5.0.10, OL-3845-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 Card 2 Port SCT ID PNNI 4 MPLS Policing 1 Notes N/A N/A All three AXSM-E card SCTs are identical. 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.
Chapter 7 Managing Service Class Templates Managing SCTs Table 7-1 Cisco Provided SCTs (continued) Card Type SCT Type FRSM-12-T3E3 Card 2 Port MPSM-T3E3-155 Card 2 Port PXM1E Port SCT ID PNNI 4 MPLS Policing 1 Notes 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. 1 On — Optimized for UNI connections that use 5 or more T1/E1 lines.
Chapter 7 Managing Service Class Templates Managing 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. You can use FTP to transfer files to this directory as described in the “Copying Software Files to the Switch” section in Appendix A, “Downloading and Installing Software Upgrades.
Chapter 7 Managing Service Class Templates Managing SCTs Table 7-2 describes the parameters used in the SCT naming convention. Table 7-2 SCT Naming Conventions Parameter Description service_module_type The type of the service module on which the SCT will be applied. The possible service module types are AXSM, AXSME, AXSMXG, FRSM12, MPSM155, and PXM1E. PORT|CARD Specifies whether this is a port SCT or a card SCT. Note SCT_ID V PXM1E cards use port SCTs only.
Chapter 7 Managing Service Class Templates Managing SCTs For more information on transferring files to the switch, see the “Copying Software Files to the Switch” section in Appendix A, “Downloading and Installing Software Upgrades.” After you download a file to a switch, you must register the SCT on the switch if it has not been registered before, or you must update a preregistered SCT. The next two sections describe how to register SCT files and how to update previously registered SCT files.
Chapter 7 Managing Service Class Templates Managing SCTs Step 2 If the SCT file you want to register is not on the switch, FTP the SCT file to the C:SCT/TEMP folder, as described in the “Copying Software Files to the Switch” section in Appendix A, “Downloading and Installing Software Upgrades.” For information on locating SCT files provided by Cisco, refer to the following release note documents: • Release Notes for Cisco MGX 8850 (PXM1E/PXM45), Cisco MGX 8950, and Cisco MGX 8830 Switches, Release 5.0.
Chapter 7 Managing Service Class Templates Managing SCTs Table 7-3 addsct and cnfsct Command Parameters (continued) 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 minor A 16-bit number which identifies the minor version of the SCT. Each time an SCT file is modified, saved, and downloaded, the minor version number changes. A minor version change does not require an upgrade or re-configuration of the card and port database. However, the card must be reset before the card can use the changed SCT settings.
Chapter 7 Managing Service Class Templates Managing PXM1E Port SCTs Displaying the SCT Assigned to a Port To display the SCT assigned to a PXM1E port, use the following procedure. Step 1 Establish a configuration session at any user access level. Step 2 Enter the following command: mgx8830a.1.PXM.a > dspports The dspports report displays a column labeled “Port SCT Id,” which identifies the SCT assigned to each port. mgx8830a.1.PXM.a > dspports ifNum Line Admin Oper.
Chapter 7 Managing Service Class Templates Managing PXM1E Port SCTs Displaying Port SCT Settings To view the port SCT settings, 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 > dspportsct Select one of the options to display one of the six SCT configuration reports, and replace with the number of the port you want to view.
Chapter 7 Managing Service Class Templates Managing PXM1E Port SCTs Port SCT ABR Parameters (dspportsct abr) The following report appears when you enter the dspportsct abr command: M8830_CH.1.PXM.
Chapter 7 Managing Service Class Templates Managing PXM1E Port SCTs Port SCT Bandwidth Parameters (dspportsct bw) The following report appears when you enter the dspportsct bw command: M8830_CH.1.PXM.
Chapter 7 Managing Service Class Templates Managing PXM1E Port SCTs Table 7-8 describes the SCT ABR Parameters shown in the example. Table 7-8 SCT Bandwidth 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). PCR Specifies the maximum PCR for a connection using this service type. The value is a percentage of the maximum cell rate for the logical interface.
Chapter 7 Managing Service Class Templates Managing PXM1E Port SCTs 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 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). COSB_NUM Class of Service Buffer Number. The number that identifies one of the sixteen CoS buffers.
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. Note 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 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). EXCESS-PRIORITY 0–15 The priority at which this COSB will be given access to excess bandwidth.
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 | DISABLED | | ATMF_UBR2(264)| 4 | DISABLE
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.
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 The actual procedure for creating an upper level peer group for your WAN depends on the structure of your WAN. This section shows how to create an upper level peer group for the WAN shown in Figure 8-1.
Chapter 8 Managing PNNI Nodes and PNNI Routing Managing PNNI Nodes Step 2 Display the current PGL priority of the node that will become PGL or a back up PGL by entering the dsppnni-election command as shown in the following example: PXM1E_SJ.7.PXM.a > dsppnni-election node index: 1 PGL state...... Priority....... OperNotPgl 0 node index: 2 PGL state...... Priority....... Starting 0 Init time(sec)....... 15 Override delay(sec).. 30 Re-election time(sec) 15 Pref PGL................56:160:47.
Chapter 8 Managing PNNI Nodes and PNNI Routing Managing PNNI Nodes 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.00 Pref PGL node name ..... PGL.....................0:0:00.000000000000000000000000.000000000000.00 PGL node name .......... Active parent node id...0:0:00.000000000000000000000000.000000000000.
Chapter 8 Managing PNNI Nodes and PNNI Routing Managing PNNI Nodes When the complex node feature is enabled, a parent LGN presents other peer groups using complex node representation. Complex node representation provides information about multiple paths through external peer groups, and this gives source route nodes more choices when routing through external peer groups. Tip For more information on complex nodes, refer to the Cisco PNNI Network Planning Guide for MGX and SES Products.
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 lists the parameter descriptions for the addpnni-summary-addr command. 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.
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 Before you can create a preferred route, all the nodes that will be in the preferred route must be in the network node table. Enter the dspnwnodes command to ensure that all the nodes in your planned preferred route are in the network node table, as shown in the following example: U1.8.PXM.a > dspnwnodes Node Identifier PXM Pref rte Node name -------------------------------------------------56:160:47.009181000000003071f80406.003071f80406.
Chapter 8 Managing PNNI Nodes and PNNI Routing Managing PNNI Routes Enter the cnfndidrtes command to replace a node ID with a different ID for all configured preferred routes. For example, if you remove a node that is a network element (NE) in one or more preferred routes, you can use the cnfndidrtes to enter a different node’s name. Providing that the new node’s name appears in the network node table, the new node replaces the old node in the preferred route.
Chapter 8 Managing PNNI Nodes and PNNI Routing Managing PNNI Routes Table 8-6 addpref Command Parameters routeid The preferred route identifier has a range of 1–65535. If a particular ID is in use, the node rejects the command. Check the dspprefs output for available route IDs as needed. neSyntax Four ways of identifying the NEs exist.
Chapter 8 Managing PNNI Nodes and PNNI Routing Managing PNNI Routes Step 4 Associate the appropriate SPVC or SPVP to the preferred route you created in Step 2. a. If you are associating a new SPVC or SPVP with the preferred route, enter the addcon command as follows: addcon -prefrte [-directrte ] For PXM1E cards, the addcon command is entered at the PXM card prompt.
Chapter 8 Managing PNNI Nodes and PNNI Routing Managing PNNI Routes Table 8-7 addcon and cnfcon Preferred Route Command Parameters (continued) -prefrte Associates a preferred route (preferredRouteId) to the connection. Use this optional parameter at the master endpoint only. Range: 0-65535 Default: 0 -directrte Specifies that the connection can take only the preferred route associated through the -prefrte parameter. Use this optional parameter at the master endpoint only.
Chapter 8 Managing PNNI Nodes and PNNI Routing Managing PNNI Routes Table 8-8 Parameters for cnfpref Command Parameter Description routeid The preferred route identifier has a range of 1–65535. If a particular ID is in use, the node rejects the command. Check the dspprefs output for available route IDs as needed. neSyntax Four ways of identifying the NEs exist.
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 Pure PXM45/B Networks Running Version 3.0.10 or Later To improve rerouting performance in a pure PXM45/B based network (Version 3.0.10 or later), Cisco recommends entering the following commands on the active PXM45/B in each switch: 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 Within the priority categories of 0 through15, connections are further divided into groups based on their bandwidth. Connections requiring more bandwidth are routed before those requiring less bandwidth. The number of bandwidth groups is fixed at 50, but you can specify the following ranges: • range with the lowest bandwidth requirement • range of cells per second in each range between the highest and lowest ranges.
Chapter 8 Managing PNNI Nodes and PNNI Routing Managing Priority Routing Table 8-9 cnfpri-routing Command Parameters Parameter Description -bwgrps Bandwidth groups. -bwstart The value for bwstart is the highest cell rate in the lowest-speed bandwidth group. The number of bandwidth groups is fixed at 50. Range: 1–500000 Default: 5000 -bwincr The increment for the cell rate between the upper and lower bounds of each intermediate bandwidth group.
Chapter 8 Managing PNNI Nodes and PNNI Routing Managing Priority Routing Configuring Priority Routing for an SPVC Once priority routing has been set up on a node, you can prioritize the node’s SPVCs. A connection’s priority is designated during the SPVC master end setup with the addcon command. (See the “Configuring the Master Side of SPVCs and SPVPs” section in Chapter 3, “Provisioning PXM1E Communication Links.
Chapter 8 Managing PNNI Nodes and PNNI Routing Managing Priority Bumping M8830_CH.1.PXM.a > dsppnport 6.1 Port: IF status: VSVD Internal Loop: VSVD External Loop: UCSM: Auto-config: IF-side: UniType: PassAlongCapab: Input filter: minSvccVpi: minSvccVci: minSvpcVpi: 6.
Chapter 8 Managing PNNI Nodes and PNNI Routing Managing Priority Bumping The following sections describe the tasks for managing the priority bumping feature: • Enabling, Configuring, and Disabling Priority Bumping • Displaying the Priority Bumping Configuration • Displaying Priority Bumping Statistics • Resetting the Priority Bumping Statistics • Displaying Priority Bumping Resource Usage Enabling, Configuring, and Disabling Priority Bumping When you enable priority bumping, you should enable i
Chapter 8 Managing PNNI Nodes and PNNI Routing Managing Priority Bumping The configuration values shown are the same as those for the cnfndconnpribump command described earlier. The Priority Bumping Oper State line shows whether or not priority bumping is operational. When priority bumping is enabled, there is a delay during which the feature is brought up. If you enable priority bumping and the operational state is down, wait a few minutes and check the state again.
Chapter 8 Managing PNNI Nodes and PNNI Routing Managing Connection Grooming Replace the portid variable with a port number in the format: [shelf.]slot[:subslot].port[:subport]. To display available port IDs, enter the dsppnports command. The following example shows the port resources for port 1:2.1:1: M8830_CH.2.PXM.a > dsppnportpribumprsrc 1:2.
Chapter 8 Managing PNNI Nodes and PNNI Routing Managing Connection Grooming How Grooming Reroutes Connections Cisco MGX switches use two different reroute methods for grooming connections. Prior to Release 5, Cisco MGX switches use only the hard reroute method. During a hard reroute, a connection that has been selected for grooming is disconnected, and then a new connection is built over a new route.
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 B1 C1 ‘D E 1 F E1 After sending release D E A F 1 B 1 C 1 D 1 E ‘ After receiving release A F B 1 C 1 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 8-36 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 The following example enables scheduled grooming on port 6:1.3:13 using the default values and uses the dsprteoptcnf command to display the configured values: M8850_LA.7.PXM.a > cnfrteopt 6:1.3:13 enable M8850_LA.7.PXM.a > dsprteoptcnf 6:1.
Chapter 8 Managing PNNI Nodes and PNNI Routing Managing Connection Grooming This example schedules grooming to occur at the default interval (60 minutes) between midnight and 4 a.m. on Mondays, Wednesdays, and Fridays: M8850_LA.7.PXM.a > cnfrteopt 6:1.3:13 enable -tod 00:00..04:00 -weekday .M.W.F. M8850_LA.7.PXM.a > dsprteoptcnf 6:1.
Chapter 8 Managing PNNI Nodes and PNNI Routing Managing Connection Grooming Table 8-11 Parameters for optrte Command (continued) vci When the -vci option is specified, the optrte command grooms only those port connections that use the specified VCI. To display a list of connections that includes the VPI and VCI for each connection, enter the dspcons command. -range When the -range option is specified, the optrte command grooms only those port connections in the specified VPI and VCI range.
Chapter 8 Managing PNNI Nodes and PNNI Routing Managing Connection Grooming When the grooming operation evaluates a connection for rerouting, it uses just one of the three available metrics. The chosen metric is based on the metrics configured for the connection. You can view the configuration of connection metrics by entering the dspcon command for the connection. Connection metrics that display -1 are not configured. In the following example, none of the three metrics are configured. PXM1E_SJ.7.PXM.
Chapter 8 Managing PNNI Nodes and PNNI Routing Managing Connection Grooming Table 8-13 Grooming Metric Selection Connection Configured Metric Max. Cost CTD CDV Selected Metric No No No AW No No Yes CDV No Yes No CTD No Yes Yes CTD Yes No No AW Yes No Yes AW Yes Yes No AW Yes Yes Yes AW The grooming operation uses both the percentage and absolute thresholds to determine if a prospective new route is better than the incumbent route.
Chapter 8 Managing PNNI Nodes and PNNI Routing Managing Connection Grooming Table 8-14 Parameters for cnfrteoptthresh Command (continued) 8-42 -awrtvbr Use the -awrtvbr option to set thresholds for the grooming rtVBR connections based on cumulative AW. When the type parameter is set to per, the range is 0 to 100 percent. When the type parameter is set to abs, the range is 0 to 4294967295. The default values are percentage reduction = 30 and absolute cost = 0.
Chapter 8 Managing PNNI Nodes and PNNI Routing Managing Connection Grooming The following example sets the percentage reduction and absolute threshold for CBR connections that reroute based on cumulative AW. This example uses the dsprteoptcnf command to show the change in grooming threshold parameter values. M8850_LA.7.PXM.a > cnfrteoptthresh per -awcbr 20 M8850_LA.7.PXM.a > cnfrteoptthresh abs -awcbr 5 M8850_LA.7.PXM.
Chapter 8 Managing PNNI Nodes and PNNI Routing Managing Connection Grooming Note The cnfndrteopt command configures other features that are described later in this chapter. Table 8-15 Parameters for cnfndrteopt Command Parameter Description -og Use the -og option to enable or disable orderly grooming. To enable orderly grooming, enter enable. To disable orderly grooming, enter disable. The default configuration disables orderly grooming.
Chapter 8 Managing PNNI Nodes and PNNI Routing Managing Connection Grooming Note The trunk utilization limit applies only to connections being groomed. It does not apply to connections that are rerouted due to failures. The default trunk utilization limit is 100 percent, and this imposes no restriction on grooming. To change the trunk utilization limit, enter the cnfndrteopt command as follows: M8850_LA.7.PXM.a > cnfndrteopt [-trkutil value] The trunk utilization value range is 5 to 100 percent.
Chapter 8 Managing PNNI Nodes and PNNI Routing Managing Connection Grooming The following example shows the display when the dsprteoptcnf command is entered without a port ID. PXM1E_SJ.7.PXM.
Chapter 8 Managing PNNI Nodes and PNNI Routing Managing Connection Grooming Displaying Nodal Grooming Configuration Parameters To display nodal grooming configuration parameters, enter the dspndrteopt command as shown in the following example: PXM1E_SJ.7.PXM.
Chapter 8 Managing PNNI Nodes and PNNI Routing Managing Connection Grooming When configuring the AIS delay, consider the following guidelines: • The AIS delay timer applies only to persistent (double-ended) P2P connections. • The AIS delay timer only applies during connection grooming. If an AIS is generated for another reason, such as a failed link, the AIS is sent immediately.
Chapter 8 Managing PNNI Nodes and PNNI Routing Displaying Node Configuration Information The default configuration (auto) automatically blocks IE forwarding on UNI and IISP interfaces and forwards the IE on NNI and AINI interfaces. You can also configure any port to allow (allowed) or disallow (disallowed) soft reroute IE forwarding. Step 4 To verify your change, enter the dsppnportie command as described in Step 2 of this procedure.
Chapter 8 Managing PNNI Nodes and PNNI Routing Displaying Node Configuration Information Displaying the PNNI Summary Address Use the dsppnni-summary-addr command to display PNNI summary addresses as follows: mgx8830a.1.PXM.a > dsppnni-summary-addr [node-index] If you specify the node-index, this command displays the summary address prefixes of the node-index PNNI node. If you do not specify the node-index, this command displays summary address prefixes for all local nodes on network.
Chapter 8 Managing PNNI Nodes and PNNI Routing Displaying Node Configuration Information The following example shows the report for this command: mgx8830a.1.PXM.a > dsppnsysaddr 47.0091.8100.0000.0030.ff0f.ef38.0000.010b.180b.00/160 Type: host Port id: 17251106 47.0091.8100.0000.0030.ff0f.ef38.0000.010b.1816.00/160 Type: host Port id: 17251106 47.0091.8100.0000.0030.ff0f.ef38.0000.010b.1820.00/160 Type: host Port id: 17251106 47.0091.8100.0000.0030.ff0f.ef38.0000.010b.1821.
Chapter 8 Managing PNNI Nodes and PNNI Routing Displaying Node Configuration Information Table 8-17 Objects Displayed for the dsppnni-intf Command Parameter Description portid The Port Identifier. token The 32-bit number used for link aggregation purpose. aw The 24-bit number used as administrative weight on this interface. The maximum possible value is a 24-bit unsigned integer. Displaying the PNNI Link Table Enter the dsppnni-link command to show the PNNI link table. mgx8830a.1.PXM.
Chapter 8 Managing PNNI Nodes and PNNI Routing Displaying Node Configuration Information Remote Remote Upnode Upnode Common Hello pkt TX......... 19582 node name.......SanJose node id.........56:160:47.00918100000000309409f1f1.00309409f1f1.01 id..............0:0:00.000000000000000000000000.000000000000.00 ATM addr........00.000000000000000000000000.000000000000.00 peer group id...00:00.00.0000.0000.0000.0000.0000.00 node index : 1 Local port id: 17504289 Remote port id: 17045537 Local Phy Port Id: 11:2.
Chapter 8 Managing PNNI Nodes and PNNI Routing Displaying Node Configuration Information Table 8-18 Objects Displayed for the dsppnni-routing-policy Command (continued) Parameter Description Load balance Defines the load balancing rule if alternative equal-cost routes exist for a given call request. Ondemand Routing The on-demand routing rule, which is either firstfit or bestfit. Firstfit routing selects the first route found that goes to the selected destination.
Chapter 8 Managing PNNI Nodes and PNNI Routing Displaying Node Configuration Information Table 8-19 Objects Displayed for the dsppnni-svcc-rcc-timer Command (continued) Parameter Description Retry time The amount of time (in seconds) this node will delay after an apparently still necessary and viable SVCC-based RCC is unexpectedly torn down, before attempting to re-establish it. The range is from 10 to 60.
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 4 To verify that the new address has been assigned, enter the dspatmaddr command. Replace with the appropriate port identifier in the format slot:bay.line:ifnum. In the following example, the user displays the ATM address for port 2:2.2:1: mgx8830a.1.PXM1.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.
Chapter 8 Managing PNNI Nodes and PNNI Routing Managing CUGs Table 8-20 addcug/dspcug Command Parameters and Options 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 prefix or address 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 Displaying CUG Configuration Data The following procedure describes how to display CUG configuration information. Step 1 To display any addresses assigned to an interface, enter the dspaddr command. Replace with the appropriate port identifier in the format slot:bay.line:ifnum, as shown in the following example: mgx8830a.1.PXM1.a > dspaddr 3:1.7:7 47.1111.1111.1111.1111.1111.1111.1111.1111.1111.
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 Note The dspaddrcug command parameters are described in Table 8-20. 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.
Chapter 8 Managing PNNI Nodes and PNNI Routing Managing CUGs Deleting a CUG Assignment A CUG assignment is made when the addcug command is used to assign a user to a CUG. To delete a single CUG assignment, use the following procedure. 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.
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 The gateway node contains information only for the nodes which are up and reachable when you add the gateway node into a peer group. It is not necessary to create a gateway node before creating a peer group, because the database contains all the reachable nodes that were in the peer group when it was first added.
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 Shelf The feeder’s shelf numbers, which identify the port on the feeder itself. Feeder Slot The feeder’s slot number, which identify the port on the feeder itself. Feeder Port The feeder’s port numbers, which identify the port on the feeder itself. Feeder model number The feeder’s model number.
Chapter 8 Managing PNNI Nodes and PNNI Routing Maintaining a Persistent Network Topology for CWM Enter the dsptopolinklst command to display link information for all links in the topology database, as shown in the following example. M8830_CH.1.PXM.a > dsptopolinklist Number of Link Entries in Persistent Topo DataBase = 21 Persistent Topo Link Index: 1 Local Node Id : 56:160:47.00918100000000001a533377.00001a533377.01 Remote Node Id : 56:160:47.00918100000000036b5e31b3.00036b5e31b3.01 Local Port Id : 7:2.
Chapter 8 Managing PNNI Nodes and PNNI Routing Maintaining a Persistent Network Topology for CWM Displaying Feeder Information The feeder database contains information about feeder nodes and nodes attached to XLMI links. Enter the dsptopofdrlst command to display information about all feeder nodes in the topology database, as shown in the following example. M8830_CH.1.PXM.
Chapter 8 Managing PNNI Nodes and PNNI Routing Maintaining a Persistent Network Topology for CWM Note Cisco recommends that you avoid using PXM1E nodes as gateway nodes due to memory limitation. Note Cisco recommends that you configure two gateway nodes for each SPG network or lowest level peer groupings of MPG. If one node goes down, CWM can pick the other node and start using it.
Chapter 8 Managing PNNI Nodes and PNNI Routing Maintaining a Persistent Network Topology for CWM Use the following procedure to delete a node from the topology database. Step 1 Physically remove the node from the network by disconnecting the cables, downing all the links between that node and the network, or powering down that node. Caution Wait for at least one hour before proceeding to Step 2.
Chapter 8 Managing PNNI Nodes and PNNI Routing Maintaining a Persistent Network Topology for CWM 8-74 Cisco MGX 8850 (PXM1E/PXM45), Cisco MGX 8950, Cisco MGX 8830, and Cisco MGX 8880 Configuration Guide Release 5.0.10, OL-3845-01 Rev.
C H A P T E R 9 2 3 Switch Operating Procedures This chapter describes procedures you can use to manage the Cisco MGX 8830, Cisco MGX 8850 (PXM1E/PXM45), and Cisco MGX 8950 switches and the Cisco 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 When you save a configuration, the switch saves all configuration data, including the software revision levels used by the cards in the switch. The saved configuration file does not include the boot and runtime software files. Should you need to restore a configuration, the restoreallcnf command restores the configuration exactly as it was when the configuration file was saved.
Chapter 9 Switch Operating Procedures Managing the Configuration Files The following example shows what appears on the switch when the saveallcnf command is used without the -v option: M8950_SF.7.PXM.a > saveallcnf 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.
Chapter 9 Switch Operating Procedures Managing the Configuration Files Step 4 In preparation for viewing the saved configuration file, enter the cd C:CNF/ command to go to the directory where the file was saved. M8850_NY.7.PXM.a > cd C:CNF/ Step 5 To verify the file is there, enter the ll command to list the directory contents. M8950_SF.7.PXM.a > ll Listing Directory .
Chapter 9 Switch Operating Procedures Managing the Configuration Files Note When replacing a T1 or T3 card with a E1 or E3 card, or vice versa, you must enter the clrsmcnf command on the appropriate slot before you install the replacement card. 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.
Chapter 9 Switch Operating Procedures Managing the Configuration Files Caution Restoring a configuration replaces the existing configuration with the saved configuration. If there are configuration changes (such as MPSM license additions) that have been made since the last configuration save, those changes will be lost. 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.
Chapter 9 Switch Operating Procedures Managing ILMI Note If there were any license additions, deletions, or transfers performed after saving the restored configuration, the switch generates a minor license alarm if the number of licenses detected does not match the number of licenses restored. For more information, see Appendix F, “MPSM Licensing”.
Chapter 9 Switch Operating Procedures Managing ILMI Step 3 To verify the ILMI status change, re-enter the dsppnports command. 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.
Chapter 9 Switch Operating Procedures Managing ILMI mgx8830a.1.PXM.a > dspilmi 1 1 Sig. Port ---1 Step 4 rsrc Ilmi Sig Sig Ilmi S:Keepalive T:conPoll K:conPoll Part State Vpi Vci Trap Interval Interval InactiveFactor ---- ---- ---- ---- --- ------------ ---------- ---------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 VPI: 0 VCI: 16 Max Prefix: 16 Total Prefix: 0 Max Address: 64 Total Address: 0 Resync State: 0 Node Prefix: yes Peer Port Id: 16848897 System_Id : 0.80.84.171.226.192 Peer Addressreg: enable Peer Ip Address : 0.0.0.0 Peer Interface Name : atmVirtual.01.1.1.
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.0.00 and the Release Notes for the Cisco MGX 8880 Media Gateway, Release 5.0.00. If the release notes are not available, you can use the firmware filename to determine the version number as described below.
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 above, 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 Displaying Software Revisions in Use To display the boot and runtime software version in use on every card in the switch, enter the dsprevs command as shown in the following example: mgx8830a.1.PXM.a > dsprevs Unknown MGX8830 Phy. Log. Inserted Slot Slot Card ---- ---- -------- Cur Sw Revision -------- Boot FW Revision -------- 01 02 03 04 05 06 07 08 09 10 11 12 13 14 3.0(0.26)P4 3.0(0.26)P4 ------------------------- 3.
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: mgx8830a.1.PXM.a > dspred Unknown System Rev: 03.00 May.
Chapter 9 Switch Operating Procedures Managing Redundant APS Lines Replace with the card number of the active card, and replace with the card number to which you want to switch control. Removing Redundancy Between Two Cards To remove the redundant relationship between two service modules, use the following procedure. Step 1 Establish a configuration session using a user name with GROUP1_GP privileges or higher.
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 Cisco MGX 8850 (PXM1E) switches, and for line redundancy on PXM1E-8-155 cards in Cisco MGX 8850 (PXM1E) and Cisco 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 Replace with the slot, bay, and line id of the APS line you want to display. After you enter the command, the switch displays a report similar to the following: 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 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. Set up a secondary server (or several secondary servers), which serves as a backup server if the SNTP client cannot reach the primary server. 3. Configure the network client.
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 Cisco MGX 8850 (PXM1E/PXM45) and Cisco MGX 8950 switches, the port identifier is 7.35 or 7.36. For clocking ports on Cisco 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 Configuring an NCDP Port Once you enable NCDP on your node, NCDP is automatically enabled on all the node’s NNI ports. You can alter the default NCDP port configuration through the cnfncdpport command, as shown in the following example: M8850_LA.8.PXM.a > cnfncdpport 1:2.2:2 -ncdp enable -vpi 0 -vci 32 -admincost 1 -pcr 200 -scr 100 -mbs 50 Table 9-15 describes the cnfncdpport command options.
Chapter 9 Switch Operating Procedures Managing NCDP Clock Sources Table 9-15 cnfncdpport Command Parameters (continued) Parameter Description -scr Specifies the SCR 2 for the port. Default = 150 cells per second -mbs Specifies the MBS3 for the port. Default = 100 cells 1. PCR = peak cell rate 2. SCR = sustained cell rate 3. MBS = maximun burst size Enter the dspncdpport command to verify that the NCDP parameters were set properly. M8850_LA.8.PXM.a > dspncdpport 1:2.
Chapter 9 Switch Operating Procedures Managing NCDP Clock Sources Note When the switch is configured for manual clock distribution, the only parameter that is useful in the dspncdp display is the Distribution Mode. Table 9-16 describes the objects displayed by the dspncdp command. Table 9-16 dspncdp Command Objects 9-36 Parameter Description Distribution Mode Current enabled method of clock distribution. If the method chosen is manual, NCDP is turned off, and vice-versa.
Chapter 9 Switch Operating Procedures Managing NCDP Clock Sources Table 9-16 dspncdp Command Objects (continued) Parameter Description Last clk src change time Time when the root clock source last changed. Last clk src change reason Reason why the root clock source last changed. Display A Specific NCDP Clock Source Enter the dspncdpclksrc command to display configuration information about a specific NCDP clock sources on the network. M8850_LA.8.PXM.a > dspncdpclksrc 7.
Chapter 9 Switch Operating Procedures Managing NCDP Clock Sources Display All NCDP Clock Sources Enter the dspncdpclksrcs command to display all configured NCDP clock sources on the network. M8850_LA.8.PXM.a > dspncdpclksrcs PortId 7.35 (e1) 7.36 (e1) 255.255 Best clk src No No Yes Priority 100 128 128 Stratum level 2 3 3 Prs id 0(external) 0(external) 255(internal) Health Bad Bad Good M8850_LA.8.PXM.a > Table 9-18 describes the objects displayed by the dspncdpclksrcs command.
Chapter 9 Switch Operating Procedures Managing NCDP Clock Sources Display All NCDP Ports on the Switch Enter the dspncdpports command to display general details about all signaling ports for NCDP. U1.8.PXM.a > dspncdpports PortId 6:1.1:1 6:1.1:2 6:1.1:3 Clock mode disable disable disable Clock Vpi 0 0 0 Clock Vci 34 34 34 Admin Cost 10 10 10 Ncdp Vc down down down Table 9-19 describes the objects displayed by the dspncdpports command.
Chapter 9 Switch Operating Procedures Managing NCDP Clock Sources Table 9-20 dspncdpport Command Objects Parameter Description PCR Displays the PCR 1 for the port. SCR Displays the SCR 2 for the port. MBS Displays the MBS3 for the port. 1. PCR = peak cell rate 2. SCR = sustained cell rate 3. MBS = maximun burst size Deleting an NCDP Clock Source Enter the delncdpclksrc [clocktype ] command to delete a clock source from the network.
Chapter 9 Switch Operating Procedures Managing Manually Configured Clocks Sources In the following example, the user deletes the clock source from the E1 port number 7.35 on a Cisco MGX 8850 (PXM45) switch. M8850_LA.8.PXM.a > delncdpclksrc 7.35 M8850_LA.8.PXM.a > Managing Manually Configured Clocks Sources The following sections provide commands and procedures for managing manually configured clock source.
Chapter 9 Switch Operating Procedures Managing Manually Configured Clocks Sources Reconfigure Manual Clock Sources The procedure you use to reconfigure a clock source depends on whether or not you need to change the role of the clock source.
Chapter 9 Switch Operating Procedures Displaying SVCs To reconfigure a BITS clock source, see the “Manually Configuring BITS Clock Sources” section in Chapter 2, “Configuring General Switch Features.” To reconfigure a PXM1E line clock source, see the “Configuring PXM1E Line Clock Sources” section in Chapter 3, “Provisioning PXM1E Communication Links.” To reconfigure an AXSM line clock source, refer to the Cisco ATM Services (AXSM) Configuration Guide and Command Reference for MGX Switches, Release 5.
Chapter 9 Switch Operating Procedures Managing Controllers Adding Controllers To add a controller, use the following procedure. Step 1 Establish a configuration session at any user access level. Step 2 Enter the addcontroller command to add a controller to the node. mgx8830a.1.PXM.a > addcontroller i [cntrlrName} Table 9-22 describes the parameters for this command.
Chapter 9 Switch Operating Procedures Viewing an ATM Port Configuration MGX8850.7.PXM.a > dspcontrollers Controller Bay Number: Controller Line Number: Controller VPI: Controller VCI: Controller In Alarm: Controller Error: MGX8850 MGX8850 Number of Controllers: Controller Name: Controller Id: Controller Location: Controller Type: Controller Logical Slot: 0 0 0 0 NO System Rev: 02.00 Jul.
Chapter 9 Switch Operating Procedures Managing PXM1E Partitions This command displays all configured ports on the PXM1E or AXSM card. Port numbers are listed in the ifNum (interface number) column. The interfaces listed include UNI and NNI ports. Note the number of the port for which you want to view the configuration. Step 3 To display the port configuration, enter the following command: mgx8830a.1.PXM.a > dspport Replace ifNum with the number assigned to the port during configuration.
Chapter 9 Switch Operating Procedures Managing PXM1E Partitions Step 3 To display the configuration of a resource partition, note the interface and partition numbers and enter the following command: mgx8830a.1.PXM.a > dsppart Replace ifnum with the interface number of the port, and replace partitionID with the partition number assigned to the port. The following example shows the report provided by the dsppart command. mgx8830a.1.PXM.
Chapter 9 Switch Operating Procedures Managing PXM1E Partitions Table 9-23 Parameters for the cnfpart 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. controllerNum Controller number. 1 = PAR (Portable AutoRoute)—Not supported in this release. 2 = PNNI—Only PNNI is supported in this release.
Chapter 9 Switch Operating Procedures Managing PXM1E Partitions Table 9-23 Parameters for the cnfpart Command (continued) Parameter Description minVpi Minimum VPI number for this port. For UNI ports, enter a value in the range from 0 to 255. For NNI ports, enter a value in the range from 0 to 4095. Note maxVpi Maximum VPI number for this port. For UNI ports, enter a value in the range from 0 to 255. For NNI ports, enter a value in the range from 0 to 4095.
Chapter 9 Switch Operating Procedures Managing PXM1E Partitions Table 9-23 Parameters for the cnfpart Command (continued) Parameter Description ingPctBw Percentage of ingress bandwidth available to the connection. Range: 0–100 percent. Note egrPctBw Percentage of egress bandwidth available to the connection. Range: 0–100 percent. Note Step 4 This parameter applies only to FRSM12 cards. To display the changed partition configuration, enter the dsppart command as described in the previous section.
Chapter 9 Switch Operating Procedures Removing Static ATM Addresses Step 4 To display the active connections, enter the following command: mgx8830a.1.PXM.a > dspcons The following is a sample dspcons display. mgx8830a.1.PXM.a > dspcons Local Port Vpi.Vci Remote Port Vpi.Vci State Owner Pri Persistency ----------------------+------------------------+---------+-------+---+----------3:1.1:1 102 102 Routed 102 102 FAIL MASTER 3 Persistent Local Addr: 47.00918100000100001a531c2a.000001031801.
Chapter 9 Switch Operating Procedures Configuring VPI and VCI Ranges for SVCs and SPVCs Table 9-24 ATM Address Configuration Parameters Parameter Description portid Port identifier in the format slot:bay.line:ifnum. These parameters are described in Table 9-1. 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 9 Switch Operating Procedures Configuring VPI and VCI Ranges for SVCs and SPVCs Step 4 Enter configure the port range, enter the following command: mgx8830a.1.PXM.
Chapter 9 Switch Operating Procedures Managing Path and Connection Traces After you enter this command, the switch displays a report similar to the following example: mgx8830a.1.PXM.a > dsppnportrange 1:2.1:2 minSvccVpi: minSvccVci: minSvpcVpi: 0 35 1 maxSvccVpi: maxSvccVci: maxSvpcVpi: 4095 65535 4095 Managing Path and Connection Traces Cisco MGX switches support the following traces: • path traces — the trace occurs only during call setup.
Chapter 9 Switch Operating Procedures Managing Load Sharing Replace portid using the format slot:bay.line:ifNum. Table 9-1 describes these parameters. The -X parameter ensures that calls will be cleared once they reach the destination specified in the portid parameter. Managing Load Sharing When redundant PXM cards are used, load sharing enables traffic routing through the switch fabric on both PXM cards, doubling the capacity of the switch.
Chapter 9 Switch Operating Procedures Managing Telnet Access Features Note You must enter values for all command parameters, even if you want to change only one of them. Table 9-27 describes the parameters for this command. Table 9-27 Command Parameters for cnfxbarmgmt Parameter Description loadSharing Enables or disables load sharing. Enter -1, 0, or 1.
Chapter 9 Switch Operating Procedures Managing Telnet Access Features Starting a Telnet Session from a Workstation For instructions on starting a Telnet session from a workstation, see “Starting a CLI Telnet Session” in Appendix C, “Supporting and Using Additional CLI Access Options.” Starting and Managing Telnet Sessions Between Switches The Cisco MGX switches support Telnet sessions between switches.
Chapter 9 Switch Operating Procedures Managing Telnet Access Features Returning to a Previous Session After you Telnet from one switch to another, enter the bye command or the exit command to close the current session and return to the previous session. For example, if you telnet from Switch A to Switch B to Switch C, the bye command will terminate the session on Switch C and display the session on Switch B.
Chapter 9 Switch Operating Procedures Managing Telnet Access Features If you are using SSH client software to access Cisco MGX switches, consider disabling Telnet client access so that the switch accepts only secure sessions. To disable Telnet client access, enter the cnfndparms command, select option number for Telnet Access To Node Disabled, and confirm the action (Y) as shown in the following example: PXM1E_SJ.7.PXM.
Chapter 9 Switch Operating Procedures Starting and Managing Secure (SSH) Access Sessions Between Switches In the next example, a Telnet client on one switch attempts to connect to a switch on which Telnet access is disabled: PXM1E_SJ.7.PXM.a > telnet 172.29.52.56 Trying 172.29.52.56... Connected to 172.29.52.56. Escape character is ^] Err: access denied Connection closed by foreign host. To display the configuration for Telnet client access, enter the dspndparms command as described in the next section.
Chapter 9 Switch Operating Procedures Starting and Managing Secure (SSH) Access Sessions Between Switches Starting a Secure Session Between Switches To start a secure session, enter the ssh command as follows: mgx8830a.1.PXM.a > ssh [-l username] [-v] [-V] [-q] [-e] [-p] [-1] [-2] [username@]host [command] Table 9-28 describes the parameters for this command. Table 9-28 Command Parameters for ssh Parameter Description -l username Specifies a username for login on the remote host.
Chapter 9 Switch Operating Procedures Starting and Managing Secure (SSH) Access Sessions Between Switches Table 9-28 Command Parameters for ssh (continued) Parameter Description host Replace host with the IP address of the remote switch. If a remote switch name is associated with an IP address in the local hosts file, you can enter a name instead of the IP address. Note command If your IP configuration supports it, you can establish a secure session with the active or the standby PXM.
Chapter 9 Switch Operating Procedures Managing Remote (TACACS+) Authentication and Authorization 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.88 closed by remote host. Connection to 172.29.52.88 closed. M8850_NY.7.PXM.
Chapter 9 Switch Operating Procedures Managing Remote (TACACS+) Authentication and Authorization The exact procedure for configuring the AAA server can be found in the documentation for that product. The following is a list of the general tasks that need to be performed: • Install the AAA server. • Configure the AAA server to use the TACACS+ protocol. • Configure the AAA server IP address and provide it to the person that configures the Cisco MGX switch.
Chapter 9 Switch Operating Procedures Managing Remote (TACACS+) Authentication and Authorization Table 9-29 Parameters for cnfaaa-server Command (continued) Parameter Description timeout The optional timeout parameter specifies how long the switch will wait for an authentication or authorization response from a server.
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 The following example configures authentication through the tacacs+ method: M8830_SF.2.PXM.
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 Displaying the TACACS+ Configuration To display the complete authentication and authorization configuration, enter the dspaaa command as shown in the following example: M8830_SF.2.PXM.a > dspaaa AAA CONFIGURATION: Authentication Methods Authorization Methods Authorization Type Default Privilege Level Prompt Display SSH/FTP Message Type IOS Exclusion List TACACS+ SERVERS: IP Address ---------------172.29.52.
Chapter 9 Switch Operating Procedures Managing Remote (TACACS+) Authentication and Authorization Tip For more information on the dspaaa-stats command display, refer to the Cisco MGX 8850 (PXM45/PXM1E), Cisco MGX 8950, Cisco MGX 8830, and Cisco MGX 8880 Command Reference, Release 5. The following example shows what appears when the command is entered without additional parameters: M8830_CH.1.PXM.a > dspaaa-stats Last cleared on: 04/01/2004 04:46:53 (GMT) Last good login authen: cisco telnet.01 10.21.
Chapter 9 Switch Operating Procedures Verifying PXM Disk Data None Type to continue, Q to stop: ____Server Messages RX____ None 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.
Chapter 9 Switch Operating Procedures Verifying PXM Disk Data Enter the verifydiskdb check [-l ] [-s ] [-p ] command at the active PXM to run the disk verification utility. Table 9-31 describes the possible options for the verifydiskdb check command. Note Cisco recommends that you run the disk verification utility during a time when there is minimal activity on the switch. Table 9-31 describes the possible options for the verifydiskdb check command.
Chapter 9 Switch Operating Procedures Verifying PXM Disk Data The disk verification task runs in the background until completion. It can take a few seconds or several hours for the disk verification task to finish. The more connections configured on the switch, the longer it takes the utility to complete disk verification. To view the progress of the disk verification task, enter the verifydiskdb status command while the verification task is running. pop20two.7.PXM.
Chapter 9 Switch Operating Procedures Verifying PXM Disk Data To view the disk verification utility log file, enter the verifydiskdb display command as shown in the following example. pop20two.7.PXM.a > verifydiskdb display If you want to view an older log file, enter the verifydiskdb display command with the -l old option, as shown in the following example. pop20two.7.PXM.a > verifydiskdb display -l old Note The directory only keeps two log files per slot.
Chapter 9 Switch Operating Procedures Verifying PXM Disk Data If the verification utility is run on a slot in which no card resides, the display will show that the slot is invalid and has been skipped as shown in the following example: ------------------------------------------------------------------------------- Information for Slot 2 -----------------Start: 22/05/2002-10:31:10 End: 22/05/2002-10:31:10 Verify SKIPPED - INV_SLOT TotalofDbs= 0, TotalofTbls= 0, #DbVerf=0, #TblVerf= 0 No Discrepancies found
Chapter 9 Switch Operating Procedures Verifying PXM Disk Data dbInd: 1 - dbName: sm_mib_v21 tblInd: 5 - tblName: mib29 Record: 1785 ActvComdID: 0 StdbyComID: 7 ============================================================= dbInd: 1 - dbName: sm_mib_v21 tblInd: 5 - tblName: mib29 Record: 1786 ActvComdID: 0 StdbyComID: 7 ============================================================= dbInd: 1 - dbName: sm_mib_v21 tblInd: 5 - tblName: mib29 Record: 1787 ActvComdID: 0 StdbyComID: 7 =============================
Chapter 9 Switch Operating Procedures Configuring a Line Loopback Configuring a Line Loopback If a connection fails and you do not know which end of the connection is causing the problem, putting a line into loopback mode can help you determine what the problem is and where it occurs on a connection. In an MGX 8830, an MGX 8850, or an MGX 8880, loopback lines provide CLI-based line level monitoring capabilities.
Chapter 9 Switch Operating Procedures Managing Bit Error Rate Tests Note Before you can change the loopback type for an existing loopback, you must first delete the loopback by executing dellnloop, or you can just enter the addlnloop command with the -lpb 1 (No loopback) option. Configuring a Line Loopback on a Service Module Once your physical line is connected, you can perform a loopback test using the following procedure.
Chapter 9 Switch Operating Procedures Managing Bit Error Rate Tests Note Step 3 BERT commands are available only on PXM1E and PXM45 cards. However, you can run BERT on any service modules that support T1 lines or IMA. Enter the dspbertcap command to display the loopback and BERT capabilities of a specific line or port on the current card. The display shows you which test patterns and loopback numbers are available on the current service module.
Chapter 9 Switch Operating Procedures Managing Bit Error Rate Tests Table 9-34 cnfbert Command Parameters singleBitErrInsert Different options of error insertion rates, where singleBitErrInsert is “1” (noError), or “| 2" (insert). Note Injection of bit error should be done after configuring BERT dropIteration where dropIteration is between 1 and 32, if loopback is 5:latchDS0Drop. used only enable Enables/disables BERT. Enter “4” to enable BERT or “6” to disable BERT.
Chapter 9 Switch Operating Procedures Managing PXM1E and AXSM Card Diagnostics 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. In the following example, the user deletes BERT from line 1 on port 2 in the PXM1E in slot 7. Unknown.7.PXM.a > delbert 7.1.1 2. Enter the cnfbert command with the -en option disabled.
Chapter 9 Switch Operating Procedures Managing PXM1E and AXSM Card Diagnostics Configuring Offline and Online Diagnostics Tests on PXM1E and AXSM Cards Enter the cnfdiag command as follows to enable online diagnostics tests on PXM1E or AXSM cards: MGX.7.PXM.a > cnfdiag [ ] Table 9-35 tells you how to set these parameters to run online diagnostics tests on PXM1E and AXSM cards.
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-4 Configuring online diagnostics only In the following example, the user enables online diagnostics only for all cards in the switch. Unknown.7.PXM.a > cnfdiagall 7 enable disable Example 9-5 Configuring offline diagnostics only In the following example, the user enables online diagnostics for all cards in the switch.
Chapter 9 Switch Operating Procedures Managing PXM1E and AXSM Card Diagnostics The following example shows the information displayed by the dspdiagcnf command. Unknown.7.PXM.
Chapter 9 Switch Operating Procedures Managing PXM1E and AXSM Card Diagnostics Displaying Online Diagnostic Errors Enter the dspdiagerr online command to display the current online diagnostics errors for all cards in a switch. Unknown.7.PXM.
Chapter 9 Switch Operating Procedures Managing PXM1E and AXSM Card Diagnostics 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 To configure ATM cell layer parameters on an IMA group, enter the cnfatmimagrp command as follows: cnfatmimagrp -grp -sps -ais In the following example, the user enables payload scrambling and AIS on the ATM IMA group 14 on the PXM1E in the lower bay. Unknown.7.PXM.a > cnfatmimagrp -grp 2.14 -sps 1 -ais 1 Table 9-37 describes the parameters for the cnfimagrp command.
Chapter 9 Switch Operating Procedures Managing IMA Managing IMA The sections that follow describe how to do the following tasks: • Display IMA groups • Display IMA links • Delete IMA groups • Deleting IMA links • Restart an IMA group Displaying IMA Groups To display general information about all configured IMA groups on the current PXM1E-16-T1E1, AXSM-32-T1E1-E, or AUSM/B card, enter the dspimagrps command, as shown in the following example: Unknown.7.PXM.
Chapter 9 Switch Operating Procedures Managing IMA Diff Delay Max (msecs) Diff Delay Max Observed (msecs) Accumulated Delay (msecs) Clear Accumulated Delay Status GTSM Up Integ Time (msecs) 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 Label Rx OAM Label Test Pattern Procedure Status Test Link Test Pattern Stuff Cell Indication (frames) Version Fal
Chapter 9 Switch Operating Procedures Managing IMA Deleting an IMA Group To delete an IMA group, enter the delimagrp . Replace bay with the number 1 to specify the top bay, or 2 to specify the lower bay. Replace group with the IMA group number you want to delete. In the following example, the user deletes the IMA group 3 in the lower bay. Unknown.7.PXM.a > delimagrp 2.3 Enter the dspimagrps command to ensure that the correct IMA link is deleted.
Chapter 9 Switch Operating Procedures Managing IMA In Figure 9-3, one link in IMA Group A is operating in loopback mode, and the other three lines are operating correctly. If different IMA group IDs are configured at each end of the IMA links (cnfimagrp -txid), the switch can easily determine which links are in loopback and which links are connected to the far end. If the received far-end ID is the same as the near-end ID, the link is in loopback.
Chapter 9 Switch Operating Procedures Managing IMA Step 1 Establish a configuration session with the active PXM1E-16-T1E1 using a user ID with GROUP1 privileges or higher. Step 2 Enter the dspimaparms command as shown in the following example to determine whether the autorestart feature is enabled on the switch. M8830_CH.1.PXM.
Chapter 9 Switch Operating Procedures Managing IMA Note Step 6 The cnfimagrp command provides additional parameters. All cnfimagrp parameters are described in Table 3-5. To verify an IMA group configuration change, enter the dspimagrp command. Displaying the IMA Group Autorestart Configuration and State Starting with Release 5, three new rows have been added to the dspimagrp command to show the autorestart state for an 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 Cisco MGX 8850 (PXM1E/PXM45) or Cisco MGX 8830 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 Table 10-2 Mastership Assignment to PXM Card Sets after Nativity Check (continued) Primary Slot 1 Secondary Slot2 Front card non-native Both cards non-native, matched serial numbers Hard disk card non-native Both cards non-native, mismatched serial numbers Nativity Status Both cards non-native Hard disk card non-native No active card set. Secondary 2 card set is active. No active card set. No active card set. No active card set.
Chapter 10 Switch Maintenance Procedures Replacing Cards To rebuild the configuration from a configured PXM45 hard disk card in the switch, do the following tasks: • Clear the configuration (clrallcnf) on the PXM45 front card using a PXM hard disk card for which the configuration can be erased. (Do not use the PXM45 slot that hosts the configuration you want to use.) • Install the unconfigured PXM45 front card and the configured PXM45 hard disk card in a chassis without a redundant card set.
Chapter 10 Switch Maintenance Procedures Replacing Cards PXM1E-4-155 card. You also need to ensure that you have the proper type of LC cable. If you will be connecting the LC cable to an SC connector, you need an SC conversion cable that has an LC connector on one end, and an SC connector on the other end. If you will be connecting the LC cable to another LC connector, you need a cable with an LC connector on both ends.
Chapter 10 Switch Maintenance Procedures Replacing Cards Note Step 6 Cisco recommends that you install FRUs on the PXM1E-8-155 ports that correspond to the configured ports on the removed standby PXM1E-4-155 back card. For example, if you had a physical SC line connected to port 1 on the removed standby PXM1E-4-155 back card, you need to install a FRU on port 1 of the installed SFP-8-155 back card. Insert the PXM1E-8-155 card set into the appropriate slots.
Chapter 10 Switch Maintenance Procedures Replacing Cards Warning Ensure that the new back cards are firmly screwed into the chassis by gently tugging on them. If one of the standby back cards feels loose, or if the standby back cards are seated slightly higher or lower in the chassis than the active back cards, the new back cards may not be seated properly. Step 16 Remove any Y-cables and straight cables connected to the removed standby PXM1E-4-155 back card.
Chapter 10 Switch Maintenance Procedures Replacing Cards Step 4 If you are installing an SFP-8-155 back card, insert FRU connectors into the appropriate ports on the back card before installing new card set into the switch. If you are installing an MCC-8-155 back card, skip Step 4 and move on to Step 5. Note Cisco recommends that you install FRUs on the PXM1E-8-155 ports that correspond to the configured ports on the removed standby PXM1E-4-155 back card.
Chapter 10 Switch Maintenance Procedures Replacing Cards Replacing PXM1E SC Cables with LC Cables via SC Conversion Cables When performing a graceful upgrade of a PXM1E-4-155 card set that uses SC cables to a PXM1E-8-155 card set, you will need to install SC conversion cables to complete the upgrade. SC conversion cables have an LC connector on one end, and an SC connector on the other. The LC connector fits into the FRUs you install in the SFP-8-155 back card.
Chapter 10 Switch Maintenance Procedures Replacing Cards Figure 10-2 Standby SFP-8-155 Back Card with SC Conversion Cable SFP-8-155 back card PXM1E-4-155 back card LC SC SC conversion cable SC 93339 SC cable Step 3 After you have installed the second SFP-8-155 back card, install the SC conversion cable or cables into the appropriate FRU or FRUs, just as you did in Step 2. The configuration should look similar to Figure 10-3.
Chapter 10 Switch Maintenance Procedures Replacing Cards Replacing PXM45/A or PXM45/B Cards with PXM45/C Cards PXM45/A and PXM45/B front cards can be replaced with PXM45/C cards while the switch is operating. If a PXM45 is operating in standalone mode, all calls are interrupted until the PXM45 is replaced and the PXM45/C card is operating correctly. If the switch is using redundant PXM45s, enter the switchcc command, if necessary, to ensure that the card you want to replace is operating in standby mode.
Chapter 10 Switch Maintenance Procedures Replacing Cards Non-gracefully Upgrade a Single PXM45 to a PXM45/C To non-gracefully upgrade from a single PXM45 to a PXM45/C, 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 Step 1 Determine if you need to upgrade the AXSM runtime software before or after the hardware upgrade. For information on the runtime software required, refer to the Release Notes for Cisco MGX 8850 (PXM1E/PXM45), Cisco MGX 8950, and Cisco MGX 8830 Switches, Release 5.0.00 or the Release Notes for the Cisco MGX 8880 Media Gateway, Release 5.0.00. Step 2 Replace the standby AXSM with the AXSM/B card.
Chapter 10 Switch Maintenance Procedures Replacing Cards The configuration for AXSM cards is stored on the PXM45. The switch will configure the new AXSM/B card and bring it up in standby mode. In standby mode, the card will operate as an AXSM/A card. Step 4 Note Enter the dspcd or dsprev command to verify that the AXSM/B card is using the correct boot software version. The switch automatically selects and loads the correct runtime software for the AXSM based on the configuration for that slot.
Chapter 10 Switch Maintenance Procedures Replacing Cards Replacing Eight-Port T1 and E1 Service Modules with MPSM-8-T1E1 The MPSM-8-T1E1 card is designed to replace older eight-port T1 and E1 service modules designed to provide ATM, circuit emulation, and Frame Relay services. The following sections list the cards that can be upgraded to MPSM-8-T1E1 and the procedures for upgrading cards that are operating in standalone and redundant configurations.
Chapter 10 Switch Maintenance Procedures Replacing Cards Step 4 Use the loadrev command to prepare the standalone service module slot for the MPSM software. The command format is: M8850_SF.7.PXM.a > loadrev mpsm Replace the slotNo variable with the slot number for the legacy service module, and replace the mpsm-rev variable with the version number of the MPSM software.
Chapter 10 Switch Maintenance Procedures Replacing Cards The following procedure describes how to upgrade the secondary card in a redundant configuration to MPSM-8-T1E1. Step 1 If you have not done so already, upgrade the PXM software to a version that supports the MPSM software you will be using. For more information, refer to the Release Notes for Cisco MGX 8850 (PXM1E/PXM45), Cisco MGX 8950, and Cisco MGX 8830 Switches, Release 5.0.
Chapter 10 Switch Maintenance Procedures Replacing Cards When upgrading redundant service module configurations, keep the following in mind: • The secondary card must be an MPSM-8-T1E1. • If the secondary card is not an MPSM-8-T1E1, the secondary card must be upgraded before upgrading a primary card. The following procedure describes how to upgrade a primary card in a redundant configuration to MPSM-8-T1E1.
Chapter 10 Switch Maintenance Procedures Replacing Cards Step 7 To finalize the upgrade, enter the commitrev command. The command format is: M8850_SF.7.PXM.a > commitrev Use the same slot number and revision number used in the previous steps. For example: M8850_SF.7.PXM.a > commitrev 13 30.0(0.85)A After you enter this command, the switch automatically makes the primary card active and resets the secondary card.
Chapter 10 Switch Maintenance Procedures Decommissioning an AXSM Slot Replacing RPM Cards If you have properly initialized an RPM card as described in the “Initializing RPM Cards” section in Chapter 6, “Preparing RPM Cards for Operation.” the configuration for the RPM card is stored on the PXM hard disk. To replace a standalone RPM card, remove the old card and insert a new card of the same type in the same slot. The switch will automatically configure the card and start it up.
Chapter 10 Switch Maintenance Procedures Decommissioning an AXSM Slot Step 1 Establish a configuration session using a user name with CISCO_GP privileges. Step 2 Use the cc command to select the AXSM slot you want to decommission. Note Step 3 The AXSM card installed in the slot you are decommissioning must be the same type of card for which the slot was configured. You cannot decommission a slot with an AXSM card type that does not match the configured card type.
Chapter 10 Switch Maintenance Procedures Decommissioning an RPM Slot Step 17 Bring down all lines by entering the following command for each line: mgx8850a.10.AXSM.a > dnln Step 18 To verify that the lines have been brought down, enter the dsplns command. When all lines have been brought down, the slot is decommissioned and you can add an AXSM card of a different type in that slot as described in “Adding Service Modules,” which appears earlier in this chapter.
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 Cisco MGX 8850 (PXM1E) and Cisco 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 11-12 Cisco MGX 8850 (PXM1E/PXM45), Cisco MGX 8950, Cisco MGX 8830, and Cisco MGX 8880 Configuration Guide Release 5.0.10, OL-3845-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.0.00 and the Release Notes for the Cisco MGX 8880 Media Gateway, Release 5.0.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 2 1 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 If the Release Notes for Cisco MGX 8850 (PXM1E/PXM45), Cisco MGX 8950, and Cisco MGX 8830 Switches, Release 5.0.00 or the Release Notes for the Cisco MGX 8880 Media Gateway, Release 5.0.
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 Step 2 Command Purpose username password Establish a CLI session with the active PXM card using a user name with SERVICE_GP privileges. 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.0.00 or the Release Notes for the Cisco MGX 8880 Media Gateway, Release 5.0.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: • 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 PXM Cards and Service Modules Note Step 3 If the primary and secondary software revisions are the same, there is no other revision level to revert back to. To abort use of the primary software revision and revert back to the secondary software revision, enter the following command: mgx8850a.7.PXM.
Appendix A Downloading and Installing Software Upgrades Upgrade Procedures for RPM-PR and RPM-XF Cards Note Cisco Systems recommends that you avoid configuration changes until after you have run the commitrev or abortrev commands. Upgrade Procedures for RPM-PR and RPM-XF Cards The following sections describe how to upgrade boot and runtime software on RPM-PR and RPM-XF cards. Note In this document, the general term “RPM” refers to RPM-PR and RPM-XF cards.
Appendix A Downloading and Installing Software Upgrades Upgrade Procedures for RPM-PR and RPM-XF Cards When managing the bootflash, consider the following facts: Caution • If the BOOTLDR variable is set and the RPM card is reset, the RPM card attempts to load the boot software specified. • If the BOOTLDR variable is not set and the RPM card is reset, the RPM card tries to load the first bootable image in bootflash.
Appendix A Downloading and Installing Software Upgrades Upgrade Procedures for RPM-PR and RPM-XF Cards Step 4 Enter Enable mode for the router. Router>enable Password: Router# Step 5 To verify router access to the PXM hard disk and display the boot file name, enter dir x: command.
Appendix A Downloading and Installing Software Upgrades Upgrade Procedures for RPM-PR and RPM-XF Cards Step 8 To verify that the file was copied, enter the show flash: command. Step 9 To set the BOOTLDR variable to specify the new boot software, complete the following steps: a. Enter the router global configuration mode Router#config terminal Enter configuration commands, one per line. b. End with CNTL/Z.
Appendix A Downloading and Installing Software Upgrades Upgrade Procedures for RPM-PR and RPM-XF Cards You might want to copy previously saved configuration files back to bootflash, or you might want to copy an older boot image to be used if the newer version becomes corrupt. e. Caution If all bootable images are deleted from bootflash and the RPM card is restarted, the card must be returned to the factory to be reprogrammed.
Appendix A Downloading and Installing Software Upgrades Upgrade Procedures for RPM-PR and RPM-XF Cards At startup, the RPM card attempts to load the software in the order listed in the startup-config file. The following example shows an excerpt from a startup-config file: ! boot system x:rpm-js-mz_122-4.T boot system bootflash:rpm-js-mz_122-4.
Appendix A Downloading and Installing Software Upgrades Upgrade Procedures for RPM-PR and RPM-XF Cards To upgrade the RPM runtime software for 1:N redundancy, use the following procedure. Step 1 Copy the new runtime 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. 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.
Appendix A Downloading and Installing Software Upgrades Upgrade Procedures for RPM-PR and RPM-XF Cards 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 Upgrade Procedures for RPM-PR and RPM-XF Cards Upgrading RPM Runtime Software for Non-Redundant Cards To upgrade the RPM-PR or RPM-XF runtime software for nonredundant cards, use the following procedure. Note In this document, the general term “RPM” refers for both the RPM-PR and RPM-XF cards. If a step or procedure is specific to only one of the RPM cards, it will be called out in the text.
Appendix A Downloading and Installing Software Upgrades Upgrade Procedures for RPM-PR and RPM-XF Cards Step 8 Display the startup runtime software filename by entering the show bootvar command. Router#show bootvar BOOT variable = x:rpm-js-mz_122-4.T,12; CONFIG_FILE variable = c:auto_config_slot09 BOOTLDR variable does not exist Configuration register is 0x2 In the example above, the startup runtime software file is x:rpm-js-mz_122-4.T, and it has a version number attached to it.
Appendix A Downloading and Installing Software Upgrades Troubleshooting Upgrade Problems Troubleshooting Upgrade Problems Table A-4 lists symptoms of upgrade problems and suggestion on how to correct them. Tip Table A-4 When troubleshooting problems on standby PXM cards or cards that do not start up to the active state, establish communications through the boot IP address or through the console port.
Appendix A Downloading and Installing Software Upgrades Troubleshooting Upgrade Problems Table A-4 Troubleshooting Upgrade Problems (continued) Primary Symptom Secondary Symptom After restart, switch stops at backup boot prompt: pxm1ebkup> or pxm45bkup. The switch displays the The version file is probably missing. Create the version file as following message: Can not described in the “Initializing the Switch” section in Chapter 2, open file C:/version. “Configuring General Switch Features.
Appendix A Downloading and Installing Software Upgrades Troubleshooting Upgrade Problems Table A-4 Troubleshooting Upgrade Problems (continued) Primary Symptom Secondary Symptom Suggested Action After restart, the switch stops at shell prompt: pxm1e> or pxm45>. — If the Return key is pressed at one of the auto-boot prompts during start up, the switch stops in shell mode. Enter the reboot 2 1 command to restart the switch and avoid pressing the Return key.
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.0.00 and the Release Notes for the Cisco MGX 8880 Media Gateway, Release 5.0.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 B-6 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.
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 PXM45 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 PXM1E 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 PXM1E 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 C-16 Cisco MGX 8850 (PXM1E/PXM45), Cisco MGX 8950, Cisco MGX 8830, and Cisco MGX 8880 Configuration Guide Release 5.0.10, OL-3845-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 of the Cisco MGX 8830, Cisco MGX 8850 (PXM1E/PXM45), and Cisco MGX 8950 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 3.0 AINI 3.1 UNI 3.0/3.1 x x x x x x x UNI 4.0 x x x x x x x IISP 1.0 x x x x x x x PNNI 1.0 x x x x x x x AINI 3.0 x 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) Hardware Survey Worksheet Reserved For Front Card Type Upper Back Card Redundant Lower Back Card 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 31 Secondary
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 Redundant Lower Back Card 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 E-4 Cisco MG
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 SRM 1 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 conf
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 index 2 slot.2.1 Protection index 2 slot.2.2 1 Intracard APS Mode 3 Working index 4 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 index 4 Protection index Mode Line 7 Redundancy Options Working index 2 Protection index Mode Intercard APS slot.2.7 2 slot.2.8 3 Working index 4 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 index 2 slot.2.11 Protection index 2 slot.2.12 1 Intracard APS Mode 3 Working index 4 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 Cisco 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 Cisco MGX 8850 (PXM45) and Cisco MGX 8950 switches, and on the Cisco MGX 8880 Media Gateway.
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 Cisco MGX 8850 (PXM45) switches.
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 VISM Configuration Worksheet VISM Configuration Worksheet Table E-14 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-14.
Appendix E Hardware Survey and Software Configuration Worksheets VXSM Configuration Worksheet VXSM Configuration Worksheet Table E-15 lists general switch parameters you will need to configure on each VXSM card. Note VXSM cards operate only on Cisco MGX 8850 (PXM45) and Cisco MGX 8950 switches. If you are configuring a Cisco 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-7.
A P P E N D I X F MPSM Licensing MPSM Licensing Information The multiprotocol service module (MPSM) family of cards includes the MPSM-T3E3-155 and MPSM-8T1E1 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 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 Licenses are installed on the PXM card and form a pool of licenses that is managed by the PXM controller. Licenses are authorized for a specific backplane serial number. (You cannot move licensed PXM cards to different chassis without sending the node into an alarm state.) The licenses can then be allocated to specific slots. When an MPSM card is provisioned, the licenses required for that configuration are allocated to that slot.
Appendix F MPSM Licensing MPSM Licensing Information MPSM License Concepts and Terms Table F-3 lists concepts and terms used to explain the MPSM licensing procedure.
Appendix F MPSM Licensing MPSM Licensing Information Table F-4 lists the terminology used for managing feature licenses on the MPSM cards. Table F-4 Feature LIcense Terminology for MPSM Cards Term Explanation Allocated Licenses To provide a feature or service, a license is acquired by a module from the pool of installed licenses on the node. An acquired license is referred to as allocated to the module.
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 Licensed Card Type ----------------MPSM-T3E3-155 System Rev: 04.
Appendix F MPSM Licensing MPSM Licensing Information 3 4 5 6 7 8 9 10 11 12 13 14 Note ---------MPSM-T3E3-155 --- ---------No --- ---------Yes --- ---------Channelize --- 0 0 0 0 0 0 0 0 0 1 0 0 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.
Appendix F MPSM Licensing MPSM Licensing Information Node Alarm: MAJOR Card Type --------------MPSM-T3E3-155 Licenses Moved ---------No 4 MPSM-T3E3-155 Yes 5 MPSM-T3E3-155 Yes 6 9 10 11 12 13 ... ... ...
Appendix F MPSM Licensing MPSM Licensing Information Provisioning allowed: Grace-Period Status: • No Expired If the slot is running normally without a license alarm, only the following output displays: Provisioning allowed: Yes The number after the dspliccd command is the slot number for which you want to display license data. An allocated license is one that has been assigned to a card. A programmed license is a license that has been shipped on a card from the factory.
Appendix F MPSM Licensing MPSM Licensing Information Displaying License Alarms To display a list of license feature alarms, enter the dsplicalms command as follows: M8830_CH.1.PXM.a > dsplicalms M8830_CH System Rev: 04.09 Mar.
Appendix F MPSM Licensing MPSM Licensing Information Step 4 To generate a license key on Cisco.com, go to the web page specified in the “MPSM License Overview” section on page F-1. At this web page, you must specify the PAK and the licenses you want to install, and you must specify the serial number collected in Step 2. After you arrange for additional licenses, you will receive an encrypted key in an E-mail message and in a license file attachment.
Appendix F MPSM Licensing MPSM Licensing Information --------------- ----MultiSrvc 1 Channelize 1 RateControl 1 MultiLink 1 Please confirm the above licence information. cnflic: Do you want to proceed (Yes/No)? y M8850_SF.7.PXM.a > Step 7 Caution Step 8 To verify that new licenses have been installed, enter the dsplics command. To avoid losing licenses during a configuration restoration, save the switch configuration after installing the new licenses by using the saveallcnf command.
Appendix F MPSM Licensing MPSM Licensing Information secondary card for a primary card, licenses are allocated to the secondary card. When the secondary card serves multiple primary cards, the secondary card receives one of each type of license used by the primary cards it serves. If the license pool on the switch has an available license for that feature on the MPSM card type, the license is automatically allocated to the card.
Appendix F MPSM Licensing MPSM Licensing Information 5. Transfer the new license to the destination switch. 6. Apply the new license on the destination switch. The following procedure provides instructions for transferring licenses between switches. Step 1 Establish a configuration session with the source and destination switches using a user name with SERVICE_GP privileges or higher. Step 2 To display the switch serial number used for licensing on the source switch, enter the dsplicnodeid command.
Appendix F MPSM Licensing MPSM Licensing Information cnflic: Do you want to proceed (Yes/No)? y Licence file has been generated as: C:/LICENSE/LX-M8850_NY-7.lic Licence is: 0105000443e166180e7a310f483833a54079b77eb217332057c3d2fbaa4e9245def5aad5558458d6ab2f6bc64a 6c0441839dbdbb43e02aa7a179facb8e058de821e270a233ce87c3 M8850_SF.7.PXM.a > This step removes the licenses identified for transfer from the license pool, and these licenses are no longer available for use on the source switch.
Appendix F MPSM Licensing MPSM Licensing Information Note To install the new license(s) using the encrypted key produced in Step 5 or Step 6, go to Step 7 To install the new license(s) on the destination switch using the new license file produced in Step 5 or Step 6, go to Step 8. 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 cnflic: Do you want to proceed (Yes/No)? y M8850_SF.7.PXM.a > Step 9 To verify that the transferred licenses have been installed on the destination switch, enter the dsplics command. Step 10 Enter the saveallcnf command. Caution To avoid losing licenses during a configuration restoration, save the switch configuration at the source and destination switches by using the saveallcnf command.
Appendix F MPSM Licensing MPSM Licensing Information Node license alarms are cleared by validating licenses in the license pool. This is done by applying the special Rekey feature license to the node using the cnflic command. When the pool licenses are validated, any existing slot license alarms are also cleared and normal operation is restored. For the procedure to rekey feature licenses, see “Rekeying Feature Licenses”.
Appendix F MPSM Licensing MPSM Licensing Information Card License Alarm: Service Module Type: Service Module Serial Number: Provisioning Allowed: Grace-Period Remaining: Minor MPSM-8T1-FRM SAG07208RRA Yes 4 Days, 22 Hrs ========================================================= Allocated License Type Quantity --------------------------RateControl 1 ========================================================= Programmed License Type Quantity --------------------------RateControl 1 ==========================
Appendix F MPSM Licensing MPSM Licensing Information M8850_SF.1.28.MPSM8T1.FRM.a > On PXM1E and PXM45 platforms, the output of the MPSM dspliccd command also shows if a card is in slot license alarm. The following example shows the output of the dspliccd command of an MPSM-8T1-FRM card in a PXM45 platform in the slot license alarm state: M8850_SF.1.28.MPSM8T1.FRM.
Appendix F MPSM Licensing MPSM Licensing Information A rekey license can be obtained by contacting Cisco TAC. The rekey license is delivered in the form of an encrypted key, which appears within an E-mail message or within a text file attached to an E-mail. To get a rekey license, provide TAC with the output generated by the dsplicnodeid command for the switch that needs to be rekeyed. The general procedure is as follows: 1.
Appendix F MPSM Licensing MPSM Licensing Information M8850_SF.8.PXM.a > cnflic -f L_20040706140923521.dat Update method :Rekey Card type :---Creation date/time :TUE JUL 06 21:09:23 2004 Grace period (days) :0 Update sequence number:8 Licence serial number :L0000003455 Num of features :0 ------------------License Type Qty ------------------Please confirm the above licence information. cnflic:Do you want to proceed (Yes/No)? y M8850_SF.8.PXM.
Appendix F MPSM Licensing MPSM Licensing Information F-24 Cisco MGX 8850 (PXM1E/PXM45), Cisco MGX 8950, Cisco MGX 8830, and Cisco MGX 8880 Configuration Guide Release 5.0.10, OL-3845-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 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 8850 (PXM45/PXM1E), Cisco MGX 8950, Cisco MGX 8830, and Cisco MGX 8880 Command Reference, Release 5.
Appendix G Reliability, Availability, and Serviceability Diagnostics 11 12 13 14 15 HDsk PCI Access HDsk Rd/Wr CBC RAM Access BRAM checksum Control Path Y Y Y Y Y 2868 95 2868 2868 28680 0 0 0 0 0 2868 95 2868 2868 28680 None None None None None 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 Power On Self-Tests (POST) • BRAM checksum • QE RAM • CBC RAM • Ethernet Register Access • PCI/IDE Register Access • Clock Mux Validation • Framer Access • Atlas1 RAM Access • Atlas2 RAM Access • Hard Disk Access PXM1E Path tests • Data Path • Control Path PXM1E Device Tests • Atlas Register Access • Atlas SRAM Access • Framer/LIU Access • Trap Frequency Monitor • Elmer Access • Flash Checksum •
Appendix G Reliability, Availability, and Serviceability Diagnostics • PCI/IDE Register Access • Clock Mux Validation • Hard Disk Access PXM45 Path Tests G-6 • 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 8850 (PXM1E/PXM45), Cisco MGX 8950, Cisco MGX 8830, and Cisco MGX 8880 Configuration Guide Relea
INDEX addlmi command Symbols 3-18, 3-20 addlnloop command ? command 2-13 9-79 addnwnode command addpart command 3-4, 3-6, 3-11, 3-13, 3-14, 3-16, 3-18, 3-49 addparty command A 8-13, 8-20 3-81 addpnni-node command AAA server addpnni-summary-addr command configuring switch access to server configuration abortrev command 9-64 9-11, A-35 ANYUSER 2-17 2-18 3-4, 3-6, 3-10, 3-11, 3-13, 3-14, 3-16, 3-18, 3-20, 3-45, 7-14 addpref command 8-14 addprfx command 3-6, 3-65 addred command 4-2, 4
Index displaying switching alarms software downgrades 11-2 ANYUSER access privileges software upgrades 2-17 APS A-22 A-2 testing loopback lines connector, displaying AXSM-E SCTs 9-19 9-79 7-3 intercard configuration 3-42 AXSM SCTs intracard configuration 3-40 AXSM slot, decommissioning lines backup boot access 9-20 displaying 9-23 modifying 9-24 AXSM-XG SCTs removing redundancy switching between troubleshooting preparing for 9-26 9-26, 9-27 back cards 9-19 backup boot nod
Index introduction Cisco MGX 8850 (PXM45) features 5-1 burnboot command bye command 9-11, A-29, A-30 2-10, 9-58, 9-63, C-15 Cisco MGX 8880 features 1-3 Cisco MGX 8950 features 1-3 1-3 Cisco TAC See TAC C Cisco user group C:CNF C:FW Cisco View B-4 C:LOG CAC See CISCO_GP B-4 class of service buffer B-4 7-1 CLI 7-1 connections cards displaying card alarms CP port setup 11-6 displaying redundancy status managing redundancy types and locations card SCT MP port setup 9-17 C-6 en
Index clrilmicnt command 9-10 clrpribumpstats command clrsmcnf command 8-31 cnflic command F-12, F-15, F-22 cnfln command 3-3, 3-23, 3-27, 5-3, 5-4 cnfln -ds3 command 9-4 3-27 cnfaaa-authen command 9-68 cnfln -sonet command cnfaaa-author command 9-69 cnfname command cnfaaa-ftpssh command 9-70 cnfncdpclksrc command cnfaaa-ignore-ios command cnfaaa-priv command 9-67 cnfaaa-server command 9-64 3-76 cnfabrtparmdft command cnfaddrcug 3-76, 7-6 cnfaddrreg command 3-6, 3-58, 3-65 cnfa
Index cnfsntprmtsvr command cnfspvcprfx command controller 9-29 configuring for MPLS 2-3, 2-29 cnfswfunc command (on IGX) 3-91 configuring for PNNI 2-30 2-23 cnftime command 2-2, 2-22 conventions, documentation cnftmzn command 2-2, 2-22 copy command cnftmzngmt command cnftopogw command 2-2, 2-22 cnftrapip command 3-91 command entry guidelines COSB 1-11 7-1 C-2 CUG 9-55 getting runtime help A-24 CP port connection setup 2-2, 2-19 cnfxbarmgmt command B-3 core switch topology 2
Index dellnloop command dnpnport command 9-80 delncdpclksrc command delnwnode command delpart command 9-40 delpref command 8-19 delprfx command 9-11 9-18 delsct command 7-11 obtaining 8-73 ordering 8-73 xlvii xliii organization 2-2, 2-19 xxvii recommended order of use DSL G-1 on AXSM cards 9-83, 9-84, 9-85, 9-86, 9-88, 9-89 on PXM1E cards 9-83, 9-84, 9-85, 9-86, 9-88, 9-89 Digital Subscriber Line Access Multiplexers dspaaa command 9-71 dspaaa-servers command 8-59 See DSL dir bo
Index dspclkalarms command 11-2 dspipif command dspclkparms command 2-33 dspipif lnPci0 command dspclksrcs command dspipif sl0 command C-7 2-11 dsplicalms command 11-7, 11-9, F-11 dspconalarms command 3-9, 3-12, 3-77, 3-85, 9-51, 10-27, 11-7 dspcontrollers command dspcug command dspliccd command 11-7 3-9, 3-12, 3-79, 3-85, 11-7 dspcons command 2-3, 2-24, 2-30, 9-45 dspcugdefaddr command 8-60 2-2, 2-10, 2-21 dspdevalms command dspdeverr command 11-3 dspdeverrhist command dspdiagcnf
Index dsppnilmi command dsprevs command 9-9 dsppnni-election command 4-5, 9-15, A-33, A-34, A-35, A-46 dsprevs -status command 8-3, 8-4 9-15 dsppnni-intf command 8-21, 8-22, 8-51 dsprmalms command 11-7 dsppnni-link command 2-27, 3-5, 3-13, 3-68, 8-52 dsprteoptcnf comman 8-43 dsppnni-link-selection command dsppnni-neighbor command dsppnni-node command 8-20 3-5, 3-13 2-24, 2-26, 2-28, 2-30, 3-69, 8-5, 8-49 dsppnni-node-list command dsprteoptcnf command 8-37, 8-45 dsprteoptstat command
Index changing 9-42 managing restoring viewing G 9-28 gateway node 9-42 disabling 9-28, 9-41 8-65 8-72 grooming configuring soft reroute F 8-35 displaying configuration parameters displaying statistics features Cisco MGX 8830 1-3 introduction Cisco MGX 8850 1-3 manual 8-38 Cisco MGX 8880 1-3 orderly 8-43 Cisco MGX 8950 1-3 scheduled displaying information introduction trunk 8-35 thresholds 8-71 8-47 8-32 soft reroute feeder 8-33 8-39 GROUP1 access privileges 1-12 8-45
Index enabling automatic configuration starting 3-62 See MPSM licensing adding an IMA port 3-37, 3-38 configuring an IMA group 3-29, 3-30, 3-31, 3-33 configuring an IMA link deleting an IMA group deleting an IMA link 3-35, 3-37 displaying IMA links 3-30, 3-31, 3-33, 3-34 3-26 lines bringing up 3-26, 3-27, 5-5 9-93 PNNI configuration See ICR runtime interface addresses 8-56 8-58 intracard APS 3-40 9-11, A-32 9-55 log files backup boot access 3-45 Interim Inter-Switch Protocol 3-2
Index See documentation MPSM-8E1-ATM service modules MPSM-8E1-CES 1-2 maximum burst size See MBS maximum frame size MPSM-8E1-FRM 4-8 MPSM-8T1-ATM 4-8 4-8 MPSM-8-T1E1, upgrading to MGX 8880 Media Gateway card locations MPSM-8T1-FRM 10-21 4-8 2-50 MGX switches card locations N 2-50 minimum cell rate NCDP See MCR clock source movelic command 4-2, F-13 deleting MPLS 9-40, 9-41 displaying controller configuration line configuration 2-30 configuring 3-5 trunk configuration 3-1
Index network topology link information 8-69 NNI creating upper levels ID configuration card support 8-1 2-24 peer group leader 1-9 See PGL node address configuration displaying alarms PNNI transit permanent virtual circuit 2-25 See PVC 11-2 persistent network topology 8-5 non-directed route 8-65 PGL 8-12 priority configuration 8-3 PNNI O AW configuration optrte command 8-21 background routing table generation 8-38 out-of-frame alarm criteria bandwidth overbooking factor conf
Index configuring port range 9-52 PXM45 card adding standby cards See also lines port SCT card types 7-1 POST See Power On Self Test Power On Self Test preferential CUG overview G-1 software upgrades A-2 verifying disk data 9-73 backup boot access 8-11 prefix B-4 PXM45 UI-S3 assigning clock source ports 8-56 priority bumping configuration clock source ports 8-30 displaying statistics 8-31 PXMbkup prompt CP connection 8-30 CP connection overview 2-39 2-5 LAN connection 8-26,
Index reboot command dspcds command display 2-2, 2-6, A-27, B-5 redundancy generic software name 6-2 A-41 displaying status 9-16 graceful boot upgrade on PXM45 cards 1-10 graceful runtime upgrade switching AXSM cards initializing 9-17 switching PXM45/PXM1E cards resetting 4-8 rrtcon command 3-40, 5-10 reliability, availability, and serviceability remote authentication remove command G-1 3-88 9-11, A-33 S A-25 saveallcnf command resetsys command 2-39, 6-2, 6-8, 7-10, 9-78, A-37 10
Index modify with CWM port show flash command 7-2, 7-6 7-1 registering 7-7 selecting a port SCT 7-22 secure session starting show inventory command 1-15 6-10 show version command 6-2, 6-8 See SNMP C-13 SERVICE_GP access privileges Service Class Template 2-16 SNMP 1-16 community string 7-1 service module configuration 2-44 2-42 RPM-PR card configuration 2-50 trap source IP address 1-2 Service Resource Module SNMP manager See SRM 6-10 2-43 1-16 destination IP address serv
Index standards SPVC summary address, display D-4 SUPER_GP 2-17, 3-1 configuring master side configuring slave side double-ended node prefix access privileges 3-78 See SUPER_GP 2-28 sustained cell rate 3-8 See SCR 3-70 SVC SPVCs card support 3-1, 3-2 displaying SVCs 1-9 9-43 quickstart configuration 2-17 configuring master side configuring slave side node prefix svcifconfig command 3-78 3-7 C-9 SVCs 3-71 card support 2-28 quickstart configuration 1-9 switchapsln command 3-
Index AINI link configuration T 3-14 BPX PNNI trunk configuration Table 9-74 bringing up TAC opening a case website 3-22, 5-4 configuration case priority definitions xlvii MPLS configuration xlvi TACACS+ 9-63 3-1 See also lines viewing configuration xlvi 3-28 XLMI link Technical Assistance Center configuration See TAC 3-17 trunk utilization limit Telnet tstdelay command client program 8-44 3-55 2-42, C-13 ending CLI session C-15 from one switch to another starting CLI sessi
Index verifydiskdb display command verifydiskdb status command version file 9-76 9-75 A-47 version levels, software determining from filenames managing 3-22, 4-3 verifying 4-5 virtual tributary 9-11 5-15 virtual tributary group 5-15 virtual trunk introduction 1-12 VISM card supported interfaces 1-5 W warning definition xxix whoami command backup boot runtime without B-3 2-18, A-25 9-74 worksheets hardware configuration E-2, E-3, E-4 X XLMI link configuration 3-17 XLMI link introduc
