Cisco MGX 8850 (PXM45) and MGX 8950 Software Configuration Guide Release 3 January 2004 Corporate Headquarters Cisco Systems, Inc. 170 West Tasman Drive San Jose, CA 95134-1706 USA http://www.cisco.
THE SPECIFICATIONS AND INFORMATION REGARDING THE PRODUCTS IN THIS MANUAL ARE SUBJECT TO CHANGE WITHOUT NOTICE. ALL STATEMENTS, INFORMATION, AND RECOMMENDATIONS IN THIS MANUAL ARE BELIEVED TO BE ACCURATE BUT ARE PRESENTED WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED. USERS MUST TAKE FULL RESPONSIBILITY FOR THEIR APPLICATION OF ANY PRODUCTS.
CONTENTS About This Guide Objectives Audience xxi xxi xxi Organization xxi Related Documentation xxii Cisco WAN Manager Release 11 xxii Cisco MGX 8850 (PXM45) Multiservice Switch Release 3 Cisco MGX 8850 (PXM1E) Multiservice Switch Release 3 Cisco MGX 8950 Multiservice Service Release 3 xxvi SES PNNI Release 3 xxvi Cisco MGX 8830 Multiservice Switch Release 3 xxvii Cisco WAN Switching Software Release 9.3 xxviii MGX 8850 Multiservice Switch Release 1.1.40 xxix MGX 8250 Edge Concentrator Release 1.1.
Contents Configuration Tasks 1-6 Collecting Information 1-7 General Configuration Data 1-7 Unique Switch Name 1-7 ATM Addressing Plan 1-8 IP Addressing Plan 1-8 Administrator Data 1-8 Network Clock Source Plan 1-8 Network Management Plan 1-13 Line and Trunk Data 1-13 IMA support on PXM1E 1-14 Planning for Card and Line Redundancy 1-14 Planning Single AXSM/FRSM-12 Front Card Configurations with Redundant Lines 1-15 Planning Redundant AXSM/FRSM-12 Configurations with Standalone Lines 1-17 Planning Redund
Contents Configuring PNNI Node Parameters 2-21 Adding the PNNI Controller 2-21 Setting the PNNI Level and Peer Group ID 2-22 Setting the PNNI Node Address 2-23 Setting the PNNI Node ID 2-24 Setting and Viewing the SPVC Prefix 2-26 Displaying PNNI Summary Addresses 2-27 Configuring the MPLS Controller 2-28 Configuring Clock Sources 2-28 Manually Configuring BITS Clock Sources Enabling NCDP on a Node 2-31 Setting the LAN IP Addresses 2-33 Setting the Boot IP Address 2-33 Setting the LAN or Disk IP Address
Contents Establishing Redundancy Between Two Lines with APS Adding Intracard APS Lines 3-19 Adding Intercard APS Lines 3-21 CHA PTER 4 Preparing FRSM12 Cards and Lines for Communication Configuration Quickstart 3-19 4-1 4-1 Managing Firmware Version Levels for FRSM12 Cards 4-2 Locating Cards that Need the Firmware Version Set 4-2 Initializing FRSM12 Cards 4-4 Verifying Card Firmware Version Levels 4-4 Establishing Redundancy Between Two FRSM12 Cards Selecting and Viewing Service Class Templates Sele
Contents Managing PNNI Route and Link Selection 6-8 Configuring the Route Selection Method (First Fit or Best Fit) Configuring the Best-Fit Route Selection Method 6-9 Configuring Preferred Routes 6-9 Configuring a Preferred Route 6-10 Associating an SPVC or an SPVP with a Preferred Route Modifying a Preferred Route 6-13 Deleting a Preferred Route 6-14 Configuring Link Selection for Parallel Links 6-15 Configuring the Maximum Bandwidth for a Link 6-15 Configuring the Administrative Weight 6-15 Configuring t
Contents Managing Redundant Cards 7-14 Displaying Redundancy Status 7-14 Switching Between Redundant PXM Cards 7-14 Switching Between Redundant AXSM Cards 7-15 Switching Between Redundant RPM-PR Cards 7-15 Removing Redundancy Between Two Cards 7-16 Managing Redundant APS Lines 7-16 Prepare for Intercard APS 7-16 Configuring Intercard APS Lines 7-17 Displaying APS Line Information 7-23 Modifying APS Lines 7-23 Switching APS Lines 7-24 Removing APS Redundancy Between Two Lines Troubleshooting APS Lines 7-25
Contents Managing Controllers 7-42 Adding Controllers 7-43 Deleting Controllers 7-44 Managing Service Class Templates 7-45 Displaying all Registered SCTs on a Switch 7-45 Displaying the SCT Assigned to a Port 7-46 Displaying the SCT Assigned to a Card 7-47 Displaying Port SCT Settings 7-47 Port SCT General Parameters (dspportsctgen) 7-48 Port SCT COSB Parameters (cosb) 7-50 Port SCT Virtual Circuit Threshold Parameters (vcThr) 7-51 Port SCT COSB Threshold Parameters (cosThr) 7-55 Displaying Card SCT Settin
Contents Clearing Path and ConnectionTraces 7-75 Clear the Connection Trace Buffer 7-76 Clear the Path Trace Buffer 7-76 Clearing a Call at the Destination Node 7-77 Managing Load Sharing 7-77 Displaying Load Sharing Status Changing Load Sharing Options 7-77 7-78 Starting and Managing Telnet Sessions to Other Switches Starting a Telnet Session 7-79 Returning to a Previous Session 7-79 Returning to the Original CLI Session 7-80 Displaying a Telnet Trace 7-80 7-79 Verifying PXM45 Disk Data 7-80 Displayin
Contents Replacing Cards with the Same Card Type 8-4 Replacing PXM45 and PXM45/B Cards 8-5 Automatic Response for Standalone PXM45 Installations 8-5 Automatic Response for Redundant PXM45 Installations 8-6 Manually Responding to Nativity Checks 8-7 Replacing AXSM Cards 8-8 Replacing RPM Cards 8-8 Upgrading Cards 8-9 Replacing PXM45 Cards with PXM45/B Cards 8-9 Replacing AXSM Cards with AXSM/B Cards 8-9 Decommissioning an AXSM Slot 8-10 Decommissioning an RPM Slot CHA PTER 9 8-12 Viewing and Respondin
Contents Non-Graceful RPM-PR Boot Software Upgrades A-14 Non-Graceful RPM-PR Runtime Software Upgrades A-15 Installing SCT Files A-17 Quickstart Procedures for Software Downgrades A-17 PXM45 and AXSM Boot Downgrades A-18 Non-Graceful PXM45 Runtime Software Downgrades A-18 Non-Graceful AXSM Runtime Software Downgrades A-19 Browsing the File System Locating Software Updates A-19 A-20 Copying Software Files to the Switch A-21 Upgrade Procedures for PXM45, AXSM, and FRSM-12 Cards A-22 Upgrading PXM45 Boot
Contents Setting Up Dial-Up Connections C-4 Setting Up ATM WAN Connections Configuring the Switch C-6 Configuring the Router C-9 C-5 Starting a CLI Management Session Using a CP Port or Terminal Server Connection Starting a CLI Telnet Session C-11 Ending a CLI Management Session APPENDIX D Standards Compliance PNNI Compliance C-10 C-12 D-1 D-1 ATM Signaling Compliance D-2 UNI 3.0/3.1 Signaling D-2 UNI 4.
Contents Cisco MGX 8850 (PXM45) and MGX 8950 Software Configuration Guide xiv Release 3, Part Number 78-14788-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 Example Network Clock Source Topology with a Single Master Clock Source Figure 1-6 Example Network Clock Source Topology with Two Master Clock Sources Figure 1-7 Example NCDP Network Clock Source Topology Figure 1-8 Single AXSM/FRSM-12 Front Card Configuration with Redundant Lines Figure 1-9 Redundant AXSM Conf
Figures Cisco MGX 8850 (PXM45) and MGX 8950 Software Configuration Guide xvi Release 3, Part Number 78-14788-01 Rev.
T A B L E S Table 1 Cisco WAN Manager Release 11 Documentation Table 2 WAN CiscoView Release 11 Documentation Table 3 Cisco MGX 8850 (PXM45) Release 3 Documentation xxiii Table 4 Cisco MGX 8850 (PXM1E) Release 3 Documentation xxiv Table 5 Cisco MGX 8950 Switch Release 3 Documentation Table 6 SES PNNI Controller Release 3 Documentation Table 7 Cisco MGX 8830 Release 3 Documentation Table 8 Cisco WAN Switching Release 9.3 Documentation Table 9 MGX 8850 Multiservice Switch Release 1.1.
Tables Table 3-6 APS Line Architecture Modes Table 6-1 Parameters for addpnni-summary-addr Command Table 6-2 Parameters for cnfpnni-svcc-rcc-timer Command 6-6 Table 6-3 Parameters for cnfpnni-routing-policy Command 6-7 Table 6-4 Parameters for cnfpnni-timer Command Table 6-5 Parameters for addpref Command Table 6-6 Parameters for cnfconpref Command Table 6-7 modpref Command Parameters Table 6-8 Objects Displayed for dsppnni-summary-addr Command Table 6-9 Objects Displayed for the dsppn
Tables Table 7-24 Options for dspcdsct Command Table 7-25 Service Class Template: SCT General Parameters Table 7-26 Service Class Template: SCT COSB Parameters Table 7-27 Service Class Template: SCT VC Threshold Parameters Table 7-28 Class of Service (CoS) Scaling Table Table 7-29 Logical Interface Scaling Table Table 7-30 Service Class Template: SCT COSB Threshold Parameters Table 7-31 Options for dspcdsct Command Table 7-32 cnfsct Command Parameters Table 7-33 Parameters for the cnfpar
Tables Table A-4 cnfsct Command Parameters Table A-5 Troubleshooting Upgrade Problems Table B-1 File System Commands at Backup Boot Prompt Table D-1 UNI 3.x Signaling Table D-2 PNNI Signaling Table D-3 PNNI 2.0 Interface Capabilities Table D-4 ATM Signaling Interworking A-38 A-39 B-3 D-2 D-3 D-3 D-3 Cisco MGX 8850 (PXM45) and MGX 8950 Software Configuration Guide xx Release 3, Part Number 78-14788-01 Rev.
About This Guide This preface describes the objectives, audience, organization, and conventions of the Cisco MGX 8850 (PXM45) and MGX 8950 Software Configuration Guide. Objectives This guide describes how to configure the MGX 8850 and the MGX 8950 switch software and how to perform some operating procedures after the switch begins operation.
About This Guide Related Documentation • Chapter 9, “Viewing and Responding to Alarms,” describes the controls available on the switch and how to view switch alarms. • Appendix A, “Downloading and Installing Software Upgrades,” explains how to upgrade switch software. • Appendix B, “PXM45 Backup Boot Procedures,” describes special procedures you can use to manage the switch when only the boot software is loaded.
About This Guide Related Documentation Table 2 WAN CiscoView Release 11 Documentation Title Description WAN CiscoView Release 3 for the MGX 8850 Edge Switch, Provides instructions for using this network management Release 1 software application that allows you to perform minor configuration and troubleshooting tasks.
About This Guide Related Documentation Table 3 Cisco MGX 8850 (PXM45) Release 3 Documentation (continued) Title Description Cisco MGX and SES PNNI Network Planning Guide Provides guidelines for planning a PNNI network that uses the Cisco MGX 8850 (PXM45 and PXM1E), Cisco MGX 8950, and the Cisco BPX 8600 switches. When connected to a PNNI network, each Cisco BPX 8600 series switch requires an SES 3 for PNNI route processing.
About This Guide Related Documentation Table 4 Cisco MGX 8850 (PXM1E) Release 3 Documentation (continued) Title Description Cisco MGX 8830, MGX 8850 (PXM45 and PXM1E), and MGX 8950 Command Reference, Release 3 Describes the PXM commands that are available on the CLI of the Cisco MGX 8830, Cisco MGX 8850, and Cisco MGX 8950 switches.
About This Guide Related Documentation Cisco MGX 8950 Multiservice Service Release 3 The product documentation for the installation and operation of the Cisco MGX 8950 Release 3 switch is listed in Table 5. Table 5 Cisco MGX 8950 Switch Release 3 Documentation Title Description Cisco MGX 8950 Hardware Installation Guide, Release 3 Describes how to install the Cisco MGX 8950 core switch.
About This Guide Related Documentation Table 6 SES PNNI Controller Release 3 Documentation Title Description Cisco SES PNNI Controller Software Configuration Guide, Release 3 Describes how to configure, operate, and maintain the SES PNNI Controller. DOC-7814258= Cisco SES PNNI Controller Command Reference, Release 3 Provides a description of the commands used to configure and operate the SES PNNI Controller.
About This Guide Related Documentation Table 7 Cisco MGX 8830 Release 3 Documentation (continued) Title Description Cisco CESM Software Configuration Guide and Command Reference for MGX 8850 (PXM1E) and MGX 8830, Release 3 Provides software configuration procedures for provisioning connections and managing the CESM cards supported in this release. Also provides command descriptions for all CESM commands.
About This Guide Related Documentation Table 8 Cisco WAN Switching Release 9.3 Documentation (continued) Title Description 9.3.42 Version Software Release Notes Cisco WAN Switching System Software Provides new feature, upgrade, and compatibility information, as well as known and resolved anomalies. DOC-7813227= Cisco IGX 8400 Series Regulatory Compliance and Safety Information Provides regulatory compliance, product warnings, and safety recommendations for the Cisco IGX 8400 Series switch.
About This Guide Related Documentation Table 9 MGX 8850 Multiservice Switch Release 1.1.40 Documentation (continued) Title Description Release Notes for Cisco Voice Interworking Service Module Release 3.1 Provides new feature, upgrade, and compatibility information, as well as known and resolved anomalies. OL-2785-01 Release Notes for Cisco WAN MGX 8850 Release 1, MGX 8250, and MGX 8230 Software Version 1.1.
About This Guide Related Documentation Table 10 MGX 8250 Multiservice Gateway Documentation (continued) Title Description Release Notes for Cisco Voice Interworking Service Module Release 3.1 Provides new feature, upgrade, and compatibility information, as well as known and resolved anomalies. OL-2785-01 Release Notes for Cisco WAN MGX 8850 Release 1, MGX 8250, and MGX 8230 Software Version 1.1.41 Provides new feature, upgrade, and compatibility information, as well as known and resolved anomalies.
About This Guide Conventions Table 11 MGX 8230 Multiservice Gateway Documentation (continued) Title Description Release Notes for Cisco Voice Interworking Service Module Release 3.1 Provides new feature, upgrade, and compatibility information, as well as known and resolved anomalies. OL-2785-01 Release Notes for Cisco WAN MGX 8850 Release 1, MGX 8250, and MGX 8230 Software Version 1.1.41 Provides new feature, upgrade, and compatibility information, as well as known and resolved anomalies.
About This Guide Obtaining Documentation Warning This warning symbol means danger. You are in a situation that could cause bodily injury. Before you work on any equipment, you must be aware of the hazards involved with electrical circuitry and familiar with standard practices for preventing accidents. (To see translated versions of this warning, refer to the Regulatory Compliance and Safety Information document that accompanied the product.
About This Guide Obtaining Technical Assistance You can submit your comments by mail by using the response card behind the front cover of your document or by writing to the following address: Cisco Systems Attn: Document Resource Connection 170 West Tasman Drive San Jose, CA 95134-9883 We appreciate your comments. Obtaining Technical Assistance Cisco provides Cisco.com as a starting point for all technical assistance.
About This Guide Obtaining Technical Assistance • Priority level 1 (P1)—Your production network is down, and a critical impact to business operations will occur if service is not restored quickly. No workaround is available. The Cisco TAC resource that you choose is based on the priority of the problem and the conditions of service contracts, when applicable. Cisco TAC Web Site You can use the Cisco TAC Web Site to resolve P3 and P4 issues yourself, saving both cost and time.
About This Guide Obtaining Technical Assistance Cisco MGX 8850 (PXM45) and MGX 8950 Software Configuration Guide xxxvi Release 3, Part Number 78-14788-01 Rev.
C H A P T E R 1 Preparing for Configuration This chapter introduces the Cisco MGX 8850 and the Cisco MGX 8950 multiservice switches and common switch topologies, provides an overview of the configuration process, and presents guidelines for collecting the information you will need to complete the configuration.
Chapter 1 Preparing for Configuration Cisco MGX 8850 and Cisco MGX 8950 Switches Table 1-1 Cisco MGX 8850 vs.
Chapter 1 Preparing for Configuration Typical Topologies Typical Topologies Release 2.1 of the Cisco MGX 8850 and the Cisco MGX 8950 switches support the following topologies: • Core switch • Multiservice edge aggregation • DSL edge aggregation Core Switch Figure 1-1 shows the switch operating in a core switch topology.
Chapter 1 Preparing for Configuration Typical Topologies Multiservice Edge Aggregation Figure 1-2 shows the switch operating in a multiservice edge aggregation topology.
Chapter 1 Preparing for Configuration Typical Topologies Figure 1-3 Virtual Trunk Topology Private switch B A Edge switch 2 Edge switch 1 Core ATM network Private switch A A Private switch C SPVP B B Edge switch 3 Legend Virtual trunk SPVP 46508 Physical line A virtual trunk provides a private virtual network path through an independent network such as a public ATM network.
Chapter 1 Preparing for Configuration Routing Technologies Figure 1-4 shows the switch operating in a Digital Subscriber Link (DSL) edge aggregation topology. Figure 1-4 DSL Edge Aggregation Topology DSL lines DSLAMs 38412 Core ATM network Typically, DSL edge nodes communicate with colocated DSLAMs over relatively slower broadband trunks such as DS3 and E3 trunks. The DSL edge node communicates with core nodes using relatively faster links such as OC-3, OC-12, and OC-48 trunks.
Chapter 1 Preparing for Configuration Collecting Information Chapter 6, “Provisioning AXSM Communication Links,” describes how to configure ATM communications on ATM Switching Service Module (AXSM) lines and how to configure different types of connections to other ATM devices. For instructions on configuring different ways to manage the Cisco MGX 8850 and the Cisco MGX 8950 switches, see Appendix C, “Supporting and Using Additional CLI Access Options.
Chapter 1 Preparing for Configuration Collecting Information ATM Addressing Plan An ATM network addressing plan is critical for successful operation of the Cisco MGX 8850 and the Cisco MGX 8950 switches in an ATM network. Both MPLS and PNNI networks require unique ATM addresses on each switch. However, the PNNI protocol uses structured network addresses to logically group network devices and determine routes between devices. For PNNI networks, an ATM address plan is required.
Chapter 1 Preparing for Configuration Collecting Information Figure 1-5 Example Network Clock Source Topology with a Single Master Clock Source Switch 2 Switch 3 P P S BITS clock sources AXSM lines with clocks P S P Switch 1 – master clock source S S Switch 6 AXSM lines with clocks P S S S P Switch 5 P = Primary clock source S = Secondary clock source 46145 Switch 4 In Figure 1-5, Switch 1 provides the master network clock source to the rest of the network and uses highly accurate ext
Chapter 1 Preparing for Configuration Collecting Information Figure 1-6 shows an example network clock source topology that uses two master clock sources.
Chapter 1 Preparing for Configuration Collecting Information Consider the following information when you create your manual network clock source plan: • Master clock sources that are located near the center of the network minimize clock signal propagation delay. • BITS clock interfaces receive Stratum-3 or higher clock signals. • Multiple master clock sources provide fault tolerance. • If both primary and secondary external clock sources fail, the switch uses an internal Stratum-3 clock.
Chapter 1 Preparing for Configuration Collecting Information You can modify the priority, stratum level, and clock source reference through the cnfncdpclksrc command, as described in Chapter 7, “Switch Operating Procedures”, in the section “Configuring an NCDP Clock Source” Figure 1-7 shows an example NCDP network clock source topology. The numbers represent the priority of each network clock source, with 1 being the highest priority (or second best clock source) and 10 being the lowest priority.
Chapter 1 Preparing for Configuration Collecting Information Note • If a failed clock source recovers, the switch will use not use the recovered clock source unless you re-add it with the network with the cnfncdpclksrc command. • Clock sources must be configured after the AXSM cards and lines are configured. For more information, see “Configuring AXSM Line Clock Sources” in Chapter 6, “Provisioning AXSM Communication Links.” Cisco advises against running NCDP on VP trunks.
Chapter 1 Preparing for Configuration IMA support on PXM1E The Cisco MGX 8850 and the Cisco MGX 8950 switches support many of the most common ATM configuration parameters. To successfully configure lines and trunks, be sure that the configuration settings used on the switch match the configuration settings used at the other end of the line or trunk. In some cases, options you want to use at one end of the trunk are not supported at the other end.
Chapter 1 Preparing for Configuration Planning for Card and Line Redundancy Note Throughout this guide, the term PXM45 is used to refer to both the PXM45 and PXM45/B cards. The PXM45 has 128 MB of memory and can scale to 40K connections. The PXM45/B has 256 MB of memory and will support more than 40K connections in future software releases. Redundancy setup and configuration is basically the same for AXSM and FRSM cards.
Chapter 1 Preparing for Configuration Planning for Card and Line Redundancy Figure 1-8 shows how a single AXSM/FRSM-12 connects to redundant lines. Figure 1-8 Single AXSM/FRSM-12 Front Card Configuration with Redundant Lines Working line A Protection line A Working line B AXSM front card Midplane AXSM back cards 45055 Protection line B The redundant lines shown in Figure 1-8 are labeled the working line and the protection line, as defined in the SONET specification for APS.
Chapter 1 Preparing for Configuration Planning for Card and Line Redundancy • Because the AXSM-1-2488 has only one OC-48 port on its back card, this card cannot be configured for intracard APS operation (although it can be configured for intercard APS, which is described later in this chapter). • 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 1 Preparing for Configuration Planning for Card and Line Redundancy • The switch ends of each Y-cable must connect to corresponding ports. For example, the cable connected to line 2 on the active lower bay back card must also connect to line 2 on the standby lower bay back card. • Optical Y-cables must use single-mode fiber (SMF) cable, not multimode fiber (MMF).
Chapter 1 Preparing for Configuration Planning for Card and Line Redundancy • The redundant back cards must be joined together with the APS mini-backplane. • 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. • The working line must be defined on the primary card. • The protection line can be defined on the same back card or on a different back card.
Chapter 1 Preparing for Configuration Planning for Card and Line Redundancy Table 1-2 General Switch Configuration Parameters (continued) Feature Parameter Information Value to Configure IP Addresses Boot IP Boot IP network mask LAN IP LAN IP network mask ATM IP ATM IP network mask SLIP IP SLIP IP network mask SNMP Community Contact Location Table 1-3 lists general switch parameters you will need to configure on each AXSM card.
Chapter 1 Preparing for Configuration Planning for Card and Line Redundancy Table 1-3 General AXSM, AXSM-E, and AXSM-E-32 Card Configuration Parameters (continued) Feature Parameter Information Line 6 APS Working index Value to Configure Protection index Mode Line 7 APS Working index Protection index Mode Line 8 APS Working index Protection index Mode Line 9 APS Working index Protection index Mode Line 10 APS Working index Protection index Mode Line 11 APS Working index Protection index Mo
Chapter 1 Preparing for Configuration Planning for Card and Line Redundancy Table 1-3 General AXSM, AXSM-E, and AXSM-E-32 Card Configuration Parameters (continued) Feature Parameter Information Value to Configure Mode Line 18 APS (AXSM-32-E only) Working index Protection index Mode Line 19 APS (AXSM-32-E only) Working index Protection index Mode Line 20 APS (AXSM-32-E only) Working index Protection index Mode Line 21 APS (AXSM-32-E only) Working index Protection index Mode Line 22 APS (AXSM-
Chapter 1 Preparing for Configuration Planning for Card and Line Redundancy Table 1-3 General AXSM, AXSM-E, and AXSM-E-32 Card Configuration Parameters (continued) Parameter Information Feature Line 27 APS (AXSM-32-E only) Value to Configure Working index Protection index Mode Line 28 APS (AXSM-32-E only) Working index Protection index Mode Line 29 APS (AXSM-32-E only) Working index Protection index Mode Line 30 APS (AXSM-32-E only) Working index Protection index Mode Line 31 APS (AXSM-32-E on
Chapter 1 Preparing for Configuration Planning for Card and Line Redundancy Table 1-4 General FRSM-12 Card Configuration Parameters (continued) Feature Parameter Information Line 2 APS Working index Value to Configure Protection index Mode Line 3 APS Working index Protection index Mode Line 4 APS Working index Protection index Mode Line 5 APS Working index Protection index Mode Line 6 APS Working index Protection index Mode Line 7 APS Working index Protection index Mode Line 8 APS Worki
Chapter 1 Preparing for Configuration Guidelines for Creating an IP Address Plan Guidelines for Creating an IP Address Plan The switch provides the following interfaces for CLI, SNMP, and CWM access: • Console Port (CP) • Maintenance Port (MP) • LAN 1 port • ATM interface Basic switch configuration and management can be completed by using a local terminal connected to the console port.
Chapter 1 Preparing for Configuration Guidelines for Creating an IP Address Plan Note Cisco MGX 8850 software releases prior to Release 2.0(12) supported unique addresses for the boot IP addresses on the PXM45 cards in slots 7 and 8. This approach required three unique addresses per switch. Beginning with Release 2.0(12), the boot IP addresses for both slots 7 and 8 must be set to the same IP address.
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.
Chapter 2 Configuring General Switch Features Configuration Quickstart Step 3 Command Purpose adduser Configure user access. This step is optional. See the “Configuring User Access” section, which appears later in this chapter. Related commands: cnfpasswd cnfuser deluser Step 4 cnfname Configure the switch name. See the “Setting and Viewing the Switch Name” section, which appears later in this chapter.
Chapter 2 Configuring General Switch Features Initializing the Switch Step 10 Command Purpose cnfsnmp community [string] Configure SNMP management. cnfsnmp contact [string] See the “Configuring for Network Management” section which appears later in this chapter. cnfsnmp location [string] Related commands: dspsnmp Step 11 dspcds Verify the hardware configuration. dspcd See the “Verifying the Hardware Configuration” section, which appears later in this chapter.
Chapter 2 Configuring General Switch Features Initializing the Switch Figure 2-1 Workstation Connection to Console Port To initialize the switch, use the following procedure. Step 1 Physically connect a terminal or workstation to the PXM45 UI-S3 back card as shown in Figure 2-1. You can use any personal computer or UNIX workstation with VT-100 emulation software. Note Step 2 You can connect the terminal to a PXM45 in either slot 7 or slot 8.
Chapter 2 Configuring General Switch Features Initializing the Switch Step 5 If the switch does not display any messages or prompt, press Return. When startup is complete for an uninitialized switch, it will display the PXM45 backup boot prompt: pxm45bkup> 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 The number 7 in the switch prompt indicates that you are managing the PXM45 in slot 7. If you are managing the PXM45 in slot 8, the switch prompt displays the number 8. The switch does not display the password during login. When login is complete, the switch prompt appears. The switch prompt for PXM45 and AXSM cards uses the following format: nodename.slot.cardtype.state> Table 2-1 describes the components in the CLI prompt.
Chapter 2 Configuring General Switch Features Starting a CLI Management Session After Initialization Step 10 To change the session time-out period, enter the timeout command as follows: unknown.7.PXM.a > timeout Replace seconds with the number of seconds you want the session to remain active before it times out. The maximum value is 600. To disable time-out, enter 0 seconds. The switch uses the new timeout value until you terminate the session.
Chapter 2 Configuring General Switch Features Ending a CLI Management Session 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.PXM45.i>.In this mode, you can only log in with the user name cisco and the password cisco, and a limited set of commands are available for troubleshooting.
Chapter 2 Configuring General Switch Features Entering Commands at the Switch Prompt To restart the session after entering the bye or exit command, press Return, and the switch will prompt you for a username and password. Entering Commands at the Switch Prompt The commands in the switch operating system are associated with the cards that are installed in the switch. Before you execute a command, you must select a card that supports the command.
Chapter 2 Configuring General Switch Features Entering Commands at the Switch Prompt The default switch configuration allows you to enter command abbreviations. 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 partial commands and displays long reports one page at a time. mgx8850a.7.PXM.
Chapter 2 Configuring General Switch Features Getting Command Help Getting Command Help The following sections describe how to display the following types of command help: • Available commands • Available commands with additional information on access levels and logging • Command syntax and parameters Displaying Command Lists The commands you can use to manage the switch are determined by your user name, which is configured for a particular access level.
Chapter 2 Configuring General Switch Features Getting Command Help To enable detailed command lists, enter the clidbxlevel command as shown in the following example: pop20two.7.PXM.a > clidbxlevel 1 Value of cliDbxLevel is now 1 After you enter this command, you can display detailed command lists by entering the help command as shown in the following example: M8850_LA.7.PXM.
Chapter 2 Configuring General Switch Features Getting Command Help 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 using the addport command. pop20two.1.AXSM.a > addport ERR: incorrect number of parameters: (not enough) Syntax: addport " [vpi]" If Number -- number between 1 and 60 Line Number -- format bay.
Chapter 2 Configuring General Switch Features Configuring User Access Configuring User Access The usernames and passwords supplied with your switch provide access to all switch features, and they allow you to add and delete users and change user passwords. When configuring user access for the switch, consider the following recommendations: • Change the default passwords provided with your switch.
Chapter 2 Configuring General Switch Features Configuring User Access Table 2-4 User Access Levels Access Level Descriptions CISCO_GP This is the highest user access level. Users with this access level have complete access to all commands. There is only one user at the CISCO_GP level, and that username is . The default password for user cisco is . Again, Cisco Systems recommends that you change the default passwords when you install a switch.
Chapter 2 Configuring General Switch Features Configuring User Access To add a user to the switch, use the following procedure. Step 1 Establish a CLI management session with GROUP1 privileges or higher. To add a user at a specific access level, you must log in as a user with a higher access level. Step 2 Enter the following command after the switch prompt: mgx8850a.7.PXM.a >adduser Enter the username using 1 to 12 alphanumeric characters.
Chapter 2 Configuring General Switch Features Configuring User Access Step 4 When prompted, enter a new password, using 5 to 15 characters. Step 5 When prompted, enter the new password a second time to validate the correct entry. This completes the change of password. Step 6 To test the new password, enter the bye command, then log in using the new password.
Chapter 2 Configuring General Switch Features Configuring User Access Deleting Users To delete a user, use the following procedure. Step 1 Establish a CLI management session using a username with privileges at least one level higher than that of the user you want to delete. Step 2 Enter the following command after the switch prompt: mgx8850a.7.PXM.a >deluser Enter the username using from 1 to 12 alphanumeric characters. This step completes the deletion of a user.
Chapter 2 Configuring General Switch Features Setting and Viewing the Switch Name Enabling and Disabling the User cisco Password Reset If the switch you are managing is in an insecure area, you might want to disable the user password reset feature. Otherwise, anyone with physical access to the switch Console Port can reset the password, deny access to other users, and reconfigure the switch.
Chapter 2 Configuring General Switch Features Viewing and Setting the Switch Date and Time Viewing and Setting the Switch Date and Time The switch date and time is appended to event messages and logs. To assure that events are properly time stamped, use the following procedure to view and change the date and time. Step 1 Establish a configuration session using a user name with SUPER_GP privileges or higher.
Chapter 2 Configuring General Switch Features Configuring PNNI Node Parameters Configuring PNNI Node Parameters The Cisco MGX 8850 and Cisco MGX 8950 switches support many PNNI configuration commands. This section describes how to configure the basic PNNI configuration parameters for the switch. Chapter 6, “Managing PNNI Nodes and PNNI Routing,” describes how to manage PNNI after you have brought up the PNNI node.
Chapter 2 Configuring General Switch Features Configuring PNNI Node Parameters Table 2-6 Parameter Descriptions for the addcontroller Command (continued) Parameter Values Descriptions slot 7 Slot number for PXM45 cards. Enter 7 or 8 to specify the PXM45 as the PNNI controller host. cntrlrName text Controller name. This parameter is optional. You can enter a text name to identify the PNNI or MPLS controller.
Chapter 2 Configuring General Switch Features Configuring PNNI Node Parameters Step 5 To display the PNNI node configuration, enter the dsppnni-node command: 8850_LA.7.PXM.a > dsppnni-node The switch displays a report similar to the following: 8850_LA.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..
Chapter 2 Configuring General Switch Features Configuring PNNI Node Parameters Step 4 Note 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 Remote Remote Upnode Upnode Common node name.......8950_SF node id.........56:160:47.00918100000100036b5e31b3.00036b5e31b3.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 In the example above, there is no reference to the ATM address for the remote switch named 8950_SF.
Chapter 2 Configuring General Switch Features Configuring PNNI Node Parameters The switch displays a report similar to the following example: 8850_LA.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.00918100000100001a531c2a.00001a531c2a.01 ATM address...........
Chapter 2 Configuring General Switch Features Configuring PNNI Node Parameters Step 3 To change the SPVC prefix, enter the following command: 8850_LA.7.PXM.a > cnfspvcprfx -prfx Replace prefix with the 13-byte prefix you want to use. For example: 8850_LA.7.PXM.a > cnfspvcprfx -prfx 47.
Chapter 2 Configuring General Switch Features Configuring the MPLS Controller 8850_LA.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 using an external clock source and redundant PXM45 cards, use a Y-cable to connect that clock source to the same clock port on both PXM45 cards. Otherwise, the clock source is available to only one of the PXM45 cards. Release 3 of the MGX switches supports two forms of network clock source configuration: • manual • NCDP Both types of network clock configuration are described in the sections that follow.
Chapter 2 Configuring General Switch Features Configuring Clock Sources Manually Configuring BITS Clock Sources The following procedure describes how to configure the switch to use clock sources on the BITS clock ports. Note For instructions on configuring the switch to use a clock source on an AXSM line, see the “Configuring AXSM Line Clock Sources” section in Chapter 6, “Provisioning AXSM Communication Links.
Chapter 2 Configuring General Switch Features Configuring Clock Sources Note The PXM45 provides a revertive function that can apply when the primary clock source fails. 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-8 cnfncdp Command Parameters (continued) Parameter Description -holdtime Specifies the time interval, in milliseconds, between each PDU configuration. The range is from 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 • Node or 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 Chapter 1, “Guidelines for Creating an IP Address Plan.
Chapter 2 Configuring General Switch Features Setting the LAN IP Addresses The following example shows all options. 8850_NY.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-9 Step 4 bootChange Command Option Descriptions (continued) Option Description user This option defines a username that can be used for FTP access to the boot and runtime software files on a remote server. ftp password This option identifies a password that can be used for FTP access to the boot and runtime software files on a remote server. flags Do not change this option. target name Do not change this option.
Chapter 2 Configuring General Switch Features Setting the LAN IP Addresses Figure 2-3 Note Hardware Required for Local LAN Connections The PXM UI-S3 card shown in Figure 2-1 has two LAN ports. In the current software release, only the LAN 1 connector is enabled for LAN communications. Communication through the LAN 2 connector is disabled. Before you can manage the switch through the PXM45 LAN port, you must first assign an IP address to the LAN port.
Chapter 2 Configuring General Switch Features Setting the LAN IP Addresses To set the IP address, enter the ipifconfig command as described in the following procedure. Step 1 Establish a CLI management session using a username with SUPER_GP privileges. The default user name and password for this level are superuser, superuser. Step 2 Verify that the IP address is not already configured by entering the dspipif command, as shown in the following example. mgx8850a.7.PXM.
Chapter 2 Configuring General Switch Features Setting the LAN IP Addresses Tip You can view the IP routing table for the switch by entering the routeShow command. To manage routes in the routing table, you can use the following commands: routeAdd, routeDelete, routeNetAdd, and routestatShow. Starting a CLI Session Through the LAN Port The switch includes a Telnet server process that you can use to connect to and manage the switch.
Chapter 2 Configuring General Switch Features Configuring for Network Management Step 3 When the Login prompt appears, enter the user name provided with your switch and press Enter. Step 4 When the password prompt appears, enter the password provided with your switch and press Enter. After you successfully log in, a prompt appears that is similar to the prompt in the following example: mgx8850a.7.PXM.
Chapter 2 Configuring General Switch Features Configuring for Network Management The IP address should match the LAN IP address or the ATM interface IP address. For information on setting and viewing the LAN IP address, see “Setting the LAN IP Addresses,” which appears earlier in this chapter. For information on setting and viewing the ATM interface IP address, see “Setting Up ATM WAN Connections” in Appendix C, “Supporting and Using Additional CLI Access Options.
Chapter 2 Configuring General Switch Features Verifying the Hardware Configuration Step 5 To display the SNMP agent configuration, enter the dspsnmp command. The command display appears similar to the following example: pop20two.7.PXM.a > dspsnmp pop20two MGX8850 Community: System Location: System Contact System Rev: 02.01 Dec.
Chapter 2 Configuring General Switch Features Verifying the Hardware Configuration Note If an RPM card is installed in the switch and does not appear in the dspcds command display, the RPM card has not loaded the boot or runtime IOS software. In this case, you need to visually locate the RPM cards by looking for them in the switch.
Chapter 2 Configuring General Switch Features Verifying the Hardware Configuration The dspcd command displays information that is unique to a particular card. For PXM45 cards, the switch displays a report similar to the following example: M8850_LA.7.PXM.a > dspcd 7 M8850_LA System Rev: 02.01 MGX8850 Slot Number 7 Redundant Slot: 8 Front Card ---------Inserted Card: PXM45 Reserved Card: PXM45 State: Active Serial Number: SAK033600AN Prim SW Rev: 2.1(60) Sec SW Rev: 2.1(60) Cur SW Rev: 2.
Chapter 2 Configuring General Switch Features Verifying the Hardware Configuration CLEI Code: BAA1BADAAA Reset Reason: On Power up Card Alarm: NONE Failed Reason: None Miscellaneous Information: 0000000000 Type to continue, Q to stop: M8850_LA System Rev: 02.01 MGX8850 Crossbar Slot Status: BAI9ADTAAA Sep. 27, 2001 20:24:09 PST Node Alarm: NONE Present Alarm Causes -----------NO ALARMS b.
Chapter 2 Configuring General Switch Features Verifying the Hardware Configuration Note The locations where the upper and lower back cards are installed are also called bays. Each slot has an upper and a lower bay for back cards. Table 2-11 Valid Card Installation Options Valid Back MGX 8850 Card Bay Valid Slot Locations Numbers MGX 8950 Valid Slot Numbers Supports APS Connector Front Card Type Description and Part No.
Chapter 2 Configuring General Switch Features Verifying the Hardware Configuration Table 2-11 Valid Card Installation Options (continued) Valid Back MGX 8850 Card Bay Valid Slot Locations Numbers MGX 8950 Valid Slot Numbers Supports APS Connector Front Card Type Description and Part No.
Chapter 2 Configuring General Switch Features Verifying the Hardware Configuration Table 2-11 Valid Card Installation Options (continued) Front Card Type Description and Part No.
Chapter 2 Configuring General Switch Features Verifying the Hardware Configuration Cisco MGX 8850 (PXM45) and MGX 8950 Software Configuration Guide 2-48 Release 3, Part Number 78-14788-01 Rev.
C H A P T E R 3 Preparing AXSM Cards and Lines for Communication This chapter describes how to prepare AXSM cards and lines for physical connectivity to other switches. Chapter 6, “Provisioning AXSM Communication Links,” describes how to add ports and connections that support ATM communications across the cards and lines configured in this chapter.
Chapter 3 Preparing AXSM Cards and Lines for Communication Configuration Quickstart Step 1 Step 2 Command Purpose username Start a configuration session. Note setrev Initialize AXSM cards by setting the firmware version level for each AXSM card. Related commands: To perform all the procedures in this quickstart procedure, you must log in as a user with GROUP1 privileges or higher.
Chapter 3 Preparing AXSM Cards and Lines for Communication Managing Firmware Version Levels for AXSM Cards Managing Firmware Version Levels for AXSM Cards The AXSM cards 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. The runtime firmware file is stored on the PXM45 hard disk.
Chapter 3 Preparing AXSM Cards and Lines for Communication Managing Firmware Version Levels for AXSM Cards Note If any AXSM card displays the Active/Active card state, you do not have to set the runtime firmware version for that card. Also, the Front/Back Card State for slots 12 and 13 show Empty Reserved. These slots will support service modules in a future release. Initializing AXSM Cards Before an AXSM card can operate, it must be initialized in a switch slot.
Chapter 3 Preparing AXSM Cards and Lines for Communication Managing Firmware Version Levels for AXSM Cards Verifying Card Firmware Version Levels When you are having problems with your switch, or when you have taken delivery of a new switch but delayed installation, it is wise to verify the firmware versions installed on the switch. If newer versions of this firmware are available, installing the updated firmware can prevent switch problems.
Chapter 3 Preparing AXSM Cards and Lines for Communication Establishing Redundancy Between Two AXSM Cards 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 3 Preparing AXSM Cards and Lines for Communication Selecting and Viewing Service Class Templates Step 5 Note One of the two cards can be configured before redundancy is established. If this is the case, the configured card should be specified as the primary card. Redundancy cannot be established if the secondary card has active lines. If the secondary card has active lines, you must delete all ports and down all lines before it can be specified as a secondary card.
Chapter 3 Preparing AXSM Cards and Lines for Communication Selecting and Viewing Service Class Templates you do not need to (re)configure the switch. The parameters in the SCTs define generic thresholds and priorities of queues that can be understood without having to go through the programming details of Queuing engines, such as QE48 (in AXSMs) or QE1210 (in AXSME).
Chapter 3 Preparing AXSM Cards and Lines for Communication Selecting and Viewing Service Class Templates Note Users do not have write access to the F:SCT / directory. The only way to download SCT files to the F: directory is to download them to your C:/SCT/Temp directory first. For instructions on downloading and installing SCT files to your switch, see the “Installing SCT Files” section in Appendix A, “Downloading and Installing Software Upgrades.
Chapter 3 Preparing AXSM Cards and Lines for Communication Selecting and Viewing Service Class Templates Step 3 All ports on the card must be down before you can configure the card SCT. To verify the status of the ports on the card, enter the dspports command. M8850_LA.2.AXSM.a > dspports ifNum Line Admin Oper. Guaranteed Maximum State State Rate Rate ----- ---- ----- ----- ---------1 2.1 Up Down 1412830 2 2.2 Up Down 1412830 3 1.
Chapter 3 Preparing AXSM Cards and Lines for Communication Setting Up Lines Reset Reason: Power ON Reset Card Operating Mode: AXSM-A SCT File Configured Version: 1 SCT File Operational Version: 1 Card SCT Id: 5 Type to continue, Q to stop: Step 6 Enter the upport command to bring up any ports you brought down in Step 3. Replace with the interface number of the downed port. M8850_LA.1.AXSM.a > upport 1 Step 7 Enter the dspports command to verify that all ports on the card are up.
Chapter 3 Preparing AXSM Cards and Lines for Communication Setting Up Lines Bringing Up Lines Installing an AXSM card can add from 1 to 16 lines to your switch. You must bring up a line before you can configure the line or provision services on the line. Before a line is brought up, or after it is brought down, the switch does not monitor the line. The AXSM port status light for the line is unlit, and all line alarms are cleared. When you bring up a line, the switch starts monitoring the line.
Chapter 3 Preparing AXSM Cards and Lines for Communication Setting Up Lines Table 3-3 Step 4 AXSM Card Types (continued) Front Card Valid Line Numbers Valid Bay Numbers AXSM-16-155 AXSM-16-155/B 1 to 8 1, 2 AXSM-2-622-E 1 to 1 1, 2 AXSM-4-622 AXSM-4-622/B 1 to 4 1, 2 AXSM-1-2488 AXSM-1-2488/B 1 1 AXSM-32-E 1 to 32 1, 2 Enter the following command: 8850_NY.7.PXM.a > dsplns The line state column shows whether each line is up or down as shown in the following example: 8850_NY.7.PXM.
Chapter 3 Preparing AXSM Cards and Lines for Communication Setting Up Lines Figure 3-1 Bay and Line Numbers SMB-8T3 ENABLED RX Line 1 PORT 1 TX RX Line 2 PORT 2 TX Bay 1 RX Line 3 PORT 3 Slot 14 TX RX Line 4 PORT 4 TX RX Line 5 PORT 5 TX RX Line 6 PORT 6 TX RX Line 7 PORT 7 TX RX Line 8 PORT 8 38424 TX SMB-8T3 ENABLED RX Line 1 PORT 1 TX RX Line 2 PORT 2 Bay 2 TX RX Line 3 PORT 3 TX RX Line 4 PORT 4 TX RX Line 5 PORT 5 TX RX Line 6 PORT 6 TX RX Line 7
Chapter 3 Preparing AXSM Cards and Lines for Communication Setting Up Lines Configuring SONET Lines All line types are brought up with a default configuration. When configuring trunks between two MGX 8850 or MGX 8950 switches, you may be able to accept the defaults for each switch and thus minimize configuration time. When configuring a line to another type of device, ensure that both devices are using the same configuration parameters on the shared line.
Chapter 3 Preparing AXSM Cards and Lines for Communication Setting Up Lines Table 3-4 Parameters for cnfln Command Parameter Line Types Supported AIScBitsCheck T3 The -cb option defines C-bit checking. Set to 1 to enable C-bit checking. Set it to 2 to ignore the C-bit. bay.line T3 E3 SONET Replace bay with 1 if the line is connected to a back card in the upper bay, or replace it with 2 if the line is connected to a back card in the lower bay.
Chapter 3 Preparing AXSM Cards and Lines for Communication Setting Up Lines Configuring T3 Lines All line types are brought up with a default configuration. When configuring trunks between two MGX 8850 or MGX 8950 switches, you may be able to accept the defaults for each switch and thus minimize configuration time. When configuring a line to another type of device, ensure that both devices are using the same configuration parameters on the shared line.
Chapter 3 Preparing AXSM Cards and Lines for Communication Setting Up Lines Configuring E3 Lines All line types are brought up with a default configuration. When configuring trunks between two MGX 8850 or MGX 8950 switches, you may be able to accept the defaults for each switch and thus minimize configuration time. When configuring a line to another type of device, ensure that both devices are using the same configuration parameters on the shared line.
Chapter 3 Preparing AXSM Cards and Lines for Communication Establishing Redundancy Between Two Lines with APS Line Type Medium Type(SONET/SDH) Medium Time Elapsed Medium Valid Intervals Medium Line Type Table 3-5 : : : : : sonetSts12c SONET 248198 96 ShortSMF Number of SPVC Number of SVC : 0 : 4 dspln Command Parameters Parameter Description type The parameter specifies the type of line that is connected to the switch. Replace with -sonet or -ds3.
Chapter 3 Preparing AXSM Cards and Lines for Communication Establishing Redundancy Between Two Lines with APS Replace with the option number that selects the automatic protection switching (APS) architecture mode you want to use. Table 3-6 shows the option numbers and the architecture modes they select. Table 3-6 APS Line Architecture Modes Option Description 1 Selects 1+1 signaling (transmission on both working and protect lines) for intracard APS.
Chapter 3 Preparing AXSM Cards and Lines for Communication Establishing Redundancy Between Two Lines with APS Adding Intercard APS Lines To establish redundancy between two lines on different cards, use the following procedure. Note For intercard APS to operate properly, an APS connector must be installed between the two cards.
Chapter 3 Preparing AXSM Cards and Lines for Communication Establishing Redundancy Between Two Lines with APS Step 6 Enter the dspapsbkplane command on both the standby and active cards to verify that the APS connector is installed properly. Note Step 7 This command can show different values for each of the two cards, which indicates the APS connector is seated properly on one card, but not on the other. To display the a list of all the APS lines on an AXSM card, enter the dspapslns command.
C H A P T E R 4 Preparing FRSM12 Cards and Lines for Communication This chapter describes how to prepare FRSM12 cards for standalone or redundant operation in Cisco MGX Release 3 switches. Frame Relay Services for MGX Release 3.0 Switches describes how to provision these cards for Frame Relay communications across an ATM network.
Chapter 4 Preparing FRSM12 Cards and Lines for Communication Managing Firmware Version Levels for FRSM12 Cards Step 3 Command Purpose addred Define which FRSM12 cards are operating as redundant cards. Related commands: See “Establishing Redundancy Between Two FRSM12 Cards,” which appears later in this chapter.
Chapter 4 Preparing FRSM12 Cards and Lines for Communication Managing Firmware Version Levels for FRSM12 Cards The following example shows the display for this command. The card state for the card in slot 4 is listed as Failed/Active. This is how a card appears when the runtime firmware version has not been selected. hsfrnd6.8.PXM.a > dspcds hsfrnd6 System Rev: 03.
Chapter 4 Preparing FRSM12 Cards and Lines for Communication Managing Firmware Version Levels for FRSM12 Cards Initializing FRSM12 Cards Before a FRSM12 card can operate, it must be initialized in a switch slot. The initialization process defines the FRSM12 runtime software version that will run on the card and identifies the slot in which the card operates. To initialize an FRSM12 card, use the following procedure. Note Step 1 The PXM45 card supports a maximum of 99 lines on the switch.
Chapter 4 Preparing FRSM12 Cards and Lines for Communication Managing Firmware Version Levels for FRSM12 Cards To verify the firmware versions in use on your switch, use the following procedure. Step 1 To display the software revision status of all the cards in a switch, enter the dsprevs command as follows: hsfrnd6.8.PXM.
Chapter 4 Preparing FRSM12 Cards and Lines for Communication Establishing Redundancy Between Two FRSM12 Cards Reset Reason:Power ON Reset Type to continue, Q to stop: Card Alarm: Card Summary: Card SCT Id: 0 !DefaultSCT used! #Lines #Ports #Partitions ------ ------ ----------11 10 10 #SPVC #MaxConns ------ --------1 16000 Step 4 Using the dsprevs and dspcd commands, complete the hardware and software configuration worksheet in Table 2-8.
Chapter 4 Preparing FRSM12 Cards and Lines for Communication Selecting and Viewing Service Class Templates Tip Step 5 If the switch displays the message, ERR: Secondary cd is already reserved, then lines are already in use on the specified secondary card. Use the dnln command to bring down these lines before re-entering the addred command, or enter the clrsmcnf command for the secondary card.
Chapter 4 Preparing FRSM12 Cards and Lines for Communication Selecting and Viewing Service Class Templates Note When an FRSM12 card is powered up for the first time, the default card SCT file is used. You must run this command in order to use another SCT file. The default SCT file is 0. Replace sctID with the number of the SCT that you want to assign to the card. For PNNI communications, use SCT ID 2 or 4 for policing applications and use SCT ID 3 or 5 for non-policing applications.
C H A P T E R 5 Preparing RPM-PR Cards for Operation This chapter describes how to do the following tasks: Note • Determine which slots host the RPM-PR cards • Initialize RPM-PR cards that are installed in the switch • Verify the software version used on the RPM-PR cards • Configure backup cards for RPM-PR cards • Where to find additional information on configuring RPM-PR cards Some of the procedures in this chapter require you to enter Cisco IOS commands that runs on the RPM-PR cards.
Chapter 5 Preparing RPM-PR Cards for Operation Locating RPM-PR Cards in the Switch Step 3 Command Purpose boot system c: Initialize RPM-PR cards by identifying a runtime software file and storing the configuration on the PXM45 hard disk. boot config e:auto_config_slot copy run start See the “Initializing RPM-PR Cards” section, which appears later in this chapter. cc 7 resetcd slot Related commands: dspcds Step 4 show version Verify the software version for each RPM-PR card.
Chapter 5 Preparing RPM-PR Cards for Operation Initializing RPM-PR Cards The following example shows the dspcd command display for an RPM-PR card: 8850_NY.7.PXM.a > dspcd 9 8850_NY System Rev: 02.
Chapter 5 Preparing RPM-PR Cards for Operation Initializing RPM-PR Cards When the RPM-PR card starts or reboots, it searches for the configuration file in the following sequence: • If there is a configuration file only on the PXM45 hard disk, the RPM-PR card uses the configuration stored on the hard disk. • If there is no configuration file on the hard disk, then the NVRAM version is used.
Chapter 5 Preparing RPM-PR Cards for Operation Initializing RPM-PR Cards Step 4 Verify the configuration status of the RPM-PR card by entering the show bootflash: command. For example, Router>show bootflash: -#- ED --type-- --crc--- -seek-- nlen -length- -----date/time------ name 1 .. image BAC7D50E 2B80EC 27 2588780 Jul 12 2001 23:05:26 rpm-boot-mz_122-4.T 2 ..
Chapter 5 Preparing RPM-PR Cards for Operation Initializing RPM-PR Cards The RPM-PR configuration file is named: auto_config_slot. The slot portion of the name must match the slot number that corresponds to the RPM-PR card. Note Step 11 The configuration is also stored in NVRAM using the name startup-config. Exit global configuration mode and save your changes with the copy run start command. For example, Router(config)#^Z Router#copy run start Building configuration...
Chapter 5 Preparing RPM-PR Cards for Operation Verifying the Software Version in Use Verifying the Software Version in Use To verify which version of software an RPM-PR card is using, you need to use Cisco IOS commands at the router prompt for the RPM-PR card. The following example shows how to do this with the show version command: Router#show version Cisco Internetwork Operating System Software IOS (tm) RPM Software (RPM-JS-M), Experimental Version 12.
Chapter 5 Preparing RPM-PR Cards for Operation Establishing Redundancy Between Two RPM-PR Cards To establish a backup card for an RPM-PR card, use the following procedure. Step 1 Establish a configuration session using a user name with SUPER_GP privileges or higher. Step 2 If you have not done so already, initialize both cards as described earlier in the “Initializing RPM-PR Cards” section. Step 3 Use the dspcds command to verify that both RPM-PR cards are in the “Active” state.
Chapter 5 Preparing RPM-PR Cards for Operation Configuring SNMP on the RPM-PR Card For information on managing redundant cards, see the “Managing Redundant Cards” section in Chapter 7, “Switch Operating Procedures.” Configuring SNMP on the RPM-PR Card To configure the SNMP community string on an RPM-PR card, you need to use Cisco IOS commands at the router prompt for the RPM-PR card. The following example shows how to do this.
Chapter 5 Preparing RPM-PR Cards for Operation Where to Go Next Where to Go Next After the RPM-PR card is initialized and any required redundancy is established, you can configure the RPM-PR card to operate in either of the following roles: • Label Switch Controller (LSC) • Label Edge Router (LER) In either the LSC or the LER role, the RPM-PR communicates with other ATM switches using MPLS AXSM communications links.
C H A P T E R 6 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. This chapter includes the following sections: Note • Managing PNNI Nodes • Managing PNNI Route and Link Selection • Displaying Node Configuration Information The concepts behind the procedures in this chapter are introduced in the Cisco MGX and SES PNNI Network Planning Guide.
Chapter 6 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 6-1.
Chapter 6 Managing PNNI Nodes and PNNI Routing Managing PNNI Nodes Step 3 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: 8950_SF.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...............0:0:00.
Chapter 6 Managing PNNI Nodes and PNNI Routing Managing PNNI Nodes The first time the dsppnni-election command was entered, the PGL state was OperNotPgl, which means that the node is operating, but is not operating as a PGL. After the priority is changed, the PGL state changes to AwaitUnanimity, which means the node is communicating with the other nodes in its peer group to see if it has the highest priority and should be PGL.
Chapter 6 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: 8850_LA.7.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 6 Managing PNNI Nodes and PNNI Routing Managing PNNI Nodes Table 6-1 lists the parameter descriptions for the addpnni-summary-addr command. Table 6-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 ATM address prefix assigned to the network. prefix-length Length of the summary address-prefix in number of bits, equal or less than 152 bits.
Chapter 6 Managing PNNI Nodes and PNNI Routing Managing PNNI Nodes Table 6-3 Parameters for cnfpnni-routing-policy Command Parameter Description -sptEpsilon Indicates the node’s policy in determining equal-cost path during routes calculation. -sptHolddown Defines the node’s minimum time interval between two consecutive calculations for generating routing tables.
Chapter 6 Managing PNNI Nodes and PNNI Routing Managing PNNI Route and Link Selection Table 6-4 Parameters for cnfpnni-timer Command Parameter Description node-index Logical node’s node index. -ptseholddown The number is used as a multiplier of the Hello interval of the peer neighbor: the product is the maximum time that the neighbor is considered to be alive without the reception of its Hello packets. Range: (0.
Chapter 6 Managing PNNI Nodes and PNNI Routing Managing PNNI Route and Link Selection To configure the route selection method, enter the cnfpnni-routing-policy command as follows: 8850_LA.7.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: 8850_LA.7.PXM.a > dsppnni-routing-policy SPT SPT SPT CTD epsilon.....
Chapter 6 Managing PNNI Nodes and PNNI Routing Managing PNNI Route and Link Selection Note Release 3 of the MGX switches supports up to 5000 preferred routes per switch. A preferred route consists of a sequential list of nodes and links between nodes that stretch from the local node to the destination node. Each node and link in the preferred route must be within the same peer group as the originating node. A node can appear only once in the preferred route.
Chapter 6 Managing PNNI Nodes and PNNI Routing Managing PNNI Route and Link Selection Step 2 Enter the addpref command to set up your preferred route as follows: 8850_LA.7.PXM.a > addpref [-name ] [-h1 ]...[-h20 ] Table 6-5 describes the addpref command parameters. Table 6-5 Parameters for addpref Command Parameter Description -name Name of the preferred route. To use node names, type -name yes. The choice is yes or no.
Chapter 6 Managing PNNI Nodes and PNNI Routing Managing PNNI Route and Link Selection Associating an SPVC or an SPVP with a Preferred Route Use the following procedure to associate an SPVC or SPVP with a preferred route. Step 1 Create the preferred route by the addpref command, as shown in the previous section.
Chapter 6 Managing PNNI Nodes and PNNI Routing Managing PNNI Route and Link Selection Table 6-6 Parameters for cnfconpref Command -direct Change the directed route status. A directed route means the preferred route associated with the connection is the only route the connection can take. If the preferred route is not available, the connection is failed. Type -direct yes to make the route identified by rteID a directed route for the associated connection. The connection is identified by portid vpi vci.
Chapter 6 Managing PNNI Nodes and PNNI Routing Managing PNNI Route and Link Selection Table 6-7 modpref Command Parameters Parameter Description rteID The preferred route identifier has a range of 1-5000. -name Enter yes to specify that the node identifier is actually the name of the node. You can see the current choice for node identifier (either by index or name) by using the dsppref command. To identify the name or persistent index number by using the dsptopondlist command.
Chapter 6 Managing PNNI Nodes and PNNI Routing Managing PNNI Route and Link Selection Configuring Link Selection for Parallel Links When parallel links exist between two nodes on a route, the node closest to the originating node selects a link based on one of the following parameters: Note • The lowest Administrative Weight (minaw) • The maximum available cell rate (maxavcr) • The maximum cell rate configured for the link (maxcr) • Random link selection (loadbalance) The route selection process
Chapter 6 Managing PNNI Nodes and PNNI Routing Managing PNNI Route and Link Selection 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.) For each class of service for which you want to change the AW value, enter the appropriate option followed by the new value. For example, the following command sets the AW for CBR calls over the link: 8850_LA.7.PXM.a > cnfpnni-intf 1:2.
Chapter 6 Managing PNNI Nodes and PNNI Routing Displaying Node Configuration Information maxVc: 100% minVc: 1% maxVcBw: 0 100% 100% 100% 100% 100% 0% 0% 0% 0% 0% 0 0 0 0 0 Displaying Node Configuration Information The following sections describe commands that display PNNI configuration information. Displaying the PNNI Node Table Once a PNNI node is configured, enter the dsppnni-node command to show the WAN nodal table.
Chapter 6 Managing PNNI Nodes and PNNI Routing Displaying Node Configuration Information Displaying the PNNI Summary Address Enter the dsppnni-summary-addr command to display PNNI summary addresses as follows: Geneva.7.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 the network.
Chapter 6 Managing PNNI Nodes and PNNI Routing Displaying Node Configuration Information 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.00/160 Type: host Port id: 17251106 47.0091.8100.0000.0030.ff0f.ef38.0000.010d.1820.00/160 Type: host Port id: 17251106 47.0091.8100.0000.0030.ff0f.ef38.0000.010d.1821.00/160 Type: host Port id: 17251106 47.0091.8100.0000.0030.ff0f.ef38.0000.010d.1822.
Chapter 6 Managing PNNI Nodes and PNNI Routing Displaying Node Configuration Information Table 6-9 describes the objects displayed for the dsppnni-intf command. Table 6-9 Objects Displayed for the dsppnni-intf Command Parameter Description portid 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.
Chapter 6 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 6 Managing PNNI Nodes and PNNI Routing Displaying Node Configuration Information Table 6-10 Objects Displayed for the dsppnni-routing-policy Command Parameter Description onDemand The on-demand routing rule. On-demand routing is used. Firstfit routing selects the first route found that goes to the selected destination. Firstfit route search time is minimized, but the selected route is not optimum. Bestfit routing selects a route based on the least-cost.
Chapter 6 Managing PNNI Nodes and PNNI Routing Displaying Node Configuration Information Table 6-11 Objects Displayed for the dsppnni-svcc-rcc-timer Command Parameter Description callingIntegrityTime The amount of time (in seconds) this node will wait for an SVCC, which it has initiated establishment of as the calling party, to become fully established before giving up and tearing it down.
Chapter 6 Managing PNNI Nodes and PNNI Routing Displaying Node Configuration Information 2wayOutside Common. remote node id - 22-byte hex string. remote node ATM address - 20 byte hex string. interface index - 32-bit number. Hello packets received - 32-bit number. Hello packets transmitted - 32-bit number. SVCC VPI - 32-bit number. SVCC VCI - 32-bit number. Cisco MGX 8850 (PXM45) and MGX 8950 Software Configuration Guide 6-24 Release 3, Part Number 78-14788-01 Rev.
C H A P T E R 7 Switch Operating Procedures This chapter describes procedures you can use to manage the Cisco MGX 8850 and Cisco MGX 8950 switches. 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. Saving a Configuration After configuring your switch or after making configuration updates, it is wise to save the configuration.
Chapter 7 Switch Operating Procedures Managing the Configuration Files You can save a configuration if both of the following are true: Caution • No save or restore process is currently running. • No configuration changes are in progress. Make sure that no other users are making configuration changes when you save the configuration. The Cisco MGX 8850 and Cisco MGX 8950 switches do not check for other CLI or CWM users before saving a configuration.
Chapter 7 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: pop20one.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 7 Switch Operating Procedures Managing the Configuration Files Caution Make sure that no other users are making configuration changes when you restore the configuration. The Cisco MGX 8850 and Cisco MGX 8950 switches do not check for other CLI or CWM users before restoring a configuration. If other users make changes while the file is being restored, the configuration can become corrupt, the switch can fail, and you might have to send switch cards back to the factory for reprogramming.
Chapter 7 Switch Operating Procedures Managing ILMI Managing ILMI The following sections describe how to perform the following tasks: • Enable and disable ILMI on a port • Display ILMI port configuration data • Display and clear ILMI management statistics • Delete ILMI prefixes Enabling and Disabling ILMI on a Port The Cisco MGX 8850 and Cisco MGX 8950 switches provide several commands that you can use to enable or disable ILMI on a port.
Chapter 7 Switch Operating Procedures Managing ILMI Displaying the ILMI Port Configuration The following procedure describes some commands you can use to view the ILMI port configuration. Step 1 Establish a configuration session using a user name with access privileges at any level. Step 2 To display the ILMI configuration for all ports on an AXSM card, enter the dspilmis command. The following example shows the dspilmis command report. pop20two.1.AXSM.a > dspilmis Sig.
Chapter 7 Switch Operating Procedures Managing ILMI Replace ifnum with the interface number of the port, and replace partitionID with the partition number assigned to the port. You can view both of these numbers in the dspilmis command report. The following is an example report for the dspilmi command. Table 7-2 describes each of the columns that appear in the command report. pop20one.10.AXSM.a > dspilmi 1 1 Sig.
Chapter 7 Switch Operating Procedures Managing ILMI Replace portid using the format slot:bay.line:ifNum. Table 7-1 describes these parameters. The following example shows the format of the dsppnilmi command report. pop20one.7.PXM.a > dsppnilmi 10:1.1:1 Port: 10:1.
Chapter 7 Switch Operating Procedures Managing ILMI Step 2 To clear the ILMI management statistics for a port, enter the clrilmicnt command as follows: pop20one.10.AXSM.a > clrilmicnt 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 switch response to this command. pop20one.10.AXSM.
Chapter 7 Switch Operating Procedures Determining the Software Version Number from Filenames Determining the Software Version Number from Filenames The following version management commands require a version number to be entered in a specific format as follows: • abortrev • burnboot • commitrev • loadrev • runrev • setrev In most cases, you will find the correct firmware version numbers in the Release Notes for Cisco MGX 8850 and MGX 8830 Software Version 3 (PXM45/B and PXM1E) or the Release
Chapter 7 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 7-1 Filenames that include “_mgx” are for runtime PXM45 firmware, and filenames that include “_bt” are for boot firmware.
Chapter 7 Switch Operating Procedures Displaying Software Revisions in Use Table 7-3 shows some example filenames and the correct version numbers to use with the revision management commands. Table 7-3 Determining Firmware Version Numbers from Filenames Filename Version Number for Revision Management Commands pxm45_002.000.000.000_bt.fw 2.0(0) pxm45_002.000.001.000_bt.fw 2.0(1) axsm_002.000.001.001.fw 2.0(1.1) pxm45_002.000.001-D_mgx.fw 2.0(1)D pxm45_002.000.014-A1_bt.fw 2.0(14)A1 axsm_002.
Chapter 7 Switch Operating Procedures Displaying Software Revisions in Use To display the upgrades status of the runtime software on all switch cards, enter the dsprevs -status command as shown in the following example: pop20one.7.PXM.a > dsprevs -status pop20one System Rev: 02.00 Jan. 24, 2001 18:37:16 PST MGX8850 Node Alarm: NONE Phy. Log.
Chapter 7 Switch Operating Procedures Managing Redundant Cards Managing Redundant Cards The Cisco MGX 8850 and Cisco MGX 8950 switches support redundancy between two cards of the same type. For PXM45 cards, this redundancy is preconfigured on the switch. To establish redundancy between two AXSM cards, enter the addred command as described in the “Establishing Redundancy Between Two AXSM Cards” section in Chapter 3, “Preparing AXSM Cards and Lines for Communication.
Chapter 7 Switch Operating Procedures Managing Redundant Cards The dspcds command should list one card as active and one card as standby. If the cards are not in their proper states, the switchover cannot take place. Step 3 To switch cards, enter the switchcc command after the switch prompt. mgx8850a.7.PXM.a > switchcc Switching Between Redundant AXSM Cards To switch operation from an active redundant AXSM card to the standby card, use the following procedure.
Chapter 7 Switch Operating Procedures Managing Redundant APS Lines Removing Redundancy Between Two Cards To remove the redundant relationship between two AXSM cards, use the following procedure. Step 1 Establish a configuration session using a user name with GROUP1_GP privileges or higher. Step 2 To remove card redundancy, enter the following command after the switch prompt: mgx8850a.7.PXM.a > delred Replace primarySlot with the number of the primary card.
Chapter 7 Switch Operating Procedures Managing Redundant APS Lines Top Back Card Bottom Back Card : ENGAGED : ENGAGED The following example shows the results displayed by the dspapsbkplane command when the APS connector is not place: M8850_LA.1.AXSM.a > dspapsbkplane Line-ID 1.1 1.2 2.1 2.
Chapter 7 Switch Operating Procedures Managing Redundant APS Lines Figure 7-3 shows an example of how this process operates in a standard APS configuration, where the primary card monitors the working line and the secondary card monitors the protection line.
Chapter 7 Switch Operating Procedures Managing Redundant APS Lines Crossed APS Configuration Remote node Local node AXSM front card Secondary card Standby card AXSM front card Primary card Active card 1 1 2 APS connector Backcard Tx Rx 2 Backcard 2 AXSM front card Secondary card Active card 6 5 Backcard APS connector 6 Tx Rx 3 Tx Rx 2 AXSM front card Primary card Standby card 4 Backcard Tx Rx 3 70055 Figure 7-4 Working line Active line Signal Physical line Protection line Stendby line
Chapter 7 Switch Operating Procedures Managing Redundant APS Lines Table 7-4 cnfapsln Command Parameters Parameter Description -w Slot number, bay number, and line number of the active line to configure, in the format: slot.bay.line Example: -w 1.1.
Chapter 7 Switch Operating Procedures Managing Redundant APS Lines Table 7-4 cnfapsln Command Parameters (continued) Parameter Description -w Slot number, bay number, and line number of the active line to configure, in the 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 7 Switch Operating Procedures Managing Redundant APS Lines Table 7-5 switchapsln Command Parameters (continued) Parameter Description switchOption The method of performing the switchover. service switch • 1 = Clear previous user switchover requests. Return to working line only if the mode is revertive. • 2 = Lockout of protection. Prevents specified APS pair from being switched over to the protection line.
Chapter 7 Switch Operating Procedures Managing Redundant APS Lines Displaying APS Line Information To display the APS line redundancy configuration for an AXSM card, enter the dspapsln command as described below. Step 1 Establish a configuration session at any access level. Step 2 To view the redundancy status, enter the following command after the switch prompt: pop20one.9.AXSM.a > dspapsln After you enter the command, the switch displays a report similar to the following: pop20one.9.AXSM.
Chapter 7 Switch Operating Procedures Managing Redundant APS Lines Table 7-6 Options for cnfapsln Command (continued) Option Description -wtr The number of minutes to wait before attempting to switch back to the working line. Replace with a number in the range of 1 to 12 (minutes). Note -dr This option is applicable only when the -rv option is set to 2, enabling revertive operation.
Chapter 7 Switch Operating Procedures Managing Redundant APS Lines Table 7-7 Options for switchapsln Command Option Value Description switchOption 1 Clear. 2 Lockout of protection. 3 Forced working->protection. 4 Forced protection->working. 5 Manual working->protection. 6 Manual protection->working; applies only to 1+1 mode. 0 or 1 0 switches specified line. 1 switches all lines.
Chapter 7 Switch Operating Procedures Managing Redundant APS Lines If an AXSM front card fails, APS communication between the redundant front cards fails. This can result in one of the following situations: • If both APS lines were working before the failure, an APS line failure causes a switchover to the protection line • If either APS line failed prior to a front card failure, a failure on the active line does not cause a switchover to the other line.
Chapter 7 Switch Operating Procedures Managing Network Clock Sources Table 7-8 Troubleshooting APS Line Problems Using the dspaps Command (continued) Active Line Working Line Protection Line Working Line LED Protection Line LED Protection SF SF Red Red Active card is not receiving signal from either line. The protection line was the last line to work. Working UNAVAIL — — The card set is not complete. One or more cards have failed or been removed. See Table 7-9 to troubleshoot card errors.
Chapter 7 Switch Operating Procedures Managing Network Clock Sources In an SNTP server/client configuration, the SNTP client periodically receives TOD requests from the primary server. If the primary server is not available for some reason, the SNTP client switches over the next available secondary server for TOD information until the primary server comes back up. An SNTP server can reside on an active PXM in an MGX and in and SES switch.
Chapter 7 Switch Operating Procedures Managing Network Clock Sources The following example shows the addsntprmtsvr command: M8850_LA.8.PXM.a > addsntprmtsvr 172.29.52.88 -version 4 -primary yes M8850_LA.8.PXM.a > Step 5 Enter the addsntprmtsvr command again to configure the secondary server. M8850_LA.8.PXM.a > addsntprmtsvr -version {version} -primary no This time, replace with the primary server’s IP address.
Chapter 7 Switch Operating Procedures Managing Network Clock Sources Table 7-12 describes the cnfsntprmtsvr command parameters. Table 7-12 cnfsntprmtsvr Command Parameters Parameter Description server IP address Server’s IP Address in dotted decimal format. version Sets the SNTP version number. primary Determines whether the server is primary or secondary. Enter yes for primary, or no for secondary. The default is no. The following example shows the cnfsntprmtsvr command: M8850_LA.8.PXM.
Chapter 7 Switch Operating Procedures Managing NCDP Clock Sources Displaying the Current SNTP Configuration Enter the dspsntp command at the active PXM45 prompt on the server to display the client requesting the TOD information from the current server. M8850_NY.8.PXM.a > dspsntp client: yes server: yes polling: 64 waiting: 5 rollback: 1024 stratum(default): 3 stratum(current): 3 sync: no Table 7-13 shows the objects displayed for the dspsntp command.
Chapter 7 Switch Operating Procedures Managing NCDP Clock Sources Configuring an NCDP Clock Source When you enable NCDP through the cnfncdp command, NCDP automatically selects the root clock source based on the following criteria: • Priority (should be sufficient to find the root) • Stratum level (should be sufficient as a tie-breaker) • Clock source reference • ATM address of the switch You can manipulate these criteria and specify a clock source through the cnfncdpclksrc command, as s
Chapter 7 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 1 -vci 1 -admincost 1 -pcr 200 -scr 100 -mcr50 Table 7-15 describes the cnfncdpport command options.
Chapter 7 Switch Operating Procedures Managing NCDP Clock Sources Table 7-15 cnfncdpport Command Parameters (continued) Parameter Description -scr Specifies the sustained cell rate (SCR) for the port. Default = 150 cells per second -mbs Specifies the maximum burst size (MBS) for the port. Default = 100 cells Enter the dspncdpport command to verify that the NCDP parameters were set properly. M8850_LA.8.PXM.a > dspncdpport 1:2.
Chapter 7 Switch Operating Procedures Managing NCDP Clock Sources Table 7-16 dspncdp Command Objects Parameter Description Distribution Mode Current enabled method of clock distribution. If the method chosen is manual, NCDP is turned off, and vice-versa. Node stratum level Stratum level of the clock source. Possible levels are 1, 2E, 2, 3E, 3,4E, or 4. Max network diameter Maximum network diameter measured in hops.
Chapter 7 Switch Operating Procedures Managing NCDP Clock Sources Table 7-17 dspncdpclksrc Command Objects Parameter Description Best clock source Describes whether the specified clock source is currently the best (or root) clock source in the network. Priority Displays the specified clock source’s priority. Stratum Level Stratum level of the specified clock source. Possible levels are 1, 2E, 2, 3E, 3,4E, or 4. Primary reference src id Displays the specified clock sources ID.
Chapter 7 Switch Operating Procedures Managing NCDP Clock Sources Table 7-18 dspncdpclksrcs Command Objects Parameter Description PortID Current enabled method of clock distribution. If the method chosen is manual, NCDP is turned off, and vice-versa. Best clk src Displays Yes if a clock source is a root clock source or a second best clock source, or displays No if a clock source is not a root or second best clock source. Priority Priority of each clock source.
Chapter 7 Switch Operating Procedures Managing NCDP Clock Sources Table 7-19 describes the objects displayed by the dspncdpports command. Table 7-19 dspncdpports Command Objects Parameter Description PortID Port identifier in the format slot:bay.line:ifnum. Table 7-1 describes these parameters. Clock mode Displays whether NCDP is enabled or disabled on each port. Clock Vpi Displays the VPI of the signaling channel for each port. Clock Vci Displays the VCI of the signaling channel for each port.
Chapter 7 Switch Operating Procedures Managing Manually Configured Clocks Sources Table 7-20 dspncdpport Command Objects (continued) Parameter Description SCR Displays the sustained cell rate (SCR) for the port. MBS Displays the maximum burst size (MBS) for the port. Deleting an NCDP Clock Source Enter the delncdpclksrc command to delete a clock source from the network. Replace with the 7.35 (for E1 ports) or 7.36 (for T1 ports). M8850_LA.8.PXM.a > delncdpclksrc 7.35 M8850_LA.8.
Chapter 7 Switch Operating Procedures Managing Manually Configured Clocks Sources In the following example, the display shows that both the primary and secondary clocks are configured for network clock sources. The primary clock source is coming from port 4 on the AXSM card in slot 10. The primary clock source is active. The secondary clock source is coming from port 1 on the AXSM card in slot 9. pop20one.7.PXM.a > dspclksrcs Primary clock type: generic Primary clock source: 10:2.
Chapter 7 Switch Operating Procedures Managing Manually Configured Clocks Sources Step 3 To delete a clock source, enter the delclksrc command. mgx8850a.7.PXM.a > delclksrc The following example deletes a primary clock source. mgx8850a.7.PXM.a > delclksrc primary Step 4 To verify that a clock source has been deleted, enter the dspclksrcs command. When the primary or secondary clock source is deleted, the clock type is set to null.
Chapter 7 Switch Operating Procedures Managing Feeder Connections Managing Feeder Connections The procedure for defining feeder connections is described in Chapter 6, “Provisioning AXSM Communication Links.” Table 7-21 lists commands that you can use to manage feeder connections. Table 7-21 Feeder Management Commands Command Description dspfdrs Display the feeders configured on an AXSM card. dspfdr Display the feeder configuration for a specific interface.
Chapter 7 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. pop20two.9.PXM45.a > addcontroller i [cntrlrName} Table 7-22 describes the parameters for this command.
Chapter 7 Switch Operating Procedures Managing Controllers Step 3 To display all controllers on the switch and verify the added controller, enter the dspcontrollers command. MGX8850.7.PXM.a > dspcontrollers MGX8850 MGX8850 Number of Controllers: Controller Name: Controller Id: Controller Location: Controller Type: Controller Logical Slot: Controller Bay Number: Controller Line Number: Controller VPI: Controller VCI: Controller In Alarm: Controller Error: System Rev: 02.00 Jul.
Chapter 7 Switch Operating Procedures Managing Service Class Templates Managing Service Class Templates Service Class Templates (SCTs) are introduced in the “Selecting and Viewing Service Class Templates” section in Chapter 3, “Preparing AXSM Cards and Lines for Communication.” Separate SCTs are available for PXM1E, AXSM, and FRSM cards. Individual SCT settings cannot be modified using the CLI.
Chapter 7 Switch Operating Procedures Managing Service Class Templates Type to continue, Q to stop: card sct sctid major minor checksum status Description type type ver ver ------ ---- ----- ----- ----- -------- ------ ----------------AXSM CARD 00113 00001 0 0x5f9d2e0f valid default_upgrade AXSM CARD 00114 00001 0 0x67c63533 valid default_upgrade AXSM CARD 00115 00001 0 0x6fef3c57 valid default_upgrade AXSM CARD 00121 00001 1 0x7189a28c valid default_upgrade AXSM CARD 00122 00001 1 0x6fae1018 va
Chapter 7 Switch Operating Procedures Managing Service Class Templates The dspports report displays a column labeled “Port SCT Id,” which identifies the SCT assigned to each port, as shown in the following example: pop20two.1.AXSM.a > dspports ifNum Line Admin Oper. Guaranteed Maximum Port SCT Id ifType VPI State State Rate Rate (VNNI only) ----- ---- ----- ----- ---------- --------- ----------------- ------ ---------1 1.1 Up Up 1412830 1412830 2 NNI 0 2 1.2 Up Up 1412830 1412830 2 NNI 0 3 2.
Chapter 7 Switch Operating Procedures Managing Service Class Templates Select one of the options to display one of the five SCT configuration reports, and replace with the number of the port you want to view. Table 7-24 describes the reports for each of these options.
Chapter 7 Switch Operating Procedures Managing Service Class Templates Table 7-25 describes the SCT General Parameters shown in the example. Table 7-25 Service Class Template: SCT General Parameters Parameter Range SERV-TYPE COSB_NUM Description The service type (for example, CBR, VBR, ABR) to which the parameters (for example, COSB_NUM, CAC_TYPE, UPC_ENB) in this table apply. 1 to 16 CAC_TYPE Class of Service Buffer Number. The number that identifies one of the sixteen CoS buffers.
Chapter 7 Switch Operating Procedures Managing Service Class Templates Table 7-25 Service Class Template: SCT General Parameters (continued) Parameter Range Description GCRA-2 1 to 3 Generic Cell Rate Algorithm – Bucket 2. In ATM, an algorithm that defines conformance with respect to the traffic contract of the connection. For each cell arrival, the GCRA determines whether the cell conforms to the traffic contract. Note If UPC-Enable is set to disable, this object is not used.
Chapter 7 Switch Operating Procedures Managing Service Class Templates Table 7-26 Service Class Template: SCT COSB Parameters Label Range and Units Description COSB — Class of Service Buffer. A buffer or queue which serves connections with similar QoS requirements. MIN-RATE 1—1000000 This field is no longer used and is currently always set to its default value (0) and will be removed in future releases.
Chapter 7 Switch Operating Procedures Managing Service Class Templates | VBR-RT.1 | 0000002 | 0000002 | VBR-RT.2 | 0000002 | 0000002 | VBR-RT.3 | 0000002 | 0000002 | VBR-nRT.1 | 0000002 | 0000002 | VBR-nRT.2 | 0000002 | 0000002 | VBR-nRT.3 | 0000002 | 0000002 | UBR.1 | 0000004 | 0000004 | UBR.2 | 0000004 | 0000004 | ABR | 0000003 | 0000003 | CBR.2 | 0000001 | 0000001 | CBR.
Chapter 7 Switch Operating Procedures Managing Service Class Templates Table 7-27 Service Class Template: SCT VC Threshold Parameters (continued) Label Range and Units Description EFCI 0 to 1000000 Explicit Forward Congestion Indication. The VC EFCI discard threshold. This value is a percentage of MAX_CELL THRESH. 1000000 is equal to 100%. CLP_HI 0 to 1000000 Cells Loss Priority - High. The high hysteresis threshold at which CLP (1) cells will be discarded.
Chapter 7 Switch Operating Procedures Managing Service Class Templates Table 7-28 Class of Service (CoS) Scaling Table Index Scaling Class Table #1 (CBR) Scaling Class Table #2 (VBR) Scaling Class Table #3 (ABR) Scaling Class Table #4 (UBR) 0 100.00% 100.00% 100.00% 100.00% 1 100.00% 100.00% 100.00% 100.00% 2 100.00% 100.00% 100.00% 100.00% 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.
Chapter 7 Switch Operating Procedures Managing Service Class Templates Table 7-29 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) 14 6.00% 1.30% 0.75% 1.00% 15 0.50% 0.50% 0.50% 0.50% Port SCT COSB Threshold Parameters (cosThr) The following report appears when you enter the dspportsct cosThr command: pop20two.10.AXSM.
Chapter 7 Switch Operating Procedures Managing Service Class Templates Table 7-30 Service Class Template: SCT COSB Threshold Parameters (continued) Label Range and Units Description CLP_HI 0 to 1000000 Cells Loss Priority High. The maximum number of cells that can be queued in the buffer. CLP(1) cells that exceed this threshold are discarded. This threshold is a percentage of the MAX_CELL THRESH for the connection. 1000000 is equal to 100%. EPD0 0 to 1000000 Early Packet Discard 0.
Chapter 7 Switch Operating Procedures Managing Service Class Templates Table 7-31 Options for dspcdsct Command Option Description bw Displays bandwidth and policing parameters. gen Displays general SCT parameters. cosb Displays COSB parameters. vcThr Displays virtual circuit threshold parameters. cosThr Displays COSB threshold parameters. The following sections display the reports for each of the dspcdsct command options.
Chapter 7 Switch Operating Procedures Managing Service Class Templates Card SCT General SCT Parameters (dspcdsct gen) The following report appears when you enter the dspcdsct gen command: pop20two.10.AXSM.
Chapter 7 Switch Operating Procedures Managing Service Class Templates Card SCT Virtual Circuit Threshold Parameters (dspcdsct vcThr) The following report appears when you enter the dspcdsct vcThr command: pop20two.10.AXSM.
Chapter 7 Switch Operating Procedures Managing Service Class Templates Applying a New Version of an SCT to a Card or Port The major version number of an SCT file changes when a new parameter is added to an SCT, or when an existing parameter in deleted from an SCT. Only Cisco can warrant a major version change to an SCT file. Major version changes are posted in Release Notes for Cisco MGX 8850 and MGX 8830 Software Version 3 (PXM45/B and PXM1E).
Chapter 7 Switch Operating Procedures Viewing an ATM Port Configuration Table 7-32 cnfsct Command Parameters Option Description card type Identifies the type of card the SCT runs on. The possible card types are as follows: 1: AXSM 2: AXSME 3: PXM (for PXM1E only) 4: HSFR. Step 3 type Determines whether the SCT is a port SCT or a card SCT. SCT d Number between 1 and 65335 which identifies an SCT. major ver Major version number of a file.
Chapter 7 Switch Operating Procedures Managing Partitions Step 3 To display the port configuration, enter the following command: mgx8850a.10.AXSM.a > dspport Replace ifNum with the number assigned to the port during configuration. The following example shows the report for this command: mgx8850a.10.AXSM.a > dspport 2 Interface Number : Line Number : Admin State : Guaranteed bandwidth(cells/sec): Maximum bandwidth(cells/sec) : ifType : SCT Id : VPI number(VNNI only) : 2 2.
Chapter 7 Switch Operating Procedures Managing Partitions 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. pop20one.10.AXSM.a > dsppart 1 1 Interface Number : Partition Id : Controller Id : egr Guaranteed bw(.0001percent): egr Maximum bw(.0001percent) : ing Guaranteed bw(.0001percent): ing Maximum bw(.
Chapter 7 Switch Operating Procedures Managing Partitions | VBR-nRT | Avl Bw | 1410377 | 1410377 | | UBR | Avl Bw | 1410377 | 1410377 | | ABR | Avl Bw | 1410377 | 1410377 | +--------------------------------------------+ M8850_NY.1.AXSM.a > Note If necessary, use the dspparts command to see existing partition numbers. Changing a Resource Partition Configuration To change the configuration of a resource partition, use the following procedure.
Chapter 7 Switch Operating Procedures Managing Partitions Table 7-33 Parameters for the cnfpart Command (continued) Parameter Description ingminbw Ingress minimum bandwidth. Enter the minimum percentage of the incoming port bandwidth that you want assigned to the controller. One percent is equal to 0.00001 units. For example, an of 500000 = 50%. The sum of the minimum ingress bandwidth settings for PNNI and MPLS must be 100% or less, and must be less than the sum of the ingmaxbw settings.
Chapter 7 Switch Operating Procedures Managing Partitions Note Step 5 The current software release does not support dynamic changes to partitions. To begin using changes to a resource partition, you need to delete the controller and then add the controller as described in the rest of this procedure. Display the available controllers with the dspcontrollers command, and write down the controller settings for the controller you are about to delete. For example: pop20two.7.PXM.
Chapter 7 Switch Operating Procedures Managing Partitions To add an MPLS partition on port which has a minimum VCI value of 32, perform one of the following options: • Add the MPLS controller, and then add the TDP sig vc using a VPI/VCI pair within its partition’s range. • Enter the dnport and cnfpart commands to change the minimum VCI to 35 for all partitions on the port.
Chapter 7 Switch Operating Procedures Removing Static ATM Addresses Removing Static ATM Addresses If you create a static ATM address and later want to remove that address, use the following procedure to delete it. Step 1 Establish a configuration session using a user name with GROUP1 privileges or higher. Step 2 To locate the port for which you want to delete an address, enter the dsppnports command. Step 3 Use the following command to delete the static address: popeye2.7.PXM.
Chapter 7 Switch Operating Procedures Configuring VPI and VCI Ranges for SVCs and SPVCs The Cisco MGX 8850 and Cisco MGX 8950 switches allow you to define the minimum and maximum values for the following connections: • SVCC VPIs • SVCC VCIs • SPVC VPIs To configure VPI and VCI usage for connections on a specific port, use the following procedure. Step 1 Establish a configuration session using a user name with GROUP1 privileges or higher.
Chapter 7 Switch Operating Procedures Managing Priority Routing Table 7-35 Parameters for the cnfpnportrange Command (continued) Parameter Description min-svpc-vpi Minimum VPI value for SVPC. Range: 1 to 4095. Default = 1. max-svpc-vpi Maximum VPI value for SVPC. Range: 1 to 4095. Default = 4095. Step 5 Enter the uppnport command to bring up the PNNI port you just configured. pop20two.8.PXM.a > dsppnportrange Replace using the formate slot:bay.line:ifNum.
Chapter 7 Switch Operating Procedures Managing Priority Routing Bandwidth for a priority is divided into three parts: Note • The lowest range: you determine the lowest range by specifying the highest rate within the range. For example, if you type 3000, the lowest range is 0–3000 cps. • The highest range: the highest range is what is left over after you specify the lowest range, the number of bandwidth groups, and the number of cells per second in each bandwidth increment.
Chapter 7 Switch Operating Procedures Configuring Priority Routing on a Connection Table 7-36 cnfpri-routing Command Options (continued) Parameter Description -pribuf The priority buffer is a time counter. It counts down to the moment when PNNI prioritizes all buffered connections for routing. A connection is buffered due to an event that causes PNNI to re-route the connection. The routing events are as follows: • An interface with a master endpoint comes up.
Chapter 7 Switch Operating Procedures Tracing Established Connections Modifying SPVC Priority Routing Configuration Enter the cnfcon command and use the -rtngprio option to change an SPVC’s routing priority, as shown in the following example: pop20one.10.AXSM.a > cnfcon 3 101 101 -rtngprio 6 Tracing Established Connections Release 3 of the MGX switches supports a path and connection trace feature which allows you to view details about established connections and their paths on your network.
Chapter 7 Switch Operating Procedures Tracing Established Connections Table 7-37 pathtraceport Command Options Command Description portid Identifies a PNNI physical port, in the format slot:subslot.port:subport. enable or disable Enables (disables) path trace at port level. -H Specifies the hierarchy option. If enabled, information from all the DTLs in the hierarchy are added in the TTL IE. Default: off -CB Specifies the crankback option.
Chapter 7 Switch Operating Procedures Tracing Established Connections Table 7-38 conntrace Command Options Command Description portid Identifies a PNNI physical port, in the format slot:subslot.port:subport. callRef Provides a call reference by itself to trace the connection. A call reference by itself identifies Range for callRef: 1-16777215 endptRef If you provide a call reference, you can also provide an endpoint reference for a point-to-multipoint (P2MP) call.
Chapter 7 Switch Operating Procedures Tracing Established Connections Clear the Connection Trace Buffer Use the following procedure to clear a specific connection trace: Step 1 Enter the dspconntracebuffers command at the active PXM45 to view all path traces in the path trace buffer, as shown in the following example: M8850_SF.7.PXM.a > dspconntracebuffers Step 2 Enter the clrconntracebuffer command to clear the specific connection trace.
Chapter 7 Switch Operating Procedures Managing Load Sharing To clear all connection traces in the path trace buffer, enter the clrpathtracebuffers command at the active PXM45, as shown in the following example. M8850_SF.7.PXM.a > clrpathtracebuffers Clearing a Call at the Destination Node When a call setup message reaches its destination, you can ensure that the call is cleared by entering the pathtraceport command as follows: pop20two.7.PXM.
Chapter 7 Switch Operating Procedures Managing Load Sharing Changing Load Sharing Options To change the load sharing options, enter the cnfxbarmgmt command as described in the following procedure. Step 1 Establish a configuration session using a user name with SUPER_GP privileges or higher. Step 2 Display the current configuration setting by entering the dspxbarmgmt command. Step 3 Set the load sharing options by entering the cnfxbarmgmt command as follows: pop20two.7.PXM.
Chapter 7 Switch Operating Procedures Starting and Managing Telnet Sessions to Other Switches Starting and Managing Telnet Sessions to Other Switches The Cisco MGX 8850 and Cisco MGX 8950 switches support Telnet sessions between switches. For example, you can start a CLI session with one switch, Telnet to a second switch to view configuration information, then switch back to the first switch and continue that CLI session.
Chapter 7 Switch Operating Procedures Verifying PXM45 Disk Data Returning to the Original CLI Session After you Telnet from switch to switch, enter the escape character to close all Telnet sessions and return to the original CLI session. The default escape sequence is Escape, Q (uppercase Q). Press the Escape key first, then press Shift-Q. If you specified an alternate escape character when opening Telnet sessions, enter that character in place of Q.
Chapter 7 Switch Operating Procedures Verifying PXM45 Disk Data Table 7-41 verifydiskdb Command options Parameter Description slot Slot number of the card on which you want to run the disk verification task. level Level on verification for the current task. The levels of verification are as follows: 1 = control information 2 = actual data Default = 2 pass Number of times the verification utility will pass through the disk if a discrepancy is found.
Chapter 7 Switch Operating Procedures Verifying PXM45 Disk Data Table 7-42 describes the information displayed by the verifydiskdb Status status command. Table 7-42 verifydiskdb status Command Display Note Parameter Description Slot Current slot whose databases on active and standby PXM hard drives are being compared. Databases: Number of databases detected for the current slot. Tables Total number of tables detected for all databases for the slot.
Chapter 7 Switch Operating Procedures Verifying PXM45 Disk Data If no discrepancies are found on a card, the log file contains only the slot number, timestamp of the verification task, and a message stating that no discrepancies were found, as shown in the following example: ------------------ Information for Slot 5 -----------------Start: 22/05/2002-10:31:19 End: 22/05/2002-10:31:27 Verify DONE TotalofDbs= 2, TotalofTbls= 15, #DbVerf=2, #TblVerf= 15 No Discrepancies found for slot 5 --------------------
Chapter 7 Switch Operating Procedures Verifying PXM45 Disk Data If a firmware upgrade had not finished (the commitrev command had not yet been used on the slot), the display indicates that the verification utility has skipped that slot because a REV_CHG is in progress, as shown in the following example: ------------------ Information for Slot 6 -----------------Start: 20/04/2002-17:44:14 End: 20/04/2002-17:44:14 Verify SKIPPED - REV_CHG TotalofDbs= 0, TotalofTbls= 0, #DbVerf=0, #TblVerf= 0 No Discrepanci
Chapter 7 Switch Operating Procedures Managing Line Loopbacks tblInd: 5 - tblName: mib29 Record: 1791 ActvComdID: 0 StdbyComID: 7 ============================================================= dbInd: 1 - dbName: sm_mib_v21 tblInd: 5 - tblName: mib29 Record: 1792 ActvComdID: 0 StdbyComID: 7 ============================================================= Note The disk verification utility only logs discrepancies. It does not synchronize the differences.
Chapter 7 Switch Operating Procedures Managing Line Loopbacks Table 7-43 addlnloop Command options Parameter Description -line type Specifies the type of line on which to perform the loopback test will. For an AXSM card, the possible line types are: • -ds3 • -sonet For an AXSME card, the possible line types are: • -ds3 • -e3 • -sonet • -ds1 • -e1 For an AXSME-32 card, the only possible line types is -ds1. For AXSM cards, the keyword ds3 applies to both T3 and E3 line types. Note bay.
Chapter 7 Switch Operating Procedures Configuring a line loopback Enter the dsplns command to verify that the appropriate line is in the specified loopback state. Replace with the appropriate line type. Replace with the appropriate bay and line number. M8850_NY.1.AXSM.a > dspln -sonet 1.1 Line Number : 1.
Chapter 7 Switch Operating Procedures Configuring a line loopback Configuring Loopback Line Tests on AXSME Cards Once the physical connection is established, you need to use the CLI to put the connection into loopback mode. The following types of loopback are supported on the AXSME: • Far-end line loopback - Loopback appears at the far-end of the CPE when you send a loopback activation code from the AXSME. The CPE enters a loop mode in which it returns the received data back to the AXSME.
Chapter 7 Switch Operating Procedures Configuring a line loopback Table 7-44 addlnloop Command Parameters Parameter Description bay.line Identifies the bay (1 or 2) and the number of the line. The line number can be 1 to the highest numbered line on the back card. -lpb Specifies the loopback type for the line type. The entry for no loopback (1) removes any existing loopback.
Chapter 7 Switch Operating Procedures Configuring a line loopback Once your physical line is connected, you can perform a loopback test using the following procedure. Step 1 Connect a single line to the appropriate transfer and receive ports on the backcard you want to test. Step 2 Establish a configuration session with the active AXSM card using a user name with SERVICE_GP privileges or higher. Step 3 Enter the dsplns command to display the configuration for all lines on the current card.
Chapter 7 Switch Operating Procedures Configuring a Bit Error Rate Test on an AXSM Configuring a Bit Error Rate Test on an AXSM BERT commands can help you analyze and resolve problems on a physical interface. To conduct a BERT on a line, a user sends a specified pattern over a line that is configured in loopback mode at the far end. The local end receives the loopback pattern, and the user compares the local end pattern to the original pattern sent from the far end.
Chapter 7 Switch Operating Procedures Configuring a Bit Error Rate Test on an AXSM Table 7-46 cnfbert Command Parameters Parameter Description -ln Replace with the number “1” to indicate the upper bay, or “2” to indicate the lower bay. Replace with the number of the line you are testing as follows: -tp • For OC12, enter the number “1.” • For OC3, enter a number from “1” through “4.” • For T1, enter the number “1.” • For T3and E3, enter a number from “1” through “8.
Chapter 7 Switch Operating Procedures Diagnostics Support MGX 8850 and MGX 8950 Switches Note The dspbert command can be issued even while the BERT is in operation. In the following example, the user displays the BERT results for line 11 on an AXSME card located in the upper bay. Unknown.11.AXSME.a > dspbert 1.
Chapter 7 Switch Operating Procedures Diagnostics Support MGX 8850 and MGX 8950 Switches The MGX 8850 and MGX 8950 switch support both online and offline diagnostics. • Note • Note Online diagnostics tests run in the background while a card is in an operational state. These tests are non-intrusive and run with minimal overhead. Online diagnostics can be used to detect hardware errors diagnosis. Its goal is to monitor any potential errors at a card level while a card is in normal operation.
Chapter 7 Switch Operating Procedures Diagnostics Support MGX 8850 and MGX 8950 Switches Table 7-47 cnfdiag command Parameters Parameter Description slot Enter the slot of the card for which to configure the diagnostics. For the AXSME, the slot number will be 7 or 8. onEnb Enter enable to enable online diagnostic on the card. Enter disable to disable offline diagnostics. offEnb Enter enable to enable offline diagnostics.
Chapter 7 Switch Operating Procedures Diagnostics Support MGX 8850 and MGX 8950 Switches Example 7-3 Configuring both online and offline diagnostics at the same time In the following example, the user enables both online and offline diagnostics for the AXSME in slot 8. A medium offline diagnostics coverage test is scheduled to run every Monday and Friday at 21:30 (8:30 PM). 8850_NY.7.
Chapter 7 Switch Operating Procedures Diagnostics Support MGX 8850 and MGX 8950 Switches Example 7-6 Configuring both online and offline diagnostics at the same time In the following example, the user enables both online and offline diagnostics for all cards in the switch. A medium offline diagnostics coverage test is scheduled to run every Monday and Friday at 21:30 (8:30 PM).
Chapter 7 Switch Operating Procedures Diagnostics Support MGX 8850 and MGX 8950 Switches 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.a > dspdiagerr online Slot Date Time Message ---- ------- ------1 --2 --3 --4 --5 --6 --7 --8 --9 --10 --11 --12 --13 --14 --15 --16 --17 --18 --19 --20 --Type to continue, Q to stop: 21 -- -- Displaying offline diagnostic errors .
Chapter 7 Switch Operating Procedures Diagnostics Support MGX 8850 and MGX 8950 Switches 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 7 Switch Operating Procedures Diagnostics Support MGX 8850 and MGX 8950 Switches Cisco MGX 8850 (PXM45) and MGX 8950 Software Configuration Guide 7-100 Release 3, Part Number 78-14788-01 Rev.
C H A P T E R 8 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: • Add cards • Replace cards • Upgrade cards • Decommission an AXSM slot • Decommission an RPM slot AXSM and RPM slots must be decommissioned when you want to change the type of card that runs in the slot.
Chapter 8 Switch Maintenance Procedures Adding Cards When adding a standby PXM45 card to your switch, you need to physically install the PXM45 card and the back cards in the following order: 1. PXM Hard Drive card (PXM-HD) 2. PXM45-UI-S3 card 3. PXM45 front card After the new standby PXM45 front and back cards are installed, the active PXM45 card will initialize the standby card set. The initialization procedure takes some time.
Chapter 8 Switch Maintenance Procedures Adding Cards Note Step 4 After installation, each card should be initialized with the setrev command only once. For instructions on upgrading the software on a card, refer to Appendix A, “Downloading and Installing Software Upgrades.” 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 AXSM card, and the card resets.
Chapter 8 Switch Maintenance Procedures Replacing Cards with the Same Card Type Adding RPM Cards When you add an RPM card to a switch, you are adding new front and back cards to a slot that is not configured for an RPM card. The following procedure describes how to add RPM cards to unconfigured slots. Note If the slot has been configured previously for an RPM card, you can either replace that card with a card of the same type or you can decommission the slot.
Chapter 8 Switch Maintenance Procedures Replacing Cards with the Same Card Type Replacing PXM45 and PXM45/B Cards PXM45 front and back cards can be replaced when the switch is operating. If a PXM45 is operating in standalone mode, all calls are interrupted until the PXM45 is replaced and 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 8 Switch Maintenance Procedures Replacing Cards with the Same Card Type Table 8-1 Automatic Response to Nativity Checks in Standalone Installations Event Nativity Check Results Response PXM45 front card and hard disk card Both PXM45 cards are configured with No action is required. have not changed. the correct chassis serial number. PXM45 front card is replaced with an PXM45 front card is not configured and The switch builds the PXM45 front card unconfigured card.
Chapter 8 Switch Maintenance Procedures Replacing Cards with the Same Card Type When the entire switch is reset, the nativity check is used to determine which card set gains mastership. The card set that gains mastership will attempt to go active and will resolve nativity conflicts as described in Table 8-1. Table 8-2 shows how the nativity check is used to assign mastership to a PXM45 card set.
Chapter 8 Switch Maintenance Procedures Replacing Cards with the Same Card Type To rebuild the configuration from a configured hard disk in the switch, do the following tasks: • Clear the configuration (clrallcnf) on the PXM45 front card. Usea PXM45 hard disk card on which the configuration can be erased. (Do not use the PXM45 hard disk that hosts the configuration you want to use.
Chapter 8 Switch Maintenance Procedures Upgrading Cards To replace an RPM card that is configured for redundancy, first switch control to the standby card, then replace the card while it is operating in standby mode. If the card you are replacing has failed, there is no reason to switch cards, as the failure should have triggered a switch to the standby card.
Chapter 8 Switch Maintenance Procedures Decommissioning an AXSM Slot The configuration for AXSM cards is stored on the PXM45. The switch will automatically configure a replacement AXSM/B card and start it up. If the card is a standalone card, the card will start up as an active card. If the card is part of a redundant pair, the card will start up in standby mode.
Chapter 8 Switch Maintenance Procedures Decommissioning an AXSM Slot The following is a sample dspcons display. pop20one.7.PXM.a > dspcons Local Port Vpi.Vci Remote Port Vpi.Vci State Owner ----------------------------+-----------------------------+-------+-----10:2.2:2 100 100 Routed 100 100 FAIL MASTER Local Addr: 47.00918100000000107b65f33c.0000010a1802.00 Remote Addr: 47.009181000000002a123f213f.000001011802.00\\ Step 4 Write down the interface, VPI, and VCI numbers for each connection.
Chapter 8 Switch Maintenance Procedures Decommissioning an RPM Slot Decommissioning an RPM Slot To decommission an RPM slot, you must remove all configuration items you configured for that card. You can do this by entering each command in the startup-config file with the key word no in front of it. These configuration items are described in the Cisco MGX 8850 Route Processor Module Installation and Configuration Guide.
C H A P T E R 9 2 Viewing and Responding to Alarms Cisco MGX 8850 and Cisco MGX 8950 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 The PXM45, AXSM, and RPM cards have LEDs for viewing alarm status and switches for responding to alarms.
Chapter 9 Viewing and Responding to Alarms Viewing and Responding to Alarms Using Physical Switch Controls Figure 9-1 PXM45 Front Card Controls Controller port CNTLR Port Critical alarm (blue) Major alarm (red) Minor alarm (yellow) DC power A (green) DC power B (green) Alarm cut-off (yellow) History (green) Ethernet LAN control port (green) CR MJ MN DC-A DC-B ACO HIST ENET Alarm cut-off History Green = active Red = major alarm Yellow = minor alarm ACO HIST PXM45/B System status 38656 SYSTEM
Chapter 9 Viewing and Responding to Alarms Viewing and Responding to Alarms Using Physical Switch Controls Table 9-1 LED Indicators for PXM45 (continued) LED Label Color Meaning System Status Green Blinking green indicates that the card is in the active state. Yellow Slow blinking yellow indicates that the card is in the standby state. Fast blinking yellow indicates that the card is in the boot state.
Chapter 9 Viewing and Responding to Alarms Viewing and Responding to Alarms Using Physical Switch Controls AXSM Card Controls Figure 9-2 shows the LEDs available on the front of the AXSM card. Table 9-2 describes these LEDs.
Chapter 9 Viewing and Responding to Alarms Viewing and Responding to Alarms Using Physical Switch Controls Table 9-2 LED Indicators for AXSM Card LED Color Description Active Green Card is active. Standby Yellow Card is in standby mode. Fail Red Failure detected on card. PORT Green Line is active; there are no alarms. Red Line is active, but a local alarm has been detected. Yellow Line is active; a remote alarm has been detected.
Chapter 9 Viewing and Responding to Alarms Displaying Alarm Reports in the CLI Table 9-3 LED Indicators for RPM-PR Card LED Color Description CPU OK Green RPM-PR has successfully loaded the boot or runtime software. Yellow ROMMON passed the Power On Self-Test (POST). Red POST failure. Off No power or ROMMON cannot execute POST. On Transmitting cells on cellbus. Off Not transmitting cells on cellbus. On Receiving cells from cellbus. This light stays on solid when downloading software.
Chapter 9 Viewing and Responding to Alarms Displaying Alarm Reports in the CLI The following is an example of the node alarm report. M8850_LA.7.PXM.a > dspndalms Node Alarm Summary Alarm Type ---------Clock Alarms Switching Alarms Environment Alarms Card Alarms Critical -------0 0 0 1 Major ------0 0 0 4 Minor ------0 3 0 0 Typically, you would start investigating alarms by displaying the node alarms.
Chapter 9 Viewing and Responding to Alarms Displaying Alarm Reports in the CLI To display a report for xbar alarms, enter the following command: M8850_NY.7.PXM.a > dspxbaralm The following display is an example xbar alarm report. M8850_NY.7.PXM.a > dspxbaralm M8850_NY System Rev: 02.01 MGX8850 Slot Plane Severity --------------7 0 None 7 1 None 7 2 None 8 0 None 8 1 None 8 2 None Sep.
Chapter 9 Viewing and Responding to Alarms Displaying Alarm Reports in the CLI Table 9-4 Crossbar Alarm Troubleshooting Commands (continued) Command Purpose dspxbarerrcnt Displays the following types of slot-link errors: dspxbarerrthresh • Loss of synchronization between the ASIC and the queuing circuitry on the service module. The synchronization in this case applies to the timing of the internal switching frames (Sframes). Loss of synchronization is a very serious error.
Chapter 9 Viewing and Responding to Alarms Displaying Alarm Reports in the CLI Displaying Environment Alarms An environmental alarm report displays the alarm status and operating statistics for the switch power supplies and cooling fans. To display the environmental alarm report, enter the dspenvalms command as shown in the following example: pop20two.7.PXM.a > dspenvalms pop20two System Rev: 02.00 Sep.
Chapter 9 Viewing and Responding to Alarms Displaying Alarm Reports in the CLI Displaying Card Alarms A card alarm report can display the alarm status of all the cards within the node or the alarm status of a single card. To display card alarms, enter the following command: pop20two.7.PXM.a > dspcdalms [slot] Replace [slot] with the number of the card for which you want to display alarms.
Chapter 9 Viewing and Responding to Alarms Displaying Log File Information Table 9-5 Card Alarm Information Commands Alarm Type Commands Card state dspcd Channel or Connection dspconalarms dspcons dspcon Feeder dspfdrs dspfdr Line dspalms dsplns dspln dspapslns dspapsln Port dspports dsppnports 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: pop20two.7.PXM.
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 and MGX 8830 Software Version 3 (PXM45/B and PXM1E) or the Release Notes for Cisco MGX 8950 Software Version 3 for the latest information. Each type of switch card runs boot and runtime software. The recommended sequence for upgrading the software on switch cards is as follows: Note 1.
Appendix A Downloading and Installing Software Upgrades Quickstart Procedures for Software Upgrades Graceful PXM45 Boot Upgrades When performed properly, graceful upgrades have minimal impact on connections in progress and do not interrupt any established connections. When a boot software upgrade is required, the procedure for upgrading redundant PXM45 cards is as follows: 1. Manually upgrade the boot software on the standby PXM45. 2. Switch cards to make the upgraded standby card active. 3.
Appendix A Downloading and Installing Software Upgrades Quickstart Procedures for Software Upgrades Step 7 Command Purpose username Establish a CLI session with the active PXM45 card (which is the non-upgraded card) using the CP port on the UI-S3 back card and a user name with CISCO_GP privileges. password Step 8 switchcc y Step 9 Switch the roles of the active and standby cards so you can upgrade the non-upgraded card in standby mode. sh Change to the PXM45 backup boot mode.
Appendix A Downloading and Installing Software Upgrades Quickstart Procedures for Software Upgrades Step 3 Command Purpose saveallcnf This optional step saves the current configuration to the hard disk. See the “Saving a Configuration” section in Chapter 7, “Switch Operating Procedures.” Step 4 sh Change to the PXM45 Backup Boot mode. sysBackupBoot Note that the software versions 2.0.11 and earlier require you to press Return during the reboot sequence to enter backup boot mode. (2.0.
Appendix A Downloading and Installing Software Upgrades Quickstart Procedures for Software Upgrades Note Cisco Systems recommends that you upgrade software on one AXSM or FRSM-12 card at a time within a switch. Wait until each AXSM or FRSM-12 card upgrade is complete before starting an upgrade on another AXSM or FRSM-12 card. To upgrade the runtime software, use the following procedure. Step 1 Command Purpose ftp Copy the boot and runtime files you want to use to the switch.
Appendix A Downloading and Installing Software Upgrades Quickstart Procedures for Software Upgrades Step 7 Command Purpose runrev Switch over to the standby PXM45 card and load the new runtime software on the new standby (non-upgraded) PXM45. dspcd dspcd Step 8 commitrev This command prevents an accidental switch back to a previous software revision if someone enters the abortrev command.
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.
Appendix A Downloading and Installing Software Upgrades Quickstart Procedures for Software Upgrades Note If you plan to upgrade PXM45 cards and AXSM or FRSM-12 cards, upgrade the PXM45 cards first. Wait until the PXM45/B cards are operating in active and standby modes with the correct software before upgrading AXSM or FRSM-12 cards. The software version used by the PXM45/B cards should be equal to or later than the version used on the AXSM, AXSM/B, AXSM-E, AXSM-32-E, and FRSM-12 cards.
Appendix A Downloading and Installing Software Upgrades Quickstart Procedures for Software Upgrades Note Step 1 Cisco Systems recommends that you upgrade software on one AXSM or FRSM-12 card at a time within a switch. Wait until each AXSM or FRSM-12 card upgrade is complete before starting an upgrade on another AXSM or FRSM-12 card. Command Purpose ftp Copy the boot and runtime files you want to use to the switch.
Appendix A Downloading and Installing Software Upgrades Quickstart Procedures for Software Upgrades Command Purpose Step 3 cc Select the slot in which the primary RPM-PR card is installed. Step 4 enable Enter Enable mode for the router. password Step 5 dir e: Verify router access to the PXM45 hard disk and the boot upgrade software. Step 6 show flash: Display current contents of bootflash. Step 7 copy filename bootflash: Copy the upgrade boot software to flash.
Appendix A Downloading and Installing Software Upgrades Quickstart Procedures for Software Upgrades Step 12 Command Purpose enable password dir e: 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 (E:RPM). See the “Copying Software Files to the Switch” section, which appears later in this appendix. Step 2 copy This step is optional. Copy and rename the runtime file to a generic name for easy updates. See the “Non-Graceful RPM-PR Runtime Software Upgrades” section, which appears later in this chapter.
Appendix A Downloading and Installing Software Upgrades Quickstart Procedures for Software Upgrades Command Purpose Step 15 softswitch 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 c: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 (E:RPM). See the “Copying Software Files to the Switch” section, which appears 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-PR Runtime Software Upgrades” section, which appears later in this chapter.
Appendix A Downloading and Installing Software Upgrades Quickstart Procedures for Software Downgrades Installing SCT Files Use the procedure in this section when you need to manually install or upgrade SCT files. If you are using CWM to install or upgrade SCT files in your network, refer to the Cisco WAN Manager User’s Guide, Release 11 Note Step 1 The following quickstart procedure is provided as an overview and as a quick reference for those who have already performed SCT upgrades on the switch.
Appendix A Downloading and Installing Software Upgrades Quickstart Procedures for Software Downgrades PXM45 and AXSM Boot Downgrades When redundant cards are used and the downgrade software is compatible with the existing runtime software, boot software downgrades can be graceful. To perform a graceful downgrade of boot software, follow the instructions for the appropriate graceful software upgrade: Caution • Graceful PXM45 Boot Upgrades • Graceful AXSM or FRSM-12 Boot Upgrades Cisco Systems, Inc.
Appendix A Downloading and Installing Software Upgrades Browsing the File System Step 4 Step 5 Command Purpose clrallcnf Clear the current configuration. y See “Clearing a Configuration” in Chapter 7, “Switch Operating Procedures.” sysVersionSet “version” Select the runtime firmware version the switch will use on the PXM45 card and restart the switch with that firmware. For example: reboot sysVersionSet "002.001.000.
Appendix A Downloading and Installing Software Upgrades Locating Software Updates Table A-1 File System Commands at Switch Prompt Command Description cd Change directories. Access level required: ANYUSER or above. copy Copies a file from one location to another. Syntax: copy Access level required: GROUP1 or above. del Deletes a file. Syntax: del Access level required: GROUP1 or above.
Appendix A Downloading and Installing Software Upgrades Copying Software Files to the Switch Copying Software Files to the Switch This section describes how to copy software files to an MGX 8850 or MGX 8950 switch. The switch cards use boot software and runtime software. Each PXM45, AXSM, and FRSM-12 card uses the boot software to define communications between the card components and to enable cards to start up. The runtime software defines how the card operates after startup.
Appendix A Downloading and Installing Software Upgrades Upgrade Procedures for PXM45, AXSM, and FRSM-12 Cards Step 5 To verify that the new RPM-PR files have been transferred to the switch, log into the switch and display the contents of the E:/RPM directory. For more information on browsing the switch file system, see the “Installing SCT Files” section, which appears earlier in this appendix.
Appendix A Downloading and Installing Software Upgrades Upgrade Procedures for PXM45, AXSM, and FRSM-12 Cards 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.01 MGX8850 Slot Number 7 Redundant Slot: 8 Front Card ---------- Upper Card ---------- Inserted Card: PXM45 Reserved Card: PXM45 State: Active Serial Number: SBK050302AF Prim SW Rev: 2.1(0) Sec SW Rev: 2.1(0) Cur SW Rev: 2.1(0) Boot FW Rev: 3.0(0.
Appendix A Downloading and Installing Software Upgrades Upgrade Procedures for PXM45, AXSM, and FRSM-12 Cards 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 PXM45, AXSM, and FRSM-12 Cards For non-graceful upgrades, the load process defines the software version to which the switch is about to be upgraded. Table A-3 shows how the revision levels change during a non-graceful upgrade. Table A-3 Software Versions Reported During Non-Graceful Upgrades Software Revision Before Upgrade After loadrev After runrev After commitrev Primary 2.1(0) 2.1(0) 3.0(0.0) 3.0(0.
Appendix A Downloading and Installing Software Upgrades Upgrade Procedures for PXM45, AXSM, and FRSM-12 Cards Starting the Upgrade Software After you load the runtime upgrade software for a PXM45, AXSM, or FRSM-12 card, enter the runrev command to start using the software. The version levels for graceful and non-graceful upgrades change as shown earlier in Table A-2 and Table A-3. The following procedure describes how to start the upgrade software.
Appendix A Downloading and Installing Software Upgrades Upgrade Procedures for PXM45, AXSM, and FRSM-12 Cards Replace with the slot number of a standalone AXSM/FRSM-12 card, or an AXSM/FRSM-12 card operating in standby mode. Replace with the software revision number to which you are upgrading. For example: pop20one.7.PXM.a > burnboot 1 2.1(0) Step 4 When prompted to confirm the upgrade, type y and press Return.
Appendix A Downloading and Installing Software Upgrades Upgrade Procedures for PXM45, AXSM, and FRSM-12 Cards To revert to the previously used runtime software version, use the following procedure. Step 1 Establish a configuration session using a user name with SERVICE_GP privileges or higher. Step 2 To display the software revisions known to the switch, enter the dspcd command. (You can also view the revision levels with the dsprevs command.
Appendix A Downloading and Installing Software Upgrades Upgrade Procedures for RPM-PR Cards Step 3 To commit to the software version, enter the following command: mgx8850a.7.PXM.a > commitrev Replace with the card slot number for the active PXM45, AXSM, or FRSM-12 card, and replace with the software version number for the currently used software version. To display the software version number, use the dspcd command to view the software version in use.
Appendix A Downloading and Installing Software Upgrades Upgrade Procedures for RPM-PR Cards When managing the bootflash, consider the following facts: Caution • If the BOOTLDR variable is set and the RPM-PR card is reset, the RPM-PR card attempts to load the boot software specified. • If the BOOTLDR variable is not set and the RPM-PR card is reset, the RPM-PR card tries to load the first bootable image in bootflash.
Appendix A Downloading and Installing Software Upgrades Upgrade Procedures for RPM-PR Cards Step 5 To verify router access to the PXM45 hard disk and display the boot file name, enter dir e: command. Router#dir e: Directory of c:/ 65539 65540 84611 66805 85809 -rw-rw-rw-rw-rw- 815 2588780 2452768 8529104 7936012 Sep May Apr May Apr 13 22 05 22 05 2001 2001 2001 2001 2001 23:51:10 19:06:54 05:34:44 19:09:00 06:28:54 auto_config_slot09 rpm-boot-mz_002.001.000.000 rpm-boot-mz.122-4.T rpm-js-mz_002.
Appendix A Downloading and Installing Software Upgrades Upgrade Procedures for RPM-PR Cards Step 10 To reorganize the bootflash so that the new boot software is loaded first when the BOOTLDR variable is not set, complete the following steps: a. Because all files that precede the new boot image in bootflash have to be deleted, copy bootflash files you want to save to the PXM45 hard disk using the following command. Router#copy b.
Appendix A Downloading and Installing Software Upgrades Upgrade Procedures for RPM-PR Cards Tip If the bootflash contains bootable images and the sequence is such that the card will not start, you can enter rommon mode and load the bootable image. To get into rommon mode, establish a console connection to the RPM-PR card, reset the RPM-PR card using the resetcd command from the active PXM1E card, then quickly enter the CTRL-[, Break sequence at the RPM-PR console.
Appendix A Downloading and Installing Software Upgrades Upgrade Procedures for RPM-PR Cards Tip To simplify runtime software updates, copy the runtime file in the E:RPM directory and rename it to a generic name such as rpm-js-mz. The production runtime filenames have version numbers appended to them, but you can change this. This approach allows you to perform future upgrades by copying the file to the hard disk, renaming a copy of the file to your generic name, and resetting each card.
Appendix A Downloading and Installing Software Upgrades Upgrade Procedures for RPM-PR Cards Step 7 Display the startup runtime software filename by entering the show bootvar command. Router#show bootvar BOOT variable = c: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 c:rpm-js-mz_122-4.T, and it has a version number attached to it.
Appendix A Downloading and Installing Software Upgrades Upgrade Procedures for RPM-PR Cards Step 14 Switch to the secondary card using the softswitch command as follows: 8850_LA.8.PXM.a > softswitch Replace with the slot number of the primary card. Replace with the slot number of the secondary card. This step makes the secondary card active and resets the primary RPM-PR card. When the Primary card resets, it loads the upgraded software.
Appendix A Downloading and Installing Software Upgrades Upgrade Procedures for RPM-PR Cards Step 6 Configure the RPM-PR card to store its configuration on the PXM45 hard disk by entering the following command: Router> boot config e:auto_config_slot# Step 7 Enter Enable mode for the router. Router>enable Password: Router# Step 8 Display the startup runtime software filename by entering the show bootvar command. Router#show bootvar BOOT variable = c:rpm-js-mz_122-4.
Appendix A Downloading and Installing Software Upgrades Upgrading SCT Files Step 14 Switch to the active PXM45 card and reset the RPM-PR card. For example: Router#cc 8 (session redirected) 8850_LA.8.PXM.a > resetcd 9 The card in slot number 9, will be reset. Please confirm action resetcd: Do you want to proceed (Yes/No)? y Upgrading SCT Files Once you have installed the SCT files on your network, you can use the cnfsct command to overwrite them with new files with the same major version.
Appendix A Downloading and Installing Software Upgrades Troubleshooting Upgrade Problems Step 4 Enter the dspscts command to ensure that the latest SCT version was registered on your network. The status of the SCT would be marked as “failed” if the file does not exist or does not match the major and minor versions. Troubleshooting Upgrade Problems Table A-5 lists the symptoms for upgrade problems and suggestion on how to correct them.
Appendix A Downloading and Installing Software Upgrades Troubleshooting Upgrade Problems Table A-5 Troubleshooting Upgrade Problems (continued) Primary Symptom Secondary Symptom After restart, switch stops at The switch displays the message: Can not open file backup boot prompt: C:/version. pxm45bkup>. (Use a console port connection to see this. If you missed the startup messages, enter the reboot command.) The switch displays the message: Unable to determine size of C:/FW/filename.
Appendix A Downloading and Installing Software Upgrades Troubleshooting Upgrade Problems Table A-5 Troubleshooting Upgrade Problems (continued) Primary Symptom Secondary Symptom Suggested Action After restart, the switch stops at backup shell prompt: 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 command to restart the switch and avoid pressing the Return key.
Appendix A Downloading and Installing Software Upgrades Troubleshooting Upgrade Problems Cisco MGX 8850 (PXM45) and MGX 8950 Software Configuration Guide A-42 Release 3, Part Number 78-14788-01 Rev.
A P P E N D I X B 2 PXM45 Backup Boot Procedures When a PXM45 card starts up, it first loads the boot software on the card. If the PXM45 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: pxm45bkup> Some switch procedures, such as PXM45 card initialization and boot software upgrades, must be performed in backup boot mode.
Appendix B PXM45 Backup Boot Procedures Changing to PXM45 Backup Boot Mode Step 3 At the shell prompt, enter the enter the sysBackupBoot command: pxm45> sysBackupBoot Note This command and all commands that you enter in shell mode are case sensitive. The PXM45 card reboots after you enter this command. Tip If you are accessing the CP port through a terminal server, rebooting the PXM45 may disrupt your connection. Random characters may appear on the display or the display may appear to “hang.
Appendix B PXM45 Backup Boot Procedures Browsing the File System in Backup Boot Mode Browsing the File System in Backup Boot Mode The PXM45 hard disk stores log files, configuration files, and boot and runtime software. The switch operating system supports a set of UNIX-like commands that you can use to locate log files or manage software updates. Many of the commands are the same commands that operate at the switch prompt, however, in backup boot mode you must enclose the file path in quotation marks.
Appendix B PXM45 Backup Boot Procedures Locating Software Updates Table B-1 File System Commands at Backup Boot Prompt (continued) Command Description pwd Display the present working directory. When you first start a session in backup boot mode, the present working directory is a directory on a remote server as specified by the runtime software bootchange command. To change to a directory on the C: drive, enter the cd command. Syntax: pwd Example: pwd rename Renames a file.
Appendix B PXM45 Backup Boot Procedures Clearing the Switch Configuration Step 1 If you are copying software files to the switch, refer to the Release Notes for Cisco MGX 8850 and MGX 8830 Software Version 3 (PXM45/B and PXM1E) or the Release Notes for Cisco MGX 8950 Software Version 3 to locate a server from which you can download the files. Step 2 Using a workstation with FTP client software, establish connections to the server where the files are stored and to the switch.
Appendix B PXM45 Backup Boot Procedures Initializing the PXM45 Hard Disk Step 4 When the stop auto-boot prompt appears, press return to enter backup boot mode. The following example shows the prompt and the message that appears when a newly formatted hard disk is detected. Press Return key to stop auto-boot...2 To avoid reset from the Active card, use sysPxmRemove() Use sysFWLoad() for FW download from active PXM.
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 Cisco MGX 8850 and Cisco MGX 8950 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. Figure C-1 Workstation Connection to the Console Port The terminal you use should emulate a VT-100 terminal. You can use any personal computer or UNIX workstation and a terminal emulation program that emulates the VT-100.
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-2 shows the hardware required for a terminal server connection. Figure C-2 Terminal Server Connection to the Console Port In the terminal server topology, any workstation with access to the terminal server can access the CP port as if the workstation were local.
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 the “Setting the LAN or Disk IP Address” section in Chapter 2, “Configuring General Switch Features.” 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 ATM WAN Connections Note If you omit the sl0 option, the switch displays the configuration for all switch IP interfaces: the ATM interface (atm0), the PXM45 LAN port interface (lnPci0), and the PXM45 maintenance port interface (sl0). Note that the address for each interface must be unique. In the IP Interface Configuration Table, look for an Internet address entry under the sl0 entry. (You may need to press Enter to see this.
Appendix C Supporting and Using Additional CLI Access Options Setting Up ATM WAN Connections Figure C-4 Hardware Required for an ATM WAN Connection ATM router (Cisco or third-party) ATM SVCs Core ATM network 38666 IP over Ethernet LAN ATM SVCs Cisco MGX 8850 IP workstation Cisco MGX 8850 The workstation in Figure C-4 uses a LAN to connect to a router that supports both LAN and ATM interfaces. An IP address is assigned to an ATM interface in each Cisco MGX 8850.
Appendix C Supporting and Using Additional CLI Access Options Setting Up ATM WAN Connections To configure the switch to support IP connectivity to the ATM interface, use the following procedure. Step 1 Establish a CLI management session using a username with SUPER_GP privileges. The default user name and password for this level are superuser, . Step 2 Verify that the IP address for the ATM interface is not already configured by entering the following command: mgx8850a.7.PXM.
Appendix C Supporting and Using Additional CLI Access Options Setting Up ATM WAN Connections Step 6 Configure the switch AESA for IP connectivity by entering the following command: mgx8850a.7.PXM.a> svcifconfig atm0 local Replace ATM_Addr with the AESA for the interface. This address must conform to the address plan for the switch. Step 7 Define the AESA for the ATM router by entering the following command: mgx8850a.7.PXM.
Appendix C Supporting and Using Additional CLI Access Options Setting Up ATM WAN Connections mgx8850a.7.PXM.a> dsppnports (example output) Per-port status summary PortId 10:1.
Appendix C Supporting and Using Additional CLI Access Options Starting a CLI Management Session Using a CP Port or Terminal Server Connection Starting a CLI Management Session Using a CP Port or Terminal Server Connection The process for starting a CLI management session is similar for both CP port and terminal server connections. Both use a serial connection to the switch. The difference is that terminal server connections require that you first select the correct port at the terminal server.
Appendix C Supporting and Using Additional CLI Access Options Starting a CLI Telnet Session Starting a CLI Telnet Session Start a CLI Telnet session when you start a CLI management session using any of the following access methods, all of which require an IP address: • Local LAN connection • Dial-up connection • ATM WAN connection The switch includes a Telnet server process that you can use to connect to and manage the switch.
Appendix C Supporting and Using Additional CLI Access Options 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 end a CLI management session, enter the bye command. Note This command ends the CLI session. It does not terminate the connection to the switch.
A P P E N D I X D Standards Compliance This appendix lists the relevant technical and compliance specifications for the Cisco MGX 8850 Release 3 PXM45 and PXM1E based PNNI controllers, PNNI, and ATM switched virtual circuits 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 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. Annex B M x Soft PVPC and PVCC 9.
Appendix D Standards Compliance ATM Signaling Compliance SONET/SDH The standards and responsible organizations with which MGX 8850 SONET technology complies are as follows: • Bell Communications Research–SONET Transport Systems: Common Generic Criteria, GR-253-CORE, Issue 2, 1995. • ITU Recommendation G.782–Types and General Characteristics of Synchronous Digital Hierarchy (SDH) Equipment, January 1994. • ITU Recommendation G.
GLOSSARY A ABR Available bit rate is a Class of Service defined for ATM connections by the ATM Forum. Devices using ABR are guaranteed no more than a certain rate of throughput. This rate dynamically changes and the current value is relayed to the sending device by way of Resource Management (RM) cells. ACR Available cell rate. AESA ATM End Station Address. The 19-octet address that uniquely identifies each logical node. AINI ATM Inter-Network Interface.
Glossary A component of a Service Class Template which contains Class of Service Buffer configurations Class of Service (CoS) Buffer indexed by CoSB number. Descriptor Template CLI Command Line Interface. Community In the context of SNMP, a relationship between an agent and a set of SNMP managers that defines security characteristics. The community concept is a local one. defined at the agent.
Glossary IISP Interim Inter-switch Protocol. ILMI Integrated Local Management Interface. IOS Cisco Internet Operating System. IP Internet Protocol. L LCN Each interface card in a switch has a certain number of Logical Connection Numbers. A Logical Connection Number is used for each cross connect leg through the card in question. “LCN” is often roughly synonymous with “cross connect leg”. In VSI terminology, and LCN is an example of an Other End Reference. LER Label Edge Router.
Glossary N nrtVBR Non-real-time-variable-bit-rate is intended for non-real-time application that have bursty traffic characteristics, and which are characterized in terms of a PCR, SCR, and MBS. NSAP Network Service Access Point. NIC Network Interface Card. An ATM card for a host or router is an ATM NIC. NNI Network-to-network interface. O Object In the context of SNMP, a data variable that represents some resource or other aspect of a managed device.
Glossary Routing Node In tiered networks terminology, a Routing Node is a larger switch to which one or more Feeders is attached. RPM Route Processor Module. Also refers to the RPM card that is designed for MGX 8230, MGX 8250, and MGX 8850 Release 1 switches. The RPM card is an Ethernet router that can operate as a Label Edge Router or a Label Switch Controller in an MPLS network. RPM-PR Newer version for the RPM card that is designed for MGX 8850 and MGX 8950 switches.
Glossary V VC ATM and Frame Relay traffic is carried in Virtual Channels which are set up between adjacent ATM or Frame Relay switches before data transmission occurs. An ATM link between switches may support up to 228 different VCs, although a small number of VCs is reserved for special purposes. VCC Traffic is carried end-to-end on an ATM network on Virtual Channel Connections, which consist of a sequence of Virtual Channels between switches linked by VC cross-connects at the switches.
INDEX ATM addresses A AESA abortrev command A-28 configuration worksheets access levels changing privileges C-6 1-19 node address configuration 2-17 removing static addresses 2-15 active card state summary addresses 2-6, 2-12 addapsln command ATM edge device 3-19, 3-21 2-21, 2-28 addpnni-node command 6-2 6-5 1-3 See AESA ATM interface addpnni-summary-addr command 6-5 3-6, 4-6, 5-8 configuration example for management access router configuration example address addtrapmgr command add
Index AXSM slot, decommissioning switching PXM45 cards 8-10 AXSM software files types and locations backup boot access card states B-4 7-14 2-45 2-6 caution symbol, defined B C-bit checking back cards cc command 2-45 3-16, 3-17 2-9 cd command backup boot ftp password backup boot B-5 bandwidth overbooking factor bay numbers runtime 6-16 B-3 7-10, A-20 CISCO_GP access privileges 3-12, 3-14 best fit PNNI routing resetting the password configuration overview Cisco View 1-9 boo
Index clrilmicnt command cnfabr command command line interface 7-9 See CLI 7-45 cnfabrtparmdft command commitrev command 7-45 cnfapsln command 7-23 cnfcdsct command 3-10, 4-7 configuration clearing cnfclksrc command PXM45 card 7-3 collecting information ending a session 2-30 cnfcmdabbr command 7-45 overview 1-6 cnfdate command 2-20 restoring 7-3 cnfilmienable command cnfln -ds3 command cnfname command backup boot access 2-19 configuring for MPLS 2-16 cnfpnni-election command c
Index delcon command delcontroller command deleting users dspcdsct bw command 7-67, 8-11 dspcdsct command 7-66 7-47, 7-56 dspcdsct cosb command 2-18 delfdr command 7-57 7-58 dspcdsct cosThr command 7-42 delpart command 7-67, 8-11 dspcdsct gen command delport command 8-11 dspcdsct vcThr command delprfx command 7-9 dspclkalarms command delred command 7-16 deluser command dspclksrcs command Digital Subscriber Line Access Multiplexers See DSLAM dspcons command 9-7 7-39 2-10 7-67,
Index dsppnni-timer command external clock sources 6-23 dsppnportcac command 6-16 changing 7-40 dsppnsysaddr command 6-18, C-8 managing 7-27 dspport command restoring 7-62 dspportsct cosb command dspportsct cosThr command dspportsct gen command Features, MGX 8850 and MGX 8950 dsppswdreset command 2-19 introduction 3-5, 4-5, 7-12, A-25, A-26, A-28, A-29, A-39 dsprevs -status command dspsnmp command 7-13 dspsvcif command filenames, case sensitive dspusers command browsing browsing
Index line numbers H 3-12, 3-14 lines hardware configuration worksheet 2-42 bringing up help configuration listing all backup boot commands listing all commands B-2 2-11 B-2 runtime runtime operation 3-18 ll command backup boot backup boot 1-2 viewing configuration help command 2-11 B-3 7-10, A-20 loadrev command 9-3 history LED 3-15, 3-17, 3-18 density per AXSM 2-11 searching for commands HIST LED 3-12 Load Sharing 9-3 A-25 7-77 log files backup boot access directory I
Index peer group leader N See PGL name PGL configuring the switch name 2-19 network clock sources changing 7-40 AW configuration 2-28 7-40 guidelines background routing table generation configuring port range 7-27 1-8 level configuration restoring 7-41 multipoint routes 7-27, 7-39 1-13 SNMP configuration 2-39 2-22 6-5 node ID configuration 2-25 parallel link selection 6-15 PGL priority configuration address configuration displaying alarms PNNI transit node IP address 2-23 peer
Index PXM45 card resource partitions adding standby cards card types LEDs changing 8-1 deleting 2-45 7-67 displaying configuration 9-1 software downgrades software upgrades switches 7-64 A-17 restoreallcnf command 7-4 restoring, configuration A-2 7-62 7-3 revertive function, BITS clock 9-1 PXM45 software files rommon mode backup boot access A-33 routeAdd command B-4 2-38, C-7 routeDelete command 2-38, C-7 routeNetAdd command Q routeShow command question mark help routing t
Index software S aborting upgrades saveallcnf command 7-2 saving, configuration committing to an upgrade 7-1 backup boot bandwidth and policing parameters 7-48, 7-57 7-50, 7-58 COSB threshold parameters runtime B-4 A-21 determining versions from filenames 7-55, 7-59 create with Cisco WAN Manager directory 3-9 3-8 downloading and installing updates locating updates displaying a port SCT 7-46 managing versions displaying card SCT settings general SCT parameters 7-47, 7-56 7-48, 7-58
Index switchapsln command 7-24 U switching redundant AXSM cards upgrades 7-15 redundant PXM45 cards See software 7-14 switching alarms, displaying upln command 9-7 switch name, setting and viewing switch prompt 2-19 uppnport command 7-9 user access, configuration 2-6, 2-8 7-15 switchredcd command 7-15 sysBackupBoot command sysClrallcnf command adding deleting B-5 sysDiskCfgCreate command A-40, B-6 sysFlashBootBurn command A-22 sysPxmRemove command 2-14 changing access levels B
