Survey
* Your assessment is very important for improving the workof artificial intelligence, which forms the content of this project
* Your assessment is very important for improving the workof artificial intelligence, which forms the content of this project
Cisco SES PNNI Controller Software Configuration Guide Release 1.1 January 2002 Corporate Headquarters Cisco Systems, Inc. 170 West Tasman Drive San Jose, CA 95134-1706 USA http://www.cisco.com Tel: 408 526-4000 800 553-NETS (6387) Fax: 408 526-4100 Customer Order Number: DOC-7813539= Text Part Number: 78-13539-01 Rev. C0 THE SPECIFICATIONS AND INFORMATION REGARDING THE PRODUCTS IN THIS MANUAL ARE SUBJECT TO CHANGE WITHOUT NOTICE. ALL STATEMENTS, INFORMATION, AND RECOMMENDATIONS IN THIS MANUAL ARE BELIEVED TO BE ACCURATE BUT ARE PRESENTED WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED. USERS MUST TAKE FULL RESPONSIBILITY FOR THEIR APPLICATION OF ANY PRODUCTS. THE SOFTWARE LICENSE AND LIMITED WARRANTY FOR THE ACCOMPANYING PRODUCT ARE SET FORTH IN THE INFORMATION PACKET THAT SHIPPED WITH THE PRODUCT AND ARE INCORPORATED HEREIN BY THIS REFERENCE. IF YOU ARE UNABLE TO LOCATE THE SOFTWARE LICENSE OR LIMITED WARRANTY, CONTACT YOUR CISCO REPRESENTATIVE FOR A COPY. The Cisco implementation of TCP header compression is an adaptation of a program developed by the University of California, Berkeley (UCB) as part of UCB’s public domain version of the UNIX operating system. All rights reserved. Copyright © 1981, Regents of the University of California. NOTWITHSTANDING ANY OTHER WARRANTY HEREIN, ALL DOCUMENT FILES AND SOFTWARE OF THESE SUPPLIERS ARE PROVIDED “AS IS” WITH ALL FAULTS. CISCO AND THE ABOVE-NAMED SUPPLIERS DISCLAIM ALL WARRANTIES, EXPRESSED OR IMPLIED, INCLUDING, WITHOUT LIMITATION, THOSE OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OR ARISING FROM A COURSE OF DEALING, USAGE, OR TRADE PRACTICE. IN NO EVENT SHALL CISCO OR ITS SUPPLIERS BE LIABLE FOR ANY INDIRECT, SPECIAL, CONSEQUENTIAL, OR INCIDENTAL DAMAGES, INCLUDING, WITHOUT LIMITATION, LOST PROFITS OR LOSS OR DAMAGE TO DATA ARISING OUT OF THE USE OR INABILITY TO USE THIS MANUAL, EVEN IF CISCO OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. AccessPath, AtmDirector, Browse with Me, CCIP, CCSI, CD-PAC, CiscoLink, the Cisco Powered Network logo, Cisco Systems Networking Academy, the Cisco Systems Networking Academy logo, Fast Step, Follow Me Browsing, FormShare, FrameShare, GigaStack, IGX, Internet Quotient, IP/VC, iQ Breakthrough, iQ Expertise, iQ FastTrack, the iQ Logo, iQ Net Readiness Scorecard, MGX, the Networkers logo, Packet, RateMUX, ScriptBuilder, ScriptShare, SlideCast, SMARTnet, TransPath, Unity, Voice LAN, Wavelength Router, and WebViewer are trademarks of Cisco Systems, Inc.; Changing the Way We Work, Live, Play, and Learn, Discover All That’s Possible, and Empowering the Internet Generation, are service marks of Cisco Systems, Inc.; and Aironet, ASIST, BPX, Catalyst, CCDA, CCDP, CCIE, CCNA, CCNP, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, the Cisco IOS logo, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Enterprise/Solver, EtherChannel, EtherSwitch, FastHub, FastSwitch, IOS, IP/TV, LightStream, MICA, Network Registrar, PIX, Post-Routing, Pre-Routing, Registrar, StrataView Plus, Stratm, SwitchProbe, TeleRouter, and VCO are registered trademarks of Cisco Systems, Inc. and/or its affiliates in the U.S. and certain other countries. All other trademarks mentioned in this document or Web site are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (0108R) Cisco SES PNNI Controller Software Configuration Guide Copyright © 2002, Cisco Systems, Inc. All rights reserved. Cisco Reader Comment Card General Information 1 Years of networking experience: 2 I have these network types: Other: LAN Backbone 3 I have these Cisco products: Other (specify models): Switches Routers 4 I perform these types of tasks: Network management H/W installation and/or maintenance Other: S/W configuration 5 I use these types of documentation: Command reference Other: H/W installation Quick reference S/W configuration Online help 6 I access this information through: % Printed docs 7 I prefer this access method: 8 I use the following three product features the most: Years of experience with Cisco products: WAN H/W configuration Release notes % Cisco.com % Other: % CD-ROM Document Information Document Title: Cisco SES PNNI Controller Software Configuration Guide Part Number: 78-13539-01 S/W Release (if applicable): 1.1 On a scale of 1–5 (5 being the best), please let us know how we rate in the following areas: The document is written at my technical level of understanding. The information is accurate. The document is complete. The information I wanted was easy to find. The information is well organized. The information I found was useful to my job. Please comment on our lowest scores: Mailing Information Company Name Contact Name Date Job Title Mailing Address City State/Province ZIP/Postal Code Country Phone ( Extension Fax ( ) ) E-mail Can we contact you further concerning our documentation? Yes No You can also send us your comments by e-mail to [email protected], or by fax to 408-527-8089. FIRST-CLASS MAIL PERMIT NO. 4631 SAN JOSE CA BUSINESS REPLY MAIL POSTAGE WILL BE PAID BY ADDRESSEE ATTN DOCUMENT RESOURCE CONNECTION CISCO SYSTEMS INC 170 WEST TASMAN DRIVE SAN JOSE CA 95134-9883 NO POSTAGE NECESSARY IF MAILED IN THE UNITED STATES C O N T E N T S About This Guide Objectives Audience xvii xvii xvii Organization xviii Related Documentation xviii Cisco WAN Manager Release 10.5 Documentation xviii Cisco MGX 8850 Release 2.1 Documentation xix SES PNNI Release 1.1 Documentation xx Cisco WAN Switching Software, Release 9.3 Documentation xx MGX 8850 Multiservice Switch, Release 1.1.40 Documentation xxi MGX 8250 Edge Concentrator, Release 1.1.40 Documentation xxii MGX 8230 Multiservice Gateway, Release 1.1.40 Documentation xxiii Conventions xxiii Obtaining Documentation xxiv World Wide Web xxiv Documentation CD-ROM xxiv Ordering Documentation xxv Documentation Feedback xxv Obtaining Technical Assistance xxv Cisco.com xxv Technical Assistance Center xxvi Contacting TAC by Using the Cisco TAC Website Contacting TAC by Telephone xxvi CHA PTER 1 Preparing For Configuration 1-1 BPX SES Node Components 1-1 SES Controller 1-2 PXM Cards 1-2 BPX 8620 Switch 1-4 Broadband Switch Module Broadband Controller Card SES and BPX Interfaces 1-5 Typical Topology Routing Technology xxvi 1-4 1-5 1-7 1-7 Cisco SES PNNI Controller Software Configuration Guide Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 iii Contents Configuration Tasks 1-7 Collecting Information 1-8 General Configuration Data 1-8 Unique Switch Name 1-8 ATM Addressing Plan 1-9 IP Addressing Plan 1-9 Administrator Data 1-9 Network Clock Source 1-9 Network Management Plan 1-9 Line and Trunk Data 1-10 Planning for Card and Line Redundancy Configuration Worksheets 1-10 1-10 Guidelines for Creating an IP Address Plan CHA PTER 2 Configuring General Switch Features Configuration Quickstarts Initializing the Controller 1-12 2-1 2-1 2-3 Starting a CLI Management Session After Initialization Ending a CLI Management Session 2-6 Entering Commands at the Switch Prompt 2-7 Displaying Detailed Command Lists 2-8 Displaying Command Syntax and Parameters Configuring User Access Adding Users 2-11 2-5 2-10 2-10 Setting and Viewing the Switch Name 2-13 Viewing and Setting the Switch Date and Time Setting the LAN IP Addresses 2-14 Setting the Boot IP Address 2-14 Setting the LAN or Disk IP Address 2-17 Setting the Dial-Up Interface Address 2-19 Starting a CLI Session Through the LAN Port Setting and Viewing the SPVC Prefix 2-13 2-20 2-21 Configuring for Network Management 2-22 Configuring the SNMP Trap Source IP Address 2-22 Configuring the SNMP Manager Destination IP Address 2-22 Configuring the Community String and General Switch Information Verifying the Hardware Configuration 2-23 2-24 Cisco SES PNNI Controller Software Configuration Guide iv Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 Contents CHA PTER 3 Provisioning Communication Links 3-1 Quickstart Procedures for Provisioning Links on the SES Controlled BPX SES Controller Uplink Configuration Quickstart 3-2 PNNI Trunk Configuration Quickstart 3-3 AutoRoute Trunk Configuration Quickstart 3-5 PNNI UNI Port Configuration Quickstart 3-5 SPVC and SPVP Configuration Quickstart 3-7 MGX 8850 Release 1 Feeder Configuration Quickstart 3-9 AINI Link Configuration Quickstart 3-11 IISP Link Configuration Quickstart 3-12 3-2 BPX Configuration Procedures 3-13 Bringing Up a BXM Trunk 3-13 Configuring a BXM Trunk 3-14 Bringing Up a BXM Line 3-15 Adding a Port to a BXM Line 3-16 Bringing Up a Port on a BXM Line 3-17 Configuring a BXM Port 3-17 Assigning a Service Class Template to a VSI Interface 3-18 Enabling a Partition and Configuring Resources for a Trunk 3-19 Enabling a Partition and Configuring Resources for a Line 3-21 Defining Destination Addresses for Static Links 3-22 Assigning Static ATM Addresses to Destination Ports 3-23 Adding a Shelf to a Trunk 3-25 Enabling ILMI on a Trunk 3-26 SES Controller Configuration and Verification Procedures 3-27 Selecting the Port Signaling Protocol 3-27 Verifying PNNI Trunk Communications 3-30 Setting Up SVCs 3-31 Setting up an SVC without ILMI Address Registration 3-32 Setting up an SVC with ILMI Address Registration 3-33 Configuring SPVCs and SPVPs 3-34 Configuring the Slave Side of SPVCs and SPVPs 3-34 Configuring the Master Side of SPVCs and SPVPs 3-38 Configuring MGX 8850 Release 1 Feeder Connections 3-40 Setting Up the MGX 8850 End of the Feeder Trunk 3-40 Setting Up the SPVC Feeder Segment on the SES 3-42 Setting Up the PVC Segment on an MGX 8850 Feeder Node Operating Procedures 3-49 Adding a Port on the PXM 3-44 3-50 Cisco SES PNNI Controller Software Configuration Guide Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 v Contents Bringing up a Port on the PXM 3-50 Configuring SPVC Statistics Collection Configuring the BXM Qbin 3-51 Qbin Dependencies 3-51 Modifying an SPVC Connection 3-52 Deleting an SPVC Connection 3-55 Changing Partition Resources 3-55 CHA PTER 4 Managing PNNI Routes Configuring PNNI 3-50 4-1 4-1 PNNI Configuration Quickstart 4-2 Configuring the SES PNNI Node 4-3 Set Peer Group Leader Parameters 4-4 Set Timers and Thresholds 4-5 Set SVCC-Based Timers 4-6 Configure Summary Address(es) 4-7 Set Routing Policies 4-7 Configure PNNI Interfaces 4-8 Set Locally Reachable Address(es) 4-8 Show PNNI Link Hello Protocol 4-9 CHA PTER 5 Switch Operating Procedures 5-1 Managing the Configuration Files 5-1 Saving a Configuration 5-1 Clearing a Configuration 5-3 Restoring a Saved Configuration 5-3 Changing User Access Levels and Passwords 5-4 Changing Your Own User Password 5-4 Changing Any User Password 5-4 Deleting Users 5-5 Resetting the User cisco Password 5-6 Enabling and Disabling the User cisco Password Reset Modifying Port Parameters After AutoConfiguration Configuring Dynamic/Soft Partitioning Configuring SPVC Stats Collection 5-7 5-7 5-8 5-9 Setting ATM Address Filtering 5-9 Ingress/Incoming Calling Party Number Filtering 5-10 Configure an Ingress Filter to Reject all Calls Whose Calling Party Ends with a Specific Set Of Digits 5-16 Cisco SES PNNI Controller Software Configuration Guide vi Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 Contents Delete An Address Entry in a Filter 5-16 Disable Address Filtering Functionality on the Ingress 5-17 Destroy an Existing Filter 5-18 Create a filter to Reject All Calls Whose Calling Party Address Does Not Match Any Address Entry in the Filter 5-18 Enable Egress Address Filtering 5-19 Disable Address Filtering Functionality on the Egress 5-20 CHA PTER 6 Viewing and Responding to Alarms 6-1 Viewing and Responding to Alarms Using Physical Switch Controls PXM Card Controls 6-1 6-1 Displaying Alarm Reports in the CLI 6-4 Displaying Node Alarms 6-4 Displaying Card Alarms 6-4 Displaying Environment Alarms 6-5 Displaying Slot Alarms 6-6 Displaying Switching Alarms 6-6 Displaying Event Log Information Displaying Error Information CHA PTER 7 Network Management 6-6 6-7 7-1 Minimum System Requirements Hardware 7-1 Software 7-3 7-1 Installing and Configuring Cisco WAN Manager 7-3 Disk Partitioning Requirements 7-3 Partitioning One 9-GB Disk 7-4 Partitioning Two 9-GB Disks 7-5 Modifying the network.conf File for PNNI Networks Configuring PNNI Topology Discovery 7-6 Configuring the SES Controller 7-6 Cisco WAN Manager SES Controller PNNI Features SPVC Overview 7-7 7-5 7-6 WAN CiscoView 3.2 7-7 Installing CiscoView 7-7 Accessing CiscoView 7-7 Navigating in CiscoView 7-7 Main Menu Buttons 7-8 Status Bar and Buttons 7-9 Cisco SES PNNI Controller Software Configuration Guide Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 vii Contents Making Selections and Displaying Menus 7-9 Popup Menu Options 7-10 Using CiscoView 7-10 Preference Setting Options 7-11 Device-Specific Buttons within Configure Menu Integrating New Device Information 7-12 Device Support Utility Features 7-13 Using the Device Support Utility 7-13 7-12 Testing Basic Connectivity and Setup 7-13 Test the IP Connectivity 7-13 Open a Telnet Session to the Device 7-14 Verify the CiscoView Preferences 7-14 Call Tracing 7-14 Connection Trace 7-14 Connection Trace Success 7-14 Connection Trace Failure 7-15 CLI Commands Functionality 7-15 conntrace Command 7-15 Path Trace 7-15 Calling and Called Path Trace Success Path Trace Failure 7-16 SES CLI Pathtrace Commands 7-16 APPENDIX A 7-16 Downloading and Installing Software Upgrades Upgrade Process Overview A-1 A-1 Quickstart Procedures for Software Upgrades A-1 Graceful PXM Boot Upgrades A-2 Non-Graceful PXM Boot Upgrades A-3 Graceful PXM Runtime Software Upgrades A-4 Non-Graceful PXM Runtime Software Upgrades A-5 Quickstart Procedures for Software Downgrades A-6 PXM Boot Downgrades A-6 Non-Graceful PXM Runtime Software Downgrades Browsing the File System Locating Software Updates A-7 A-8 A-9 Copying Software Files to the Controller A-9 Upgrade Procedures for PXM Cards A-10 Upgrading PXM Boot Software A-10 Loading the Runtime Upgrade Software A-12 Cisco SES PNNI Controller Software Configuration Guide viii Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 Contents Starting the Upgrade Software A-14 Committing to a Runtime Software Upgrade Troubleshooting Upgrade Problems APPENDIX B Technical Specifications PNNI Compliance A-14 A-15 B-1 B-1 ATM Signaling Compliance B-2 UNI 3.0/3.1 Signaling B-2 UNI 4.0 Signaling B-2 IISP Signaling B-2 PNNI Signaling B-2 ATM Signaling Interworking B-3 Interoperability Support B-3 Processor Switching Module Specifications APPENDIX C Virtual Switch Interface B-4 C-1 Virtual Switch Interface Protocol C-1 VSI Master and Slaves C-1 Resource Partitioning C-3 Configuring VSI-ILMI C-4 Support Enabling ILMI Functionality for VSI Partitions on Port Interfaces Enable ILMI Functionality for VSI Partitions on Physical Trunk Interfaces Enable VSI ILMI Functionality on Virtual Trunk Interfaces C-5 Class of Service Templates C-6 Functional Description C-7 Service Class Template Structure C-8 Downloading Service Class Templates C-10 Assignment of a Service Class Template to an interface Card Qbin Configuration C-11 Qbin Dependencies C-11 Extended Services Types Support C-12 Connection Admission Control C-12 Supported Service Types C-12 APPENDIX D SNMP Management Information Base C-4 C-5 C-10 D-1 SNMP Fundamentals D-1 MIB Tree D-1 MIB Objects Overview D-3 Object Identifier D-3 Cisco SES PNNI Controller Software Configuration Guide Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 ix Contents Object Definitions SNMP Traps D-7 D-3 MIBs Supported by the SES Controller D-8 ATM MIB Object D-8 atmInterfaceConfTable D-8 PNNI MIB Objects D-9 pnniBaseGroup D-9 pnniNodeTable D-10 pnniNodePglTable D-13 pnniNodeTimerTable D-16 pnniNodeSvccTable D-18 pnniScopeMappingTable D-19 pnniLinkTable D-21 pnniSummaryAddressTable D-25 Cisco WAN SVC MIB Objects D-25 ciscoWANSvcInfo D-26 CiscoWANSpvc Port D-26 cwspConnTrace D-42 Cisco WAN ATM MIB Objects D-47 cwAtmChanCfgTable D-48 CwAtmChanStateTable D-56 CwAtmChanTestTable D-56 GLOSSARY INDEX Cisco SES PNNI Controller Software Configuration Guide x Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 F I G U R E S Figure 1-1 SES PNNI Node Figure 1-2 PXM Back Card Simple Block Diagram Figure 1-3 OC-3 Cabling from Two BXMs to Redundant PXMs Figure 1-4 DS3 Y-Cabling from Single BXM to Redundant PXM Figure 1-5 Using Multiple IP Addresses for Switch Access Figure 2-1 Workstation Connection to Console Port Figure 2-2 Hardware Required for Local LAN Connections Figure 3-1 SVC Setup Example Figure 4-1 PNNI Configuration Sequence Overview Figure 6-1 PXM Front Card Controls Figure 7-1 Connection Trace in PNNI and IISP Network Figure 7-2 Insert and Remove IEs Figure C-1 VSI Controller and Slave VSIs Figure C-2 VSI Master and VSI Slave Example Figure C-3 BXM Virtual Interfaces and Qbins C-3 Figure C-4 Service Class Template Overview C-8 Figure C-5 Service Class Template and Associated Qbin Selection Figure D-1 MIB Tree 1-2 1-3 1-6 1-7 1-12 2-3 2-17 3-31 4-2 6-2 7-15 7-17 C-2 C-2 C-9 D-2 Cisco SES PNNI Controller Software Configuration Guide Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 xi Figures Cisco SES PNNI Controller Software Configuration Guide xii Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 T A B L E S Table 1 Cisco WAN Manager Release 10.5 Documentation Table 2 WAN CiscoView Release 10 Documentation Table 3 Cisco MGX 8850 Switch Release 2.1 Documentation Table 4 SES PNNI Controller Release 1.1 Documentation Table 5 Cisco WAN Switching Release 9.3 Documentation Table 6 MGX 8850 Multiservice Gateway Documentation xxi Table 7 MGX 8250 Multiservice Gateway Documentation xxii Table 8 MGX 8230 Multiservice Gateway Documentation xxiii Table 1-1 General Switch Configuration Parameters Table 1-2 Port Address Worksheet Table 2-1 CLI Prompt Components 2-5 Table 2-2 Card State Descriptions 2-9 Table 2-3 User Access Levels Table 2-4 bootChange Command Option Descriptions Table 2-5 Hardware Configuration Worksheet Table 2-6 Valid Card Installation Options Table 3-1 ATM Address Configuration Parameters 3-22 Table 3-2 ATM Address Configuration Parameters 3-24 Table 3-3 Port Signaling Configuration Parameters 3-28 Table 3-4 Parameters for the addcon Command Table 3-5 Service Class Template Qbin Parameters Table 3-6 Service Class Template Commands Table 3-7 Partition Resource Command Parameters Table 6-1 LED Indicators for PXM Table 7-1 Minimum CWM Release 10.2 Workstation Requirements Table 7-2 Sun Platform Requirements Table 7-3 Partitioning a Single 9-GB Disk 7-4 Table 7-4 Partitioning the First 9-GB Disk 7-5 Table 7-5 Supported SPVC Connections Table 7-6 CiscoView Main Menu Buttons Table 7-7 CiscoView Status Bar and Buttons xviii xix xix xx xxi 1-10 1-11 2-11 2-15 2-24 2-26 3-35 3-51 3-51 3-55 6-2 7-1 7-2 7-7 7-8 7-9 Cisco SES PNNI Controller Software Configuration Guide Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 xiii Tables Table 7-8 Cisco View Popup Menu Options Table 7-9 Configure Menu Buttons (Device Specific) Table A-1 File System Commands Table A-2 Software Versions Reported During Graceful Upgrades Table A-3 Software Versions Reported During Non-Graceful Upgrades Table A-4 Troubleshooting Upgrade Problems Table B-1 PXM Specifications Table C-1 ifci Parameters (Virtual Switch Interface) Table C-2 Partition Criteria Table C-3 Service Class Template Qbin Parameters Table C-4 Service Category Listing Table C-5 VSI Special Service Types Table C-6 ATM Forum Service Types, CBR, UBR, and ABR Table C-7 ATM Forum VBR Service Types Table C-8 MPLS (Tag Switching) Service Types Table C-9 Connection Parameter Descriptions and Ranges Table D-1 atmInterfaceConfTable Entries Table D-2 pnniBaseGroup D-9 Table D-3 pnniNodeTable D-11 Table D-4 pnniNodePglTable Table D-5 pnniNodeTimerTable Table D-6 Nodal SVCC-based RCC Variables Table Table D-7 pnniScopeMappingTable Table D-8 pnniLinkTable Table D-9 pnniSummaryAddressTable Table D-10 SVC Information Group Table D-11 Interface Configuration Table Entries Table D-12 Port Call Statistics Table Entries Table D-13 Port CAC Configuration Table Entries Table D-14 Port Signaling Statistics Table Entries Table D-15 Port Address Table Entries D-39 Table D-16 Port Loading Table Entries D-40 Table D-17 Port Connection Trace Availability Entry Table D-18 Port Connection Trace If Index Entry Table D-19 Port Connection Trace Control Table Entry 7-10 7-12 A-8 A-12 A-13 A-16 B-4 C-3 C-4 C-11 C-13 C-14 C-15 C-16 C-16 C-17 D-8 D-13 D-16 D-18 D-19 D-22 D-25 D-26 D-27 D-30 D-32 D-37 D-42 D-42 D-42 Cisco SES PNNI Controller Software Configuration Guide xiv Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 Tables Table D-20 Port Connection Trace Control Table Entries Table D-21 Port Connection Data Table Table D-22 Interface Operation Table Entries Table D-23 cwAtmChanCfgTable Table D-24 cwAtmChanStateEntry Objects Table D-25 cwAtmChanTestEntry Objects D-42 D-44 D-45 D-48 D-56 D-56 Cisco SES PNNI Controller Software Configuration Guide Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 xv Tables Cisco SES PNNI Controller Software Configuration Guide xvi Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 About This Guide Welcome to the software configuration manual for the Service Expansion Shelf (SES) controller. The SES controller is a virtual switch interface (VSI) controller that provides a BPX 8600 series wide-area switch with the capability to create switched virtual circuits (SVCs) by using the UNI and PNNI protocols, and soft permanent virtual circuits by using the PNNI protocol. Each BPX 8600 series node that will originate, transport, or terminate SVC/SPVC connections must be collocated and directly connected to an SES controller to deploy PNNI functionality. The combined BPX 8600 and SES controller are referred to as a SES PNNI node in this manual. This preface contains the following sections: • Objectives • Audience • Organization • Related Documentation • Conventions • Obtaining Documentation • Obtaining Technical Assistance Objectives This publication describes the SES controller hardware, software, services, and configuration procedures for adding PNNI, IISP, ATM SVCs/SVPs, and ATM SPVCs/SPVPs to a BPX 8600 network. Audience This publication is designed for the network operator responsible for configuring the SES controller(s) in a BPX 8600 network, and for provisioning PNNI services. Both the installer and network operator should be familiar with Cisco WAN switching networks, the BPX 8600 series of wide area switches, and the Cisco WAN Manager (CWM)—formerly known as StrataView Plus—and CiscoView network management systems. Note Installation of the equipment must be performed by trained service personnel. Cisco SES PNNI Controller Software Configuration Guide Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 xvii About This Guide Organization Organization This document contains the following chapters and appendices: Chapter 1, “Preparing For Configuration,” provides an overview of the SES controller, the SES PNNI node, and ATM SVCs and SPVCs. Chapter 2, “Configuring General Switch Features,” provides procedures for setting general switch features on an SES controller. Chapter 3, “Provisioning Communication Links,” provides bring-up and initial configuration procedures for communication links of the SES node. Chapter 4, “Managing PNNI Routes,” provides procedures for setting up PNNI Routing parameters and SPVC/SVC connections on the SES node. Chapter 5, “Switch Operating Procedures,” provides general operational procedures for the SES node. Chapter 6, “Viewing and Responding to Alarms,” provides information about alarms on the SES node. Chapter 7, “Network Management,” introduces the network management tools used in conjunction with the SES controller: Cisco WAN Manager, CiscoView, SES CLI show commands, and call tracing in a PNNI network. Appendix A, “Downloading and Installing Software Upgrades,” provides procedures for downloading and installing software on an SES controller. Appendix B, “Technical Specifications,” lists the relevant specifications for the SES controller. Appendix C, “Virtual Switch Interface,” provides an overview of the Virtual Switch Interface protocol used by the SES controller to control the BPX switch for PNNI networking. Appendix D, “SNMP Management Information Base,” describes the SNMP MIBs used by the SES controller for PNNI and ATM signaling. Related Documentation The following Cisco publications contain additional information related to the operation of this product and associated equipment in a Cisco WAN switching network. Cisco WAN Manager Release 10.5 Documentation The product documentation for the Cisco WAN Manager (CWM) network management system for Release 10.5 is listed in Table 1. Table 1 Cisco WAN Manager Release 10.5 Documentation Title Description Cisco WAN Manager Installation Guide for Solaris, Provides procedures for installing Release 10 of the CWM network Release 10.5 management system and Release 5.3 of CiscoView. DOC-7812948= Cisco WAN Manager User’s Guide, Release 10.5 DOC-7812945= Describes how to use the CWM Release 10 software which consists of user applications and tools for network management, connection management, network configuration, statistics collection, and security management. Cisco SES PNNI Controller Software Configuration Guide xviii Release 1.1, Part Number 78-13539-01 Rev. A0, September 2001 About This Guide Related Documentation Table 1 Cisco WAN Manager Release 10.5 Documentation (continued) Title Description Cisco WAN Manager SNMP Service Agent, Release 10.5 Provides information about the CWM Simple Network Management Protocol Service Agent, an optional adjunct to CWM used for managing Cisco WAN switches using SNMP. DOC-7812947= Cisco WAN Manager Database Interface Guide, Release 10.5 Provides information about accessing the CWM Informix OnLine database that is used to store information about the network elements. DOC-7812944= Table 2 WAN CiscoView Release 10 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. DOC-7811242= WAN CiscoView Release 3 for the MGX 8250 Edge Concentrator, Release 1 DOC-7811241= Provides instructions for using this network management software application that allows you to perform minor configuration and troubleshooting tasks. WAN CiscoView Release 3 for the MGX 8230 Multiservice Provides instructions for using this network management Gateway, Release 1 software application that allows you to perform minor configuration and troubleshooting tasks. DOC-7810926= Cisco MGX 8850 Release 2.1 Documentation The product documentation for the installation and operation of the MGX 8850 Release 2.1 switch is listed in Table 3. Table 3 Cisco MGX 8850 Switch Release 2.1 Documentation Title Description Cisco MGX 8850 Routing Switch Hardware Installation Guide, Release 2.1 Describes how to install the MGX 8850 routing switch. It explains what the switch does, and covers site preparation, grounding, safety, card installation, and cabling. DOC-7812561= Cisco MGX 8850 Switch Command Reference, Release 2.1 Describes how to use the commands that are available in the CLI 1of the MGX 8850 switch. DOC-7812563= Cisco MGX 8850 Switch Software Configuration Guide, Release 2.1 DOC-7812551= Cisco MGX 8850 SNMP Reference, Release 2.1 DOC-7812562= Describes how to configure the MGX 8850 switch to operate as ATM edge and core switches. This guide also provides some operation and maintenance procedures. Provides information on all supported MIB 2objects, support restrictions, traps, and alarms for the AXSM, PXM45, and RPM. PNNI is also supported. Cisco SES PNNI Controller Software Configuration Guide Release 1.1, Part Number 78-13539-01 Rev. A0, September 2001 xix About This Guide Related Documentation Table 3 Cisco MGX 8850 Switch Release 2.1 Documentation (continued) Title Description Cisco MGX and SES PNNI Network Planning Guide Provides guidelines for planning a PNNI network that uses the MGX 8850 switch and the BPX 8600 switch. When connected to a PNNI network, each BPX 8600 series switch requires a Service Expansion Shelf (SES) for PNNI route processing. DOC-7813543= Cisco MGX Route Processor Module Installation and Configuration Guide, Release 2.1 DOC-7812510= Describes how to install and configure the MGX Route Processor Module (RPM-PR) in the MGX 8850 Release 2.1 switch. Also provides site preparation, troubleshooting, maintenance, cable and connector specifications, and basic IOS configuration information. 1. CLI = command line interface 2. MIB = Management Information Base SES PNNI Release 1.1 Documentation The product documentation that contains information for the understanding, the installation, and the operation of the Service Expansion Shelf (SES) PNNI Controller is listed in Table 4. Table 4 SES PNNI Controller Release 1.1 Documentation Title Description Cisco SES PNNI Controller Software Configuration Guide, Release 1.1 Describes how to configure, operate, and maintain the SES PNNI Controller. DOC-7813539= Cisco SES PNNI Controller Software Command Reference, Release 1.1 Provides a description of the commands used to configure and operate the SES PNNI Controller. DOC-7813541= Cisco MGX and SES PNNI Network Planning Guide DOC-7813543= Provides guidelines for planning a PNNI network that uses the MGX 8850 switch and the BPX 8600 switch. When connected to a PNNI network, each BPX 8600 series switch requires a SES for PNNI route processing. Cisco WAN Switching Software, Release 9.3 Documentation The product documentation for the installation and operation of the Cisco WAN Switching Software Release 9.3 is listed in Table 5. Cisco SES PNNI Controller Software Configuration Guide xx Release 1.1, Part Number 78-13539-01 Rev. A0, September 2001 About This Guide Related Documentation Table 5 Cisco WAN Switching Release 9.3 Documentation Title Description Cisco BPX 8600 Series Installation and Configuration, Release 9.3.30 Provides a general description and technical details of the BPX broadband switch. DOC-7812907= Cisco WAN Switching Command Reference, Release 9.3.30 DOC-7812906= Cisco IGX 8400 Series Installation Guide, Release 9.3.30 Provides detailed information on the general command line interface commands. Provides hardware installation and basic configuration information for IGX 8400 Series switches running Switch Software Release 9.3.30 or earlier. OL-1165-01 (online only) Cisco IGX 8400 Series Provisioning Guide, Release 9.3.30 Provides information for configuration and provisioning of selected services for the IGX 8400 Series switches running Switch Software Release 9.3.30 or earlier. OL-1166-01 (online only) Cisco IGX 8400 Series Regulatory Compliance and Safety Information Provides regulatory compliance, product warnings, and safety recommendations for the IGX 8400 Series switch. DOC-7813227= MGX 8850 Multiservice Switch, Release 1.1.40 Documentation The product documentation that contains information for the installation and operation of the MGX 8850 Multiservice Switch is listed in Table 6. Table 6 MGX 8850 Multiservice Gateway Documentation Title Description Cisco MGX 8850 Multiservice Switch Installation and Configuration, Release 1.1.3 Provides installation instructions for the MGX 8850 multiservice switch. DOC-7811223= Cisco MGX 8800 Series Switch Command Reference, Release 1.1.3. Provides detailed information on the general command line for the MGX 8850 switch. DOC-7811210= Cisco MGX 8800 Series Switch System Error Messages, Release 1.1.3 Provides error message descriptions and recovery procedures. DOC-7811240= Cisco MGX 8850 Multiservice Switch Overview, Release 1.1.3 OL-1154-01 (online only) Provides a technical description of the system components and functionary of the MGX 8850 multiservice switch from a technical perspective. Cisco SES PNNI Controller Software Configuration Guide Release 1.1, Part Number 78-13539-01 Rev. A0, September 2001 xxi About This Guide Related Documentation Table 6 MGX 8850 Multiservice Gateway Documentation (continued) Title Description Cisco MGX Route Processor Module Installation and Configuration Guide, Release 1.1 Describes how to install and configure the MGX Route Processor Module (RPM/B and RPM-PR) in the MGX 8850, MGX 8250, and MGX 8230 Release 1 switch. Also provides site preparation, troubleshooting, maintenance, cable and connector specifications, and basic IOS configuration information. DOC-7812278= 1.1.40 Version Software Release Notes Cisco WAN MGX 8850, MGX 8230, and MGX 8250 Switches Provides new feature, upgrade, and compatibility information, as well as known and resolved anomalies. DOC-7813594= MGX 8250 Edge Concentrator, Release 1.1.40 Documentation The documentation that contains information for the installation and operation of the MGX 8250 Edge Concentrator is listed in Table 7. Table 7 MGX 8250 Multiservice Gateway Documentation Title Description Cisco MGX 8250 Edge Concentrator Installation and Configuration, Release 1.1.3 Provides installation instructions for the MGX 8250 Edge Concentrator. DOC-7811217= Cisco MGX 8250 Multiservice Gateway Command Reference, Release 1.1.3 Provides detailed information on the general command line interface commands. DOC-7811212= Cisco MGX 8250 Multiservice Gateway Error Messages, Release 1.1.3 Provides error message descriptions and recovery procedures. DOC-7811216= Cisco MGX 8250 Edge Concentrator Overview, Release 1.1.3 Describes the system components and functionality of the MGX 8250 edge concentrator from a technical perspective. DOC-7811576= Cisco MGX Route Processor Module Installation and Configuration Guide, Release 1.1 DOC-7812278= Describes how to install and configure the MGX Route Processor Module (RPM/B and RPM-PR) in the MGX 8850, MGX 8250, and MGX 8230 Release 1 switch. Also provides site preparation, troubleshooting, maintenance, cable and connector specifications, and basic IOS configuration information. 1.1.40 Version Software Release Notes Cisco WAN MGX 8850, MGX 8230, and MGX 8250 Switches Provides new feature, upgrade, and compatibility information, as well as known and resolved anomalies. DOC-7813594= Cisco SES PNNI Controller Software Configuration Guide xxii Release 1.1, Part Number 78-13539-01 Rev. A0, September 2001 About This Guide Conventions MGX 8230 Multiservice Gateway, Release 1.1.40 Documentation The documentation that contains information for the installation and operation of the MGX 8230 Edge Concentrator is listed in Table 8. Table 8 MGX 8230 Multiservice Gateway Documentation Title Description Cisco MGX 8230 Edge Concentrator Installation and Configuration, Release 1.1.3 Provides installation instructions for the MGX 8230 Edge Concentrator. DOC-7811215= Cisco MGX 8230 Multiservice Gateway Command Reference, Release 1.1.3 Provides detailed information on the general command line interface commands. DOC-7811211= Cisco MGX 8230 Multiservice Gateway Error Messages, Release 1.1.3 Provides error message descriptions and recovery procedures. DOC-78112113= Cisco MGX 8230 Edge Concentrator Overview, Release 1.1.3 DOC-7812899= Cisco MGX Route Processor Module Installation and Configuration Guide, Release 1.1 DOC-7812278= 1.1.40 Version Software Release Notes Cisco WAN MGX 8850, MGX 8230, and MGX 8250 Switches Provides a technical description of the system components and functionary of the MGX 8250 edge concentrator from a technical perspective. Describes how to install and configure the MGX Route Processor Module (RPM/B and RPM-PR) in the MGX 8850, MGX 8250, and MGX 8230 Release 1 switch. Also provides site preparation, troubleshooting, maintenance, cable and connector specifications, and basic IOS configuration information. Provides new feature, upgrade, and compatibility information, as well as known and resolved anomalies. DOC-7813594= Conventions The Cisco SES PNNI Controller Software Controller Configuration Guide uses the following conventions to convey instructions and information. Command descriptions use these conventions: • Commands and keywords are in boldface. • Arguments for which you supply values are in italic font. • Elements in square brackets ([ ]) are optional. • Alternative but required keywords are grouped in braces ({ }) and are separated by vertical bars (|). • Terminal sessions and information the system displays are in screen font. • Information you enter is in boldface screen font. • Nonprinting characters, such as passwords, are in angle brackets (< >). • Default responses to system prompts are in square brackets ([ ]). Cisco SES PNNI Controller Software Configuration Guide Release 1.1, Part Number 78-13539-01 Rev. A0, September 2001 xxiii About This Guide Obtaining Documentation Notes, cautions, warnings, and tips use the following conventions and symbols: Note Caution Warning Tip Means reader take note. Notes contain helpful suggestions or references to material not covered in this manual. Means reader be careful. In this situation, you might do something that could result in equipment damage or loss of data. 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 the warning, refer to the Regulatory Compliance and Safety document that accompanied the device. Means the following information will help you solve a problem. Obtaining Documentation The following sections provide sources for obtaining documentation from Cisco Systems. World Wide Web You can access the most current Cisco documentation on the World Wide Web at the following sites: • http://www.cisco.com • http://www-china.cisco.com • http://www-europe.cisco.com Documentation CD-ROM Cisco documentation and additional literature are available in a CD-ROM package, which ships with your product. The Documentation CD-ROM is updated monthly and may be more current than printed documentation. The CD-ROM package is available as a single unit or as an annual subscription. Cisco SES PNNI Controller Software Configuration Guide xxiv Release 1.1, Part Number 78-13539-01 Rev. A0, September 2001 About This Guide Obtaining Technical Assistance Ordering Documentation Cisco documentation is available in the following ways: • Registered Cisco Direct Customers can order Cisco Product documentation from the Networking Products MarketPlace: http://www.cisco.com/cgi-bin/order/order_root.pl • Registered Cisco.com users can order the Documentation CD-ROM through the online Subscription Store: http://www.cisco.com/go/subscription • Nonregistered Cisco.com users can order documentation through a local account representative by calling Cisco corporate headquarters (California, USA) at 408 526-7208 or, in North America, by calling 800 553-NETS(6387). Documentation Feedback If you are reading Cisco product documentation on the World Wide Web, you can submit technical comments electronically. Click Feedback in the toolbar and select Documentation. After you complete the form, click Submit to send it to Cisco. You can e-mail your comments to [email protected]. To submit your comments by mail, for your convenience many documents contain a response card behind the front cover. Otherwise, you can mail your comments to the following address: Cisco Systems, Inc. Document Resource Connection 170 West Tasman Drive San Jose, CA 95134-9883 We appreciate your comments. Obtaining Technical Assistance Cisco provides Cisco.com as a starting point for all technical assistance. Customers and partners can obtain documentation, troubleshooting tips, and sample configurations from online tools. For Cisco.com registered users, additional troubleshooting tools are available from the TAC website. Cisco.com Cisco.com is the foundation of a suite of interactive, networked services that provides immediate, open access to Cisco information and resources at anytime, from anywhere in the world. This highly integrated Internet application is a powerful, easy-to-use tool for doing business with Cisco. Cisco.com provides a broad range of features and services to help customers and partners streamline business processes and improve productivity. Through Cisco.com, you can find information about Cisco and our networking solutions, services, and programs. In addition, you can resolve technical issues with online technical support, download and test software packages, and order Cisco learning materials and merchandise. Valuable online skill assessment, training, and certification programs are also available. Cisco SES PNNI Controller Software Configuration Guide Release 1.1, Part Number 78-13539-01 Rev. A0, September 2001 xxv About This Guide Obtaining Technical Assistance Customers and partners can self-register on Cisco.com to obtain additional personalized information and services. Registered users can order products, check on the status of an order, access technical support, and view benefits specific to their relationships with Cisco. To access Cisco.com, go to the following website: http://www.cisco.com Technical Assistance Center The Cisco TAC website is available to all customers who need technical assistance with a Cisco product or technology that is under warranty or covered by a maintenance contract. Contacting TAC by Using the Cisco TAC Website If you have a priority level 3 (P3) or priority level 4 (P4) problem, contact TAC by going to the TAC website: http://www.cisco.com/tac P3 and P4 level problems are defined as follows: • P3—Your network performance is degraded. Network functionality is noticeably impaired, but most business operations continue. • P4—You need information or assistance on Cisco product capabilities, product installation, or basic product configuration. In each of the above cases, use the Cisco TAC website to quickly find answers to your questions. To register for Cisco.com, go to the following website: http://www.cisco.com/register/ If you cannot resolve your technical issue by using the TAC online resources, Cisco.com registered users can open a case online by using the TAC Case Open tool at the following website: http://www.cisco.com/tac/caseopen Contacting TAC by Telephone If you have a priority level 1(P1) or priority level 2 (P2) problem, contact TAC by telephone and immediately open a case. To obtain a directory of toll-free numbers for your country, go to the following website: http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml P1 and P2 level problems are defined as follows: • P1—Your production network is down, causing a critical impact to business operations if service is not restored quickly. No workaround is available. • P2—Your production network is severely degraded, affecting significant aspects of your business operations. No workaround is available. Cisco SES PNNI Controller Software Configuration Guide xxvi Release 1.1, Part Number 78-13539-01 Rev. A0, September 2001 C H A P T E R 1 Preparing For Configuration This chapter introduces the Service Expansion Shelf (SES) controller 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. BPX SES Node Components The complete BPX SES node architecture consists of the combined BPX 8620 switch and the SES controller (see Figure 1-1). The SES controller uses a Command Line Interface and/or combined network management system of Cisco WAN Manager and CiscoView to configure and monitor the BPX SES node. Note This document only describes how to use the SES in conjunction with a BPX 8600 as a PNNI controller. Cisco SES PNNI Controller Software Configuration Guide Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 1-1 Chapter 1 Preparing For Configuration BPX SES Node Components Figure 1-1 SES PNNI Node SES controller BPX SES node 40852 BPX 8620 SES Controller The SES controller is a 7-slot chassis that contains two Processor Switch Modules (PXMs) that run the PNNI and SVC software. One PXM serves as the active processor, while the other serves as the standby. The PNNI controller is connected to the BPX switch by either the ATM/OC-3 interface (see Figure 1-3) or the ATM/DS3 interfaces (see Figure 1-4). Note The SES can be used in several WAN switching applications, and is not limited to function only as a PNNI controller. However, when used as the SES controller, the SES may only be populated with two switch processor modules (PXMs) and associated back cards. The remaining five slots of a shelf in service as a SES controller are not used. PXM Cards Two PXM cards must reside in the SES controller to enable redundant PNNI functionality. Line and service cards are not applicable to PNNI operations and do not operate in the PNNI controller. Cisco SES PNNI Controller Software Configuration Guide 1-2 Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 Chapter 1 Preparing For Configuration BPX SES Node Components PXM Front Cards The active PXM card controls the Service Expansion Shelf and runs the PNNI and SVC software, which controls the associated BPX switch for PNNI networking and ATM switched virtual circuits. The standby PXM provides backup redundancy if the active PXM fails. PXM Back Cards A pair of PXM back cards is required for each installed PXM front card. A PXM back card pair consists of the following: • User interface back card—PXM-UI The PXM-UI back card provides the following ports: – Ethernet port – RS232 Maintenance port – RS232 Control port – T1/E1 timing reference ports – Audio and visual alarm interface port • ATM trunk interface—PXM ATM uplink The PXM ATM uplink back card is the ATM Trunk Interface that provides line drivers for the uplink interface. For SES controller applications, the PXM ATM interface uplink card uses either a single port from the quad OC-3 multi-mode port or the quad DS-3 port back card. Figure 1-2 shows a block diagram of the PXM back card. PXM Back Card Simple Block Diagram Terminal Modem RS232 RS232 Control port Maintenance port Ext clocks T1/E1 timing reference PXM-UI backcard Alarm Alarm output Network management Processor Memory Hard disk PNNI and ATM software VSI software Ethernet PXM ATM Trunk Interface -uplink backcard- LAN OC-3 ATM interface or DS3 Collocated BPX 8620 Switch A mismatch between the PXM back card and front card will generate a major alarm. (The PXM has a daughter card that is factory installed and must match the type of ATM interface back card.) Cisco SES PNNI Controller Software Configuration Guide Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 1-3 40853 Figure 1-2 Chapter 1 Preparing For Configuration BPX SES Node Components BPX 8620 Switch The BPX 8620 is a standards based, high-capacity broadband ATM switch that provides backbone ATM switching and delivers a wide range of other user services. For more information about the BPX, refer to Cisco BPX 8600 Series Installation and Configuration Release 9.2. Broadband Switch Module The Broadband Switch Module (BXM) is a multiplexing ATM interface card that uses STRATM-based application-specific integrated circuit (ASIC) technology to deliver ATM networking functions. Interfaces Supported The following interfaces for ATM CPE and ATM trunks are supported on the BXM for PNNI and ATM SVCs/SPVCs: Interface Card Type OC-12 BXM-2-OC-12 OC-3 BXM-8-OC-3 T3 BXM-12-DS3 E3 BXM-12-E3 The internal interface between the SES controller and the BPX switch is either OC-3 or T3/E3. UNI and NNI Interfaces BXM trunks and ports are classified as User-to-Network Interface (UNI) or Network-to-Network Interface (NNI). The UNI is the service interface for ATM customer premise equipment (CPE) connected to the BPX SES node. It defines the signaling method which the CPE must use to request and setup SVCs/SPVCs through the wide-area ATM network. Used to send messages from the network to the CPE (such as a user device) on the status of the circuit and rate control information to prevent network congestion. Each UNI port in a BPX SES node can support 16 ATM end systems addresses. For ATM SVCs/SPVCs, the UNI supports either the ATM Forum 3.0 or 3.1 signaling standards as well as traditional ATM PVCs. Note The BPX switch also supports high-speed ATM UNI ports. The NNI is the interface to other SES PNNI nodes or foreign ATM switches. The SES controller supports either the Interim Inter-switch Protocol (IISP) 3.0/3.1, the Private Network-to-Network Interface (PNNI), or AINI. These NNI interfaces provide the switching and routing functions between Cisco WAN switching networks and other networks. Information passing across an NNI is related to circuit routing and status of the circuit in the adjacent network. Note In this guide, a trunk refers to the connection between two BPX switches, but NNI may also refer to both a connection between WAN Service Nodes and a connection between a WAN Service Node and a foreign switch. Cisco SES PNNI Controller Software Configuration Guide 1-4 Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 Chapter 1 Preparing For Configuration BPX SES Node Components Broadband Controller Card The Broadband Controller Card (BCC) is a microprocessor-based system controller used to control the overall operation of the BPX switch. The controller card is a front card that is usually equipped as a redundant pair. Slots number 7 and number 8 of the BPX chassis are reserved for the active and standby broadband controller cards. Each broadband controller front card requires a corresponding back card. BPX BCC Major Functions The BCC performs the following major system functions for the BPX switch portion of a BPX SES node: • Runs the system software for controlling, configuring, diagnosing, and monitoring the BPX switch. • Contains the crosspoint switch matrix operating at 800 Mbps per serial link (BCC-32 or BCC-3) or up to 1600 Mbps (BCC-4). • Contains the arbiter, which controls polling on each high-speed data port and grants the access to the switch matrix for each port with data to transfer. • Generates Stratu-3 system clocking, which can be synchronized to either a selected trunk or an external clock input. • Communicates configuration and control information to all other cards in the same node over the backplane communication bus. • Communicates with all other nodes in the network. • Provides a communications processor for an Ethernet LAN port plus two low-speed data ports. – The BCC-bc provides the physical interface for the BCC-32. – The BCC-3-bc provides the physical interface for the BCC-3 and BCC-4. SES and BPX Interfaces Figure 1-3 and Figure 1-4 are simple block diagrams of a BPX SES node. These figures illustrate the internal interfaces of the BPX SES node (that is, between the SES controller and the BPX switch) and the external interfaces. The external interfaces of a BPX SES node connect to ATM end systems, other ATM or PNNI nodes or networks, and Network Management Systems, such as the Cisco WAN Manager or CiscoView. Cisco SES PNNI Controller Software Configuration Guide Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 1-5 Chapter 1 Preparing For Configuration BPX SES Node Components OC-3 Cabling from Two BXMs to Redundant PXMs Network Management station Cisco WAN Manager and CiscoView BPX SES node SES controller User interface PXM (active) Ethernet RS232 Terminal PXM (standby) OC-3 BCC BXMs ATM end systems BXM BXM ATM end systems BXM BXM BPX 8600 To other BPX 8600 switches or PNNI nodes ATM trunks NNI to foreign switch ATM trunks 40858 Figure 1-3 Cisco SES PNNI Controller Software Configuration Guide 1-6 Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 Chapter 1 Preparing For Configuration Typical Topology Figure 1-4 DS3 Y-Cabling from Single BXM to Redundant PXM Network Management station Cisco WAN Manager and CiscoView BPX SES node SES controller User interface PXM (active) RS232 Terminal PXM (standby) Ethernet DS3 BCC BXM BXM BXM ATM end systems BXM BXM BPX 8600 NNI to foreign switch ATM trunks 40859 ATM end systems To other BPX 8600 switches or PNNI nodes ATM trunks Typical Topology Release 1.1 of the SES controller acts as a core switch in the PNNI network. Routing Technology Release 1.1 of the SES controller supports the Private Network-to-Network Interface (PNNI) routing protocol. Configuration Tasks Switch configuration is easier if you are familiar with the overall configuration process. To configure and start up the SES switch, you need to do some or all of the following tasks: • Configure general switch features • Configure the physical connections to other devices • Provision ATM connections to other devices • Enable PNNI call routing Cisco SES PNNI Controller Software Configuration Guide Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 1-7 Chapter 1 Preparing For Configuration Collecting Information This chapter describes how to collect or create the information you need to complete these tasks. Chapter 2, “Configuring General Switch Features,” describes how to set up general switch features such as the date, the PNNI controller, and network management. You need to follow the procedures in this chapter to prepare your switch for general operation. Collecting Information To successfully configure the SES controller, you must collect information about the other devices to which it will connect. Also, you need to know the line speeds and protocols used on the trunks that connect to the switch. For PNNI routing, you also need to have an addressing plan for the network in which the SES controller is installed. This information can be grouped into the following categories: • General configuration data • Edge device and ATM device trunk data • Core node trunk data The following sections introduce these types of data and provide guidelines for collecting the data. General Configuration Data During configuration, you will need to enter general configuration data that describes the switch and how it will be used in the network. This data includes • Unique switch name • ATM addressing plan • IP addressing plan • Administrator data • Network clock source plan • Network management plan • Line and trunk data The following sections describe these topics in more detail. Unique Switch Name Each switch must have its own name (which consists of up to 32 characters), unique within the ATM network. If you are adding a switch to a network, find out if the network administrator has established switch naming conventions, and find out which names have already been used. It is a good practice to name switches according to location, as such names convey both the switch identity and its location. The procedure for setting the name is described in “Setting and Viewing the Switch Name” in Chapter 2, “Configuring General Switch Features.” Cisco SES PNNI Controller Software Configuration Guide 1-8 Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 Chapter 1 Preparing For Configuration Collecting Information ATM Addressing Plan An ATM network addressing plan is critical for successful operation of the SES Controller Release 1.1 switch in an ATM network. 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. PNNI network addressing is described in “Cisco MGX and SES PNNI Network Planning Guide.” IP Addressing Plan An IP network-addressing plan is required for switch management. IP network addressing is described in “Guidelines for Creating an IP Address Plan,” later in this chapter. Administrator Data In most cases, more than one administrator will manage the switch. The SES Controller Release 1.1 switch supports multiple administrators and several different administration levels. As part of the planning process, you might want to identify who will be managing the switch and at what level. You can learn more about managing administrators by reading “Configuring User Access” in Chapter 2, “Configuring General Switch Features.” Network Clock Source The SES controller receives its clock synchronization automatically from the BPX switch to which it is attached. You do not need to do any clock configuration on the SES controller. Network Management Plan You can use the following tools to manage the SES controller: • Command line interface (CLI) provided with the switch • Cisco WAN Manager • Cisco View • Third-party SNMP manager The CLI that comes with the switch is the least expensive option. To use the other tools, you must purchase Cisco WAN Manager (CWM) or a Simple Network Management Protocol (SNMP) manager. The SES Controller Release 1.1 switch comes with an SNMP agent for use with an SNMP manager. The advantage to using CWM or an SNMP manager is that you can use one program to simultaneously manage multiple devices. Also, CWM is the only management tool that can configure Service Class Templates (SCTs), which are described in Chapter 5, “Switch Operating Procedures.” Most installations require at least one CWM workstation to complete the switch configuration. Cisco View is a CWM component that can be used independently of CWM to provide limited monitoring and management capabilities. To determine which versions of CWM and Cisco View are compatible with this SES Controller Release 1.1, refer to the Release Notes for Cisco WAN SES Controller Software Release 1.1. For information on managing the switch with an SNMP manager, refer to the Cisco SNMP Reference, Release 1.1. Cisco SES PNNI Controller Software Configuration Guide Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 1-9 Chapter 1 Preparing For Configuration Planning for Card and Line Redundancy Line and Trunk Data When configuring lines and trunks that connect the controller to other devices, you need to collect the following: • Physical line type and configuration data • ATM port configuration data The SES Controller Release 1.1 supports 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. In these situations, change your configuration plan to use settings that are supported at both ends. Planning for Card and Line Redundancy Card redundancy is a feature that associates two cards, so that if one card fails, the other card assumes operation. Processor Switch Module (PXM) card redundancy is preconfigured on the SES Controller Release 1.1 switch for PXM cards. If PXM cards and their associated back cards are inserted in slots 1 and 2, they will automatically operate as redundant cards. One card assumes the active role, and the other card operates in standby mode. Note PXM redundancy does not provide protection for the BXM card on the BPX. You must establish BXM redundancy at the BPX CLI. Configuration Worksheets Table 1-1 lists general switch parameters you will need to configure in each new switch. Table 1-1 General Switch Configuration Parameters Feature Parameter Information Value to Configure PXM runtime software version number Text Node name Text Time zone Enter a zone Time zone offset Hours to offset PNNI controller Controller ID 2 Controller type 2 (PNNI) Controller name PNNI node address See Table 1-2 SPVC prefix See Table 1-2 Cisco SES PNNI Controller Software Configuration Guide 1-10 Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 Chapter 1 Preparing For Configuration Planning for Card and Line Redundancy Table 1-1 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-1 is a worksheet that you can use to write down ATM address planning information that applies to the switches in your WAN. Table 1-2 is another worksheet that you can use to write down ATM address planning information that applies to a port on a single switch. To complete an address plan, complete one nodal address worksheet for the WAN and an individual port address worksheet for each switch in the WAN. Table 1-2 Port Port Address Worksheet ILMI Prefixes IISP Prefixes and Addresses Static Addresses Cisco SES PNNI Controller Software Configuration Guide Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 1-11 Chapter 1 Preparing For Configuration Guidelines for Creating an IP Address Plan Guidelines for Creating an IP Address Plan The node provides the following interfaces for CLI, SNMP, and CWM access: • Console port (CP) • Maintenance port (MP) • LAN 1 port • ATM interface Basic node configuration and management can be completed by using a local terminal connected to the CP. However, to configure and manage the switch from a LAN connection, a modem connection, or with CWM, you need to define an IP address for the appropriate interface. A typical switch configuration requires either one or two IP addresses for LAN access. When the switch hosts a single PXM card, use just one IP address and assign it to both the boot and LAN IP address options (more on this later in this section). When the switch uses two PXM cards, you can choose to use one or two IP addresses.Figure 1-5 shows a redundant PXM configuration that uses two IP addresses. Using Multiple IP Addresses for Switch Access Slot 1 PXM Slot 2 PXM Boot IP address: A.A.A.A Boot IP address: A.A.A.A Node or disk IP address: B.B.B.B 66395 Figure 1-5 The configuration shown in Figure 1-5 provides the following benefits: • Direct access to the active PXM using address B.B.B.B. • Direct access to the standby PXM card using address A.A.A.A. • The boot code on the standby PXM card can be upgraded without interrupting service on the active PXM card. • You can perform additional procedures in backup boot mode on the standby card without interrupting the active card. These procedures include hard disk formats and file transfers. When different IP addresses are used for the boot and LAN IP addresses, you can manage the active PXM card and the switch using the LAN or disk IP address, which is B.B.B.B in Figure 1-5. You can also access the standby PXM card using the boot IP address. When the same address is used for both the boot and LAN IP addresses, that address can be used only to manage the active PXM card. Note Prior to Release 1., the SES controller supported unique addresses for the boot IP addresses on the PXM cards in slots 1 and 2. This approach required three unique addresses per switch. Beginning with Release 1.1, the boot IP addresses for both slots 1 and 2 must be set to the same IP address. Cisco SES PNNI Controller Software Configuration Guide 1-12 Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 Chapter 1 Preparing For Configuration Guidelines for Creating an IP Address Plan When planning IP addresses for your switch, use the following guidelines: • If the switch has one PXM card, set the boot and LAN IP addresses to the same address. • If the switch has two PXM cards and you want to minimize the number of IP addresses used, set both boot IP addresses and the LAN IP address to the same address. • If the switch has two PXM cards and you want to maximize your control options from remote locations, assign the same boot IP address to each PXM card, and assign a different IP address to the LAN IP address. • Be sure to define the default gateway IP address when defining the boot IP addresses. • To minimize router configuration, choose boot, LAN, and default gateway IP addresses that are all on the same subnet. For instructions on setting boot and LAN IP addresses, refer to “Setting the LAN IP Addresses” in Chapter 2, “Configuring General Switch Features.” Cisco SES PNNI Controller Software Configuration Guide Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 1-13 Chapter 1 Preparing For Configuration Guidelines for Creating an IP Address Plan Cisco SES PNNI Controller Software Configuration Guide 1-14 Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 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 provide detailed information on how to complete the configuration tasks. Configuration Quickstarts This quickstart procedure is provided as an overview and as a quick reference for those who have previously configured an SES controller. Step 1 Command Purpose sysVersionSet version Select the runtime firmware version the switch will use on the PXM card and restart the switch with that firmware. For example: reboot sysVersionSet “001.001.000.060” Note These commands must be entered at the PXM backup boot prompt: pxmbkup>. See “Initializing the Switch,” which appears later in this chapter. Step 2 username Start a management session. password For instructions on starting a session from a terminal or workstation attached to the console port (CP), see “Starting a CLI Management Session After Initialization,” which appears later in this chapter. Note To perform all the procedures in this quickstart procedure, you must log in as a user with SERVICE_GP privileges. The default user with these privileges is service and the default password is serviceuser. For more information on access privileges, see “Configuring User Access,” which appears later in this chapter. Cisco SES PNNI Controller Software Configuration Guide Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 2-1 Chapter 2 Configuring General Switch Features Configuration Quickstarts Step 3 Command Purpose adduser <username> <accessLevel> Configure user access. This step is optional. See “Configuring User Access,” which appears later in this chapter. Related commands: cnfpasswd cnfuser <options> deluser <username> Step 4 cnfname <node name> Configure the switch name. See “Setting and Viewing the Switch Name,” which appears later in this chapter. Step 5 cnfdate <mm/dd/yyyy> Configure the switch date and time. cnftmzn <timezone> See “Viewing and Setting the Switch Date and Time,” which appears later in this chapter. cnftmzngmt <timeoffsetGMT> cnftime <hh:mm:ss> Related commands: dspdate Step 6 cnfpnni-node <options> Set the PNNI node address. See “Setting the PNNI Node Address,” which appears later in this chapter. Step 7 Step 8 bootChange Set the IP address or addresses for LAN access. ipifconfig <options> See “Setting the LAN IP Addresses.”, which appears later in this chapter. cnfspvcprfx <prefix> Set the Soft Permanent Virtual Circuit (SPVC) prefix. Related commands: See “Setting and Viewing the SPVC Prefix,” which appears later in this chapter. dspspvcprfx Step 9 cnfsnmp community [string] Configure SNMP management. cnfsnmp contact [string] See “Configuring for Network Management,” which appears later in this chapter. cnfsnmp location [string] Related commands: dspsnmp Step 10 dspcds Verify the hardware configuration. dspcd See “Verifying the Hardware Configuration,” which appears later in this chapter. cc <slotnumber> Cisco SES PNNI Controller Software Configuration Guide 2-2 Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 Chapter 2 Configuring General Switch Features Initializing the Controller Initializing the Controller After you assemble a new switch, as described in the Cisco Service Expansion Shelf Hardware Installation Guide, Release 1.0, you must initialize the switch before you can configure it. Although PXM cards ship with the latest version of boot firmware on the front card, the runtime firmware cannot be loaded until both front and the back cards have been installed. When you initialize the switch, you are configuring the switch to load a specific runtime firmware version from the PXM hard disk back card. A new switch must be initialized using a console port management session. As shown in Figure 2-1, a console port management session requires a terminal or workstation with a serial connection to the console port (CP) on the PXM back card. Figure 2-1 Workstation Connection to Console Port PXM back card PXM UI-S3 C P M P L A N Serial cable 1 L A N 2 E X T C L K 1 Workstation E X T C L K 2 66396 A L A R M To initialize the controller, use the following procedure. Step 1 Physically connect a terminal or workstation to the PXM UI 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 PXM in either slot 1 or slot 2. Start the terminal, or, if you are using a workstation, start a terminal emulation program and configure it to connect to the controller through the serial port on the workstation. For instructions on configuring the terminal emulation program, refer to the documentation for the program. The default switch configuration supports the following settings: 9600 bps, 8 data bits, no parity, 1 stop bit, no hardware flow control. Cisco SES PNNI Controller Software Configuration Guide Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 2-3 Chapter 2 Configuring General Switch Features Initializing the Controller Step 3 At the workstation, enter the command that connects the terminal emulation program to another computer. Step 4 If the controller power is not on, turn on the controller power as described in the Cisco Service Expansion Shelf Hardware Installation Guide. Note You can connect the workstation to the controller before or after power is applied. If you connect the terminal emulation program to the switch before power is applied, the terminal emulation program displays the controller startup messages. Step 5 Plug a new PXM card into the shelf. If the card comes up as active with the Unknown.1.pxm.a> CLI prompt, skip Steps 6 through 8. If the cards gets stuck at the pxm1> prompt, proceed to step 6. Step 6 Execute the sysClrallcnf command at the pxm1> prompt. This cleans up the old database residing on the card. The card will come up in the pxm1bkup> backup boot prompt. Step 7 When the PXM backup boot prompt appears, define the PXM runtime firmware version by entering the sysVersionSet command as follows: pxm1bkup> sysVersionSet <version> Replace <version> with the version number for the runtime firmware. For example: pxmbkup> sysVersionSet 001.001.000.060 Step 8 Reboot the switch by entering the reboot command as follows: pxm1bkup> reboot During initialization, the switch will appear to boot twice. When the reboot is complete, the switch displays the Login prompt, which indicates that the firmware is loaded and the switch is ready for configuration. Tip Step 9 The sysVersionSet command has failed if the switch reboot process stops and displays the message “Can not open file C:/version” or the message “ Unable to determine size of C:/FW/filename.” If this happens, press Enter to display the backup boot prompt, then refer to “Troubleshooting Upgrade Problems” in “Downloading and Installing Software Upgrades.” If the controller does not display any messages or prompt, press Enter. The Login prompt appears, indicating that the terminal connected successfully to the switch. Step 10 At the Login prompt, enter the user name provided with your controller and press Enter. Step 11 At the Login password prompt, enter the password provided with your controller and press Enter. When login is complete, the controller prompt appears. The switch prompt for PXM cards uses the following format: nodename.slot.cardtype.state> Cisco SES PNNI Controller Software Configuration Guide 2-4 Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 Chapter 2 Configuring General Switch Features Starting a CLI Management Session After Initialization Table 2-1 describes the components in the CLI prompt. Table 2-1 CLI Prompt Components Component Description nodename The nodename is the name of the node. When a new switch starts up, the node name is set to “unknown.” To change the name, see “Setting and Viewing the Switch Name,” which appears later in this chapter. slot The slot indicates which card you are configuring. Configure the switch using the PXM cards in slots 1 and 2. cardtype The cardtype identifies the model of the card, which is the PXM. state The card state is active (a), standby (s), or initialized (i). Cards are labeled as initialized during controller startup. After initialization, the PXM card in the initialized slot becomes active. If a second PXM is installed in the other slot, the active PXM initiates a runtime firmware load on the other slot. After the runtime firmware loads on the nonactive PXM, the card enters standby mode, ready to take control if the active card fails. After you log in, the controller maintains your session for the default period of 10 minutes (600 seconds) after the last keystroke is entered. If the session is idle longer than 600 seconds, the session is terminated. Tip Step 12 To restart an automatically terminated session, press Enter. The switch will prompt you for a login name and password. To change the session time-out period, enter the timeout command as follows: sesone.1.PXM.a > timeout <seconds> 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. Each time a new session is started, the timeout value returns to the default value, 600 seconds. Once you have completed the procedure above, you have established a command line interface (CLI) management session. You can use a CLI management session to configure or monitor the switch. Starting a CLI Management Session After Initialization After initialization, you can terminate and start sessions at any time using the terminal or workstation connection to the CP port, which was described in the previous section. The SES supports IP communications over the following interface types: • Ethernet LAN port on the PXM • Dial-up SLIP port on the PXM • ATM SVCs configured on the switch Cisco SES PNNI Controller Software Configuration Guide Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 2-5 Chapter 2 Configuring General Switch Features Ending a CLI Management Session Tip The switch also supports several other types of management connections, including remote connections. To start a CLI management session at the CP port for switch configuration and monitoring, use the following procedure. Step 1 Turn on the terminal or start the terminal session. For instructions on preparing the terminal and the connection, refer to the previous section, “Initializing the Controller.” Step 2 If the Login prompt does not appear, press Return. The Login prompt comes from the controller and indicates that the terminal has successfully connected to the controller. Step 3 When the Login prompt appears, enter the user name supplied with your controller, and then enter the password for that user name. For example: Login: superuser password: sesone.1.PXM.a > Note To perform most of the procedures in this chapter, you will need to login as a user with SUPER_GP privileges. The default username and password is superuser. The controller does not display the password during login. When login is complete, a prompt appears. The prompt for the PXM cards uses the following format: nodename.slot.cardtype.state> Table 2-1 describes the components in the prompt. After you log in, the controller maintains your session for 10 minutes (600 seconds) after the last keystroke is entered. If the session is idle longer than the configured time-out period, the session is terminated. (To change the timeout period, enter the timeout command, as shown in Step 12 in “Initializing the Controller.”) Tip To restart an automatically terminated session, press Return. The controller will then prompt you for a user name and password. Once you have completed the procedure above, you have established a command line interface (CLI) management session. You can use a CLI management session to configure or monitor the controller. Ending a CLI Management Session CLI management sessions automatically terminate after the configured idle time. The default idle time can be changed with the timeout command. To manually end a CLI management session, enter the bye or exit command. Cisco SES PNNI Controller Software Configuration Guide 2-6 Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 Chapter 2 Configuring General Switch Features Entering Commands at the Switch Prompt Note The bye and exit commands end the CLI session. They do not terminate the terminal session. For instructions on terminating the terminal session, refer to the manuals for your terminal or terminal emulation program. 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 PXM cards installed in slots 1 and 2 of the controller. The switch displays the currently selected card in the switch prompt. For example, the following switch prompt shows that the PXM card in slot 1 is selected: sesone.1.PXM.a > To select another card in the switch, enter the cc command: sesone.1.PXM.a > cc <slotnumber> Replace slotnumber with the slot number of the card you want to manage. Valid slot numbers for the SES controller are 1 and 2. After you execute the cc command to change cards, verify that you are managing the correct card by viewing the slot number that is shown in the switch prompt. The following example shows the prompt for a PXM card in slot 2: sesone.2.PXM.a > If you have trouble executing a command, look at the switch prompt to see if you have selected the correct card for the command. The following example shows the response to an unrecognized command: sesone.1.PXM.a > dsptrkcnf ERR: unknown command: "dsptrkcnf" The dsptrkcnf command is not recognized by a PXM card. Tip The command examples in this guide include the switch prompt so that you can verify which card types support specific commands. Cisco SES PNNI Controller Software Configuration Guide Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 2-7 Chapter 2 Configuring General Switch Features Entering Commands at the Switch Prompt 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. sesone.1.PXM.a > he Available commands -----------------? abortallsaves abortofflinediag abortrev actaudit addaddr addapsln addcon addfltset addlmiloop addpnni-node addpnni-summary-addr addpnport addprfx addserialif addtrapmgr adduser aesa_ping arpadd Type <CR> to continue, Q<CR> to stop: Because the help report is too long to appear on one screen, it is displayed in pages. Press Return to display the next page, or type q and press Return to cancel the report display. Displaying Detailed Command Lists Detailed command lists display the following additional information for each command: Note • Access level required to execute the command • Card state in which the command can be executed • Whether command execution is logged To display detailed command lists, you must establish a session using a username with SERVICE_GP privileges or higher (access privileges are described later in this chapter in “Configuring User Access.”). You can also find this information in the Cisco SES Controller Command Reference, Release 1.1. To enable detailed command lists, enter the clidbxlevel command as shown in the following example: sesone.1.PXM.a > clidbxlevel 1 Value of cliDbxLevel is now 1 Cisco SES PNNI Controller Software Configuration Guide 2-8 Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 Chapter 2 Configuring General Switch Features Entering Commands at the Switch Prompt After you enter this command, you can display detailed command lists by entering the help command as shown in the following example: sesone.1.PXM.a > help Command Access Card Log --------------------------------------------------? ANYUSER A|S|I abortallsaves GROUP1 A + abortofflinediag SERVICE_GP A|S abortrev SERVICE_GP A|S + actaudit SUPER_GP A + addaddr GROUP1 A + addapsln SUPER_GP A + addcon GROUP1 A + addfltset GROUP1 A + addlmiloop SUPER_GP A addpnni-node SUPER_GP A + addpnni-summary-addr SUPER_GP A + addpnport GROUP1 A + addprfx GROUP1 A + addserialif SUPER_GP A addtrapmgr SUPER_GP A + adduser GROUP1 A + aesa_ping SUPER_GP A + arpadd SUPER_GP A|S + Note After you enter the clidbxlevel command, the help command displays detailed reports for that session only. You can disable detailed reports by entering the clidbxlevel 0 command. Every time you start a new session, detailed command lists are disabled. The Access column shows the access level required to execute the command. Access levels are described in “Configuring User Access,” which appears later in this chapter. The Card State column identifies the card states during which the command can be executed. Valid card states are active, standby, and initialized. Cards are labeled as initialized during switch startup. The options that appear in the Card State column are described in Table 2-2. If a plus symbol appears in the Log column, each execution of the command has been logged. If a minus symbol appears in the column, the command has not been logged. Table 2-2 Card State Descriptions Card State Description ACTIVE_ONLY Command is supported when card state is active. ANY_STATE Command is supported when the card state is active or standby. ALLSTATES Command is supported in active, standby, and initialized states. CLIINIT Command is supported while card is in the initialized state. IN_NO_STATE Command is disabled. Cisco SES PNNI Controller Software Configuration Guide Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 2-9 Chapter 2 Configuring General Switch Features Configuring User Access Displaying Command Syntax and Parameters To display the syntax of a command, enter the command without any parameters. The following example shows the syntax report provided by the switch using the addpnport command. sesone.1.PXM.a > addpnport Err: Too few arguments. Syntax: addpnport <portid> shelf.slot:subslot.port:subport -- [shelf.]slot[:subslot].port[:subport0 possible errors are: When a parameter is shown between less-than (<) and greater-than (>) symbols, the parameter represents a variable that must be replaced by a value. The values are described below the command syntax. When the parameter is shown between brackets ([ ]), it is an optional parameter. If you omit an optional parameter, most commands will use the last value defined for the option. If no value has been assigned to an option, the default value is used. Note Some commands, such as dspcd and saveallcnf, do not require parameters, so entering the command without parameters executes the command. When you enter the saveallcnf command, which saves the current switch configuration to a file, the switch prompts you to confirm the save before execution begins. Whenever the switch prompts you to confirm a command, the command you are confirming is likely to change the switch configuration, reduce switch performance, or take a long time to execute. Tip To see the syntax of a command that does not require parameters, enter the command with a parameter you know is incorrect. For example: sesone.1.PXM.a > dspcd jim ERR: Invalid Slot number specified ERR: Syntax: dspcd ["slot_number"] slot number -- optional; Configuring User Access The usernames and passwords supplied with your switch provide access to all switch features. They allow you to add and delete users and to change user passwords. When configuring user access for the switch, consider the following recommendations: • Change the default passwords provided with your switch. These passwords are published on the Cisco website and enable anyone with local or remote network access to configure and manage your switch. • Share the usernames and passwords with only one or two people. • If usernames and passwords become common knowledge during the switch installation and configuration, change the passwords. • If additional users need to access the controller, create usernames and passwords below the top levels so that these users cannot access or modify the top-level user information. Cisco SES PNNI Controller Software Configuration Guide 2-10 Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 Chapter 2 Configuring General Switch Features Configuring User Access The following sections describe how to add users, change passwords for existing users, delete users, and recover the user cisco password. Adding Users The controller supports up to 50 users. When you add users, you must specify the following for each user: • user name • password • access level The user name and password identify the user and determine the user access level for switch management. An access level must be assigned to a user when the user is added to the switch. The access levels listed in Table 2-3 are used throughout this guide to indicate the level of access required to execute a command or complete a procedure. These access levels are also called access privileges. If a user has access privileges at a lower level than a command requires, the user cannot execute the command. If the user has access privileges at the level required or at a higher level, the user can execute the command. Table 2-3 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 <cisco>. The default password for user cisco is <cisco>. Again, Cisco recommends that you change the default passwords when you install a switch. Users at the CISCO_GP access level can add users, delete users, change passwords, and change access levels for users at the following levels: SERVICE_GP, SUPERUSER_GP, GROUP1 to GROUP 5, and ANYUSER. SERVICE_GP This access level allows access to commands that update switch firmware, save and restore the switch configuration, and enable debugging. This access level also provides access to all commands in all lower access levels: SUPERUSER_GP, GROUP1, and ANYUSER. The default username is service. The default password is <serviceuser>. Users at the service access level can add users, delete users, change passwords, and change access levels for users at the following levels: SUPERUSER_GP, GROUP1 to GROUP5, and ANYUSER. SUPER_GP This access level allows users to configure switch level parameters such as the node name, date, and interface IP addresses. Users at this level can also enable traces. This access level also provides access to all commands in all lower access levels: GROUP 1 to GROUP 5 and ANYUSER. The default username is superuser, and the default password is <superuser>. Users at the superuser access level can add users, delete users, change passwords, and change access levels for users at the following levels: GROUP1 to GROUP5 and ANYUSER. Cisco SES PNNI Controller Software Configuration Guide Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 2-11 Chapter 2 Configuring General Switch Features Configuring User Access Table 2-3 User Access Levels (continued) Access Level Descriptions GROUP1 This access level allows users to configure line and port level parameters and create SPVCs and Soft Permanent Virtual Paths (SPVPs). This access level also provides access to all commands at the GROUP 2 to GROUP 5 and ANYUSER access levels. No default username and password is provided for this access level. Users at the GROUP1 access level can add users, delete users, and change passwords for users at the GROUP 2 to GROUP 5 and ANYUSER access levels. GROUP2 through GROUP5 In this release, the GROUP2, GROUP3, GROUP4, and GROUP5 access levels provide the same level of control as the ANYUSER access level. No CLI commands are assigned to any of these access levels. No default username and password is provided for these access levels. ANYUSER This access level allows users to run display and status commands that display the switch configuration and operational status. No default username and password is provided for this access level. 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 adduser command after the switch prompt: sesone.1.PXM.a >adduser <username> <accessLevel> Enter the username using 1 through 12 alphanumeric characters. Specify the access level by entering one of the levels defined in Table 2-3. Note The access levels are case-sensitive and must be entered as shown in Table 2-3. Also, you cannot add users at access levels that are equal to or above your own access level. If you enter the command correctly, the switch prompts you for a password. Step 3 Enter a password, using 5 to 15 characters. Step 4 When prompted, enter the password a second time to validate the previous entry. This completes the addition of the new user. Step 5 Tip Step 6 To display the new user in a list of all users, enter the dspusers command. To determine which commands are available at a particular access level, log in to the switch as a user at that access level, then enter the help command. To test the username, enter the bye command, then log in as the new user. Cisco SES PNNI Controller Software Configuration Guide 2-12 Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 Chapter 2 Configuring General Switch Features Setting and Viewing the Switch Name Tip If you forget which username you used to log in, enter the whoami command. This command displays the username, access level, and access method (for example, Telnet) for the current session. Setting and Viewing the Switch Name The switch name identifies the switch you are working on, which is important when you are managing multiple switches. The current switch name appears in the CLI prompt when you are managing a PXM cards and service modules. To change the switch name, use the following procedure. Step 1 Establish a configuration session using a user name with SUPER_GP privileges or higher. Step 2 Enter the cnfname command after the switch prompt: unknown.1.PXM.a > cnfname <node name> Enter up to 8 alphanumeric characters for the new node name, and because the node name is case-sensitive, be sure to use the correct case. For example: unknown.8.PXM.a > cnfname sesone This node name will be changed to sesone. Please Confirm cnfname: Do you want to proceed (Yes/No)? y cnfname: Configured this node name to sesone Successfully. sesone.1.PXM.a > The new name appears immediately in the next CLI prompt. Warning The SES controller must have its own unique node name. It cannot have the same node name as the BPX Switch to which it is attached. If the SES controller and the BPX Switch have the same node name, the SES will not boot up. 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. Step 2 To view the current switch date and time, enter the dspdate command after the switch prompt: sesone.1.PXM.a > dspdate Step 3 To change the switch date, enter the cnfdate command as follows: sesone.1.PXM.a > cnfdate <mm/dd/yyyy> Cisco SES PNNI Controller Software Configuration Guide Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 2-13 Chapter 2 Configuring General Switch Features Setting the LAN IP Addresses Step 4 To change the time zone, enter the cnftmzn command as follows: sesone.1.PXM.a > cnftmzn <timezone> Replace <timezone> with GMT for Greenwich Mean Time, EST for Eastern Standard Time, CST for Central Standard Time, MST for Mountain Standard Time, PST for Pacific Standard Time. Options 2 through 5 are for switches located in the Western Hemisphere. If your switch is located outside the Western Hemisphere, select GMT and use the next step to specify an offset from GMT. Step 5 To configure an offset from GMT, enter the cnftmzngmt command as follows: sesone.1.PXM.a > cnftmzngmt <timeoffsetGMT> Replace <timeoffsetGMT> with the offset in hours from GMT. Enter a number from -12 to +12. Step 6 To change the switch time, enter the cnftime command as follows: sesone.1.PXM.a > cnftime <hh:mm:ss> Replace <hh> with the hour of the day (0 to 23), <mm> with the minute of the hour (0 to 59), and <ss> with the number of seconds in the minute (0 to 59). Step 7 To verify the new date and time settings, enter the dspdate command. 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 “Guidelines for Creating an IP Address Plan" in Chapter 1. Note The switch also supports IP addresses for dial-in and ATM in-band access. Setting the Boot IP Address The boot IP address is the LAN port IP address that a PXM card uses when it first starts up. If the switch cannot fully start, this IP address can be used to access the switch in boot mode. When the switch is properly configured (with different addresses set for the boot IP and LAN IP addresses), the boot IP address can also be used to access the standby PXM card directly, while the disk IP address can be used to access the active PXM. Note Because the LAN IP address is stored on the PXM hard disk and is not used until after the runtime software loads, Cisco recommends that the boot IP address be set in every switch. This enables switch management over Ethernet when the boot software has loaded. Cisco SES PNNI Controller Software Configuration Guide 2-14 Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 Chapter 2 Configuring General Switch Features Setting the LAN IP Addresses To set the boot IP address, enter the bootChange command, which allows you to also define a remote boot location, a default gateway IP address, and a username and password for the remote boot location. Step 1 Establish a configuration session using a user name with SUPER_GP privileges or higher. Step 2 Enter the bootChange command as shown in the following example. sesone.1.PXM.a > bootChange '.' = clear field; boot device '-' = go to previous field; ^D = quit : lnPci In this example, the switch is waiting for you to take action on the boot device option. Enter a period <.> to clear the current value (lnPci), enter minus <-> to go back to the previous field (although this is the first of 14 fields), or press Return to accept the current value and display the next option. 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.1 user (u) : ftp password (pw) (blank = use rsh): flags (f) : 0x0 target name (tn) : pxm-1 startup script (s) : other (o) : Note Step 3 The only two options that must be set to support the boot IP address are inet on ethernet (e) and gateway inet. Accept, clear, or change option values as necessary until the inet on ethernet option appears. Table 2-4 defines the options that you can change. Table 2-4 bootChange Command Option Descriptions Option Description boot device Selects an external server as the boot source when the boot or runtime software is not found on the PXM hard disk. processor number Do not change this option. host name Identifies an external server that has switch boot and runtime software. file name Defines the path and filename of the runtime software on a remote server. inet on ethernet Selects the boot IP address and network mask for the PXM you are configuring. (This PXM is identified in the switch prompt.) Enter the address and mask in the format: a.b.c.d:w.x.y.z, where a.b.c.d is the IP address and w.x.y.z is the network mask. Cisco SES PNNI Controller Software Configuration Guide Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 2-15 Chapter 2 Configuring General Switch Features Setting the LAN IP Addresses Table 2-4 Step 4 bootChange Command Option Descriptions (continued) Option Description inet on backplane Do not change this option. host inet Defines the IP address for the external server that has boot and runtime software for the switch. gateway inet Identifies the IP address for the default gateway on the subnet that hosts the switch. user Defines a username that can be used for FTP access to the boot and runtime software files on a remote server. ftp password 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. startup script Do not change this option. other Do not change this option. Set the inet on ethernet (e) option to the boot IP address value you want to use. The following example shows how the command appears when a new value has been entered: inet on ethernet (e) : 172.29.52.88 172.29.52.8:255.255.255.0 The 172.29.52.88 address appeared as part of the prompt. If no address had been previously defined, no text would appear after the colon. In this example, 172.29.52.188 is the new boot IP address, and 255.255.255.0 is the new network mask. Step 5 Set the gateway inet option to the IP address for the default gateway on the subnet that hosts the switch. Step 6 Accept, clear, or change the values as necessary until the switch prompt reappears. Step 7 To verify the new values you have set, enter the bootChange command and press Enter for each of the 14 values. Note Prior to Release 1.1, BPX SES PNNI Controller software releases supported unique addresses for the boot IP addresses on the PXM cards in slots 1 and 2. This approach required three unique Ethernet IP addresses per switch. Beginning with Release 1.1, the bootChange command automatically sets the boot IP addresses for both slots 1 and 2 to the same IP address. Cisco SES PNNI Controller Software Configuration Guide 2-16 Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 Chapter 2 Configuring General Switch Features Setting the LAN IP Addresses Setting the LAN or Disk IP Address A local LAN connection extends switch management to all workstations that have connectivity to the LAN to which the switch is connected. Figure 2-2 shows the hardware required for a local LAN connection. Figure 2-2 Hardware Required for Local LAN Connections Hub or router PXM UI-S3 C P M P L A N 1 Ethernet cable L A N 2 E X T C L K 1 Workstation E X T C L K 2 44372 A L A R M Note The PXM UI-S3 card shown in Figure 2-2 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 PXM LAN port, you must first assign an IP address to the LAN port. The LAN or disk IP address is the IP address for the Ethernet LAN port on the active PXM. The LAN IP address is also called the Disk IP address because it is stored on the PXM hard disk. Note To enable LAN connectivity to the active PXM card, you must configure a LAN IP address. The boot IP address cannot be used to access an active PXM card. If you want to assign only one IP address for LAN access, assign the same IP address to the boot and LAN IP addresses. Tip The Disk IP address for the LAN Port is significant because it is stored on the hard disk and is not available until the runtime software is loaded on the PXM card and the card is active. To access the LAN port over Ethernet when a PXM is operating in boot or standby mode, you must use the Boot IP address. Cisco SES PNNI Controller Software Configuration Guide Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 2-17 Chapter 2 Configuring General Switch Features Setting the LAN IP Addresses The LAN IP address can be set to match the boot IP address when only one IP address is available, or it can be set to a unique address to support access to the standby PXM during regular operation. For more information on how the boot and LAN IP addresses are used, see “Guidelines for Creating an IP Address Plan” in Chapter 1. To set the IP address, use the ipifconfig command as described in the following procedure. Step 1 Establish a CLI management session using a username with SUPER_GP privileges. Both the default user name and password for this level are superuser. Step 2 Verify that the IP address is not already configured by entering the dspipif command: sesone.1.PXM.a > dspipif lnPci0 Note If you omit the lnPci0 option, the switch displays the configuration for all switch IP interfaces: the ATM interface (atm0), the PXM LAN port interface (lnPci0), and the PXM maintenance port interface (sl0). The address for each interface must be unique. In the IP Interface Configuration Table, look for an Internet address entry under the lnPci entry. If an IP address is configured, you can use that address and skip the rest of this procedure. However, if the address has not been entered or is incompatible with your network, you must configure a valid IP address as described in the next step. Step 3 To set the IP address for the LAN port, enter the ipifconfig command using the following format: sesone.1.PXM.a > ipifconfig lnPci0 <IP_Addr> <netmask Mask> Replace <IP_Addr> with the IP address you want this port to use, and replace <Mask> with the network mask used on this network. Note Step 4 Tip There are other options for the ipifconfig command, and you can set one or more options simultaneously. Any options you do not define in a command remain unchanged. For more information on this command, refer to Cisco SES Controller Command Reference, Release 1.1. Verify that the IP address changes by entering the dspipif command. 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. Cisco SES PNNI Controller Software Configuration Guide 2-18 Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 Chapter 2 Configuring General Switch Features Setting the LAN IP Addresses Setting the Dial-Up Interface Address Before you can manage the switch using the dial-up interface, you must first assign an IP address to the maintenance port on the switch. This maintenance port is located on the PXM back card. For instructions on physically connecting a modem to this maintenance port, refer to the Cisco Service Expansion Shelf Hardware Installation Guide, Release 1.0. To configure an IP address on the switch maintenance port, use the following procedure. Step 1 Establish a configuration session through a directly attached terminal. Step 2 Verify that the IP address for the ATM interface is not already configured by entering the dspipif command: spirita.1.PXM.a> dspipif sl0 Note If you omit the sl0 option, the switch displays the configuration for all switch IP interfaces: the ATM interface (atm0), the PXM LAN port interface (lnPci0), and the PXM maintenance port interface (sl0). Each interface must have its own unique address. 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.) If an IP address is configured, you can use that address and skip the rest of this procedure. However, if the address has not been entered or is incompatible with your network, you must configure a valid IP address as described in the next step. Step 3 To set the IP address for the maintenance port, enter the ipifconfig command using the following format: spirita.1.PXM.a> ipifconfig sl0 <IP_Addr> [netmask Mask] [broadcast <broad_addr>] Replace IP_Addr with the IP address you want this port to use, and replace Mask with the network mask used on this network. Replace <broad_addr> with the interface broadcast address. Tip Cisco recommends that you use the same subnet for all IP addresses defined on all SESs. This simplifies router configuration. Note There are other options for the ipifconfig command, and you can set one or more options simultaneously. Any options you don’t define in a command remain unchanged. After you complete this procedure, the switch is ready for configuration through the maintenance port. Cisco SES PNNI Controller Software Configuration Guide Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 2-19 Chapter 2 Configuring General Switch Features Setting the LAN IP Addresses 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. Before you can establish a CLI Telnet session, you must set up the hardware for your access method and assign the appropriate boot and LAN IP addresses. After the LAN IP interface has been configured and a physical path has been established to the SES controller, you can start a CLI session using a workstation with a Telnet client program. To establish a CLI management session, use the following procedure. Step 1 Start the Telnet client program on a LAN workstation with a command similar to the following example: C:>telnet ipaddress Replace ipaddress with the appropriate LAN IP address as follows: • Active PXM card: Enter the LAN IP address. • Standby PXM card: Enter the Boot IP address (requires separate addresses for boot and LAN IP addresses). • PXM in backup boot mode: Enter the Boot IP address. Note Tip Step 2 The Telnet program on your workstation may require a different start up and connection procedure. For instructions on operating your Telnet program, refer to the documentation for that product. If you have trouble accessing the switch from a workstation, use the PING program at the workstation to test communications. For example, ping 10.10.10.1. You can also 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. If the Login prompt does not appear, press Enter. The Login prompt comes from the switch and indicates that the workstation has successfully connected to the switch. 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 following example: sesone.1.PXM.a > Cisco SES PNNI Controller Software Configuration Guide 2-20 Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 Chapter 2 Configuring General Switch Features Setting and Viewing the SPVC Prefix Setting and Viewing the SPVC Prefix The SPVC node prefix is the ATM prefix that PNNI advertises for all SPVCs and Soft Permanent Virtual Paths (SPVP) on this node. The ATM address for each SPVC and SPVP is the combination of the SPVC prefix and a port identification number. You can configure one SPVC node prefix per node. The default SPVC prefix is set to match the first 13 bytes of the default ATM address. In most cases, if you change the PNNI node address, you should change the SPVC prefix to match the new ATM address. Note Although the SPVC prefix is set to match the first 13 bytes of the PNNI node address by default, changing either the PNNI node address or the SPVC prefix has no effect on the other setting. If the PNNI node ATM address and the SPVC prefix do not match, the switch advertises both prefixes instead of just one, and this advertising takes additional bandwidth. To set the SPVC prefix, use the following procedure. Step 1 Establish a configuration session using a user name with SUPER_GP privileges or higher. Step 2 Use the dspspvcprfx command to display the current SPVC prefix: sesone.1.PXM.a > dspspvcprfx The switch response is similar to the following example: sesone.1.PXM.a > dspspvcprfx SPVC Node Prefix: 47.00918100000000001a531c2a Tip Step 3 If the SPVC prefix begins with 47.009181000000, the SPVC prefix is probably set to the default value. To display the current PNNI node address, enter the dsppnni-node command. To change the SPVC prefix, enter the cnfspvcprfx command as follows: sesone.1.PXM.a > cnfspvcprfx -prfx <prefix> Replace <prefix> with the 13-byte prefix you want to use. Note Step 4 Note The SPVC node prefix for each node must be unique within the network. Verify the correct entry of the prefix by entering the dspspvcprfx command. You can change the SPVC prefix only when no SPVCs or SPVPs have been defined. Once an SPVC has been defined, you must delete all SPVCs before you can change the SPVC prefix. Cisco SES PNNI Controller Software Configuration Guide Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 2-21 Chapter 2 Configuring General Switch Features Configuring for Network Management Configuring for Network Management The SES controller controller includes a Simple Network Management Protocol (SNMP) agent that you can configure for communications with a network management station such as Cisco WAN Manager (CWM) or a third-party SNMP manager. When configured for SNMP management, the controller accepts configuration commands from management stations and sends status and error messages to the management station. Typically, CWM operates on a workstation that is connected to an IP network, and CWM uses IP over ATM connections to connect to the SES controller controllers. To support the auto-discovery feature of CWM, ILMI should be brought up on all links between the CWM workstation and the switches it will manage. The rest of this section describes the following: • Configuring the SNMP Trap Source IP Address • Configuring the SNMP Manager Destination IP Address • Configuring the Community String and General Switch Information Configuring the SNMP Trap Source IP Address The SNMP trap source IP address is sent to SNMP managers, such as CWM, in the SNMP trap Packet Data Unit (PDU). This IP address identifies the source of the trap and can be used by the SNMP manager to access the remote SNMP agent. This address must be configured to enable communications with an SNMP manager. Note If the trap manager IP address is not set, CWM will reject traps from the switch. The switch can communicate with an SNMP manager over the LAN or ATM IP interfaces. In some installations, the LAN IP interface will be used for CLI management and the ATM IP interface will be used for SNMP management. When you select the SNMP trap manager IP address, you must select the correct interface address. To define the SNMP trap manager IP address, enter the cnftrapip command as follows: sesone.1.PXM.a > cnftrapip <ipaddress> The IP address should match either 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. Configuring the SNMP Manager Destination IP Address The SNMP Manager destination IP address identifies the IP address of an SNMP manager, such as CWM, to which the switch sends SNMP traps. If you are using CWM to manage the switch, CWM will automatically configure the destination IP address on the switch. If you are using another SNMP manager, you can configure the destination IP address with the addtrapmgr command as follows: sesone.1.PXM.a > addtrapmgr <ipaddress> <port> Cisco SES PNNI Controller Software Configuration Guide 2-22 Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 Chapter 2 Configuring General Switch Features Configuring for Network Management Replace ipaddress with the IP address of the SNMP manager, and replace port with the UDP port number assigned to that manager. For more information on the SNMP manager IP address, refer to the SNMP manager documentation. Configuring the Community String and General Switch Information To configure information about a switch in the local SNMP agent, use the following procedure. Step 1 Establish a configuration session using a user name with SUPER_GP privileges or higher. Step 2 To define the SNMP password for network management, enter the following command: sesone.1.PXM.a > cnfsnmp community [password] If the password parameter is not specified, the password becomes <private>. Step 3 To define a text string that identifies the location of the switch to the management station, enter the following command: sesone.1.PXM.a > cnfsnmp location [location] If the location parameter is not specified, the location is set to null (no text). The location value is sent to SNMP managers when information is requested about the sysLocation MIB object. Step 4 To define a text string that identifies a person to contact regarding issues with this switch, enter the following command: sesone.1.PXM.a > cnfsnmp contact [contact] If the contact parameter is not specified, the location is set to null (no text). The contact value is sent to SNMP managers when information is requested about the sysContact MIB object. Step 5 To display the SNMP agent configuration, enter the dspsnmp command. The command display appears similar to the following example: sesone.1.PXM.a > dspsnmp sesone BPX8600 Community: System Location: System Contact System Rev: 02.01 Dec. 28, 2000 20:37:18 PST Node Alarm: NONE private Pubs Lab Jim Cisco SES PNNI Controller Software Configuration Guide Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 2-23 Chapter 2 Configuring General Switch Features Verifying the Hardware Configuration Verifying the Hardware Configuration Before you can configure your switch, you need to collect information about the cards and software installed on the switch. You need to enter this information during the various configuration tasks. Table 2-5 shows the information you need and serves as a worksheet where you can enter this information. Table 2-5 Card Hardware Configuration Worksheet Front Card Type Upper Back Card Primary Software Lower Back Card Version Boot Firmware Version Redundant Slot Redundancy Type 1 2 The following procedure describes how to display the configuration information you need to enter in this table. It also describes how to verify that the correct upper and lower back cards are installed for each front card. Step 1 Establish a configuration session at any access level. Step 2 To display a list of all the cards installed in the switch, enter the dspcds command after the switch prompt: sesone.1.PXM.a > dspcds The switch displays a report similar to the following example: sesone.1.PXM.a> dspcds sesone System Rev: 01.01 Aug. 23, 2001 18:09:12 PST Chassis Serial No: SCA050209X1 Chassis Rev: A0 GMT Offset: -8 Node Alarm: CRITICAL Card Front/Back Card Alarm Redundant Redundancy Slot Card State Type Status Slot Type -----------------------------------01 02 03 04 05 06 Step 3 Active/Active Empty Resvd/Empty Empty Empty Empty Empty PXM1_OC3 ----------- CRITICAL MAJOR --------- 02 01 --------- PRIMARY SLOT SECONDARY SLOT --------- In the Hardware Configuration Worksheet (see Table 2-5), write down the following information for each card: • Front card type (from Card Type column) • Redundant slot • Redundancy type Cisco SES PNNI Controller Software Configuration Guide 2-24 Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 Chapter 2 Configuring General Switch Features Verifying the Hardware Configuration Step 4 For each slot in which a card is installed, complete the following tasks: a. Enter the dspcd command as follows: sesone.1.PXM.a > dspcd slot The dspcd command displays information that is unique to a particular card. For PXM cards, the switch displays a report similar to the following example: sesone.1.PXM.a> dspcd 1 SES_LA System Rev: 01.01 SES-CNTL Slot Number 1 Redundant Slot: 2 Front Card ---------Inserted Card: PXM1_OC3 Reserved Card: PXM1_OC3 State: Active Serial Number: SBK043200VK Prim SW Rev: 1.1(60.16)P2 Sec SW Rev: 1.1(60.16)P2 Cur SW Rev: 1.1(60.16)P2 Boot FW Rev: 1.1(60.16)A 800-level Rev: B0 800-level Part#: 800-06454-03 CLEI Code: BAA6CCVCAA Reset Reason: On Power up Card Alarm: CRITICAL Failed Reason: None Miscellaneous Information: Upper Card ---------- Lower Card ---------- UIA BackCard UIA BackCard Active SBK041200W7 --------A0 800-03688-01 BAI9Y00AAA SMFIR_4_OC3 SMFIR_4_OC3 Active SBK05070188 --------E1 800-05351-01 BA2IKNHBAA Type <CR> to continue, Q<CR> to stop: SES_LA System Rev: 01.01 SES-CNTL Crossbar Slot Status: Aug. 23, 2001 18:10:28 PST Node Alarm: CRITICAL Aug. 23, 2001 18:10:28 PST Node Alarm: CRITICAL No Crossbar Alarm Causes -----------NO ALARMS Note b. The dspcd and dspcds commands are very similar, but they produce different reports. The dspcd command displays information about a specific card. The dspcds command displays summary information for all cards in the switch. In the Hardware Configuration Worksheet (see Table 2-5), write down the following information for each card: – Upper back card type, which appears in the Upper Card column of the Inserted Card row. – Lower back card type, which appears in the Lower Card column of the Inserted Card row. – Primary software version, which appears in the Prim SW Rev row. – Boot firmware version, which appears in the Boot FW Rev row. Cisco SES PNNI Controller Software Configuration Guide Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 2-25 Chapter 2 Configuring General Switch Features Verifying the Hardware Configuration Tip Step 5 Another way to display a detailed report on a card is to use the cc command to select the card, then use the dspcd command without a slot number. However, the preferred method is to use the dspcd command with a slot number because this method can display information on a card when card errors prevent access through the cc command. After you have entered the required information for all cards in the Hardware Configuration Worksheet (see Table 2-5), use Table 2-6 to verify that each card is installed in a slot that supports that card type. Verify that the correct back cards are installed for the corresponding front cards. If any of the cards are installed incorrectly, refer to the Cisco Service Expansion Shelf Hardware Installation Guide for instructions on installing the cards correctly. Note The locations or slots where the upper and lower back cards are installed are also called bays. In an SES controller, the bays are turned sideways, and the cards are installed in left and right bays. The upper back cards reside in the left bay, and the lower back cards reside in the right bay. Table 2-6 Valid Card Installation Options Front Card Type PXM Description and Part Number Processor Switch Module Back Card Types Valid Back Card Locations Valid Slot Numbers UI Stratum-3 Left 1 and 2 OC-3 DS3 Cisco SES PNNI Controller Software Configuration Guide 2-26 Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 C H A P T E R 3 Provisioning Communication Links This chapter describes how to configure the communications links that connect the SES controller to the BPX, and how to configure the BPX trunks and lines the SES controller will control. This chapter explains how to provision the following types of links and connections on the SES controller Release 1.1 switch: • SES controller uplink • PNNI trunks • AutoRoute Trunks • PNNI UNI ports • Soft Permanent Virtual Circuits (SPVCs) • Soft Permanent Virtual Paths (SPVPs) • MGX 8850 Release 1 feeder PNNI trunks • Interim Inter-switch Protocol (IISP) links • ATM Inter-Network Interface (AINI) links • Switched Virtual Circuits (SVCs) The configuration differences between these different types of connections are often as simple as an additional command or a different set of command options. To eliminate redundancy and help experienced users complete configuration procedures quickly, this chapter uses configuration quickstarts and task descriptions to explain how to configure connections. The first time you configure a connection type, use the quickstart procedure to see the order of tasks to complete, and then read the task descriptions for detailed instructions. As you get more experience configuring connections, you can look up fewer tasks. Tips Remember that you can get information on most commands by entering the command without parameters. Experienced users can usually configure connections using just the quickstarts and the online help. Note For all SES controller commands in this chapter, refer to the Cisco SES PNNI Controller Software Command Reference, Release 1.1 for detailed information. The BPX CLI commands are documented in detail in the Cisco WAN Switching Command Reference, Release 9.3. Cisco SES PNNI Controller Software Configuration Guide Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 3-1 Chapter 3 Provisioning Communication Links Quickstart Procedures for Provisioning Links on the SES Controlled BPX Note Before you start configuring ATM connections, complete the general switch configuration as described in Chapter 2 “SES Controller Interface Connections and Initial Configuration.” Some of the procedures described in this chapter will not work if the SES controller has not been set up properly. Quickstart Procedures for Provisioning Links on the SES Controlled BPX The quickstart procedures in this section provides a summary of the tasks required to provision links on the SES. These procedures are provided as an overview and as a quick reference for those who have previous experience provisioning links on the SES. SES Controller Uplink Configuration Quickstart The SES controller uplink is the communications link between the VSI master in the SES controller and the VSI slave on a BXM card. This link must be configured before the SES controller can provide PNNI services to the trunks and lines that lead from BXM cards to other switches and to CPE. The quickstart procedure in this section provides a summary of the tasks required to configure an SES controller uplink. This procedure is provided as an overview and as a quick reference for those who have already configured the SES. Command Purpose Step 1 username <password> Start a configuration session on the BPX to which the SES controller is connected. Step 2 uptrk <slot.port> Bring up the trunk that leads to the SES controller. Related commands: See “Bringing Up a BXM Trunk”, which appears later in this chapter. cnftrk dsptrks Step 3 cnfvsiif <slot.port> <sct_ID> Related commands: Define the SES controller trunk as a VSI interface and set the Service Class Template to 3. See “Assigning a Service Class Template to a VSI Interface”, which appears later in this chapter. dspsct dspvsiif <slot.port> Step 4 cnfrsrc <slot.port> <options> Related commands: Enable a VSI partition and configure resources for the trunk. You can accept the default values for most options. The required options are the partition number and e, which enables the VSI partition. dsprsrc <slot.port> Note Do not set the VPI to 3. See “Enabling a Partition and Configuring Resources for a Trunk”, which appears later in this chapter. Cisco SES PNNI Controller Software Configuration Guide 3-2 Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 Chapter 3 Provisioning Communication Links Quickstart Procedures for Provisioning Links on the SES Controlled BPX Command Purpose Step 5 addshelf <slot.port> x Configure the trunk to support the external SES controller shelf. Step 6 addctrlr <slot.port> <options> Configure the trunk to support the SES controller as a VSI master. Related commands: dsptrks Step 7 username <password> dsplmilink Start a configuration session on the SES controller and verify BPX connectivity. PNNI Trunk Configuration Quickstart The SES controller can manage PNNI trunks between a BXM card port on the SES controlled BPX and the following: • A BXM port on another SES controlled BPX • An AXSM port on a Cisco MGX 8850 switch The quickstart procedure in this section provides a summary of the tasks required to configure PNNI trunks to PNNI controlled BXM and AXSM ports. This procedure is provided as an overview and as a quick reference for those who have already configured the SES. Command Purpose Step 1 username <password> Start a configuration session on the BPX to which the SES controller is connected. Step 2 uptrk <slot.port> Bring up the trunk that leads to a remote BXM or AXSM. Related commands: See “Bringing Up a BXM Trunk”, which appears later in this chapter. cnftrk<slot.port> dsptrks Step 3 cnftrk<slot.port> Configure the trunk that leads to a remote BXM or AXSM. Note Related commands: dsptrk <slot.port> Step 4 cnfvsiif <slot.port> <sct_ID> Related commands: Set the Protocol By The Card option to Yes. See “Configuring a BXM Trunk”, which appears later in this chapter. Define the trunk as a VSI interface and set the Service Class Template to 3. See “Assigning a Service Class Template to a VSI Interface”, which appears later in this chapter. dspsct dspvsiif <slot.port> Cisco SES PNNI Controller Software Configuration Guide Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 3-3 Chapter 3 Provisioning Communication Links Quickstart Procedures for Provisioning Links on the SES Controlled BPX Step 5 Command Purpose cnfrsrc <slot.port> <options> Enable a VSI partition and configure resources for the trunk. Related commands: See “Enabling a Partition and Configuring Resources for a Trunk”, which appears later in this chapter. dsprsrc <slot.port> Step 6 cnfvsipart <slot.port> <partition_id> y Enable ILMI on the trunk. Related commands: See “Enabling ILMI on a Trunk”, which appears later in this chapter. dspvsipartcnf <slot.port> Step 7 username <password> Start a configuration session on the SES controller . Step 8 dnpnport <portid> Configure the VSI trunk for PNNI signalling. cnfpnportsig <options> See “Selecting the Port Signaling Protocol,” which appears later in this chapter. uppnport <portid> Related commands: dsppnports dsppnport <portid> dsppnportsig <portid> Step 9 dsppnni-link dsppnni-neighbor When both ends of the trunk are configured for PNNI signalling, verify the PNNI communications between the two ends. In the dsppnni-link report, there should be an entry for the port for which you are verifying communications. The Hello state reported should be twoWayInside or twoWayOutside, and the Remote node ID should display the remote node ATM address after the second colon. See “Verifying PNNI Trunk Communications,” which appears later in this chapter. Cisco SES PNNI Controller Software Configuration Guide 3-4 Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 Chapter 3 Provisioning Communication Links Quickstart Procedures for Provisioning Links on the SES Controlled BPX AutoRoute Trunk Configuration Quickstart AutoRoute is needed to provide IP connectivity, Time of Date, and Network Clocking for the SES node, it is essential to add an AutoRoute partition to a trunk, even if you will not implement an AutoRoute PVC service. The quickstart procedure in this section provides a summary of the tasks required to configure AutoRoute trunks. This procedure is provided as an overview and as a quick reference for those who have already configured the SES. Command Purpose Step 1 username <password> Start a configuration session on the BPX to which the SES controller is connected. Step 2 uptrk <slot.port> Bring up the trunk that leads to a remote BXM or AXSM. Related commands: See “Bringing Up a BXM Trunk”, which appears later in this chapter. cnftrk<slot.port> dsptrks Step 3 cnftrk<slot.port> Related commands: dsptrk <slot.port> Configure the trunk that leads to a remote BXM. Note Set the Protocol By The Card option to No. Note When the AutoRoute service is added to the trunk, VPI = 0 and 1 is reserved for AutoRoute. The available VPI for VSI (or PNNI) starts from VPI = 2. See “Configuring a BXM Trunk”, which appears later in this chapter. PNNI UNI Port Configuration Quickstart The quickstart procedure in this section provides a summary of the tasks required to configure a UNI port on the SES. This procedure is provided as an overview and as a quick reference for those who have already configured the SES. Command Purpose Step 1 username <password> Start a configuration session on the BPX to which the SES controller is connected. Step 2 upln <slot.port> Bring up the line that leads to CPE. Related commands: See “Bringing Up a BXM Line”, which appears later in this chapter. dsplns dspln <slot.port> cnfln <slot.port> Cisco SES PNNI Controller Software Configuration Guide Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 3-5 Chapter 3 Provisioning Communication Links Quickstart Procedures for Provisioning Links on the SES Controlled BPX Step 3 Command Purpose addport <slot.port> Add a port to the line. Related commands: See “Adding a Port to a BXM Line”, which appears later in this chapter. dspports dspport <slot.port> Step 4 upport <slot.port> Related commands: Bring up the port. See “Bringing Up a Port on a BXM Line”, which appears later in this chapter. dspports dspport <slot.port> Step 5 cnfport <slot.port> <options> Configure the port. Note Related commands: Step 6 Enable ILMI and set the Protocol By The Card option to Yes. dspports dspport <slot.port> See “Configuring a BXM Port”, which appears later in this chapter. cnfvsiif <slot.port> <sct_ID> Define the port as a VSI interface and set the Service Class Template to 2. Related commands: See “Assigning a Service Class Template to a VSI Interface”, which appears later in this chapter. dspsct dspvsiif <slot.port> Warning Step 7 cnfrsrc <slot.port> <options> Related commands: The default SCT is 1 (for MPLS). The SES does not support MPLS. If the SCT is set to 1 (MPLS) on an SES switch, the trunk or port will not become active. Enable a VSI partition and configure resources for the line. See “Enabling a Partition and Configuring Resources for a Line”, which appears later in this chapter. dsprsrc <slot.port> Step 8 username <password> Start a configuration session on the SES controller. Cisco SES PNNI Controller Software Configuration Guide 3-6 Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 Chapter 3 Provisioning Communication Links Quickstart Procedures for Provisioning Links on the SES Controlled BPX Step 9 Command Purpose dnpnport <portid> Configure the VSI trunk for PNNI signaling. The default signaling protocol is UNI 3.1, so this step is not required when you plan to use UNI 3.1 signaling. cnfpnportsig <options> uppnport <portid> See “Selecting the Port Signaling Protocol,” which appears later in this chapter. Related commands: dsppnports dsppnport <portid> dsppnportsig <portid> Step 10 dsppnni-link dsppnni-neighbor When both ends of the trunk are configured for PNNI signalling, verify the PNNI communications between the two ends. In the dsppnni-link report, there should be an entry for the port for which you are verifying communications. The Hello state reported should be twoWayInside or twoWayOutside, and the Remote node ID should display the remote node ATM address after the second colon. See “Verifying PNNI Trunk Communications,” which appears later in this chapter. SPVC and SPVP Configuration Quickstart A Soft Permanent Virtual Circuit (SPVC) is a Permanent Virtual Circuit (PVC) that can be rerouted using the Private Network-to-Network Interface (PNNI) Version 1.0 protocol. As with PVCs, SPVCs are full-time connections. A PVC, however, uses a predefined circuit path and will fail if the path is interrupted. Using the PNNI protocol, SPVCs can be rerouted to avoid failed communication links or to use links that offer better bandwidth. A Soft Permanent Virtual Path (SPVP) is a permanent virtual path that can be rerouted using the Private Network-to-Network Interface (PNNI) Version 1.0 protocol. The difference between an SPVC and an SPVP is that the SPVP supports multiple virtual circuits, whereas a SPVC is by definition a single virtual circuit. As with SPVCs, when an SPVP fails, PNNI can determine if an alternate route exists and reroute the connection. The quickstart procedure in this section provides a summary of the tasks required to configure SPVCs and SPVPs on the SES controller. This procedure is provided as an overview and as a quick reference for those who have previously configured these types of connections. Cisco SES PNNI Controller Software Configuration Guide Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 3-7 Chapter 3 Provisioning Communication Links Quickstart Procedures for Provisioning Links on the SES Controlled BPX Step 1 Command Purpose username Start a configuration session. <password> Note To perform all the procedures in this quickstart procedure, you must log in as a user with SUPER_GP privileges or higher. Step 2 See “PNNI Trunk Configuration Configure the trunks that link the switches to which the ATM end Quickstart,” which appears earlier stations connect. in this chapter. Note The path between the end points can include the MGX 8850 switch. For information on configuring trunks on these switches, refer to the Cisco MGX 8850 Routing Switch Software Configuration Guide, Release 2.1 Step 3 dsppnni-reachable-addr network Verify PNNI connectivity to the two nodes that will host the SPVC or SPVP end points. See “Verifying PNNI Trunk Communications,” which appears later in this chapter. Step 4 See “PNNI UNI Port Configuration Quickstart,” which appears earlier in this chapter. Configure lines for the ATM end stations at each end of the SPVC or SPVP, and assign either static or dynamic addressing to each line. Note Step 5 addcon <options> Related commands: dspcons Configure the slave side of an SPVC. See “Configuring SPVCs and SPVPs,” which appears later in this chapter. Note dspcon <ifNum> <vpi> <vci> Step 6 addcon <options> Related commands: dspcons dspcon <ifNum> <vpi> <vci> End points can be located on the MGX 8850 switch. For information on configuring UNI ports on these switches, refer to the Cisco MGX 8850 Routing Switch Software Configuration Guide, Release 2.1 The slave side of the connection can be located on the MGX 8850 switch. For information on configuring slave-side connections on these switches, refer to the Cisco MGX 8850 Routing Switch Software Configuration Guide, Release 2.1 Configure the master side of an SPVC. See “Configuring SPVCs and SPVPs,” which appears later in this chapter. Note The master side of the connection can be located on the MGX 8850 switch. For information on configuring master-side connections on these switches, refer to the Cisco MGX 8850 Routing Switch Software Configuration Guide, Release 2.1 Cisco SES PNNI Controller Software Configuration Guide 3-8 Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 Chapter 3 Provisioning Communication Links Quickstart Procedures for Provisioning Links on the SES Controlled BPX MGX 8850 Release 1 Feeder Configuration Quickstart The quickstart procedure in this section provides a summary of the tasks required to configure an MGX 8850 Release 1 switch, a BPX, and an SES controller to support a feeder connection from the MGX 8850 to the PNNI network. This procedure is provided as an overview and as a quick reference for those who have previously configured these types of connections. Step 1 Command Purpose addln <LineNum> At the MGX 8850 PXM CLI, add and configure line with LMI/Annex G enabled. See “Setting Up the MGX 8850 End of the Feeder Trunk,” which appears later in this chapter. Step 2 addport <slot.port> Add a service port to the shelf. Step 3 cnfswfunc -vsvd <enable(yes) | disable(no)> -ndtype <fdr | routing> Set the feeder implementation and VS/VD control for ABR traffic. Step 4 cnfifastrk <slot.port> <if-type> Configure the logical interface on the PXM to act as a feeder trunk. Step 5 dspln <LineNum> Verify the new line’s parameters. Step 6 dspipifs Verify the interface parameters. Use the following commands on the BPX switch to configure a feeder trunk. Step 1 uptrk <slot.port> Related commands: Bring up the trunk that leads to the MGX 8850 Release 1 switch. See “Bringing Up a BXM Trunk”, which appears later in this chapter. cnftrk<slot.port> dsptrks Step 2 cnfvsiif <slot.port> <sct_ID> Related commands: Define the trunk as a VSI interface and set the Service Class Template to 3. See “Assigning a Service Class Template to a VSI Interface”, which appears later in this chapter. dspsct dspvsiif <slot.port> Step 3 cnfrsrc <slot.port> <options> Related commands: Enable a VSI partition and configure resources for the trunk. You can accept the default values for most options. The required options are the partition number and e, which enables the VSI partition. dsprsrc <slot.port> Note Do not set the VPI to 3. See “Enabling a Partition and Configuring Resources for a Trunk”, which appears later in this chapter. Cisco SES PNNI Controller Software Configuration Guide Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 3-9 Chapter 3 Provisioning Communication Links Quickstart Procedures for Provisioning Links on the SES Controlled BPX Step 4 Step 5 addshelf <slot.port> <shelf-type> [vpi] [vci] Add the MGX 8850 as a feeder on the trunk. cnftrk <slot.port>[.vtrk] <options for E1 | T1 | E3 | T3 | OC-3 | OC-12 | E2 | HSSI | SR > Configure the trunk. See “Adding a Shelf to a Trunk,” which appears later in this chapter. See “Configuring a BXM Trunk,” which appears later in this chapter. Use the following commands on the SES switch to configure a feeder trunk. Step 1 dsppnports Display status information for all UNI and NNI ports on the node. See “Setting Up the SPVC Feeder Segment on the SES,” which appears later in this chapter. Step 2 cnfoamsegep <portid> no dspoamsegep <portid> Define a specified port as a segment endpoint for F4 and F5 OAM flow. Verify the configuration. Step 3 addcon <portid> <vpi> <vci> <serviceType> <master_ship> <slave_nsap.vpi.vci> Add a new connection endpoint on the port. Verify that the connection has been added correctly. dspcons Use the following commands on the MGX 8850 switch to configure a PVC segment. Step 1 cc <slot number> Login to the MGX8850. Change to the card on which the PVC Segment will reside. See “Setting Up the PVC Segment on an MGX 8850 Feeder Node,” which appears later in this chapter Step 2 addln <LineNum> Add a new line and verify that the configuration took place. dspln <LineNum> Step 3 addport <slot.port> dspports Step 4 addcon <portid> <vpi> <vci> <serviceType> <master_ship> <slave_nsap.vpi.vci> Add a new connection port and verify that the port was added correctly. Add a new connection. Display all connections on the port and verify that the new connection is added properly. dspchans Step 5 cc <slot number> Set up the second PVC connection. Change to the card on which the second PVC will reside. Step 6 addln <LineNum> Add a line to the card. Step 7 addport <slot.port> Add a port on the line and verify that it was added. dspports Cisco SES PNNI Controller Software Configuration Guide 3-10 Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 Chapter 3 Provisioning Communication Links Quickstart Procedures for Provisioning Links on the SES Controlled BPX Step 8 addcon <portid> <vpi> <vci> <serviceType> <master_ship> <slave_nsap.vpi.vci> Add a new connection. dspcons Step 9 dspchans Verify that the new connection was added properly. Step 10 cc <slot number> Change to the active PXM card. Step 11 dspcons Display a summary of all channels on the card configured in Steps 1-3. Verify that the connection was set up properly. Step 12 cc <slot number> Change to the card configured in Steps 1-3. Step 13 dspchans Display a summary of all channels on the card configured in Steps 1-4. Step 14 tstdelay <channel number> Verify the continuity of the connection on the card in slot 3. Step 15 cc <slot number> Change to the card configured in Steps 5-9. Step 16 dspchans Display a summary of all channels on the card configured in Steps 1-4. Step 17 tstdelay <channel number> Verify the continuity of the connection on the card in slot 4. AINI Link Configuration Quickstart The quickstart procedure in this section provides a summary of the tasks required to configure ATM Inter-Network Interface (AINI) links on the SES switch. This procedure is provided as an overview and as a quick reference for those who have previously configured these types of connections. Step 1 Command Purpose username Start a configuration session. <password> Note To perform all the procedures in this quickstart procedure, you must log in as a user with SUPER_GP privileges or higher. Step 2 Prepare the cards and lines as described in “Preparing Cards and Lines for Communication.” Remember to select the appropriate card SCT for the controller or controllers you are using. Step 3 addport <options> Related commands: dspports Add and configure ATM ports. This step establishes ATM communications between two ATM devices. Specify NNI for interswitch trunks. See “Adding ATM Ports,” which appears later in this chapter. Step 4 addpart <options> Related commands: dspparts dsppart Assign trunk resources to the PNNI controller. This step can assign all the trunk bandwidth to a single controller, or it can assign portions of the trunk bandwidth to each controller. See “Partitioning Port Resources Between Controllers,” which appears later in this chapter. cnfpart Cisco SES PNNI Controller Software Configuration Guide Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 3-11 Chapter 3 Provisioning Communication Links Quickstart Procedures for Provisioning Links on the SES Controlled BPX Step 5 Command Purpose dnpnport <portid> Define the signaling protocol used at each end of the AINI link. The default signaling protocol is UNI Version 3.1. Specify aini for AINI trunks cnfpnportsig <options> uppnport <portid> Related commands: dsppnports dsppnport <portid> dsppnportsig <portid> Define the signaling protocol used at each end of the AINI link. The default signaling protocol is UNI Version 3.1. Specify aini for AINI trunks. Step 6 addaddr <options> Add destination addresses to each end of the trunk. See “Defining Destination Addresses for Static Links,” which appears later in this chapter. Step 7 addaddr <options> Add static addresses to destination ports. This step is required when addresses are not dynamically assigned to the CPE at the destination ports. See “Assigning Static ATM Addresses to Destination Ports,” which appears later in this chapter. IISP Link Configuration Quickstart The quickstart procedure in this section provides a summary of the tasks required to configure Interim Inter-switch Protocol (IISP) links on the SES controller. This procedure is provided as an overview and as a quick reference for those who have previously configured these types of connections. AINI is a newer protocol that is designed to replace the function of IISP. Unless you are configuring a link with another switch that does not support AINI, you should configure an AINI link instead of an IISP link. IISP links provide fewer capabilities than AINI links. For example, IISP links cannot support UNI 4.0 connections. Step 1 Step 2 Command Purpose username Start a configuration session. <password> Note addpnport <options> Add and configure ATM ports. This step establishes ATM communications between two ATM devices. Related commands: dsppnports To perform all the procedures in this quickstart procedure, you must log in as a user with SUPER_GP privileges or higher. Specify NNI for interswitch trunks. Cisco SES PNNI Controller Software Configuration Guide 3-12 Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 Chapter 3 Provisioning Communication Links BPX Configuration Procedures Step 3 Command Purpose dnpnport <portid> Define the signaling protocol used at each end of the IISP link. The default signaling protocol is UNI Version 3.1. Specify either iisp30 or iisp31 for IISP trunks. cnfpnportsig <options> uppnport <portid> Related commands: dsppnports dsppnport <portid> dsppnportsig <portid> Define the signaling protocol used at each end of the AINI link. The default signaling protocol is UNI Version 3.1. Specify aini for AINI trunks. Step 4 addaddr <options> Add destination addresses to each end of the trunk. See “Defining Destination Addresses for Static Links,” which appears later in this chapter. Step 5 addaddr <options> Add static addresses to destination ports. This step is required when addresses are not dynamically assigned to the CPE at the destination ports. See “Assigning Static ATM Addresses to Destination Ports,” which appears later in this chapter. BPX Configuration Procedures This section provides additional procedures that support the tasks in the configuration quickstarts. Bringing Up a BXM Trunk BXM trunks can be use for the following types of connections: • SES controller uplink • PNNI connection to another BXM • PNNI connection to an AXSM on an MGX 8850 switch Cisco SES PNNI Controller Software Configuration Guide Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 3-13 Chapter 3 Provisioning Communication Links BPX Configuration Procedures The following procedure describes how to bring up a BXM trunk. Step 1 Start a configuration session on the BPX. Step 2 Enter the uptrk command at the BPX CLI as follows: uptrk <slot.port> Replace <slot.port> with the slot number of the card and the physical port to which the trunk is connected. For example: B8650_CH TRK 1.2 1.3 1.4 2.1 2.2 3.1 TN Type OC3 OC3 OC3 OC3 OC3 T3 Cisco Current Clear Clear Clear Clear Clear Clear - BPX 8620 9.3.3W Aug. 30 2001 19:36 PST Line Alarm Status OK OK OK OK OK OK Other End VSI only B8650_SJ/3.1 Last Command: uptrk 1.4 256 PVCs allocated. Use 'cnfrsrc' to configure PVCs Next Command: After you enter the command, the BPX displays the trunk and the current line alarm status. If the line is in alarm, it might be because the opposite end of the trunk has not been brought up. Note Step 3 For SES controller uplinks, you do not need to bring up the port on the SES controller. It automatically comes up when you configure the BPX. To check trunk status at any time, enter the dsptrks command. Configuring a BXM Trunk The following procedure describes how to configure a BXM trunk. Step 1 Start a configuration session on the BPX. Step 2 Enter the cnftrk command at the BPX CLI as follows: cnftrk <slot.port> Replace <slot.port> with the slot number of the card and the physical port to which the trunk is connected and set the Protocol By The Card option to no. For example: B8650_CH TN Cisco BPX 8620 TRK 1.4 Config OC3 [353207cps] Transmit Rate: 353208 Protocol By The Card: Yes VC Shaping: No Hdr Type NNI: Yes Statistical Reserve: 5000 cps 9.3.3W Aug. 30 2001 19:53 PST BXM slot: 1 VPC Conns disabled: Line framing: coding: recv impedance: cable type: No STS-3C ---- Cisco SES PNNI Controller Software Configuration Guide 3-14 Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 Chapter 3 Provisioning Communication Links BPX Configuration Procedures Idle code: 7F hex Connection Channels: 256 Traffic:V,TS,NTS,FR,FST,CBR,N&RT-VBR,ABR Restrict CC traffic: No Link type: Terrestrial Routing Cost: 10 F4 AIS Detection: -- length: Pass sync: Loop clock: HCS Masking: Payload Scramble: Frame Scramble: Vtrk Type / VPI: Incremental CDV: Deroute delay time: -Yes No Yes Yes Yes -- / -0 0 seconds Last Command: cnftrk 1.4 353208 y y 5000 7F V,TS,NTS,FR,FST,CBR,NRT-VBR,ABR,RT-V BR N TERRESTRIAL 10 0 Y N Y Y Y 0 N Next Command: Note Be sure the Protocol By The Card field is set to No. For more information on configuring trunks with the cnftrk command, refer to the Cisco WAN Switching Command Reference, Release 9.3. Step 3 To check trunk configuration at any time, enter the dsptrk <slot.port> command. Bringing Up a BXM Line BXM lines are typically used for UNI connections to CPE. The following procedure describes how to bring up a BXM line. Step 1 Start a configuration session on the BPX. Step 2 Enter the upln command at the BPX CLI as follows: upln <slot.port> Replace <slot.port> with the slot number of the card and the physical port to which the trunk is connected. For example: B8650_CH Line 2.5 TN Type OC3 Cisco BPX 8620 9.3.3W Aug. 31 2001 21:09 PST Current Line Alarm Status Clear - OK Last Command: upln 2.5 After you enter the command, the BPX displays the line and the current line alarm status. If the line is in alarm, it might be because the opposite end of the line has not been brought up. Step 3 To check line status at any time, enter the dsplns command. Step 4 To view the configuration of a line, enter the dspln <slot.port> command. Step 5 To change the configuration of a line, enter the cnfln <slot.port> command. Cisco SES PNNI Controller Software Configuration Guide Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 3-15 Chapter 3 Provisioning Communication Links BPX Configuration Procedures Adding a Port to a BXM Line After you bring up a line, you can add an ATM UNI port to the line using the following procedure. Step 1 Start a configuration session on the BPX. Step 2 Enter the addport command to add a port to a BXM line. bpxone.1.BXM.a > addport <slot.port> Replace <slot.port> with the slot number of the card and the physical port identifier. For example: B8650_CH TN Cisco BPX 8620 9.3.3W Aug. 31 2001 21:21 PST Port configuration for ATM 2 From 2.5 VPI Min/Max 0 / 255 Bandwidth 353208 (cps) Interface LM-BXM State INACTIVE Protocol NONE Type UNI Last Command: addport 2.5 256 PVCs allocated. Use 'cnfrsrc' to configure PVCs Next Command: Step 3 To display a list of ports, enter the dspports command. For example: B8650_CH TN Cisco BPX 8620 9.3.3W Aug. 31 2001 21:23 PST Port States Port State 2.5 INACTIVE Last Command: dspports Step 4 To display the status and configuration of a port, enter the dspport command. For example: B8650_CH TN Cisco BPX 8620 9.3.3W Aug. 31 2001 21:25 PST Port: 2.5 Interface: VPI Range: Type: Shift: SIG Queue Depth: [INACTIVE] Bandwidth/AR BW: LM-BXM CAC Override: 0 - 255 CAC Reserve: UNI %Util Use: SHIFT ON HCF (Normal Operation) 640 Port Load: Protocol: NONE 353208/353208 Enabled 0 Disabled 0 % Protocol by Card: No Last Command: dspport 2.5 Cisco SES PNNI Controller Software Configuration Guide 3-16 Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 Chapter 3 Provisioning Communication Links BPX Configuration Procedures Bringing Up a Port on a BXM Line The following procedure describes how to bring up a port on a BXM line. Step 1 Start a configuration session on the BPX. Step 2 Enter the upport command to bring the port up. bpxone.1.BXM.a > upport <slot.port> Replace <slot.port> with the slot number of the card and the physical port identifier. After you enter this command, the port status changes to active. For example: B8650_CH TN Cisco BPX 8620 9.3.3W Aug. 31 2001 21:28 PST Port: 2.5 Interface: VPI Range: Type: Shift: SIG Queue Depth: [ACTIVE ] Bandwidth/AR BW: LM-BXM CAC Override: 0 - 255 CAC Reserve: UNI %Util Use: SHIFT ON HCF (Normal Operation) 640 Port Load: Protocol: NONE 353208/353208 Enabled 0 Disabled 0 % Protocol by Card: No Last Command: upport 2.5 Configuring a BXM Port The following procedure describes how to configure a BXM port. Step 1 Start a configuration session on the BPX. Step 2 Enter the cnfport command at the BPX CLI as follows: cnfport <slot.port> Note The parameters for this command vary depending on the card type. For more information on how this command should be entered for each specific card, refer to the Cisco WAN Switching Command Reference, Release 9.3. Replace <slot.port> with the slot number of the card and the physical port to which the line is connected. Set the Protocol option to i (for ILMI) and the Protocol By The Card option to y. For example: B8650_SJ TN Port: 2.5 Interface: VPI Range: Type: Shift: SIG Queue Depth: Cisco BPX 8620 9.3.3W Sep. 4 2001 [ACTIVE ] Bandwidth/AR BW: LM-BXM CAC Override: 0 - 255 CAC Reserve: UNI %Util Use: SHIFT ON HCF (Normal Operation) 640 Port Load: Protocol: ILMI Advertise Intf Info: 11:26 PST 353208/353208 Enabled 0 Disabled 0 % Protocol by Card: Yes No Cisco SES PNNI Controller Software Configuration Guide Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 3-17 Chapter 3 Provisioning Communication Links BPX Configuration Procedures VPI.VCI: ILMI Polling Enabled: Trap Enabled: T491 Polling Interval: N491 Error Threshold: N492 Event Threshold: 0.16 Y Y 30 3 4 Addr Reg Enab: Y ILMI Reset Flag:Y Last Command: cnfport 2.5 353208 UNI H i 0 16 y y y 30 3 4 Y N 0 N y N Note All ILMI features on the SES controller are enabled by default. You do not need to use the SES controller commands, cnfaddrreg and cnfautocnf, to enable ILMI features on the SES controller. For more information on configuring ports with the cnfport command, refer to the Cisco WAN Switching Command Reference, Release 9.3. Step 3 To check port configuration at any time, enter the dspport <slot.port> command. Assigning a Service Class Template to a VSI Interface A VSI interface is a trunk or line that is controlled by a VSI controller such as the SES controller. Use the following procedure to define an interface as a VSI trunk and set the Service Class Template (SCT). Step 1 Start a configuration session on the BPX. Step 2 Enter the cnfvsiif command as follows: cnfvsiif <slot.port> <SCT_ID> Replace <slot.port> with the slot number of the card and the physical port identifier. For a trunk, replace <SCT_ID> with 3, which selects an ATM forum template with policing disabled. For a line, replace <SCT_ID> with 2, which selects an ATM forum template with policing enabled. For a complete listing of all SCTs, enter the dspsct command. Warning Step 3 The default SCT is 1 (for MPLS). The SES does not support MPLS. If the VSI trunk SCT is set to 1 (MPLS) on an SES switch, the trunk or port will not become active. To determine which SCT is assigned to a port, enter the dspvsiif <slot.port> command. Cisco SES PNNI Controller Software Configuration Guide 3-18 Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 Chapter 3 Provisioning Communication Links BPX Configuration Procedures Enabling a Partition and Configuring Resources for a Trunk The following procedure describes how to enable a partition and configure resources for the partition. Step 1 Start a configuration session on the BPX. Step 2 Enter the cnfrsrc command as follows: cnfrsrc <slot.port> The syntax for the complete command is as follows: cnfrsrc <slot.port.vtrk> <maxpvclcns> <maxpvcbw> <y/n> <y/n> <partition> <e/d> <minvsilcns> <maxvsilcns> <vsistartvpi> <vsiendvpi><vsiminbw> <vsimaxbw> Replace <slot.port> with the slot number of the card and the physical port to which the trunk is connected. The parameters for the cnfrsrc command are described below: Parameter Description slot.port.vtrk Slot number of the card and the physical port identifier and the virtual port identifier. maxpvclcns Maximum number of LCNs allocated for Automatic Routing Management PVCs for this port. The range depends upon the card type; (1-11771 for the BNI T/E3 and 1-15867 for the BNI OC) 256 is the default. The default is 256 only if 256 are available. If other ports and trunks on the card have been configured to use LCNs such that there are only 100 remaining, then the default value for the newly added port would be 100. In this instance trunk upping would be blocked indicating that there are not enough LCNs to support the trunk. For trunks, there are additional LCNs allocated for Automatic Routing Management that are not configurable. y/n Answer y (yes) configure PVC VIP ranges. y/n Answer y (yes) configure VSI parameters. partition Identifies the partition. Replace <partition> with a number in the range from 1 to 3. e/d Answer e to enable or d to disable your configured partition. minvsilcns Minimum LCNs guaranteed for this partition.Replace <minvsilcns> with a number in the range from 0 to the port_group/card limit maxvsilcns Maximum LCNs permitted on this partition. Replace <maxvsilcns> with a number in the range from 1 to port_group/card limit vsistartvpi Partition Start VPI. Replace <vsistartvpi> with a number in the range from 0 to 4095. Cisco SES PNNI Controller Software Configuration Guide Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 3-19 Chapter 3 Provisioning Communication Links BPX Configuration Procedures Parameter Description vsiendvpi Partition End VPI. VSI connections on this partition can use VPIs up to this VPI. The end VSI VPI should be equal to or greater than the Start VSI VPI. Replace <vsiendvpi> with a number in the range from 0 to 4095. vsiminbw Minimum Partition bandwidth. Replace <vsiminbw> with a number in the range from 0 to the Line Rate. vsimaxbw Maximum Partition bandwidth. Replace <vsimaxbw> with a number in the range from 0 to the Line Rate. Refer to the Cisco WAN Switching Command Reference, Release 9.3 for more information on the cnfrsrc command parameters. Step 3 When prompted to Edit VSI Parms, enter y, then enter a partition number for the SES controller. Valid choices are 1 through 3. Step 4 When prompted, enter e to enable the partition for the SES controller. Step 5 To display resources for a trunk, enter the dsprsrc <slot.port> command. The following example shows the resources assigned to a trunk: B8650_CH TN Cisco BPX 8620 9.3.3W Aug. 30 2001 20:42 PST Trunk : 1.2 Maximum PVC LCNS: PVC VPI RANGE [1]: PVC VPI RANGE [3]: Partition : Partition State : VSI LCNS (min/max): VSI VPI (start/end): VSI BW (min/max): VSI ILMI Config: 256 -1 -1 /-1 /-1 1 Enabled 0 /1000 1 /4095 0 /348207 SET Full Port Bandwidth: 353208 Maximum PVC Bandwidth: 0 (Statistical Reserve: 5000) PVC VPI RANGE [2]: -1 PVC VPI RANGE [4]: -1 2 Disabled 0 /0 0 /0 0 /0 CLR /-1 /-1 3 Disabled 0 /0 0 /0 0 /0 CLR Last Command: dsprsrc 1.2 Next Command: Cisco SES PNNI Controller Software Configuration Guide 3-20 Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 Chapter 3 Provisioning Communication Links BPX Configuration Procedures Enabling a Partition and Configuring Resources for a Line The following procedure describes how to enable a partition and configure resources for the partition. Step 1 Start a configuration session on the BPX. Step 2 Enter the cnfrsrc command as follows: cnfrsrc <slot.port> Replace <slot.port> with the slot number of the card and the physical port to which the trunk or line is connected. Refer to the Cisco WAN Switching Command Reference, Release 9.3 for descriptions of the parameters for which the switch prompts. Step 3 When prompted to Configure PVC VPI ranges?, enter n. Step 4 When prompted to Edit VSI Parms, enter y, then enter a partition number for the SES controller. Valid choices are 1 through 3. Step 5 When prompted, enter e to enable the partition for the SES controller. Step 6 To display resources for a line, enter the dsprsrc <slot.port> command. The following example shows the resources assigned to a line: B8650_CH TN Cisco BPX 8620 9.3.3W Aug. 31 2001 22:58 PST Port : 2.5 Maximum PVC LCNS: PVC VPI RANGE [1]: PVC VPI RANGE [3]: 256 -1 -1 Partition : Partition State : VSI LCNS (min/max): VSI VPI (start/end): VSI BW (min/max): VSI ILMI Config: /-1 /-1 1 Enabled 2000 /7000 1 /255 0 /0 SET Full Port Bandwidth: 353208 Maximum PVC Bandwidth: 353208 (CAC Reserve: 0) PVC VPI RANGE [2]: -1 PVC VPI RANGE [4]: -1 2 Disabled 0 /0 0 /0 0 /0 CLR /-1 /-1 3 Disabled 0 /0 0 /0 0 /0 CLR Last Command: dsprsrc 2.5 Next Command: Cisco SES PNNI Controller Software Configuration Guide Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 3-21 Chapter 3 Provisioning Communication Links BPX Configuration Procedures Defining Destination Addresses for Static Links Typically, an AINI or IISP static link joins two independent networks. AINI or IISP links are used instead of PNNI so that the topologies of the two networks remain unknown to the each other. When you create a static link, you must identify destination addresses for each side of the link. These addresses identify which ATM nodes are accessible on the other side of the link. After you define these addresses, all requests for these addresses are routed over the static link to the other network. Note To enable bidirectional call initiation, the appropriate destination address must be configured at each end of the link. For example, if nodes A and B have PNNI connections to a static link, the ATM address for Node B must be added to the Node A side of the static link, and the Node A address must be added to the Node B side of the static link. To add destination addresses to a static link, use the following procedure. Step 1 Establish a configuration session using a user name with GROUP1 privileges or higher. Step 2 To locate the port to which you want to add an address, enter the dsppnports command. Step 3 Specify an ATM address using the following command: spirita.1.PXM.a > addaddr <portid> <atm-address> <length> -type ext -proto static [-plan {e164 | nsap}] [-scope scope] [-redistribute {yes | no}] Note The addaddr command is used to define destination addresses for static links and to specify static addresses for links to CPE. The command format above shows the options as they apply when defining destination addresses for static links. Table 3-1 describes the parameters used with the addaddr command. Table 3-1 ATM Address Configuration Parameters Parameter Description portid Enter the port identifier in the format slot:bay.line:ifnum. atm-address Enter the ATM address using up to 40 nibbles. The ATM address can include up to 20 bytes, which is 40 nibbles or 160 bits. To summarize a group of destination addresses, enter an ATM address that is less than 20 bytes and includes the common bytes in the group of destination addresses. length Enter the length, in bits, of the address you specified with the <atm-address> parameter. Each nibble is equal to 4 bits. The acceptable range for the parameter is from 0 to 160 bits. When you enter a complete 20-byte ATM address, the length is 160. When you summarize a group of destination addresses, the length is equal to the number of bytes entered multiplied by 8. -type Enter the address type, which is ext (external) for destination addresses on the other side of a static link. The int (internal) value is used when creating static addresses for links to CPE. Default = int. Cisco SES PNNI Controller Software Configuration Guide 3-22 Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 Chapter 3 Provisioning Communication Links BPX Configuration Procedures Table 3-1 ATM Address Configuration Parameters (continued) Parameter Description -proto For static link destination addresses, specify the -proto option with the static value. The local value applies to CPE links. Default = local. -plan Enter the address plan, which is either e164 (E.164) or nsap (NSAP). For an NSAP address, the first byte of the address automatically implies one of the three NSAP address plans: NSAP E.164, NSAP DCC, or NSAP ICD. Default = nsap. -scope PNNI scope of advertisement. The scope defines the level of the PNNI hierarchy at which this address is advertised. Enter 0 to advertise the destination address to all nodes in the node’s peer group. Range: 0 through 104. Default = 0. -redistribute Specifies whether or not the ATM address should be distributed or advertised to PNNI neighbor nodes. Enter yes to enable distribution and enter no to disable. When this option is set to yes, the node distributes the address to the PNNI neighbors defined with the scope option. When set to no, the address is not advertised to any other nodes. Default = no. Step 4 To verify that the new address has been assigned, enter the following command: spirita.1.PXM.a > dspatmaddr <portid> Replace <portid> with the port address using the format slot:bay.line:ifnum. For example: spirita.1.PXM.a > dspaddr 2:1.2:2 47.0091.8100.0000.0003.6b5e.30cd.0003.6b5e.30cd.01 length: 160 type: exterior proto: static scope: 0 plan: nsap_icd redistribute: false Assigning Static ATM Addresses to Destination Ports When a CPE does not support ILMI, the switch cannot automatically determine the CPE address. To enable communications with the CPE, you must assign a static ATM address to the port leading to the CPE. The static address must match the address used by the CPE. When assigning the static address, you can use command options to define how widely the static address is advertised within the switch network. Use the following procedure to define a static address for a UNI port. Step 1 Establish a configuration session using a user name with GROUP1 privileges or higher. Step 2 To locate the port to which you want to add an address, enter the dsppnports command. Cisco SES PNNI Controller Software Configuration Guide Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 3-23 Chapter 3 Provisioning Communication Links BPX Configuration Procedures Step 3 Use the following command to turn off automatic address registration (it is enabled by default) on the port that will use the static address: spirita.1.PXM.a > cnfaddrreg <portid> no Replace portid using the format slot:bay.line:ifNum. Step 4 Specify an ATM address for the port using the following command: spirita.1.PXM.a > addaddr <portid> <atm-address> <length> [-type int] [-proto local] [-plan {e164 | nsap}] [-scope scope] [-redistribute {yes | no}] Note The addaddr command is used to specify static addresses for UNI links to CPE and to define destination addresses for AINI and IISP static links. The command format above shows the options that apply when defining static addresses for CPE. Replace <portid> with the ID you used with the cnfaddreg command described earlier. Table 3-2 describes the other parameters used with the addaddr command. Note The static ATM address you choose should conform to the address plan for your network. For more information on address planning, refer to the Cisco MGX and SES PNNI Network Planning Guide. Table 3-2 ATM Address Configuration Parameters Parameter Description portid Port identifier in the format slot:bay.line:ifnum. atm-address Enter the ATM address using up to 40 nibbles. The ATM address can include up to 20 bytes, which is 40 nibbles or 160 bits. length Enter the length, in bits, of the address you specified with the <atm-address> parameter. Each nibble is equal to 4 bits. The acceptable range for the parameter is from 0 to 160 bits. -type Enter the address type, which is int (internal) for CPE static addresses. The ext (external) value is used when creating destination addresses for AINI and IISP static links. Note that because the default value is int, you do not have to specify this option when defining static CPE addresses. Default = int. -proto For CPE static addresses, specify the -proto option with the local value. The static value applies to AINI and IISP static links. Note that because the default value is local, you do not have to specify this option when defining static CPE addresses. Default = local. -plan Enter the address plan, which is either e164 (E.164) or nsap (NSAP). For an NSAP address, the first byte of the address automatically implies one of the three NSAP address plans: NSAP E.164, NSAP DCC, or NSAP ICD. Default = nsap. Cisco SES PNNI Controller Software Configuration Guide 3-24 Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 Chapter 3 Provisioning Communication Links BPX Configuration Procedures Table 3-2 ATM Address Configuration Parameters (continued) Parameter Description -scope PNNI scope of advertisement. The scope defines the level of the PNNI hierarchy at which this address is advertised. Enter 0 to advertise the destination address to all nodes in the node’s peer group. Range: 0 to 104. Default = 0. -redistribute Specifies whether or not the ATM address should be distributed or advertised to PNNI neighbor nodes. Enter yes to enable distribution and enter no to disable. When this option is set to yes, the node distributes the address to the PNNI neighbors defined with the scope option. When set to no, the address is not advertised to any other nodes. Default = no. The following example assigns an ATM address to port 9:1.2:2: spirita.1.PXM.a > addaddr 1:2.1:3 47.1111.1111.1111.1111.1111.1111.1111.1111.1111.11 160 Step 5 To verify that the new address has been assigned, enter the dspatmaddr command as shown in the following example: spirita.1.PXM.a > dspatmaddr 2:2.2:1 Port Id: 2:2.2:1 Configured Port Address(es) : 47.1111.1111.1111.1111.1111.1111.1111.1111.1111.11 length: 160 type: internal proto: local scope: 0 plan: nsap_icd redistribute: false Adding a Shelf to a Trunk To configure a trunk to support communications with an external controller or feeder switch enter the addshelf command at the BPX CLI: addshelf <slot.port> <shelf type> Replace <slot.port> with the slot and port number of the trunk. Replace <shelf type> with the type of interface shelf. The choices are I for IGX/AF, A for the MGX 8220, V for VSI, or X for the MGX 8800. Cisco SES PNNI Controller Software Configuration Guide Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 3-25 Chapter 3 Provisioning Communication Links BPX Configuration Procedures A system response similar to the following example occurs: sjbpxbxm> addshelf 3.4 x Shelf has been added sj862241 TN Cisco BPX 8620 TRK 3.4 Config OC3 [353207cps] Transmit Rate: 353208 Protocol By The Card: Yes VC Shaping: No Hdr Type NNI: Yes Statistical Reserve: 5000 cps Idle code: 7F hex Connection Channels: 1000 Traffic:V,TS,NTS,FR,FST,CBR,N&RT-VBR,ABR SVC Vpi Min: 0 SVC Channels: 0 SVC Bandwidth: 0 cps Restrict CC traffic: No Link type: Terrestrial Routing Cost: 10 9.3.10 Nov. 10 2000 18:03 PST BXM slot: 3 VPC Conns disabled: Line framing: coding: recv impedance: cable type: length: Pass sync: Loop clock: HCS Masking: Payload Scramble: Frame Scramble: Virtual Trunk Type: Virtual Trunk VPI: Deroute delay time: No STS-3C ----No No Yes Yes Yes --0 seconds Enabling ILMI on a Trunk To enable ILMI on a trunk, use the following procedure. Note This procedure is for enabling ILMI on a trunk. This procedure will not enable ILMI on a line or port. Step 1 Start a configuration session on the BPX. Step 2 Enter the cnfvsipart command as follows: cnfvsipart <slot.port> <partition_id> y Replace <slot.port> with the slot number of the card and the physical port identifier. Replace <partition_id> with the partition ID you specified with the cnfrsrc command, and enter y to enable ILMI on the partition. Cisco SES PNNI Controller Software Configuration Guide 3-26 Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 Chapter 3 Provisioning Communication Links SES Controller Configuration and Verification Procedures Step 3 To verify the ILMI status on a VSI partition, enter the dspvsipartcnf command as shown in the following example: B8650_CH Trunk: 1.2 Trunk: 1.2 Trunk: 1.2 TN Cisco Partn: 1 Partn: 2 Partn: 3 BPX 8620 9.3.3W ILMI: E LCN: 815 -- VSI partition DISABLED -- VSI partition DISABLED Aug. 30 2001 21:00 PST Topo: BPX NW/LAN IP Sys_Id generated = 67.39.38.37.35.31 Last Command: dspvsipartcnf 1.2 Next Command: SES Controller Configuration and Verification Procedures This section provides additional procedures that support the tasks in the configuration quickstarts. Selecting the Port Signaling Protocol The default signaling protocol for all new ports is UNI Version 3.1. If you plan to use this protocol on a line, you can accept this default and skip this section. However, if you plan to use a different protocol on the line, such as PNNI, you must select the correct protocol using the following procedure. Step 1 Establish a configuration session using a user name with GROUP1 privileges or higher. Step 2 Use the following command to display a list of the ports you can configure: SES_CH.1.PXM.a > dsppnports Step 3 Use the following command to bring down the port you want to configure: SES_CH.1.PXM.a > dnpnport <slot.port> A port is automatically brought up when you add it. You must bring down the port before you can change the port signaling protocol. Replace <slot.port> with the slot number of the card and the physical port identifier. Step 4 To confirm the port is down, enter the dsppnports command. Cisco SES PNNI Controller Software Configuration Guide Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 3-27 Chapter 3 Provisioning Communication Links SES Controller Configuration and Verification Procedures Step 5 To select the port signaling protocol, enter the following command: SES_CH.1.PXM.a > cnfpnportsig <portid> [-univer {uni30|uni31|uni40|none}] [-nniver {iisp30|iisp31|pnni10|enni|aini}] [-unitype {public|private}] [-addrplan {both|aesa|e164}] [-side {user|network}] [-vpi <vpi>] [-sigvci <signalling-vci>] [-rccvci <routing-vci>] [-cntlvc <ip>] The only required parameter for this command is the <slot.port> parameter, but the command serves no purpose if you do not enter at least one option with it. If you include some options with the command and omit others, the omitted option remains set to the last configured value. Table 3-3 lists and describes the options and parameters for the cnfpnportsig command. Table 3-3 Port Signaling Configuration Parameters Parameter Description <slot.port> Replace <slot.port> with the slot number of the card and the physical port identifier. -univer When configuring PNNI signaling for a UNI port, you can use this option to specify which version of UNI signaling you want the port to use. You can select UNI version 3.0 (uni30), UNI version 3.1 (uni31), UNI version 4.0 (uni40) or no UNI signaling (none). The default value is uni31. For lines that will support ABR SVCs, select uni40. The UNI ports at each end of a virtual trunk SPVP must be set to none. SPVCs and SPVPs can use UNI 3.x or 4.0 signaling. -nniver When configuring PNNI signaling for an NNI port, you can use this option to specify which signaling protocol you want the port to use. You can select IISP version 3.0 (iisp30), IISP version 3.1 (iisp31), PNNI version 1.0 (pnni10), ENNI (enni), or AINI (aini). The NNI ports at each end of a virtual trunk SPVP must be set to none. -unitype When configuring PNNI signaling for a UNI port, you can use this option to specify the UNI type. You can define the port as a private UNI port (private) or as a public UNI port (public). The default value is private . -addrplan When configuring PNNI signaling for a UNI port, this parameter specifies the ATM address plan used on this port. You can select AESA (aesa), E.164 (e164), or both (both). The default value is aesa. -side Defines the role of the signaling service used on the port. This parameter applies to IISP ports when static addressing is used (address registration is disabled). If this is a UNI connection or an NNI connection within the network, select network. For connections to other networks, you might need to select user (this is negotiated with the administrators of the other network). The default value is network. -vpi Defines the VPI for signaling services on this port. Enter a value in the range from 0 to 4095. The default value is 0. -cntlvc This option defines a feeder trunk. The syntax for the feeder trunk definition is: pop20two.7.PXM.a > cnfpnportsig <portid> -cntlvc ip Cisco SES PNNI Controller Software Configuration Guide 3-28 Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 Chapter 3 Provisioning Communication Links SES Controller Configuration and Verification Procedures Table 3-3 Note Port Signaling Configuration Parameters (continued) Parameter Description -sigvci Defines the VCI for signaling services on this port. The default value is 5, which is the well-known, reserved VCI for signaling services on VPI 0. If you choose another VCI for signaling, choose a VCI value in the range from 32 to 65535. Otherwise, the VCI can conflict with other VCIs in the reserved range from 0 to 31 on VPI 0. -rccvci Defines the VCI for the PNNI Routing Control Connection (RCC) on this port. The default value is 18, which is the well-known, reserved VCI for this services on VPI 0. If you choose another VCI for signaling, choose a VCI value in the range of 32 to 65535. Otherwise, the VCI can conflict with other VCIs in the reserved range from 0 to 31 on VPI 0. The selection of UNI or NNI is made when the port is added with the uptrk or upln command. You cannot use the -univer and -nniver options to change the port type. The following example illustrates how to configure VSI trunk to use PNNI Version 1.0 signaling. SES_CH.1.PXM.a > cnfpnportsig 1.2 -nniver pnni10 Step 6 Use the following command to define the local routing switch feeder port as a non-OAM segment endpoint: SES_CH.1.PXM.a > cnfoamsegep <slot.port> Replace <slot.port> with the slot number of the card and the physical port identifier. This step is required to enable testing with the tstdelay command. Step 7 Use the following command to bring up the port you just configured: SES_CH.1.PXM.a > uppnport <slot.port> Step 8 To verify the status of the port, enter the dsppnports command. Step 9 To display the configuration of the PNNI port, enter the following command: SES_CH.1.PXM.a > dsppnport <slot.port> Cisco SES PNNI Controller Software Configuration Guide Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 3-29 Chapter 3 Provisioning Communication Links SES Controller Configuration and Verification Procedures The following example shows the report for the dsppnport command. SES_CH.1.PXM.a > dsppnport 1.2 Port: IF status: UCSM: Auto-config: IF-side: UniType: PassAlongCapab: Input filter: minSvccVpi: minSvccVci: minSvpcVpi: p2p : p2mp: p2p : p2mp: #SpvcCfg: 0 0 #Svcc: 0 0 1.2 up enable enable network private n/a 0 1 35 1 #SpvcActive: 0 0 #Svpc: 0 0 Logical ID: Admin Status: 66048 up Addrs-reg: IF-type: Version: enable nni pnni10 Output filter: maxSvccVpi: maxSvccVci: maxSvpcVpi: 0 4095 65535 4095 #SpvpCfg: 0 0 Total: 0 0 Total: #SpvpActive: 0 0 0 Verifying PNNI Trunk Communications After you configure both ends of a PNNI trunk, it should be ready to support SVCs and any SPVCs or SPVPs that are configured. To verify that the trunk is functioning, use the following procedure. Step 1 Establish a CLI session using a user name at any access level. Step 2 If you do not know the line number you are validating, you can view the port and line numbers by entering the dsppnports command. Step 3 Enter the dsppnni-link command as follows: SES_CH.1.PXM.a > dsppnni-link The dsppnni-link command displays a report for every PNNI link on the switch. The following example shows the report for a switch with a single PNNI link. SES_CH.1.PXM.a > dsppnni-link node index : 1 Local port id: 66048 Remote port id: 66304 Local Phy Port Id: 1:0.2:0 Type. lowestLevelOutsideLink Hello state.......twoWayOutside Derive agg........... 0 Intf index........... 66048 SVC RCC index........ 0 Hello pkt RX......... 4032 Hello pkt TX......... 3969 Remote node name....... Remote node id.........56:160:47.009181000001003071f813a1.003071f813a1.01 Upnode id..............0:0:00.000000000000000000000000.000000000000.00 Upnode ATM addr........00.000000000000000000000000.000000000000.00 Common peer group id...00:00.00.0000.0000.0000.0000.0000.00 Cisco SES PNNI Controller Software Configuration Guide 3-30 Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 Chapter 3 Provisioning Communication Links SES Controller Configuration and Verification Procedures In the dsppnni-link command report, there should be an entry for the port for which you are verifying communications. The Local Phy Port Id field in this entry displays the port id in the same format shown in the dsppnports command report. The Hello state reported for the port should be twoWayInside or twoWay Outside, and the Remote note ID should display the remote node ATM address after the second colon. (An inside link is a link between two PNNI nodes in the same peer group, and an outside link is a link between two nodes in different peer groups.) In the example above, the report shown is for port 1.2. The Hello state is twoWayOutside, and the ATM address of the node at the other end of the link is 47.009181000001003071f813a1.003071f813a1.01. This link is ready to support connections between the two switches. Tips If the Hello state for the link is oneWayInside, that side is trying to communicate. Check the status at the other end. Remember that the configuration at each end of the trunk must be compatible with that on the other end. For example, if ILMI auto configuration is configured at one end and not at the other, the Hello state cannot change to twoWayInside or twoWayOutside. Setting Up SVCs After you have configured the UNI ports, NNI trunks, and PNNI, you can provision SVCs and SPVCs in your network. This section describes how to set up an SVC. A two-node network is used to describe the SVC setup procedure. (See Figure 3-1). SVC Setup Example orioses3 CPE #1 UNI BPX/ 1.3 SES #1 orioses1 PNNI 1.2 1.2 BPX/ UNI SES #2 1.8 CPE #2 56137 Figure 3-1 Cisco SES PNNI Controller Software Configuration Guide Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 3-31 Chapter 3 Provisioning Communication Links SES Controller Configuration and Verification Procedures Setting up an SVC without ILMI Address Registration Use the following procedure to set up an SVC without ILMI address registration between two SES nodes. In the following example, the user sets up addresses on orioses1 and orioses3 before placing the SVC call. The CPE ATM Addresses are as follows: Step 1 • CPE #1— 47.00918100000000d058ac26b6.000000010800.00. • CPE #2— 47.00918100000000107bc154b5.000000010300.00. Enter the addaddr command to add the CPE#1 ATM address to the first SES node. In the following example, the user adds the CPE #1 ATM address to UNI port 1.3 on orioses3: orioses3.1.1.PXM.a > addaddr 1.3 47.00918100000000d058ac26b6.000000010800.00 160 Note Step 2 Note Once you add an address, it is propagated to all the other addresses on the node. If you want to summarize different addresses on the node into one single address, enter the addpnni-summary-addr command to add an ATM summary address on the first SES. This step is optional. You do not need a summary address to setup SVCs. In the following example, the user adds the ATM summary address on orioses3: orioses3.1.1.PXM.a > addpnni-summary-addr 1 47.00918100000000d058ac26b6 104 Step 3 Enter the addaddr command to add the CPE#2 ATM address to the second SES node. In the following example, the user adds the CPE #2 ATM address to UNI port 1.8 on orioses1: orioses1.1.1.PXM.a > addaddr 1.8 47.00918100000000107bc154b5.000000010300.00 160 Step 4 Enter the addpnni-summary-addr command to add an ATM summary address on the second SES. In the following example, the user adds the ATM summary address on orioses1: orioses1.1.1.PXM.a > addpnni-summary-addr 1 47.00918100000000107bc154b5 104 Step 5 Enter the dsppnni-reachable-addr network command to see the summary address of the other node. orioses1.1.1.PXM.a > dsppnni-reachable network Step 6 Place a SVC call from CPE #1 to CPE #2. Cisco SES PNNI Controller Software Configuration Guide 3-32 Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 Chapter 3 Provisioning Communication Links SES Controller Configuration and Verification Procedures Step 7 Enter the dsppncons command to display SVC connection between two nodes. A System response similar to the following occurs: -----------------------------------------------------------------------------orioses3.1.1.PXM.a > dsppncons Port VPI VCI CallRef X-Port VPI VCI CallRef Type OAM-Type 1.2 1 42 11 1.3 99 999 11 PTP Yes Calling-Addr:47.00918100000000d058ac26b6.000000010800.00 Called-Addr:47.00918100000000107bc154b5.000000010300.00 1.3 99 999 11 1.2 1 42 11 PTP Yes Calling-Addr:47.00918100000000d058ac26b6.000000010800.00 Called-Addr:47.00918100000000107bc154b5.000000010300.00 ------------------------------------------------------------------------------ Setting up an SVC with ILMI Address Registration Use the following procedure to setup an SVC with ILMI address registration: Step 1 Use the cnfport command to configure a port on the first SES with ILMI enabled. In the following example, the user enables ILMI on UNI port 1.3 on orioses3: Step 2 Use the cnfport command to configure orioses1 UNI 1.8 with ILMI enabled. orioses3.1.1.PXM.a > addaddr 1.3 47.00918100000000d058ac26b6.000000010800.00 160 Note Step 3 Make sure both CPE#1 and CPE#2 have ILMI turned on. Enter the addprfx command to add a prefix on the first SES controller. In the following example, the user adds a prefix to UNI port 1.3 on orioses3: orioses3.1.1.PXM.a > addprfx 1.3 47.00918100000000d058ac26b6 Step 4 Enter the addprfx command to add a prefix on the second SES controller. In the following example, the user adds a prefix to UNI port 1.8 on orioses1: orioses1.1.1.PXM.a > addprfx 1.8 47.00918100000000107bc154b5 Note Step 5 You must enter the add and address prefix to both controllers. Enter the dsppnni-reachable-addr local command to display the registered address. orioses1.1.1.PXM.a > dsppnni-reachable-addr local A system response similar to the following example occurs: orioses1.1.1.PXM.a > dsppnni-reachable-addr local scope............... 56 port id............. Exterior............ false ATM addr prefix.....47.0091.8100.0000.0010.7bc1.54b/5 2 Cisco SES PNNI Controller Software Configuration Guide Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 3-33 Chapter 3 Provisioning Communication Links SES Controller Configuration and Verification Procedures Step 6 Place an SVC call from CPE #1 to CPE #2, using the ATM address of the first SES controller, combined with the MAC address of CPE#2. In the following example, a call is placed to the ATM address of orioses3, where 00d058ac4021 is the MAC addr of CPE#2: 47.00918100000000d058ac26b6.00d058ac4021.00 Configuring SPVCs and SPVPs You can provision an SPVC through the SES controller CLI or through CWM. This section describes how to use the SES controller CLI to provision an SPVC. To provision an SPVC through CWM, refer to Chapter 7, “Network Management.” SPVCs and SPVPs are created between two ATM CPE and must be configured at each endpoint. The master endpoint is responsible for routing and rerouting. The slave endpoint is responsible for responding to requests from the master during connection setup and rerouting. Both endpoints are configured on the switch to which the ATM CPE connects. These endpoints can be on the same switch or on different switches. The master and slave relationships exist for each SPVC or SPVP and apply only to the SPVC or SPVP connection. For example, you can have one SPVC with a master on Node A and a slave on Node B, and then create another with the Master on Node B and the slave on Node A. It is good practice to distribute the master side of SPVCs and SPVPs among the network nodes so that route processing is distributed. The following sections describe how to configure slave and master SPVC and SPVP connections. Tips The configuration of SPVCs and SPVPs is very similar. The difference is that SPVPs are assigned VCI 0 and do not use nonzero VCI numbers. An SPVC requires a nonzero VCI. Configuring the Slave Side of SPVCs and SPVPs To configure the slave side of an SPVC or SPVP, use the following procedure. Step 1 Establish a configuration session on the SES controller using a user name with GROUP1 privileges or higher. Step 2 Define the slave side of the SPVC by entering the following command: SES_SJ.1.PXM.a > addcon <slot.port> <vpi> <vci> <serviceType> <mastership> [-lpcr <cellrate>] [-rpcr <cellrate>] [-lscr <cellrate>] [-rscr <cellrate>] [-lmbs <cells>] [-rmbs <cells>] [-lcdv <time>] [-rcdv <time>] [-lctd <time>] [-rctd <time>] [-lmcr <cellrate>] [-rmcr <cellrate>] [-cdvt <time>] [-icr <cellrate>] [-int_vsvd <1/2/3>] [-ext_vsvd <1/2/3>] [-stats <1|0>] [-frame <1|0>] [-mc <maxCost>] Caution Once you create an SPVC connection, you cannot change the SPVC prefix until all SPVC connections have been deleted. The procedure for changing the SPVC prefix is described in “Setting and Viewing the SPVC Prefix,” in Chapter 2, “Configuring General Switch Features.” Cisco SES PNNI Controller Software Configuration Guide 3-34 Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 Chapter 3 Provisioning Communication Links SES Controller Configuration and Verification Procedures Table 3-4 lists and defines the parameters and options for the addcon command. The local and remote terms used in Table 3-4 refer to settings for the local port you are configuring and the remote port at the other end of the connection. If you omit an option, the SPVC uses the default value. Table 3-4 Parameters for the addcon Command Parameter Description slot.port Replace <slot.port> with the slot number of the card and the physical port identifier. vpi Enter the VPI for the slave side of the SPVC. The VPI must be within the range defined for the VSI partition on the BPX with the cnfrsrc command. vci Enter the VCI for the slave side of the SPVC or SPVP. SPVC Range: 32 to 65535. SPVP Range: 0. Note serviceType Cisco Systems, Inc., recommends setting the minimum VCI to 35 or higher. Future products will use VCI 32 through 34 for other services. Replace with the number that corresponds to the requested service type for this SPVC (this value must be identical on master and slave sides): cbr1 = 1 cbr2 = 11 cbr3 = 12 vbr1rt = 2 vbr2rt = 3 vbr3rt = 4 vbr1nrt = 5 vbr2nrt = 6 vbr3nrt = 7 ubr1 = 8 ubr2 = 9 abrstd = 10 mastership Enter 2 or s if this port will serve as the slave side of the connection. Enter 1 or m if the port serves as the master side of the connection. atmAddr.vpi.vci This parameter is used only when defining the master side of a connection. The value entered here should match the NSAP displayed after the slave side of the connection is defined. The atmAddr portion of the address corresponds to the remote ATM address and the vpi and vci parameters correspond to the VPI and VCI settings for the slave. The periods between atmAddrp and vpi and between vpi and vci are required. -lpcr -rpcr These options specify the local-to-remote (-lpcr) and remote-to-local (-rpcr) Peak Cell Rate (PCR) for the connection. The values defined at each connection end must correspond to the values set at the other end. For example, the PCR defined for the local-to-remote direction at one end must match the value set for the remote-to-local direction at the other end. Range cells per second: OC3: 7 to 353207. T3: 7 to 96000(PLCP) or 104268(ADM). E3: 7 to 80000. Default: 50 cells per second. Cisco SES PNNI Controller Software Configuration Guide Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 3-35 Chapter 3 Provisioning Communication Links SES Controller Configuration and Verification Procedures Table 3-4 Parameters for the addcon Command (continued) Parameter Description -lscr -rscr These options specify the local-to-remote (-lscr) and remote-to-local (-rscr) Sustained Cell Rate (SCR) for the connection. The values defined at each connection end must correspond to the values set at the other end. For example, the SCR defined for the local-to-remote direction at one end must match the value set for the remote-to-local direction at the other end. Range cells per second: OC3: 7 to 353207. T3: 7 to 96000(PLCP) or 104268(ADM). E3: 7 to 80000. Default: Uses -lpcer and -rpcr values. -lmbs -rmbs These options specify the local-to-remote (-lmbs) and remote-to-local (-rmbs) Maximum Burst Size (MBS) for the connection. The values defined at each connection end must correspond to the values set at the other end. For example, the MBS defined for the local-to-remote direction at one end must match the value set for the remote-to-local direction at the other end. Range: 1 to 5000000 cells. Default: 1024 cells. Note that you can change the default MBS with the cnfmbsdft command. -lcdv -rcdv These options specify the maximum Cell Delay Variation (CDV) desired for the connection. The -lcdv option defines the CDV setting for the local-to-remote direction, and the -rcdv option specifies the CDV for the remote-to-local direction. Range: 1 to 16777215 microseconds. Default: -1, parameter not used in route selection. -lctd -rctd These options specify the maximum Cell Transfer Delay (CTD) desired for the connection. The -lctd option defines the CTD setting for the local-to-remote direction, and the -rctd option specifies the CTD for the remote-to-local direction. Range: 1 to 65535 milliseconds. Default: -1, parameter not used in route selection. -lmcr> -rmcr These options specify the local-to-remote (-lmcr) and remote-to-local (-rmcr) Minimum Cell Rate (MCR) for the connection. The values defined at each connection end must correspond to the values set at the other end. For example, the MCR defined for the local-to-remote direction at one end must match the value set for the remote-to-local direction at the other end. Range cells per second: OC3: 7 to 353207. T3: 7 to 96000(PLCP) or 104268(ADM). E3: 7 to 80000. Default: Uses -lpcer and -rpcr values. Cisco SES PNNI Controller Software Configuration Guide 3-36 Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 Chapter 3 Provisioning Communication Links SES Controller Configuration and Verification Procedures Table 3-4 Parameters for the addcon Command (continued) Parameter Description -cdvt This option specifies the local Cell Delay Variation Tolerance (CDVT) for the SPVC. Range: 1 to 5000000 microseconds. Default: 250,000 microseconds. Note that you can change the default CDVT with the cnfcdvtdft command. -icr This optional keyword can be used for specifying the ICR required for the connection in the local -> remote direction. Default = lpcr. -int_vsvd Internal Segment VSVD: 1 (off) / 2 (on) /3 (unspe -ext_vsvd External Segment VSVD: 1 (off) / 2 (on) /3 (unspec). Default = off. -stats This option enables or disables statistics collection for the SPVC. Enter 1 to enable OAM statistics collection, or enter 0 to disable it. Default: 0, disabled. -frame This option enables or disables frame discard. Enter 1 to enable frame discard, or enter 0 to disable it. Default: 0, disabled. -mc The maximum cost option assigns a maximum acceptable cost value to the connection. When a connection is being established, there can be multiple routes available. The cost of the connection over each route is the sum of the Administrative Weight (AW) values assigned to the links along that route. The connection will not be attempted across any route for which the total cost exceeds the value set for this option. Range: 0 to 16777215 microseconds Default: -1, no maximum cost required for route. Note The AW for each link is set with the cnfpnni-intf command. For more information, refer to the Cisco SES PNNI Controller Software Command Reference, Release 1.1. Tips The PCR, MBS, CDVT, CDV, MCR, and CTD configuration options are optional. If you omit one of these options when entering the addcon command, the connection uses the default value listed in Table 3-4. To override the default values for any option, enter the option with a new value. Note You can configure additional ABR parameters with the cnfabr and cnfabrtparmdft commands. For more information, refer to the Cisco SES PNNI Controller Software Command Reference, Release 1.1. The following command example defines a port as the slave side of an SPVC. Note the slave id shown in the command response. SES_SJ.1.PXM.a > addcon 1.5 100 100 1 2 LOCAL ADDR: 47009181000000003071F813A100000001050000.100.100 Cisco SES PNNI Controller Software Configuration Guide Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 3-37 Chapter 3 Provisioning Communication Links SES Controller Configuration and Verification Procedures Step 3 Tips Step 4 Write down the local address the SES controller displays when the addcon command is complete. You will need this to configure the master side of the SPVC. When you set up the master side of the connection, you will have to enter the slave ATM address reported by the addcon command. If you maintain the current session or use the session Copy command to copy the ATM address now, you can use the session Paste command to complete the addcon command on the switch that hosts the master side of the connection. Verify the slave-side SPVC addition by entering the following command: SES_SJ.1.PXM.a > dspcons Local Port Vpi.Vci Remote Port Vpi.Vci State Owner ----------------------------+-----------------------------+-------+-----1.5 100 100 Routed 0 0 FAIL SLAVE Local Addr: 47.009181000000003071f813a1.000000010500.00 Remote Addr: 00.000000000000000000000000.000000000000.00 Configuring the Master Side of SPVCs and SPVPs To configure the master side of an SPVC, use the following procedure. Step 1 Tips Step 2 Establish a configuration session on the SES controller using a user name with GROUP1 privileges or higher. During this procedure, you will have to enter the ATM address for the slave end of the connection. If you establish this session from the same workstation you used to create the slave connection, you can use the Copy and Paste commands to avoid data entry errors. Define the master side of the SPVC by entering the following command: SES_CH.1.PXM.a > addcon <ifNum> <vpi> <vci> <serviceType> <mastership> <atmAddr.vpi.vci> [-lpcr <cellrate>] [-rpcr <cellrate>] [-lscr <cellrate>] [-rscr <cellrate>] [-lmbs <cells>] [-rmbs <cells>] [-cdvt <time>] [-lcdv <time>] [-rcdv <time>] [-lctd <time>] [-rctd <time>] [-icr <cellrate>] [-int_vsvd <1/2/3>] [-ext_vsvd <1/2/3>] [-stat <1|0>] [-frame <1|0>] [-mc <maxCost>] Table 3-4 lists and defines the parameters and options for this command. If you omit an option, the SPVC uses the default value. Tips The PCR, MBS, CDVT, CDV, MCR, and CTD configuration options are optional. If you omit one of these options when entering the addcon command, the connection uses the default value listed in Table 3-4. To override the default values for any option, enter the option with a new value. The following command example defines a port as the master side of an SPVC. SES_CH.1.PXM.a > addcon 1.4 100 100 1 1 47009181000000003071F813A100000001050000.100.100 Cisco SES PNNI Controller Software Configuration Guide 3-38 Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 Chapter 3 Provisioning Communication Links SES Controller Configuration and Verification Procedures Step 3 Verify the master-side SPVC addition by entering the following command: SES_CH.1.PXM.a > dspcons The switch displays a report showing all connections. The following example show a report for a switch with one connection: SES_CH.1.PXM.a > dspcons Local Port Vpi.Vci Remote Port Vpi.Vci State Owner ----------------------------+-----------------------------+-------+-----1.4 100 100 Routed 100 100 OK MASTER Local Addr: 47.009181000000003071f81ae7.000000010400.00 Remote Addr: 47.009181000000003071f813a1.000000010500.00 Step 4 To display the configuration for a single connection, enter the following command: SES_CH.1.PXM.a > dspcon ifNum vpi vci Replace the ifNum parameter with the interface or port number. The vpi and vci parameters are described in Table 3-4. The following example shows a dspcon command report. SES_CH.1.PXM.a > dspcon 1.4 100 100 Port Vpi Vci Owner State ------------------------------------------------------------------------Local 1:-1.4:-1 100.100 MASTER OK Address: 47.009181000000003071f81ae7.000000010400.00 Node name: SES_CH Remote Routed 100.100 SLAVE -Address: 47.009181000000003071f813a1.000000010500.00 Node name: SES_SJ -------------------- Provisioning Parameters -------------------Connection Type: VCC Cast Type: Point-to-Point Service Category: CBR Conformance: CBR.1 Bearer Class: BCOB-X Last Fail Cause: No Fail Attempts: 0 Continuity Check: Disabled Frame Discard: Disabled L-Utils: 100 R-Utils: 100 Max Cost: -1 Routing Cost: 10080 OAM Segment Ep: Enabled ---------- Traffic Parameters ---------Tx PCR: 50 Rx PCR: 50 Tx CDV: -1 Rx CDV: -1 Tx CTD: -1 Rx CTD: -1 Type <CR> to continue, Q<CR> to stop: ------- SES Parameters only ---------Tx AIS: 0 Rx AIS: 0 Rx Abit:0 lpbk_type : No Loopback lpbk_dir : ---lpbk_status : None round trip delay: 0 usec Stats : Disabled The -1 entries in the example above indicate that a value was not specified with the addcon command. The N/A entries indicate that a value is not applicable to connections with this service type. Cisco SES PNNI Controller Software Configuration Guide Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 3-39 Chapter 3 Provisioning Communication Links Configuring MGX 8850 Release 1 Feeder Connections Configuring MGX 8850 Release 1 Feeder Connections Use the following procedure to setup an SPVC feeder connection between an MGX 8850 Release 1 switch and an SES Controlled BPX switch. Note Configure the feeder node feeder trunk with Service Class Template (SCT) 3 to disable the policing for SPVCs terminating on the feeder trunk. Setting Up the MGX 8850 End of the Feeder Trunk Use the following procedure to configure the MGX 8850 feeder trunk. Note Step 1 LMI/Annex G must be enabled on the feeder node feeder trunk. Enter the addln command to configure the feeder trunk. jcfb8850.1.7.PXM.a > addln -sonet 7.1 Step 2 Enter the addport command to add the port. cfb8850.1.7.PXM.a > addport <port_number> <line_number> <percent_bandwidth> <min_vpi> <max_vpi> Replace <port_number> with the port number to be added, in the range 1-32. Replace <line_number> with the line number. Replace <percent_bandwidth> with the percentage of bandwidth to be allocated to the port, in the range 1-100. Replace <min_vpi> with the minimum VPI value, in the range 0-4095. Replace <max_vpi> with the maximum VPI value, in the range 0-4095. Step 3 Enter the cnfswfunc command to enable VS/VD and set the node type as fdr (feeder). jcfb8850.1.7.PXM.a > cnfswfunc -vsvd yes -ndtype fdr Step 4 Enter the cnfifastrk command to configure the logical interface as a feeder trunk. jcfb8850.1.7.PXM.a > cnfifastrk <slot.port> fdr Replace <slot.port> with the slot and port number of the interface. Cisco SES PNNI Controller Software Configuration Guide 3-40 Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 Chapter 3 Provisioning Communication Links Configuring MGX 8850 Release 1 Feeder Connections Step 5 Enter the dspln command to display the new line’s parameters. jcfb8850.1.7.PXM.a > dspln <-ds3|-e3|-sonet> <line number> Replace <-ds3|-e3 |-sonet> with the line type. Replace <line number> with the line number in the format slot.line. A system response similar to the following example occurs: jcfb8850.1.7.PXM.a > dspln -sonet 7.1 sonetLineNum: 1 sonetLineType: sonetSts3c sonetLineLoopback: NoLoop sonetHCSmasking: Enabled sonetPayloadScramble: Enabled sonetFrameScramble: Enabled sonetLineEnable: Enabled sonetMediumType: sonet sonetMediumTimeElapsed: 112 sonetMediumValidIntervals: 0 sonetMediumLineCoding: Other sonetMediumLineType: ShortSingleMode sonetMediumCircuitIdentifier: Sonet Line Step 6 Enter the addport command to create a logical port. cfb8850.1.7.PXM.a > addport <port_number> <line_number> <percent_bandwidth> <min_vpi> <max_vpi> Replace <port_number> with the port number to be added, in the range 1-32. Replace <line_number> with the line number. Replace <percent_bandwidth> with the percentage of bandwidth to be allocated to the port, in the range 1-100. Replace <min_vpi> with the minimum VPI value, in the range 0-4095. Replace <max_vpi> with the maximum VPI value, in the range 0-4095. Step 7 Enter the dspports command to display the new logical port’s parameters. jcfb8850.1.7.PXM.a > dspports A system response similar to the following example occurs: jcfb8850.1.7.PXM.a > dspports Port Status Line PctBw minVpi maxVpi maxRatePct -----------------------------------------------------1 ON 1 100 0 4095 100 Step 8 Enter the cnfswfunc command to enable VS/VD and set the node type as fdr (feeder). jcfb8850.1.7.PXM.a > cnfswfunc -vsvd yes -ndtype fdr Step 9 Enter the dspifs command to display the interface parameters. jcfb8850.1.7.PXM.a > dspifs A system response similar to the following example occurs: jcfb8850.1.7.PXM.a > dspifs ifNum Status Line ingrPctBw egrPctBw minVpi maxVpi maxRatePct ------------------------------------------------------------------1 Ena 1 100 100 0 4095 100 Cisco SES PNNI Controller Software Configuration Guide Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 3-41 Chapter 3 Provisioning Communication Links Configuring MGX 8850 Release 1 Feeder Connections Setting Up the SPVC Feeder Segment on the SES Use the following steps to set up an SPVC segment in PNNI network. Make sure the VPI/VCI used for SPVC segment matches the vpi/vci used by the PVC segment configured on the same feeder trunk. Step 1 Enter the dsppnports command to display all PNNI ports. A system response similar to the following example occurs: sjses58.1.PXM.a > dsppnports Summary of total connections (p2p=point to point,p2mp=point to Type #Svcc: #Svpc: #SpvcD: p2p: 0 0 0 p2mp: 0 0 0 multipoint,SpvcD=DAX spvc,SpvcR=Routed spvc) #SpvpD: #SpvcR: #SpvpR: #Total: 0 0 0 0 0 0 0 0 Total=0 Summary of total configured SPVC endpoints Type #SpvcCfg: #SpvpCfg: p2p: 0 0 p2mp: 0 0 Per-port status summary Step 2 PortId IF status Admin status ILMI state #Conns 3.1 up up Disable 0 3.4 up up Disable 0 10.1 up up Disable 0 10.5 up up Disable 0 10.8 up up Disable 0 Enter the dsppnport command to view status information for a specific port. sjses58.1.PXM.a > dsppnport 3.4 Port: 3.4 IF status: up UCSM: enable Auto-config: enable IF-side: network UniType: private Input filter: 0 minSvccVpi: 4 minSvccVci: 35 minSvpcVpi: 4 #SpvcCfg: #SpvcActive: p2p : 0 0 p2mp: 0 0 #Svcc: #Svpc: p2p : 0 0 p2mp: 0 0 Step 3 Logical Id: Admin Status: 197632 up Addrs-reg: enable IF-type: uni version: uni3.1 Output filter: 0 maxSvccVpi: 4095 maxSvccVci: 65535 maxSvpcVpi: 4095 #SpvpCfg: #SpvpActive: 0 0 0 0 Total: 0 0 Total : 0 Enter the cnfoamsegep command to disable the OAM segment endpoint on the feeder trunk. jceases.1.PXM.a > cnfoamsegep <portid> no Replace <portid> with the port identifier. Cisco SES PNNI Controller Software Configuration Guide 3-42 Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 Chapter 3 Provisioning Communication Links Configuring MGX 8850 Release 1 Feeder Connections Step 4 Enter the dspoamsegep command to make sure the OAM segment endpoint is disabled. A system response similar to the following example occurs: jceases.1.PXM.a > dspoamsegep 3.4 Port 3.4 Step 5 OAM End Point No Enter the addcon command to add a slave endpoint connection. pswpop9.1.PXM.a > addcon <portid> <vpi> <vci> <serviceType> <master_ship> <slave_nsap.vpi.vci> Refer to Table 3-5 at the end of this section for a description of the addcon parameters. In the following example, the user configures a slave connection on port 3.4 with a starting VPI of 5, a starting VCI of 100, and CBR service. The slave_nsap is 47009181000000003071F8030D00000003040000.5.100. sjses58.1.PXM.a > addcon 3.4 5 100 1 2 LOCAL ADDR: 47009181000000003071F8030D00000003040000.5.100 Step 6 Enter the addcon command to add a master endpoint connection: pswpop9.1.PXM.a > addcon <portid> <vpi> <vci> <serviceType> <master_ship> <slave_nsap.vpi.vci> Refer to Table 3-5 at the end of this section for a description of the addcon parameters. In the following example, the user configures a master connection on port 3.4 with a starting VPI of 6, a starting VCI of 100, and CBR service. The slave_nsap is 47009181000000003071F8030D00000003040000.5.100. sjses58.1.PXM.a > addcon 3.4 6 100 1 1 47009181000000003071F8030D00000003040000.5.100 Cisco SES PNNI Controller Software Configuration Guide Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 3-43 Chapter 3 Provisioning Communication Links Configuring MGX 8850 Release 1 Feeder Connections Step 7 Enter the dspcons command to verify that the connection you added in Step 5 appears: orioses1.1.1.PXM.a > dsppncons A system response similar to the following example occurs: sjses58.1.PXM.a > dspcons Local Port Vpi.Vci Remote Port Vpi.Vci State Owner ----------------------------+-----------------------------+-------+---3.4 5 100 3.4 6 100 OK SLAVE Local Addr: 47.009181000000003071f8030d.000000030400.00 Remote Addr: 47.009181000000003071f8030d.000000030400.00 3.4 6 100 3.4 5 100 OK MASTER Local Addr: 47.009181000000003071f8030d.000000030400.00 Remote Addr: 47.009181000000003071f8030d.000000030400.00 jceases.1.PXM.a > dsppncons Port VPI VCI CallRef X-Port VPI VCI AM-Type 3.4 5 100 2 3.4 6 100 Yes Calling-Addr: 47.009181000000003071f8030d.000000030400.00 Called-Addr: 47.009181000000003071f8030d.000000030400.00 3.4 6 100 1 3.4 5 100 Yes Calling-Addr: 47.009181000000003071f8030d.000000030400.00 Called-Addr: 47.009181000000003071f8030d.000000030400.00 CallRef Type O 1 PTP 2 PTP Setting Up the PVC Segment on an MGX 8850 Feeder Node Follow these steps to set up the PVC segment on each FrameRelay port on an MGX 8850, Release 1 feeder node. Step 1 Enter the cc command to change to card 3. jcfb8850.1.7.PXM.a > cc <slot number> Replace <slot number> with the slot number of the card you with to change to. Step 2 Enter the addln command to change to add a line. jcfb8850.1.3.FRSM.a > addln <LineNum> Replace <LineNum> with the corresponding line number. Cisco SES PNNI Controller Software Configuration Guide 3-44 Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 Chapter 3 Provisioning Communication Links Configuring MGX 8850 Release 1 Feeder Connections Step 3 Enter the dspln command on the new line to be sure the line was added: jcfb8850.1.3.FRSM.a > dspln <LineNum> Replace <LineNum> with the corresponding line number. A system response similar to the following example occurs: jcfb8850.1.3.FRSM.a > dspln 1 LineNum: LineConnectorType: LineType: LineEnable: LineCoding: LineLength: LineXmtClockSource: LineLoopbackCommand: LineSendCode: LineUsedTimeslotsBitMap: LineLoopbackCodeDetection: LineBertEnable: 1 RJ-48 dsx1ESF Enabled dsx1B8ZS 0-131 ft LocalTiming NoLoop NoCode 0xffffff codeDetectDisabled Disable LineNumOfValidEntries: 8 Step 4 Enter the addport command to add a port: jcfb8850.1.3.FRSM.a > addport <port_number> <line_number> <ds0_speed> <begin_slot> <num_slot> <port_type> Replace <port_number> with the port identifier. Replace <line_number> with the line number. Replace <ds0_speed> with the bit rate for the DS0; type “1” for 56 Kbps, or “2” for 64 Kbps. Replace <begin_slot> with the number of the beginning timeslot in the T1 or E1 frame. Replace <num_slot> with Number of consecutive timeslots in the T1 or E1 frame. Replace <port_type> with the type of service; type “1” for Frame Relay, “2” for FUNI, or “3” for frame forwarding. In the following example, the user configures port 1, line 1 with a DS0 bit rate of 56 Kbps. jcfb8850.1.3.FRSM.a > addport 1 1 2 1 7 1 Step 5 Enter the dspports command on the new line to verify the port was added: A system response similar to the following example occurs: jcfb8850.1.3.FRSM.a > dspports Port Ena/Speed EQServ SignalType T391 T392 N391 N392 N393 Type Alar ELMI Ratio -------- --- ----- ------ ------------ ---- ---- ---- ---- ---- -------- ---- ---3.1.1 Mod/1536k 1 NoSignalling 10 15 6 3 4 frameRel No Off Step 6 Enter the addcon command to add a new connection. Note The parameters for this command vary depending on the card type. For more information on how this command should be entered for each specific card, refer to the Cisco MGX 8800 Series Command Reference. The following example shows the addcon command on a FRSM card: jcfb8850.1.3.FRSM.a > addcon 1 101 15360 1 1 1 1 jcfb8850.0.1.5.100 9 Cisco SES PNNI Controller Software Configuration Guide Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 3-45 Chapter 3 Provisioning Communication Links Configuring MGX 8850 Release 1 Feeder Connections Step 7 Enter the dspchans command to be sure the connection was added properly. A system response similar to the following example occurs: jcfb8850.1.3.FRSM.a > dspchans DLCI Chan EQ ServType I/EQDepth I/EQDEThre I/EECNThre Fst/ DE Type Alarm ------------- ---- -- -------- ----- ----- ----- ----- ----- ----- --- --- ----- ----3.1.1.101 16 2 stdABR 65535/65535 32767/32767 6553/6553 Dis/Dis NIW No Number of channels: 1 ChanNumNextAvailable: 17 Use the following procedure to set up the second PVC Connection on Second Service Module (Frame Relay) Card #2. Step 8 Enter the cc command to change to card 3. cc jcfb8850.1.7.PXM.a > cc <slot number> Replace <slot number> with the slot number of the card you with to change to. In the following example, card 2 is a VHS card: jcfb8850.1.7.PXM.a > cc 2 Step 9 Enter the addln command to add a line: jcfb8850.1.2.VHS2CT3.a > addln <line number> Replace <line number> with the number of the line you want to add. Note Step 10 The parameters for this command vary depending on the card type. For more information on how this command should be entered for each specific card, refer to the Cisco MGX 8800 Series Command Reference. Enter the addport command to change to add a port: jcfb8850.1.2.VHS2CT3.a > addport <port_number> <line_number> <ds0_speed> <begin_slot> <num_slot> <port_type> Replace <port_number> with the port identifier. Replace <line_number> with the line number. Replace <ds0_speed> with the bit rate for the DS0; type “1” for 56 Kbps, or “2” for 64 Kbps. Replace <begin_slot> with the number of the beginning timeslot in the T1 or E1 frame. Replace <num_slot> with Number of consecutive timeslots in the T1 or E1 frame. Replace <port_type> with the type of service; type “1” for Frame Relay, “2” for FUNI, or “3” for frame forwarding. In the following example, the card is a VHS card: jcfb8850.1.2.VHS2CT3.a > addport 1 1 2 1 7 1 Cisco SES PNNI Controller Software Configuration Guide 3-46 Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 Chapter 3 Provisioning Communication Links Configuring MGX 8850 Release 1 Feeder Connections Step 11 Enter the dspports command on the new line to be sure the port was added. jcfb8850.1.2.VHS2CT3.a > dspports Port ---2.1.1 Step 12 Note Ena/Speed --------Add/ 448k EQServ SignalType Ratio ------ ----------n/a NoSignalling Number of ports: 1 PortNumNextAvailable: 2 T391 T392 N391 N392 N393 Type Alarm ELMI ---- ---- ---- ---- ---- ---- ----- ---10 15 6 3 4 frameRel No Off Enter the addcon command to add a new connection. The parameters for this command vary depending on the card type. For more information on how this command should be entered for each specific card, refer to the Cisco MGX 8800 Series Command Reference. The following example shows the addcon command on a VHS card: jcfb8850.1.2.VHS2CT3.a > addcon 1 200 15360 1 1 2 1 1 jcfb8850.0.1.6.100 Step 13 Enter the dspcons command on the new connection to be sure it was added properly. A system response similar to the following example occurs: jcfb8850.1.2.VHS2CT3.a > dspcons Line ConnId Chan EgrQ ServType I/EQDepth I/EQDEThre I/EECNThre Fst/ DE Type Alarm ---- ------------------- ---- ---- --------- ---- ----- ----- ----- ----- ----- --- ------- ----1 jcfb8850.2.1.0.200 21 n/a CBR 65535/65535 32767/32767 6553/6553 Dis/Dis NIW Yes ChanNumNextAvailable: Step 14 22 Enter the dspchans command to display all channels on the node. A system response similar to the following example occurs: jcfb8850.1.2.VHS2CT3.a > dspchans DLCI --------2.1.1.200 Chan EgrQ ServType I/EQDepth I/EQDEThre I/EECNThre Fst/ DE Type Alarm ---- ---- -------- ----- ----- ----- ----- ----- ----- --- --- ----- ----21 n/a CBR 65535/65535 32767/32767 6553/6553 Dis/Dis NIW Yes Number of channels: 1 ChanNumNextAvailable: 23 jcfb8850.1.2.VHS2CT3.a > dspchans DLCI --------2.1.1.200 Chan EgrQ ServType I/EQDepth I/EQDEThre I/EECNThre Fst/ DE Type Alarm ---- ---- -------- ----- ----- ----- ----- ----- ----- --- --- ----- ----21 n/a CBR 65535/65535 32767/32767 6553/6553 Dis/Dis NIW Yes Number of channels: 1 ChanNumNextAvailable: 24 Cisco SES PNNI Controller Software Configuration Guide Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 3-47 Chapter 3 Provisioning Communication Links Configuring MGX 8850 Release 1 Feeder Connections Step 15 Enter the cc command to change to the PXM card. In the following example, the PXM is in slot 7. cc jcfb8850.1.7.PXM.a > cc <slot number> Replace <slot number> with the slot number of the card you with to change to. cc jcfb8850.1.7.PXM.a > cc 7 Step 16 Step 17 Enter the dspcons command to display a summary of Soft PVCs on all ports. A system response similar to the following example occurs: jcfb8850.1.7.PXM.a > dspcons This End Node Name Other End Status 2.1.0.200 3.1.0.101 7.1.5.100 7.1.6.100 7.1.6.100 7.1.5.100 3.1.0.101 2.1.0.200 OK OK OK OK jcfb8850 jcfb8850 jcfb8850 jcfb8850 Enter the cc command to change to the card you configured in Step 2 through Step 7. cc jcfb8850.1.7.PXM.a > cc <slot number> Replace <slot number> with the slot number of the card you with to change to. In the following example, card 3 is the FRSM card. jcfb8850.1.7.PXM.a > cc 3 (session redirected) Step 18 Enter the dspchans command to display all channels on the card. A system response similar to the following example occurs: jcfb8850.1.3.FRSM.a > dspchans DLCI Chan EQ ServType I/EQDepth I/EQDEThre I/EECNThre Fst/ DE Type Alarm ------------- ---- -- -------- ----- ----- ----- ----- ----- ----- --- --- ----- ----3.1.1.101 16 2 stdABR 65535/65535 32767/32767 6553/6553 Dis/Dis NIW Yes Step 19 Number of channels: 1 ChanNumNextAvailable: 17 Enter the tstdelay command to verify the continuity of the connection on the card in slot 3: jcfb8850.1.3.FRSM.a > tstdelay <channel number> Replace with <channel number> with a channel number appropriate for the card. A system response similar to the following example occurs: jcfb8850.1.3.FRSM.a > tstdelay 16 TestDelay in progress. TestDelay Passed with 41 ms. Cisco SES PNNI Controller Software Configuration Guide 3-48 Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 Chapter 3 Provisioning Communication Links Operating Procedures Step 20 Enter the cc command to change to the card you configured in Step 9 through Step 14. cc jcfb8850.1.7.PXM.a > cc <slot number> Replace <slot number> with the slot number of the card you with to change to. In the following example, card 2 is the VHS card. jcfb8850.1.3.FRSM.a > cc 2 (session redirected) Step 21 Enter the dspcons command to display all connections on the card. In the following example, the card is the VHS card in slot 2. jcfb8850.1.2.VHS2CT3.a > dspcons Line ConnId Chan EgrQ ServType I/EQDepth I/EQDEThre I/EECNThre Fst/ DE Type Alarm ---- ------------------- ---- ---- --------- ---- ----- ----- ----- ----- ----- --- ------- ----1 jcfb8850.2.1.0.200 26 n/a CBR 65535/65535 32767/32767 6553/6553 Dis/Dis NIW No ChanNumNextAvailable: Step 22 27 Enter the tstdelay command to verify the continuity of the connection on the card in slot 3: jcfb8850.1.3.FRSM.a > tstdelay <channel number> Replace with <channel number> with a channel number appropriate for the card. A system response similar to the following example occurs: jcfb8850.1.2.VHS2CT3.a > tstdelay 26 test type is..... 2 TestDelay in progress. TestDelay Passed with 50 ms. 2.1.1.200 21 n/a CBR Number of channels: 65535/65535 32767/32767 6553/6553 Dis/Dis NIW Yes 1 Operating Procedures This section decribes how to perform the following standard operating procedures on an SES controller: • Add a Port on the PXM • Bring up a Port on the PXM • Configure SPVC Statistics Collection • Configure the BXM Qbin • Modify an SPVC Connection • Delete an SPVC Connection • Change Partition Resources Cisco SES PNNI Controller Software Configuration Guide Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 3-49 Chapter 3 Provisioning Communication Links Operating Procedures Adding a Port on the PXM Ports are automatically added to the PXM when they are added as VSI ports on the BXM card. However, the SES controller software allows you to preconfigure PNNI ports before the BXM ports are brought up. You might want to do this when a BXM card is not installed and you do not want to wait to start configuration. To add a port on the PXM, enter the addpnport command as follows: sesone.1.PXM.a > addpnport <slot.port> Replace <slot.port> with the slot number of the card and the physical port identifier. Note When ports are added with the addpnport command, the ports are administratively down, by default. Once you have added the port, you can configure it. However, the port cannot start until the corresponding port on the BXM is configured and brought up. Bringing up a Port on the PXM Ports are automatically brought up on the PXM after the corresponding BXM port is configured. However, if you manually bring down a port, you must manually bring it back up with the uppnport command: sesone.1.PXM.a > uppnport <slot.port> Note Replace <slot.port> with the slot number of the card and the physical port identifier. Note The port cannot begin operation until the corresponding port on the BXM is brought up, configured, and operational. Configuring SPVC Statistics Collection The quickstart procedure in this section provides a summary of the tasks required to configure SPVC statistics collection on the SES controller Release 1.1 switch. This procedure is provided as an overview and as a quick reference for those who have previously configured these types of connections. Command Purpose Step 1 cnfcdparm Set the stats level on the BCC. Step 2 addcon -stats enable Add an SPVC connections with stats enabled. For existing SPVCs, use the cnfcon command to enable the -stats option. dsppnilmi Cisco SES PNNI Controller Software Configuration Guide 3-50 Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 Chapter 3 Provisioning Communication Links Operating Procedures Configuring the BXM Qbin The default Service Class Template is automatically assigned to the interface (VI) when you enter uptrk or upport to activate the interface. The corresponding Qbin template is then copied into the data structure of that interface at the BXM. Enter the cnfqbin command to manually configure Qbin parameters. Enter the dspqbin command to display Qbin configuration information. Qbin Dependencies The available Qbin parameters are shown in Table 3-5. Qbins 10-15 are available for VSI.There are 32 possible virtual interfaces, and each one has 16 Qbins. Table 3-5 Service Class Template Qbin Parameters Template Object Name Template Units Template Range/Values QBIN Number enumeration 0—15 (10-15 valid for VSI) Max QBIN Threshold u sec 1—2000000 QBIN CLP High Threshold % of max Qbin threshold 0—100 QBIN CLP Low Threshold % of max Qbin threshold 0—100 EFCI Threshold % of max Qbin threshold 0—100 Discard Selection enumeration 1—CLP Hystersis 2—Frame Discard Weighted Fair Queueing enable/disable 0—Disable 1—Enable Table 3-6 describes additional Service Class Template commands. Table 3-6 Service Class Template Commands Command Description dspsct: Enter this command to view the template number assigned to an interface. The command has three levels of operation. dspsct Enter this command without arguments to view all current templates. dspsct [tmplt_id] [service class name] Enter this command to view all service classes in the template. cnfqbin Enter this command to set parameters for the Qbin. You can elect to use the card Qbin values from the Qbin templates, by typing yes when prompted. dspqbin Enter this command to view Qbin parameters currently configured for the virtual interface. dspcd Enter this command to view current card configuration Cisco SES PNNI Controller Software Configuration Guide Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 3-51 Chapter 3 Provisioning Communication Links Operating Procedures Note ILMI runs automatically on BXM cards and does not need to be configured. Note VSI ILMI can be enabled for only one VSI partition on trunk interfaces. Modifying an SPVC Connection Use the following procedure to modify an SPVC in a PNNI network. When an SPVC endpoint is modified, the SPVC manager re-establishes the SPVC based on the new endpoint setup. Step 1 Enter the cnfcon command to configure the local PCR and remote PCR at the Master Endpoint. :orioses1.1.1.PXM.a > cnfcon <portid> <vpi> <vci> [-lpcr <local PCR>] [-rpcr <remote PCR> Replace <portid> with the port identifier. Replace <vpi> with the starting VPI to view active calls starting from the specified VPI of the specified port (in the range from 0 to 255). Replace <vci> with the starting VCI to view active calls starting from the specified VPI/VCI of the specified port (in the range from 32 to 65535). Replace <local PCR> with the local PCR range. Replace <remote PCR> with the remote PCR range. In the following example, the user configures the local PCR and remote PCR at Master Endpoint 1.8. ------------------------------------------------------------------------------orioses1.1.1.PXM.a > cnfcon 1.8 100 1000 -lpcr 5000 -rpcr 5000 Step 2 Enter the dspcon command to confirm your configuration. orioses1.1.1.PXM.a > dsppncon <portid> <vpi> <vci> Replace <portid> with the port identifier. Replace <vpi> with the starting VPI. Replace <vci> with the starting VCI. Cisco SES PNNI Controller Software Configuration Guide 3-52 Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 Chapter 3 Provisioning Communication Links Operating Procedures A system response similar to the following example occurs: orioses1.1.1.PXM.a > dspcon 1.8 100 1000 Port Vpi Vci Owner State ------------------------------------------------------------------------Local 1:-1.8:-1 100.1000 MASTER OK Address:47.00918100000000d058ac26b6.000000010800.00 Remote Routed 99.999 SLAVE OK Address:47.00918100000000107bc154b5.000000010300.00 -------------------- Provisioning Parameters -------------------Connection Type:VCC Cast Type:Point-to-Point Service Category:CBR Conformance:CBR.1 Bearer Class:BCOB-X Last Fail Cause:SPVC Established Attempts:0 Continuity Check:Disabled Frame Discard:Disabled L-Utils:100 R-Utils:100 Max Cost:-1 Routing Cost:10080 ---------- Traffic Parameters ---------Tx PCR: 5000 Rx PCR: 5000 Tx SCR: 1000 Rx SCR: 1000 Tx MBS: 1024 Rx MBS: 1024 Tx CDVT:250000 Rx CDVT:250000 Tx CDV: N/A Rx CDV: N/A Tx CTD: N/A Rx CTD: N/A Type <CR> to continue, Q<CR> to stop: Step 3 Enter the cnfcon command to configure the local PCR and remote PCR at the slave endpoint as follows: :orioses1.1.1.PXM.a > cnfcon <portid> <vpi> <vci> [-lpcr <local PCR>] [-rpcr <remote PCR> Replace <portid> with the port identifier. Replace <vpi> with the starting VPI to view active calls starting from the specified VPI of the specified port (in the range from 0 to 255). Replace <vci> with the starting VCI to view active calls starting from the specified VPI/VCI of the specified port (in the range from 32 to 65535). Replace <local PCR> with the local PCR range. Replace <remote PCR> with the remote PCR range. In the following example, the user configures the local PCR and remote PCR at slave endpoint 1.3. orioses3.1.1.PXM.a > cnfcon 1.3 99 999 -lpcr 5000 -rpcr 5000 Step 4 Enter the dspcon command to confirm your configuration. orioses1.1.1.PXM.a > dsppncon <portid> <vpi> <vci> Replace <portid> with the port identifier. Replace <vpi> with the starting VPI. Replace <vci> with the starting VCI. Cisco SES PNNI Controller Software Configuration Guide Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 3-53 Chapter 3 Provisioning Communication Links Operating Procedures A system response similar to the following example occurs: orioses3.1.1.PXM.a > dspcon 1.3 99 999 Port Vpi Vci Owner State ------------------------------------------------------------------------Local 0:0.0:0 99.999 SLAVE OK Address:47.00918100000000d058ac26b6.000000010800.00 Remote Routed 100.1000 MASTER OK Address:47.00918100000000107bc154b5.000000010300.00 -------------------- Provisioning Parameters -------------------Connection Type:VCC Cast Type:Point-to-Point Service Category:CBR Conformance:CBR.1 Bearer Class:BCOB-X Last Fail Cause:SPVC Established Attempts:0 Continuity Check:Disabled Frame Discard:Disabled L-Utils:0 R-Utils:0 Max Cost:0 Routing Cost:0 ---------- Traffic Parameters ---------Tx PCR: 5000 Rx PCR: 5000 Tx SCR: 1000 Rx SCR: 1000 Tx MBS: 1024 Rx MBS: 1024 Tx CDVT:250000 Rx CDVT:250000 Tx CDV: -1 Rx CDV: -1 Tx CTD: -1 Rx CTD: -1 Type <CR> to continue, Q<CR> to stop: ------- SES Parameters only ---------Tx AIS:0 Rx AIS:0 lpbk_type :No Loopback lpbk_dir :---lpbk_status :None round_trip_delay:0 Stats :Disabled ------------------------------------------------------------------------------- Cisco SES PNNI Controller Software Configuration Guide 3-54 Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 Chapter 3 Provisioning Communication Links Operating Procedures Deleting an SPVC Connection Enter the delcon command to delete SPVC endpoints as follows: orioses1.1.1.PXM.a > delcon <portid> <vpi> <vci> Replace <portid> with the port identifier. Replace <vpi> with the starting VPI. Replace <vci> with the starting VCI. Note Delete the master endpoint first, then delete the slave endpoint for each SPVC. Changing Partition Resources Use the BPX CLI to configure dynamic/soft partitioning. Enter the cnfrsrc command on the BPX to alter resources (such as LCNs, BW, VPI/VCI range) allocated to a VSI partition as follows: orioses1.1.1.PXM.a > cnfrsrc <slot.port.vtrk> <maxpvclcns> <maxpvcbw> <y/n> <y/n> <partition> <e/d> <minvsilcns> <maxvsilcns> <vsistartvpi> <vsiendvpi> <vsiminbw> <vsimaxbw> The parameters for the cnfrsrc command are described below: Table 3-7 Partition Resource Command Parameters Parameter Description slot.port.vtrk Slot number of the card and the physical port identifier and the virtual port identifier. maxpvclcns Maximum number of LCNs allocated for Automatic Routing Management PVCs for this port. The range depends upon the card type; (1-11771 for the BNI T/E3 and 1-15867 for the BNI OC) 256 is the default. The default is 256 only if 256 are available. If other ports and trunks on the card have been configured to use LCNs such that there are only 100 remaining, then the default value for the newly added port would be 100. In this instance trunk upping would be blocked indicating that there are not enough LCNs to support the trunk. For trunks, there are additional LCNs allocated for Automatic Routing Management that are not configurable. y/n Answer y (yes) configure PVC VIP ranges. y/n Answer y (yes) configure VSI parameters. partition Identifies the partition. Replace <partition> with a number in the range from 1 to 3. e/d Answer e to enable or d to disable your configured partition. Cisco SES PNNI Controller Software Configuration Guide Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 3-55 Chapter 3 Provisioning Communication Links Operating Procedures Table 3-7 Partition Resource Command Parameters (continued) Parameter Description minvsilcns Minimum LCNs guaranteed for this partition.Replace <minvsilcns> with a number in the range from 0 to the port_group/card limit maxvsilcns Maximum LCNs permitted on this partition. Replace <maxvsilcns> with a number in the range from 1 to port_group/card limit vsistartvpi Partition Start VPI. Replace <vsistartvpi> with a number in the range from 0 to 4095. vsiendvpi Partition End VPI. VSI connections on this partition can use VPIs up to this VPI. The end VSI VPI should be equal to or greater than the Start VSI VPI. Replace <vsiendvpi> with a number in the range from 0 to 4095. vsiminbw Minimum Partition bandwidth. Replace <vsiminbw> with a number in the range from 0 to the Line Rate. vsimaxbw Maximum Partition bandwidth. Replace <vsimaxbw> with a number in the range from 0 to the Line Rate. If ILMI is already enabled on the interface on which VPI/VCI range is being altered, ILMI experiences a “Loss of Connectivity” as a result of the change in VPI/VCI range. Depending on how the ILMI protocol has been configured on this interface, existing connections can be dropped or retained. Enter the dsppnilmi command to see current configuration as follows: orioses1.1.1.PXM.a > dsppnilmi Enter the cnfilmiproto command to modify configurations as follows: orioses1.1.1.PXM.a > cnfilmiproto <portid>[securelink][attachmentpoint][modlocattrstd] Replace <portid> with the port identifier. Replace [securelink] with “enable” to enable the ILMI secure link protocol. Replace [attachmentpoint] with “enable” to enable detection of loss of attachment point procedures. Replace [modlocattrstd] with “enable” to enable ILMI standard procedures on modification of local ATM parameters. If you do not want connections on the interface to be dropped when the VPI/VCI range is changed, configure the ILMI protocol as follows: orioses1.1.1.PXM.a > cnfilmiproto port_id -securelink no -attachmentpoint no Cisco SES PNNI Controller Software Configuration Guide 3-56 Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 C H A P T E R 4 Managing PNNI Routes Configuring PNNI Figure 4-1 outlines the recommended configuration sequence for each SES PNNI node in a switched system. Use the SES PNNI Controller CLI to complete this configuration. Note Some of the tasks, as indicated in Figure 4-1, can be configured using CiscoView. Cisco SES PNNI Controller Software Configuration Guide Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 4-1 Chapter 4 Managing PNNI Routes PNNI Configuration Quickstart Figure 4-1 PNNI Configuration Sequence Overview CiscoView or CLI Configure the BPX PNNI Node CiscoView or CLI Define the Peer Group Node These tasks must always be performed CiscoView or CLI Set Peer Group Leader Parameters CiscoView or CLI Set Timers and Thresholds CLI only Set SVCC-Based Timers CiscoView or CLI Configure Summary Recommended (not required) sequence of tasks. CLI only Set Routing Policies CLI only Configure PNNI Interfaces Set Locally Reachable Address(es) 56136 CLI only For more information about PNNI Controller commands, refer to the Cisco SES PNNI Command Reference. For more information about SES PNNI Controller shelf commands, refer to the Cisco SES Controller Command Reference, “Shelf Operations Commands”. For more information about CiscoView PNNI menus, see Chapter 7, “Network Management.” PNNI Configuration Quickstart The quickstart procedure in this section provides a summary of the tasks required to configure PNNI on the SES. This procedure is provided as an overview and as a quick reference for those who have already configured the SES. Cisco SES PNNI Controller Software Configuration Guide 4-2 Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 Chapter 4 Managing PNNI Routes PNNI Configuration Quickstart Step 1 Command Purpose username Start a configuration session. password Step 2 addpnni-node <level> [optional parameters] cnfpnni-node <node-index> [optional parameters] Add the SES node to the network and configure the PNNI parameters. dsppnni-node [node-index] Step 3 cnfpnni-election <node-index> <-parameter> <number> Set leadership priority and configure peer group leader parameters. dsppnni-election <node-index> Step 4 cnfpnni- timer <node-index> <-parameter> <number> Define timers and set thresholds for the node. dsppnni- timer [node-index] Step 5 cnfpnni-svcc-rcc- timer <node-index> Set and configure SVCC-based RCC timers. dsppnni-svcc-rcc- timer [node-index] Step 6 addpnni-summary address <node-index> <address-prefix> <prefix-length> [optional parameters] Add a summary address on the SES node. dsppnni-summary address [node-index] Step 7 cnfpnni-routing-policy [optional parameters] For a low-level PNNI node, set routing policy parameters. Step 8 cnfpnni-intf <port id> [optional parameters] Configure PNNI interface parameters.F dsppnni-intf <port id> Step 9 dsppnni-reachable-addr <local | network> Display locally reachable PNNI addresses. Step 10 dsppnni-link [node-index [node-index [port id]] Display links and Hello related information. Configuring the SES PNNI Node Use the addpnni-node and cnfpnni-node commands to set up the PNNI node and configure node parameters. You must run the cnfpnni-node -enable false command to disable the node before configuring or modifying the following parameters: Note • Node AESA • Administrative status • Node ID • Node PG ID Remember to run the cnfpnni-node -enable true to enable the node once you have configured or modified node parameters. Cisco SES PNNI Controller Software Configuration Guide Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 4-3 Chapter 4 Managing PNNI Routes PNNI Configuration Quickstart You do not need to disable the node before configuring the following parameters: • Level Indicator • Node representation • Transit restriction • Branching restriction Step 1 Enter the cnfpnni-node -enable false command to disable the node index. Step 2 Enter the addpnni-node command and set the desired parameters. Step 3 Enter the cnfpnni-node -enable true command to enable the node index. Step 4 Enter the dsppnni-node command to display a PNNI node configuration, as shown in the following example: ---------------------------------------------------------------------------orioses1.1.1.PXM.a > dsppnni-node node index: 1 node name: 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.00918100000000d058ac26b6.00d058ac26b6.01 ATM address...........47.00918100000000d058ac26b6.00d058ac26b6.01 Peer group id.........56:47.00.9181.0000.0000.0000.0000.00 ---------------------------------------------------------------------------- In CiscoView, use the following dialogs to display these node parameters: • PNNI Node Configuration • More PNNI Node Configuration Set Peer Group Leader Parameters Use the commands in this section to set the following peer group leader parameters: • Leadership priority • Election init time • Election override time • Re-election time Enter the cnfpnni-election <node-index> <-parameter> <number> command to set leadership priority: ORSES17.1.1.PXM.a > cnfpnni-election 1 -priority 1 Cisco SES PNNI Controller Software Configuration Guide 4-4 Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 Chapter 4 Managing PNNI Routes PNNI Configuration Quickstart Enter the dsppnni-election <node-index> command to display peer group leader election set up: ------------------------------------------------------------------------------ORSES17.1.1.PXM.a > dsppnni-election 1 node index:1 PGL state...... Priority....... OperPgl 51 Init time(sec)....... 15 Override delay(sec).. 30 Re-election time(sec) 15 Pref PGL...............56:160:47.00918100000000d058ac2613.00d058ac2613.01 PGL....................56:160:47.00918100000000d058ac2613.00d058ac2613.01 Active parent node id..40:56:47.009181111111111111111111.00d058ac2613.00 ---------------------------------------------------------------------------- In CiscoView, use the following dialogs to display peer group leadership parameters: • PNNI PGL Configuration • More PNNI PGL Configuration Set Timers and Thresholds Use the commands in this section to set the following parameters to define timers and thresholds for the PNNI node: • PTSE holddown timer value • Hello holddown timer value • Hello interval • Hello inactivity factor • Logical horizontal link inactive timer • PTSE refresh interval • PTSE delayed interval • PTSE Lifetime factor • PTSE Retransmit interval • AvCR proportional multiplier • AvCR minimum threshold • MaxCTD proportional multiplier • CDV proportional multiplier Enter the cnfpnni-timer <node-index> <-parameter> <number> command to set PTSE refresh interval: orioses1.1.1.PXM.a > cnfpnni-timer 1 -ptseRefreshInterval 1000 Cisco SES PNNI Controller Software Configuration Guide Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 4-5 Chapter 4 Managing PNNI Routes PNNI Configuration Quickstart Enter the dsppnni-timer <node-index> command to display timer set up: ---------------------------------------------------------------------------orioses1.1.1.PXM.a > dsppnni-timer 1 node index:1 Hello holddown(100ms)... 10 PTSE holddown(100ms)... 10 Hello int(sec).......... 15 PTSE refresh int(sec).. 1800 Hello inactivity factor. 5 PTSE lifetime factor... 200 Retransmit int(sec)..... 5 AvCR proportional PM.... 50 CDV PM multiplier...... 25 AvCR minimum threshold.. 3 CTD PM multiplier...... 50 Peer delayed ack int(100ms)................... 10 Logical horizontal link inactivity time(sec).. 120 ---------------------------------------------------------------------------- In CiscoView, use the PNNI Timer Configuration dialog to display timers and thresholds. Set SVCC-Based Timers Enter the cnfpnni-svcc-rcc-timer <node-index> command to set the following SVCC-Based RCC-Timer parameters for the PNNI node: • Init timer value • Retry timer value • Calling party integrity timer value • Called party integrity timer value Cisco SES PNNI Controller Software Configuration Guide 4-6 Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 Chapter 4 Managing PNNI Routes PNNI Configuration Quickstart Configure Summary Address(es) Use the following procedure to set summary address parameters for the PNNI node. Step 1 Enter the addpnni-summary-addr <node-index> <address-prefix> <prefix-length> command to add a summary address on the PNNI node: orioses1.1.1.PXM.a > addpnni-summary-addr 1 47.0091.8100.0000.1111.2222 88 Note Step 2 This command is not available in CiscoView. Enter the dsppnni-summary-addr <node-index> command to display summary addresses: ------------------------------------------------------------------------------orioses1.1.1.PXM.a > dsppnni-summary-addr 1 node index:1 Type.............. internal Suppress.............. false State............. advertising Summary address........47.0091.8100.0000.00d0.58ac.26b6/104 node index:1 Type.............. internal Suppress.............. false State............. inactive Summary address........47.0091.8100.0000.1111.2222/88 ------------------------------------------------------------------------------- In CiscoView, use the PNNI Address Summary dialog to display address summary parameters for a PNNI node. Set Routing Policies Enter the cnfpnni-routing-policy command to set the following routing policy parameters for the lowest level PNNI node: Note • SPT holddown timer value • SPT equal-cost epsilon • Border bypass generation timer value • Network-wide load-balancing policy • On-demand routing • AW background table • CTD background table • CDV background table You can not use CiscoView to set routing policy parameters. Cisco SES PNNI Controller Software Configuration Guide Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 4-7 Chapter 4 Managing PNNI Routes PNNI Configuration Quickstart Configure PNNI Interfaces Use the following procedure to set the following PNNI interface parameters on the PNNI node: Step 1 • Port ID • Administrative weight • Aggregation token Enter the cnfpnni-intf <slot.port> <-parameter> <number> command to set interface parameters. The following example shows CBR AW configuration on an interface: orioses1.1.1.PXM.a > cnfpnni-intf 1.3 -awcbr 10000 Step 2 Enter the dsppnni-intf <slot.port> command to display an PNNI interface set up: ------------------------------------------------------------------------------orioses1.1.1.PXM.a > dsppnni-intf 1.3 Physical port id:1.3 Logical port id: 66304 Aggr token.......... 0 AW-NRTVBR........... 5040 AW-CBR.............. 10000 AW-ABR.............. 5040 AW-RTVBR............ 5040 AW-UBR.............. 5040 ------------------------------------------------------------------------------- Note PNNI interface parameters are not available in CiscoView. Set Locally Reachable Address(es) Enter the dsppnni-reachable-addr <local/network> command to display the following locally reachable address parameters for the lowest level PNNI node: • Address prefix • Address plan (DCC/ICD/E164, and so on) • Address scope • Address type (internal/exterior) Cisco SES PNNI Controller Software Configuration Guide 4-8 Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 Chapter 4 Managing PNNI Routes PNNI Configuration Quickstart The following example shows locally reachable address parameters for the lowest level PNNI node: ---------------------------------------------------------------------------orioses1.1.1.PXM.a > dsppnni-reachable-addr local scope............... 0 port id............. -1 Exterior............ false ATM addr prefix.....47.0091.8100.0000.00d0.58ac.26b6.0000.0001.0200/152 scope............... 0 port id............. -1 Exterior............ false ATM addr prefix.....47.0091.8100.0000.00d0.58ac.26b6.0000.0001.0300/152 scope............... 0 port id............. -1 Exterior............ false ATM addr prefix.....47.0091.8100.0000.00d0.58ac.26b6.0000.0001.0600/152 scope............... 0 port id............. -1 Exterior............ false ATM addr prefix.....47.0091.8100.0000.00d0.58ac.26b6.0000.0001.0800/152 scope............... 0 port id............. -1 Exterior............ false ATM addr prefix.....47.0091.8100.0000.00d0.58ac.26b6.00d0.58ac.26b6/152 The following example shows locally reachable address parameters for nodes across the network: orioses1.1.1.PXM.a > dsppnni-reachable-addr network scope............... 0 Advertising node number 2 Exterior............ false ATM addr prefix.....47.0091.8100.0000.0010.7bc1.54b5/104 Advertising nodeid..56:160:47.00918100000000107bc154b5.00107bc154b5.01 ---------------------------------------------------------------------------- Note There are three types local addresses: (1) ILMI registered addresses, (2) user provisioned addresses via addaddr CLI, and (3) host application addresses (such as AESA-Ping, PNNI LGN, IP connectivity and similar). Note You can not use CiscoView to set locally reachable addresses. Show PNNI Link Hello Protocol Enter the dsppnni-link [node-index [slot.port] command to display the following link and Hello related information: • node index • logical port id • link type • link hello state • remote node id • remote port id • derived aggregation token • upnode id • upnode ATM address • common peer group id Cisco SES PNNI Controller Software Configuration Guide Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 4-9 Chapter 4 Managing PNNI Routes PNNI Configuration Quickstart • interface index • SVC RCC index • Hello packets received • Hello packets transmitted Example: ---------------------------------------------------------------------------orioses3.1.PXM.a > dsppnni-link 1 node index : 1 Local port id: 262912 Remote port id: 66304 Local Phy Port Id: 4:0.3:0 Type. lowestLevelHorizontalLink Hello state....... twoWayInside Derive agg........... 0 Intf index........... 262912 SVC RCC index........ 0 Hello pkt RX......... 39638 Hello pkt TX......... 39697 Remote node name.......orses7 Remote node id.........56:160:47.00918100000000107be92f1c.00107be92f1c.01 Upnode id..............0:0:00.000000000000000000000000.000000000000.00 Upnode ATM addr........00.000000000000000000000000.000000000000.00 Common peer group id...00:00.00.0000.0000.0000.0000.0000.00 ------------------------------------------------------------------------------ Cisco SES PNNI Controller Software Configuration Guide 4-10 Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 C H A P T E R 5 Switch Operating Procedures Use this chapter to find out about the tasks typically performed on the SES controller. This chapter assumes you have completed the following tasks: • installed the hardware at the BPX switch and the SES Controller, as described in the Cisco SES Hardware Installation Guide. • set up the general switch features as described in Chapter 2, “Configuring General Switch Features.” 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. Restoring a saved configuration is much easier than re-entering all the commands used to configure the switch. To save a configuration, enter the saveallcnf command, which saves the configuration to a file in the C:/CNF directory. The file is named using the switch name and the current date as follows: Name_01_DateTime.zip. The date appears in YYYYMMDD (year, month, day) format, and the time appears in HHMM (hour, minute) format. For example, if the configuration for a switch named “mgx8850a” were saved on February 29, 2000 at 2:31pm, the file would be named C:/CNF/mgx8850a_01_200002291431.zip. When you save a configuration, the switch saves all configuration data, including the software revision levels used by the cards in the switch. The saved configuration file does not include the boot and runtime software files. To restore a configuration exactly as it was when the configuration file was saved, enter the restoreallcnf command. If the boot and runtime files have been removed from the switch, they must be transferred to the switch before the restored configuration can start. Note If you have upgraded software on the switch since the last time the configuration was saved, a configuration restore will restore the non-upgraded software versions and configuration data. The software does not allow you to save a configuration and restore it on a different revision level of the software. Cisco SES PNNI Controller Software Configuration Guide Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 5-1 Chapter 5 Switch Operating Procedures Managing the Configuration Files You can save a configuration if both of the following statements 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 SES controller does not check for other CLI or CWM users before saving a configuration. If other users make changes while the file is being saved, the configuration can become corrupt. If you try to restore the configuration from a corrupt file, the switch can fail and you might have to send switch cards back to the factory for reprogramming. To save a switch configuration, use the following procedure. Step 1 Establish a configuration session using a user name with SERVICE_GP privileges or higher. Step 2 To save the configuration, enter the saveallcnf command: sesone.1.PXM.a > saveallcnf [-v] The verbose option, -v, displays messages that show what the switch is doing during the save process. You do not need to see these messages, but they do give you an indication on how the save process is proceeding. If you do not enter the -v option, the switch does not display any status messages until the save is complete. Step 3 Read the prompt that appears. Press Y if you want to continue, and press Enter. When the save is complete, the switch prompt reappears, and the new file is stored in the C:/CNF directory. Note The switch stores only the last two files saved with the saveallcnf command. This prevents the hard disk from getting full due to repetitive use of this command. If you need to save files that will be erased the next time the saveallcnf command is run, use an FTP client to copy them to a file server or workstation before saving the next configuration. The following example shows what appears on the switch when the saveallcnf command is used without the -v option: sesone.1.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. Do you want to proceed (Yes/No)? y saveallcnf: shelf configuration saved in C:/CNF/pop20one_01_200006151550.zip. Note Cisco Systems recommends that you use an FTP client to copy the saved configuration file to a workstation. This ensures that you have a backup copy if the PX hard drive card fails. Cisco SES PNNI Controller Software Configuration Guide 5-2 Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 Chapter 5 Switch Operating Procedures Managing the Configuration Files Clearing a Configuration There are two commands that allow you to clear the switch configuration, clrcnf and clrallcnf. To clear switch provisioning data such as the PNNI controller and SPVC connections, enter the clrcnf command. This command clears all configuration data except the following: • IP address configuration • Node name • Software version data for each card • SNMP community string, contact, and location • Date, time, time zone, and GMT offset To clear the entire configuration, enter the clrallcnf command. This command clears all the provisioning data and most of the general switch configuration parameters, such as the switch name and SNMP configuration. The clrallcnf command clears all IP addresses except the boot IP address. Restoring a Saved Configuration You can restore a configuration if all of the following statements are true: Caution • No save or restore process is currently running. • No configuration changes are in progress. • The switch is not hosting any critical calls. Make sure that no other users are making configuration changes when you restore the configuration. The SES controller does 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. To restore a saved switch configuration, use the following procedure. Step 1 Establish a configuration session using a user name with SERVICE_GP privileges or higher. Step 2 Verify that the file from which you want to restore configuration data is located in the C:/CNF directory. Note Tips The C:/CNF directory is the only location from which you can restore a configuration file. If the file is moved to another directory or stored on another system, the file must be returned to this directory before the data can be restored. Use the cd command to navigate the C:/CNF directory, and use the ll command to display the directory contents. Cisco SES PNNI Controller Software Configuration Guide Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 5-3 Chapter 5 Switch Operating Procedures Changing User Access Levels and Passwords Step 3 To restore a saved configuration file, enter the restoreallcnf command: sesone.1.PXM.a > restoreallcnf -f filename Caution The restoreallcnf command resets all cards in the switch and terminates all calls passing through the switch. Note The configuration file saved with the saveallcnf command does not include the boot and runtime software files in use at the time of the save. If you have removed any of these files, you need to transfer them to the switch before the switch can start the restored configuration. Replace filename with the name of the saved configuration file.You do not have to enter the path to the file or the extension. For information on the location and name of the file, see “Saving a Configuration.” Changing User Access Levels and Passwords Use the PXM CLI to change user access levels and password. Changing Your Own User Password Enter the cnfpasswd command to change your own password. To change your own password with the cnfpasswd command, use the following procedure. Step 1 Establish a CLI management session using the username for which you want to change the password. Step 2 Enter the following command after the switch prompt: sesone.1.PXM.a >cnfpasswd Step 3 When prompted, enter your current password. 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. Changing Any User Password After you create a user, you can change that user’s access level or password using the cnfuser command. Note You can also change your own user password with the cnfpasswd command as described in the preceding section. Cisco SES PNNI Controller Software Configuration Guide 5-4 Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 Chapter 5 Switch Operating Procedures Changing User Access Levels and Passwords To change the user level or password of a switch user, use the following procedure. Step 1 Establish a CLI management session. Use either the username for which you want to change the password, or a username with privileges at least one level higher than those of the user whose password you want to change. Step 2 Enter the cnfuser command after the switch prompt. sesone.1.PXM.a >cnfuser -u <username> [-p <password>] [-l <accessLevel>] Replace username with the name of the user for whom you are making the change. If you are changing the password, specify the -p option and enter a password containing from 5 to 15 characters. If you are changing the user access level, specify the -l (lowercase L) option and enter the appropriate access level as shown in Table 2-4. Note You can change passwords and access levels only for users who have privileges lower than the username you used to log in. Step 3 To test a new password, enter the bye command, then log in using the new password. Step 4 To verify a user access level change, enter the dspusers command. The dspusers command displays all the usernames and the access level for each user as shown in the following example: sesone.1.PXM.a > dspusers UserId AccessLevel ------------------------cisco CISCO_GP service SERVICE_GP superuser SUPER_GP jbowman GROUP1 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 deluser command after the switch prompt as follows: sesone.1.PXM.a > deluser <username> Enter the username using from 1 to 12 alphanumeric characters. This completes the deletion of a user. Step 3 To verify the user has been deleted, enter the dspusers command as follows: sesone.1.PXM.a > dspusers UserId AccessLevel ------------------------- Cisco SES PNNI Controller Software Configuration Guide Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 5-5 Chapter 5 Switch Operating Procedures Changing User Access Levels and Passwords cisco service superuser raoul duke CISCO_GP SERVICE_GP SUPER_GP GROUP3 GROUP1 sesone.1.PXM.a > Resetting the User cisco Password If you lose or forget your password for switch access, you should ask a user with a higher access level to reset your password using the cnfuser command as follows: sesone.1.PXM.a > cnfuser <-u user id> [-p password] Replace user id with your user name. Replace password with a new password. If you do not have any passwords for any access levels, you can use the following password recovery procedure to reset the password for user cisco. This procedure resets the user cisco password to <cisco> and leaves all other passwords unchanged. (You can change the other passwords with the cnfuser command after logging in as user cisco.) Note This feature can be disabled using the cnfpswdreset command as described in the next section. You can determine if this feature is enabled or disabled by logging in as a user at any level and entering the dsppswdreset command. Step 1 Establish a physical connection to the switch through the Console Port (CP) connector on the PXM UI-S3 card. Caution Anyone with physical access to the switch Console Port can reset the password, deny access to other users, and reconfigure the switch. To prevent unauthorized switch access and configuration, the switch should be installed in a secure area. Step 2 When the login prompt appears, press ESC, CTRL-Y to reset the password. Step 3 Log in using username cisco and password cisco. Step 4 To maintain switch security after resetting the cisco user password, change the password using the cnfpasswd command as follows: sesone.1.PXM.a > cnfpasswd <user_id> Enter existing password: Enter new password: Re-enter new password: spirit4.1.2.PXM.a > Replace <user_id> with your user name. Cisco SES PNNI Controller Software Configuration Guide 5-6 Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 Chapter 5 Switch Operating Procedures Modifying Port Parameters After AutoConfiguration 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 cisco 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. This feature can be enabled again at a later date if you know the user name and password for a user at the SERVICE_GP privilege level or higher. To enable or disable the password reset feature, use the following procedure. Step 1 Establish a configuration session using a user name with SERVICE_GP privileges or higher. Step 2 To disable password reset, enter the cnfpswdreset off command. Step 3 To enable password reset, enter the cnfpswdreset on command. Step 4 To view the status of this feature, enter the dsppswdreset command. Modifying Port Parameters After AutoConfiguration The procedure for AutoConfiguring a port is described in Chapter 3, “Provisioning Communication Links.” To modify port parameters after AutoConfiguration, perform the following steps at the SES Controller CLI. Note When using service-affecting parameters on a port already configured, the port must be brought down prior to attempting modifications to port parameters. Step 1 Enter the dnpnport command at the PXM to bring down the signaling stacks for the port. Step 2 Change the appropriate parameter with one of the following cnf commands. • cnfpnportsig Set ATM signaling parameters on a specified port. • cnfpnportrange Set VPI values for SVCC and SVPC on a specified port. The following commands are only available on ports running ILMI: • cnfilmienable Enables ILMI on a PNNI port. • cnfaddrreg Set ILMI address registration options on a PNNI port. • cnfautocnf Enables ILMI auto configuration on a PNNI port. Cisco SES PNNI Controller Software Configuration Guide Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 5-7 Chapter 5 Switch Operating Procedures Configuring Dynamic/Soft Partitioning Step 3 Step 4 Use one of the following display commands to see the current configurations: • dsppnportsig Display ATM signaling parameters for a port. • dsppnportrange Display ATM VPI/VCI range for a specified port. • dsppnilmi Display the current ILMI service configuration for a specified port. • dsppnportcc Display call control parameters for a specified port. • dsppnportcac Display CAC policy parameters for a specified port. • dspprfx Display ILMI/AINI address prefixes for a specified port. This command is only available on ports running ILMI or AINI. • dspaddr Display ATM addresses and associated information for a UNI or IISP. Enter the uppnport command to enable the port. Non-service affecting parameters can be changed without downing the port. For example, you do not need to down the port to execute the following SES Controller CLI commands: • cnfpnportcc Set call control parameters for a specified port. • cnfpnportcac Set CAC policy parameters for a specified port. • addprfx Add an ILMI address prefix for UNI. • addaddr Add or delete an ATM address for a UNI or IISP. Configuring Dynamic/Soft Partitioning Dynamic/soft partitioning is configured on the BPX. Refer to the Switch Software configuration documentation for detail. The cnfrsrc command on the BPX is used to alter resources allocated to a VSI partition (for example, LCNs, BW, VPI/VCI range). If ILMI is enabled on the interface on which the VPI/VCI range is being altered, then ILMI experiences a “Loss of Connectivity” as a result of the change in the VPI/VCI range. Depending on how the ILMI protocol has been configured on this interface, existing connections on the can be dropped or retained. Enter the dsppnilmi command to see current configuration. Enter the cnfilmiproto command to change the ILMI protocol. If you do not want connections on the interface to be dropped when the VPI/VCI range is changed, configure the ILMI protocol in the following manner: cnfilmiproto port_id -securelink no -attachmentpoint no Cisco SES PNNI Controller Software Configuration Guide 5-8 Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 Chapter 5 Switch Operating Procedures Configuring SPVC Stats Collection Configuring SPVC Stats Collection Use the following procedure to enable SPVC stats collection on an SES Controller: Step 1 Verify the SNMP configuration both on BCC and PXM cards. Step 2 Enter the cnfcdparm <slotId> <stat-level> command to set the stats level on BCC. Note Step 3 There must not be any connections on the BXM when the cnfcdparm command is executed. The BXM must be reset for the new stats level to take effect. Enter the addcon command to add an SPVC connection with stats enabled. Note To enable statistics on existing SPVCs, modify the connections with cnfcon and enable the -stats enable option with this command. Configure statistics on CWM as follows: Step 1 Telnet to the PXM card and setup CWM's IP address for stats using cnfstatsmgr In the SCM GUI (runScmGui <host>): Step 2 Click the node tab. Step 3 Navigate to a node and click on it to open a telnet window. Step 4 Enter the cnfstatsmgr <ip address> command. Step 5 Enable the stats parameters. Step 6 Add the required statistic id's and start collecting the statistics. Step 7 Wait at least 15 minutes to see if any stats files have been collected. If no files have been collected after 30 minutes, check the error logs for any error messages. Setting ATM Address Filtering The BPX-SES node supports the following forms of address filtering to process addresses during the transport of SETUP messages across the network: 1. Ingress/Incoming Call-In Party Number Filtering 2. Ingress/Incoming Called Party Number Filtering 1. Egress/Outgoing Call-In Party Number Filtering 2. Egress/Outgoing Called Party Number Filtering Cisco SES PNNI Controller Software Configuration Guide Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 5-9 Chapter 5 Switch Operating Procedures Setting ATM Address Filtering The filtering process consists of the following two steps: Step 1 Enter the addfltset command to create an address filter. Step 2 Enter the addfltset command to enable the filter on the port. Step 3 Enter the cnfpnportacc command to enable an address access filter group on the port. Use the delpnportacc to disable a filter set on a port. Use the delfltset command to delete an address filter completely. For more details on the syntax and usage of these commands, please refer to the Cisco SES PNNI Controller Command Reference, Release 1.1. Enter the cnfe164justify command to convert a native E.164 address to an AESA E.164 address. Note • Right justify is specified in UNI 3.x and is the default setting. • Left Justify is specified in PNNI 2.0 Living List, July 1998, (not yet a standard) Annex C.6. All nodes in a PNNI network should use the same justification. The call will be rejected if the addresses are the same, but justification is different. The SES Controller uses filter sets to permit or deny incoming or outgoing calls on a port interface. It uses access filter sets to filter calls based on the destination ATM address or source ATM address (or a combination of both) in the SETUP message. Access control lists, or filters, are mapped to a port. Currently, two filter sets can be configured for each port—one for incoming calls, and the other for outgoing calls. The following sections provide examples of different address filtering configurations on an SES Controller. Ingress/Incoming Calling Party Number Filtering Incoming calling number filtering enables the network to block or accept calls from specific source addresses. Incoming calling number (ingress) filtering uses a filter list to filter incoming calling party numbers. A calling party number with digits matching those of an address entry in the incoming filtering list will be rejected or accepted, depending on the filtering policy assigned to the entry on the list. You must set the calling party absent action (the filtering policy) to one of the following options: • Permit—If the filter address entry has a permit filtering policy and the digits match those of the call-in party, then the call can be made. • Deny—If the filter address entry has a permit filtering policy and the digits match those of the call-in party, then the call is rejected. The address entry and the digits of the calling/called party can be configured as an exact match. However, the filter also contains options to match address prefixes and wildcards. If a calling party address does not match any address entry in the incoming filtering list, the call is accepted or rejected depending on how the filter option was set. Cisco SES PNNI Controller Software Configuration Guide 5-10 Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 Chapter 5 Switch Operating Procedures Setting ATM Address Filtering Example 5-1 Configure an Address Filter to Reject a Specific Ingress/Incoming Called Party The following example describes how to configure an address filter to reject a specific called party on the ingress. Step 1 Enter the addfltset command to create a filter. In the example, a filter called firstfilter is created. espses1.1.PXM.a > addfltset firstfilter Step 2 Enter the dspfltset command to display summary information pertaining to all filters created on the node. espses1.1.PXM.a > dspfltset Filter Number: 1 FilterName: firstfilter CgPtyAbsentAction: Permit CdPtyAbsentAction: Permit Enter the dspfltset -name command to display detailed information pertaining to a specific filter. espses1.1.PXM.a > dspfltset -name firstfilter espses1.1.PXM.a > Note Since no addresses have been added yet, the dspfltset -name command does not show any information. Enter the cnffltset command to add an address to a filter. In the example below, an AESA address is added to the called party list with the accessMode set to deny. If a call is made with the AESA address 4722222222222222222222222222222222222222 as the called party, then the call will be rejected due to address filtering. This action takes effect after the filter is attached to the port (Step 4). espses1.1.PXM.a > cnffltset firstfilter -address 4722222222222222222222222222222 222222222 -length 160 -list called -accessMode deny Step 3 Enter the dspfltset command to display the detailed information for the firstfilter to verify that the address has been added to the filter. espses1.1.PXM.a > dspfltset -name firstfilter FilterName: firstfilter Index: 1 Address: 4722222222222222222222222222222222222222 AddrLen: 160 bits AddrPlan: Nsap AccessMode: Deny AddrList: Called Party List Step 4 Enter the cnfpnportacc command to attach the filter to a port. In the example below, port 4.3 is associated with the firstfilter in the ingress direction. When a SETUP is received by port 4.3, the call is subjected to address filtering depending on the rules in firstfilter. espses1.1.PXM.a > cnfpnportacc 4.3 -in firstfilter Step 5 Enter the dsppnport command to display the port information and verify that the filter is correctly bound to the port on the ingress. Cisco SES PNNI Controller Software Configuration Guide Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 5-11 Chapter 5 Switch Operating Procedures Setting ATM Address Filtering In the example below, the Input filter field shows the value 1. The filter number for firstfilter is 1, as seen in the output of the dspfltset command in Step 2. espses1.1.PXM.a > dsppnport 4.3 Port: 4.3 Logical Id: 262912 IF status: up Admin Status: up UCSM: enable Auto-config: enable Addrs-reg: enable IF-side: network IF-type: uni UniType: private version: uni3.1 Input filter: 1 Output filter: 0 minSvccVpi: 1 maxSvccVpi: 4095 minSvccVci: 35 maxSvccVci: 65535 minSvpcVpi: 1 maxSvpcVpi: 4095 #SpvcCfg: #SpvcActive: #SpvpCfg: #SpvpActive: p2p: 0 0 0 0 p2mp: 0 0 0 0 #Svcc: #Svpc: Total: p2p : 1 0 1 p2mp : 0 0 0 Total : 1 Step 6 Make an SVC call to verify that address filtering is taking effect. In the example below, a call is made from port 4.3 to port 4.1. The called party is 4722222222222222222222222222222222222222. Therefore, the call is rejected. espses1.1.PXM.a > TICK: 7790466, RCVP: 262912, CRV:1, -> Rcvd Setup TICK: 7790466, SNDP: 262912, CRV: 1, <Send Release Complete Example 5-2 Configure an Address Filter To Reject a Specific Ingress/Incoming Calling Party The following example shows how to configure an address filter to reject a specific calling party on the ingress. Step 1 Enter the addfltset command to create a filter. A filter called secondfilter is created for this example. espses1.1.PXM.a > addfltset secondfilter Step 2 Enter the dspfltset command to display the filter contents. espses1.1.PXM.a > dspfltset Filter Number: 1 FilterName: secondfilter CgPtyAbsentAction: Permit CdPtyAbsentAction: Permit --------------------------------------espses1.1.PXM.a > dspfltset -name secondfilter espses1.1.PXM.a > Cisco SES PNNI Controller Software Configuration Guide 5-12 Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 Chapter 5 Switch Operating Procedures Setting ATM Address Filtering Step 3 Enter the cnffltset command to add an address to the filter. In the example below, an AESA address 4711111111111111111111111111111111111111 is added to the calling party list, with the accessMode set to deny. If a call is made with the calling party as 4711111111111111111111111111111111111111, it will be rejected due to address filtering. This action takes effect after the filter is attached to the port (Step 5). espses1.1.PXM.a > cnffltset secondfilter -address 4711111111111111111111111111111111111111 -length 160 -list calling accessMode deny Step 4 Enter the dspfltset command to display the filter contents. espses1.1.PXM.a > dspfltset -name secondfilter FilterName: secondfilter Index: 1 Address: 4711111111111111111111111111111111111111 AddrLen: 160 bits AddrPlan: Nsap AccessMode: Deny AddrList: Calling Party List Step 5 Attach the filter to a port/interface. espses1.1.PXM.a > cnfpnportacc 4.3 -in secondfilter Step 6 Make a call and ensure that address filtering is taking effect. In the example below, a call is made from port 4.3 to port 4.1. The calling address is 4711111111111111111111111111111111111111. The called address is 4733333333333333333333333333333333333333. The call gets rejected because of the calling party restriction in the filter secondfilter attached to the port 4.3. espses1.1.PXM.a > TICK: 8088755, RCVP: 262912, CRV:1, -> Rcvd Setup TICK: 8088755, SNDP: 262912, CRV: 1, <Send Release Complete Example 5-3 Configure an Address Filter To Reject a Specific Incoming/Ingress Calling Party and Called Party Use the following procedure to configure an address filter to reject a specific calling and called parties on the ingress. Step 1 Enter the addfltset command to create a filter. espses1.1.PXM.a > addfltset thirdfilter Step 2 Enter the dspfltset command to display the filter contents. espses1.1.PXM.a > dspfltset Filter Number: 1 FilterName: thirdfilter CgPtyAbsentAction: Permit CdPtyAbsentAction: Permit --------------------------------------espses1.1.PXM.a > dspfltset -name thirdfilter espses1.1.PXM.a > Cisco SES PNNI Controller Software Configuration Guide Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 5-13 Chapter 5 Switch Operating Procedures Setting ATM Address Filtering Step 3 Enter the cnffltset command to add addresses to the filter: Add the address 4711111111111111111111111111111111111111 to the calling party list to be rejected. espses1.1.PXM.a > cnffltset thirdfilter -address 4711111111111111111111111111111111111111 -length 160 -list calling accessMode deny Step 4 Enter the cnffltset command to add the address 4722222222222222222222222222222222222222 to the called party list to be rejected. Every address entry stored in a filter requires a unique index number. If no index is specified, the index value 1 is assumed by default. In this example, the user specifies the index value 2 for the new address. cnffltset thirdfilter -address 4722222222222222222222222222222222222222 length 160 -list called -accessMode deny -index 2 On display, the filter should contain 2 addresses as follows: espses1.1.PXM.a > dspfltset -name thirdfilter FilterName: thirdfilter Index: 1 Address: 4711111111111111111111111111111111111111 AddrLen: 160 bits AddrPlan: Nsap AccessMode: Deny AddrList: Calling Party List --------------------------------------FilterName: thirdfilter Index: 2 Address: 4722222222222222222222222222222222222222 AddrLen: 160 bits AddrPlan: Nsap AccessMode: Deny AddrList: Called Party List Step 5 Enter the cnfpnportacc command to attach the filter to the port. espses1.1.PXM.a > cnfpnportacc 4.3 -in thirdfilter Step 6 Make a call to verify that address filtering is taking effect. If a call is made from port 4.3 to port 4.1 and if the SETUP message contains either 4711111111111111111111111111111111111111 as the calling party address or 4722222222222222222222222222222222222222 as the called party address, then the call will be released. Cisco SES PNNI Controller Software Configuration Guide 5-14 Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 Chapter 5 Switch Operating Procedures Setting ATM Address Filtering Example 5-4 Configure an Ingress/Incoming Filter to Reject All Calls Whose Calling Party Begins With a Specific Set Of Digits Use the following procedure to configure an ingress filter to reject all calls whose calling party number begins with a specific set of digits. The rest of the digits in the calling party will not be taken into account. In the following example, the user configures the filter to reject all calls whose calling party number begins with the digits 47123. The user adds address entries to the thirdfilter. The filter is bound to the port 4.3 on the ingress. Step 1 Enter the cnffltset command to add an address to the already existing filter: cnffltset thirdfilter -address 47123... -length 20 -list calling -index 3 accessMode deny Step 2 Enter the dspfltset command to display the filter contents. espses1.1.PXM.a > dspfltset -name thirdfilter FilterName: thirdfilter Index: 1 Address: 4711111111111111111111111111111111111111 AddrLen: 160 bits AddrPlan: Nsap AccessMode: Deny AddrList: Calling Party List --------------------------------------FilterName: thirdfilter Index: 2 Address: 4722222222222222222222222222222222222222 AddrLen: 160 bits AddrPlan: Nsap AccessMode: Deny AddrList: Called Party List --------------------------------------FilterName: thirdfilter Index: 3 Address: 47123 AddrLen: 20 bits AddrPlan: Nsap AccessMode: Deny Type <CR> to continue, Q<CR> to stop: Filter Address Type : NSAP Prefix AddrList: Calling Party List Step 3 Make a call and ensure that address filtering is taking effect. In the example below, a call is made from port 4.3 to port 4.1. The calling party is 4712344444444444444444444444444444444444. The called party is 4733333333333333333333333333333333333333. The call is rejected because the calling party begins with the digits 47123. espses1.1.PXM.a > TICK: 8311351, RCVP: 262912, CRV:2, -> Rcvd Setup TICK: 8311351, SNDP: 262912, CRV: 2, <Send Release Complete Cisco SES PNNI Controller Software Configuration Guide Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 5-15 Chapter 5 Switch Operating Procedures Setting ATM Address Filtering Configure an Ingress Filter to Reject all Calls Whose Calling Party Ends with a Specific Set Of Digits Use the following procedure to configure an ingress filter to reject all calls whose calling party number ends with the digits 56789. In the example, the user is adding address entries to the already created thirdfilter. The filter should be bound to the port 4.3 on the ingress. Step 1 Enter the cnffltset command to add an address to the already existing filter. cnffltset thirdfilter -address ...56789 -length 20 -list calling -index 4 access Mode deny Step 2 Make a call and ensure that address filtering is taking effect. In the example below, a call is made from port 4.3 to port 4.1. The calling party is 4712344444444444444444444444444444456789. The called party is 4733333333333333333333333333333333333333. espses1.1.PXM.a > TICK: 8690114, RCVP: 262912, CRV:1, -> Rcvd Setup TICK: 8690115, SNDP: 262912, CRV: 1, <Send Release Complete The call is rejected as expected. Delete An Address Entry in a Filter Use the following procedure to delete an address entry in a filter. The address entry for index 4 is deleted in this example. Step 1 Delete the address entry in the filter. espses1.1.PXM.a > delfltset thirdfilter -index 4 Step 2 Enter the dspfltset command to display the remaining contents of the filter. espses1.1.PXM.a > dspfltset -name thirdfilter FilterName: thirdfilter Index: 1 Address: 4711111111111111111111111111111111111111 AddrLen: 160 bits AddrPlan: Nsap AccessMode: Deny AddrList: Calling Party List --------------------------------------FilterName: thirdfilter Index: 2 Address: 4722222222222222222222222222222222222222 AddrLen: 160 bits AddrPlan: Nsap AccessMode: Deny AddrList: Called Party List --------------------------------------- Cisco SES PNNI Controller Software Configuration Guide 5-16 Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 Chapter 5 Switch Operating Procedures Setting ATM Address Filtering FilterName: thirdfilter Index: 3 Address: 47123 AddrLen: 20 bits AddrPlan: Nsap AccessMode: Deny Type <CR> to continue, Q<CR> to stop: Filter Address Type : NSAP Prefix AddrList: Calling Party List --------------------------------------- If a call is made from port 4.3 to port 4.1 with the calling address ending in digits 56789, the call will succeed. Disable Address Filtering Functionality on the Ingress Use the following procedure to disable address filtering functionality on the ingress. Step 1 Enter the delpnportacc command. espses1.1.PXM.a > delpnportacc 4.3 in Step 2 Enter the dsppnport command to verify that the filter is detached from the port. The Input filter field shows the filter number to be 0. This implies that no filter is attached to this port on the ingress. Hence, no address filtering functionality will be available for this port on the ingress. espses1.1.PXM.a > dsppnport 4.3 Port: 4.3 Logical Id: 262912 IF status: up Admin Status: up UCSM: enable Auto-config: enable Addrs-reg: enable IF-side: network IF-type: uni UniType: private version: uni3.1 Input filter: 0 Output filter: 0 minSvccVpi: 1 maxSvccVpi: 4095 minSvccVci: 35 maxSvccVci: 65535 minSvpcVpi: 1 maxSvpcVpi: 4095 #SpvcCfg: #SpvcActive: #SpvpCfg: #SpvpActive: p2p : 0 0 0 0 p2mp: 0 0 0 0 #Svcc: #Svpc: Total: p2p : 1 0 1 p2mp: 0 0 0 Total : 1 Cisco SES PNNI Controller Software Configuration Guide Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 5-17 Chapter 5 Switch Operating Procedures Setting ATM Address Filtering Destroy an Existing Filter In the previous section, “Disable Address Filtering Functionality on the Ingress,” the user only detached the filter from the port. However, the filter continues to exist though it is now non-functional. Use the following procedure to delete the entire filter along with all the address entries contained in it. Step 1 Enter the delfltset command to delete a filter. espses1.1.PXM.a > delfltset thirdfilter Step 2 Enter the dspfltset command to verify that the filter is deleted. In this case, the command displays no existing filters. espses1.1.PXM.a > dspfltset Create a filter to Reject All Calls Whose Calling Party Address Does Not Match Any Address Entry in the Filter By default, filters allow calling/called addresses which do not match any address entries in the filter. However, you can create a filter to reject calling addresses which do not match any entry in the filter. Use the following procedure to create a filter which rejects all calls whose calling party address does not match any address entry in the filter. In the example, the user creates a filter called fourthfilter. This filter allows only 4711111111111111111111111111111111111111 as the calling party address. Any other calling party address will be rejected. Step 1 Enter the addfltset command to create the filter. espses1.1.PXM.a > addfltset fourthfilter -cgPtyAbsentAction deny Step 2 Enter the cnffltset command to add an address entry to the filter. espses1.1.PXM.a > cnffltset fourthfilter -address 4711111111111111111111111111111111111111 -length 160 -list calling -index 1 accessMode permit Step 3 Enter the dspfltset command display the filter contents. espses1.1.PXM.a > dspfltset Filter Number: 1 FilterName: fourthfilter CgPtyAbsentAction: Deny CdPtyAbsentAction: Permit --------------------------------------espses1.1.PXM.a > dspfltset -name fourthfilter FilterName: fourthfilter Index: 1 Address: 4711111111111111111111111111111111111111 AddrLen: 160 bits AddrPlan: Nsap AccessMode: Permit AddrList: Calling Party List Step 4 Enter the cnfpnportacc command to attach the filter to a port on the ingress. espses1.1.PXM.a > cnfpnportacc 4.3 -in fourthfilter Cisco SES PNNI Controller Software Configuration Guide 5-18 Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 Chapter 5 Switch Operating Procedures Setting ATM Address Filtering Step 5 Make a call to verify that address filtering action is taking effect. If the calling party address in the SETUP message is 4711111111111111111111111111111111111111, the call will succeed. If the calling party address is not 4711111111111111111111111111111111111111, it will be rejected. The user can use the same procedure to create a filter to reject called party addresses which do not match any address entry in the filter. Use the -cdPtyAbsentAction deny option in the addfltset command. Enable Egress Address Filtering Use the following procedure to enable egress address filtering. Step 1 Enter the addfltset command to create the filter. espses1.1.PXM.a > addfltset fourthfilter -cgPtyAbsentAction deny Step 2 Enter the cnffltset command to add an address entry to the filter. espses1.1.PXM.a > cnffltset fourthfilter -address 4711111111111111111111111111111111111111 -length 160 -list calling -index 1 accessMode permit Step 3 Enter the cnfpnportacc command to attach the filter to a port on the egress. In the following example, the fourthfilter is attached to the port 4.1 on the egress. This implies that address filtering action will take effect as dictated by the contents of the fourthfilter for all calls exiting port 4.1. espses1.1.PXM.a > cnfpnportacc 4.1 -out fourthfilter Step 4 Enter the dsppnport command to verify that the filter is attached to a port on the egress. espses1.1.PXM.a > dsppnport 4.1 Port: 4.1 Logical Id: 262400 IF status: up Admin Status: up UCSM: enable Auto-config: enable Addrs-reg: enable IF-side: network IF-type: uni UniType: private version: uni3.1 Input filter: 0 Output filter: 1 minSvccVpi: 1 maxSvccVpi: 1 minSvccVci: 35 maxSvccVci: 65535 minSvpcVpi: 1 maxSvpcVpi: 1 #SpvcCfg: #SpvcActive: #SpvpCfg: #SpvpActive: p2p : 0 0 0 0 p2mp: 0 0 0 0 #Svcc: #Svpc: Total: p2p : 1 0 1 p2mp: 0 0 0 Total : 1 The Output filter field shows that it is attached to filter 1. This is the filter number, which refers to the fourthfilter, as seen in the results of the dspfltset command. Step 5 Make a call to verify that egress address filtering functionality is taking effect. Cisco SES PNNI Controller Software Configuration Guide Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 5-19 Chapter 5 Switch Operating Procedures Setting ATM Address Filtering Disable Address Filtering Functionality on the Egress Use the following procedure to disable address filtering functionality on the egress. Step 1 Enter the delpnportacc command. espses1.1.PXM.a > delpnportacc 4.1 out Step 2 Enter the dsppnport command to verify that the filter is detached from the port. espses1.1.PXM.a > dsppnport 4.1 Port: 4.1 Logical Id: 262400 IF status: up Admin Status: up UCSM: enable Auto-config: enable Addrs-reg: enable IF-side: network IF-type: uni UniType: private version: uni3.1 Input filter: 0 Output filter: 0 minSvccVpi: 1 maxSvccVpi: 1 minSvccVci: 35 maxSvccVci: 65535 minSvpcVpi: 1 maxSvpcVpi: 1 #SpvcCfg: #SpvcActive: #SpvpCfg: #SpvpActive: p2p : 0 0 0 0 p2mp: 0 0 0 0 #Svcc: #Svpc: Total: p2p : 1 0 1 p2mp: 0 0 0 Total : 1 Note The Output filter field shows the filter number 0. This implies that no filter is attached to this port on the egress. Hence, no address filtering functionality will be available for this port on the egress. Cisco SES PNNI Controller Software Configuration Guide 5-20 Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 C H A P T E R 6 2 Viewing and Responding to Alarms The SES displays alarm information on the PXM cards, and it stores information on these 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 PXM cards host LEDs and switches that you can use to view alarm status and respond to alarms. PXM Card Controls Figure 6-1 shows the LEDs and switches available on the front of the PXM card. Table 6-1 describes these controls. Note Although there are LEDs for critical, major, and minor alarms on the PXM, only one of these LEDs is set to on when multiple alarms are active. The switch always displays the status of the most severe alarm. Critical alarms are the most severe, and minor alarms are the least severe. For example if there were 2 major alarms and 10 minor alarms, the switch would set the major alarm LED to on. Cisco SES PNNI Controller Software Configuration Guide Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 6-1 Chapter 6 Viewing and Responding to Alarms Viewing and Responding to Alarms Using Physical Switch Controls Figure 6-1 PXM 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 STATUS Blinking green = active Slow blink yellow = standby Fast blink yellow = boot Solid red = reset, failure, or missing back card Blinking red = software download Table 6-1 LED Indicators for PXM LED Label Colors Meaning CNTRLR Port (Controller Port) Green Green indicates the Controller port is active. Red Yellow Off Red indicates a Major alarm on this port. Yellow indicates a Minor alarm on this port. Off indicates the port has not been activated (upped). Cisco SES PNNI Controller Software Configuration Guide 6-2 Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 Chapter 6 Viewing and Responding to Alarms Viewing and Responding to Alarms Using Physical Switch Controls Table 6-1 LED Indicators for PXM (continued) LED Label Colors Meaning System Status Green Blinking green indicates the card is in the active state. Yellow Slow blink yellow indicates the card is in the standby state. Red Fast blink yellow indicates the card is in the boot state. Solid red indicates either the card is in the reset state, the card has failed, or that a back card is missing. Blinking red indicates the card is downloading new software. CR (Critical alarm) Blue Blue indicates a Critical Network alarm in the node. MJ (Major alarm) Red Red indicates a Major Network alarm in the node. MN (Minor alarm) Yellow Yellow indicates a Minor Network alarm in the node. HIST (History) Green Green indicates a network alarm occurred, but has been cleared. ACO (Alarm cut-off) Yellow Yellow indicates the ACO switch was pushed to clear the audible alarm indicator, but the alarm condition still exists. DC-A Green Green indicates that the power supplies in tray “A” are functioning. Off Off indicates that power supply tray “A” is empty (no power modules). Green Green indicates that the power supplies in tray “B” is empty. Off Off indicates that power supply tray “B” is empty (no power modules). Green Blinking green indicates that there is activity on the LAN control port. DC-B ENET (Ethernet) Cisco SES PNNI Controller Software Configuration Guide Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 6-3 Chapter 6 Viewing and Responding to Alarms Displaying Alarm Reports in the CLI Displaying Alarm Reports in the CLI Use the CLI to view the status of switch alarms. Alarms are reported in the following categories: • Node alarms • Card alarms • Clock alarms • Environment alarms • Slot alarms • Switching alarms This section describes how to display the different types of alarm reports. Displaying Node Alarms A node alarm report displays a summary report of all alarms on the node. Enter the dspndalms command to display node alarms: spirit.1.PXM.a > dspndalms The following is an example of the node alarm report. spirit.1.PXM.a > dspndalms Node Alarm Summary Alarm Type Clock Alarms Switching Alarms Shelf Slot Alarms Environment Alarms Alarms From Cards Critical 0 0 0 0 0 Major 0 0 2 0 1 Minor 0 0 0 0 0 Typically, you would start investigating alarms by displaying the node alarms. Once you have identified the area that is producing the alarms, enter additional commands to display detailed information on those alarms. The following sections describe how to display these detailed reports. 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: spirit.1.PXM.a > dspcdalms [slot] Replace slot with the number of the card for which you want to display alarms. Note The dspcdalms command must be run at the CLI prompt. Cisco SES PNNI Controller Software Configuration Guide 6-4 Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 Chapter 6 Viewing and Responding to Alarms Displaying Alarm Reports in the CLI The following example shows a partial card alarm report for all cards: spirit.1.PXM.a > dspcdalms Node Card Alarm Summary Line Alarm Port Alarm Channel Alarm Slot Slot Slot 1 1 1 Critical Critical Critical 0 0 0 Major Major Major 1 0 0 Minor Minor Minor 0 0 0 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 following command: spirit.1.PXM.a > dspenvalms The following example shows an environmental alarm report: spirit.1.PXM.a > dspenvalms spirita System Rev:01.00 May. 19, 2000 07:52:19 PST SES-CNTL Node Alarm:MAJOR ENVIRONMENTAL ALARM STATE INFO ^Notification Disabled Alarm Type Unit Threshold DataType Value State ---------------- ---- --------------------- ---------- ------------Temperature <= 50 Celsius 26 Normal Power Supply Power Supply Power Supply DC Voltage A1 A2 A3 A none none none 42 to 54 None None None VoltsDC none none none 49 Normal Missing Missing Normal Power Supply Power Supply Power Supply DC Voltage B1 B2 B3 B none none none 42 to 54 None None None VoltsDC none none none 0 Missing Missing Missing Normal Fan Fan Fan Fan Fan 1 2 3 4 5 >= >= >= >= >= RPM RPM RPM RPM RPM 2784 2760 2700 2646 2670 Normal Normal Normal Normal Normal Tray Tray Tray Tray Tray 2000 2000 2000 2000 2000 Type <CR> to continue, Q<CR> to stop: spirita System Rev:01.00 May. 19, 2000 07:52:19 PST SES-CNTL Node Alarm:MAJOR ENVIRONMENTAL ALARM STATE INFO ^Notification Disabled Alarm Type Unit Threshold DataType Value State ---------------- ---- --------------------- ---------- ------------Fan Tray 6 >= 2000 RPM 2616 Normal Fan Tray 7 >= 2000 RPM 2670 Normal Fan Tray 8 >= 2000 RPM 2676 Normal +5V Input +3.3V Input Calibration VDC 4.850^ to 5.150^ 3.200^ to 3.400^ 0x7e^ to 0x82^ VoltsDC VoltsDC Other 4.978 Informational 3.259 Informational 0x80 Informational Cisco SES PNNI Controller Software Configuration Guide Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 6-5 Chapter 6 Viewing and Responding to Alarms Displaying Event Log Information Displaying Slot Alarms Slot alarms identify issues with the physical slots that host the PXM card. To display a report of all active slot alarms, enter the following command: spirit.1.PXM.a > dspslotalms The following is a sample report showing no slot alarms. spirit.1.PXM.a > dspslotalms Node Slot Alarm Summary Card Alarm Critical 0 Major 2 Minor 0 Displaying Switching Alarms Switching alarms identify problems with the switching components within the SES and PXM. To display a report of all switching alarms, enter the following command: spirit.1.PXM.a > dspswalms The following is a sample report showing no switching alarms. spirit.1.PXM.a > dspswalms Card Crossbar Critical Crossbar Fabric Critical Humvee Alarm Critical 0 0 0 Major Major Major 0 0 0 Minor Minor Minor 0 0 0 Displaying Event Log Information Log files record switch events such as operator login and command entry. The syntax for the dsplog command is as follows: dsplog [-sl <slot>] [-mod <module>] To limit the log display to the events for a single slot, use the -sl option and replace slot with the appropriate slot number. To limit the log display to events from a single module, use the -mod option with the module name, for example LDRV. To display the current log file number, enter the following command: spirit.1.PXM.a > dsplogs The log files are stored in the C:/LOG directory, under the names event 01.log through event 50.log. The following is a sample report showing event log information. spirit.1.PXM.a > dsplog 01-00369 05/19/2000-07:56:51 CLI-7-CMDLOG tDbgInTask 0x80199084 cliCmdLog:cisco@console:(cc 1). 01-00368 05/19/2000-07:56:51 CLI-7-CMDLOG tDbgInTask 0x80199084 cliCmdLog:cisco@console:(cc 1). 01-00367 05/19/2000-07:56:51 CLI-7-CMDLOG tDbgInTask 0x80199084 cliCmdLog:cisco@console:(cc 1). Cisco SES PNNI Controller Software Configuration Guide 6-6 Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 Chapter 6 Viewing and Responding to Alarms Displaying Error Information 01-00366 05/19/2000-07:40:39 CLI-7-CMDLOG tDbgInTask 0x80199084 cliCmdLog:cisco@console:(cc 1). 01-00365 05/19/2000-07:38:06 CLI-7-CMDLOG tDbgInTask 0x80199084 cliCmdLog:cisco@console:(cc 1). 01-00364 05/19/2000-07:38:06 CLI-7-CMDLOG tDbgInTask 0x80199084 cliCmdLog:cisco@console:(login). 01-00363 05/19/2000-05:17:43 CLI-7-CMDLOG tDbgInTask 0x80199084 cliCmdLog:cisco@console:(logout). - 1 dropped 01-00362 05/19/2000-05:03:10 CLI-7-CMDLOG Type <CR> to continue, Q<CR> to stop: Displaying Error Information Error files record all errors on the system. To view the contents of the current error log file, enter the dsperr command. The syntax for the dsperr command is as follows: spirit.1.PXM.a > dsperr [-en <error slot>] [-sl<slot number>] The following is a sample report showing error log information. spirita.1.PXM.a > dsperr Error Log for Slot 01:Error Num 32 Firmware version:002.000.001-D_mdamle Product Id:3 Timestamp:05/17/2000-02:29:55 Node name:spirita Section Number 0: Event Logged: 01-00304 05/17/2000-02:29:55 SSI-4-MEMBLKERROR E:00032 tTnCmdTsk0 0x80063614 Memory Block Error:invalid start magic word value 0x80898b00 block 0x81f866a8 in ssiFree. Section Number 1: Stack Trace: 0x805d2d24 vxTaskEntry 0x80072114 sysTaskSetup 0x8019c824 cliCmdTask 0x8019bf98 cliCmdExec 0x801f9e1c GetSizes 0x801f9a50 sysDiskPartitionInfoShow 0x8055d818 snmpSsiFree 0x8006181c ssiFree 0x80063614 ssiMemErrorLog 0x8005e10c ssiEvent 0x8005e648 ssiEventMsgReport + -------------- +00c:sysTaskSetup+0() +09c:cliCmdTask+0() +478:cliCmdExec+0() +270:GetSizes+0() +3a8:sysDiskPartitionInfoShow+0() +0e0:snmpSsiFree+0() +024:ssiFree+0() +0e8:ssiMemErrorLog+0() +06c:ssiEvent+0() +24c:ssiEventMsgReport+0() +284:ssiStackTrace+0() Type <CR> to continue, Q<CR> to stop: Cisco SES PNNI Controller Software Configuration Guide Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 6-7 Chapter 6 Viewing and Responding to Alarms Displaying Error Information Cisco SES PNNI Controller Software Configuration Guide 6-8 Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 C H A P T E R 7 Network Management This chapter describes the following network management tools you can use with SES controllers and PNNI networks: • Cisco WAN Manager SES Controller PNNI Features • WAN CiscoView 3.2 • Call Tracing • Call Tracing Minimum System Requirements The following sections describe the hardware and software components that make up the Cisco WAN Manager (CWM) network management workstation. Hardware This section lists the hardware requirements for a Cisco WAN Manager network management workstation. Table 7-1 lists the minimum workstation requirements. Using a workstation that meets these requirements ensures sufficient performance. Table 7-1 Minimum CWM Release 10.2 Workstation Requirements Component Minimum Requirement Workstation Sun Ultra 10 Memory 512 MB CPU Speed 440 MHz Hard Disk Drive 9.1 GB Graphics Card 24-bit Monitor 19 inch Cisco SES PNNI Controller Software Configuration Guide Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 7-1 Chapter 7 Network Management Minimum System Requirements Three types of machines are supported for WAN Manager 10.2 as standard platforms. They are low-end, mid-range, and high-end platforms. Table 7-2 describes the configuration for each platform. Table 7-2 Platform Type Sun Platform Requirements Number of CPUs Size of RAM Hard Disk Drive Swap Space Desktops Supported Connections Supported 1 512 MB One 9 GB 1 GB Less than 5 Less than 5,000 Mid Range Sun Ultra Enterprise 2 option 1 Model 2300 or Ultra 60 2 1 GB Two 9 GB drives 2 GB 5—10 5,000—50,000 Mid Range Sun Ultra Enterprise 2 option 2 Model 2300 or Ultra 60 2 2 GB Two 9 GB drives 2 GB 10—20 50,000— 100,000 High End at least 4 4 GB Two 9 GB drives or disk array 4 GB More than 20 More than 100,000 Low End Machine Type Sun Ultra Enterprise 1 Model 151 or Ultra 10 with SCSI controller Sun Enterprise 4000 or Enterprise 450 Note The minimum CPU speed requirement for all but the low end platforms is 300 MHz. All platforms require a 24-bit graphics card. The selection of a proper CWM platform depends on a number of factors, such as, the number of CWM desktops, the number of managed connections, and the number of statistics collected and stored. Table 7-2 lists recommended CWM platforms based on the size of the network. The following are additional notes for CWM platform requirements: • For every additional CWM desktop application, an additional 8 MB of RAM is needed beyond the standard platform configuration. • You may upgrade the standard configuration such as CPU speed, RAM size, and disk space for future expansion. • The default disk size for the Informix raw database is 900 MB. 2 GB disk space is recommended for the statistics collection process. • If the X server crashes for any reason while CWM is running, CWM should be stopped and restarted. • While CWM is running, if the remote display is killed without properly shutting down the CWM Desktop, then reopening it remotely may not succeed. • CWM must be started from a CDE environment. • For every additional CiscoView instance for BPX/IGX/MGX 8220, you need 7 additional MB of RAM and 4 additional MB of swap space beyond the CWM standard. Cisco SES PNNI Controller Software Configuration Guide 7-2 Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 Chapter 7 Network Management Installing and Configuring Cisco WAN Manager Software This section lists the required software to install on the Cisco WAN Manager Network Management workstation to manage the SES controller and PNNI networks. • Release 10.5 CWM (including CiscoView 5.1) • Solaris 2.7 • Informix 9.2 • Orbix 3.0 • Orbix Web 3.1 • WingZ 2.5.5 • HPOV 6.1.0 HP OpenView 6.1 is not bundled with CWM CDs. You must order HP OpenView separately. For HP OpenView installation requirements and procedures, refer to the HP OpenView Network Node Manager Products, Installation Guide (part number J1136-90000 from HP). • BPX 9.2.33 • PNNI 1.0 Installing and Configuring Cisco WAN Manager Refer to the appropriate chapters in the Cisco WAN Manager Installation Guide for Solaris, Release 10.5 for general workstation setup (including disk partitioning) and installation procedures. Disk Partitioning Requirements A change in the installation procedure requires that you use the following disk partitioning requirements instead of those found in the CWM 10.5 Installation Guide for Solaris (Doc-7810308=). Sufficient disk space and proper disk partitioning are essential to achieving the best performance from CWM and your network management workstation. Note The minimum disk space requirement for CWM 10.5 is one 9-GB disk drive. Use the following commands to gather some of the required information: • dmesg—Provides information about the workstation type, amount of memory and CPU speed. • format—Enables you to determine information about the disk drives on your workstation. Select a disk from the list of those available, and enter the verify command to determine the current partitioning of each disk. Cisco SES PNNI Controller Software Configuration Guide Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 7-3 Chapter 7 Network Management Installing and Configuring Cisco WAN Manager Partitioning One 9-GB Disk This section describes how to partition a CWM workstation’s single 9-GB disk drive. Use the information in Table 7-3 to ensure that all but the final partition will be at a set size. Note The actual total disk space for a 9-GB disk varies depending on the manufacturer of the disk. One 9-1 GB disk might have 9.05 GB of available space, while another might only have 8.9 GB of space available. Other disk drive flaws also limit disk capacity. Most disks will NOT have a full 9.1 GB, and the slice 2 (s2) total will vary. Table 7-3 Partitioning a Single 9-GB Disk Slice Partition Space Comments s0 / 2000 MB Allocate third. s1 swap 1030 MB Allows for memory upgrade to 1 GB; allocate second. s2 <overlap> 8996 MB Total amount of space on the disk; do not attempt to modify. s3 /opt 500 MB Allocate fourth. s4 /var 1000 MB Allocate fifth. /usr/users 2500 MB Must be 2000 MB; allocate first. 1966 Raw partition; might be less than this amount; allocate last. s5 s6 s7 Note To check the running total of remaining disk space, click any partition to update the total free value. When the total free value is 0 free and a rounding error of 0 or 1, click OK. Cisco SES PNNI Controller Software Configuration Guide 7-4 Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 Chapter 7 Network Management Installing and Configuring Cisco WAN Manager Partitioning Two 9-GB Disks This section describes how to partition a CWM workstation that has two 9-GB disk drives. When you install Solaris, partition the first disk drive as shown in Table 7-4. Note Do not partition the second disk. The second disk is automatically partitioned during the CWM software installation. Table 7-4 Partitioning the First 9-GB Disk Slice Partition Space Comments s0 / 2000 MB Allocate third. s1 swap 1030 MB Allows for memory upgrade to 1024 MB; allocate second. s2 <overlap> 8996 MB Total amount of space on the disk; do not attempt to modify. s3 /opt 1000 MB Allocate fourth. s4 /var 1000 MB Remainder of disk; allocate last. /usr/users 2000 MB Must be 2000 MB; allocate first. s5 s6 s7 Note The total disk space should equal the space shown in s2. Modifying the network.conf File for PNNI Networks For PNNI networks using in-band management, provide the following information for your network: NETWORK:Network2 GATEWAYS:sj234567 DISCOVERY PROTOCOL:PNNI Note To save your changes while using the vi editor, remember to press Esc, colon (:), then wq!. Cisco SES PNNI Controller Software Configuration Guide Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 7-5 Chapter 7 Network Management Installing and Configuring Cisco WAN Manager Configuring PNNI Topology Discovery Use the Topology Configurator to provide information required to communicate with the nodes. Also use the configurator to specify Network IP. Note These are nodes that have their SNMP community string for GET operations not set to public, and SNMP community string for SET operations not set to private. Configuring the SES Controller To configure a PXM card, telnet to the card and enter the following shellConn commands: pxm1> shmsimulateresetReason 0 pxm1> deltree “D:/DB2” Note The above commands are used when inconsistency exists between the database and the image. pxm1> addpnport 9.1 pxm1> cnfpnportsig 9.1 -nniver pnni10 assumes a BXM in slot 9 Cisco WAN Manager SES Controller PNNI Features Cisco WAN Manager (CWM) provides the following features for the SES controller: • SPVC connection management between Release 1.0 SES controllers with BXM cards at each endpoint. • Connection trace • Connection testing • End-to-End connection alarms • End-to-End connection template • Connection database • Java-based CM GUI and service class template GUI Cisco SES PNNI Controller Software Configuration Guide 7-6 Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 Chapter 7 Network Management WAN CiscoView 3.2 SPVC Overview Table 7-5 lists the types of SPVCs supported by the SES controller using CWM Release 10.5. Table 7-5 Supported SPVC Connections Endpoint 1 Endpoint 2 SPVC Connection Type Node Type BXM BXM ATM SPVC Routing nodes on BPX with feeder node on SES WAN CiscoView 3.2 The SES controller is managed through WAN CiscoView 3.2. WAN CiscoView 3.2 requires Release 5.1 of the CiscoView Engine, which is included on the CWM Release 10.5 CD. CiscoView Release 5.1 has been migrated from X/MOTIF to a JAVA based application. WAN CiscoView 3.2 supports line, port and resource partition configuration and real-time counters on SES controllers. The look and feel of CiscoView 5.1 is slightly different from CiscoView 4.2, but most dialog screens will be familiar to experienced CiscoView users. Rear view selection (normally done by selecting the outer part of the device with the right mouse button) is not available for the SES controller. Installing CiscoView During the CWM Release 10.5 installation process, CiscoView 5.1 and BPX-SES device packages are installed for you. This eliminates the need to incrementally select device packages to install. Accessing CiscoView Accessing CiscoView is a simple task. From the CWM Release 10.5 Topology Map, a device can be selected for management by CiscoView. Navigating in CiscoView When you start CiscoView, the CiscoView main window opens. The following components comprise the CiscoView main window: • Select Device drop-down list box • Device Commands buttons • Main Menu buttons • Graphical Device display window Cisco SES PNNI Controller Software Configuration Guide Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 7-7 Chapter 7 Network Management WAN CiscoView 3.2 Select Device Drop-Down List Box Use the Select Device drop-down list box to select and display a device. Either enter a device name or IP address, or select from the recently displayed devices listed. Device names and SNMP read and write community strings are preserved when you open new CiscoView sessions. Device Commands Buttons Use the device command buttons to activate device commands unique to the displayed device. The device command buttons are described in the online help for each device package. Main Menu Buttons Use the Main Menu buttons to perform various CiscoView tasks. Graphical Device Display Window Use the Graphical Device Display window to view a graphical display of the device’s back or front panel once you select a device. The display shows all device components color-coded according to their current status and refreshed according to your polling frequency. If a hot swap is detected, the device is rediscovered and the display redrawn at the next poll. Status Bar and Buttons Use the Status Bar and buttons to display the result of device polling, selections, and so on. Main Menu Buttons Table 7-6 describes the Main Menu buttons. Table 7-6 CiscoView Main Menu Buttons Main Menu Button Description Telnet Launches a Telnet command-line session to the managed device. CCO Launches a separate browser containing the Cisco Connection Online (CCO) web page. This feature is not supported in WAN CiscoView 3.2. Cisco Support Opens the TAC Mailer dialog box for sending reports to the Cisco Technical Assistance Center (TAC) group. You can describe the problem using the available options and the comment field. When you click Send, your descriptions and information about the runtime device package and operating environment are sent to the specified mail recipients. This feature is not supported in WAN CiscoView 3.2. Preferences Opens the Preferences dialog box where you can specify SNMP and community string. The preferences settings are preserved for all new CiscoView 5.1 sessions. Cisco SES PNNI Controller Software Configuration Guide 7-8 Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 Chapter 7 Network Management WAN CiscoView 3.2 Table 7-6 CiscoView Main Menu Buttons (continued) Main Menu Button Description About Displays the following information: Help • CiscoView release version and copyright • Active device package, if applicable • All installed device package information Opens CiscoView 5.1 help if no device is selected. Opens context help if a device or component is selected. This feature is not supported in WAN CiscoView 3.2. Status Bar and Buttons Table 7-7 describes the options on the status bar and buttons. Table 7-7 CiscoView Status Bar and Buttons Status Bar/Button Description Status Bar Displays the progress and result of device polling, selections, and so on. System Info Button Displays system information (name, description, location, contact, and up-time) for a displayed device. Print Button Prints the current graphical display. Color Legend Button Describes the significance of the colors on the graphical display. Color schemes are listed below: • Blue or Gray—Port is dormant. • Orange—Port is down. • Red—Port failed. • Yellow—Port has a minor failure. • Purple—Port is being tested. • Green—Port is active. Making Selections and Displaying Menus When you select a device in CiscoView, a graphical representation of the device is displayed. You view the front device panel and select different components and menu options to configure and monitor status for these devices. Cisco SES PNNI Controller Software Configuration Guide Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 7-9 Chapter 7 Network Management WAN CiscoView 3.2 Popup Menu Options Table 7-8 describes the options on the popup menu. Table 7-8 Cisco View Popup Menu Options Popup Menu Option Description Configure Configures device categories, such as Node Management, NNI, and so on. Monitor Displays a set of dynamic charts for selected device categories. Front and Rear Displays either the front or back device panel. The BPX-SES has only a front panel view. Resize Reduces the graphical display down to 90%, 80%, 70%, 60%, or 50%. You can resize the window back up to 100% after you have reduced it. Refresh Triggers component polling and display update. System Info Displays system MIB information (name, description, location, contact, and up-time) for a device. Using CiscoView Once you install CiscoView and learn to navigate within it, you can perform various tasks. Starting CiscoView Depending on the platform, you can start CiscoView. • Within CWM Release 10.5, select a device on the Topology map. • From the CLI, enter the ~svplus/wancv/bin/cvw command. Selecting a Device Select a device to view its graphical representation to configure and monitor it. The device names and SNMP read and write community strings are preserved when you open new CiscoView sessions. Setting Preferences Use the Set Preferences option to change certain options within CiscoView. Selecting a Component Select a component on the graphical device display to configure and monitor it. Cisco SES PNNI Controller Software Configuration Guide 7-10 Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 Chapter 7 Network Management WAN CiscoView 3.2 Configuring Your Device Use the Configure menu to configure multiple categories of information, for example, Interface, Management, Physical, and ARP Table, simultaneously. Different categories of information can be displayed for each device, card, and port. To see the categories of information that can be displayed for each component type, look at the Category pop up menu from the Configuration window. Monitoring Your Device Use the Monitor menu to monitor multiple categories of information, for example, Ethernet collisions, Management, Physical, and ARP Table, simultaneously. The Monitoring dialog is non-modal and resizeable. Preference Setting Options Setting Community Strings Use the Preferences Community tab to delete the read and write community strings for the device currently being managed. This lets you enter the read and write community strings for a device after you display the device. If you want to make changes to a device or port setting, but did not specify community string when you first opened the device display, you can enter the community string without exiting and reopening the device window. If a host’s community strings are not already defined within CiscoView, you can add them with the CiscoView Community Strings dialog. Otherwise, CiscoView allows you to enter the correct community strings when you try to access the host. If you do not enter a host’s community strings when accessing the host, CiscoView uses the default read and write community strings of public and private. Setting SNMP Preferences Use the Preferences SNMP tab to set polling frequency, SNMP timeout and retries, and default read and write community strings. The recommended values for preferences are as follows: • Polling Frequency (sec.): 60 • SNMP Timeout (sec.): 20 • SNMP Retry Count: 1 • Show MIB Label as: Alias Use the Default Read and Write Community fields to define the community strings that CiscoView automatically uses for device when you do not specify the device’s current community strings. Cisco SES PNNI Controller Software Configuration Guide Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 7-11 Chapter 7 Network Management WAN CiscoView 3.2 Device-Specific Buttons within Configure Menu Table 7-9 describes the Configure menu buttons. Table 7-9 Configure Menu Buttons (Device Specific) Device-Specific Buttons Description OK Writes modification of all categories to managed device then closes the dialog box. Apply Writes modification of the current category to managed device, leaving the dialog box open. Cancel Aborts changes and closes the catalog list. Print Prints the current category. Help Launches device-specific help. Create Launches a table row creation dialog box. Delete Deletes a selected row from the table. Integrating New Device Information Use the Device Support Utility to integrate new Cisco device information asynchronously with the CiscoView engine, uninstall device packages, install new device packages, or upgrade existing installed packages. The Device Support Utility operates in one of two modes: Interactive mode or Command Line mode. The functionality of both modes is similar; the only difference between the two is that Interactive mode provides a Graphical User Interface (GUI). Each mode allows the user to display a list of currently installed device packages and their versions, uninstall one or more packages, and automate device package installations and upgrades. Cisco SES PNNI Controller Software Configuration Guide 7-12 Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 Chapter 7 Network Management Testing Basic Connectivity and Setup Device Support Utility Features Use the Device Support Utility to perform the following tasks: • Install and uninstall device packages. • Upgrade device packages. • View a list of currently installed device packages and their versions. Using the Device Support Utility Starting the Device Support Utility From a UNIX platform, you can start the Device Support Utility by running the script “xdsu” from the ~svplus/wancv/bin directory. Installing Device Packages In Interactive mode, the Install Device Packages dialog box installs new device packages or upgrades existing packages. The Device Support Utility will not allow you to select a package whose superseding version has already been installed in the package repository. Uninstalling Device Packages In Interactive mode, the Device Support Utility dialog box shows a list of the device packages that are already installed. It also acts as a launch point for uninstalling device packages. Testing Basic Connectivity and Setup The following sections describe how to test the basic connectivity and setup for CiscoView. Perform the following steps when you have a CiscoView-related problem: Step 1 Test IP the Connectivity Step 2 Open a Telnet Session to the Device Step 3 Verify the CiscoView Preferences Test the IP Connectivity From the UNIX workstation, try to ping the router’s IP address. If the ping is unsuccessful, make sure that IP routing is properly enabled and is functioning. Use “ping -s” to check for slow IP response. Ping the device by its Network IP as well as by its LAN IP address. If you can ping the device by its LAN IP address but not its Network IP address, there is a Network IP problem. Consult your system administrator for assistance in resolving this problem. Cisco SES PNNI Controller Software Configuration Guide Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 7-13 Chapter 7 Network Management Call Tracing Open a Telnet Session to the Device Enter the dspsnmp command to view the SNMP configuration and verify the community strings. If the strings are not correct, configure the device with the cnfsnmp command. Verify the CiscoView Preferences Use the Preferences SNMP tab to set polling frequency, SNMP timeout and retries, and default read and write community strings. The recommended values for preferences are as follows: • Polling Frequency (sec.): 60 • SNMP Timeout (sec.): 20 • SNMP Retry Count: 1 • Show MIB Label as: Alias Call Tracing The SES controller supports the Call Trace feature as two distinct facilities, as defined by ATM Forum PNNI v2.0 Living List, July ‘98. • Connection Trace—Allows you to trace an existing connection. • Path Trace—Allows you to trace the calls in real time. Both these facilities can be used to trace a call in the Control Plane. Connection Trace The Connection Trace facility can be used to determine the path taken by an existing connection from any node in the network to the destination node of the call. You initiate the trace of a connection through the SES CLI by providing the ingress interface, the call reference for Call Ref or VPI/VCI. This generates a TRACE CONNECTION message, which includes Trace Transit List (TTL) IE. This message will travel towards the node which has the called address. Each node fills up TTL IE with node ID and Egress logical port ID and passes the message on. The egress logical port ID is obtained from the call record of the existing connection, using CallRef and VPI/VCI. The destination node makes the portID zero. This feature is not supported on an IISP/AINI interface, neither for the transporting of IEs nor for the processing of the IEs. Connection Trace Success The destination node copies the TTL IE as is into TRACE CONNECTION ACK message, and sends it back to the source node with the following status: trace completed normally Use the Trace Transit List to find the path taken by an existing connection. Cisco SES PNNI Controller Software Configuration Guide 7-14 Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 Chapter 7 Network Management Call Tracing Connection Trace Failure A connection trace may fail at any node for the following reasons: 1. Message is dropped as it is not supported. 2. Trace can not be progressed to the destination node due to some failure (say the call is already released, or call release is in progress). You are then informed of these failure events, with appropriate cause values along with the TTL up to the last node which sent the failure message back. CLI Commands Functionality Refer to the Cisco SES PNNI Controller Software Command Reference, Release 1.1 for command syntax details. conntrace Command Refer to the Cisco SES PNNI Controller Software Command Reference, Release 1.1, for the full syntax of the conntrace command Figure 7-1 shows the section within which a call can be traced. For instance, you could start the trace for a call setup between SRC and DST. The Trace Connection message would terminate at the IISP interface and an ACK/NACK would be sent back. This would enable the user to complete a partial trace. Figure 7-1 Connection Trace in PNNI and IISP Network PNNI Cloud PNNI Cloud Foreign switch IISP DST SRC Trace Connection Trace Connection 56139 IISP Active Call -End to End Path Trace Path Trace facility allows you to trace calls in real time. You enable or disable this feature node wide, on a per UNI interface basis or based on called party/calling party number. When enabled, the source node adds a TTL IE as part of the Setup/AddParty message and subsequent nodes supporting this feature add their own TTL IE. Various flags can be turned ON/OFF as part of the TTL on the source node, enabling a user to filter details on the trace. These flags are 1. Hierarchy (H)—Information from all the DTLs in the hierarchy are added if this flag is enabled, as defined in the ATM Forum specifications. 2. Crankback (CB)—If a call fails with a Crankback, the cause value is inserted in the TTL IE. Cisco SES PNNI Controller Software Configuration Guide Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 7-15 Chapter 7 Network Management Call Tracing Note This feature is not a safeguard against mis-configuration, to prevent the calls from being released inadvertently. 3. VPI/VCI values (V): If enabled, VPI/VCI values of the egress port are filled up in the TTL IE at every node. 4. Call Reference values (CR): If enabled, Call Reference values of all the egress ports are filled up in the TTL IE. Path trace information for all the traced calls are stored in the trace log file, where they can be display information on the CLI screen. Calling and Called Path Trace Success Use the dsplog command to display the information from the response message. This information includes the path and result of the return code. Path Trace Failure Path trace fails due to similar reasons specified above for Connection Trace Fail. However, since this is a real-time trace, the node detecting the failure fills in the proper information in TTL IE, apart from filling up the Release Message. An IISP interface is treated similarly to a UNI interface and the trace is terminated. SES CLI Pathtrace Commands The Pathtrace commands are as follows: • pathtracenode • pathtraceport • pathtraceie Their syntax is described in the Cisco SES PNNI Controller Software Command Reference, Release 1.1 , Chapter 2, “SVC, SPVC, and PNNI Commands.” pathtracenode If path trace is enabled, the source node adds the TTL IE in the Setups depending on the flags set. The via node processes this IE and adds the relevant octets into the IE. The signaling stack checks this flag before decoding TTL IE in an incoming setup message. It then checks this flag before starting TTL IE encoding procedures for an outgoing call. pathtraceport The pathtraceport command is for incoming calls on a source node. Signaling checks these flags/parameters before generating/decoding the TTL IE. If the user selects disable, the rest of the parameters are ignored. Cisco SES PNNI Controller Software Configuration Guide 7-16 Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 Chapter 7 Network Management Call Tracing pathtraceie The pathtraceie command is used for interoperability when the SES controller is connected to equipment that does not support path trace. It takes the following two option:. • rmv This command option allows you to control/handle Path trace on a interface level, when the PNNI network is connected to another through an IISP link, or to another PNNI network that does not support this facility. When this command is issued, TTL IE would be removed from all subsequent Setup messages going out on that interface, and would be reinserted to Connect/Release/Rls_Comp messages coming back for the same call. This ensures interoperability with other vendors’ switches. All other flags would be ignored when issued with the removeIE flag. It would also remove the TTL IE from the connect message going out on that interface. • ins This option inserts the TTL IE to any incoming Setup/Connect message. The direction of this option is exactly opposite of removeIE option. Both these options can be applied on any interface on any via node. Figure 7-2 illustrates a sample network with pathtrace insert and remove IEs. Figure 7-2 Insert and Remove IEs Foreign Switches PNNI Controller PNNI Controller PNNI Controller IISP PNNI PNNI Controller IISP SRC DST Connect - insert IE Remove IE / Insert IE Connect - insert IE 56140 Setup - remove IE Setup - remove IE The SES controller supports Connection Trace and Path trace facility for maximum 10-hops network and maximum 5 traces are allowed to be in progress at a time. The trace log file is recycled every time it reaches 1 MB in size. Cisco SES PNNI Controller Software Configuration Guide Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 7-17 Chapter 7 Network Management Call Tracing Cisco SES PNNI Controller Software Configuration Guide 7-18 Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 A P P E N D I X A Downloading and Installing Software Upgrades Upgrade Process Overview This appendix provides a series of quickstart procedures that describe how to perform graceful and non-graceful upgrades to the controller. To perform a graceful upgrade on a controller card, the card must be operating in redundant mode with another controller card of the same type. When performed properly, graceful upgrades have minimal impact on connections in progress and do not interrupt any established connections. When a card to be upgraded is not operating in redundant mode, you must do a non-graceful upgrade, which disrupts all traffic that passing through the card and through the controller. When you upgrade the software in the SES Controller, you should refer to the Release Notes for Cisco WAN SES Controller Software Release 1.1 for the latest information. Each type of controller card runs boot and runtime software. The recommended sequence for upgrading the software on a controller card is as follows: • PXM boot software • PXM runtime software Typically, the boot software requires less frequent upgrades. Some upgrades might only require updates to one type of controller card. Release Notes for Cisco WAN SES Controller Software Release 1.1 should explain which software components require upgrading. When you upgrade the software on a controller card, proceed as follows: • Decide whether you are performing a graceful or non-graceful upgrade • Follow the appropriate quickstart procedure for that type of upgrade. For additional information on a task within a quickstart procedure, see the appendix section to which the procedure refers. The next section presents the quickstart procedure for controller card software upgrades. Quickstart Procedures for Software Upgrades The following sections provide quickstart procedures for the following upgrades: • Graceful PXM Boot Upgrades • Non-Graceful PXM Boot Upgrades Cisco SES PNNI Controller Software Configuration Guide Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 A-1 Appendix A Downloading and Installing Software Upgrades Quickstart Procedures for Software Upgrades Graceful PXM 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 PXM cards updates the standby card and then makes that card active. This method ensures a smooth transition to the new software and preserves all established calls. Any calls that are not established are lost. 1. A graceful upgrade of the boot software does the following: 2. Loads the new software on the standby PXM card 3. Makes the standby PXM card active 4. Loads the new software on the formerly active (now standby) PXM 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 controller. See “Copying Software Files to the Controller,” which appears later in this appendix. Step 2 username password Step 3 saveallcnf Establish a CLI session with the standby PXM card using the CP port on the UI-S3 back card and a user name with CISCO_GP privileges. This optional step saves the current configuration to the hard disk. Refer to “Saving a Configuration” in Chapter 5, “Switch Operating Procedures.” Step 4 sh Change to the PXM Backup Boot mode. sysBackupBoot <Return> Step 5 sysPxmRemove At the backup boot prompt, enter the sysPxmRemove command: This step prevents the active card from resetting the standby card while you are working with it. Step 6 burnboot “Filename” Burn the boot code. Remember to enter quotation marks before and after the boot software filename. For example: reboot burnboot “C:FW/pxm1_001.001.060.000_bt.fw” username password See “Upgrading PXM Boot Software,” which appears later in this appendix. dspcd Step 7 username password Step 8 switchcc y Establish a CLI session with the active PXM 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. controller the roles of the active and standby cards so you can upgrade the non-upgraded card in standby mode. Cisco SES PNNI Controller Software Configuration Guide A-2 Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 Appendix A Downloading and Installing Software Upgrades Quickstart Procedures for Software Upgrades Step 9 Command Purpose sh Change to the PXM Backup Boot mode. sysBackupBoot <Return> Step 10 sysPxmRemove At the backup boot prompt, enter the sysPxmRemove command: This step prevents the active card from resetting the standby card while you are working with it. Step 11 burnboot “Filename” Burn the boot code. Remember to enter quotation marks before and after the boot software filename. For example: reboot burnboot “C:FW/pxm45_002.001.000.000_bt.fw” username See “Upgrading PXM Boot Software,” which appears later in this appendix. password dspcd Both active and standby cards should now be upgraded. The card that was active before the upgrade is now operating in standby mode. Non-Graceful PXM Boot Upgrades Ungraceful upgrades disrupt all controller traffic and are usually used in lab installations where the use o f standalone cards provides no opportunity for a graceful upgrade. The quickstart procedure is provided as an overview and as a quick reference for those who have already performed ungraceful upgrades on the controller. Step 1 Command Purpose ftp Copy the boot and runtime files you want to use to the controller. See “Copying Software Files to the Controller,” which appears later in this appendix. Step 2 Step 3 username password Establish a CLI session with the active PXM card using the CP port on the UI-S3 back card and a user name with CISCO_GP privileges. saveallcnf This optional step saves the current configuration to the hard disk. Refer to Refer to “Saving a Configuration” in Chapter 5, “Switch Operating Procedures.” Step 4 sh Change to the PXM Backup Boot mode. sysBackupBoot <Return> Cisco SES PNNI Controller Software Configuration Guide Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 A-3 Appendix A Downloading and Installing Software Upgrades Quickstart Procedures for Software Upgrades Command Purpose Step 5 sysPxmRemove If the controller has two PXM cards installed in it, enter the sysPxmRemove command, which prevents the active card from resetting the standby card while you are working with it. Step 6 burnboot “Filename” Burn the boot code. Remember to enter quotation marks before and after the boot software filename. For example: reboot username password dspcd burnboot “C:FW/pxm45_002.001.000.000_bt.fw” See “Upgrading PXM Boot Software,” which appears later in this appendix. Graceful PXM Runtime Software Upgrades When performed properly, graceful upgrades have minimal impact on connections in progress and do not interrupt any established connections. This quickstart procedure applies to PXM cards and does the following: 1. Loads the new software on the standby PXM card 2. Makes the standby card active 3. Loads the new software on the formerly active (now standby) 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 controller. See “Copying Software Files to the Controller,” which appears later in this appendix. Step 2 If the Release Notes for Cisco WAN SES Controller Software Release 1.1 call for a boot software upgrade, upgrade the boot software for the card you are upgrading. PXM cards should be upgraded first. See “Graceful PXM Boot Upgrades,” which appears earlier in this appendix. Step 3 username password Step 4 saveallcnf Establish a CLI session with the active PXM card using a user name with SERVICE_GP privileges. This optional step saves the current configuration to the hard disk. Refer to Refer to “Saving a Configuration” in Chapter 5, “Switch Operating Procedures.” Step 5 dspcd Verify that all previous upgrades have been committed. commitrev <slot> <revision> If a previous upgrade has not been committed, commit to the new upgrade. See “Committing to a Runtime Software Upgrade,” which appears later in this appendix. Step 6 loadrev <slot> <revision> Load the new runtime software on the standby PXM. dspcd Cisco SES PNNI Controller Software Configuration Guide A-4 Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 Appendix A Downloading and Installing Software Upgrades Quickstart Procedures for Software Upgrades Step 7 Command Purpose runrev <slot> <revision> Switch over to the standby PXM card and load the new runtime software on the new standby (non-upgraded) PXM. dspcd dspcd <slot> Step 8 commitrev <slot> <revision> Optional. This command prevents an accidental switch back to a previous software revision if someone enters the abortrev command. Enter the commitrev command after the former active PXM comes up in the standby-U state. Non-Graceful PXM Runtime Software Upgrades Ungraceful upgrades disrupt all switch traffic and are usually used in lab installations where the use of standalone cards provides no opportunity for a graceful upgrade. The quickstart procedure is provided as an overview and as a quick reference for those who have already performed ungraceful upgrades on the controller. Step 1 Command Purpose ftp Copy the boot and runtime files you want to use to the controller. See “Copying Software Files to the Controller,” which appears later in this appendix. Step 2 Step 3 If the Release Notes for Cisco WAN SES Controller Software Release 1.1 call for a boot software upgrade, upgrade the boot software as described in “Non-Graceful PXM Boot Upgrades,” which appears earlier in this appendix. username password Step 4 saveallcnf Establish a CLI session with the active PXM card using a user name with SERVICE_GP privileges. This optional step saves the current configuration to the hard disk. Refer to Refer to “Saving a Configuration” in Chapter 5, “Switch Operating Procedures.” Step 5 dspcd Verify that all previous upgrades have been committed. commitrev <slot> <revision> If a previous upgrade has not been committed, commit to the new upgrade. See “Committing to a Runtime Software Upgrade,” which appears later in this appendix. Step 6 loadrev <slot> <revision> Define the new software version to be used. dspcd Cisco SES PNNI Controller Software Configuration Guide Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 A-5 Appendix A Downloading and Installing Software Upgrades Quickstart Procedures for Software Downgrades Step 7 Command Purpose runrev <slot> <revision> Reset the card and run the new software version. dspcd Step 8 commitrev <slot> <revision> Optional. This command prevents an accidental switch back to a previous software revision if someone enters the abortrev command. Enter the commitrev command after the former active PXM comes up in the standby-U state. Quickstart Procedures for Software Downgrades Cisco Systems, Inc., recommends that you avoid software downgrades, which replace a current software release with another that has a lower version number. However, there are some situations in which you might want to downgrade the software. For example, if you have been testing pre-release software in a lab, the software version number can be higher than a later official software release. Any time the software version number to which you are changing is lower than the current software version, the change is a downgrade, regardless of when the software versions are released. The following sections provide quickstart procedures for the following downgrades: • PXM Boot Downgrades • Non-Graceful PXM Runtime Software Downgrades PXM 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 in “Graceful PXM Boot Upgrades.” Caution Cisco Systems, Inc., does not guarantee that any software downgrade is graceful, so assume that the downgrade is non-graceful and time the downgrade accordingly. The advantage to following the graceful upgrade procedures listed above is that you might be able to delay traffic interruption until the runtime software is downgraded. When upgrading a standalone card, the downgrade is non-graceful, and you should follow one of the following software upgrade procedures in “Non-Graceful PXM Boot Upgrades” Cisco SES PNNI Controller Software Configuration Guide A-6 Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 Appendix A Downloading and Installing Software Upgrades Quickstart Procedures for Software Downgrades Non-Graceful PXM Runtime Software Downgrades To downgrade PXM runtime software, you must clear the entire controller configuration.All traffic is disrupted until the controller downgrade is complete and the configuration has been re-entered. The following quickstart procedure is provided as an overview for PXM runtime software downgrades. Note Step 1 The controller does not support a configuration restore to a downgraded software version. When you downgrade the PXM runtime software, you must re-enter the configuration. Command Purpose username Establish a CLI session with the active PXM card using a user name with SERVICE_GP privileges. password Step 2 saveallcnf Save the current controller configuration. y See “Saving a Configuration” in Chapter 5, “Switch Operating Procedures.” This step gives you the option to upgrade to the software version from which you are downgrading and use the former configuration. Step 3 ftp Copy the boot and runtime files you want to use to the controller. Also copy the saved configuration file from the C:CNF directory to a remote workstation so you have a backup file if something happens to the hard disk. See “Copying Software Files to the Controller,” which appears later in this appendix. Step 4 Step 5 clrallcnf Clear the current configuration. y See “Clearing a Configuration” in Chapter 5, “Switch Operating Procedures.” sysVersionSet “version” Select the runtime firmware version the controller will use on the PXM card and restart the controller with that firmware. For example: reboot sysVersionSet “002.001.000.000” Note that these commands must be entered at the PXM backup boot prompt: pxmbkup>. Refer to “Initializing the Controller” in Chapter 2, “Configuring General Switch Features.”. Step 6 Reconfigure the PXM cards as described in “Configuration Quickstarts” in Chapter 2, “Configuring General Switch Features.” Cisco SES PNNI Controller Software Configuration Guide Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 A-7 Appendix A Downloading and Installing Software Upgrades Browsing the File System Browsing the File System The PXM hard disk stores log files, configuration files, and boot and runtime software. The controller operating system supports a set of UNIX-like commands that you can use to locate log files or manage software updates. Table A-1 lists commands that you can use to browse the file system. Note File and directory names in the controller file system are case sensitive. Also, some of the commands listed in Table A-1 are not available at all administrator access levels. Table A-1 File System Commands Command Description cd Change directories. Access level required: ANYUSER or above. copy Copies a file from one location to another. Syntax: copy <source file name> <destination file name> Access level required: GROUP1 or above. del Deletes a file. Syntax: del <file name> Access level required: GROUP1 or above. ll List directory contents using long format, which includes the name, size, modification date, and modification time for each file. This command also displays the total disk space and free disk space. Syntax: ll Access level required: ANYUSER or above. ls List directory contents using the short format, which displays filenames, total disk space, and free disk space. Syntax: ls Access level required: ANYUSER or above. pwd Display the present working directory. Syntax: pwd Access level required: ANYUSER or above. rename Renames a file. Syntax: rename <old file name> <new file name> Access level required: GROUP1 or above. whoami Lists the login name for the current session. Syntax: whoami Access level required: ANYUSER or above. Cisco SES PNNI Controller Software Configuration Guide A-8 Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 Appendix A Downloading and Installing Software Upgrades Locating Software Updates Locating Software Updates For information on locating software updates, refer to the Release Notes for Cisco WAN SES Controller Software Release 1.1. Copying Software Files to the Controller This section describes how to copy software files to the SES controller . The PXM cards use boot software and runtime software. Each PXM 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. Note The boot and runtime software are installed on the controller at the factory. Before you copy new files to the controller, verify that you need to update them by comparing the file versions on the disk to those recommended in the Release Notes for Cisco WAN SES Controller Software Release 1.1. The SES controller provides a File Transfer Protocol (FTP) service to support file transfers to the controller. If you have FTP client software and network connectivity to both the controller and the server where the software files are stored, you can use FTP to transfer files directly from the server to the controller. Note The following procedure describes how to copy files to the controller when the runtime software is up and running (showing the node name switch prompt). When the runtime software cannot load, copy the software files to the controller. Step 1 Refer to the Release Notes for Cisco WAN SES Controller Software Release 1.1 to locate a server from which you can download the files. Step 2 Using a workstation with FTP client software, transfer PXM files from the server to the controller directory C:/FW. The procedure you use for transferring the files depends on the FTP client software you are using. When initiating the FTP connection, remember the following: Step 3 • Select the controller by entering its IP address. • When prompted for a username and password, enter the username and password you use when managing the controller. • When configuring file transfer options, select binary mode for the file transfer. To verify that the new PXM files have been transferred to the controller, log into the controller and display the contents of the C:/FW directory. For more information on browsing the SES Controller file system, see “Browsing the File System,” which appears earlier in this appendix. Cisco SES PNNI Controller Software Configuration Guide Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 A-9 Appendix A Downloading and Installing Software Upgrades Upgrade Procedures for PXM Cards Upgrade Procedures for PXM Cards The following sections describe procedures that support upgrades to PXM cards. For complete upgrade procedures, see “Quickstart Procedures for Software Upgrades,” which appears earlier in this appendix. The procedures in this section detail some of the tasks listed in the quickstart procedures. Upgrading PXM Boot Software This section describes how to upgrade the PXM boot software on a single PXM card. If you are performing a graceful upgrade, use the quickstart procedure described in “Graceful PXM Boot Upgrades,” which appears earlier in this appendix. The following procedure provides detailed information on the upgrade task within the quickstart procedure. Step 1 If you have not done so already, establish a CLI session with the PXM card using the CP port on the UI-S3 back card and a user name with CISCO_GP privileges. Step 2 If you have not done so already, change to PXM Backup Boot mode. Step 3 To burn the boot software on the PXM, enter the burnboot command as follows: pxmbkup> burnboot “filename Replace filename with the complete path to the boot file on the PXM hard drive. For example: pxmbkup> burnboot “C:FW/pxm1_001.001.060.000_bt.fw” Step 4 When the controller prompts you to confirm this action, type y and press Return. When the boot code burning process is complete, the controller displays a message similar to the following: Flash download completed ... value = 0 = 0x0 Step 5 When the boot code has been burned, reset the card with the reboot command. For example: pxmbkup> reboot Be patient and wait for Login prompt to appear. Step 6 When the Login prompt appears, log in to the controller as you do at the beginning of a CLI session. The switch prompt should appear. Step 7 To confirm that the PXM card is now using the correct boot code, enter the dspcd command. Cisco SES PNNI Controller Software Configuration Guide A-10 Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 Appendix A Downloading and Installing Software Upgrades Upgrade Procedures for PXM Cards The Boot FW Rev row in the display should show the new revision as shown in the following example: spirita.1.PXM.a > dspcd espses1 System Rev: 01.00 SES-CNTL Slot Number 1 Redundant Slot: 2 Front Card ---------Inserted Card: PXM1_OC3 Reserved Card: PXM1_OC3 State: Active Serial Number: SBK033300FP Prim SW Rev: 1.0(13) Sec SW Rev: 1.0(13) Cur SW Rev: 1.0(13) Boot FW Rev: 65.1(50.163) 800-level Rev: A0 Orderable Part#: 800-05610-02 CLEI Code: BAA4HCZAAA Reset Reason: On Reset From Shell Card Alarm: NONE Failed Reason: None Miscellaneous Information: Aug. 28, 2001 16:27:58 PDT Node Alarm: MAJOR Upper Card ---------- Lower Card ---------- UIA BackCard UIA BackCard Active SBK0329018V --------A0 800-03688-01 BAI9Y00AAA MMF_4_OC3 MMF_4_OC3 Active SAK032500IE --------A0 800-05053-01 BA2IKNJBAA Type <CR> to continue, Q<CR> to stop: After you confirm the upgrade to the first PXM card, the boot software upgrade for that card is complete. Cisco SES PNNI Controller Software Configuration Guide Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 A-11 Appendix A Downloading and Installing Software Upgrades Upgrade Procedures for PXM 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. For graceful upgrades, the upgrade software is loaded on the standby card first, and then the control is switched to upgraded card so that the other card can be upgraded. The best way to assess the upgrade status of a card is to enter the dspcd <slot> command. For example: spirita.1.PXM.a > dspcd espses1 System Rev: 01.00 SES-CNTL Slot Number 1 Redundant Slot: 2 Front Card ---------Inserted Card: PXM1_OC3 Reserved Card: PXM1_OC3 State: Active Serial Number: SBK033300FP Prim SW Rev: 1.0(13) Sec SW Rev: 1.0(13) Cur SW Rev: 1.0(13) Boot FW Rev: 65.1(50.163) 800-level Rev: A0 Orderable Part#: 800-05610-02 CLEI Code: BAA4HCZAAA Reset Reason: On Reset From Shell Card Alarm: NONE Failed Reason: None Miscellaneous Information: Aug. 28, 2001 16:27:58 PDT Node Alarm: MAJOR Upper Card ---------- Lower Card ---------- UIA BackCard UIA BackCard Active SBK0329018V --------A0 800-03688-01 BAI9Y00AAA MMF_4_OC3 MMF_4_OC3 Active SAK032500IE --------A0 800-05053-01 BA2IKNJBAA Type <CR> to continue, Q<CR> to stop: The primary (Prim SW Rev), secondary (Sec SW Rev), and current (Cur SW Rev) software revision labels indicate the status of an upgrade. In this example, these numbers match because the runtime software upgrade has not started. (Note that the boot software has been upgraded as indicated by the Boot FW Rev label.) The primary software revision indicates which revision a card will run if it becomes active, and the secondary revision indicates an alternate revision that the card will use if the abortrev command is entered. The current software revision represents the software the active card is using. The normal sequence of commands for a runtime software upgrade is loadrev, runrev, and commitrev. Table A-2 shows an example of how the software revision levels change during a graceful runtime software upgrade. Table A-2 Software Versions Reported During Graceful Upgrades Before Upgrade After loadrev After runrev After commitrev Software Revision Slot 1 Slot 2 Slot 1 Slot 2 Slot 1 Slot 2 Slot 1 Slot 2 Active Standby Active Standby Standby Active Active Standby Primary 1.0(13) 1.0(13) 1.0(13) 1.0(13) 1.1(0) 1.1(0) 1.1(0) 1.1(0) Secondary 1.0(13) 1.0(13) 1.1(0) 1.1(0) 1.0(13) 1.0(13) 1.1(0) 1.1(0) Current 1.0(13) 1.0(13) 1.0(13) 1.1(0) 1.1(0) 1.1(0) 1.1(0) 1.1(0) Cisco SES PNNI Controller Software Configuration Guide A-12 Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 Appendix A Downloading and Installing Software Upgrades Upgrade Procedures for PXM Cards For non-graceful upgrades, the load process defines the software version to which the controller 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 1.0(13) 1.0(13) 1.1(0) 1.1(0) Secondary 1.0(13) 1.1(0) 1.0(13) 1.1(0) Current 1.0(13) 1.0(13) 1.1(0) 1.1(0) If you are performing a graceful upgrade, use the quickstart procedure described in “Graceful PXM Runtime Software Upgrades,” which appears earlier in this appendix. The following procedure provides detailed information on the load task within the quickstart procedure. Step 1 To load the upgrade runtime software version on a PXM card, enter the following command: mgx8850a.7.PXM.a > loadrev <slot> <revision> Replace <slot> with the card slot number for the card to be upgraded, and replace <revision> with the software version number for the update. For graceful upgrades, you can specify either the active or the standby card. The controller software will automatically load the upgrade software on the standby card when it is installed. The following example shows how to enter this command: mgx8850a.7.PXM.a > loadrev 1 1.1(0) After you enter the loadrev command, the standby card comes up in the standby-U state. You can find the software version number in the Release Notes for Cisco WAN SES Controller Software Release 1.1. Step 2 When prompted to confirm the command, type y and press Return to continue. Step 3 To verify that the load command was processed correctly, enter the dspcd <slot> command and check the status of the software revision levels. You can also view the revision levels with the dsprevs command. Note In a standalone configuration, the controller does not start the upgraded software until the runrev command is entered. In a redundant configuration, the controller starts the upgraded software on the standby card. The standby card does not become active until the runrev command is entered. Cisco SES PNNI Controller Software Configuration Guide Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 A-13 Appendix A Downloading and Installing Software Upgrades Upgrade Procedures for PXM Cards Starting the Upgrade Software After you load the runtime upgrade software for a PXM 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. Step 1 To start using the new runtime software version on a PXM card, enter the following command: mgx8850a.7.PXM.a > runrev <slot> <revision> Replace <slot> with the card slot number, and replace <revision> with the software version number specified with the loadrev command. For graceful upgrades, you can specify either the active or the standby card. The controller software will automatically run the upgrade software on the standby card when it is installed. The following example shows how to enter this command: mgx8850a.7.PXM.a > runrev 1 1.1(0) The active card is reset, and the former standby card comes up in the active-U state. Step 2 When prompted to confirm the command, type y and press Return to continue. Step 3 To verify that the load command was processed correctly, enter the dspcd <slot> command and check the status of the software revision levels. You can also view the revision levels with the dsprevs command. Step 4 When the former active PXM come sup in the standby-U state, enter the commitrev command to commit to that software version. This step is optional. After the runrev command is entered, the controller starts running the new software revision. The secondary software revision shows that a previous revision is still available. Whenever the secondary software revision is different from the primary and current software revisions, you can revert back to the secondary software revision. Committing to a Runtime Software Upgrade Committing to an upgrade does the following: • Disables use of the abortrev command to revert back to the previously used version of software • Enables upgrading of the current version of software Once you are sure that an upgrade is stable, you can use the commitrev command commit to that software version. This prevents other administrators from inadvertently reverting to the previous version. You must also commit to the current software version before you can upgrade to another software version. Cisco SES PNNI Controller Software Configuration Guide A-14 Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 Appendix A Downloading and Installing Software Upgrades Troubleshooting Upgrade Problems To commit to the currently running 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 Determine if there is an unfinished upgrade by doing the following: a. If necessary, use the cc command to select the active PXM card. b. Enter the dspcd <slot> command. c. Check the dspcd command report to see if the same software revision is listed for the Primary Software Revision (Prim SW Rev), Secondary Software Revision (Sec SW Rev), and Current Software Revision (Curr SW Rev). If all version numbers are identical, the runtime software can be upgraded. There is no need to commit to the current software revision. Step 3 To commit to the software version, enter the following command: mgx8850a.7.PXM.a > commitrev <slot> <revision> Replace <slot> with the card slot number for the active PXM card, and replace <revision> with the software version number for the currently used software version. To display the software version number, use the dspcd <slot> command to view the software version in use. You can also view the revision levels with the dsprevs command. Troubleshooting Upgrade Problems Table A-4 lists symptoms of upgrade problems and suggestion on how to correct them. Tips When troubleshooting problems on standby PXM cards or cards that do not start up to the active state, establish communications through the boot IP address or through the console port. Cisco SES PNNI Controller Software Configuration Guide Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 A-15 Appendix A Downloading and Installing Software Upgrades Troubleshooting Upgrade Problems Table A-4 Troubleshooting Upgrade Problems Primary Symptom Secondary Symptom loadrev or runrev command fails Suggested Action The loadrev command is blocked when a previous upgrade has not been completed with the commitrev command. Use the dsprevs command to locate the cards that are still being upgraded. For more information on a particular card, enter the dspcd <slot> command and verify that the Current, Primary, and Secondary software revision numbers are identical. If the numbers are not identical, issue the commitrev <slot> command. Enter the dspcds and verify that the standby card is in standby state. Also look for a -U or -D in the dspcds command display, which indicates that the card is in the process of being upgraded (-U) or downgraded (-D). The loadrev and runrev commands are blocked whenever the standby card is not in standby state or an upgrade or downgrade is in progress. After restart, the controller stops displaying messages and does not display a prompt. Press Return to display the prompt. After restart, the controller The controller displays the stops at backup boot prompt: message: Can not open file C:/version. pxmbkup>. The version file is probably missing. Create the version file as described in “Initializing the Controller” in Chapter 2, “Configuring General Switch Features.” The controller displays the message: Unable to determine size of C:/FW/filename. The version recorded in the version file doesn’t match software installed in the C:FW directory. (Use a console port connection to see this. If you missed the startup messages, enter the reboot command.) Enter the sysVersionShow command to see which file the PXM is trying to load. Verify that the correct software is installed on the controller. If the runtime software is not on the hard disk, copy it to the hard disk. If a typo is entered when initializing the controller, re-enter the sysVersionSet command, enter the sysVersionShow command to verify the correct setting, and then reboot the controller with the reboot command. The controller displays the message: Please run sysDiskCfgCreate. The hard disk is formatted, but not ready for operation. Enter the sysDiskCfgCreate command. Cisco SES PNNI Controller Software Configuration Guide A-16 Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 Appendix A Downloading and Installing Software Upgrades Troubleshooting Upgrade Problems Table A-4 Troubleshooting Upgrade Problems (continued) Primary Symptom Secondary Symptom Standby PXM continually reboots. You can view the rebooting process through the console port. Suggested Action The active PXM card cannot bring up the standby card. The following procedure assumes that this card has just been installed in the controller and that you have given the standby card sufficient time to synchronize with the Active card. Interrupt the boot cycle by pressing Return. Timing is important, so you might have to press Return multiple times. When the pxmbkup prompt appears, immediately enter the sysPxmRemove command to prevent the Active card from rebooting the standby card while you are working on it. Enter the sysChangeEnet command and verify that the inet on ethernet (e) and gateway inet (g) values are set to the boot and gateway IP address set with the bootChange command on the active card. Also, verify that the boot device is set to lnPci. The sysChangeEnet command works like the bootChange command, which is described in “Setting the Boot IP Address” in Chapter 2, “Configuring General Switch Features.” Enter the sysClrallcnf command to clear any configuration data on the standby card set. This command does not clear the boot IP address set with the sysChangeEnet command. After restart, the controller stops at backup shell prompt: pxm>. If the Return key is pressed at one of the auto-boot prompts during start up, the controller stops in shell mode. Enter the reboot command to restart the controller and avoid pressing the Return key. Cisco SES PNNI Controller Software Configuration Guide Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 A-17 Appendix A Downloading and Installing Software Upgrades Troubleshooting Upgrade Problems Cisco SES PNNI Controller Software Configuration Guide A-18 Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 A P P E N D I X B Technical Specifications This appendix lists the relevant technical and compliance specifications for the SES PNNI controller, 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.1 Physical specifications for the Service Expansion Shelf are listed in the Cisco Service Expansion Shelf Hardware Installation Guide, Release 1.1. PNNI Compliance The SES PNNI controller PNNI routing software was designed to be compliant with 1 below. The software supports robust topology convergence, dynamic and QoS based routing in hierarchical ATM networks with scalability from small to very large networks. Other specifications to which the PNNI routing conforms are as follows: 1. ATM Forum, “PNNI Specification Version 1.0,” af-pnni-0055.000, March 1996 2. ATM Forum, “PNNI V1.0 Errata and PICS,” af-pnni-0081.000, March 1997. 3. ATM Forum, “Interim Inter-switch Signaling Protocol (IISP) Specification Version 1.0,” af-pnni-0026.000, December 1994. 4. AINI 5. PNNI v2.0 draft 6. Path and Connection Trace Cisco SES PNNI Controller Software Configuration Guide Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 B-1 Appendix B Technical Specifications 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. Capability Reference Network Equipment Mandatory/Optional Support Point-to-Point calls 5.5 M x Address Registration 5.8 — x Sub-addressing 5.4.5.12, 14 — x B-LLI Negotiation Annex C M x AAL Parameter Negotiation Annex F M x UNI 4.0 Signaling UNI 4.0 Signaling is supported. IISP Signaling IISP 1.0 Signaling is supported, including transport of SPVC IEs over an IISP trunk. PNNI Signaling PNNI Signaling is supported, 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 Cisco SES PNNI Controller Software Configuration Guide B-2 Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 Appendix B Technical Specifications ATM Signaling Compliance Capability Reference Network Equipment Mandatory//Optional Support 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. Annex C O x SPVC Any VCCI value 9.2.3.1 O Generic Identifier Transport 6.4.5.31 O x Frame Discard — O x In addition to the above, the following PNNI 2.0 capabilities are supported on an interface Capability Reference Network Equipment Mandatory//Optional Support Connection Tracing 6.7 — x Path Tracing 6.7 — x ATM Signaling Interworking Interworking between all combinations of signaling protocol is supported at all interfaces types: UNI to UNI, UNI to NNI and NNI to NNI. Protocol UNI 3.0 UNI 3.1 UNI 4.0 IISP 1.0 PNNI 1.0 AINI 3.0 AINI 3.1 UNI 3.0/3.1 x x x x x x x UNI 4.0 x x x x x x x IISP 1.0 x x x x x x x PNNI 1.0 x x x x x x x AINI 3.0 x x x x x x x AINI 3.1 x x x x x x x Interoperability Support The SES PNNI controller is interoperable with all standards-compliant networking equipment. The SES PNNI controller is also backward compatible with earlier SES software releases, as well as the MGX 8850. Cisco SES PNNI Controller Software Configuration Guide Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 B-3 Appendix B Technical Specifications Processor Switching Module Specifications Processor Switching Module Specifications Table B-1 contains general specifications for the Processor Switching Module (PXM) on the Service Expansion Shelf. The table includes information for the two types of back cards—the control access card and uplink card (with ports serving either as trunks or user-ports) Table B-1 PXM Specifications Category Control access: Description • Control port: RJ45 connector, EIA/TIA 232, DTE mode, asynchronous interface 19,200 baud, 1 start bit, 1 stop bit, no parity bits. • Maintenance port: RJ45 connector, EIA/TIA 232, DTE mode, asynchronous interface 9600 baud, 1 start bit, 1 stop bit, no parity bits. • LAN port: RJ45 connector, 10-baseT, 802.3 Ethernet. Uplink ports and connectors: • 2 T3 ports, BNC connectors. An uplink card can have one of these number and type of connectors. The wavelength on optical lines is 1310 nm. • 2 E3, BNC connectors. • 4 OC3 multi-mode fiber, SC connectors. • 4 OC3 single-mode fiber, intermediate reach, SC connectors. • 4 OC3 single-mode fiber, long reach, SC connectors. These ports exits on the PXM-UI back card. Number of logical ports: 32 across all physical ports on the uplink card. LEDs on PXM front card: Status for the card: LEDs display status, but alarm history is a switch. • Green means active. • Red means failed. • Yellow indicates the standby card. LAN activity: flashing green indicates activity. Node alarm: • Red indicates major alarm. • Yellow indicates minor alarm. Node power (note that each AC power supply also has an LED): • “DC OK A” is green for okay or red for trouble. • “DC OK B” is green for okay or red for trouble. Alarm history: ACO Port interface (per port): LEDs on back cards: • Green means active and okay. • Red means active and local alarm. • Yellow means active and remote alarm. • No light means inactive or not provided. Green means active. No light means inactive or not provided. Cisco SES PNNI Controller Software Configuration Guide B-4 Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 Appendix B Technical Specifications Processor Switching Module Specifications Table B-1 PXM Specifications (continued) Category Description Synchronization: 8 KHz clock derived from the following sources: These clock sources satisfy Stratum.4 requirements. BITS clock interface: Trunk history counters: Connection capacities supported by PXM: Processor clock speed and memory specifics: Alarm indicators (audible and visual): Maintenance features: Card dimensions: Power: • Internal 8 KHz clock (10 ppm). • Service modules or trunk line interfaces. • External BITS clock port. • T1 clock rate 1.544 MHz +/- 50 bps. • E1 clock rate 2.048 MHz +/- 100 bps (can be either sync or data signal). • T1 with an RJ45 connector. • E1 with an SMB connector. • Ingress, per connection: Number of received cells with CLP=0. Number of received cells with CLP=1. • Egress, per connection: Number of received cells. Number of transmitted cells. Number of received cells with EFCI bit set. Number of transmitted cells with EFCI bit set. • Maximum number of connections: 16,000 bi-directional channels for local switching. 32,000 bi-directional channels for switching across uplink card. • Maximum aggregate bandwidth: 600 Mbps local switching (service module to service module). 1,200 Mbps switching across uplink. • Cell memory: 256K cells. • Clock speed: 200 MHz internal, 50 MHz external. • Flash memory: 2 MB. • DRAM: 64 MB, upgradeable to 128 Mbytes. • Secondary cache: 512 KB. • BRAM: 128 KB. • Hard disk: 2.1 GB. Central office-compatible alarm indicators and controls through a DB15 connector. • Internal isolation loopback. • External remote loopback. • Hot-pluggable. • Front card: 15.65 inches by 16.83 inches. • Back card: 7.25 inches by 4.125 inches. Requires –48 VDC, dissipates 150W. Cisco SES PNNI Controller Software Configuration Guide Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 B-5 Appendix B Technical Specifications Processor Switching Module Specifications Cisco SES PNNI Controller Software Configuration Guide B-6 Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 A P P E N D I X C Virtual Switch Interface This appendix provides a description of the Virtual Switch Interface (VSI) protocol as it is used to control a BPX node for PNNI routing or Multiprotocol Label Switching (MPLS) in switched software Release 9.2. The appendix contains the following sections: • Virtual Switch Interface Protocol • Class of Service Templates • Supported Service Types Virtual Switch Interface Protocol The Virtual Switch Interface (VSI) protocol is used to control a Cisco Wide Area Network switch, such as the BPX 8620, for networking applications, such as Multiprotocol Label Switching (MPLS: sometimes referred to as Tag switching) or PNNI routing. The VSI is a mechanism for networking applications to control the BPX 8600 and use a partition of the switch’s resources for its specific application. With VSI, external controllers are used to control the switch for applications not supported by the traditional WAN switch set of routing protocols known as AutoRoute. The VSI protocol allows a BPX switch to be controlled by multiple controllers, such as a PNNI controller (SES PNNI controller) or an MPLS controller (Tag or Label Switch Controller), along with the traditional AutoRoute controlling software. These additional controllers provide control planes that can be external or internal to the BPX switch. VSI Master and Slaves The VSI protocol is a master/slave protocol. The master part of the VSI protocol runs on the SES PNNI controller for PNNI networking, and is referred to in this application as the PNNI controller. (For MPLS, the controller is an external Tag Switch controller.) The slave part of the VSI protocol runs on the BXMs on the BPX 8620. Figure C-1 provides a simple illustration of the VSI master and slave relationship. Cisco SES PNNI Controller Software Configuration Guide Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 C-1 Appendix C Virtual Switch Interface Virtual Switch Interface Protocol Figure C-1 VSI Controller and Slave VSIs PNNI application (VSI controller) SES PNNI controller VSI master Auto route VSI slaves BPX 40857 Resource management When enabled and configured, the VSI controller automatically establishes a link between the VSI master and every VSI slave on the associated switch, as shown in Figure C-2. When enabled, the VSI slaves in turn establish links between each other. Figure C-2 VSI Master and VSI Slave Example BPX SES PNNI controller Slave PNNI application VSI master 40861 Slave Slave The BXM has 32 virtual interfaces that provide a number of resources including Qbin buffering capability. With physical lines and trunks, one virtual interface is assigned to each port (Figure C-3). With virtual trunking, a physical trunk can comprise a number of logical trunks called virtual trunks, and each of these virtual trunks is assigned the resources of one of the 32 virtual interfaces on a BXM (Figure C-3). Each virtual interface has 16 Qbins assigned to it. Qbins 0-9 are used for AutoRoute and 10–15 are available for use by a VSI enabled on the virtual interface. (In Release 9.1, only Qbin 10 was used.) The Qbins 10–15 support class of service (CoS) templates on the BPX. A virtual switch interface may be enabled on a port, trunk, or virtual trunk. The virtual switch interface is assigned the resources of the associated virtual interface. Cisco SES PNNI Controller Software Configuration Guide C-2 Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 Appendix C Virtual Switch Interface Virtual Switch Interface Protocol Figure C-3 BXM Virtual Interfaces and Qbins BXM Virtual trunk 4.1.1 qbins 1 Port 1 Virtual trunk 4.1.2 VSI controller VI_1 16 qbins Port 2 Trunk 4.2 1 Tag (MPLB) PNNI, or other VI_2 16 Port 3 qbins 1 VI_3 16 Port 4 qbins 1 VI_32 56141 16 Resource Partitioning With the VSI protocol, the resources on a BXM port or trunk must be partitioned between competing controllers, AutoRoute, MPLS, and PNNI. Once the resources are partitioned, the controller can use them for its networking application. In other words, AutoRoute uses the resources in its partition to provision permanent virtual circuits, just like a standard BPX switch. And the PNNI controller, will use the resources in its partition to establish ATM switched virtual circuits. The two partitions are completely independent and the connections from one never interfere with the connections in another partition. Note Resources can only be partitioned on a BXM card in Release 9.2. The resources that need to be configured for a partition are shown in Table C-1 for a partition designated ifci (interface controller 1). The three parameters that need to be distributed are number of logical connections (LCNs), bandwidth (BW), and virtual path identifiers (VPIs). Table C-1 ifci Parameters (Virtual Switch Interface) ifci parameters Min Max lcns min_lcns max_lcns bw min_bw max_bw vpi min_vpi max_vpi Cisco SES PNNI Controller Software Configuration Guide Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 C-3 Appendix C Virtual Switch Interface Virtual Switch Interface Protocol Partition Criteria shows the VPI ranges available for partitions on a BXM card. Table C-2 Partition Criteria Partition Range NNI trunk/port 1-4095 VPI range UNI trunk/port 1-255 VPI range Virtual trunk • Only one VPI available per virtual trunk since a virtual trunk is currently delineated by a specific VP. • Each virtual trunk can either be AutoRoute or VSI, not both. When a trunk is added, the entire bandwidth is allocated to AutoRoute. To change the allocation in order to provide resources for a VSI partition, the cnfrsrc BPX CLI command is used on the BXM. Configuring VSI-ILMI This section describes how to perform the following tasks for ILMI functionality: • Support Enabling ILMI Functionality for VSI Partitions on Port Interfaces • Enable ILMI Functionality for VSI Partitions on Physical Trunk Interfaces • Enable VSI ILMI Functionality on Virtual Trunk Interfaces Support Enabling ILMI Functionality for VSI Partitions on Port Interfaces The ILMI protocol can either run on the BPX or on the BXM card. For ILMI functionality to work for VSI partitions, the ILMI protocol should run on the BXM card. To enable ILMI functionality for VSI partitions on port interfaces, perform the following steps: Step 1 Step 2 Enable ILMI session for the port using the cnfport command. a. When prompted for protocol type, specify the ILMI protocol by typing an i. b. When prompted by “Protocol by the Card?” type y. Enable VSI ILMI functionality using the cnfvsipart command. In the following example, the user configures the active VSI partition 1 on the port interface 13.1: cnfvsipart 13.1 1 y Cisco SES PNNI Controller Software Configuration Guide C-4 Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 Appendix C Virtual Switch Interface Virtual Switch Interface Protocol Enable ILMI Functionality for VSI Partitions on Physical Trunk Interfaces This section describes how to enable ILMI functionality for an active VSI partition, using the example of active VSI partition 1 on a physical trunk interface 13.2. Step 1 Enable ILMI protocol to run on the BXM card by entering the cnftrk command. Step 2 When prompted by “Protocol by the card?” type y. Note Unlike the cnfport command, the cnftrk command does not provide an option to configure the ILMI protocol on the trunk. The cnfvsipart command automatically configures on the trunk. Enable VSI ILMI Functionality on Virtual Trunk Interfaces This section describes how to enable ILMI functionality for an active VSI partition on a specified virtual trunk interface, using the example of active VSI partition 1 on a virtual trunk interface 13.3.1. ILMI sessions on Virtual trunks always run on the BXM card. Hence it is not necessary that you run the cnftrk command when enabling ILMI functionality for a VSI partition on a virtual trunk interface. Step 1 Enable ILMI functionality for the VSI partition on the virtual trunk interface using the cnfvsipart command. cnfvsipart 13.3.1 1 y Note ILMI functionality cannot be enabled on Feeder Trunk Interfaces. By default LMI protocol runs on these interfaces. Step 2 Note Check to ensure that ILMI functionality is enabled for a VSI partition on an interface Currently all ILMI sessions exchange only the BPX NW IP address with peer ILMI sessions. The Sys_Id is generated using the NOVRAM contents in the backplane of the BPX shelf. If for some reason, this NOVRAM could not be read, then a default Sys_Id of 1 is downloaded to the BXM card. If this is done, the dspvsipartcnf command will display this information as follows: Sys_Id generation failed!! Using default value = 0.0.0.0.0.1 cnfvsipart Enter the cnfvsipart command to configure VSI partition characteristics. The cnfvsipart command is currently the only way to enable VSI ILMI sessions. Cisco SES PNNI Controller Software Configuration Guide Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 C-5 Appendix C Virtual Switch Interface Class of Service Templates Syntax Description Related Commands cnfvsipart <slot.port.[vtrk]> <part_id> <enable_option> slot.port.[vtrk] Slot, port of the interface. If applicable, enter the virtual port number. part_id Partition identifier associated with the VSI partition. enable_option Activate (y) or deactivate (n) the VWI ILMI session, cnfrsrc, dspvsipartcnf, cnfport, cnftrk dspvsipartcnf Use the dspvsipartcnf command to view VSI partition characteristics. Currently this command only displays information about VSI ILMI sessions. This command displays whether VSI ILMI is enabled for a given partition, the LCN used for the sessions (only for trunk interfaces) and the type of IP address downloaded to the BXM card for topology discovery purposes. On Trunk Interfaces, ILMI functionality can be enabled on one VSI partition only. Use the dspvsipartcnf command to view ILMI functionality for VSI partitions on trunk interface 13.2, dspvsipartcnf 12.1 If, for example, a VSI ILMI session is enabled on partition 1, it would provide output similar to the following example: Trunk: Trunk: Trunk: Sys_Id 13.2 13.2 13.2 generated Partn: 1 ILMI: E LCN: 272 Partn: 2 -- VSI partition DISABLED Partn: 3 -- VSI partition DISABLED = 32.31.39.36.30.35 Topo: BPX NW IP The above output says that ILMI functionality is enabled on VSI partition 1 on trunk interface 13.2 and it uses LCN 272 and the BPX Network IP is exchanged by the ILMI session with the peer ILMI session. If no partition is specified, this command displays the above information about all the VSI partitions and also the Sys_Id downloaded to the BXM card for ILMI functionality. Syntax Description dspvsipartcnf <slot.port.[vtrk]> [partition_id] slot.port.[vtrk] Slot, port (and virtual port if applicable) of the interface. part_id Partition ID corresponding to the VSI partition. This parameter is optional and if not specified, this command will display information about all the VSI partitions. Class of Service Templates Class of Service (CoS) Templates provide a means of mapping a set of standard connection protocol parameters to extended platform specific parameters. Full QoS implies that each VC is served through one of a number of Class of Service buffers (Qbins) which are differentiated by their QoS characteristics. Note The terms Class of Service Template and CoS Template can be used interchangeably. Cisco SES PNNI Controller Software Configuration Guide C-6 Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 Appendix C Virtual Switch Interface Class of Service Templates When a connection set up request is received from the VSI Master in the PNNI or MPLS controller, the VSI slave (in the BXM) uses the class of service index of the request to retrieve the corresponding set of extended parameters defined in the template for the corresponding index. The BXM VSI slave uses these values to complete the connection setup and program the cross-connect in the card. Functional Description The service class template provides a means of mapping a set of extended parameters, which are generally platform specific, based on the set of standard ATM parameters passed to the VSI slave during connection setup. A set of service templates is stored in each switch (for example, BPX) and downloaded to the service modules (for example, BXMs) as needed. The service templates contain two classes of data. • One class consists of parameters necessary to establish a connection (for example, per VC) and includes entries such as UPC actions, various bandwidth related items, per VC thresholds. • The second class of data items includes those necessary to configure the associated class of service buffers (Qbins) that provide QoS support. The general types of parameters passed from a VSI master to a slave include: • Service type identifier • QoS parameters (CLR, CTD, CDV) • Bandwidth parameters (for example PCR, MCR) • Other ATM Forum Traffic Management 4.0 parameters Each VC added by a VSI master is assigned to a specific service class by means of a 32-bit service type identifier. Current identifiers are for • ATM Forum service types (used for ATM SVCs) • AutoRoute • MPLS When a connection setup request is received from a VSI master controller, the VSI slave uses the service type identifier to index into a Service Class Template database containing extended parameter settings for connections matching that index. The firmware then programs the hardware with the applicable extended parameter values to complete the connection setup. One of the parameters specified for each service type is the particular BXM class of service buffer (Qbin) to use. The Qbin buffers provide separation of service type to match the QoS requirements. Service class templates on the BPX are maintained by the BCC and are downloaded to the BXM cards as part of the card configuration process as a result of card activation, rebuild, or switchover. In Release 9.2 the templates are non-configurable. Nine template types are available (as of 9.2.3x). You can assign any one of the templates to a virtual switch interface (Figure C-4). For more information about these templates, refer to the BPX documentation associated with Release 9.2.30. Cisco SES PNNI Controller Software Configuration Guide Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 C-7 Appendix C Virtual Switch Interface Class of Service Templates Figure C-4 Service Class Template Overview Qbin SC database 1 Qbin SC database 2 SC Database 3 SC Database 15 Qbin SC Databases per Qbin Databases per VC SC = Service Class. Each pre-configured template is one of the above for each of 4 Service Class Templates (VC Database + Qbin (10-15) Pre-configured Service Class Templates on BCC(1- 4) Template values on BXM initialized via ComBus messages at card bring up CoS Buffer Descriptor Templates Master SCT copies on BXM 56142 VC Descriptor Templates Service Class Template Structure Each template table row includes an entry that defines the Qbin to be used for that class of service (Figure C-5). This mapping defines a relationship between the template and the interface Qbin’s configuration. Cisco SES PNNI Controller Software Configuration Guide C-8 Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 Appendix C Virtual Switch Interface Class of Service Templates Figure C-5 Service Class Template and Associated Qbin Selection Templates Expanded Service Service Class Type ID Category Associtaed Qbin Parameters VSI Special Type (Note 1) Template 1 Tag 1 Template 1 PNNI_1 Template 1 PNNI_2 Template 1 Tag 2 0x000 0x001 0x002 10 15 Null Default Signaling ATM Forum Type (Note 2) upc_e/d, etc. 0x0100 0x0101 0x0102 0x0103 0x0104 0x0105 0x0106 0x0107 0x0108 0x0109 0x010A 0x010B cbr.1 vbr.1rt vbr.2rt vbr.3rt vbr.1nrt vbr.2nrt vbr.3nrt ubr.1 ubr.2 abr cbr.2 cbr.3 “ “ “ “ “ “ “ “ “ “ “ “ “ “ “ “ “ “ “ “ “ “ “ “ 10 11 11 11 12 12 12 13 13 14 10 10 Tag Switching Type per class service cos0 cos1 cos2 cos3 cos0 cos1 cos0 cos1 ABR “ “ “ “ “ “ “ “ “ “ “ “ “ “ “ “ “ “ Qbin Note 1: Used as applicable for TAG or PNNI. Note 2: Used by PNNI_1 or PNNI_2. Note 3. Template numbers 1,2, and so on, are just a general classification. The service class category (for example, 0x0202 associated with a VC) determines the row selected in the service class data file. The Qbin parameters associated with that row are applied to the VC. Where a parameter is optional or has not been specified for the VC, the default values from the template are applied. 0 .. 9 10 11 12 13 14 15 (Tag with ABR Control) max Qbin threshold Qbins 0-9 for AutoRoute Qbin clphi Qbin clplo 10 11 12 13 10 11 12 13 14 efci discard wqf thresh epd 56143 0x0200 0x0201 0x0202 0x0203 0x0204 0x0205 0x0206 0x0207 0x0210 Cisco SES PNNI Controller Software Configuration Guide Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 C-9 Appendix C Virtual Switch Interface Class of Service Templates A Qbin template defines a default configuration for the set of Qbins for the logical interface. When a template assignment is made to an interface, the corresponding default Qbin configuration becomes the interface’s Qbin configuration. Some of the parameters of the interface’s Qbin configuration can be changed on a per interface basis. Such changes affect only that interface’s Qbin configuration and no others, and do not affect the Qbin templates. Qbin templates are used only with Qbins that are available to VSI partitions (PNNI or MPLS), namely Qbins 10 through 15. Qbins 10 through 15 are used by the VSI on interfaces configured as trunks or ports. The rest of the Qbins (0-9) are reserved for and configured by AutoRoute. Downloading Service Class Templates Service Class Templates are downloaded to a BXM card under the following conditions: • when adding a y-redundant card • during a BCC (control card) switchover • when a card that has active interfaces is reset (hardware reset) • during a BCC (control card) rebuild Assignment of a Service Class Template to an interface A default Service Class Template is assigned to a logical interface (VI) when the interface is upped via upport/uptrk. For example, • uptrk 1.1 • uptrk 1.1.1 (virtual trunk) • upport 1.1 This default template has the identifier of 1. Users can change the Service Class Template from Service Class Template 1 to another Service Class Template using the cnfvsiif (configure VSI interface) command. The dspvsiif command allows the user to display the template associated with the interface. For example, • cnfvsiif 1.1 2 • cnfvsiif 1.1.1 2 • dspvsiif 1.1 • dspvsiif 1.1.1 cnfvsiif example The cnfvsiif command is used to assign a selected Service Class Template to an interface (VI) by specifying the template number. It has the following syntax: cnfvsiif <slot.port.vtrk> <tmplt_id> dspvsiif example The dspvsiif command is used to display the type of Service Class Template assigned to an interface (VI). It has the following syntax: dspvsiif <slot.port.vtrk> Cisco SES PNNI Controller Software Configuration Guide C-10 Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 Appendix C Virtual Switch Interface Class of Service Templates Card Qbin Configuration When an interface (VI) is activated by uptrk or upport, the default Service Class Template is assigned to the interface (VI). The corresponding Qbin template is then copied into the card’s (BXM) data structure of that interface. A user can change some of the Qbin parameters using the cnfqbin command. The Qbin is now “user configured” as opposed to “template configured.” This information may be viewed on the dspqbin screen. Qbin Dependencies The available Qbin parameters are shown in Table C-3. Notice that the Qbins available for VSI are restricted to Qbins 10–15 for that interface. All 32 possible virtual interfaces are provided with 16 Qbins. Table C-3 Service Class Template Qbin Parameters Template Object Name Template Units Template Range/Values QBIN Number enumeration 0–15 (10-15 valid for VSI) Max QBIN Threshold u sec 1–2000000 QBIN CLP High Threshold % of max Qbin threshold 0–100 QBIN CLP Low Threshold % of max Qbin threshold 0–100 EFCI Threshold % of max Qbin threshold 0–100 Discard Selection enumeration 1–CLP Hystersis 2–Frame Discard Weighted Fair Queueing enable/disable 0–Disable 1–Enable Additional Service Class Template commands are: dspsctmplt Display the template number assigned to an interface. The command has three levels of operation • dspsctmplt View current Service Class Templates on the node. • dspsctmplt <tmplt_id> View all Service Classes in the template • dspsctmplt <tmplt_id> Lists all the parameters of that Service Class. dspqbintmlt View the Qbin templates cnfqbin Set parameters on the Qbin. Answer yes, when prompted, to use the card qbin values from the Qbin templates. dspqbin View Qbin parameters currently configured for the virtual interface. dspcd View the current card configuration. Cisco SES PNNI Controller Software Configuration Guide Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 C-11 Appendix C Virtual Switch Interface Class of Service Templates Extended Services Types Support The service-type parameter for a connection is specified in the connection bandwidth information parameter group. The service-type and service-category parameters determine the service class to be used from the Service Class Template. Connection Admission Control For Release 9.2, when the VSI Slave receives a connection request, it is first subjected to a Connection Admission Control (CAC) process before being forwarded to the FW layer responsible for actually programming the connection. The granting of the connection is based on the following criteria: • LCNs available in the VSI partition • Qbin • Service Class QoS guarantees • max CLR • max CTD • max CDV When the VSI slave accepts (for example, after CAC) a connection setup command from the VSI master in the PNNI or MPLS Controller, it receives information about the connection including service type, bandwidth parameters, and QoS parameters. This information is used to determine an index into the VI’s selected Service Class Template’s VC Descriptor table thereby establishing access to the associated extended parameter set stored in the table. Supported Service Types The service type identifier is a 32-bit number. Table C-4 lists the supported service types. Cisco SES PNNI Controller Software Configuration Guide C-12 Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 Appendix C Virtual Switch Interface Class of Service Templates Table C-4 Service Category Listing Service Category Service Type Identifiers Service Types Associated Qbin VSI Special Types 0x0000 Null — 0x0001 Default 10 0x0002 Signaling 15 0x0100 CBR.1 10 0x0101 VBR.1-RT 11 0x0102 VBR.2-RT 11 0x0103 VBR.3-RT 11 0x0104 VBR.1-nRT 12 0x0105 VBR.2-nRT 12 0x0106 VBR.3-nRT 12 0x0107 UBR.1 13 0x0108 UBR.2 13 0x0109 ABR 14 0x010A CBR.2 10 0x010B CBR.3 10 0x0200 Tag 0, COS 1 0, per-class service 10 ATMF Types MPLS Types 0x0201 0x0202 0x0203 Tag 1, COS1 1, per-class service 0x0204 Tag 2, COS1 2, per-class service 0x0205 1 0x0206 0x0207 0x0210 Tag 3, COS 3, per-class service 1 Tag 4, COS 0, per-class service, shadow 11 12 13 10 11 12 13 14 Tag 5, Class of Service COS1 1, per-class service Tag 6, Class of Service COS1 2, per-class service Tag 7, Class of Service COS1 3, per-class service, shadow Tag ABR, (Tag with ABR flow control) 1 COS = Class of Service Cisco SES PNNI Controller Software Configuration Guide Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 C-13 Appendix C Virtual Switch Interface Class of Service Templates A summary of the parameters associated with each of the Service Class Templates is provided in Table C-5 through Table C-8. Table C-9 provides a description of these parameters and also the range of values that may be configured if the template does not assign an arbitrary value. Table C-5 lists the parameters associated with Default (0x0001) and Signaling (0x0002) Service Class Template categories. Table C-5 VSI Special Service Types Parameter VSI Default (0x0001) VSI Signaling (0x0002) QBIN Number 10 15 UPC Enable 0 *1 UPC CLP Selection 0 * Policing Action (GCRA #1) 0 * Policing Action (GCRA #2) 0 * PCR — 300 kbps MCR — 300 kbps SCR — — ICR — — MBS — — CoS Min BW% 0 * CoS Max BW % 0 * Scaling Class 3 3 CAC Treatment ID 1 1 VC Max Threshold Q_max/4 * VC CLPhi Threshold 75 * VC CLPlo Threshold 30 * VC EPD Threshold 90 * VC EFCI Threshold 60 * VC discard selection 0 * 1 = * indicates not applicable Cisco SES PNNI Controller Software Configuration Guide C-14 Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 Appendix C Virtual Switch Interface Class of Service Templates Table C-6 and Table C-7 lists the parameters associated with the PNNI Service Class Templates. Table C-6 ATM Forum Service Types, CBR, UBR, and ABR Parameter CBR.1 CBR.2 CBR.3 UBR.1 UBR.2 ABR QBIN Number 10 10 10 13 13 14 UPC Enable 1 1 1 1 1 1 UPC CLP Selection *1 * * * * * Policing Action (GCRA #1) * * * * * * Policing Action (GCRA #2) * * * * * * PCR — — — * * * MCR — — — * * * SCR — — — 50 50 * ICR — — — — — * MBS — — — — — * CoS Min BW% 0 0 0 0 0 0 CoS Max BW% 100 100 100 100 100 100 Scaling Class * * * * * * CAC Treatment ID * * * * * * VC Max Threshold * * * * * * VC CLPhi Threshold * * * * * * VC CLPlo Threshold * * * * * * VC EPD Threshold * * * * * * VC EFCI Threshold * * * * * * VC discard selection * * * * * * VSVD/FCES — — — — — * ADTF — — — — — 500 RDF — — — — — 16 RIF — — — — — 16 NRM — — — — — 32 TRM — — — — — 0 CDF — — — — — 16 TBE — — — — — 16777215 FRTT — — — — — * Cisco SES PNNI Controller Software Configuration Guide Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 C-15 Appendix C Virtual Switch Interface Class of Service Templates Table C-7 ATM Forum VBR Service Types Parameter VBRrt.1 VBRrt.2 VBRrt.3 VBRnrt.1 VBRnrt.2 VBRnrt.3 QBIN Number 11 11 11 12 12 12 UPC Enable 1 1 1 1 1 1 * * * * * 1 UPC CLP Selection * Policing Action (GCRA #1) * * * * * * Policing Action (GCRA #2) * * * * * * MCR * * * * * * SCR * * * * * * ICR — — — — — — MBS * * * * * * CoS Min BW% 0 0 0 0 0 0 CoS Max BW% 100 100 100 100 100 100 Scaling Class * * * * * * CAC Treatment ID * * * * * * VC Max Threshold * * * * * * VC CLPhi Threshold * * * * * * VC CLPlo Threshold * * * * * * VC EPD Threshold * * * * * * VC EFCI Threshold * * * * * * VC discard selection * * * * * * PCR 1 = * indicates not applicable Table C-8 lists the connection parameters and their default values for MPLS (Tag Switching) Service Class Templates. Table C-8 MPLS (Tag Switching) Service Types Parameter CoS 0/4 CoS 1/5 CoS 2/6 CoS 3/7 Tag-ABR Qbin # 10 11 12 13 14 UPC Enable 0 0 0 0 0 UPC CLP Selection 0 0 0 0 0 Policing Action (GCRA #1) 0 0 0 0 0 Policing Action (GCRA #2) 0 0 0 0 0 PCR — — — — cr/10 MCR — — — — 0 SCR — — — — P_max ICR — — — — 100 Cisco SES PNNI Controller Software Configuration Guide C-16 Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 Appendix C Virtual Switch Interface Class of Service Templates Table C-8 MPLS (Tag Switching) Service Types (continued) Parameter CoS 0/4 CoS 1/5 CoS 2/6 CoS 3/7 Tag-ABR MBS — — — — — CoS Min BW% 0 0 0 0 0 CoS Max BW% 0 0 0 0 100 Scaling Class 3 3 2 1 2 CAC Treatment 1 1 1 1 1 VC Max Q_max/4 Q_max/4 Q_max/4 Q_max/4 cr/200ms VC CLPhi 75 75 75 75 75 VC CLPlo 30 30 30 30 30 VC EPD 90 90 90 90 90 VC EFCI 60 60 60 60 30 VC discard selection 0 0 0 0 0 VSVD/FCES — — — — 0 ADTF — — — — 500 RDF — — — — 16 RIF — — — — 16 NRM — — — — 32 TRM — — — — 0 CDF — — — — 16 TBE — — — — 16777215 FRTT — — — — 0 Table C-9 describes the connection parameters that are listed in the preceding tables and also lists the range of values that may be configured, if not pre-configured. Table C-9 Connection Parameter Descriptions and Ranges Object Name Range/Values Template Units QBIN Number 10 - 15 Qbin number Scaling Class 0-3 enumeration CDVT 0 - 5M (5 sec) secs MBS 1 - 5M cells ICR MCR - PCR cells MCR 50 - LR cells SCR MCR - LineRate cells UPC Enable 0–Disable GCRAs enumeration 1–Enabled GCRAs 2–Enable GCRA #1 3–Enable GCRA #2 Cisco SES PNNI Controller Software Configuration Guide Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 C-17 Appendix C Virtual Switch Interface Class of Service Templates Table C-9 Connection Parameter Descriptions and Ranges (continued) Object Name Range/Values Template Units UPC CLP Selection 0–Bk 1: CLP (0+1) enumeration Bk 2: CLP (0) 1–Bk 1: CLP (0+1) Bk 2: CLP (0+1) 2–Bk 1: CLP (0+1) Bk 2: Disabled Policing Action (GCRA #1) 0–Discard enumeration 1–Set CLP bit 2–Set CLP of untagged cells, disc. tagged cells Policing Action (GCRA #2) 0–Discard enumeration 1–Set CLP bit 2–Set CLP of untagged cells, disc. tagged cells VC Max cells CLP Lo 0–100 %Vc Max CLP Hi 0–100 %Vc Max EFCI 0–100 %Vc Max VC Discard Threshold Selection 0–CLP Hysteresis enumeration VSVD 0–None 1– EPD enumeration 1–VSVD 2: VSVD w / external Segment Reduced Format ADTF 0–7 enumeration Reduced Format Rate Decrease 1–15 Factor (RRDF) enumeration Reduced Format Rate Increase Factor (RRIF) 1–15 enumeration Reduced Format Time Between 0 - 7 Fwd RM cells (RTrm) enumeration Cut-Off Number of RM Cells (CRM) cells 1 - 4095 Cisco SES PNNI Controller Software Configuration Guide C-18 Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 A P P E N D I X D SNMP Management Information Base The SES controller SNMP implementation uses the MGX 8800 distributed Management Information Base. In this implementation, a master agent resides on a PXM card. A subagent also resides on the PXM to support the PNNI application. This appendix contains the following sections: • SNMP Fundamentals • MIBs Supported by the SES Controller SNMP Fundamentals A network management system contains several (potentially many) nodes, each with a processing entity—termed an agent—which has access to management instrumentation, at least one management station, and a management protocol that conveys management information between the agents and management stations. Network management stations execute management applications which monitor and control network elements. Network elements are devices such as hosts, routers, terminal servers, and so forth, which are monitored and controlled through access to their management information. Management information is viewed as a collection of managed objects. Collections of related objects are defined in Management Information Base (MIB) modules. These modules are written using a subset of OSI’s Abstract Syntax Notation One (ASN.1), termed the Structure of Management Information (SMI). The management protocol, SNMP, provides for the exchange of messages that convey management information between the agents and the management stations. MIB Tree Figure D-1 shows the MIB tree from its root, “iso,” to some of its lower branches. The branches of primary interest are “mgmt” and “private.” The mgmt branch contains standard MIBs and the private branch contains enterprise MIBs. Private enterprises obtain branch number assignments from the Internet Assigned Numbers Authority (IANA). Cisco developers obtain branch number assignments in the Cisco branch from the Cisco Assigned Numbers Authority (CANA). Cisco SES PNNI Controller Software Configuration Guide Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 D-1 Appendix D SNMP Management Information Base SNMP Fundamentals Figure D-1 MIB Tree ISO(1) internet( .3.6.1) directory(1) mgmt(2) experimental(3) private(4) mib-2(1) system(1) atmMIB(37) atmMIBObjects(1) ip(4) interfaces(2) enterprise(1) snmp(11) tcp(6) cisco(9) ATMForum(353) stratacom(351) AtmForumNetworkManagement(5) atmInterfaceConfTable(2) ciscoWANSvcMIB(140) atmfPnni(4) ciscoWan(150) ciscoWANSvcMIBObjects(1) pnnimib(1) ciscoWANAtmConnMIB(1) pnniMIBObjects(1) cwConnMibObjects(1) ciscoWANSvcInfo(1) pnniBaseGroup(1) pnniNodeTable(2) pnniNodeSvccTable(5) pnniNodePglTable(3) pnniScopeMappingTable(6) pnniNodeTimerTable(4) pnniLinkTable(9) cwspConfig(1) ciscoWANSvcPort(2) pnniSummaryAddressTable(20) cwspCacConfig(2) cwspLoad(13) cwspCallStats(5) cwspConnTrace(14) cwspSigStats(6) cwspAddress(11) cwspOperation(15) cwAtmChanCnfg(1) cwAtmChanConfigTable(1) cwAtmChanTest(3) cwAtmChanTestTable(1) cw AtmChanStateTable(1) 56144 cwAtmChanState(2) The following object identifiers (OID) all refer to the same place in the tree: iso.org.dod.internet.mgmt.mib-2.system 1.3.6.1.2.1.1 iso.org.dod.internet.2.1.1 An object is a leaf on such a tree. For example, sysDescr is an object in the System branch of MIB-II. The unique identification of an object comprises the list of branch points down to the object plus an instance identifier. The instance identifier for an ordinary, single instance (scalar) object is always zero, so the full OID for sysDescr is shown in the following example: iso.internet.mgmt.mib-2.system.sysDescr.0 The numeric OID for sysDescr is shown in the following example: 1.3.6.1.2.1.1.1.0 Cisco SES PNNI Controller Software Configuration Guide D-2 Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 Appendix D SNMP Management Information Base SNMP Fundamentals Note Some Table objects can have more than one instance. MIB Objects Overview A primary component of SNMP is the MIB, defining data for observation and control and asynchronous notifications (Trap in SNMPv1). The SNMP MIB is conceptually a tree structure with table, the leaves of MIB tree are individual items of data called objects. Object Identifier An object identifier uniquely designates any point in the tree, whether leaf object or branch point. An object identifier may be expressed as a series of integers or text strings. The numeric form is used in the protocol among machines. The text form, sometimes mixed with the numeric form is for use by people. Technically, the numeric form is the object name and the text form is the object descriptor. In practice, either is usually called an object identifier (OID). Object Definitions An object definition contains the following fields: SYNTAX, MAX-ACCESS, STATUS, DESCRIPTION, IndexPart, and DefValPart. OBJECT-TYPE MACRO ::= BEGIN TYPE NOTATION ::= “SYNTAX” Syntax UnitsPart “MAX-ACCESS” Access “STATUS” Status “DESCRIPTION” Text IndexPart DefValPart Syntax ::= data types -- please see data type table below for primitive data types allowed by the SNMP SMI, and Textual conventions . Access ::= “not-accessible” | “accessible-for-notify” | “read-only” | “read-write” | “read-create” Status ::= “current” | “deprecated” | “obsolete” IndexPart ::= “INDEX” | empty END Cisco SES PNNI Controller Software Configuration Guide Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 D-3 Appendix D SNMP Management Information Base SNMP Fundamentals The MIB object data types are shown in the following table. Data Type Description primitive type INTEGER Integer-valued information between -2147483648 and 2147483647). OCTET STRING String of bytes of length 0 to 65,535 OBJECT IDENTIFIER Numeric ASN-1-type object identifier Integer32 Integer-valued information in the range from -2147483648 through 2147483647. Unsigned32 Unsigned Integer-valued information in the range from 0 through 2147483647. Counter32 Represents a non-negative integer which monotonically increases until it reaches a maximum value of 4294967295 decimal, when it wraps around and starts increasing again from zero TimeTicks Period of time, measured in units of 0.01 seconds, in the range from 0 through 4294967295. Textual Convention TimeStamp Value of the sysUpTime object at which a specific occurrence happened. The specific occurrence must be defined in the description of any object defined using this type, TimeTicks. TruthValue Represents a boolean value, INTEGER { true(1), false(2) } DisplayString Octet string, in the range from 0 through 255. AtmAddress ATM End-System Addresses, OCTET STRING (SIZE (8 | 20)) NetPrefix Network-Prefixes for an ATM Address, OCTET STRING (SIZE (8 | 13)) IpAddress Represents a 32-bit internet address. It is in network byte-order, OCTET STRING (SIZE (4)) RowStatus Manages the creation and deletion of rows, and is the value of the SYNTAX clause for the status column of a row. Cisco SES PNNI Controller Software Configuration Guide D-4 Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 Appendix D SNMP Management Information Base SNMP Fundamentals Data Type Description CiscoAtmServiceCategory The ATM forum service categories. Additionally, ABR foresight service type is also supported. The valid values are CiscoWanLpbkTypes • cbr1(1) • vbr1RT(2) • vbr2RT(3) • vbr3RT(4) • vbr1nRT(5) • vbr2nRT(6) • vbr3nRT(7) • ubr1(8) • ubr2(9) • abr(10) • cbr2(11) • cbr3(12). Defines possible loopback configurations for a connection. • noLpbk(1)—no loopback or clear configured loopback • destructive(2)—loopback all cells, causing data disruption. • nonDestructive(3)—loopback performed using OAM loopback cells. Does not disrupt regular traffic. CiscoWanLpbkDir CiscoWanTestStatus Direction in which looped should be effected. • external (1)—loop port traffic back to port. Applicable only for destructive mode. • internal(2)—loop switch’s egress traffic back to switch. Applicable only for destructive mode. • forward(3)—inject OAM loopback cells towards the switching fabric (ingress). Applicable only for non-destructive mode. • reverse(4)—inject OAM loopback cells towards the port (egress). Applicable only for non-destructive mode. Defines possible loopback test status at an endpoint.noStatus (1). The valid values are: lpbkInProgress(2), lpbkSuccess(3), lpbkAbort(4), lpbkTimeOut(5), lpbkInEffect(6) CiscoWanOperStatus Defines operational status of an endpoint. The valid values are operOk(1), operFail(2), or adminDown(3) CiscoWanNsapAtmAddress ATM address used by the networking entity. The only address type presently supported is NSAP (20 octets). OCTET STRING (SIZE(20)) Cisco SES PNNI Controller Software Configuration Guide Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 D-5 Appendix D SNMP Management Information Base SNMP Fundamentals Data Type Description CiscoWanAlarmState Defines possible alarms at an endpoint. The valid options are CiscoWanXmtState CiscoWanRcvState CiscoWanERSConfg CiscoWanVSVDConfg • ingAisRdi(1)—Endpoint receiving AIS or RDI cells in ingress direction • egrAisRdi(2)—Endpoint receiving AIS or RDI cells in egress direction • conditioned(4)— Networking entity has forced the endpoint out of service. This alarm could be attributed to either routing failure or to a maintenance operation initiated by the networking entity. • interfaceFail(8)—Interface to which this connection belongs has failed. • ccFail (16)— OAM continuity check between the connection and its peer endpoint has detected a failure. • mismatch(32)—Connection exists in SM database, but not in the network controller database. • ingAbitFail(64)—Feeder connection detects A-bit failure in the ingress direction. Defines possible transmit states of an endpoint. Enter one of the following options: • normal(1)—Endpoint transmitting normal traffic. • sendingAIS(2)—Endpoint inhibits regular traffic, sends AIS on egress • sendingRDI(3)—Endpoint inhibits regular traffic, sends AIS on egress Defines possible receive states of an endpoint. Enter one of the following options: • normal(1)—Endpoint receiving normal traffic. • receivingAIS(2)—Endpoint receiving AIS, in either ingress/egress. • receivingRDI(3)—Endpoint receiving RDI, in either ingress/egress. • ccFailure(4)—Endpoint does not receive OAM CC cells. Defines possible configuration for Explicit Rate Stamping (ERS). Enter one of the following options: • None(1)—Disable the ERS on connection. • enableIngress(2)—Enable ERS in the Ingress direction ONLY. • enableEgress(3)—Enable ERS in the Egress direction ONLY. • enableBoth(4)—Enable ERS in both direction. Defines possible VSVD configuration applicable to an endpoint. Enter one of the following options: • vsvdOff (1)—Disable VSVD. • vsvdOn(2)—Enable VSVD. • switchDefault(3)—Use default settings on switch. Cisco SES PNNI Controller Software Configuration Guide D-6 Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 Appendix D SNMP Management Information Base SNMP Fundamentals Data Type Description CiscoWanAisIW Defines an SPVC endpoint’s AIS capability: AbrRateFactors • e2eAisCapable(1)—Endpoint capable of detecting/generating e2e AIS. • segAisCapable(2)—Endpoint capable of detecting/generating seg AIS. Defines possible rate factors to be used in increasing/decreasing ABR cell rate. The valid values are: • oneOver32768(1) • oneOver16384(2) • oneOver8192(3) • oneOver4096(4) • oneOver2048(5) • oneOver1024(6) • oneOver512(7) • oneOver256(8) • oneOver128(9) • oneOver64(10) • oneOver32(11) • oneOver16(12) • oneOver8(13) • oneOver4(14) • oneOver2(15) • one(16) SNMP Traps A trap is an unsolicited message sent by an agent to a registered SNMP management stations. Traps notify the management stations of some unusual event. Traps provide management stations with the following information: • Network management subsystem that generated the trap (Enterprise)—Identifies the network management subsystem that generated the trap. • IP address of the object generating the trap (Agent-addr). • Generic trap type (Generic)—Pre-defined trap type, RFC1157 generic trap types includes coldStart, warmStart, linkDown, linkUp, authenticationFailure, egpNeighborLoss and enterpriseSpecific. • Specific trap type (Specific)—If the value of Generic Trap Type is enterpriseSpecific, this specific trap type field contains a number that indicates a CISCO specific trap. • Time between the last initialization of the network entity that issued the trap and the generation of the Atropatene Ticks. • “Interesting” information (Varbind List)—Additional information relating to the trap (the significance of this field is implementation-specific). Cisco SES PNNI Controller Software Configuration Guide Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 D-7 Appendix D SNMP Management Information Base MIBs Supported by the SES Controller MIBs Supported by the SES Controller The SES controller uses the following MIBs: • ATM MIB Object • PNNI MIB Objects • Cisco WAN ATM MIB Objects ATM MIB Object The ATM MIB uses the atmInterfaceConfTable MIB objects. Table D-1 describes the objects in the atmInterfaceConfTable MIB. atmInterfaceConfTable The atmInterfaceConfTable contains ATM local interface configuration parameters, one entry per ATM interface port. Although there are many attributes for the table, the SES controller supports only atmInterfaceMyNeighborIpAddress and atmInterfaceMyNeighborIfName as read-only access. . Table D-1 atmInterfaceConfTable Entries No. Object Type Access Description 11 atmInterfaceMyNeighborIpAddress read-write IP address of the neighbor system connected to the far end of this interface, to which a network management station can send SNMP messages, as IP datagrams sent to UDP port 161, in order to access network management information concerning the operation of that system. Note 12 atmInterfaceMyNeighborIfName read-write The value of this object may be obtained by using various methods, such as manual configuration, or through ILMI interaction with the neighbor system. Text name of the interface on the neighbor system at the far end of this interface, and to which this interface connects. If the neighbor system is manageable with SNMP and supports the object ifName, the value of this object must be identical with that of ifName for the ifEntry of the lowest level physical interface for this port. If this interface does not have a a text name, the value of this object is a zero length string. Note The value of this object may be obtained by using various methods, such as manual configuration, or through ILMI interaction with the neighbor system. Cisco SES PNNI Controller Software Configuration Guide D-8 Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 Appendix D SNMP Management Information Base MIBs Supported by the SES Controller PNNI MIB Objects The PNNI MIB refers to the following objects: • pnniBaseGroup • pnniNodeTable • pnniNodePglTable • pnniNodeTimerTable • pnniNodeSvccTable • pnniScopeMappingTable • pnniLinkTable • pnniSummaryAddressTable • These MIB Objects are described in Table D-2 through Table D-9. pnniBaseGroup Table D-2 describes the objects in the pnniBaseGroup MIB. Table D-2 pnniBaseGroup No. Object Type Access Description 1 pnniHighestVersion read only The highest version of the PNNI protocol that the software in this switching system is capable of executing. Note 2 pnniLowestVersion read only See “ATM Forum PNNI 1.0 Section 5.6.1.” The lowest version of the PNNI protocol that the software in this switching system is capable of executing. Note See “ATM Forum PNNI 1.0 Section 5.6.1.” 3 pnniDtlCountOriginator read only The total number of DTL stacks that this switching system has originated as the DTLOriginator and placed into signaling messages. This includes the initial DTL stacks computed by this system as well as any alternate route (second, third choice and so forth) DTL stacks computed by this switching system in response to crankbacks 4 pnniDtlCountBorder read only The number of partial DTL stacks that this switching system has added into signaling messages as an entry border node. This includes the initial partial DTL stacks computed by this system as well as any alternate route (second, third, choice, and so forth) partial DTL stacks computed by this switching system in response to crankbacks. 5 pnniCrankbackCountOriginator read only The count of the total number of connection setup messages including DTL stacks originated by this switching system that have cranked back to this switching system at all levels of the hierarchy. 6 pnniCrankbackCountBorder The count of the total number of connection setup messages including DTLs added by this switching system as an entry border node that have cranked back to this switching system at all levels of the hierarchy. This count does not include crankbacks. This switching system was not the crankback destination, only those crankbacks that were directed to this switching system are counted here. read only Cisco SES PNNI Controller Software Configuration Guide Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 D-9 Appendix D SNMP Management Information Base MIBs Supported by the SES Controller Table D-2 pnniBaseGroup (continued) No. Object Type Access Description 7 pnniAltRouteCountOriginator read only The total number of alternate DTL stacks that this switching system computed and placed into signaling messages as the DTL originator. 8 pnniAltRouteCountBorder read only The total number of alternate partial DTL stacks that this switching system computed and placed into signaling messages as a entry border node. 9 pnniRouteFailCountOriginator read only The total number of times the switching system failed to compute a viable DTL stack as the DTL originator for some call. It indicates the number of times a call was cleared from this switching system due to originator routing failure. 10 pnniRouteFailCountBorder read only The total number of times the switching system failed to compute a viable partial DTL stack as an entry border node for some call. It indicates the number of times a call was either cleared or cranked back from this switching system due to border routing failure. 11 pnnieRouteFailUnreachableOri read ginator only The total number of times the switching system failed to compute a viable DTL stack as the DTLOriginator because the destination was unreachable. For example, those calls that are cleared with cause #2 ‘specified transit network unreachable’ or cause #3 ‘destination unreachable’ in the cause. 12 pnniRouteFailUnreachableBord read er only The total number of times the switching system failed to compute a viable partial DTL stack as an entry border node because the target of the path calculation was unreachable; for example, those calls that are cleared or cranked back with cause #2 “specified transit network unreachable” or cause #3 “destination unreachable” in the cause. pnniNodeTable The pnniNodeTable (Table D-3) collects attributes that affect the operation of a PNNI logical node. Note createAndWait is not supportedas a rowStatus value for the pnniNodeRowStatus attribute. Note See “ATM Forum PNNI 1.0 Annex F.” Cisco SES PNNI Controller Software Configuration Guide D-10 Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 Appendix D SNMP Management Information Base MIBs Supported by the SES Controller Table D-3 pnniNodeTable No. Object Type Access Description 1 pnniNodeIndex not-accessible A value assigned to a node in this switching system that uniquely identifies it in the MIB. 2 pnniNodeLevel read-create pnniNodeId read-create — The level of the node in the PNNI hierarchy. This 96 attribute is used to determine the default node ID and the default peer group ID. This object may only be written when pnniNodeAdminStatus has the value down. Note 3 Default See “ATM Forum PNNI 1.0 Section 5.3.1 Annex F.” The value the switching system is using to represent itself as this node. This object may only be written when pnniNodeAdminStatus has the value down. — If pnniNodeLowest is true, then the default node ID takes the form defined in Section 5.3.3 for lowest level nodes, with the first octet equal to pnniNodeLevel, the second octet equal to 160, and the last 20 octets equal to pnniNodeAtmAddress. If pnniNodeLowest is false, the default node ID takes the form defined in Section 5.3.3 for logical group nodes. The first octet is equal to pnniNodeLevel, the next fourteen octets are equal to the value of pnniNodePeerGroupId for the child node whose election as PGL causes this LGN to be instantiated. The next six are octets equal to the ESI of pnniNodeAtmAddress, and the last octet equal to zero. 4 pnniNodeLowest read-create — Indicates whether this node acts as a lowest level node or whether this node is a logical group node that becomes active when one of the other nodes in this switching system becomes a peer group leader. The value “false” must not be used with nodes that are not PGL/LGN capable. This object may only be written when pnniNodeAdminStatus has the value “down.” 5 pnniNodeAdminStatus read-create Indicates whether the administrative status of the node is “up” (the node is allowed to become active) or “down” (the node is forced to be inactive). Up When pnniNodeAdminStatus is down, then pnniNodeOperStatus must also be “down.” 6 pnniNodeOperStatus read-only Indicates whether the node is active or whether the — node has yet to become operational. When the value is down, all state has been cleared from the node and the node is not communicating with any of its neighbor nodes. Cisco SES PNNI Controller Software Configuration Guide Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 D-11 Appendix D SNMP Management Information Base MIBs Supported by the SES Controller Table D-3 pnniNodeTable (continued) No. Object Type Access Description Default 8 pnniNodeAtmAddress read-create — This node’s ATM End System Address. Remote systems exchanging PNNI protocol packets with this node direct the packets or calls to this address. This attribute may only be written when pnniNodeAdminStatus has the value down. Note 9 pnniNodePeerGroupId read-create See “ATM Forum PNNI 1.0 Section 5.2.2.” The Peer Group Identifier of the peer group of which — the node will become a member. The default value of this attribute has the first octet equal to pnniNodeLevel. The next pnniNodeLevel bits are equal to the pnniNodeLevel bits starting from the third octet of pnniNodeId. The remainder are padded with zeros. This object may only be written when pnniNodeAdminStatus has the value down. Note 10 pnniNodeRestrictedTransit read-create Specifies whether the node is restricted from allowing support of SVCs transiting this node. This attribute determines the setting of the restricted transit bit in the nodal information group originated by this node. Note 11 pnniNodeComplexRep read-create See “ATM Forum PNNI 1.0 Section 5.3.2, Annex F.” — See “ATM Forum PNNI 1.0 Section 5.8.1.2.3.” Specifies whether this node uses the complex node representation. A value of “true” indicates that the complex node representation is used. A value of “false” indicates that the simple node representation is used. This attribute determines the setting of the nodal representation bit in the nodal information group originated by this node. — Reference: ATM Forum PNNI 1.0 Section 5.8.1.2.3 12 pnniNodeRestrictedBranching read-only Indicates whether the node is able to support — additional point-to-multipoint branches. A value of “false” indicates that additional branches can be supported; a value of “true” indicates that additional branches cannot be supported. This attribute reflects the setting of the restricted branching bit in the nodal information group originated by this node. Reference: ATM Forum PNNI 1.0 Section 5.8.1.2.3 Cisco SES PNNI Controller Software Configuration Guide D-12 Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 Appendix D SNMP Management Information Base MIBs Supported by the SES Controller Table D-3 pnniNodeTable (continued) No. Object Type Access Description 13 pnniNodeDatabaseOverload read-only Specifies whether the node is currently operating in — topology database overload state. This attribute has the same value as the non-transit for PGL Election bit in the nodal information group originated by this node. Note Default See “ATM Forum PNNI 1.0 Section 5.8.1.2.3.” 14 pnniNodePtses read-only Gauges the total number of PTSes currently in this node’s topology databases(s). — 15 pnniNodeRowStatus read-create Creates, deletes, activates, and deactivates a node. — pnniNodePglTable Peer group leader election information for a PNNI node in this switching system. Table D-4 describes the objects in the pnniNodePglTable. Reference: ATM Forum PNNI 1.0 Section 5.10.1. Table D-4 pnniNodePglTable No. Object Type Access Description 1 pnniNodePglLeadershipPriority read-create The Leadership priority value this 0 node should advertise in its nodal information group for the given peer group. Only the value zero can be used with nodes that are not PGL/LGN capable. If there is no configured parent node index or no corresponding entry in the pnniNodeTable, then the advertised leadership priority is zero regardless of this value Note 2 pnniNodeCfgParentNodeIndex Default See “ATM Forum PNNI 1.0 Section 5.10.1.2.” 0 read-create The local node index used to identify the node that represents this peer group at the next higher level hierarchy, if this node becomes peer group leader. Value 0 indicates that there is no parent node. Note See “ATM Forum PNNI 1.0 Annex F.” Cisco SES PNNI Controller Software Configuration Guide Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 D-13 Appendix D SNMP Management Information Base MIBs Supported by the SES Controller Table D-4 pnniNodePglTable (continued) No. Object Type Access Description 3 pnniNodePglInitTime read-create The amount of time in seconds this 15 node will delay advertising its choice of preferred PGL after having initialized operation and reached the full state with at least one neighbor in the peer group. Note 4 pnniNodePglOverrideDelay pnniNodePglReelectTime pnniNodePglState See “ATM Forum PNNI 1.0 Annex G OverrideDelay.” read-create The amount of time, in seconds, after losing connectivity to the current peer group leader that this node will wait before re-starting the process of electing a new peer group leader. Note 6 See “ATM Forum PNNI 1.0 Annex G PGLInitTime” read-create The amount of time, in seconds, a 30 node will wait for itself to be declared the preferred PGL by unanimous agreement among its peers. In the absence of unanimous agreement, this objects set the amount of time that will pass before a two thirds majority declares the node a peer group leader. Attempts to get a unanimous agreement will be abandoned. Note 5 Default read-only 15 See “ATM Forum PNNI 1.0 Annex G ReElectionInterval.” Indicates the state that this node is in with respect to the peer group leader election that takes place in the node’s peer group. The values are enumerated in the peer group leader state machine. Note See “ATM Forum PNNI 1.0 Section 5.10.1.1.2.” Cisco SES PNNI Controller Software Configuration Guide D-14 Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 Appendix D SNMP Management Information Base MIBs Supported by the SES Controller Table D-4 pnniNodePglTable (continued) No. Object Type Access Description 7 pnniNodePreferredPgl read-only The Node ID of the node that the local node believes should be or becomes the peer group leader. This is also the value the local node is currently advertising in the “preferred peer Group Leader Node ID field of its nodal information group within the given peer group. If a Preferred PGL has not been chosen, this attribute’s value is set to (all) zero(s). Note Default See “ATM Forum PNNI 1.0 Section 5.10.1.1.6.” 8 pnniNodePeerGroupLeader read-only The Node Identifier of the node that is currently operating as peer group leader of the peer group this node belongs to. If a PGL has not been elected, this attribute’s value is set to (all) zero(s). 9 pnniNodePglTimeStamp read-only The time at which the current Peer Group Leader established itself. 10 pnniNodeActiveParentNodeId read-only The Node Identifier value being used by the Peer Group Leader to represent this peer group at the next higher level of the hierarchy. If this node is at the highest level of the hierarchy or if no PGL has yet been elected the PNNI Protocol Entity sets the value of this attribute to (all) zero(s). Cisco SES PNNI Controller Software Configuration Guide Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 D-15 Appendix D SNMP Management Information Base MIBs Supported by the SES Controller pnniNodeTimerTable Table D-5 describes initial PNNI timer values and significant change thresholds . Table D-5 pnniNodeTimerTable No. Object Type Access Description Default 1 pnniNodePtseHolddown read-create The initial value for the PTSE hold down timer that will be used by the given node to limit the rate at which it can re-originate PTSEs. It must be a positive non-zero number. 10 Reference: ATM Forum PNNI 1.0 Annex G MinPTSEInterval 2 pnniNodeHelloHolddown read-create The initial value for the Hello hold down timer that will be used by the given node to limit the rate at which it sends Hellos. It must be a positive non-zero number. 10 Reference: ATM Forum PNNI 1.0 Annex G MinHelloInterval 3 pnniNodeHelloInterval read-create The initial value for the Hello Timer. In the absence of triggered Hellos, this node will send one Hello packet on each of its ports on this interval. 15 Reference: ATM Forum PNNI 1.0 Annex G HelloInterval 4 pnniNodeHelloInactiveFactor read-create The value for the Hello Inactivity factor that this node will use to determine when a neighbor has gone down. 5 Reference: ATM Forum PNNI 1.0 Annex G InactivityFactor 5 pnniNodeHlinkInact read-create The amount of time a node will continue to advertise a horizontal (logical) link for which it has not received and processed a LGN Horizontal Link information group. 120 Reference: ATM Forum PNNI 1.0 Annex G HorizontalLinkInactivityTime 6 pnniNodePtseRefreshInterval read-create The initial value for the Refresh timer that this node will use to drive (re-)origination of PTSEs in the absence of triggered updates. 1800 Reference: ATM Forum PNNI 1.0 Annex G PTSERefreshInterval Cisco SES PNNI Controller Software Configuration Guide D-16 Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 Appendix D SNMP Management Information Base MIBs Supported by the SES Controller Table D-5 pnniNodeTimerTable (continued) No. Object Type Access Description 7 pnniNodePtseLifetimeFactor read-create The value for the lifetime multiplier, expressed as a percentage. The result of multiplying the pnniNodePtseRefreshInterval attribute value by this attribute value is used as the initial lifetime that this node places into self-originated PTSEs Default 200 Reference: ATM Forum PNNI 1.0 Annex G PTSELifetimeFactor 8 pnniNodeRxmtInterval read-create The period between retransmissions of unacknowledged Database Summary packets, PTSE Request packets, and PTSPs 5 Reference: ATM Forum PNNI 1.0 Annex G DSRxmtInterval 9 pnniNodePeerDelaydAckInterval read-create The minimum amount of time between transmissions of delayed PTSE acknowledgement packets. 10 10 pnniNodeAvcrPm read-create The proportional multiplier used in the algorithms that determine significant change for AvCR parameters, expressed as a percentage. 50 Reference: ATM Forum PNNI 1.0 Section 5.8.5.2.5.4 Annex G AvCR_PM. 11 pnniNodeAvcrMt read-create The minimum threshold used in the algorithms that determine significant change for AvCR parameters, expressed as a percentage. 3 Reference: ATM Forum PNNI 1.0 Section 5.8.5.2.5.4 Annex G AvCR_mT 12 pnniNodeCdvPm read-create The proportional multiplier used in the alg9orithms that determine significant change for CDV metrics, expressed as a percentage. 25 Reference: ATM Forum PNNI 1.0 Section 5.8.5.2.5.6 Annex G CDV_PM 13 pnniNodeCtdPm read-create The proportional multiplier used in the algorithms that determine significant change for CTD metrics, expressed as a percentage. 50 Reference: ATM Forum PNNI 1.0 Section 5.8.5.2.5.5. Annex maxCTD_PM Cisco SES PNNI Controller Software Configuration Guide Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 D-17 Appendix D SNMP Management Information Base MIBs Supported by the SES Controller pnniNodeSvccTable The pnniNodeSvccTable is a table of variables related to SVCC-based routing control channels. Table D-6 Nodal SVCC-based RCC Variables Table No. Object Type Access Description 1 pnniNodeSvccInitTime read-create The amount of time this node will delay initiating establishment of an SVCC to a neighbor with a numerically lower ATM address, after determining that such an SVCC should be established. Default 4 Reference: ATM Forum PNNI 1.0 Annex G InitialLGNSVCTimeout. 2 pnniNodeSvccRetryTime read-create The amount of time this node will delay after an apparently still necessary and viable SVCC-based RCC is unexpectedly torn down before attempting to re-establish it. 30 Reference: ATM Forum PNNI 1.0 Annex G RetryLGNSVCTimeout. 3 pnniNodeSvccCallingIntegrityT read-create The amount of time this node will ime 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. 35 Reference: ATM Forum PNNI 1.0 Annex G SVCCallingIntegrityTime Cisco SES PNNI Controller Software Configuration Guide D-18 Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 Appendix D SNMP Management Information Base MIBs Supported by the SES Controller Table D-6 Nodal SVCC-based RCC Variables Table (continued) No. Object Type Access Description 4 pnniNodeSvccCalledIntegrityTi me read-create The amount of time this node will wait for an SVCC, which it has decided to accept as the called party, to become fully established before giving up and tearing it down. Default 50 Reference: ATM Forum PNNI 1.0 Annex G SVCCalledIntegrityTime 5 pnniNodeSvccTrafficDescriptior read-create A index into the Index atmTrafficDescrParamTable defined in RFC 1695. This traffic descriptor is used when establishing switched virtual channels for use as SVCC-based RCCs to/from PNNI logical group nodes. Reference: ATM Forum PNNI 1.0 Section 5.5.2, Annex G RCCMaximumBurstSize, RCCPeakCellRate, RCCSustainableCellRate pnniScopeMappingTable The pnniScope Table contains the mapping of membership and connection scope from organization scope values (used at the UNI interfaces) to PNNI scope (for example, in terms of PNNI routing level indicators). Reference: ATM Forum PNNI 1.0 Section 5.3.6. Table D-7 pnniScopeMappingTable No. Object Type Access Description Default 1 pnniScopeLocalNetwork read-create The highest level of PNNI hierarchy (namely, smallest PNNI routing level) that lies within the organizational scope value localNetwork(1). 96 2 pnniScopeLocalNetworkPlusOne read-create The highest level of PNNI hierarchy (namely, smallest PNNI routing level) that lies within the organizational scope value localNetwtorkPlusOne(1). 96 Cisco SES PNNI Controller Software Configuration Guide Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 D-19 Appendix D SNMP Management Information Base MIBs Supported by the SES Controller Table D-7 pnniScopeMappingTable (continued) No. Object Type Access Description Default 3 pnniScopeLocalNetworkPlusTwo read-create The highest level of PNNI hierarchy (namely, smallest PNNI routing level) that lies within the organizational scope value localNetworkPlusTwo(3). 96 4 pnniScopeSiteMinusOne read-create The highest level of PNNI hierarchy (namely, the smallest PNNI routing level) that lies within the organizational scope value siteMinusOne(4). 80 5 pnniScopeIntraSite read-create The highest level of PNNI hierarchy (namely, the smallest PNNI routing level) that lies within the organizational scope value interaSite(5). 80 6 pnniScopeSitePlusOne read-create The highest level of PNNI hierarchy (namely, the smallest PNNI routing level) that lies within the organizational scope value sitePlusOne(6). 72 7 pnniScopeOrganizationMinusOne read-create The highest Level of PNNI hierarchy (namely, the smallest PNNI routing level) that lies within the organizational scope value organizationMinusOne(7) . 72 8 pnniScopeIntraOrganization read-create The highest level of PNNI hierarchy (namely, the smallest PNNI routing level) that lies within the organizational scope value intraOrganization(8). 64 9 pnniScopeOrganizationPlusOne read-create The highest level of PNNI hierarchy (namely, the PNNI routing level) that lies within the organizational scope value organizationPlusOne(9). 64 Cisco SES PNNI Controller Software Configuration Guide D-20 Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 Appendix D SNMP Management Information Base MIBs Supported by the SES Controller Table D-7 pnniScopeMappingTable (continued) No. Object Type Access Description Default 10 pnniScopeCommunityMinusOne read-create The highest level of PNNI hierarchy (namely, the smallest PNNI routing level) that lies within the organizational scope value communityMinusOne(10) . 64 11 pnniScopeIntraCommunity read-create The highest level of PNNI hierarchy (namely, the smallest PNNI routing level) that lies within the organizational scope value intrCommunity(11). 48 12 pnniScopeCommunityPlusOne read-create The highest level of PNNI hierarchy (namely, the smallest PNNI routing level) that lies within the organizational scope communityPlusOne(1). value 48 13 pnniScopeRegional read-create The highest level of PNNI hierarchy (namely, the smallest PNNI routing level) that lies within the organizational scope value regional(13). 32 14 pnniScopeInterRegional read-create The highest level of PNNI hierarchy (namely, the smallest PNNI routing level) that lies within the organizational scope value interRegional(14). 32 15 pnniScopeGlobal read-create The highest level of PNNI hierarchy (namely, the smallest PNNI routing level) that lies within the organizational scope value vlobal(15). 0 pnniLinkTable This table contains the attributes necessary to describe the operation of logical links attached to the local switching system and the relationship with the neighbor nodes on the other end of the links. Links are attached to a specific node within the switching system. A concatenation of the Node Index of the node within the local switching system and the port ID are used a the instance ID to uniquely identify the link. Links may represent horizontal links between lowest level neighboring peers, outside links, uplinks, or horizontal links to and from LGNs. Cisco SES PNNI Controller Software Configuration Guide Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 D-21 Appendix D SNMP Management Information Base MIBs Supported by the SES Controller The entire pnniLink object is read-only, reflecting the fact that this information is discovered dynamically by the PNNI protocol rather than configured. Reference: ATM Forum PNNI 1.0 Section 5.6. Table D-8 pnniLinkTable No. Object Type Access Description 1 pnniLinkPortId not-accessible The Port Identifier of the link as selected by the local node. This value has meaning only within the context of the node to which the port is attached. 2 pnniLinkType read-only Indicates the type of link being described. 3 pnniLinkVersion read-only For horizontal and outside links between lowest-level nodes and for links of unknown type, this attribute indicates the version of PNNI routing protocol used to exchange information over this link. If communication with the neighbor node has not yet been established, then the Version is set to “unknown”. For uplinks (where the port ID is not also used for the underlying outside link) or links to/from LGNs, the Version is set to “unknown.” 4 pnniLinkHelloState read-only For horizontal and outside links between lowest-level nodes and for links of unknown type. This attribute indicates the state of the Hello protocol exchange over this link. For links to/from LGCs, this attribute indicates the state of the corresponding LGC Horizontal Link Hello State Machine. For uplinks (where the port ID is not also used for the underlying outside link), this attribute is set to notApplicable. Default Reference: ATM Forum PNNI 1.0 Section 5.6.2.1. Cisco SES PNNI Controller Software Configuration Guide D-22 Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 Appendix D SNMP Management Information Base MIBs Supported by the SES Controller Table D-8 pnniLinkTable (continued) No. Object Type Access Description 5 pnniLinkRemoteNodeId read-only Indicates the node identifier of the remote (neighboring) node on the other end of the link. If the pnniLinkType is ‘outside link and uplink,’ this is the node identifier of the lowest-level neighbor node on the other end of the outside link. If the remote node ID is unknown or if the pnniLinkType is “uplink,” this attribute is set to all zeros. 6 pnniLinkRemotePortId read-only Injustices the port identifier of the port at the remote rend of the link as assigned by the remote node. If the pnniLinkType is ‘outside link and uplink,’ this is the port identifier assigned by the lowest-level neighbor node to identify the outside link. If the remote port ID is unknown or if the pnniLinkType is ‘uplink,’ this attribute is set to zero. 7 pnniLinkDerivedAggrToken read-only Indicates the derived aggregation token value used on this link. For horizontal links between lowest-level nodes and when the link type is not yet known, this attribute takes the value of zero. Default Reference: ATM Forum PNNI 1.0 Section 5.10.3.1 8 pnniLinkUpnodeId read-only For outside links and uplinks, this attribute contains the Node Identifier of the upnode (the neighbor node’s identity at the level of the common peer group). When the upnode has not yet been identified, this attribute is set to zero. For horizontal links or when the link type is not yet known, this attribute is set to zero. 9 pnniLinkUpnodeAtmAddress read-only For outside links and uplinks, this attribute contains the ATM End System Address used to establish connections to the upnode.When the upnode has not yet been identified, this attribute is set to zero. For horizontal links or when the link type is not yet known, this attribute is set to zero. Cisco SES PNNI Controller Software Configuration Guide Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 D-23 Appendix D SNMP Management Information Base MIBs Supported by the SES Controller Table D-8 pnniLinkTable (continued) No. Object Type Access Description 10 pnniLinkCommonPeerGroupId read-only For outside links and uplinks, this attribute contains the peer group identifier of the lowest level common Peer Group in the ancestry of the neighboring node and the node within the local switching system. The value of this attribute takes on a value determined by the Hello exchange of hierarchical information that occurs between the two lowest-level border nodes. When the common peer group has not yet been identified, this attribute is set to zero. For horizontal links or when the link type is not yet known, this attribute is set to all zeros. 11 ppniLinkIfIndex read-only For horizontal and outside links between lowest-level nodes and for links of unknown type, this attribute identifies the interface to which the logical link corresponds. Default For all other cases, the value of this object is zero. 12 PnniSvccRccIndex read-only For horizontal links to/from LGNs, this attribute identifies the SVCC-based RCC used to exchange information with the neighboring peer logical group node. If the pnniLinkType is not ‘horizontal link to/from LGN’, this attribute shall take the value of zero. 13 pnniLinkRcvHellos read-only For horizontal and outside links between lowest-level nodes and for links of unknown type, this attribute contains a count of the number of Hello Packets received over this link. If the pnniLinkType is ‘horizontal link to/from LGN’ or ‘uplink’, this attribute is set to zero. 14 pnniLinkXmtHellos read-only For horizontal and outside links between lowest-level nodes and for links of unknown type, this attribute contains a count of the number of Hello Packets transmitted over this link. If the pnniLinkType is ‘horizontal link to/from LGN’ or ‘uplink’, this attribute is set to zero. Cisco SES PNNI Controller Software Configuration Guide D-24 Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 Appendix D SNMP Management Information Base MIBs Supported by the SES Controller pnniSummaryAddressTable The pnniSummaryAddressTable is a list of the summary address prefixes that may be advertised by the specified logical PNNI entity. Note createAndWait is not supported as a rowStatus value for the pnniSummaryAddressRowStatus attribute. Reference: ATM Forum PNNI 1.0 Section 5.9.2 Table D-9 pnniSummaryAddressTable No. Object Type Access Description Default 1 pnniSummaryAddressType not-accessible The type (e.g. internal or exterior) of summary being described. 2 pnniSummaryAddressAddress not-accessible The ATM end system address prefix for the summary. 3 pnniSummaryAddressPrefixLength not-accessible The prefix length for the summary. 4 pnniSummaryAddressSuppress read-create false Determines what is done with addresses that are being summarized by the instance. The default value will indicate that the summary should propagate into the peer group. Network management will be able to set the value of this attribute to “suppress (e.g. true), which suppresses the summary and any reachable addresses it summarizes from being advertised into the peer group. 5 pnniSummaryAddressState read-only Indicates whether the summary is currently being advertised by the node within the local switching system into its peer group. 6 pnniSummaryAddressRowStatus read-create To create, delete, activate, and deactivate a summary Cisco WAN SVC MIB Objects • ciscoWANSvcInfo • ciscoWANSpvcPort Cisco SES PNNI Controller Software Configuration Guide Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 D-25 Appendix D SNMP Management Information Base MIBs Supported by the SES Controller ciscoWANSvcInfo Table D-10 SVC Information Group No. Object Type Access Description 1 cwsSwRevision read-onl y PNNI network controller software revision number 6 cwsControllerStatus read-onl y Administrative status of the controller as active(1), standby(2), or quiescent(3). 7 cwspPnniStndbyControllerStatus Default • Active (1) indicates the card is in active state. • Stanby(2) indicates the card is out of service • Quiescent(3) is neither of the above two conditions are present. read-onl y Administrative status of the standby controller. This object is only used in the trap varbind. 8 cwspPnniControllerStatus read-onl y Administrative status of the PNNI controller. 9 cwspPnniControllerPhySlot read-onl y the PNNI controller physical location. This object is only used in the trap varbind. CiscoWANSpvc Port • cwspConfigTable • cwspCallStatsTable • cwspCacConfigTable • cwspSigStatsTable • cwspAddressTable • cwspLoadTable • cwspConnTrace • cwspOperationTable cwspConfigTable The interface configuration table collects attributes that affect the operation of the controller interface. Note Use createAndGo to create a row and enter 3 (destroy) to delete a row. The managed device will return either active or notInService for a row status. There is a single row for each interface that the managed system is expected to be added or managed. Cisco SES PNNI Controller Software Configuration Guide D-26 Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 Appendix D SNMP Management Information Base MIBs Supported by the SES Controller Table D-11 Interface Configuration Table Entries No Object Type Access Description Default 1 cwspAdminStatus read-create Administrative status of the interface, as either in service or out of service. outService • inService(1) indicates that the interface is currently operational. • outService(2) indicates that the interface is not operational. 3 cwspSvcBlocked read-create Indicates whether switch’s virtual connections are allowed through this interface. false 4 cwspSpvcBlocked read-create Indicates whether soft permanent virtual connections are allowed through this interface. false 5 cwspIlmiAddrRegEnable read-create Indicates whether ILMI address registration is enabled or disabled. true 6 cwspIlmiAutoConfEnable read-create Indicates whether auto-configuration of the interface is turned on or off. If auto-configuration is enabled, the interface comes up using the ILMI auto-configuration. true 7 cwspIlmiServRegEnable read-create Indicates whether service registry is enabled or disabled true on the PNNI controller interface. 8 cwspPhyIdentifier read-create Indicates the physical identification of the interface. Mandatory when the port is provisioned for the first time through SNMP. 9 cwspSignallingVpi read-create Denotes the signaling VPI used on the interface in the range of 0 and 4095. 10 cwspSignallingVci read-create Indicates the signaling VCI used on the PNNI Controller 5 interface, in the range 0 to 65535. 11 cwspRoutingVpi read-create Indicates the VPI used for PNNI lowest level RCC. 12 cwspRoutingVci read-create Indicates the VCI used for the PNNI lowest level RCC, 18 in the range 0 to 65535. 13 cwspMaxVpiBits read-only Maximum number of active VPI bits on this ATM interface in the range of 0 to 12. For virtual interfaces (namely, the virtual path connections used by PNNI), this value has no meaning and is set to zero. 14 cwspMaxVciBits read-only Maximum number of active VCI bits on this ATM interface. 0 0 Cisco SES PNNI Controller Software Configuration Guide Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 D-27 Appendix D SNMP Management Information Base MIBs Supported by the SES Controller Table D-11 Interface Configuration Table Entries (continued) No Object Type Access Description 15 cwspUniVersion read-create Indication of the latest version of the ATM Forum UNI uni31(3) signaling specification on this ATM interface. If this value is not present, a version of the UNI earlier than 3.1 is assumed. Acceptable values are: • uni20(1), • uni30(2), • uni31(3), • uni40(4), • ituDss2(5), • frf4(6) • unsupported(7) • ip(8) Default If the peer IME value of this object is the same as, or later than the local IME value, the version corresponding to the local IME value should be attempted. If the peer IME value of this object is earlier the local IME should attempt the version corresponding to the peer IME value. If neither of the above two conditions exist, compatibility of the two IMEs cannot be assumed. 16 cwspNniVersion read-create Indication of the latest version of the ATM Forum PNNI pnni10(3) Signaling specification on this ATM interface. Acceptable values are: • iisp30(1), • iisp31(2), • pnni10(3) Note the PNNI routing version is determined through ILMI. If the peer IME value of this object is the same as, or later than the local IME value, the version corresponding to the local IME value should be attempted. If the peer IME value of this object is earlier, the local IME should attempt the version corresponding to the peer IME value. If neither of the above two conditions exist, compatibility of the two IMEs cannot be assumed. 17 cwspUniType read-create Type of ATM device, either public or private. private(2) Cisco SES PNNI Controller Software Configuration Guide D-28 Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 Appendix D SNMP Management Information Base MIBs Supported by the SES Controller Table D-11 Interface Configuration Table Entries (continued) No Object Type Access Description Default 18 cwspSide read-create Type of ATM device, either user(1) or network(2). This network(2) object is used in automatic ATM interface-type determination procedure such that a correct operational ATM interface-type can be determined. An ATM end system shall take the value of user(1) and an ATM network node shall take the value of node (2). 19 cwspMaxP2pCalls read-create Maximum number of point-to-point calls (including 10000 VCs and VPs allowed on the interface) in the range 0 to 65535. This attribute is read-only. 20 cwspMaxP2mpRoots read-create Maximum number of root VCs (for point-to-multipoint) 1000 allowed on the interface in the range 0 to 65535. 21 cwspMaxP2mpLeafs read-create Maximum number of leaf VCs (for point-to-multipoint) 4095 allowed on the interface, in the range 0 to 65535. 22 cwspMinSvccVpi read-create Minimum SVCC VPI configured on the interface, in the 0 range 0 to 4095. 23 cwspMaxSvccVpi read-create Maximum SVCC VPI configured on the interface, in the 4095 range 0 to 4095. 24 cwspMinSvccVci read-create Minimum SVCC VCI configured on the interface, in the 35 range 0 to 65535. 25 cwspMaxSvccVci read-create Maximum SVCC VCI configured on the interface, in the 65535 range 35 to 65535. 26 cwspMinSvpcVpi read-create Minimum SVPC CPI configured on the interface, in the 1 range 1 to 4095. 27 cwspMaxSvpcVpi read-create Maximum SVPC VPI configured on the interface, in the 4095 range 1 to 4095. 28 cwspEnhancedIisp read-create Indicates if enhanced features for IISP are either enabled or disabled. 29 cwspConfigTableRowStatus read-create Used to either create or delete the interface. 30 cwspAddrPlanSupported read-create The ATM address plan supported on an interface: false aesa(2) 1 = both 2 = aesa 3 = e164 This can only be modified if interface is public UNI. For all other interfaces, the value is aesa. 31 cwspIlmiSecureLink read-create Indicates whether ILMI Secure Link Protocol is enabled true or disabled. When secure link protocol is enabled, loss in ILMI connectivity is treated as loss of attachment point which results in all SVCs/SVPs being released on the interface. Cisco SES PNNI Controller Software Configuration Guide Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 D-29 Appendix D SNMP Management Information Base MIBs Supported by the SES Controller Table D-11 Interface Configuration Table Entries (continued) No Object Type Access Description Default 32 cwspIlmiAttachmentPoint read-create true Indicates whether detection of loss of attachment procedures are enabled on this interface. When set to true, then standard ILMI procedures are employed to detect loss of attachment point. If set to false, then ILMI protocol on the interface does not detect the loss of attachment. 33 cwspIlmiLocalAttrStd read-create Indicates whether on modification of local attributes, procedures as recommended by ILMI 4.0 specification are followed or cisco proprietary procedures are followed. When set to true, the standard ILMI procedures are followed. true 34 cwspIlmiUCSMEnable read-create Indicates whether ILMI user connection status monitoring is enabled or disabled. true cwspCallStatsTable The port call statistics table contains objects that show the statistics for SVC/SPVC calls on a specific interface. Table D-12 Port Call Statistics Table Entries No Object Type Access Description Default 1 cwspCountReset read-write Value to reset counters. Acceptable values are: noop • (noop)1 = none of the following • (reset)2 = reset all counters 2 cwspInCallAttempts read-only Number of incoming signaling messages (setup and add party) received by the switching node on this interface for call establishment. 3 cwspInCallEstabs read-only Number of incoming signaling messages (connect and add party ack) received by the switching node on this interface that indicate successful establishment of a call. Cisco SES PNNI Controller Software Configuration Guide D-30 Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 Appendix D SNMP Management Information Base MIBs Supported by the SES Controller Table D-12 Port Call Statistics Table Entries (continued) No Object Type Access Description 4 cwspInCallFailures read-only Total number of failed incoming point-to-point (p2p) and point-to-multipoint(p2mp) SVC/SPVC call attempts on this interface. 5 cwspInFilterFailures read-only Number of failed incoming point-to-point (p2p) and point-to-multipoint (p2mp) SVC/SPVC call attempts due to address filtering on this interface. 6 cwspInRouteFailures read-only Number of failed incoming point-to-point (p2p) and point-to-multipoint (p2mp) SVC/SPVC call attempts on this interface due to route to the destination not available. 7 cwspInResrcFailures read-only Number of failed incoming point-to-point (p2p) and point-to-multipoint (p2mp) SVC/SPVC call attempts on this interface due to insufficient resources, as requested in the call parameters. 8 cwspInTimerFailures read-only Number of signaling timers timed out for incoming point-to-point (p2p) and point-to-multipoint (p2mp) SVC/SPVC calls on this interface. 9 cwspInCrankbacks read-only Number of crankback IEs received on this interface for incoming point-to-point (p2p) and point-to-multipoint (p2mp) SVC/SPVC call attempts. 10 cwspOutCallAttempts read-only Number of outgoing signaling messages (setup and add party) on this interface for call establishment. 11 cwspOutCallEstabs read-only Number of outgoing signaling messages (connect and add party ack) that mark the call being established on this interface. Default Cisco SES PNNI Controller Software Configuration Guide Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 D-31 Appendix D SNMP Management Information Base MIBs Supported by the SES Controller Table D-12 Port Call Statistics Table Entries (continued) No Object Type Access Description 12 cwspOutCallFailures read-only Number of failed outgoing signaling messages for point-to-point (p2p) and point-to-multipoint (p2mp) call establishment on this interface. 13 cwspOutFilterFailures read-only Number of failed outgoing signaling messages for call establishment on this interface, due to address filtering. 14 cwspOutRouteFailures read-only Number of failed outgoing signaling messages for call establishment on this interface, due to unavailable route. 15 cwspOutResrcFailures read-only Number of failed outgoing signaling messages for call establishment on this interface, due to unavailable resources. 16 cwspOutTimerFailures read-only Number of signaling timers timed-out on this interface for outgoing signaling messages. 17 cwspOutCrankbacks read-only Number of crankback IEs sent on this interface for outgoing signaling release messages. This is generated on the node that generates the crankback IEs. Default cwspCacConfigTable The port CAC configuration table specifies the CAC information for each interface on the PNNI Controller. Table D-13 Port CAC Configuration Table Entries No. Object Type Access Description Default 1 cwspUtilFactorCbr read-write Booking factor for CBR services, in the range 1 to 200. 100 2 cwspUtilFactorRtVbr read-write Booking factor for real-time VBR service, in the range 100 1 to 200. 3 cwspUtilFactorNrtVbr read-write Booking factor for non-real-time VBR service, in the range 1 to 200. 4 cwspUtilFactorAbr read-write Booking factor for ABR service, in the range 1 to 200. 100 100 Cisco SES PNNI Controller Software Configuration Guide D-32 Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 Appendix D SNMP Management Information Base MIBs Supported by the SES Controller Table D-13 Port CAC Configuration Table Entries (continued) No. Object Type Access Description Default 5 cwspUtilFactorUbr read-write Booking factor for UBR service, in the range 1 to 200. 100 6 cwspMaxBwCbr read-write Maximum percentage bandwidth for CBR service, in the range 0 to 10000000. 1000000 The value of this variable is interpreted in the format of xxx.xxxx. For example a value of 750000 is interpreted as 75.0000%. 7 cwspMaxBwRtVbr read-write Maximum percentage bandwidth for real-time VBR service, in the range 0 to 1000000. 1000000 The value of this variable is interpreted in the format of xxx.xxxx. For example a value of 750000 is interpreted as 75.0000%. 8 cwspMaxBwNrtVbr read-write Maximum percentage bandwidth for non-real-time VBR service, in the range 0 to 1000000. 1000000 The value of this variable is interpreted in the format of xxx.xxxx. For example a value of 750000 is interpreted as 75.0000%. 9 cwspMaxBwAbr read-write Maximum percentage bandwidth for ABR service, in the range 0 to 1000000. 1000000 The value of this variable is interpreted in the format of xxx.xxxx. For example a value of 750000 is interpreted as 75.0000%. 10 cwspMaxBwUbr read-write Maximum percentage bandwidth for UBR service, in the range 0 to 1000000. 1000000 The value of this variable is interpreted in the format of xxx.xxxx. For example a value of 750000 is interpreted as 75.0000%. 11 cwspMinBwCbr read-write Minimum percentage bandwidth for CBR, in the range 0 to 1000000. 0 The total values of cwspMinBwCbr, cwspMinBwRtVbr, cwspMinBwNrtVbr, cwspMinBwAbr and cwspMinBwUbr can not exceed 1000000(100%). The value of this variable is interpreted in the format of xxx.xxxx. For example a value of 750000 is interpreted as 75.0000%. Cisco SES PNNI Controller Software Configuration Guide Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 D-33 Appendix D SNMP Management Information Base MIBs Supported by the SES Controller Table D-13 Port CAC Configuration Table Entries (continued) No. Object Type Access Description Default 12 cwspMinBwRtVbr read-write Minimum percentage bandwidth for VBR, in the range 0 0 to 1000000. The total values of cwspMinBwCbr, cwspMinBwRtVbr, cwspMinBwNrtVbr, cwspMinBwAbr and cwspMinBwUbr can not exceed 1000000(100%). The value of this variable is interpreted in the format of xxx.xxxx. For example a value of 750000 is interpreted as 75.0000%. 13 cwspMinBwNrtVbr read-write Minimum percentage bandwidth for non-real-time VBR, in the range 0 to 1000000. 0 The total values of cwspMinBwCbr, cwspMinBwRtVbr, cwspMinBwNrtVbr, cwspMinBwAbr and cwspMinBwUbr can not exceed 1000000(100%). The value of this variable is interpreted in the format of xxx.xxxx. For example a value of 750000 is interpreted as 75.0000%. 14 cwspMinBwAbr read-write Minimum percentage bandwidth for ABR, in the range 0 0 to 1000000. The total values of cwspMinBwCbr, cwspMinBwRtVbr, cwspMinBwNrtVbr, cwspMinBwAbr and cwspMinBwUbr can not exceed 1000000(100%). The value of this variable is interpreted in the format of xxx.xxxx. For example a value of 750000 is interpreted as 75.0000%. 15 cwspMinBwUbr read-write Minimum percentage bandwidth for UBR. This value is always 0. 16 cwspMaxVcCbr read-write Maximum number of VCs for CBR service percentage, 1000000 in the range 0 to 1000000. The value of this variable is interpreted in the format of xxx.xxxx. For example a value of 750000 is interpreted as 75.0000%. 17 cwspMaxVcRtVbr read-write Maximum number of VCs for real-time VBR service percentage, in the range 0 to 1000000. 1000000 The value of this variable is interpreted in the format of xxx.xxxx. For example a value of 750000 is interpreted as 75.0000%. Cisco SES PNNI Controller Software Configuration Guide D-34 Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 Appendix D SNMP Management Information Base MIBs Supported by the SES Controller Table D-13 Port CAC Configuration Table Entries (continued) No. Object Type Access Description Default 18 cwspMaxVcNrtVbr read-write Maximum number of VCs for non-real-time VBR service percentage, in the range 0 to 1000000. 1000000 The value of this variable is interpreted in the format of xxx.xxxx. For example a value of 750000 is interpreted as 75.0000%. 19 cwspMaxVcAbr read-write Maximum number of VCs for ABR service percentage, 1000000 in the range 0 to 1000000. The value of this variable is interpreted in the format of xxx.xxxx. For example a value of 750000 is interpreted as 75.0000%. 20 cwspMaxVcUbr read-write Maximum number of VCs for UBR service percentage, 1000000 in the range 0 to 1000000. The value of this variable is interpreted in the format of xxx.xxxx. For example a value of 750000 is interpreted as 75.0000%. 21 cwspMinVcCbr read-write Minimum number of VCs for CBR service percentage, 0 in the range 0 to 1000000. The value of this values of cwspMinVcCbr, cwspMinVcRtVbr, cwspMinVcNrtVbr, cwspMinVcAbr and cwspMinVcUbr can not exceed 1000000(100%). This variable is interpreted in the format of xxx.xxxx. For example a value of 750000 is interpreted as 75.0000%. 22 cwspMinVcRtVbr read-write Minimum number of VCs for real-time VBR service percentage, in the range 0 to 1000000. 0 The value of this values of cwspMinVcCbr, cwspMinVcRtVbr, cwspMinVcNrtVbr, cwspMinVcAbr and cwspMinVcUbr can not exceed 1000000(100%). This variable is interpreted in the format of xxx.xxxx. For example a value of 750000 is interpreted as 75.0000%. 23 cwspMinVcNrtVbr read-write Minimum number of VCs for non-real-time VBR service percentage, in the range 0 to 1000000. 0 The value of this values of cwspMinVcCbr, cwspMinVcRtVbr, cwspMinVcNrtVbr, cwspMinVcAbr and cwspMinVcUbr can not exceed 1000000(100%). This variable is interpreted in the format of xxx.xxxx. For example a value of 750000 is interpreted as 75.0000%. Cisco SES PNNI Controller Software Configuration Guide Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 D-35 Appendix D SNMP Management Information Base MIBs Supported by the SES Controller Table D-13 Port CAC Configuration Table Entries (continued) No. Object Type Access Description Default 24 cwspMinVcAbr read-write Minimum number of VCs for ABR service percentage, 0 in the range 0 to 1000000. The value of this values of cwspMinVcCbr, cwspMinVcRtVbr, cwspMinVcNrtVbr, cwspMinVcAbr and cwspMinVcUbr can not exceed 1000000(100%). This variable is interpreted in the format of xxx.xxxx. For example a value of 750000 is interpreted as 75.0000%. 25 cwspMinVcUbr read-write Minimum number of VCs for UBR service percentage, 0 in the range 0 to 1000000. The value of this values of cwspMinVcCbr, cwspMinVcRtVbr, cwspMinVcNrtVbr, cwspMinVcAbr and cwspMinVcUbr can not exceed 1000000(100%). This variable is interpreted in the format of xxx.xxxx. For example a value of 750000 is interpreted as 75.0000%. 26 cwspMaxVcBwCbr read-write Maximum bandwidth allowed for CBR service on a VC, 0 in the range 0 to 1000000. 27 cwspMaxVcBwRtVbr read-write Maximum bandwidth allowed for VBR service on a VC, 0 in the range 0 to 1000000. 28 cwspMaxVcBwNrtVbr read-write Maximum bandwidth allowed for non-real-time VBR on a VC, in the range 0 to 1000000. 29 cwspMaxVcBwAbr read-write Maximum bandwidth allowed for ABR service on a VC, 0 int he range 0 to 1000000. 30 cwspMaxVcBwUbr read-write Maximum bandwidth allowed for UBR service, in the range 0 to 1000000. 0 31 cwspDefaultCdvtCbr read-write Default CDVT for CBR service, in the range 0 to 2147483647. 1024 32 cwspDefaultCdvtRtVbr read-write Default CDVT real-time VBR service, in the range 0 to 1024 2147483647. 33 cwspDefaultCdvtNrtVbr read-write Default CDVT non-real-time VBR service, in the range 1024 0 to 2147483647. 34 cwspDefaultCdvtAbr read-write Default CDVT for ABR service, in the range 0 to 2147483647. 1024 35 cwspDefaultCdvtUbr read-write Default CDVT for UBR service, in the range 0 to 2147483647. 1024 0 Cisco SES PNNI Controller Software Configuration Guide D-36 Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 Appendix D SNMP Management Information Base MIBs Supported by the SES Controller Table D-13 Port CAC Configuration Table Entries (continued) No. Object Type Access Description Default 36 cwspDefaultMbsRtVbr read-write Default MBS real-time VBR service, in the range 0 to 2147483647. 1024 37 cwspDefaultMbsNrtVbr read-write Default MBS non-real-time VBR service, in the range 0 1024 to 2147483647. cwspSigStatsTable The port signaling statistics table contains signaling statistics counters. Table D-14 Port Signaling Statistics Table Entries No. Object Type Access Description Default 1 cwspSigCounterReset read-write Determines resetting of counters: noop(1) • 1 (noop) = None of the following • 2 (reset) = Resetting 2 cwspCallProcRcv read-only Number of CALL PROCEEDING messages received on this interface 3 cwspConnectRcv read-only Number of CONNECT messages received on this interface 4 cwspConnectAckRcv read-only Number of CONNECT ACK messages received on this interface 5 cwspSetupRcv read-only Number of SETUP messages received on this interface 6 cwspReleaseRcv read-only Number of RELEASE messages received on this interface 7 cwspReleaseComplRcv read-only Number of RELEASE COMPLETE messages received on this interface. 8 cwspRestartRcv read-only Number of RESTART messages received on this interface. 9 cwspRestartAckRcv read-only Number of RESTART ACK messages received on this interface. 10 cwspStatusRcv read-only Number of STATUS messages received on this interface. 11 cwspStatusEngRcv read-only Number of STATUS ENQUIRY messages received on this interface. 12 cwspNotifyRcv read-only Number of NOTIFY messages received on this interface. 13 cwspAlertRcv read-only Number of ALERT messages received on this interface. 14 cwspProgressRcv read-only Number of PROGRESS messages received on this interface. 15 cwspAddPtyRcv read-only Number of ADD PARTY messages received on this interface. 16 cwspAddPtyAckRcv read-only Number of ADD PARTY ACK messages received on this interface. 17 cwspAddPtyRejRcv read-only Number of ADD PARTY reject messages received on this interface. 18 cwspDropPtyRcv read-only Number of DROP PARTY messages received on this interface. 20 cwspIncorrectMsgRcv read-only Number of incorrect messages received on this interface. Cisco SES PNNI Controller Software Configuration Guide Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 D-37 Appendix D SNMP Management Information Base MIBs Supported by the SES Controller Table D-14 Port Signaling Statistics Table Entries (continued) No. Object Type Access Description Default 21 cwspTimerExpires read-only Number of timeouts that have occurred on this interface. 22 cwspLastCause read-only Indicates last cause of release or crankback. 23 cwspLastDiagnostic read-only Indicates the last diagnostic of release or crankback. 24 cwspCallProcXmt read-only Number of CALL PROCEEDING messages transmitted from this interface. 25 cwspConnectXmt read-only Number of CONNECT messages transmitted from this interface. 26 cwspConnectAckXmt read-only Number of C ONNECT ACK messages transmitted from this interface. 27 cwspSetupXmt read-only Number of SETUP messages transmitted from this interface. 28 cwspReleaseXmt read-only Number of RELEASE messages transmitted from this interface. 29 cwspReleaseComplXmt read-only Number of RELEASE COMPLETE messages transmitted from this interface. 30 cwspRestartXmt read-only Number of RESTART messages transmitted from this interface. 31 cwspRestartAckXmt read-only Number of RESTART ACK messages transmitted from this interface. 32 cwspStatusXmt read-only Number of STATUS messages transmitted from this interface. 33 cwspStatusEnqXmt read-only Number of STATUS ENQUIRY messages transmitted from this interface. 34 cwspNotifyXmt read-only Number of NOTIFYmessages transmitted from this interface. 35 cwspAlertXmt read-only Number of ALERT messages transmitted from this interface. 36 cwspProgressXmt read-only Number of PROGRESS messages transmitted from this interface. 37 cwspAddPtyXmt read-only Number of ADD PARTY messages transmitted from this interface. 38 cwspAddPtyAckXmt read-only Number of ADD PARTY ACK messages transmitted from this interface. 39 cwspAddPtyRejXmt read-only Number of ADD PARTY REJECT messages transmitted from this interface. 40 cwspDropPtyXmt read-only Number of DROP PARTY messages transmitted from this interface. 42 cwspSscopStatus read-only SSCOP link status --up(1) or down(2) -- on an NNI interface, object is meaningful along with ciscoWANSscopLinkChange trap. Cisco SES PNNI Controller Software Configuration Guide D-38 Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 Appendix D SNMP Management Information Base MIBs Supported by the SES Controller cwspAddressTable The port address table is the interface ATM address table. This table contains all attributes necessary to determine what the PNNI entity believes is reachable in terms of ATM End System Addresses and to determine which nod4es are advertising this reachability. This table is also used to configured static routes to reachable addresses. Entries in this table can be created/deleted by setting the cwspAddressRowsStatus object to createAndGo/detrory values. Existing entries in this table cannot modified. Entries in this table can also be created/deleted through the command provided in the CLI. Note Use createAndGo to create a row and use destroy to delete a row. The managed device will return either active or notInService for a row status. Table D-15 Port Address Table Entries No. Object Type Access Description Default 1 cwspAtmAddress not-accessible Value of the ATM end-system address. 2 cwspAddrLen not-accessible Address length, in bits in range 0 to 160, to be applied to the ATM end-system address. 3 cwspAddrType read-create Type of reachability from the advertising node to the address. Options are: • internal(1) • exterior(2) exterior( 2) Reference: ATM Forum PNNI 1.0 Section 5.8.1.3 4 5 cwspAddrProto cwspAddrPlan read-create read-create Routing mechanism by which the connectivity from the advertising node to the reachable address is learned. Options are: • local(1) • static(2) Address plan. Options are: • e164(1) • nsap(2) local(1) nsap(2) For NSAP address, the first byte of the address automatically implies one of the following NSAP address plans: 6 cwspAddrScope read-create • NSAP E.164 • NSAP DCC • NSAP ICD PNNI scope of advertisement (level of PNNI hierarchy) of 0 the reachability from the advertising node to the address, in the range 0 to 104. Cisco SES PNNI Controller Software Configuration Guide Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 D-39 Appendix D SNMP Management Information Base MIBs Supported by the SES Controller Table D-15 Port Address Table Entries (continued) No. Object Type Access Description 7 cwspAddrRedistribute read-create Defines if the reachable address specified by this entry is to false(2) be advertised by the local node into its PNNI routing domain. Options are: • true(1) • false(2) Default This object is meaningful only if the routing mechanism (cwspAddrProto) is static. 8 cwspAddressRowStatus read-create Create or delete a reachable address cwspLoadTable The port loading table specifies the load/cwsd information for each interface on the PNNI Controller. Table D-16 Port Loading Table Entries No. Object Type Access Description 1 cwspLoadBwTotal read-only Total bandwidth of the interface, in the range 0 to 2147483647 2 cwspLoadMaxBwCbr read-only Maximum bandwidth for CBR service, in the range 0 to 2147483647. 3 cwspLoadMaxBwRtVbr read-only Maximum bandwidth for real-time VBR service, in the range 0 to 2147483647. 4 cwspLoadMaxBwNrtVbr read-only Maximum bandwidth for non-real time VBR service, in the range 0 to 2147483647. 5 cwspLoadMaxBwAbr read-only Maximum bandwidth for ABR service, in the range 0 to 2147483647. 6 cwspLoadMaxBwUbr read-only Maximum bandwidth for UBR service, in the range 0 to 2147483647. 7 cwspLoadBwAvail read-only Total available bandwidth of the interface, in the range 0 to 2147483647. 8 cwspLoadAvlBwCbr read-only Available bandwidth for CBR service, in the range 0 to 2147483647. 9 cwspLoadAvlBwRtVbr read-only Available bandwidth for real time VBR service, in the range 0 to 2147483647. 10 cwspLoadAvlBwNrtVbr read-only Available bandwidth for non-real time VBR service, in the range 0 to 2147483647. 11 cwspLoadAvlBwAbr read-only Available bandwidth for ABR service, in the range 0 to 2147483647. 12 cwspLoadAvlBwUbr read-only Available bandwidth for UBR service, in the range 0 to 2147483647. 13 cwspLoadVcAvail read-only Total number of available VCs of the interface, in the range 0 to 2147483647. 14 cwspLoadAvlVcCbr read-only Number of VCs used by CBR service, in the range 0 to 2147483647. 15 cwspLoadAvlRtVbr read-only Number of VCs used by real-time VBR service, in the range 0 to 2147483647. 16 cwspLoadAvlVcNrtVbr read-only Number of VCs used by non-real time VBR service, in the range 0 to 2147483647. 17 cwspLoadAvlVcAbr read-only Number of VCs used by ABR service, in the range 0 to 2147483647. Cisco SES PNNI Controller Software Configuration Guide D-40 Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 Appendix D SNMP Management Information Base MIBs Supported by the SES Controller Table D-16 Port Loading Table Entries (continued) No. Object Type Access Description 18 cwspLoadAvlVcUbr read-only Number of VCs used by UBR service, in the range 0 to 2147483647. 19 cwspLoadCtdCbr read-only Cell transfer delay of CBR service, in the range 0 to 2147483647. 20 cwspLoadCtdRtVbr read-only Cell transfer delay of real-time VBR service, in the range 0 to 2147483647. 21 cwspLoadCtdNrtVbr read-only Cell transfer delay of non-real time VBR service, in the range 0 to 2147483647. 22 cwspLoadCtdAbr read-only Cell transfer delay of ABR service, in the range 0 to 2147483647. 23 cwspLoadCtdUbr read-only Cell transfer delay of UBR service, in the range 0 to 2147483647. 24 cwspLoadCdvCbr read-only Cell delay variation of CBR service, in the range 0 to 2147483647. 25 cwspLoadCdrRtVbr read-only Cell delay variation of real-time VBR service, in the range 0 to 2147483647. 26 cwspLoadCdvNrtVbr read-only Cell delay variation of non-real time VBR service, in the range 0 to 2147483647. 27 cwspLoadCdvAbr read-only Cell delay variation of ABR service, in the range 0 to 2147483647. 28 cwspLoadCdvUbr read-only Cell delay variation of UBR service, in the range 0 to 2147483647. 29 cwspLoadClr0Cbr read-only Cell loss ratio -0 of CBR service. -1 implies N/A. 30 cwspLoadClr0RtVbr read-only Cell loss ratio -0 of CBR service. -1 implies N/A. 31 cwspLoadClr0NrtVbr read-only Cell loss ratio -0 of non-real time VBR service. -1 implies N/A. 32 cwspLoadClr0Abr read-only Cell loss ratio -0 of ABR service. -1 implies N/A. 33 cwspLoadClr0Ubr read-only Cell loss ratio -0 of UBR service. -1 implies N/A. 34 cwspLoadClr01Cbr read-only Cell loss ratio -0 of CBR service. -1 implies N/A. 35 cwspLoadClr01RtVbr read-only Cell loss ratio-1 of real time VBR service. -1 implies N/A. 36 cwspLoadClr01NrtVbr read-only Cell loss ratio-1 of non-real time VBR service. -1 implies N/A. 37 cwspLoadClr01Abr read-only Cell loss ratio -1 of ABR service. -1 implies N/A. 38 cwspLoadClr01Ubr read-only Cell loss ratio-1 of UBR service. -1 implies N/A. 39 cwspLoadMinGurCrCbr read-only Minimum guaranteed cell rate capacity of CBR service, in the range 0 to 2147483647. 40 cwspLoadMinGurCrRtVbr read-only Minimum guaranteed cell rate capacity of real time VBR service, in the range 0 to 2147483647. 41 cwspLoadMinGurCrNrtVbr read-only Minimum guaranteed cell rate capacity of non-real time VBR service, in the range 0 to 2147483647. 42 cwspLoadMinGurCrAbr read-only Minimum guaranteed cell rate capacity of ABR service, in the range 0 to 2147483647. 43 cwspLoadMinGurCrUbr read-only Minimum guaranteed cell rate capacity of UBR service. Cisco SES PNNI Controller Software Configuration Guide Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 D-41 Appendix D SNMP Management Information Base MIBs Supported by the SES Controller cwspConnTrace Collection of objects that provide trace information about SVC/PNNI Connections. • cwspConnTraceAvail • cwspConnTraceCntlTable • cwspConnTraceTable cwspConnTraceAvail Table D-17 Port Connection Trace Availability Entry No. Object Type Access Description 1 cwspConnTraceAvail read-only Number of calls that can be traced concurrently. Depending on the system resource, this object may vary from time to time. NMS should query this object to ensure there is a system resource available before creating a row in the cwspConnTraceCntlTable. cwspConnTraceNextIndex Table D-18 Port Connection Trace If Index Entry No. Object Type Access Description 2 cwspConnTraceNextIndex read-only NMS queries this object to obtain the index value to be used row creation. cwspConnTraceCntlTable Table D-19 Port Connection Trace Control Table Entry No. Object Type 3 cwspConnTraceCntlTable Access Description This Table contains the objects which control the creation of connection trace for the existing SVC call. ConnTraceCntlTable Table D-20 Port Connection Trace Control Table Entries No. Object Type Access Description 1 cwspConnTraceIndex not-accessible This greater than 0 object is the index for a row to create connection trace. 2 cwspConnTraceifIndex read-create Equivalent to ifIndex for the port to trace connection. ifIndex is used as a reference to create a row which represents an existing connection. 3 cwspConnTraceSrcVpi read-create Shows the VPI value of the starting point on this interface in the range 0 to 4095. Cisco SES PNNI Controller Software Configuration Guide D-42 Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 Appendix D SNMP Management Information Base MIBs Supported by the SES Controller Table D-20 Port Connection Trace Control Table Entries (continued) No. Object Type Access Description 4 cwspConnTraceSrcVci read-create Shows The VCI value of the starting point on this interface, in the range 32 - 65535. 0 = SPVP 5 cwspConnTraceType read-create Specifies tracing, as either p2p(1) or p2mp(2), on a p2p or p2mp connection 6 cwspConnTraceCallRef read-only Shows the Call Reference value of the call on this interface. 7 cwspConnTraceLeafRef read-create Shows the value, in the range 0 to 65535, of the Leaf Reference (EndPointReference) of the Call on this interface, this value is used to support p2mp call trace. For p2p call, this value should be set as 0 by NMS. 8 cwspConnTraceDestVpi read-only This object shows the endpoint VPI value of the call on this interface. 9 cwspConnTraceDestVci read-only This object shows the endpoint VCI value of the call on this interface. 10 cwspConnTraceDestCallRef read-only This object shows the endpoint call reference on this interface. 11 cwspConnTraceResultStatus read-only This object shows the result of tracing the call. NMS should get positive result (for example, traceCompleted(2) for this attribute before querying the cwspConnTraceTable. Options are: 12 cwspConnTraceQueryStatus read-create • traceInProgress(1), • traceCompleted(2), • traceIncompleted(3), • traceExceededLength(4), • traceContRefused(5), • traceLackResource(6) This object used to manage rows in this table. However, only CreateAndGo, NotInService, Active, and Destroy are supported. NMS should only set value to be CreateAndGo to startup the trace. To remove a row, NMS set this value to be Destroy. The managed device will either return Active or NotInService. Cisco SES PNNI Controller Software Configuration Guide Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 D-43 Appendix D SNMP Management Information Base MIBs Supported by the SES Controller Port Connection Data Table Table D-21 contains the objects which show the traversed node information in the existing SVC call. Table D-21 Port Connection Data Table No. Object Type Access Description 1 cwspConnTraceEntry not-accessible Along with cwspConnTraceIndex, this object specified an unique entry in the cwspConnTraceTable 2 cwspConnTraceNodeId read-only Octet string representing 22 bytes nodeId in the traced connection 3 cwspConnTraceEgressPortId read-only Represents 4 bytes logical port ID of the traversed node. When 0 is specified, the destination node for the trace is reached. 4 cwspConnTraceEgressVpi read-only Egress port's VPI value for the traced connection. 5 cwspConnTraceEgressVci read-only Egress port's VCI value for the traced connection. 6 cwspConnTraceEgressCallRef read-only Egress port's call reference. 7 cwspConnTraceEgressPhyPortId read-only Egress port's physical port Identifier for the traversed node; if this object is 0 meaning that the destination node for the traced connection has been reached. The meaning for the bytes are: • first byte = flag (used by CLI to decode the rest of bytes) • 2 nd byte = shelf • 3rd & 4th bytes = slot • 5th byte = subslot • 6th & 7th bytes = port • 8th byte= subport Cisco SES PNNI Controller Software Configuration Guide D-44 Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 Appendix D SNMP Management Information Base MIBs Supported by the SES Controller cwspOperationTable The interface operation table contains the runtime negotiated values between platform, PNNI controller, and peer on an interface. Table D-22 Interface Operation Table Entries No Object Type Access Description ‘ cwspOperIlmiEnable read-only Operational state of ILMI 2 cwspOperIfcType read-only Interface type. Options are: 3 cwspOperIfcSide read-only • publicUni(1) • privateUni(2) • iisp(3) • pnni(4) • aini(5) • enni(6) The IME type of the ATM device which is concluded from automatic interface type determination procedure. • userSide(1) • networkSide(2) • symmetric(3) Reference: ATM Forum ILMI 4.0 Section 8.3.4.1 4 cwspOperMaxVPCs read-only Maximum number of switched and permanent VPCs supported. 5 cwspOperMaxVCCs read-only Maximum number of switched and permanent VCCs supported. 6 cwspOperMaxVpiBits read-only Maximum number of active VPI bits on this ATM interface. 7 cwspOperMaxVciBits read-only Maximum number of active VCI bits on this ATM interface. 8 cwspOperUniType read-only ATM device type, either public(1) or private(2). Cisco SES PNNI Controller Software Configuration Guide Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 D-45 Appendix D SNMP Management Information Base MIBs Supported by the SES Controller Table D-22 Interface Operation Table Entries (continued) No Object Type Access Description 9 cwspOperUniVersion read-only Displays current version of the ATM Forum UNI Signaling Specification supported. The values are: • version2point0(1) • version3poing0(2) • version3poing1(3) • version4poing0(4) • unsupported(5) If no value is present, a version of the UNI earlier than 3.1 is supported. If the peer IME value of this object identical, or later, the version corresponding to the local IME value should then be attempted. If the peer IME value of this object is earlier, and supported locally, the local IME should then attempt the version corresponding to the peer IME value. If neither of the above two consideration are present, compatibility of the two IMEs cannot be assumed. 10 cwspOperDeviceType read-only Determines ATM device type. This object is used in automatic ATM Interface-Type determination procedure, such that a correct operational ATM Interface type can be determined. An ATM End System shall take the value of user(1), and an ATM network node shall take the value of node(2). 11 cwspOperIlmiVersion read-only An indication of the latest version of the ATM Forum ILMI Specification that is supported on this ATM Interface. The values are: • unsupported(1) • version4point0(2) If this object is not present, a version of the ILMI earlier than 4.0 is supported. If the peer IME value of this object identical, or later, the version corresponding to the local IME value should then be attempted. If the peer IME value of this object is earlier, and supported locally, the local IME should then attempt the version corresponding to the peer IME value. If neither of the above two consideration are present, compatibility of the two IMEs cannot be assumed. Cisco SES PNNI Controller Software Configuration Guide D-46 Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 Appendix D SNMP Management Information Base MIBs Supported by the SES Controller Table D-22 Interface Operation Table Entries (continued) No Object Type Access Description 12 cwspOperNniSigVersion read-only Indicates the latest version of the ATM Forum PNNI signaling specification that is supported in this ATM interface. The supported versions are: • undsupported(1) • iisp(2) • pnniVersion1point0(3) • enni(4) Note The PNNI routing version is not determined through ILMI. 13 cwspOperMaxSvpcVpi read-only Maximum switched VPC VPI. 14 cwspOperMinSvpcVpi read-only Minimum switched VPC VPI. 15 cwspOperMaxSvccVpi read-only Maximum switched VCC VPI. 16 cwspOperMinSvccVpi read-only Minimum switched VCC VPI. 17 cwspOperMaxSvccVci read-only Maximum switched VCC VCI. 18 cwspOperMinSvccVci read-only Minimum switched VCC VCI. 19 cwspOperAddrPlanSupported read-only The ATM address plan supported on a public UNI. The values are: • both(1) • aesa(2) • e164(3) For all other interfaces, the value is aesa(2). Cisco WAN ATM MIB Objects • cwAtmChanCfgTable • cwAtmChanStateTable • cwAtmChanTestTable Cisco SES PNNI Controller Software Configuration Guide Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 D-47 Appendix D SNMP Management Information Base MIBs Supported by the SES Controller cwAtmChanCfgTable Each entry in the cwAtmChanCfgEntry table corresponds to an endpoint on the PNNI Controller. Table D-23 cwAtmChanCfgTable No. Object Type Access Description Default 1 cwaChanVpi not-accessible The VPI value of a VP or VC connection in range of 0 and 4095. The cwaChanVPcFlag serves to distinguish if this is a VP / VC connection 2 cwaChanVci not-accessible The VCI value of a VC connection in range of 0 and 65535. The cwaChanVPcFlag serves to distinguish if this is a VP / VC connection. For a VPC, the VCI is irrelevant and is set to a value of -2. 3 cwaChanServiceCategory read-create Identifies the service type to which this connection belongs. The service type specified is one among the ATM Forum service types and implicitly determines the configuration for GCRA. 4 cwaChanVpcFlag read-create Identifies if the endpoint is a VP / VC endpoint. When set to true (1) this implies a VP endpoint. 5 cwaChanIdentifier read-only Uniquely identifies a connection within a physical entity (such as a service card). This object can be used as a quick reference index between the network management server and the switch. The range is 0..524287. 6 cwaChanUploadCounter read-only A set of a value of 1: when the row is created for a channel and is incremented whenever there is a configuration change to the row. This counter is used by the NMS to determine if a row in the table had been modified and requires an upload. This function is conventionally achieved by using timestamp. However, in certain implementations, where storage is at a premium, the use of counter rather than a timer tick can be an advantage. For example, a 4-bit counter incremented only during row modification serves the same purpose of a 32-bit timestamp. The range is 0..4294967295. 7 cwachanStatsEnable read-create Limits imposed by software or hardware implementations false(2) could restrict the amount of statistical data that can be maintained in a physical entity (such as a service module). Hence there could be a need to restrict statistics collection to a smaller subset. This object serves the purpose of enabling or disabling statistics collection on a per connection basis. In implementations that do not have such limitations, this object can be set to true(1) for all connections. Cisco SES PNNI Controller Software Configuration Guide D-48 Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 Appendix D SNMP Management Information Base MIBs Supported by the SES Controller Table D-23 cwAtmChanCfgTable (continued) No. Object Type Access Description Default 8 cwaChanCCEnable read-create Serves to enable or disable continuity check (CC) on a connection endpoint. When continuity check is enabled on an endpoint, the endpoint anticipates OAM CC cells from its peer endp0oint. OAM CC cells are sent when the peer endpoint does not have traffic cells to send. If the connection is idle and this endpoint has not received OAM CC cells for a period of 3.5 +/- 0.5 seconds, it declares continuity failure. This object serves to administratively control the CC feature. Typical implementations of this feature may choose to ignore this control or impose other conditions to actually enable CC cell flow. However, if this object is set to false (2), then this feature should be disabled. false(2) 9 cwaChanLocalVpi read-only Identifies the internal VPI assigned to a local endpoint, by the switch. The cwaChanLocalVpi, cwaChanLocalVci and the cwaChanLocalINSAPAddr, form a unique identifier for the connection endpoint in the networking domain. The value is in the range of 0 and 4095. 10 cwaChanLocalVci read-only Identifies the internal VCI assigned to a local endpoint by the switch. The cwaChanLocalVpi, cwaChanLocalVci, and the cwaChanLocalINSAPAddr, form a unique identifier for the connection endpoint in the networking domain. Then value is in the range of 0 and 65535. 11 cwaChanLocalINSAPAddr read-only Identifies the internal NSAP assigned to a local endpoint by the switch. The cwaChanLocalVpi, cwaChanLocalVci, and the cwaChanLocalINSAPAddr, form a unique identifier for the connection endpoint in the networking domain. 12 cwaChanRemoteVpi read-create Identifies the VPI of the peer endpoint. The cwaChanRemoteVpi, cwaChanRemoteVpi, and the cwaChanRemoteNSAPAddr identify the peer endpoint in the networking domain. The value is in the range of 0 and 4095. 13 cwaChanRemoteVci read-create Identifies the VCI of the peer endpoint. The cwaChanRemoteVpi, cwaChanRemoteVpi, and the cwaChanRemoteNSAPAddr, identify the peer endpoint in the networking domain. The value is in the range of 0 and 65535. 14 cwaChanRemoteNSAPAddr read-create Identifies the NSAP of the peer endpoint. The cwaChanRemoteVpi, cwaChanRemoteVpi, and the cwaChanRemoteNSAPAddr identify the peer endpoint in the networking domain. Cisco SES PNNI Controller Software Configuration Guide Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 D-49 Appendix D SNMP Management Information Base MIBs Supported by the SES Controller Table D-23 cwAtmChanCfgTable (continued) No. Object Type Access Description Default 15 cwaChanControllerId read-create This object serves to associate an endpoint with a specific controller. Usually resource partitioning makes the association between a controller and a range of VPI-VCI. There could be switches where hard partitioning of VPI-VCI may not be implemented, in which case this object serves to tie a specific vpi-vci to a controller. The range is 1..255. The default is 2. 16 cwaChanRoutingMastership read-create If set to true(1), identifies this endpoint as the ‘master’ endpoint of the connection. 1 false (2) The networking entity initiates routing of a PVC connection only after a master endpoint is added. Mastership of a PVC cannot be changed, once provisioned, which implies that this object can be set only during row creation. 17 cwaChanMaxCost read-create Used by the routing entity to select a route based on the cost factor. The cost of a route is represented as a number between 1 and 65535. The value of this object represents the maximum cost of the route that this connection could be routed through. The range is 0..4294967295. The default is 'FFFFFFFF'h(4294967295). 100 18 cwaChanReroute read-create Used by the administrator to trigger the rerouting of the connection false (2) • Rerouting takes effect when this object is set to true(1). When set to false(2) rerouting does not occur. • A GET on this object always returns false(2). • If setting cwaChanReroute, other MIB objects should not be SET except for the RowStatus. • Reroute can be triggered only from the master endpoint. Any attempt to trigger reroute from the slave endpoint results in failure of the SET operation. 19 cwaChanFrameDiscard read-create If set to true(1), enables the frame discard feature at the endpoint. 20 cwaChanOperStatus read-only Reflects operational status of an endpoint. • If the connection is not routed or if the endpoint receives AIS/RDI, or if there is a CC failure, this object is SET to OperFail (2) • If the connection is administratively down, this object is SET to adminDown (3) • If normal operations, this object is SET to operOk(1) 21 cwaChanPCR read-create Peak cell rate for the direction from local to remote. The value is in the range 7 to 23000000. 22 cwaChanMCR read-create Maximum cell rate for the direction from local to remote. The value is in the range 7 to 2300000. false (2) Cisco SES PNNI Controller Software Configuration Guide D-50 Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 Appendix D SNMP Management Information Base MIBs Supported by the SES Controller Table D-23 cwAtmChanCfgTable (continued) No. Object Type Access Description 23 cwaChanSCR read-create Sustainable cell rate fro the direction from local to remote. The value is in the range 7 to 2300000. 24 cwaChanCDV read-create Maximum tolerable cell delay variation in the direction from local to remote. Default 1677721 5 A value of 16777215 indicates to the switch that this parameter does not have significance in SPVC call setup. The range is 1..16777215. The default is 'FFFFFF'h(166777215). The unit of this variable is “microseconds”. 25 cwaChanCTD read-create Maximum tolerable network transfer delay in the direction from local to remote. The value is in the range 1 to 65535. The default is 'FFFF'h(65535). The unit of this variable is “milliseconds”. 26 cwaChanMBS read-create Maximum Burst Size used in the direction from local to remote. The value is in the range 1 to 5000000. The unit of this variable is in cells. Reference: ATM Forum Traffic Management Specification Version 4.0 Annex C. 27 cwaChanCDVT read-create Cell delay variation tolerance used in the direction from local to remote. The value is in the range 1 to 4294967295. The default is 4294967295. The unit of this variable is in microseconds. Reference: ATM Forum Traffic Management Specification Version 4.0 Annex C. 28 cwaChanPercentUtil read-create Provides a per-connection control for overbooking bandwidth. Used in conjunction with the VSI interface policy while performing CAC. This is applied for the direction from local to remote. The value is in range 0 to 100. 29 cwaChanRemotePCR read-create Peak cell rate for the direction from remote to local. The value is in range 7 to 23000000. The unit of this variable is in cells per second. 30 cwaChanRemoteMCR read-create Minimum cell rate for the direction from remote to local. The value is in range 7 to 23000000. The unit of this variable is in cells per second. 31 cwaChanRemoteSCR read-create Sustainable cell rate for the direction from remote to local. The value is in range 7 to 23000000. The unit of this variable is in cells per second. 32 cwaChanRemoteCDV read-create Maximum tolerable cell delay variation for the direction from remote to local. The value is in range 1 to 16777215. The unit of this variable is in microseconds. 100 Reference: A value of 16777215 indicates to the switch that this parameter does not have significance in SPVC call setup. Cisco SES PNNI Controller Software Configuration Guide Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 D-51 Appendix D SNMP Management Information Base MIBs Supported by the SES Controller Table D-23 cwAtmChanCfgTable (continued) No. Object Type Access Description Default 33 cwaChanRemoteCTD read-create Maximum tolerable network transfer delay in the direction from remote to local. The value is in range 1 to 65535. The unit of this variable is in milliseconds. The default is 'FFFF'h(65535). 34 cwaChanRemoteMBS read-create Maximum burst size used in the direction from remote to local. The value is in range 1 to 5000000. The unit of this variable is in cells. Reference: ATM Forum Traffic Management Specification Version 4.0 Annex C 35 cwaChanRemoteCDVT read-create Cell delay variation tolerance used in the direction from remote to local. The value is in range 1 to 5000000. The unit of this variable is in cells. The default is FFFFFFFF'h(4294967295). The range is (1..4294967295). Reference: ATM Forum Traffic Management Specification Version 4.0 Annex C. 36 cwaChanRemotePercentUtil read-create Provides a per-connection control for overbooking bandwidth. Used in conjunction with the VSI interface policy while performing CAC. Applied in the direction from remote to local. The value is in range 0 to 100. 37 cwaChanAbrICR read-create Initial cell rate; rate at which a source should send initially after an idle period. This value must not be larger than that configured for PCR. The value is in range 7 to 23000000. 100 Reference: ATM Forum Traffic Management Specification Version 4.0 Section 5.10.2 38 cwaChanAbrADTF read-create Value for ACR decrease time factor, which is the time permitted between sending resource management (RC) cells before the rate is decreased to the initial cell rate (ICR). The value is in the range 1 to 1023, in the unit of 10 milliseconds. Reference: ATM Forum Traffic Management Specification Version 4.0 Section 5.10.2. 39 cwaChanAbrRDF read-create Value for rate decrease factor, which controls the rate decrease that occurs when backward RM-cells with CI set for 1 are received. Larger values lead to faster rate decreases. Reference: ATM Forum Traffic Management Specification Version 4.0 Section 5.10.2. Cisco SES PNNI Controller Software Configuration Guide D-52 Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 Appendix D SNMP Management Information Base MIBs Supported by the SES Controller Table D-23 cwAtmChanCfgTable (continued) No. Object Type Access Description 40 cwaChanAbrRIF read-create Value for rate increase factor, which controls the rate increase that occurs when a backward RM-cell is received with CI set for 1, and NI set for 0. Default Larger values lead to faster rate increase. Reference: ATM Forum Traffic Management Specification Version 4.0 Section 5.10.2. 41 cwaChanAbrNRM read-create Maximum number of cells a source may send for each forward RM-cell. Options are: • nrm2(1) • nrm4(2) • nrm8(3) • nrm16(4) • nrm32(5) • nrm64(6) • nrm128(7) • nrm256(8) Reference: ATM Forum Traffic Management Specification Version 4.0 Section 5.10.2. 42 cwaChanAbrTRM read-create Number of milliseconds to represent upper bound on the time between forward RM-cells for an active source. Options are: • trm0point78125(1) • trm1point5625(2) • trm3point125(3) • trm6point25(4) • trm12point5(5) • trm25(6) • trm50(7) • trm100(8) Reference: ATM Forum Traffic Management Specification Version 4.0 Section 5.10.2. Cisco SES PNNI Controller Software Configuration Guide Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 D-53 Appendix D SNMP Management Information Base MIBs Supported by the SES Controller Table D-23 cwAtmChanCfgTable (continued) No. Object Type Access Description Default 43 cwaChanAbrCDF read-create Cutoff decrease factor, which controls the rate decrease associated with lost of delayed backward RM cells. Larger values result in faster rate decrease. Options are: • cdf0(1) • cdfOneOver64(2) • cdfOneOver32(3) • cdfOneOver16(4) • cdfOneOver8(5) • cdfOneOver4(6) • cdfOneOver2(7) • cdfOne(8) Reference: ATM Forum Traffic Management Specification Version 4.0 Section 5.10.2. 44 cwaChanAbrFRTT read-create Number of milliseconds to represent fixed round trip time, which is the sum of the fixed propagation delays from the source to a destination network. The range is 0..16700000. The unit is in microseconds. Reference: ATM Forum Traffic Management Specification Version 4.0 Section 5.10.2. 45 cwaChandAbrTBE read-create Transient buffer exposes, which is a negotiated number of cells to be limited over the network, between the time at which the source transmits during startup periods, and before the first RM cell returns. The range is 0..16777215. Reference: ATM Forum Traffic Management Specification Version 4.0 Section 5.10.2. 46 cwaChanAbrERS read-create Configuration of an endpoint for explicit rate stamping. 47 cwaChanAbrVSVDEnable read-create ABR connections require close loop control to limit the transmission rate, depending on the network bandwidth. Now this close loop can be end-to-end or between intermediate network segments. When terminating on ABR VPL, the endpoint needs to act like a Virtual Destination to the incoming traffic and generate backward RM cells. While doing this, it also needs to act as a virtual source and forward RM cells to the real destination. This is a feature that can be enabled or disabled under the control of this object. none When set to true(1), this feature is enabled. Cisco SES PNNI Controller Software Configuration Guide D-54 Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 Appendix D SNMP Management Information Base MIBs Supported by the SES Controller Table D-23 cwAtmChanCfgTable (continued) No. Object Type Access Description 48 cwaChanRowStatus read-create Used to create, modify, or delete an entry in the ciscoWanAtmChanTable. • A row may be created using the ‘CreateAndGo’ option. When the row is successfully create, the RowStatus would be set to ‘active’ by the agent. • A row may be deleted by setting the RowStatus to ‘destroy.’ • When there is a need to administratively down the connection, the RowStatus could be set to ‘notInService.’ When the switch completes the ‘down’ operation, the value of this object would be ‘notInService.’ • The connection can be made active again, by setting this object to ‘active.’ • Administrative status control is limited to the master endpoint only. The switch would reject any request for admin state change on the slave endpoint. • Other options such as ‘CreateAndWait’ will not be used.’ Default 49 cwaChanIntAbrVSVD read-create This object is used for enabling/disabling VSVD internal to a segment i.e the closed loop control is in effect between the two provisioned endpoints of the SPVC.(This object is not supported at this time.) 50 waChanExtAbrVSVD read-create This object is used for enabling/disabling VSVD external to the segment which hosts the two endpoints of the SPVC i.e the closed loop control will be in effect outside the segment either towards a CPE or towards another segment.(This object is not supported at this time.) 51 cwaChanAisIWCapability read-create This object is used for achieving OAM inter-operability between switches that cannot generate/detect segment AIS cells. This attribute enables the newer generation of switches to understand the OAM capability of the peer endpoint and accordingly generate/detect seg/e2e AIS as required. The value of this attribute is decided during provisioning time by network management. The values are: e2eAisCapable(1) and segAisCapable(2). e2eAisC apable(1 ) 52 cwaChanCLR read-create Encoded value representing the maximum tolerable cell loss ratio in the direction local -> remote. The actual CLR value is derived as the negative logarithm of this value. The range is 1..15. 6 53 cwaChanRemoteCLR read-create Encoded value representing the maximum tolerable cell loss ratio in the direction remote -> local. The actual CLR value is derived as the negative logarithm of this value. The range is (1..100000000). The units are in microseconds. 6 Cisco SES PNNI Controller Software Configuration Guide Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 D-55 Appendix D SNMP Management Information Base MIBs Supported by the SES Controller CwAtmChanStateTable Each entry in the cwAtmChanStateTable corresponds to a connection endpoint on the PNNI Controller. Table D-24 cwAtmChanStateEntry Objects No. Object Type Access Description 1 cwAtmChanAlarmState read-only Defines alarms associated with an endpoint. 2 cwaChanEgressXmtState read-only State of the transmit portion of the endpoint in the egress direction. 3 cwaChanEgressRcvState read-only The state of the receive portion of the endpoint in the egress direction. 4 cwaChanIngressXmtState read-only The state of the transmit portion of the endpoint in the ingress direction. 5 cwaChanIngressRcvState read-only The state of the receive portion of the endpoint in the ingress direction CwAtmChanTestTable Each entry in the cwAtmChanTextTable corresponds to a connection endpoint on the PNNI Controller. Table D-25 cwAtmChanTestEntry Objects No. Object Type Access Description Default 1 cwAtmChanTestType read-create This object sets a particular channel in one of three loopback types: • chanLpbk: a disruptive loopback performed within the PNNI Controller, which loops data from the CPE back to the CPE. • camLpbk: a non-disruptive loopback performed using OAM loopback cells sent toward the remote endpoint and looped back at the remote endpoint. • cpeLpbk: a non-disruptive loopback performed using OAM loopback cells that are sent toward the CPE and logged back by the CPE. notLpbk(1) Attempting to set a channel in loopback during a test is progress results in failure of the SET operation. 2 cwaChanTestDir read-create Specifies the direction in which loopback should be effected: * For destructive loopback, this takes values external (1) and internal (2). * For non-destructive loopback, this takes values forward (3) and reverse (4). * When cwaChanTestType is noLpbk (1), this object is ignored. Cisco SES PNNI Controller Software Configuration Guide D-56 Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 Appendix D SNMP Management Information Base MIBs Supported by the SES Controller Table D-25 cwAtmChanTestEntry Objects (continued) No. Object Type Access Description Default 3 cwaChanTestIterations read-create Specifies the number of times that a test needs to be performed. This object is applicable only to camLpbk and cpeLpbk types. A GET performed on this object results in return of the number of successful iterations of the loopback test. 4 cwaChanTestState read-only Reflects the status of the last OAM loopback test performed on a connection. Where a loopback is in progress, this object displays the type of loopback in effect. Removal of chanLpbk results in SET to notInLpbk. 5 cwaChanTestRoundTripD elay read-create Returns the round trip delay in milliseconds, measured during the last OAM loopback test. 1 noStatus(1) The value is in range 1 to 100000000. The unit of this variable is in microseconds. Cisco SES PNNI Controller Software Configuration Guide Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 D-57 Appendix D SNMP Management Information Base MIBs Supported by the SES Controller Cisco SES PNNI Controller Software Configuration Guide D-58 Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 G L O S S A R Y A ABR Available Bit Rate. See ATM Service Categories AESA ATM End Station Address. The 19-octet address that uniquely identifies each logical node. Annex G A bidirectional protocol, defined in Recommendation Q.2931, used for monitoring the status of connections across an UNI interface. The SES PNNI controller uses the Annex G protocol to pass connection status information between a itself and the BPX 8600 switch. ATM Service Categories 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. CBR: Constant Bit Rate is used by connection that request a static amount of bandwidth, for continuous availability during the connection lifetime. The amount of bandwidth is characterized PCR. 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. rtVBR: Real-time-variable-bit-rate is intended for real-time applications that require tightly constrained delay and delay variation (such as voice and video applications). rtVBR is characterized by PCR, SCR, and MBS. UBR: Unspecified Bit Rate is intended for non-real-time application, such as those that do not require tightly constrained delay and delay variation. Traffic in the UBR class is not guaranteed any particular throughput or delay performance. In this regard, UBR is similar to ‘traditional’ IP service. B BCC The switch control card in the BPX is the Broadband Control Card, which has a 68040 processor. BPX The WAN Business Unit’s high-end ATM switch is the Broadband Packet Exchange (BPX). The BPX is a carrier-quality switch, with trunk and CPU hot standby redundancy. BXM The Broadband Switch Module (BXM) cards are ATM port cards for the BPX switch, which use the Monarch chipset. Cisco SES PNNI Controller Software Configuration Guide Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 1 Glossary C CBR Constant Bit Rate. See also ATM Service Categories. Class of Service (CoS) Buffer A buffer or queue which serves connections with similar QoS requirements. A component of a Service Class Template which contains Class of Service Buffer configurations Class of Service (CoS) Buffer indexed by CoSB number. Note: A Qbin is a platform-specific (BXM in this case) instance of the more Descriptor Template general Class of Service (CoS) Buffer. CommBus The CommBus is the BPX’s internal messaging bus. 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. The agent establishes one community for each desired combination of authentication, access control, and proxy characteristics. Each community is given a unique (within this agent) community name, and the management stations within that community are provided with and must employ the community name in all get and set operations. The agent may establish a number of communities, with overlapping management station membership. CosB See Class of Service (CoS) Buffer. D DCC Data Country Code. DTL Designated Transit List. E Enterprise MIB A MIB module defined in the enterprise-specific portion of the Internet management space. Cisco SES PNNI Controller Software Configuration Guide 2 Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 Glossary F Feeder A Feeder is a small switch which acts as an extension shelf, typically with lower-bandwidth interfaces, for a larger switch. The larger switch is referred to as the Routing Node for the Feeder(s). I ICD International Code Designator. IISP Interim Inter-switch Protocol. ILMI Integrated Local Management Interface. 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. LGN Logical Group Node. Logical Interface Each physical interface and every virtual trunk endpoint on a platform is represented to the VSI Controllers as a different Logical Interface with partitions, and other VSI configuration. Logical Interface numbers are 32-bit with a format which is, in general, known only to the platform. Logical Link Either a physical link or a VPC PVC across another ATM network. Logical links are referred to as horizontal links (if connecting logical nodes within a pair) or outside links (if connecting peer groups). Cisco SES PNNI Controller Software Configuration Guide Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 3 Glossary M Managed device A device containing a network management agent implementation. C5K is a managed device MBS Maximum Burst Size. MIB Management Information Base, a structured set of data variables, called objects, in which each variable represents some resource to be managed. MIB-II Internet-standard MIB, RFC 1213 Monarch The ATM interface chipset used on recent WANBU port cards. N NSAP Network Service Access Point. NIC Network Interface Card. An ATM card for a host or router is an ATM NIC. nrtVBR Non-real-time-variable-bit-rate. See also ATM Service Categories. O Object In the context of SNMP, a data variable that represents some resource or other aspect of a managed device Object type Defines a particular kind of managed object. The definition of an object type is therefore a syntactic description. P PCR Peak Cell Rate PGL Peer Group Node. PNNI Private Network-to-Network Interface PNNI RCC PNNI routing control channel. See RCC. Port The VSI makes no distinction between trunk ports and end-point ports. “Port” is synonymous with “Interface”. Cisco SES PNNI Controller Software Configuration Guide 4 Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 Glossary PTSE PNNI Topology State Element. PXM Processor Switch Module. The processor card used in the MGX 8800 series switches and in the Service Expansion Shelf. In the SES PNNI controller application, described in this manual, only PXMs (active and standby), running PNNI and ATM SVC software, are installed in the SES. There are no service modules used. Q Qbin A Qbin is a platform-specific (BXM in this case) instance of the more general Class of Service Buffer (or CosB). R RCC Routing control channel. A VCC used for the exchange of PNNI routing protocol messages. RFC Request For Comment. Routing Node In tiered networks terminology, a routing node is a larger switch to which one or more feeders or SES PNNI Controllers is attached. rtVBR Real-time-variable-bit-rate. See also ATM Service Categories. Cisco SES PNNI Controller Software Configuration Guide Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 5 Glossary S Service Class (aka Service Type, or Service Category) A concept for grouping connections that share a common set of traffic characteristics and QoS requirements. Service Class database The collection of data items which support the Service Class Template concept, and implemented on a per-VI basis on the BXM. These items include a copy of the specific Service Class Template selected for a VI, as well as additional data as required. Service Class Template (SCT) A set of data structures which map VSI Service Types to sets of pre-configured VC and Qbin parameters. Consists of two sub-components - a VC Descriptor Template and a Class of Service Buffer Descriptor Template. Service Expansion Shelf A flexible 7-slot chassis which can be outfitted with MGX 8800 modules for a variety of applications. As a SES PNNI controller, the SES contains only two PXM modules running PNNI and ATM SVC software, and no service modules; it acts as a virtual switch interface controller to control the BPX switch for PNNI networking and ATM SVCs. SES PNNI Controller A Service Expansion Shelf outfitted with two Processor Switch Modules (PXMs) running PNNI and ATM SVC software. In this application, the PBX SES PNNI Controller is attached to and controls the BPX switch to provide PNNI networking and ATM SVCs. SCR Sustainable Cell Rate. SNMP Simple Network Management Protocol SPVC Smart/Soft Permanent Virtual Circuit. As related to ATM, either of two kinds of SPVCs: smart permanent virtual path connections (SPVPCs) and smart permanent virtual channel connections (SPVCCs). SVC Switched Virtual Circuit. U UBR Unspecified Bit Rate. See also ATM Service Categories. UNI User-to-Network Interface. Cisco SES PNNI Controller Software Configuration Guide 6 Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 Glossary V Variable Binding (Varbind) A pairing of an object instance name and associated value in an SNMP MIB. 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 2 28 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. VC Descriptor Template A component of a Service Class Template which contains platform-specific VC configurations which are indexed primarily by Service Type. Together with a Class of Service Buffer Descriptor Template, it defines a Service Class Template. VCI Each VC within a specific Virtual Path on a link has a unique Virtual Channel Identifier, which is a 16-bit number (see also VPCI). Virtual Trunks A Virtual Trunk is a Virtual Path Connection which appears to VSI masters as an ordinary trunk (except that the trunk supports 64k VCs at most). In a VSI Platform, a Virtual Trunk end-point has its own Logical Interface. VP, VPC, VPI A Virtual Path is a ‘bundle’ of 2 16 Virtual Connections with the same Virtual Path Identifier; for example, the first 12 bits of the VPCI. Most ATM switches can switch VPs using only a single cross-connect (instead of up to 216). An end-to-end sequence of VPs cross-connected at the intermediate switches is a Virtual Path Connection. VPCI Each VC on a link has a unique Virtual Path and Channel Identifier, which is a 28-bit number. The VPCI consists of a 12-bit VPI concatenated with a 16-bit VCI. VSI Virtual Switch Interface: this is a common control interface to all WANBU switches, which is implemented first on the BPX. It will be implemented on other switches, both within Cisco and on switches belonging to Cisco’s Partner. It embodies both connection management and switch configuration discovery capabilities. VSI Controller A controller, such as a PNNI SVC Controller, Portable AutoRoute or Tag Switch Controller, which controls a switch using the VSI. VSI Master A VSI Master process implementing the master side of the VSI protocol in a VSI Controller. Sometimes the whole VSI Controller might be referred to as a ‘VSI Master’, but this is not strictly correct. VSI Platform A VSI Platform is a switch with one or more VSI Slaves allowing connections to be set up using the VSI. VSI Slave A VSI Slave process implementing the slave side of the VSI protocol within a VSI Platform. Sometimes a whole VSI Platform might be referred to as a ‘VSI Slave’, but this is not strictly correct. Cisco SES PNNI Controller Software Configuration Guide Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 7 Glossary VSI2 Virtual Switch Interface, Protocol Version 2: this is revision 2 of a proposed common control interface to all WANBU switches. It embodies both connection management and switch configuration discovery capabilities. VSI Master i. A device which controls a VSI switch, e.g. a VSI Tag Switch Controller. ii. A process implementing the master side of the VSI protocol. VSI Slave i. A switch (in the “Single Slave model”) or a port card (in the “Multiple Slave Model”) which implements the VSI. ii. A process implementing the slave side of the VSI protocol. Cisco SES PNNI Controller Software Configuration Guide 8 Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 I N D E X ATM addresses configuration worksheets audible alarm indicator A 1-10 6-3 audience access levels changing for manual 2-11, 2-12 5-4 privileges 2-11 GROUP1 B 2-12 GROUP2 toGR0UP5 active card state 2-12 addcon command 2-26 minimum requirements 3-22, 3-24 functionality configuration worksheets addtrapmgr command adduser command 1-10 2-22 2-12 1-5 bootChange command boot IP address 2-15 1-12, 2-14 BPX 8620 description alarm cut-off (ACO) 1-4 BPX SES node 6-3 switch 1-5 BCC cards 3-34, 3-38 address architecture 6-3 alarms 1-1 Broadband Controller Card (BCC) displaying Minimum requirements card alarms 6-5 node alarms 6-4 slot alarms Xbar alarms supported interfaces bye command 6-6 6-1 switches ANYUSER 1-4 2-6 6-6 PXM LEDs 1-4 BXM card 6-6 switching alarms 1-5 Broadband Switch Module (BXM) 6-4 environment arbiter back cards BCC 2-9 addaddr command LED xvii C cards 6-1 2-12 1-5 alarms, displaying 6-4 Broadband Controller Card (BCC) minimum requirements 1-5 Broadband Switch Module (BXM) 1-4 Cisco SES PNNI Controller Software Configuration Guide Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 IN-1 Index PXM LEDs states 6-1 standby 2-14 cnfuser command 2-5 cc command 2-14 2-22 5-5 command entry 2-5 types and locations guidelines 2-26 2-7 command line interface 2-7 See CLI cd command commitrev command A-8 CISCO_GP (Cisco user group) 2-11 Cisco user group clearing 5-3 collecting information password, resetting ending a session 5-6 See CISCO_GP CiscoView Cisco WAN Manager (CWM) Cisco Wan Manager (CWM) xvii, 1-5 1-9 CLI overview 1-7 restoring 5-3 saving 1-8 2-6 hardware worksheet 1-9 2-24 5-1 user access introduction A-15 configuration 2-11 CISCO_GP (Cisco user group) access levels 2-10 configuration, quickstart 1-9 session starting over LAN clidbxlevel command 2-20 SPVCs and SPVPs 3-7 controller 2-8 clock sources BITS clocks, configuring planning cnftmzn command cnftrapip command 2-5 initialized runtime 2-14 cnftmzngmt command 2-5 active cnftime command 2-14 PNNI, configuring for 2-14 controller,configuration 2-14 copy command 1-9 clrallcnf command runtime 5-3 A-8 clrcnf command 5-3 critical alarm LED cnfabr command 3-37 CR LED cnfabrtparmdft command 3-37 cnfaddrreg command 3-24 cnfcdvtdft command 3-37 cnfdate command 2-13 cnfmbsdft command cnfname command 3-36 2-13 cnfpasswd command 6-3 crosspoint switch matrix data ports, low-speed DC-A 6-3 6-3 3-37 DC-B cnfpnportsig command 3-28 del command A-8 deleting users 5-5 2-23 cnfspvcprfx command 1-5 date, setting and viewing 5-4 2-21 1-5 D cnfpnni-intf command cnfsnmp command 6-3 deluser command 2-13 5-5 Cisco SES PNNI Controller Software Configuration Guide IN-2 Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 Index directories log files F 6-6 names case sensitive PXM disk IP address runtime 5-1 browsing 1-12, 2-14 dnpnport command A-8 commands 3-27 A-8 File Transfer Protocol 1-7 dspatmaddr command dspcd command See FTP 3-23, 3-25 dspcdalms command firmware 6-4 See software 2-25 dspcds command 2-24 front cards dspcon command 3-39 FTP dspdate command 2-13 dspenvalms command dsplog command 2-18 G Guidelines 6-6 dspndalms command dsppnport command 3-30 H 3-29 dsppnports command 3-27 hardware configuration worksheet A-13, A-14, A-15, A-16 dspslotalms command dspsnmp command 6-6 HIST LED dspswalms command 6-3 history LED 6-3 2-21 I 6-6 2-12 IISP In 1-4 1-4 initialized card state E IP addres ending a session 2-6 exit command 1-12 plan, creating environmental alarms, displaying 2-9 IP address 6-3 Ethernet LAN port 2-24 2-23 dspspvcprfx command dspusers command 1-12 6-4 dsppnni-link command dsprevs command A-9 6-5 6-6 dsplogs command 2-26 runtime service dspipif lnPci0 command ENET LED A-8 file system A-9 saved configurations DSL filenames, case sensitive A-8 6-5 1-5 2-6 1-12 ipifconfig command maintenance port 2-19 ipifconfig lnPci0 command IP routing table 2-18 2-18, 2-20 Cisco SES PNNI Controller Software Configuration Guide Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 IN-3 Index Network-to-Network Interface (NNI) L NNI LAN 2 connector, disabled LAN IP address LED 2-17 1-4 1-4 node 1-12 alarms, displaying 6-3 node IP address LED, CNTRLR (controller ) port LED 6-4 2-14 6-2 ll command runtime O A-8 loadrev command A-13 options 1-12 log files directory 6-6 displaying information log out, automatic P 6-6 2-5 passwords ls command runtime changing for other users A-8 changing your own length 2-13 2-12 resetting M 5-4 5-6 permanent virtual circuit major alarm LED 6-3 See PVC management ports, ATM overview 1-9 selecting the signaling protocol SNMP configuration minor alarm LED MJ LED 2-22 Private Network-to-Network Interface (PNNI) 6-3 privileges 6-3 MN LED 3-27 2-11, 2-12 privileges, users 6-3 1-7, 2-14 2-11 prompt switch PVC N 2-4 3-7 pwd command name runtime configuring the switch name 2-13 PXM network clock sources BITS sources, configuring planning 2-14 1-9 Network congestion switches 6-1 PXM card 1-2 alarms 1-4 network management overview 1-9 SNMP configuration 2-22 Network Management System (NMS) Cisco WAN Manager A-8 6-4 back card 1-3 card types 2-26 front card 1-3 software downgrades A-6 1-5 1-5 Cisco SES PNNI Controller Software Configuration Guide IN-4 Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 Index SNMP Q configuration quickstart configuration 2-22 soft permanent virtual circuits general switch features 2-1 software downgrades See SPVC A-6 software locating updates PXM directory R A-9 A-9 switch, copying files reboot command runtime A-10 upgrade, committing to rename command runtime A-14 SPVC A-8 restoreallcnf command routeAdd command 2-18, 2-20 2-18, 2-20 routeNetAdd command routeShow command 3-7 configuring master side 3-38 2-21 slave, configuring 2-18, 2-20 3-34 SPVP 2-18, 2-20 2-18, 2-20 routing technologies configuration, quickstart 3-7 configuring master side 3-38 node prefix 1-7 runrev command 3-34 configuration, quickstart node prefix 2-18, 2-20 routestatShow command routing table, IP configuration 5-4 routeDelete command PNNI A-9 2-21 slave, configuring A-14 standby card state 3-34 2-9 static ATM addresses S adding saveallcnf command SERVICE_GP Stratum3 system clocking 5-2 default username and password 2-6 superuser user group See SERVICE_GP See SUPER_GP SES controller configuration data configuration tasks switching alarms, displaying 1-8 switch prompt 1-2 session termination, automatic xviii 2-5 Simple Network Management Protocol (SNMP) configuration sysDiskCfgCreate command A-16 sysFlashBootBurn command A-10 sysPxmRemove command A-2, A-3 6-3 sysVersionShow command 1-9 2-13 2-4 system status LED 1-9 slot alarms, displaying 6-6 switch name, setting and viewing 1-7 SES controller manual organization manager 1-5 SUPER_GP 2-11 service user group description 3-23 A-16 6-6 Cisco SES PNNI Controller Software Configuration Guide Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002 IN-5 Index T X Telnet Xbar alarms, displaying client program 6-6 2-20 starting CLI session over LAN time, setting and viewing timeout command 2-20 2-13 2-5 topologies DSL aggregation 1-7 tstdelay command 3-29 U UNI 1-4 uppnport command 3-29 user access, configuration 2-10 users access levels, changing adding deleting 5-4 2-11 5-5 resetting user cisco password User-to-Network Interface (UNI) 5-6 1-4 port Address limit 1-4 V version file A-16 W whoami command runtime 2-13, A-8 worksheets hardware configuration port address 2-24 1-11 Cisco SES PNNI Controller Software Configuration Guide IN-6 Release 1.1, Part Number 78-13539-01 Rev. C0, January 2002