Cisco SES PNNI Controller Software
Configuration Guide
Release 1
March 2001
Corporate Headquarters
Cisco Systems, Inc.
170 West Tasman Drive
San Jose, CA 95134-1706
USA
http://www.cisco.com
Tel: 408 526-4000
800 553-NETS (6387)
Fax: 408 526-4100
Customer Order Number: DOC-786123=
Text Part Number: 78-6123-05
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 ORIMPLIED,
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, CCDA, CCDE, CCDP, CCIE, CCNA, CCNP, CCSI, CD-PAC, CiscoLink, the Cisco NetWorks logo, the Cisco
Powered Network logo, Cisco Systems Networking Academy, the Cisco Systems Networking Academy logo, Fast Step, Follow Me Browsing, FormS hare,
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, PIX, 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, Cisco, the Cisco Certified Internetwork Expert logo,
Cisco IOS, the Cisco IOS logo, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Enterprise/Solver, EtherChannel, EtherSwitch, FastHub,
FastSwitch, IOS, IP/TV, LightStream, MICA, Network Registrar, Post-Routing, Pre-Routing, Registrar, StrataView Plus, Stratm, SwitchProbe, TeleRouter,
and VCO are registered trademarks of Cisco Systems, Inc. or its affiliates in the U.S. and certain other countries.
All other brands, names, or 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. (0102R)
Cisco SES PNNI Controller Software Configuration Guide
Copyright © 2001, Cisco Systems, Inc.
All rights reserved.
C O N T E N T S
About This Manual
Objectives
Audience
xvii
xvii
xvii
Organization
xviii
Related Documentation
xviii
Cisco SES PNNI Controller Release 1 Documentation
Cisco WAN Manager Release 10 Documentation
xviii
xix
WAN CiscoView Release 3 for BPX SES PNNI Controller, Release 1
Conventions
xix
Obtaining Documentation
World Wide Web
xx
xx
Documentation CD-ROM
xx
Ordering Documentation
xxi
Documentation Feedback
xxi
Obtaining Technical Assistance
Cisco.com
xxi
xxi
Technical Assistance Center
xxii
Contacting TAC by Using the Cisco TAC Website
Contacting TAC by Telephone
C H AP TER
1
SES PNNI Controller Overview
SES PNNI Node Components
SES PNNI Controller
BPX 8620 Switch
1-1
1-1
1-2
1-2
1-4
Broadband Switch Module
1-4
Broadband Controller Card
1-5
SES/BPX Interfaces
1-5
System and Network Management
Cisco WAN Manager
Features
xxii
xxii
Processor Switch Module (PXM)
CiscoView
xix
1-7
1-7
1-8
1-9
Cisco SES PNNI Controller Software Configuration Guide
Release 1, Part Number 78-6123-05 Rev. A0, March 2001
iii
Contents
Features
1-9
Command Line Interface
1-10
PNNI Routing and ATM Switched Virtual Circuits
ATM Routing and Signaling
1-11
Topology State Routing
1-11
PNNI Signaling
1-11
Interim Inter-Switch Protocol Routing
ILMI
1-10
1-11
1-11
Redundant SES PNNI Controllers
1-12
Automatic Protection Switching
Y-Cable Redundancy
1-12
1-13
SES PNNI Node Software Architecture
PXM Software
1-13
1-14
Control Point Software
PNNI and SVC Software
1-14
1-15
PNNI and SVC Routing Software
Platform Software
1-17
Virtual Switch Interface Protocol
VSI Master and Slaves
Resource Partitioning
1-18
1-19
1-20
Service Class Templates
Qbin Templates
AutoRoute and PNNI
1-17
1-18
BXM Resources
System Templates
1-17
1-20
1-21
1-21
SVC with PNNI Routing
1-22
SVC with Mixed PNNI and IISP Networks
1-22
PNNI and AutoRoute Co-existence on the Network
User Interfaces and Network Management
1-24
Configuration and Network Management Tools
Provisioning Data Saving
System Error Log
SNMP
1-25
1-25
1-26
Real Time Cell Statistics and Call Statistics
Event Log
1-23
1-26
1-26
1-26
Cisco SES PNNI Controller Software Configuration Guide
iv
Release 1, Part Number 78-6123-05 Rev. A0, March 2001
Contents
SNMP Error Log
1-26
Trap/Alarm Log
1-26
Auto Configuration
C H AP TER
2
1-26
Redundancy and Serviceability
PXM Redundancy
2-1
2-1
Platform Redundancy
PNNI Redundancy
2-1
2-2
Call Redundancy
2-3
Provisioning Redundancy and Persistency
SES Uplink Redundancy
BXM Redundancy
2-3
2-4
Initial Data Transfer (Standby Card Retrieval)
Redundancy Procedures
System Call Redundancy
2-7
2-7
2-8
SES PNNI Controller Switch-over
BPX BCC Switchover
C H AP TER
3
Getting Started
2-6
2-6
System Availability and Switch Over
Switch Over
2-3
2-8
2-9
3-1
Configuration Quickstart
3-1
Establishing and Ending a CLI Management Session
3-2
Starting a CLI Session with a Directly-Attached Terminal
Configuring IP Connectivity on the SES
3-3
3-4
Preparing for IP Communications through the PXM LAN Port
Preparing for IP Communications through the Dial-Up Interface
Start a CLI Telnet Session from a LAN Workstation
Entering Commands at the Switch Prompt
Getting Help for Commands
3-7
3-8
3-9
3-10
Configuring Administrator Access
Adding Users
3-5
3-6
Start a Dial-Up CLI Telnet Session from a Workstation
Ending a CLI Management Session
3-4
3-10
3-11
Changing User Passwords with cnfpasswd
3-12
Changing User Access Levels and Passwords with cnfuser
3-13
Cisco SES PNNI Controller Software Configuration Guide
Release 1, Part Number 78-6123-05 Rev. A0, March 2001
v
Contents
Deleting Users
3-14
Setting and Viewing the Switch Name
3-14
Viewing and Setting the Switch Date and Time
Verifying the Hardware Configuration
Managing Redundant Cards
3-14
3-15
3-19
Displaying Redundancy Status
3-19
Switching Between Redundant PXM Cards
3-20
Managing Firmware Version Levels for Cards
Verifying Card Firmware Version Levels
3-20
3-21
Determining the Firmware Version Number from Filenames
Setting the Firmware Version for a Card
Managing Network Clock Sources
3-24
Configuring for Network Management
4
3-24
3-25
Restoring a Saved Configuration
C H AP TER
3-23
3-23
Configuring the PNNI Controller
Saving a Configuration
3-26
SES PNNI Controller Setup and Initial Configuration
SES PNNI Controller Interfaces
PXM Control Port
PXM LAN Port
3-21
4-1
4-2
4-2
4-3
PXM Maintenance Port
4-3
Attach the Interfaces at the BPX and the PNNI Controller
Perform Initial Configuration Tasks at the PNNI Controller
4-4
4-5
Connect a Terminal to the PNNI Controller and Start the CLI
PNNI Controller Command Line Interface Overview
Bring Up the SES PXM Card
4-5
4-6
Check PXM Front Card/Back Card and BXM
Boot Up PXM
4-5
4-6
4-7
Configure the IP Address
4-7
Assign One IP Address for both the Disk IP and Boot IP
4-7
Assign Two Different IP Addresses for the Disk IP and the Boot IP
Update Backup Boot File and Runtime Controller Image
Prepare to Install the Backup Boot File
Install the Backup Boot
Install the Runtime Image
4-8
4-10
4-10
4-12
4-12
Cisco SES PNNI Controller Software Configuration Guide
vi
Release 1, Part Number 78-6123-05 Rev. A0, March 2001
Contents
Configure SES PNNI Controller Shelf Parameters
Bring Up the SES PNNI Controller
4-16
Configure SES PNNI Redundancy
4-17
OC-3 Y-cable redundancy
4-17
DS-3/E3 Y cable redundancy
APS Redundancy
C H AP TER
5
4-14
4-18
4-19
Configuring ATM SVCs, PNNI Routing, and SPVCs
UNI Configuration
5-1
5-2
AutoConfigure a UNI Port
5-2
Modifying Port Parameters After AutoConfiguration
5-4
Pre-configuring a UNI Port with AutoConfiguration
5-5
Configuring a Port without AutoConfiguration and ILMI
NNI Trunk Configuration
5-6
5-7
AutoConfigure an NNI Trunk
5-7
Pre-configuring a NNI Trunk with AutoConfiguration
Configuring Virtual Trunk on a BXM Port
Configure the BXM Qbin
5-9
5-10
5-11
Qbin Dependencies
5-11
Enable VSI ILMI Functionality
5-12
Enable VSI ILMI Functionality on Line (Port) Interfaces
5-12
Enable VSI ILMI Functionality on Physical Trunk Interfaces
Enable VSI ILMI Functionality on Virtual Trunk Interfaces
View VSI ILMI Functionality on Interfaces
Configuring PNNI
5-13
5-13
5-13
Configure the BPX PNNI Node
5-15
Set Peer Group Leader Parameters
Set Timers and Thresholds
Set SVCC-Based Timers
Set Routing Policies
5-16
5-16
5-17
Configure Summary Address(es)
5-18
5-18
Configure PNNI Interfaces
5-19
Set Locally Reachable Address(es)
Show PNNI Link Hello Protocol
Setting Up SVCs
5-12
5-20
5-21
5-22
Set up an SVC without ILMI Address Registration
5-22
Cisco SES PNNI Controller Software Configuration Guide
Release 1, Part Number 78-6123-05 Rev. A0, March 2001
vii
Contents
Set up an SVC with ILMI Address Registration
Set Up Address Filtering
5-23
5-23
Configure an Address Filter To Reject a Specific Called Party on the Ingress
5-23
Configure an Address Filter To Reject a Specific Calling Party on the Ingress
5-25
Configure an Address Filter To Reject a Specific Calling Party and Called Party on the Ingress
5-26
Configure an Ingress Filter to Reject All Calls Whose Calling Party Begins With a Specific Set Of
Digits 5-27
Configure an Ingress Filter to Reject all Calls Whose Calling Party Ends with a Specific Set Of
Digits 5-28
Delete An Address Entry in a Filter
5-28
Disable Address Filtering Functionality on the Ingress
Destroy an Existing Filter
5-29
5-30
Create a filter to Reject All Calls Whose Calling Party Address Does Not Match Any Address Entry
in the Filter 5-30
Enable Egress Address Filtering
5-31
Disable Address Filtering Functionality on the Egress
Configuring an ATM SPVC
5-33
Configuring Node Prefix
5-34
Add an SPVC Connection
5-34
Modify an SPVC Connection
5-38
Delete an SPVC Connection
5-39
Add an SPVP Connection
5-40
Configuring SPVC Feeder Connection
5-40
Set up the feeder trunk on the MGX 8850.
Set up the Feeder trunk on the BPX
5-40
5-42
Set up an SPVC Segment on the SES
5-44
Set up the PVC segment on an MGX 8850 Feeder Node
Configuring Dynamic/Soft Partitioning
C H AP TER
6
5-33
5-45
5-49
Configuring SPVC Stats Collection
5-49
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
Displaying Node Alarms
Displaying Card Alarms
6-4
6-4
6-4
Cisco SES PNNI Controller Software Configuration Guide
viii
Release 1, Part Number 78-6123-05 Rev. A0, March 2001
Contents
Displaying Environment Alarms
Displaying Slot Alarms
6-6
Displaying Switching Alarms
6-6
Displaying Event Log Information
6-6
Displaying Error Information
C H AP TER
7
6-5
Network Management
6-7
7-1
Minimum System Requirements
Hardware
7-1
Software
7-2
7-1
Installing and Configuring Cisco WAN Manager
Disk Partitioning Requirements
7-3
Partitioning One 9-GB Disk
7-3
Partitioning Two 9-GB Disks
7-3
7-5
Modifying the network.conf File for PNNI Networks
Configuring PNNI Topology Discovery
7-5
Configuring the SES PNNI Controllers
Cisco WAN Manager SES PNNI Features
SPVC Overview
WAN CiscoView 3.2
7-6
7-6
7-6
7-6
Installing CiscoView
7-7
Accessing CiscoView
7-7
Navigating in CiscoView
7-7
Main Menu Buttons
7-8
Status Bar and Buttons
7-8
Making Selections and Displaying Menus
Popup Menu Options
Using CiscoView
7-10
7-10
7-10
Preference Setting Options
7-11
Device-Specific Buttons within Configure Menu
Integrating New Device Information
7-12
Device Support Utility Features
7-12
Using the Device Support Utility
Testing Basic Connectivity and Setup
Troubleshooting
7-5
7-12
7-12
7-13
7-13
Test the IP Connectivity
7-13
Cisco SES PNNI Controller Software Configuration Guide
Release 1, Part Number 78-6123-05 Rev. A0, March 2001
ix
Contents
Open a Telnet Session to the Device
Verify the CiscoView Preferences
Call Tracing
7-14
Connection Trace Success
7-14
Connection Trace Failure
7-14
CLI Commands Functionality
conntrace Command
Path Trace
7-14
7-15
7-15
Path Trace Success
7-16
Path Trace Failure:
7-16
SES CLI Pathtrace Commands
A
Technical Specifications
PNNI Compliance
A-1
UNI 3.x Signaling
IISP Signaling
7-16
A-1
ATM Signaling Compliance
A-2
A-2
A-2
PNNI Signaling
A-2
ATM Signaling Interworking
A-3
Networking Application Support
Interoperability Support
A-3
A-4
Processor Switching Module Specifications
AP PE N DIX
B
7-13
7-14
Connection Trace
AP PE N DIX
7-13
Virtual Switch Interface
A-4
B-1
Virtual Switch Interface Protocol
VSI Master and Slaves
B-1
B-1
Resource Partitioning
B-3
Configuring VSI-ILMI
B-4
Support Enabling ILMI Functionality for VSI Partitions on Port Interfaces
B-4
Enable ILMI Functionality for VSI Partitions on Physical Trunk Interfaces
B-5
Enable VSI ILMI Functionality on Virtual Trunk Interfaces
Class of Service Templates
B-6
Functional Description
B-7
Service Class Template Structure
B-5
B-8
Downloading Service Class Templates
B-11
Cisco SES PNNI Controller Software Configuration Guide
x
Release 1, Part Number 78-6123-05 Rev. A0, March 2001
Contents
Assignment of a Service Class Template to an interface
Card Qbin Configuration
Qbin Dependencies
B-11
B-12
Extended Services Types Support
Connection Admission Control
Supported Service Types
AP PE N DIX
C
B-12
B-13
B-13
SNMP Management Information Base
SNMP Fundamentals
MIB Tree
B-11
C-1
C-1
C-1
MIB Objects Overview
Object Identifier
C-3
C-3
Object Definitions
SNMP Traps
C-3
C-7
MIBs Supported by the PNNI Controller
ATM MIB Objects
C-7
atmInterfaceConfTable
PNNI MIB Objects
C-8
C-8
pnniBaseGroup
C-9
pnniNodeTable
C-10
pnniNodePglTable
C-16
pnniNodeTimerTable
C-19
pnniNodeSvccTable
C-21
pnniScopeMappingTable
pnniLinkTable
C-22
C-24
pnniSummaryAddressTable
Cisco WAN SVC MIB Objects
ciscoWANSvcInfo
C-27
C-28
C-28
CiscoWANSpvc Port
cwspConnTrace
C-7
C-29
C-45
Cisco WAN ATM MIB Objects
cwAtmChanCfgTable
CwAtmChanStateTable
CwAtmChanTestTable
C-50
C-51
C-58
C-59
Cisco SES PNNI Controller Software Configuration Guide
Release 1, Part Number 78-6123-05 Rev. A0, March 2001
xi
Contents
GL OS SA RY
IN DEX
Cisco SES PNNI Controller Software Configuration Guide
xii
Release 1, Part Number 78-6123-05 Rev. A0, March 2001
F I G U R E S
Figure1-1
SES PNNI Node
Figure1-2
PXM Backcard Simple Block Diagram
Figure1-3
OC-3 Cabling from Two BXMs to Redundant PXMs
Figure1-4
DS3 Y-Cabling from Single BXM to Redundant PXMs
Figure1-5
APS 1 + 1 (Card and Line Redundancy) Dual Backcard Configuration
Figure1-6
PXM Software Architecture
Figure1-7
SES PNNI Software Architecture
Figure1-8
Controller and Slave VSIs
Figure1-9
VSI Master and VSI Slave Example
Figure1-10
BPX Resource Partitioning
Figure1-11
Resource Partitioning between AutoRoute and VSI
Figure1-12
PNNI Network
Figure1-13
PNNI Network with IISP Trunks
Figure1-14
Mixed AutoRoute and PNNI Networks
Figure2-1
BXM Redundancy Example
Figure4-1
Initial Setup Tasks for PNNI Controller
Figure4-2
BPX and SES PNNI Controller Interfaces
Figure4-3
User Interface (PXM UIA) Backcard
Figure4-4
PXM OC-3 Backcard
Figure4-5
Command Prompt Components
Figure5-1
Bringup Tasks for PNNI Controller
Figure5-2
PNNI Configuration Sequence Overview
Figure5-3
SVC Set Up Example
5-22
Figure5-4
SPVC Setup Example
5-34
Figure6-1
PXM Front Card Controls
Figure7-1
Connection Trace in PNNI and IISP Network
Figure7-2
Insert and Remove IEs
FigureB-1
VSI, Controller and Slave VSIs
FigureB-2
VSI Master and VSI Slave Example
FigureB-3
BXM Virtual Interfaces and Qbins
B-3
FigureB-4
Service Class Template Overview
B-8
1-2
1-3
1-6
1-7
1-13
1-14
1-15
1-18
1-18
1-19
1-19
1-22
1-23
1-24
2-5
4-1
4-2
4-4
4-4
4-6
5-1
5-14
6-2
7-15
7-17
B-2
B-2
Cisco SES PNNI Controller Software Configuration Guide
Release 1, Part Number 78-6123-05 Rev. A0, March 2001
xiii
Figures
FigureB-5
Service Class Template and Associated Qbin Selection
FigureC-1
MIB Tree
B-10
C-2
Cisco SES PNNI Controller Software Configuration Guide
xiv
Release 1, Part Number 78-6123-05 Rev. A0, March 2001
T A B L E S
Table1
Cisco SES PNNI Controller Release 1
Table2
Cisco WAN Manager Release 10
Table3
WAN CiscoView Release 3 for BPX SES PNNI Controller Documentation
Table1-1
Hitless Operations
Table1-2
Call Control Block Components
Table2-1
BXM Redundancy—Supported Hardware
Table2-2
BXM Redundancy Types
Table2-3
Call Redundancy Functions
Table3-1
User Access Levels
Table3-2
Hardware Configuration Worksheet
Table3-3
Valid Card Installation Options
Table3-4
Determining Firmware Version Numbers from Filenames
Table4-1
SES F/W Compatibility Matrix
Table5-1
Service Class Template Qbin Parameters
Table5-2
Service Class Template Commands
Table6-1
LED Indicators for PXM
Table7-1
Minimum CWM Release 10.2 Workstation Requirements
Table7-2
Sun Platform Requirements
Table7-3
Partitioning a Single 9-GB Disk
7-4
Table7-4
Partitioning the First 9-GB Disk
7-5
Table7-5
Supported SPVC Connections
Table7-6
CiscoView Main Menu Buttons
Table7-7
CiscoView Status Bar and Buttons
Table7-8
Cisco View Popup Menu Options
Table7-9
Configure Menu Buttons (Device Specific)
TableA-1
PXM Specifications
TableB-1
ifci Parameters (Virtual Switch Interface)
TableB-2
Partition Criteria
TableB-3
Service Class Template Qbin Parameters
TableB-4
Service Category Listing
TableB-5
VSI Special Service Types
xviii
xix
xix
1-12
1-16
2-4
2-4
2-7
3-11
3-15
3-19
3-23
4-11
5-11
5-11
6-2
7-1
7-2
7-6
7-8
7-8
7-10
7-12
A-4
B-3
B-4
B-12
B-13
B-15
Cisco SES PNNI Controller Software Configuration Guide
Release 1, Part Number 78-6123-05 Rev. A0, March 2001
xv
Tables
TableB-6
ATM Forum Service Types, CBR, UBR, and ABR
TableB-7
ATM Forum VBR Service Types
TableB-8
MPLS (Tag Switching) Service Types
TableB-9
Connection Parameter Descriptions and Ranges
TableC-1
atmInterfaceConfTable Entries
TableC-2
pnniBaseGroup
C-9
TableC-3
pnniNodeTable
C-11
TableC-4
pnniNodePglTable
TableC-5
pnniNodeTimerTable
TableC-6
Nodal SVCC-based RCC Variables Table
TableC-7
pnniScopeMappingTable
TableC-8
pnniLinkTable
TableC-9
pnniSummaryAddressTable
TableC-10
SVC Information Group
TableC-11
Interface Configuration Table Entries
TableC-12
Port Call Statistics Table Entries
TableC-13
Port CAC Configuration Table Entries
TableC-14
Port Signaling Statistics Table Entries
TableC-15
Port Address Table Entries
C-43
TableC-16
Port Loading Table Entries
C-44
TableC-17
Port Connection Trace Availability Entry
TableC-18
Port Connection Trace If Index Entry
TableC-19
Port Connection Trace Control Table Entry
TableC-20
Port Connection Trace Control Table Entries
TableC-21
Port Connection Data Table
TableC-22
Interface Operation Table Entries
TableC-23
cwAtmChanCfgTable
TableC-24
cwAtmChanStateEntry Objects
TableC-25
cwAtmChanTestEntry Objects
B-16
B-17
B-17
B-18
C-8
C-17
C-19
C-21
C-22
C-24
C-27
C-28
C-29
C-34
C-36
C-41
C-45
C-46
C-46
C-46
C-47
C-48
C-51
C-58
C-59
Cisco SES PNNI Controller Software Configuration Guide
xvi
Release 1, Part Number 78-6123-05 Rev. A0, March 2001
About This Manual
Welcome to the software configuration manual for the BPX Service Expansion Shelf (SES) PNNI
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 be originating, transporting, or terminating SVC/SPVC connections must be
collocated and directly connected to an SES PNNI node 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 t he 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
Cisco View network management systems.
Warning
Installation of the equipment should be performed by trained service personnel.
Cisco SES PNNI Controller Software Configuration Guide
Release 1, Part Number 78-6123-05 Rev. A0, March 2001
xvii
About This Manual
Organization
Organization
This document contains t he following chapters and appendices:
Chapter1, “SES PNNI Controller Overview,” provides an overview of the SES Controller, the SES
PNNI node, and ATM and SVC s.
Chapter2, “Getting Started,” provides procedures for setting general switch features on an SES node.
Chapter3, “SES PNNI Controller Setup and Initial Configuration,” provides procedures for the SES
node.
Chapter4, “Configuring ATM SVCs, PNNI Routing, and SPVCs,” provides bring-up and initial
configuration procedures for the SES node.
Chapter5, “Viewing and Responding to Alarms,” provides information about Alarms on the SES node.
Chapter6, “Network Management,” provides an introduction to 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.
AppendixA, “Technical Specifications,” lists the relevant specifications for the SES PNNI node.
Appendix B, “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 C, “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 the SES
PNNI Controller Release 1.
Cisco SES PNNI Controller Release 1 Documentation
The following table lists the documentation for the Cisco SES PNNI Release 1.
Table1
Cisco SES PNNI Controller Release 1
Documentation
Description
Cisco PNNI Configuration Guide, Release1
Provides a detailed description of the PNNI protocol as it is used
on Cisco WAN switches.
DOC-7812275=
Cisco SES PNNI Controller Software Configuration Guide, Provides a detailed description the SES Controller hardware,
Release 1
software, services, and configuration procedures for adding PNNI,
IISP, ATM SVCs/SVPs, and ATM SPVCs/SPVPs to a
DOC-786123=
BPX 8600 Network.
Cisco SES PNNI Controller Software Command
Reference, Release 1
Provides a detailed description of the Command Line Interface
used to configure the SES Controller.
DOC-7812274=
Cisco SES PNNI Controller Software Configuration Guide
xviii
Release 1, Part Number 78-6123-05 Rev. A0, March 2001
About This Manual
Conventions
Cisco WAN Manager Release 10 Documentation
The following table lists the documentation for the Cisco WAN Manager (CWM) network management
system for Release 10.
Table2
Cisco WAN Manager Release 10
Documentation
Description
Cisco WAN Manager Installation for Solaris, Release10
Provides procedures for installing Release 10 of the CWM
network management system on Solaris systems.
DOC-7810308=
Cisco WAN Manager User’s Guide, Release 10
DOC-7810658=
Cisco WAN Manager SNMP Service Agent Guide,
Release 10
DOC-7810786=
Provides procedures for operating Release 10 of the CWM
network management system.
Provides information about the CWM Simple Network
Management Protocol (SNMP) Service Agent components and
capabilities.
Cisco WAN Manager Database Interface Guide, Release10 Provides the information to gain direct access to the CWM
Informix OnLine database that is used to store information
DOC-7810785=
about the elements within your network.
WAN CiscoView Release 3 for BPX SES PNNI Controller, Release 1
The following table lists documentation for t he CiscoView product that operates with the BPX SES
PNNI Controller.
Table3
WAN CiscoView Release 3 for BPX SES PNNI Controller Documentation
Documentation
Description
WAN CiscoView Release 3 for the BPX SES PNNI
Controller, Release1
Provides instructions for using WAN CiscoView Release 3 for the
BPX SES PNNI Controller, a network management software
application that allow you to perform minor configuration and
troubleshooting tasks.
DOC-7812303=
Conventions
The Cisco SES PNNI Controller Software 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.
Cisco SES PNNI Controller Software Configuration Guide
Release 1, Part Number 78-6123-05 Rev. A0, March 2001
xix
About This Manual
Obtaining Documentation
•
Nonprinting characters, such as passwords, are in angle brackets (< >).
•
Default responses to system prompts are in square brackets ([ ]).
Notes, cautions, and warnings use the following conventions and symbols:
Tips
The Tip symbol contains additional information that can help you understand the product
or complete a task more efficiently.
Note
The Note symbol means reader take note . Notes contain helpful suggestions or references
to information not contained in this manual.
Caution
The Caution symbol means reader be careful . In this situation, you might do something
that could result in equipment damage or loss of data.
Warning
The Warning symbol means danger. You are in a situation that could cause bodily injury.
Before you work on any equipment, you must be aware of the hazards involved with
electrical circuitry and familiar with standard practices for preventing accidents.
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
withyour 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 annualsubscription.
Cisco SES PNNI Controller Software Configuration Guide
xx
Release 1, Part Number 78-6123-05 Rev. A0, March 2001
About This Manual
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 408526-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, Part Number 78-6123-05 Rev. A0, March 2001
xxi
About This Manual
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
xxii
Release 1, Part Number 78-6123-05 Rev. A0, March 2001
C H A P T E R
1
SES PNNI Controller Overview
The Cisco Service Expansion Shelf (SES) Private Network-to-Network Interface (PNNI) controller
attaches to a BPX 8600 series switch to provide PNNI signaling and routing. PNNI is used to establish
ATM Switched Virtual Circuits (SVCs) and Soft Permanent Virtual Circuits (SPVCs) over a BPX 8600
wide area network. The SES PNNI Controller uses the Cisco Virtual Switch Interface (VSI) protocol to
control the BPX switch for its networking application.
SES PNNI Node Components
The complete SES node architecture consists of the combined BPX 8620 switch and the SES PNNI
Controller (Figure1-1). The SES PNNI Controller uses the combined network management system of
Cisco WAN Manager and CiscoView to configure and monitor the SES PNNI node. An SES PNNI node
is the combined SES PNNI Controller and a BPX 8620 switch.
Cisco SES PNNI Controller Software Configuration Guide
Release 1, Part Number 78-6123-05 Rev. A0, March 2001
1-1
Chapter1
SES PNNI Controller Overview
SES PNNI Node Components
Figure1-1
SES PNNI Node
SES PNNI Controller
The SES PNNI Controller is a 7-slot chassis that contains two Processor Switch Modules (PXMs) that
run the PNNI and SVC software. One of the PXMs serves as the active processor, while the other serves
as the standby. The PNNI controller is connected to the BPX switch by either the ATM/OC-3 interface
(Figure1-3) or the ATM/DS3 interfaces (Figure1-4).
Note
The Service Expansion Shelf (SES) can be used in several WAN switching applications,
and is not limited to function only as a SES PNNI Controller. However, when used as the
SES PNNI Controller, the SES may only be populated with two switch processor modules
(PXMs) and associated backcards. The remaining five slots of a shelf in service as a SES
PNNI Controller are not used.
Processor Switch Module (PXM)
Two PXM cards must reside in the SES PNNI Controller to enable redundant PNNI functionality. Line
and service cards are not applicable to PNNI operations and cannot be installed in the PNNI Controller.
Cisco SES PNNI Controller Software Configuration Guide
1-2
Release 1, Part Number 78-6123-05 Rev. A0, March 2001
Chapter1
SES PNNI Controller Overview
SES PNNI Node Components
Note
The PXM used in the SES PNNI Controller application is logically identical to the PXM
used in the MGX 8850 but is keyed to fit only in the PNNI Controller. Also, the PXM for
the PNNI controller is referenced by a different model number than is the PXM used in an
MGX8850.
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 are required for each installed PXM front card. A PXM back card pair
consists of the following:
•
User interface backcard—PXM-UI 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 backcard is the ATM Trunk Interface that provides line drivers for the uplink
interface. For SES PNNI Controller applications, the PXM ATM interface uplink card uses either
a single port from the quadOC-3 multi-mode port or the quad DS-3 port backcard.
Figure1-2 shows a diagram of the PXM backcard.
Figure1-2
PXM Backcard Simple Block Diagram
Cisco SES PNNI Controller Software Configuration Guide
Release 1, Part Number 78-6123-05 Rev. A0, March 2001
1-3
Chapter1
SES PNNI Controller Overview
SES PNNI Node Components
A mismatch between the uplink back card type and that of the PXM will generate a major alarm. (The
PXM has a daughter card that is factory installed and must match the type of ATM interface backcard.)
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 the Cisco BPX 8600 Series Installation and Configuration documentation for 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 SES PNNI node internal interface between the SES PNNI 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 SES
PNNI 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 SES PNNI 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 WAN Service Node
supports either the Interim Inter-switch Protocol (IISP) 3.0/3.1, or the Private Network-to-Network
Interface (PNNI). These NNI interfaces provide the switching and routing functions between Cisco
WAN switching networks and other networks. Information passing across a NNI is related to circuit
routing and status of the circuit in the adjacent network.
Cisco SES PNNI Controller Software Configuration Guide
1-4
Release 1, Part Number 78-6123-05 Rev. A0, March 2001
Chapter1
SES PNNI Controller Overview
SES PNNI Node Components
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.
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 SES PNNI
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 Stratum 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/BPX Interfaces
Figure1-3 and Figure1-4 are simple block diagrams of a SES PNNI node. These figures illustrate the
internal interfaces of the SES PNNI node (that is, between the PBX SES PNNI controller and the BPX
switch) and the external interfaces. The external interfaces of a SES PNNI node connect to ATM end
systems, and ATM trunks to other ATM or PNNI nodes or networks, and connections to Network
Management Systems, such as the Cisco WAN Manager or CiscoView.
Cisco SES PNNI Controller Software Configuration Guide
Release 1, Part Number 78-6123-05 Rev. A0, March 2001
1-5
Chapter1
SES PNNI Controller Overview
SES PNNI Node Components
Figure1-3
OC-3 Cabling from Two BXMs to Redundant PXMs
Cisco SES PNNI Controller Software Configuration Guide
1-6
Release 1, Part Number 78-6123-05 Rev. A0, March 2001
Chapter1
SES PNNI Controller Overview
System and Network Management
Figure1-4
DS3 Y-Cabling from Single BXM to Redundant PXMs
System and Network Management
Cisco WAN Manager (CWM) and CiscoView are network management applications that can be used to
configure, monitor, and manage the SES PNNI node. The Network Management Station can be
connected to the SES PNNI either with directly connected Ethernet interfacing or by using the Cisco
WAN Switching IP Relay application.
Note
•
Cisco WAN Manager
•
CiscoView
•
Command Line Interface
CWM is formerly known as StrataView Plus.
Cisco WAN Manager
Cisco WAN Manager (CWM), a suite of WAN multiservice management applications, provides
powerful fault, configuration, and performance management functionality for WAN multiservice
switches. CWM also provides robust statistics collection, storing the information in an Informix SQL
database and allowing simple integration of this data into existing network management and operations
systems.
Cisco SES PNNI Controller Software Configuration Guide
Release 1, Part Number 78-6123-05 Rev. A0, March 2001
1-7
Chapter1
SES PNNI Controller Overview
System and Network Management
Element and network management functions are provided by the CWM system, which can manage
Cisco BPX 8600 series wide-area switches and Cisco SES Controller devices seamlessly. CWM
provides open interfaces for higher level service management systems.
The CWM desktop graphical user interface (GUI) provides the following applications:
•
Physical Topology
•
Connection Manager
•
Network Browser
•
Service Class Template Manager
•
Statistic Collection Manager
•
CWM Administration
•
Summary Report
CWM provides these functions in an open management environment. CWM runs on Solaris, AIX, and
HP-UX platforms, and integrates with HP OpenView and IBM NetView.
Features
This section provides information about the main features of CWM.
From the Cisco WAN Manager interface you perform the following tasks:
•
Add, modify, and delete connections
•
Collect statistics on network operation
•
Manage all the different models of Cisco multiservice switches
Connection Management
The Connection Manager provides the network manager the ability to add, modify, and delete
end-to-end connections. The Connection Manager provides a series of forms-based screens to add,
modify, or delete connections. You select the desired connection end-points and configure the
connection type and class of service. The end-to-end connection is automatically established without
requiring configuration of the network on a switch-by-switch basis. In addition, each connection’s
status can be viewed from one endpoint to the other.
Connection management is one of the most challenging issues in ATM network management; ATM
networks support so many connections that it can become impossible to administer and manage them.
The Connection Service MIB provides integrated automated provisioning of connections based on
quality of service parameters, such as the type of connection being made, available bandwidth, and the
current state of the network.
The Connection Service MIB provides a standard SNMP interface for the WAN ATM network at the
service level. Service providers who are responsible for managing the entire shared network can use
this interface to integrate with automated Operations Support Systems (OSS) provisioning systems and
also to provide Customer Network Management (CNM) views and control capabilities on a
per-connection basis.
Statistics Collection Manager
The Statistics Collection Manager (SCM) provides a forms-based interface to establish and modify
statistics collection policies for the network. You can configure statistics collection policies such as
which statistics to collect and collection interval periods for a node, port, or private virtual circuit
Cisco SES PNNI Controller Software Configuration Guide
1-8
Release 1, Part Number 78-6123-05 Rev. A0, March 2001
Chapter1
SES PNNI Controller Overview
System and Network Management
(PVC). SCM provides extensive error handling and logging capabilities that enable reliable collection
of statistics for performance or billing applications. Additional SCM agent workstations can be
installed for gathering additional statistics. Each SCM agent can collect in excess of 1 million statistics
per hour. Scalability of statistics collection is an important feature of CWM. CWM also provides node
utilization reports not based on WingZ.
Access to IGX, BPX, and MGX Networks
IGX, BPX, and MGX switches provide an Ethernet 802.3 AUI LAN interface to CWM for network
management control and information. An entire network can be managed through an Ethernet
connection on a single WAN switch or through multiple Ethernet interfaces distributed throughout the
network. Cisco WAN switches use TCP/IP over Ethernet to communicate between CWM network
management workstations and the WAN switch. Telnet support is also available to enable LAN-based
workstations access to the IGX, BPX, or MGX management interface.
Out-of-Band Network Management
An entire network can be managed through a connection on a single WAN switch or through multiple
interfaces distributed throughout the network. Network Management access to the IGX can be either
provided locally through a direct interface or remotely. Remote and dial access to any IGX node can be
accomplished by connecting a dial modem to the control port. All of the security management functions
of the IGX, BPX, or MGX platforms are maintained whether access is local or remote.
Virtual Terminal access to any remote IGX from the CWM configuration screen or a VT100 connected
to the control port is supported using the VT command. The VT command will provide network
operations staff with identical control and monitoring capabilities as if they were locally attached to the
switch.
CiscoView
WAN CiscoView is a GUI-based device management software application that allows you to display
configuration and performance information, and perform minor configuration tasks on the SES PNNI
Controller. WAN CiscoView for the SES PNNI Controller, Release 1.0 provides a description of tasks
that can be performed through CiscoView.
For more information on managing the network elements using CiscoView, please refer to
Release 1.0, WAN CiscoView for the SES PNNI Controller , and Release 2.0, WAN CiscoView for BPX
8600 Switches.
CiscoView is a graphical SNMP-based device management tool that provides real-time views of
networked Cisco Systems devices. These views deliver a continuously updated physical picture of
device configuration and performance conditions, with simultaneous views available for multiple
device sessions.
Features
This section provides information about the main features of CiscoView.
From the CiscoView interface you perform the following tasks:
•
View a graphical representation of the device, including component (interface, card, power supply)
status.
•
Configure parameters for devices, cards, and interfaces.
Cisco SES PNNI Controller Software Configuration Guide
Release 1, Part Number 78-6123-05 Rev. A0, March 2001
1-9
Chapter1
SES PNNI Controller Overview
PNNI Routing and ATM Switched Virtual Circuits
•
Monitor real-time statistics for interfaces, resource utilization, and device performance.
•
Telnet, access CCO, send e-mail to TAC, set values for SNMP parameters and community strings.
•
Perform device-specific operations as defined in each device package.
•
Manage groups of stackable devices.
CiscoView contains common devices functions such as selecting main menu options and categories of
information for configuring and monitoring. Each device package also has its own specific menu
options and functions.
Command Line Interface
The SES Controller command line interface (CLI) configures ATM SVCs, SPVCs, and PNNI routing
and signaling on the SES Controller.
Note
Throughout this manual, some BPX-specific commands are presented where applicable to
PNNI configuration tasks. For additional information on the BPX command suite, refer to
Cisco BPX 8600 Series Installation and Configuration, the Cisco WAN Switching
Command Reference, and the SuperUser Command Reference for Switch Software
Release 9.2.
PNNI Routing and ATM Switched Virtual Circuits
The SES PNNI node adds PNNI routing and ATM switched virtual circuits to a traditional Cisco WAN
switching network. The network created with SES PNNI nodes is enhanced for SVCs/SPVCs and also
supports traditional ATM and Frame Relay permanent virtual circuits (PVCs) in a separately partitioned
AutoRoute network.
ATM SVCs are ATM connections that are established and maintained by a standardized signaling
mechanism between ATM CPE (ATM end systems) across a Cisco WAN switching network. ATM
SVCs are set up in accordance with user demand and removed when calls are completed, thus freeing
up network resources.
SPVCs (Soft Permanent Virtual Circuit) are persistent ATM connections established by the PNNI
routing database and signalling across a Cisco WAN switching network. The routing protocol that the
SES PNNI node uses to establish connections is the Private Network-to-Network Interface (PNNI)
routing protocol. Defined by the ATM Forum for ATM networks, PNNI is a dynamic routing protocol
that responds to changes in network resource availability, and scales to large networks.
SES PNNI node resources, such as port virtual path identifier (VPI) range and bandwidth and trunk
bandwidth, are partitioned between SVCs/SPVCs and PVCs. Resource partitioning provides a firewall
between PVCs and SVCs/SVPs so that problems with CPE or large bursts do not affect the robustness
and availability of PVC services. Bursty data for either PVCs or SVCs/SPVCs can always use any
unused link bandwidth, regardless of partitioning.
Cisco SES PNNI Controller Software Configuration Guide
1-10
Release 1, Part Number 78-6123-05 Rev. A0, March 2001
Chapter1
SES PNNI Controller Overview
PNNI Routing and ATM Switched Virtual Circuits
ATM Routing and Signaling
For ATM SVCs/SPVCs, the SES PNNI node uses the Private Network-to-Network Interface (also
known as Private Network-to-Node Interface). As defined by the ATM Forum, PNNI is a dynamic
routing protocol specified for use between private ATM switches (for example, Cisco SES PNNI
nodes), and between groups of private ATM switches.
PNNI defines the following two protocol categories:
•
Topology State Routing
•
PNNI Signaling
Topology State Routing
Topology state routine distributes topology information between switches and clusters of switches. This
information is used to compute paths through the network. A key feature of the PNNI mechanism is its
ability to automatically configure itself in networks in which the address structure reflects the topology.
PNNI topology and routing are based on the well-known link-state routing technique. Refer to the Cisco
PNNI Configuration Guide for more information about PNNI routing protocol.
PNNI Signaling
Private Network-to-Network Interface (PNNI) signaling defines the message flows used to establish
point-to-point connections across the ATM network. This protocol is based on the ATM Forum UNI
signaling and includes functions to support source routing, crankback, load balancing, and alternate
routing of call setup requests in case of connection setup failure.
Interim Inter-Switch Protocol Routing
Interim Inter-switch Protocol (IISP) is a static routing protocol defined by the ATM Forum to provide
base level UNI signaling between switches until PNNI was specified. IISP is sometimes referred to as
PNNI Version 0. The IISP provides users with a fundamental level of multi-vendor switch
interoperability based on the existing ATM Forum UNI 3.1 specifications. IISP assumes no exchange
of routing information between switching systems. It uses a a fixed routing algorithm with static routes.
Routing is done on a hop-by-hop basis by making a best match of the destination address in the call
setup with address entries in the next hop routing table at a given switching system. Entries in the next
hop routing table are manually configured. Refer to the Cisco PNNI Configuration Guide for more
information about IISP.
ILMI
The SES PNNI node uses ILMI to automatically identify which of its interfaces are User-Network
Interface (UNI), attached to ATM end systems, and which are Network-to-Network Interface (NNI),
attached to other systems. This information is used by ATM Routing protocols, PNNI, and
Interim-Interswitch Signaling Protocol (IISP) to automatically discover and bring up a network of
interconnected SES PNNI nodes.
Cisco SES PNNI Controller Software Configuration Guide
Release 1, Part Number 78-6123-05 Rev. A0, March 2001
1-11
Chapter1
SES PNNI Controller Overview
Redundant SES PNNI Controllers
The ILMI protocol is used for the following procedures:
•
Registering ATM address across an ATM UNI.
•
Configuring ATM end systems with ATM address prefixes.
•
Enabling the SES PNNI node to discover the 48-bit Media Access Control (MAC) addresses of the
attached systems.
Redundant SES PNNI Controllers
The BPX and SES PNNI Controller are completely redundant and offer hitless operation. A hitless
switchover occurs when the controller is switched over from an active processor to a standby processor
due to system hardware or software failure. During hitless switchovers, all established active calls are
unaffected by the switchover and continue to stay up (Table1-1), however a probability exists that calls
that have been established over the past 1 (one) second will be dropped.
Table1-1
Hitless Operations
Type of Event
Result
Hitless switchover between PXM
(active/standby) in the SES.
All active calls are maintained after PXM switchover.
Failure of the OC-3 link between the
SES and BPX.
Automatic APS switchover to alternate OC-3 link. There is
no impact to existing fully established calls.
Hitless switchover between the BCC
cards in the BPX.
No impact to existing, fully established calls.
Hitless software upgrade in the BPX
and/or the SES.
No impact to existing, fully established calls.
Automatic Protection Switching
Also referred to as line redundancy, automatic protection switching (APS) is a standard that defines the
switching of SONET lines from the active line to a standby line to provide hardware line redundancy
after failure of an active line. This function is defined by the standards GR-253, ITU-G.7683, and
ITU-G.841, which describe switching criteria and an in-band protocol carried by the K1/K2 bytes, and
is applicable to OC-3, OC-12, and DS3 interfaces.
Upon detection of a signal fail condition (for example, LOS, LOF, Line AIS, or Bit Error Rate in excess
of a configured limit) or a signal degradation condition (for example, BER exceeding a configured
limit), the hardware switches from the working line to the protection line, assuming that the working
line was the active line and the protection line was not in alarm.
APS 1+1 dual backcard, provides card and line redundancy, using the same numbered ports on adjacent
BXM backcards (Figure1-5). Each OC-3 link on the PXM is connected to an OC-3 link on a BPX card.
These links use APS, which enables APS switchover in fewer than 60 ms in the event of a link failure.
This switchover occurs at the backcards of the PXM and BXM only. Front cards do not switch over
during an APS switchover session.
Cisco SES PNNI Controller Software Configuration Guide
1-12
Release 1, Part Number 78-6123-05 Rev. A0, March 2001
Chapter1
SES PNNI Controller Overview
SES PNNI Node Software Architecture
Figure1-5
APS 1 + 1 (Card and Line Redundancy) Dual Backcard Configuration
Coordination between the interfaces on the two ends of the lines is provided using an in-band protocol.
Y-Cable Redundancy
The SES supports Y-cable port redundancy. To set up port redundancy, installing two identical front and
back PXM card sets, connecting them with a Y-cable on each paired port.
During normal operation, the primary card set is “active” and carrying traffic, while the secondary card
set is in “standby.” The primary set configuration is the configuration for both the primary and
redundant set. If you reset the primary cards or the primary card set becomes inactive for another
reason, the secondary card set becomes active.
SES PNNI Node Software Architecture
The SES PNNI Node Software is distributed across three branches of software:
•
PXM Software
•
BPX Software
•
Network Management Software (namely, Cisco WAN Manager and CiscoView)
These three branches of software interact to create SES PNNI nodes, a PNNI network, and ATM
SVC/SPVC services.
Cisco SES PNNI Controller Software Configuration Guide
Release 1, Part Number 78-6123-05 Rev. A0, March 2001
1-13
Chapter1
SES PNNI Controller Overview
SES PNNI Node Software Architecture
PXM Software
The PXM software for the SES PNNI Controller contains three major functional blocks (Figure1-6):
•
Control Point Software
•
PNNI and SVC Software
•
Platform Software
VSI software provides the VSI master application used by the PNNI and SVC/SPVC networking
control software to control the BPX switch. (For more information, refer to the “Virtual Switch
Interface Protocol” section on page1-17.)
Figure1-6
PXM Software Architecture
Control Point Software
Control Point software runs on the PXM at the SES PNNI Controller to provide a single, integrated
point of control for the PXM and the PNNI and ATM SVC application software. It provides the interface
that enables configuration of the PNNI and ATM SVC parameters for the SES PNNI node, and the PXM
management functions.
This interface takes the form of an API, in which requests to get or send data are made to PNNI and
SVC software through a well defined message based interface. Additionally, PNNI and SVC software
may generate events to the Control Point, for reasons such as alarm status changes (such as connection
routing and rerouting).
The Control Point software enables direct access to the SES PNNI Controller command sets by
providing a consistent, integrated SNMP proxy for the platform, and CLI for the service expansion
shelf.
Cisco SES PNNI Controller Software Configuration Guide
1-14
Release 1, Part Number 78-6123-05 Rev. A0, March 2001
Chapter1
SES PNNI Controller Overview
SES PNNI Node Software Architecture
PNNI and SVC Software
The PNNI and SVC software architecture consists of three major components (Figure1-7):
•
Call Control Block
•
PNNI
•
Redundancy Manager
Figure1-7
SES PNNI Software Architecture
Call Control Block
The major features implemented in Call Control Block are as follows:
•
UNI 3.X SVC support.
•
IISP 1.0 support plus crankback, load balancing, and overbooking enhancements.
•
PNNI/IISP and AutoRoute coexistence on the same port, trunk, and BPX node in the network.
The PNNI controller will use the VSI partition to provide its networking capabilities.
•
Set of MIBs to allow both provisioning and surveillance of the PNNI system.
The major components in Call Control Block are shown in Table1-2.
Cisco SES PNNI Controller Software Configuration Guide
Release 1, Part Number 78-6123-05 Rev. A0, March 2001
1-15
Chapter1
SES PNNI Controller Overview
SES PNNI Node Software Architecture
Table1-2
Call Control Block Components
Components
Description
•
Sets up/tears down cross-connect on the switch when an SVC is
established/released.
•
Provides the finite state machine of point-to-point calls.
•
Performs address filtering.
•
Works with the PNNI process for source routing or termination port
determination.
•
Releases calls upon switch port failure.
•
Includes ATM Forum UNI 3.x, PNNI 1.0, and IISP signaling.
•
Provides the message encoding and decoding of the signaling.
•
Manages the signaling stack finite state machine.
SSCOP
•
Layer 2 protocol that provides a reliable AAL layer link between a
pair of signaling entities.
VSI Master
•
Interface between SES PNNI Controller and switch. The SES PNNI
Controller uses this interface to set cross-connect on the switch and
pass the ILMI address registration information from switch
interface module to Call Control.
RM (Resource Manager)
•
Manages the interface resource such as VPI/VCI and bandwidth. It
also performs UPC control and CAC operations.
CM (Connection Manager)
•
Manages the addition and deletion of cross-connects.
Route Agent
•
Contains the routing table that is updated by PNNI.
•
Searches an optimal path in the routing table, as requested by Call
Control.
•
Performs on-demand route calculation if no path is found in the
pre-calculated routing table.
Call Control
ATM Signaling Stack
PNNI
Performs topology information exchange and routing information exchange with other SES PNNI
Controllers.
PNNI pre-calculates a set of possible routing paths for all reachable nodes in the network. The routing
information is saved in a routing table of the route agent.
Redundancy Manager
The redundancy manager supports active call redundancy by shadowing the essential data structure
information on the standby SES PNNI Controller.
Cisco SES PNNI Controller Software Configuration Guide
1-16
Release 1, Part Number 78-6123-05 Rev. A0, March 2001
Chapter1
SES PNNI Controller Overview
Virtual Switch Interface Protocol
PNNI and SVC Routing Software
The major features included in PNNI Routing Block are as follows:
•
PNNI 1.0 support
•
PNNI Multiple Peer Group (MPG) support
•
Special network-wide and local load balancing and enhanced crankback
•
Overbooking
Platform Software
Platform software runs on the PXM at the SES PNNI Controller to provide low-level operation of the
system (including resource management and physical redundancy control) and a set of services to the
remaining subsystems. These services are categorized as Basic Platform-Specific Configuration and
Monitoring Service, and Platform Infrastructure.
Platform-Specific Configuration and Monitoring Services
The platform software provides an API to the management layer (namely, the Control Point software)
to allow the configuration and monitoring of cards, ports, redundancy options and any platform specific
features. It also enables the platform software to generate asynchronous events to the management
layer. This API consists of a message passing request/response protocol running on the PXM card.
Basic Platform Infrastructure
The platform software provides the basic infrastructure for the following:
•
Drivers for the PXM segmentation and reassembly (SAR)
•
Inter-card communications between PXM cards for redundancy control
•
File system support
•
PXM redundancy
Virtual Switch Interface Protocol
The Virtual Switch Interface (VSI) protocol controls a Cisco Wide Area Network Switch, such as the
BPX 8600, for networking applications, such as Multiprotocol Label Switching (MPLS) or PNNI
routing. With VSI, external controllers are used to control the switch for applications not supported by
the proprietary WAN switch set of routing protocols known as AutoRoute.
The SES PNNI Controller uses the VSI protocol to control BPX VC applications by creating a separate
control plane, distinct from the standard BPX AutoRoute control plane, that includes all the SES PNNI
nodes in the PNNI network. The SES PNNI node VSI control plane is the API that separates portable
network software from platform-specific software and firmware.
This section describes VSI in the following topics:
•
VSI Master and Slaves
•
Resource Partitioning
•
System Templates
For more information about the VSI protocol, refer to AppendixD, “Virtual Switch Interface.”
Cisco SES PNNI Controller Software Configuration Guide
Release 1, Part Number 78-6123-05 Rev. A0, March 2001
1-17
Chapter1
SES PNNI Controller Overview
Virtual Switch Interface Protocol
VSI Master and Slaves
The VSI is a master/slave protocol. The master VSI protocol runs on the SES PNNI Controller, and is
referred to in this application as the VSI controller. The slave VSI protocol runs on the BXM cards in
the BPX 8620 (Figure1-8).
Figure1-8
Controller and Slave VSIs
The VSI controller automatically establishes a link between the VSI master and every VSI slave on the
associated switch (Figure1-9). When enabled, the VSI slaves establish links.
The SES controller uses the VSI control channel to set up virtual circuit cross connect via VSI slaves
on BXM cards.
Figure1-9
VSI Master and VSI Slave Example
Resource Partitioning
Internal resources on the BPX must be partitioned between AutoRoute and the external VSI controller
to enable VSI establishment of a separate PNNI control plan. In a SES PNNI node, the resources are
partitioned between AutoRoute and PNNI on the BXM cards (Figure1-10). An MPLS partition can also
be added, but the SES PNNI Controller will not control or share the MPLS partition. A separate MPLS
controller will be required.
Cisco SES PNNI Controller Software Configuration Guide
1-18
Release 1, Part Number 78-6123-05 Rev. A0, March 2001
Chapter1
SES PNNI Controller Overview
Virtual Switch Interface Protocol
Figure1-10 BPX Resource Partitioning
BXM Resources
The resources that need to be partitioned between AutoRoute and PNNI on each BXM (Figure1-11)
are as follows:
•
Logical Connection Numbers (LCNs)
•
Virtual Path Identifiers (VPIs)
•
Port Bandwidth
Figure1-11 Resource Partitioning between AutoRoute and VSI
All bandwidth is allocated by default to AutoRoute when a BXM trunk is added. To preserve resources
for a VSI, enter the cnfrsrc command on the BPX switch to change the bandwidth allocation. See
Chapter 5, “Configuring ATM SVCs, PNNI Routing, and SPVCs” for more information about resource
partitioning.
Once the resources are partitioned, the PNNI controller (VSI controller) can use the resources to set up
user ATM SVCs/SPVCs across the PNNI network.
To add or remove bandwidth from autoroute without affecting the dynamic aspect, increase the VSI
partition and decrease autoroute.
Cisco SES PNNI Controller Software Configuration Guide
Release 1, Part Number 78-6123-05 Rev. A0, March 2001
1-19
Chapter1
SES PNNI Controller Overview
Virtual Switch Interface Protocol
System Templates
This section introduces the following system templates:
•
Service Class Templates (SCT)
•
Qbin Templates
For more information about SCT and Qbin templates, see Chapter5, “Configuring ATM SVCs, PNNI
Routing, and SPVCs.”
Note
The terms Class of Service Template and Service Class Template can be used
interchangeably.
Service Class Templates
Each BPX switch (running Release 9.2 and up) contains a set of nine SCTs that can be downloaded to
a BXM as needed. These SCTs have pre-defined, non-changeable values tailored for typical interfaces
such as a PNNI trunk or PNNI UNI.
SCT templates contain two classes of data:
•
Per-VC Parameters
These parameters are necessary to establish a per-VC connection. They include entries such as UPC
actions, various bandwidth-related items, per-VC thresholds and hardware-specific items.
•
Class of Service Buffers (Qbins)
These parameters provide Quality of Service (QoS) support. Full QoS implies that each VC is
served through one of a number of Qbins which are differentiated by their QoS characteristics.
The SES PNNI Controller (VSI master) uses the Service Class Templates to configure the appropriate
type of ATM connection.
When an ATM SVC connection setup request is received from the VSI Master in the SES PNNI
Controller, the VSI slave (as in the BXM) uses the SCT index of the request to retrieve the
corresponding set of extended parameters defined in the template for the corresponding index. The
slave uses these values to complete the connection setup and program the hardware.
The general types of parameters passed from a VSI Master to a Slave include:
•
Service type identifier
•
QoS parameters (such as CLR, CTD, CDV)
•
Bandwidth parameters (such as 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 the following:
•
ATM Forum service types
•
AutoRoute
•
MPLS
Cisco SES PNNI Controller Software Configuration Guide
1-20
Release 1, Part Number 78-6123-05 Rev. A0, March 2001
Chapter1
SES PNNI Controller Overview
AutoRoute and PNNI
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 that match the index. The firmware then programs the hardware with the
applicable extended parameter values to complete the connection setup.
Service Class Templates on the BPX are maintained by the BCC and downloaded to the BXM cards as
part of the card configuration process occurring as a result of card activation, rebuild, or switchover.
Note
In Release 9.2 the templates are not configurable.
Qbin Templates
A BXM class of service buffer (Qbin) is specified for each service type to be used. The Qbin buffers
provide the separation of service type to match the QoS requirements. This mapping defines a
relationship between the template and the Qbin interface configuration.
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 interface’s Qbin configuration parameters can be changed
on a per interface basis. Such changes affect only that interface’s Qbin and no others. Changes do not
affect the Qbin templates.
Only Qbin templates are used with Qbins available to VSI partitions; namely Qbins 10 through 15.
Qbins 10 through 15 are used by the VSI (on interfaces configured as trunks or ports.
Qbins 0 through 9 are reserved for and configured by AutoRoute.
AutoRoute and PNNI
This section introduces the major ATM SVC applications supported by the PNNI controller:
•
SVC with PNNI Routing
•
SVC with Mixed PNNI and IISP Networks
•
SVP, SPVC, SPVP
•
PNNI and AutoRoute co-existence on the Network
Cisco SES PNNI Controller Software Configuration Guide
Release 1, Part Number 78-6123-05 Rev. A0, March 2001
1-21
Chapter1
SES PNNI Controller Overview
AutoRoute and PNNI
SVC with PNNI Routing
The SES PNNI node supports SVC applications with PNNI routing (Figure1-12). PNNI routing
protocol runs between ATM switches. The network topology information and routing information are
exchanged between ATM switches via PNNI routing protocol. The routing path from a calling CPE to
a called CPE is dynamically selected based on current network traffic and resource conditions.
Note
A PNNI network uses AutoRoute functions for network timing.
Figure1-12 PNNI Network
SVC with Mixed PNNI and IISP Networks
Where SVC applications contain both IISP and PNNI networking, IISP runs on the edges of a PNNI
network and interconnects non-PNNI networks via a backbone PNNI network (Figure1-13). IISP
maintains a set of static routing tables to direct signaling between a non-PNNI network and a PNNI
network. The static routing information can be advertised into PNNI network through boundary
switches (namely, switches #4 and #6 in the illustration). With static route advertising, the end system
A on the non-PNNI network #a can place a call to the end system C on the non-PNNI network #b.
Because the PNNI network is running PNNI 1.0 Signaling, and IISP is based on UNI 3.1 Signaling, IE
mapping between PNNI 1.0 and UNI 3.1 occurs on the boundary switches # 4 and #6.
Cisco SES PNNI Controller Software Configuration Guide
1-22
Release 1, Part Number 78-6123-05 Rev. A0, March 2001
Chapter1
SES PNNI Controller Overview
AutoRoute and PNNI
Figure1-13 PNNI Network with IISP Trunks
PNNI and AutoRoute Co-existence on the Network
A SES PNNI network allows both PNNI and AutoRoute networks to coexist in the same physical
network (Figure1-14). The illustration shows switches #1 through #6 all participating in the PNNI
network, while switches #4, #5, and #6 are part of AutoRoute network. The trunks between switch #4
and switch #5, and between switch #5 and switch #6, carry both AutoRoute and PNNI traffic on the
same physical trunk. The trunk bandwidth is partitioned between AutoRoute and PNNI traffic at trunk
initialization stage.
Cisco SES PNNI Controller Software Configuration Guide
Release 1, Part Number 78-6123-05 Rev. A0, March 2001
1-23
Chapter1
SES PNNI Controller Overview
User Interfaces and Network Management
Figure1-14 Mixed AutoRoute and PNNI Networks
User Interfaces and Network Management
The following tools are used to control and manage the SES PNNI node:
•
Configuration and Network Management Tools
•
Auto Configuration Tools
These tools are used on the PNNI Controller, the BPX 8600, CWM, and CiscoView.
Cisco SES PNNI Controller Software Configuration Guide
1-24
Release 1, Part Number 78-6123-05 Rev. A0, March 2001
Chapter1
SES PNNI Controller Overview
User Interfaces and Network Management
Configuration and Network Management Tools
All user interfaces use control point software to access the SES PNNI Controller. The control point
software interacts with the PNNI, SVC, VSI, and platform software.
The four main interfaces used to configure and operate an SES PNNI node are as follows:
1. SES Command Line Interface
The SES CLI can be used for low-level configuration and access to the SES PNNI Controller.
2. BPX Command Line Interface
An SES PNNI node consists of a SES PNNI Controller and a BPX switch. The BPX switch is
configured and operated with the standard BPX switched software commands described in the
Cisco WAN Switching Command Reference.
3. Cisco WAN Manager
The Cisco WAN Manager provides network management functions for a SES PNNI network. These
functions are described in Chapter 7, “Network Management”. These features include the
following:
Note
•
Topology—The physical topology of the nodes in the network are provided. The SES will
appear as a shelf under the BPX. CWM can only show physical topology.
•
Traps display—All traps display in the form consistent with all other
BPX/MGX 8850 traps and use the existing applications on the CWM.
•
Network Browser—The Network Browser is enhanced to indicate which trunks are PNNI
trunks and will display additional state information related to PNNI on these trunks.
•
Config/Restore—The configuration saves and restores using the standard CWM application.
•
Image Download—The software images download to SES using the standard CWM download
mechanism.
IP connectivity to the SES PNNI Controller is provided by using the inband IP Relay
capability of AutoRoute. Therefore, AutoRoute will still be required in the network. Its
main function will be for the use of IP Relay, Time of Day propagation, and Network
Clock Sync. (Out-of-band network management connectivity is also provided through the
Serial and Ethernet interfaces on the PXM.) These services will be provided in a pure
PNNI network (namely, one that does not use AutoRoute) in a future release.
4. CiscoView
CiscoView can be used to configure some aspects of a SES PNNI Controller, PNNI routing, and
ATM SVCs/SPVCs. The CiscoView functions that are specific to the SES PNNI Controller are
described in Chapter 7, “Network Management”.
Provisioning Data Saving
Configuration data is written to the disk and the DRAM when configuration is changed. This data is
used to initialize the PXM upon reset. Configuration data can be saved on an external server such as
CWM via configuration upload. Configuration data can also be saved in a separate file and restored later
if necessary.
Cisco SES PNNI Controller Software Configuration Guide
Release 1, Part Number 78-6123-05 Rev. A0, March 2001
1-25
Chapter1
SES PNNI Controller Overview
User Interfaces and Network Management
System Error Log
The SES PNNI Controller maintains a log of system errors in BRAM. This log contains crucial system
details, and should be read prior to a system reset.
Real Time Cell Statistics and Call Statistics
CWM provides remote access to cell statistics from physical interfaces and SES PNNI Controller.
Event Log
The SES PNNI Controller maintains log files on system disk to log events in the system.
SNMP
The SES PNNI Controller complies with SNMP VI. The Management Information Base (MIBs) used
by the SES PNNI Controller are described in Appendix C, “SNMP Management Information Base.”
SNMP Error Log
The SNMP Error log provides SNMP error details to the Cisco WAN Manager. CWM maintains a
sequential log ordered list of Error Events for each SNMP Manager.
Trap/Alarm Log
Alarms generated by theSES PNNI Controller are mapped into traps and sent to the CWM. The SES
provides support for Robust Trap Messages. Trap messages are maintained in a circular buffer, with the
latest message overwriting the oldest. Each trap is labelled with a sequence numbers. By using these
sequence numbers, management stations can request previously issued traps that were not received.
Auto Configuration
The SES PNNI nodes are preconfigured with Cisco ATM address prefixes, which are combined with
the preconfigured MAC address of the switch to form a unique node identifier. These are used to
configure both attached ATM end systems and to automatically bring up the PNNI routing hierarchy for
simple network configurations.
Cisco SES PNNI Controller Software Configuration Guide
1-26
Release 1, Part Number 78-6123-05 Rev. A0, March 2001
C H A P T E R
2
Redundancy and Serviceability
Redundancy means redundant cards are integrated into the switch as standbys. When a primary card
malfunctions, the associated standby will take over and continue the services originally provided by the
primary hardware component. A user can achieve the following with redundancy:
•
No disruption of call traffic in case of hardware failure on one card
•
Preservation of call states in case of hardware failure
•
Gives time to get the hardware failure rectified without affecting the existing operations
This chapter describes redundancy and serviceability in following sections:
•
PXM Redundancy
•
SES Uplink Redundancy
•
BXM Redundancy
•
System Availability and Switch Over
PXM Redundancy
This section describes the following aspects of PXM redundancy:
•
platform redundancy
•
PNNI redundancy
•
call redundancy
•
provisioning redundancy and persistency
Platform Redundancy
The SES platform replicates the following information from active PXM to standby PXM to support
PXM redundancy:
1. Images downloaded on the active card get replicated to the standby.
2. System name if changed on the active card gets replicated to the standby.
3. Run time IP changed through the ipifconfig command on the active card gets replicated to the
standby.
4. Sys logs are maintained to be the same on both active and standby cards.
Cisco SES PNNI Controller Software Configuration Guide
Release 1, Part Number 78-6123-05 Rev. A0, March 2001
2-1
Chapter2
Redundancy and Serviceability
PXM Redundancy
5. Users added through the adduser command on the active card are added to the standby as well.
6. Configuration of users through the cnfuser command is also replicated to the standby.
7. Deletion of users on the active card through the deluser command results in their deletion on the
standby as well
8. Trap Manager added on the active card through the addtrapmgr command gets replicated to the
standby as well.
9. APS configuration done on the active card through the addapsln , delapsln, and cnfapsln
commands gets reflected on the standby as well.
PNNI Redundancy
The PXM consists of an active card and a standby processor card operating as a hot-redundancy pair.
The SVC redundancy scope includes the following:
•
preservation of provisioning data
•
reservation of switch configuration data
•
reservation of call state data
•
PNNI Controller Cold Start or Initialization and the rebuild of the persistent data
Data redundancy is accomplished through updates messages from the Active controller to Standby. Data
persistency is accomplished through disk storage at Active and Standby controller. Both the standby
update and disk read/write operation are supported by the SES platform software.
The data persistency and redundancy model for the configuration information and run time data base
on a PNNI Controller are managed in the following way:
•
Provisioning—Provisioning data at the PNNI Controller via CLI or the NMS. This data is
redundant and persistent.
•
Switch Config —Provisioning at the BPX switch and learned through VSI protocol. They are
redundant but not persistent. All dynamic information is sent on a timer; not on real-time.
•
CPE ILMI address registration—They are delivered to PNNI controller by the VSI PassThrough
mechanism. The ILMI registered address is redundant, but not persistent. If the PNNI controller
switchover or rebuilt, they are “uploaded” from the switching module.
•
Call—SVC call database, they are redundant but not persistent.
•
SPVC
– addcon/delcon/cnfcon commands from CLI are persistent and redundant.
– Route optimization commands are persistent and redundant.
– Dynamic information related to SPVCs is sent to standby in the same way as call redundancy.
•
Routing Tables —Generated by PNNI for call routing. Routing tables are generated and updated
during PNNI controller’s normal operation; hence, they are not redundant nor persistent
•
Dynamic —Includes all run-time states, transit buffers and data structures of the PNNI Controller
Application, they are not redundant nor persistent.
Cisco SES PNNI Controller Software Configuration Guide
2-2
Release 1, Part Number 78-6123-05 Rev. A0, March 2001
Chapter2
Redundancy and Serviceability
SES Uplink Redundancy
Call Redundancy
To support call redundancy, the call states and a minimum set of connection information are sent to the
standby PNNI controller. The Call Control Blocks (CCB) task manages the call database, while the
Redundancy Manager task manages the standby updates when call becomes active or release.
The standby update function of the Redundancy Manager task is kicked off by a periodic timer. When
the call becomes active at active CCB, the call data structures are converted into a single Active Call
record and put on the update tracking queue of the Redundancy Manager task. When the Redundancy
Manager task kick off after timer expires, all active call records are sent to the standby PXM. There is
a delay in SVC call availability to the standby PAM after it is made available on the active side. When
a switchover is initiated, some SVC calls made after the timer expires can be lost. However, the loss is
minimal.
When a call is releasing, the Active Call record is removed from both the active BCC and the standby
BCC. Similar to adding active call record to the standby PXM, all call record removing queries to the
standby PXM are sent to the update tracking queue of the Redundancy Manager task until update timer
expires.
Provisioning Redundancy and Persistency
Provisioning is an infrequent event, but it is required that the data be sent to Standby and Disk before
the acknowledgement is returned to the user. Any data learned dynamically from the switch is sent on
a 250 millisecond timer.
The redundancy and persistency provisioning process is as follows:
1. Provisioning request is made on the NMS or CLI.
2. Request is sent to CCB.
3. When the provisioning is done, CCB sends a provisioning redundancy request to the Redundancy
Manager task.
4. Redundancy Manager task sends out a standby redundancy update to the standby PXM. Unlike call
record redundancy, there is no timer delay provisioning data sent to the standby PXM.
5. Standby PXM sends a disk persistency update.
6. Redundancy Manager task sends a response message to the NMS or CLI. Once the response
message is returned without an error, redundancy and persistency data is guaranteed, and all the
provisioning information is written to the disk on the redundancy side.
SES Uplink Redundancy
SES supports three different uplink redundancy configurations:
•
DS3/E3 Y cable redundancy (Y-red)
•
OC3 Y cable redundancy (Y-red)
•
OC3 APS 1+1 redundancy
Y cable redundancy provides:
•
No disruption of traffic on a front card switchover
APS redundancy provides:
•
No disruption of traffic in case of a hardware failure on one of the trunk back cards
Cisco SES PNNI Controller Software Configuration Guide
Release 1, Part Number 78-6123-05 Rev. A0, March 2001
2-3
Chapter2
Redundancy and Serviceability
BXM Redundancy
•
Protection against signal degradation and failures on the active line. In this case the other line, if
healthy, will take over as active line.
•
No switchover on PXM front card in case of line failure
BXM Redundancy
The BXM hot standby redundancy function pre-programs the slave standby BXM card the same as the
active BXM card. When the active card fails, the slave card switch over operation can be done quickly
(within 250 ms). Table2-1 describes the hardware supported by BXM redundancy.
Table2-1
BXM Redundancy—Supported Hardware
Hardware
Type of Support
OC3 APS 1+1
Supported on AutoRoute and PNNI.
OC3 APS 1 by 1
Supported only on AutoRoute.
DS3 y-red
Supported on AutoRoute and PNNI.
E3 y-red
Supported on AutoRoute and PNNI.
Table2-2 describes the three forms of BXM redundancy.
Table2-2
BXM Redundancy Types
Type of Redundancy
Function
AutoRoute combus configuration Provides backward AR compatibility.
message redundancy
VSI slave configuration message
and connection data base
redundancy
Supported when a standby BXM card is plugged in.
ILMI configuration message and Supported when a standby BXM card is plugged in
data base redundancy
and ILMI function on the active BXM card is
turned on.
Cisco SES PNNI Controller Software Configuration Guide
2-4
Release 1, Part Number 78-6123-05 Rev. A0, March 2001
Chapter2
Redundancy and Serviceability
BXM Redundancy
Figure2-1 shows how redundancy is performed between active card and standby card.
Figure2-1
BXM Redundancy Example
The VSI master resides in the PXM controller card. The VSI slaves reside on the BXM cards. Without
VSI operation, the BXM card provides the hot standby mechanism by duplicating combus messages
from BCC to standby BXM card. (The flow of this operation is shown by broken lines in Figure2-1.)
With VSI operation, the active slave card forwards any VSI configuration messages it receives from the
master VSI controller to standby slave VSI card. (The flow of this operation is shown by the continuous
line in Figure2-1.) When the standby BXM card is activated by the user, the active BXM card forwards
all Combus/VSI/ILMI configuration messages it received from the master VSI controller to the standby
BXM card.
Cisco SES PNNI Controller Software Configuration Guide
Release 1, Part Number 78-6123-05 Rev. A0, March 2001
2-5
Chapter2
Redundancy and Serviceability
BXM Redundancy
The hot standby operations between active and standby card are performed as below:
Step 1
AutoRoute ComBus configuration messages are duplicated to standby slave VSI card by BCC.When
standby BXM card starts up, it retrieves all VSI configuration messages from active slave VSI card and
processes these messages.
Step 2
VSI configuration messages (from Master VSI controller or other slave VSI card) are forwarded to
standby slave VSI card by active slave VSI card.
Initial Data Transfer (Standby Card Retrieval)
When a standby VSI card is plugged in or reset, the standby card retrieves all VSI configuration
messages and connection data bases from the active card. The standby will also check to see if ILMI is
enabled on the card. If ILMI is enabled, the standby card will try retrieve the ILMI database from the
active card.
The following ILMI data bases on the active card need to be retrieved by the standby card:
•
Network Prefix database
•
ATM Layer parameters database
•
Address database
•
ILMI Operation parameters
•
Link Status
The database retrieval will be done by the existing vsi passthru protocol. The standby VSI card will act
like a VSI master and use the VSI interface functions (VSI get and getmore commands) to retrieve the
VSI/ILMI databases. Normal data transfers and switchovers happen as described below:
•
Normal Data Transfer (Active Card Forwarding)
When the active card detects that it has a redundant standby card associated with it, it will take any
VSI/ILMI configuration messages from the VSI master and forward them to the standby VSI card.
In addition, any ILMI traps from the active ILMI task will be forwarded to the standby ILMI task.
•
SwitchOver Condition
The standby card’s VSI task will inform the ILMI task that the standby card has now become active.
The old active card’s VSI task will inform the ILMI task that it has become the standby card, and
it will perform the Initial Data Transfer to retrieve all configuration message and data base from the
newly active BXM card. On switchover, the VSI master will issue a resync command to resync VSI
and ILMI data base with the newly active slave card.
Redundancy Procedures
To make a standby BXM card a hot-standby card, the user executes the addyred command from the
BCC CLI.
To remove the hot-standby status of a BXM card, the user executes an delyred command from the BCC
CLI. The primary card of the redundancy pair will become the active card after delyred is issued. This
would be the case even the secondary card was active before.
To perform a switchover from an active card to the hot-standby card, the user executes a switchyred
command from the BCC CLI, or removes the active BXM card from its slot.
Cisco SES PNNI Controller Software Configuration Guide
2-6
Release 1, Part Number 78-6123-05 Rev. A0, March 2001
Chapter2
Redundancy and Serviceability
System Availability and Switch Over
System Availability and Switch Over
The SES PNNI node achieves system availability through the use of the following features:
•
Provisioning Data Base Redundancy
•
System System Call Redundancy
•
SES PNNI Controller Switch-over
•
BPX BCC Switchover
•
Y-redundancy BXM card switchover
•
Y-redundancy BXM trunk switch-over (BXM APS/PXM APS)
System Call Redundancy
Call redundancy applies to the connections as follows:
•
Control PVC connections, which are used to deliver the control messages to and from the line/trunk
port to the SES PNNI controller signaling handling processes.
•
Control SVC connections, which are used to deliver the control messages between the SES PNNI
controller node.
•
SVC connections requested from the CPE.
Table2-3
Call Redundancy Functions
Occurrence
Call Redundancy Result
SES PNNI controller switch-over
All active connections (SVCs/SPVCs) are preserved.
Platform Controller switch-over
All active connections are preserved.
Y-redundancy line card switch-over
All active connections are preserved.
Y-redundancy trunk card switch-over
All active connections are preserved.
SES PNNI controller software upgrade or All active connections are preserved.
downgrade
Standalone SES PNNI controller
configuration fail-over
All active SVC connections are release.
Standalone platform controller
configuration fail-over
All active SVC connections are release.
Cisco SES PNNI Controller Software Configuration Guide
Release 1, Part Number 78-6123-05 Rev. A0, March 2001
2-7
Chapter2
Redundancy and Serviceability
System Availability and Switch Over
Switch Over
SES PNNI Controller Switch-over
The PNNI redundant controller supports forced switchover. A forced switchover occurs under the
following circumstances:
•
the active controller receives a switchcc or resetcd command.
•
a critical error affects the active controller.
During a forced switchover, the system shuts down the active controller, and the standby controller
resumes the active role as described in the following steps:
Step 1
The active controller encounters a fatal error, or receives a switchcc (or resetcd) command, and is
warm rebooted.
Step 2
The standby controller resumes the active role, and its applications transition to an ACTIVE_READY
state. During this transition, the synchronization of the RAM and the disk is ensured. Asynchronously,
it is also waiting for the newly-standby entity to be ready for RAM synchronization.
Step 3
The newly-initialized entity is asked to resume a standby role. During the transition, it performs the RAM is
synchronized with the newly-active entity.
Regardless of whether it is fatal or on-demand, a forced switchover will be carried out despite any
controller congestion.
During a SES PNNI controller switchover, active connections in the SES PNNI controller component
database will be maintained with no impact on the user data plane. Connections in the process of being
set up, or not yet mirrored on the standby processor, are released. The control PVC connections are
re-established. The signaling layer 2 of the UNI and PNNI will be restarted, but the layer 3 database is
preserved.
Post-Switchover Operations
Post-switchover operations are carried out after a switchover. The post-switchover operations are as
follows:
1. Node internal VSI master/slave communications are re-established.
2. Node external SSCOP link is re-established.
3. Node external PNNI RCC link is re-established.
4. Interface resync between the VSI master/slave switch and interface info is performed.
5. Node external routing/topology info is rebuilt.
6. Node external call state resync (SSCOP Status Enquiry) is performed.
7. Node internal call Release Pending queue is processed.
8. Node internal VSI master/slave connection resync is performed.
New SVC calls can be made when steps 1 and 2 are both done.
Cisco SES PNNI Controller Software Configuration Guide
2-8
Release 1, Part Number 78-6123-05 Rev. A0, March 2001
Chapter2
Redundancy and Serviceability
System Availability and Switch Over
Congestion Management of Post-Switchover Operations
Because of the possibly large-scale post-switchover operations and the need for handling normal
controller operations after the switchover as early as possible, the controller is considered in congestion
right after normal switchover. Under switchover congestion, some thresholds are controlled so both
normal controller operations and post-switchover operations can be performed smoothly at the same
time.
Note
Maximum call rate may not be sustained during a resync.
Note
During switch over and re-sync, system may not be able to sustain the normal full call
setup rate due to CPU utilization.
Note
The current redundancy backup has an one-second window to back up the active calls to
the standby. When the controller switches over, it may have some inconsistent active call
records with switch platform. After the VSI re-synchronizes, it eliminates the
inconsistency between the controller and switch platform. Calls established within the last
one second before the switchover may be deleted.
Stand-alone SES PNNI Controller fail-over
In the standalone SES PNNI controller configuration, upon its fail-over, SVC connections are
re-initiated by the ATM CPE. SPVC connections are re-initiated by the master endpoints of SPVCs.
BPX BCC Switchover
BCC switchovers are managed by the BPX switch. The new active BCC are synchronized with the SES
PNNI controller. Mismatched connections are released.
Y-redundancy BXM card switchover
The Y-redundancy BXM card switch-over is managed by the BPX switch. The new active BXM card
are synchronized with the SES PNNI controller. Mismatched connections are released.
Y-redundancy BXM trunk switch-over
The Y-redundancy BXM trunk switch-over is managed by the BPX switch. The new active BXM trunk
is synchronized with the SES PNNI controller. Mismatched connections are released.
Cisco SES PNNI Controller Software Configuration Guide
Release 1, Part Number 78-6123-05 Rev. A0, March 2001
2-9
Chapter2
Redundancy and Serviceability
System Availability and Switch Over
Cisco SES PNNI Controller Software Configuration Guide
2-10
Release 1, Part Number 78-6123-05 Rev. A0, March 2001
C H A P T E R
3
2
Getting Started
This chapter describes how to set up general switch features that apply to multiple switch interfaces.
This chapter starts with a configuration quickstart procedure, which introduces the configuration tasks.
The following sections provided detailed information on how to complete the configuration tasks.
Configuration Quickstart
The quickstart procedure in this section provides a summary of the tasks required to configure the
SES. This procedure is provided as an overview and as a quick reference for those who have already
configured the SES.
Step1
Command
Purpose
username
Start a configuration session. (Refer to “Establishing and
Ending a CLI Management Session,” page 3-2.)
password
Step2
adduser [username] <accessLevel>
cnfpasswd [username]
Configure administrator access. (Refer to “Configuring
Administrator Access,” page 3-10.)
deluser [username]
Step3
cnfname <node name>
Configure the switch name. (Refer to “Setting and Viewing
the Switch Name,” page 3-14.)
Step4
dspdate
Configure the switch time. (Refer to “Viewing and Setting
the Switch Date and Time,” page 3-14.)
cnfdate <mm:dd:yyyy >
cnftmzn <timezone >
cnftmzngmt <timeoffsetGMT>
cnftime <hh:mm:ss>
Step5
dspcds
dspcd
Verify the hardware configuration. (Refer to “Verifying the
Hardware Configuration,” page 3-15.)
cc <slotnumber >
Step6
dspred
Verify PXM card redundancy configuration, if two cards
are installed. (Refer to “Managing Redundant Cards,” page
3-19.)
Cisco SES PNNI Controller Software Configuration Guide
Release 1, Part Number 78-6123-05 Rev. A0, March 2001
3-1
Chapter3
Getting Started
Establishing and Ending a CLI Management Session
Step7
Command
Purpose
dspcds
Verify firmware versions installed and configure version to
use for each card. (Refer to “Managing Firmware Version
Levels for Cards,” page 3-20.)
setrev <slot> <Primary revision>
<secondary revision>
Step8
No CLI commands needed to configure
Clocksource
No clocking configuration is required for the SES. Clock
Source is pre-set to use the uplink for the in-band clock
source. (Refer to “Managing Network Clock Sources,”
page 3-23.)
Step9
No CLI commands needed to configure
the PNNI controller on the SES.
No PNNI controller configuration is required for the SES.
Controller configuration is done through a BPX 8600
switch.(Refer to “Configuring the PNNI Controller,” page
3-24.)
For more information, refer to Chapter 5, “Configuring
ATM SVCs, PNNI Routing,” and SPVCs”.
Step10
cnfsnmp community [string]
cnfsnmp contact [string]
Configure SNMP management. (Refer to “Configuring for
Network Management,” page 3-24.)
cnfsnmp location [string]
dspsnmp
Step11
saveallcnf
Save the switch configuration. (Refer to “Saving a
Configuration,” page 3-25.)
Establishing and Ending a CLI Management Session
The Command Line Interface (CLI) management tool allows you to configure the SES and display the
switch status. All the configuration and monitoring procedures described in this book use the CLI tool.
While the switch does support management from Cisco WAN Manager (CWM) or an SNMP manager,
you must begin your configuration using the CLI. Before other tools can connect the switch, you must
use the CLI to configure the switch to support those tools.
To configure the switch using the CLI, you can use either of the following methods:
•
Directly-attached terminal
•
Telnet workstation with an IP connection to the SES
You must begin the configuration with a directly attached terminal. To enable Telnet client
management, you must configure the appropriate IP interfaces on the switch.
The following sections describe how to establish CLI management sessions using a directly-attached
terminal, how to configure the switch to support CLI sessions over IP, and how to establish CLI sessions
over IP.
Cisco SES PNNI Controller Software Configuration Guide
3-2
Release 1, Part Number 78-6123-05 Rev. A0, March 2001
Chapter3
Getting Started
Establishing and Ending a CLI Management Session
Starting a CLI Session with a Directly-Attached Terminal
For instructions on physically connecting a terminal directly to the switch, refer to the instructions in
the Cisco Service Expansion Shelf Hardware Installation Guide, Release 1.0 .
The terminal you use should emulate a VT-100 terminal. You can use any personal computer or UNIX
workstation and a terminal emulation program that emulates the VT-100.
To begin configuration, use the following procedure.
Step 1
After you connect the terminal or computer to the control port (CP), turn on the terminal or start the
terminal session.
For instructions on operating the terminal or terminal emulation program, refer to the documentation
for that product.
Step 2
If the Login prompt does not appear, press Enter. The Login prompt comes from the switch and
indicates that the terminal connected successfully to the switch.
Step 3
When the
Login
Step 4
When the
password
prompt appears, enter the user name provided with your switch and press Enter.
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:
spirit.1.PXM.a >
The CLI prompt uses the following format:
nodename.slot.cardtype.state>
nodename
Name of the node. To change the name, see “Setting and Viewing the Switch Name,”
which appears later in this chapter.
slot
Indicates the slot number of the card you are connected to.
cardtype
Identifies the model of the card: PXM.
state
Card state is active (a), standby (s), or initialized (i). Cards are labeled as initialized
during switch startup.
Once you complete the procedure above, you establish a configuration session. You are ready to begin
configuration. The next two sections describe how to enable a configuration for Ethernet and dial-up
connections.
Cisco SES PNNI Controller Software Configuration Guide
Release 1, Part Number 78-6123-05 Rev. A0, March 2001
3-3
Chapter3
Getting Started
Establishing and Ending a CLI Management Session
Configuring IP Connectivity on the SES
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
The following sections describe how to configure the switch to support IP communications through the
Ethernet and dial-up ports on the PXM.
Preparing for IP Communications through the PXM LAN Port
Before you can manage the switch through the PXM LAN port, you must first assign an IP address to
the LAN port. This Ethernet LAN port is located on the PXM back card. For instructions on physically
connecting a terminal or workstation to this port, refer to the Cisco Service Expansion Shelf Hardware
Installation Guide, Release 1.0 .
To configure an IP address for the PXM LAN port, use the following procedure.
Step 1
Establish a configuration session through a directly attached terminal as described in the previous
section, “Starting a CLI Session with a Directly-Attached Terminal.”
Step 2
Verify that the IP address is not already configured by entering the dspipif command:
spirita.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).
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:
spirita.1.PXM.a> ipifconfig lnPci0 < 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.
Note
Tips
The mask value should be identical to the net_mask value. When set to different
values, netmask becomes a sub_netmask by default. Do not set netmask unless
you want to build a complicated SNMP network by using a subnet.
Use the same subnet for all IP addresses defined on all SESs. This simplifies router
configuration.
Cisco SES PNNI Controller Software Configuration Guide
3-4
Release 1, Part Number 78-6123-05 Rev. A0, March 2001
Chapter3
Getting Started
Establishing and Ending a CLI Management Session
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 management through the PXM Ethernet port.
Preparing for IP Communications through the Dial-Up Interface
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 as described earlier in “Starting
a CLI Session with a Directly-Attached Terminal.”
Step 2
Verify that the IP address is not already configured by entering the following 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).
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.
Tips
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, Part Number 78-6123-05 Rev. A0, March 2001
3-5
Chapter3
Getting Started
Establishing and Ending a CLI Management Session
Start a CLI Telnet Session from a LAN Workstation
Before you can establish a CLI Telnet session from a LAN workstation, you must configure one of the
following switch interfaces to support IP connectivity:
•
Ethernet LAN port on the PXM
•
ATM SVC on a PXM card
The procedure for configuring the PXM LAN port is described in the previous section. The procedure
for configuring the ATM interface is described in AppendixB, “Preparing for IP Communications over
an ATM Interface.”
After the appropriate interface is configured and a physical path is established to the SES, you can start
a CLI session using a workstation with a Telnet program and the switch’s IP address. To establish a CLI
management session, use the following procedure.
Step 1
At a workstation that has a path to the switch, start the Telnet program with a command similar to the
following:
C:>telnet ipaddress
Replace ipaddress with the IP address assigned to the switch.
Note
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 the Login prompt does not appear, press Enter.
The Login prompt comes from the switch and indicates that the terminal has successfully connected to
the switch.
Step 3
When the
Login
Step 4
When the
password
prompt appears, enter the user name provided with your switch and press Enter.
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:
spirita.1.PXM.a >
Cisco SES PNNI Controller Software Configuration Guide
3-6
Release 1, Part Number 78-6123-05 Rev. A0, March 2001
Chapter3
Getting Started
Establishing and Ending a CLI Management Session
The CLI prompt uses the following format:
nodename.slot.cardtype.state>
nodename
Name of the node. To change the name, see “Setting and Viewing the Switch Name,”
which appears later in this chapter.
slot
Indicates which card you are configuring. For most general switch configuration
procedures, you need to configure the switch using the PXM cards in slots 1 or 2. For
many trunk configuration procedures, you need to modify a PXM card.
cardtype
Identifies the model of the card: PXM.
state
Card state is active (a), standby (s), or initialized (i). Card is labeled initialized during
switch startup.
When you complete the above procedure, a CLI session is established. You are ready to begin switch
configuration and monitoring.
Start a Dial-Up CLI Telnet Session from a Workstation
Before you can establish a dial-up CLI Telnet session from a workstation, you must configure an IP
address for the maintenance port as described in “Preparing for IP Communications through the
Dial-Up Interface.” You must also install the correct hardware to support dial-up communications. For
instructions on preparing the switch for dial-up communications through the maintenance port, refer to
the instructions in the Cisco Service Expansion Shelf Hardware Installation Guide, Release 1.0.
After the maintenance port interface is configured and a physical path is established to the SES, you
can start a CLI session by establishing a dial-up connection from the workstation to the switch and
directing a Telnet session to the switch’s IP address. To establish a CLI management session, use the
following procedure.
Step 1
After you connect to the workstation to a phone line, establish a dial-up connection to the switch.
Note
Step 2
You will need the telephone number for the line connected to the modem at the
switch. For instructions on establishing the connection to the switch, refer to the
documentation for the workstation and the attached modem.
Start the Telnet program with a command similar to the following:
C:>telnet ipaddress
Replace ipaddress with the IP address assigned to the switch.
Note
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.
Cisco SES PNNI Controller Software Configuration Guide
Release 1, Part Number 78-6123-05 Rev. A0, March 2001
3-7
Chapter3
Getting Started
Establishing and Ending a CLI Management Session
Step 3
If the Login prompt does not appear, press Enter.
Note
The Login prompt comes from the switch and indicates that the terminal
successfully connected to the switch.
Step 4
When the
Login
Step 5
When the
password
prompt appears, enter the user name provided with your switch and press Enter.
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:
spirita.1.PXM.a >
The CLI prompt uses the following format:
nodename.slot.cardtype.state>
nodename
Name of the node. To change the name, see “Setting and Viewing the Switch Name,”
which appears later in this chapter.
slot
Indicates the slot number of the card you are configuring: 1 or 2.
cardtype
Identifies the model of the card: PXM.
state
Card state is active (a), standby (s), or initialized (i). Cards are labeled as initialized
during switch startup.
Once you complete the above procedure, you establish a CLI management session. You are ready to
begin configuration.
Ending a CLI Management Session
To end a CLI management session, enter the bye command.
Note
This command ends the CLI session. It does not terminate the phone call when you use a
dial-up connection.
To restart the session after entering the bye command, press Return and the switch will prompt you for
a username and password.
Cisco SES PNNI Controller Software Configuration Guide
3-8
Release 1, Part Number 78-6123-05 Rev. A0, March 2001
Chapter3
Getting Started
Entering Commands at the Switch Prompt
Entering Commands at the Switch Prompt
The commands in the switch operating system are associated with the cards that are installed in the
switch. Before you execute a command, you must select a card that supports the command. 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:
spirita.1.PXM .a >
To select another card in the switch, enter the following command:
spirita.1.PXM.a >
cc <slotnumber >
Replace slotnumber with the number of the slot in which the card you want to manage is installed Valid
slot numbers for PXM cards are 1 and 2.
spirita.2.PXM .a >
If you have trouble executing a command, look at the switch prompt to see if you have selected the
correct card and type for the command. The following example shows the response to an unrecognized
command:
spirita.1.PXM.a > dspport
ERR: unknown command: "dspport"
Tips
The command examples include the switch prompt to verify which card type supports a
command. Also, commands can be entered without options. When a command is entered
without an option, the last value defined for that option is maintained.
The following example demonstrates that the switch recognizes partial commands and displays long
reports one page at a time.
spirita.1.PXM.a > he
Available commands
-----------------?
abortofflinediag
abortrev
addaddr
addapsln
addchan
addcon
addfltset
addlmiloop
addmaster
addpnni-node
addpnni-summary-addr
addpnport
addprfx
addserialif
addslave
addtrapmgr
adduser
Type <CR> to continue, Q<CR> to stop:
Because the help command is the only command that begins with he, you can use the abbreviated he
command to display help. 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.
Cisco SES PNNI Controller Software Configuration Guide
Release 1, Part Number 78-6123-05 Rev. A0, March 2001
3-9
Chapter3
Getting Started
Getting Help for Commands
The following example demonstrates what can happen when a command is entered at the wrong card
prompt.
spirita.2.PXM.s > ipifconfig
ERR: command unavailable in current card state
This command is available only on the active card and not on the standby card.
Getting Help for Commands
The switch operating system provides two ways to display information on commands. To display a list
of all the commands available, enter the following command:
spirita.1.PXM .a > help
To display the syntax of a command, enter the command without any parameters. The following
example shows the syntax report provided by the switch using the addport command.
spirita.1.PXM.a > addpnport
ERR: incorrect number of parameters: (not enough)
Syntax: addpnport <portid>
shelf.slot:subslot.port:subport -[shelf.]slot[:subslot].port[:subport]default=Mandatory Parameter
possible errors are:
NULL
Note
Some commands, such as dspcd and saveallcnf, do not require parameters. 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
or reduce switch performance.
Configuring Administrator Access
The username and password supplied with your switch provides access to all customer accessible
features within the switch and allows you to add and delete users and change user passwords.
When configuring administrator access for the switch, consider the following recommendations:
•
Share the Cisco-provided username and password with only one or two people.
•
If the Cisco-provided username and password become common knowledge during the switch
installation and configuration, create a new top-level username and password, and delete the
original username and password.
•
If additional administrators need access to the switch, create usernames and passwords below the
top level so that these administrators cannot access or modify the top level user information.
The following sections describe how to add users, change passwords for existing users, and delete users.
Cisco SES PNNI Controller Software Configuration Guide
3-10
Release 1, Part Number 78-6123-05 Rev. A0, March 2001
Chapter3
Getting Started
Configuring Administrator Access
Adding Users
When you add users to the switch, you must specify the following information for each user:
•
user name
•
password
•
access level
The user name and password identify the user when the user wants to manage the switch. The access
level you specify determines which commands the user can use and at which levels the user can add
users or modify user configurations.
To add a user to the switch, use the following procedure.
Step 1
Establish a configuration session as described in “Establishing and Ending a CLI Management
Session,” earlier in this chapter.
Step 2
Enter the following command after the switch prompt:
spirita.1.PXM.a > adduser
[username] <accessLevel>
Enter the username using 1–12 alphanumeric characters. Specify the access level by entering one of the
levels defined in Table2-1.
Note
The access level keywords are case-sensitive and must be entered as shown. Also,
you cannot add users at access levels that are equal to or above your own access
level.
Table3-1
User Access Levels
Access Level Keyword
Description
CISCO_GP
Users at the Cisco 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 GROUP5, and
ANYUSER.
SERVICE_GP
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
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.
GROUP1
Users at the GROUP1 access level can add users, delete users, change
passwords, and change access levels for users at the following levels:
GROUP2 to GROUP5 and ANYUSER.
GROUP2
Users at the GROUP2 access level can add users, delete users, change
passwords, and change access levels for users at the following levels:
GROUP3 to GROUP5 and ANYUSER.
GROUP3
Users at the GROUP3 access level can add users, delete users, change
passwords, and change access levels for users at the following levels:
GROUP4 to GROUP5 and ANYUSER.
Cisco SES PNNI Controller Software Configuration Guide
Release 1, Part Number 78-6123-05 Rev. A0, March 2001
3-11
Chapter3
Getting Started
Configuring Administrator Access
Table3-1
Tips
User Access Levels (continued)
Access Level Keyword
Description
GROUP4
Users at the GROUP4 access level can add users, delete users, change
passwords, and change access levels for users at the following levels:
GROUP5 and ANYUSER.
GROUP5
Users at the GROUP5 access level can add users, delete users, change
passwords, and change access levels for users at the ANYUSER level.
ANYUSER
Users at the ANYUSER level cannot add users, delete users, change
passwords or change access levels for other users.
To determine which commands are available at a particular access level, log into the
switch as a user at that access level, then enter the help command.
If you enter the command correctly, the switch prompts you for a password.
Step 3
Enter a password using 5 to 15 characters. If you press Return without entering a password, the system
assigns the default password “newuser.”
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
To display the new user in a list of all users, enter the command dspusers .
Step 6
To test the username, enter the bye command, then log in as the new user.
Tips
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.
Changing User Passwords with cnfpasswd
The Cisco SES provides two commands that you can use to changer administrator passwords:
cnfpasswd and cnfuser. The next section describes how to use the cnfuser command. This section
describes how to change passwords with the cnfpasswd command.
To change the password of a switch administrator with the cnfpasswd command, use the following
procedure.
Step 1
Establish a configuration session as described in “Establishing and Ending a CLI Management
Session,” earlier in this chapter.
Step 2
Enter the following command after the switch prompt:
spirita.1.PXM.a > cnfpasswd
[username]
Replace username with the name of the user whose password you are changing. If you want to change
the password of the username you used to log in, you can omit the username. You can only change
passwords for users that have privileges lower than the username you used to log in.
Cisco SES PNNI Controller Software Configuration Guide
3-12
Release 1, Part Number 78-6123-05 Rev. A0, March 2001
Chapter3
Getting Started
Configuring Administrator Access
Step 3
Enter a password using 5 to 15 characters.
Step 4
When prompted, enter the password a second time to validate the correct entry.
This completes the change of password.
Step 5
To test the new password, enter the bye command, then log in using the new password.
Changing User Access Levels and Passwords with cnfuser
After you create an administrator user, you can change that user’s access level or password using the
cnfuser command.
Note
You can also change the user password with the cnfpasswd command as described in the
preceding section.
To change the user level or password of a switch administrator, use the following procedure.
Step 1
Establish a configuration session as described in “Establishing and Ending a CLI Management
Session,” earlier in this chapter.
Step 2
Enter the following command after the switch prompt:
spirita.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 5-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 Table2-1.
Note
Change passwords and access levels only for users that have privileges lower than
the username you used to log in.
Step 3
To test a new password, enter the bye command, then login 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:
p2_203.7.PXM.a > dspusers
UserId
AccessLevel
------------------------cisco
CISCO_GP
service
SERVICE_GP
superuser
SUPER_GP
jbowman
GROUP1
Cisco SES PNNI Controller Software Configuration Guide
Release 1, Part Number 78-6123-05 Rev. A0, March 2001
3-13
Chapter3
Getting Started
Setting and Viewing the Switch Name
Deleting Users
To delete a user, use the following procedure.
Step 1
Establish a configuration session as described in “Establishing and Ending a CLI Management
Session,” earlier in this chapter.
Step 2
Enter the following command after the switch prompt:
spirita.1.PXM.a >deluser [ username ]
Enter the username using 1 to 12 alphanumeric characters.
This completes the deletion of a user.
Step 3
To verify the user has been deleted, enter the command dspusers .
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 switch.
To change the switch name, use the following procedure.
Step 1
Establish a configuration session as described in “Establishing and Ending a CLI Management
Session,” earlier in this chapter.
Step 2
Enter the following command after the switch prompt:
spirita.1.PXM.a > cnfname <node name>
Enter up to 32 characters for the new node name, and since the node name is case-sensitive, be sure to
use the correct case. For example:
spirita.1.PXM.a > cnfname spiritb
The new name appears immediately in the next CLI prompt.
spiritb.1.PXM.a >
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 as described in “Establishing and Ending a CLI Management
Session,” earlier in this chapter.
Step 2
To view the current switch date and time, enter the following command after the switch prompt:
spirita.1.PXM.a >
dspdate
Cisco SES PNNI Controller Software Configuration Guide
3-14
Release 1, Part Number 78-6123-05 Rev. A0, March 2001
Chapter3
Getting Started
Verifying the Hardware Configuration
Step 3
To change the switch date, enter the following command:
spirita.1.PXM.a > cnfdate <mm/dd/yyyy >
Step 4
To change the time zone, enter the following command:
spirita.1.PXM.a > cnftmzn <timezone>
timezone
Timezone for the node:
•
GMT—Greenwich Mean Time,
•
EST— Eastern Standard Time,
•
CST—Central Standard Time
•
MST—Mountain Standard Time
•
PST—Pacific Standard Time.
EST, CST, MST, and PST are for switches located in the Western Hemisphere. If
your switch is located outside the Western Hemisphere, select GMT and use Step 4
to specify an offset from GMT.
Step 5
To configure an offset from GMT, enter the following command:
spirita.1.PXM.a > cnftmzngmt <timeoffsetGMT>
Replace timeoffsetGMT with the offset in hours from GMT. Enter a number in the range of -12 to +12.
Step 6
To change the switch time, enter the following command:
spirita.1.PXM.a > cnftime <hh:mm:ss>
Replace hh with the hour of the day (0–23), mm with the minute of the hour (0–59), and ss with the
number of seconds in the minute (0–60).
Step 7
To verify the new date and time settings, enter the dspdate command.
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.
Table3-2 shows the information you need and serves as a worksheet where you can enter this
information.
Table3-2
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
Cisco SES PNNI Controller Software Configuration Guide
Release 1, Part Number 78-6123-05 Rev. A0, March 2001
3-15
Chapter3
Getting Started
Verifying the Hardware Configuration
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 as described in “Establishing and Ending a CLI Management
Session,” earlier in this chapter.
Step 2
To display a list of all the cards installed in the switch, enter the dspcds command after the switch
prompt:
spirita.1.PXM.a > dspcds
dspcds
spirita
Backplane Serial No: 12345
Step 3
Step 4
Card
Slot
---
Front/Back
Card State
----------
01
02
03
04
05
06
07
Active/Active
Standby/Active
Empty
Empty
Empty
Empty
Empty
Card
Type
-------PXM1_OC3
PXM1_OC3
-----------
System Rev: 01.00
Bp HW Rev: 00.00
Alarm
Status
--------
May. 21, 2000 03:48:51 PST
GMT Offset: -8
Node Alarm: NONE
Redundant Redundancy
Slot
Type
-----------
NONE
NONE
-----------
02
01
-----------
PRIMARY SLOT
SECONDARY SLOT
-----------
In the worksheet in Table3-2, write down the following information for each card:
•
Card type (goes in Front Card Type column)
•
Redundant Slot
•
Redundancy Type
To display additional information on the PXM card, enter the dspcd command:
spirita.1.PXM.a > dspcd
Note
The dspcd and dspcds commands are very similar, but they produce different
reports. The dspcd command displays information about a specific card and is
entered at the prompt for PXM cards. The dspcds command displays summary
information for all cards in the switch and runs only at the PXM card prompt.
Cisco SES PNNI Controller Software Configuration Guide
3-16
Release 1, Part Number 78-6123-05 Rev. A0, March 2001
Chapter3
Getting Started
Verifying the Hardware Configuration
The dspcd command displays information that is unique to a particular card. The switch displays a
report similar to the following:
spirita.1.PXM.a > dspcd
spirita
System Rev:01.00
SES-CNTL
Slot Number
1
Redundant Slot: 2
Front Card
---------Inserted Card:
PXM1_T3E3
Reserved Card:
PXM1_T3E3
State:
Active
Serial Number:
SAK0352002S
Prim SW Rev:
1.0(1)
Sec SW Rev:
1.0(1)
Cur SW Rev:
1.0(1)
Boot FW Rev:
1.0(1)
HW Rev:
48.50
Orderable Part#:
800-06699-01
CLEI Code:
BAI9Y00CAR
Reset Reason:
On Reset From Shell
Card Alarm:
NONE
Failed Reason:
None
Miscellaneous Information:
Upper Card
----------
Lower Card
----------
UIA BackCard
UIA BackCard
Active
SBK033101K1
--------65.48
800-03688-01
BAI9Y00AAA
BNC_2T3
BNC_2T3
Active
SBK032502JQ
--------65.48
800-04057-02
BAI9A6NAAA
Type <CR> to continue, Q<CR> to stop:
w-ses-5a
System Rev:01.00
SES-CNTL
Crossbar Slot Status:
Aug. 03, 2000 05:16:57 GMT
Node Alarm:MAJOR
Aug. 03, 2000 05:16:57 GMT
Node Alarm:MAJOR
No Crossbar
Alarm Causes
-----------NO ALARMS
w-ses-5a.1.PXM.a >
Step 5
Step 6
In the worksheet in Table2-2, write the following information for each card:
•
Primary software version—appears in the Prim SW Rev row.
•
Boot firmware version—appears in the Boot FW Rev row.
•
Upper Back Card—appears in the Upper Card column of the Inserted Card row.
•
Lower Back Card—appears in the Lower Card column of the Inserted Card row.
To collect card specific information for another card, enter the cc and dspcd commands:
spirita.1.PXM.a > cc number
spirita.1.PXM.a > dspcd
number
Slot number for the card for which you want information.
Cisco SES PNNI Controller Software Configuration Guide
Release 1, Part Number 78-6123-05 Rev. A0, March 2001
3-17
Chapter3
Getting Started
Verifying the Hardware Configuration
When the report appears for the card, write the card information in the worksheet in Table3-2. The
following example shows the report for an PXM card:
spirita.1.PXM.a > cc 2
(session redirected)
spirita.2.PXM.s > dspcd
spirita
System Rev: 02.00
SES-CNTL
Slot Number
2
Redundant Slot: 1
Front Card
---------Reserved Card:
PXM1_OC3
Inserted Card:
State:
Standby
Serial Number:
SAK023800HV
Prim SW Rev:
2.0(1)D
Sec SW Rev:
2.0(1)D
Boot FW Rev:
1.0(39)B1
HW Ver:
69.5248.57
Orderable Part#:
800-04001-02
CLEI Code:
0
Reset Reason:
On Reset From Shell
Card Alarm:
UNKNOWN
Failed Reason:
None
Miscellaneous Information:
spirita
System
SES-CNTL
Crossbar Slot Status:
No Crossbar
Upper Card
---------UIA BackCard
Active
SBK03050077
------800-03688-01
BAI9Y00AAA
Rev: 02.00
Alarm Causes
-----------Reserved Front Card Role Not Assigned
Reserved Back Card Missing
Step 7
May. 22, 2000 10:54:30 GMT
Node Alarm: UNKNOWN
800-03061-02
May. 22, 2000 10:54:30 GMT
Node Alarm: UNKNOWN
: ALARM
: ALARM
After you enter the required information for all cards in Table3-2, refer to Table3-3 to verify the
following:
•
PXM cards are installed in slots 1 and 2.
•
Correct PXM back cards are installed in the correct upper and lower slots.
•
For each PXM card, the correct back cards are installed in the correct upper and lower locations.
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 where the upper and lower back cards are installed are also called
bays. Each slot has an upper and a lower bay for back cards.
Cisco SES PNNI Controller Software Configuration Guide
3-18
Release 1, Part Number 78-6123-05 Rev. A0, March 2001
Chapter3
Getting Started
Managing Redundant Cards
Table3-3
Valid Card Installation Options
Front Card Type
Description
Back Card Types
Back Card
Locations
Valid Slot
Numbers
PXM-OC3
Processor Switch Module
UI Stratum 3
Upper
1 and 2
MMF-4-155
Lower
1 and 2
SMF-4-155
Lower
1 and 2
UI Stratum 3
Upper
1 and 2
PSM-DC-T3
Lower
1 and 2
PSM-DC-E3
Lower
1 and 2
PXM-T3E3
Processor Switch Module
Managing Redundant Cards
The Cisco SES supports redundancy between two PXM cards. This redundancy is preconfigured on the
switch. The following sections describe how to display the redundancy configuration and how to switch
operation from one card to the other.
Displaying Redundancy Status
To display the redundancy configuration for the switch, use the following procedure.
Step 1
Establish a configuration session as described in “Establishing and Ending a CLI Management
Session,” earlier in this chapter.
Step 2
To view the redundancy status, enter the following command after the switch prompt:
spirita.1.PXM.a > dspred
After you enter the command, the switch displays a report similar to the following:
spirita.1.PXM.a > dspred
spirita
SES-CNTL
Primary Primary Primary
SlotNum
Type
State
------- ------- ------1
PXM1
Active
System Rev: 02.00
Secondary
SlotNum
--------2
Secondary
Type
--------PXM1
May. 22, 2000 11:25:02 GMT
Node Alarm: NONE
Secondary Redundancy
State
Type
--------- ---------Standby
1-1
Cisco SES PNNI Controller Software Configuration Guide
Release 1, Part Number 78-6123-05 Rev. A0, March 2001
3-19
Chapter3
Getting Started
Managing Firmware Version Levels for Cards
Switching Between Redundant PXM Cards
To switch operation from one redundant PXM card to another, use the following procedure.
Step 1
Establish a configuration session as described in “Establishing and Ending a CLI Management
Session,” earlier in this chapter.
Step 2
To switch cards, enter the following command after the switch prompt:
spirita.1.PXM.a > switchcc
Managing Firmware Version Levels for Cards
Cards within the SES switch can run two types of firmware:
•
boot firmware—Provides the basic information the card needs to start up.
•
runtime firmware—Controls the operation of the card after startup.
Before a switch can begin using a card, it must have the correct firmware installed and a version number
must be specified for the firmware. When you receive a new switch from Cisco, it is a good idea to
verify that the switch has been configured to use the proper firmware for each card.
If you received a new switch from Cisco, perform the procedure in the next section to verify that the
firmware version is set correctly for all the cards. If the version levels are set correctly, skip the other
procedures.
Cisco SES PNNI Controller Software Configuration Guide
3-20
Release 1, Part Number 78-6123-05 Rev. A0, March 2001
Chapter3
Getting Started
Managing Firmware Version Levels for Cards
Verifying Card Firmware Version Levels
When you are having problems with your switch, or when you’ve taken delivery of a new switch and it
has not been installed immediately, it is wise to verify the firmware versions installed on the switch. If
newer versions of this firmware are available, installing the updated firmware can eliminate or prevent
switch problems.
To verify the firmware versions in use on your switch, use the following procedure.
Step 1
Complete the hardware and software configuration worksheet in Table3-2, as described earlier in
“Verifying the Hardware Configuration.”
Step 2
Compare the versions you noted in Table3-2 with the latest versions listed in the Release Notes for the
SES PNNI Controller.
Note
For instructions on download and installing new firmware versions, refer to Appendix A,
“Technical Specifications.”
Determining the Firmware Version Number from Filenames
To set the firmware version number for an inactive card or for an updated firmware version, you must
know the version number and be able to enter it in the correct format. In most cases, you will find the
correct firmware version numbers in the Release Notes for the SES PNNI Controller . If the release
notes are not available and you’ve downloaded the firmware file, you can use the firmware filename to
determine the version number as described in the following procedure.
Step 1
Establish a configuration session as described in “Establishing and Ending a CLI Management
Session,” earlier in this chapter.
Step 2
To view the files on the switch hard drive, you can enter standard UNIX commands at the switch
prompt. To change directories to the firmware directory, FW, enter the cd C:/FW command:
spirita.1.PXM.a > cd C:/FW
Note
Remember that UNIX directory and filenames are case sensitive.
Cisco SES PNNI Controller Software Configuration Guide
Release 1, Part Number 78-6123-05 Rev. A0, March 2001
3-21
Chapter3
Getting Started
Managing Firmware Version Levels for Cards
Step 3
To list the contents of the directory, enter the ll command:
spirita.1.PXM.a > ll
The display shows:
spirita.1.PXM.a > ll
size
date
------------512
OCT-09-2000
512
OCT-09-2000
3098752
OCT-09-2000
701664
OCT-11-2000
3006584
NOV-06-2000
708368
DEC-13-2000
3154152
DEC-13-2000
time
-----22:51:12
22:51:12
14:54:58
18:48:28
05:05:38
14:47:20
14:47:42
name
-------.
<DIR>
..
<DIR>
pxm1_001.000.010.000_ses.fw
pxm1_001.000.001.000_bt.fw
pxm1_001.000.001.000_ses.fw
pxm1_001.000.011.001_bt.fw
pxm1_001.000.011.001_ses.fw
In the file system :
total space : 819200 K bytes
free space : 781105 K bytes
jaaa8620
TN
Cisco
BPX 8620
9.3.10
Dec. 14 2000 16:55 PST
Trunk : 10.1
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
1000
/4000
2
/4095
0
/200000
CLR
Full Port Bandwidth: 353208
Maximum PVC Bandwidth: 148207
(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
In the file system :
total space : 819200 K bytes
free space : 783016 K bytes
Filenames that include “_ses” are for runtime firmware, and filenames that include “_bt” are for boot
image. When you first receive the switch from Cisco, there will be single versions of each file. If you
download updates to any files, there will be multiple versions of those files.
Step 4
Translate the filenames to version numbers and write this down so you can set the revision levels for
the software.
Table3-4 shows some example filenames and the correct version numbers. The next section describes
how to set the firmware version number for a card.
Cisco SES PNNI Controller Software Configuration Guide
3-22
Release 1, Part Number 78-6123-05 Rev. A0, March 2001
Chapter3
Getting Started
Managing Network Clock Sources
Table3-4
Determining Firmware Version Numbers from Filenames
Filename
Description
Setrev Command
pxm1_001.000.000.000_ses.fw
run time firmware image
setrev 1 1.0(0)0 1.0(0)0
pxm1_001.006.000.000_ses.fw
run time firmware image
setrev 1 1.6(0)0 1.6(0)0
pxm1_001.006.007.000_ses.fw
run time firmware image
setrev 1 1.6(7)0 1.6(7)0
pxm1_001.006.007.002_ses.fw
run time firmware image
setrev 1 1.6(7)2 1.6(7)2
pxm1_002.000.014-A1_bt.fw
boot image
not applicable
Setting the Firmware Version for a Card
To set the firmware version of the card, use the following procedure.
Step 1
If you haven’t already done so, determine the software version number for each card by referring to the
Release Notes for the SES PNNI Controller or by using the procedure in “Determining the Firmware
Version Number from Filenames.”
Step 2
Establish a configuration session as described in “Establishing and Ending a CLI Management
Session,” earlier in this chapter.
Step 3
If you haven’t already done so, complete the hardware and software configuration worksheet in
Table2-2 as described earlier in “Verifying the Hardware Configuration.” You need information from
this worksheet to complete the next step.
Step 4
To set the firmware revision level for a card, enter the setrev command:
spirita.1.PXM.a > setrev <slot > < primary
revision>
<secondary
revision >
Replace slot with the card slot number and replace both primary_revision and secondary_revision with
the software version number.
Step 5
To verify the activation of a card for which the status was previously listed as Failed/Empty, enter the
dspcds command.
Step 6
To verify that an updated version of the software has been successfully activated, use the cc and dspcd
commands to display the software versions as described in “Verifying the Hardware Configuration.”
Managing Network Clock Sources
The clock source is automatically configured on the SES. You do not need to run any clock source
configuration commands.
Cisco SES PNNI Controller Software Configuration Guide
Release 1, Part Number 78-6123-05 Rev. A0, March 2001
3-23
Chapter3
Getting Started
Configuring the PNNI Controller
Configuring the PNNI Controller
There are no PNNI controller commands for the SES. All controller configuration is done on a
BPX 8600 series switch.
Configuring for Network Management
The Cisco SES 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 switch accepts configuration
commands from management stations and sends status and error messages to the management station.
To configure the SNMP agent, use the following procedure.
Step 1
Establish a configuration session as described in “Establishing and Ending a CLI Management
Session,” earlier in this chapter.
Step 2
To define the SNMP password for network management, enter the following command:
spirita.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:
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:
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:
spirita.1.PXM.a > dspsnmp
spirita
spirit
Community:
System Location:
System Contact
System Rev: 02.00
password
Lab
Jack, 555-555-1212
Feb. 17, 2000 09:18:04 PST
Shelf Alarm: NONE
rw
Cisco SES PNNI Controller Software Configuration Guide
3-24
Release 1, Part Number 78-6123-05 Rev. A0, March 2001
Chapter3
Getting Started
Saving a Configuration
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 reentering all the commands used to
configure the switch.
The configuration is saved 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 spirita were saved on
February 29th, 2000 at 2:31pm, the file would be named C:/CNF/spiritspirita_01_200002291431.zip.
You can perform a configuration save if both of the following are true:
•
No save or restore process is currently running.
•
No configuration changes are in progress.
To save the current switch configuration, use the following procedure.
Step 1
Establish a configuration session as described in “Establishing and Ending a CLI Management
Session,” earlier in this chapter.
Step 2
To save the configuration, enter the saveallcnf command:
spirita.1.PXM.a > saveallcnf
Step 3
Read the prompt that appears, click Y if you want to continue, and click Enter.
When the save is complete, the switch prompt reappears and the new file is stored in the C:/CNF
directory.
Cisco SES PNNI Controller Software Configuration Guide
Release 1, Part Number 78-6123-05 Rev. A0, March 2001
3-25
Chapter3
Getting Started
Restoring a Saved Configuration
Restoring a Saved Configuration
You can perform a configuration restore if all of the following are true:
Caution
•
No save or restore process is currently running.
•
No configuration changes are in progress.
•
Switch is not hosting any critical calls.
The restoreallcnf command resets all cards in the switch and terminates all calls passing
through the switch.
To restore a saved switch configuration, use the following procedure.
Step 1
Establish a configuration session as described in “Establishing and Ending a CLI Management
Session,” earlier in this chapter.
Step 2
Verify that the file from which you want to restore configuration data is located in the C:/CNF directory.
Note
Step 3
The C:/CNF directory is the only location from which you can restore a
configuration file. If the file has been moved to another directory or stored on
another system, the file must be returned to this directory before the data can be
restored.
To restore a saved configuration file, enter the restoreallcnf command:
spirita.1.PXM.a > restoreallcnf -f
filename
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.”
Cisco SES PNNI Controller Software Configuration Guide
3-26
Release 1, Part Number 78-6123-05 Rev. A0, March 2001
C H A P T E R
4
SES PNNI Controller Setup and Initial
Configuration
This chapter assumes you have rack-mounted the PNNI Controller and the BPX switch, and have
powered up the units as described in the Cisco Service Expansion Shelf (SES) Hardware Installation
Guide. If so, you are now ready to perform the initial setup task sequence shown in Figure4-1.
Figure4-1
Initial Setup Tasks for PNNI Controller
After completing the initial setup, you will be ready to bring up the system.
Cisco SES PNNI Controller Software Configuration Guide
Release 1, Part Number 78-6123-05 Rev. A0, March 2001
4-1
Chapter4
SES PNNI Controller Setup and Initial Configuration
SES PNNI Controller Interfaces
SES PNNI Controller Interfaces
The SES PNNI controller interfaces (Figure4-2) are located on the PXM UIA backcard (Figure8-3) of
the SES PNNI node. Control interfaces associated with PNNI configuration are as follows:
•
PXM Control Port
•
PXM LAN Port
•
PXM Maintenance Port
•
PXM on ATM Uplink Ports (OC3 and T3/E3)
The remaining ports on the PXM-UIA backcard—T1 clock input, E1 clock input, and external alarm
output—are typically not used during the SES PNNI controller application. These ports support
external audio or visual alarms and external clock sources.
Figure4-2
BPX and SES PNNI Controller Interfaces
PXM Control Port
The control port (sometimes referred to as the Console Port) provides an RS232 interface for connecting
an ASCII terminal to the shelf, and for running the PNNI Controller CLI. This interfaces provides an
RJ45 connector with the following configuration:
•
EIA/TIA 232
Cisco SES PNNI Controller Software Configuration Guide
4-2
Release 1, Part Number 78-6123-05 Rev. A0, March 2001
Chapter4
SES PNNI Controller Setup and Initial Configuration
SES PNNI Controller Interfaces
•
DTE mode
•
Asynchronous interface 19,200 baud
•
1 start bit
•
1 stop bit
•
no parity bits
The control port provides
•
Initial assignment of IP addresses to the Ethernet port, maintenance port, the in-band ATM IP
address, and the IP address of the statistics manager. The ATM IP address belongs to the link
between the PXM and the BPX 8600 series switch.
•
Low-level control or troubleshooting. (You can also use the SES CLI through a window in the Cisco
WAN Manager application.)
Note
Before you use the CiscoView or the Cisco WAN Manager network management
applications, the IP addresses associated with the switch must reside on the workstation in
the etc/hosts file.
Altenatively, you can use DNS, if applicable.
Note
The text file— config.sv—on the workstation must contain information associated with the
switch intended to serve as the gateway node, such as the name of the switch you intend
to be the gateway node, the network ID, the network name, and so on. See the Cisco WAN
Manager documentation for the file system requirements on the workstation.
PXM LAN Port
The LAN port provides an Ethernet interface. It uses an RJ45 connector, 10BaseT, and supports 802.3
Ethernet. Through the Ethernet Port, you can use a workstation running a Cisco network management
application such as the Cisco WAN Manager (formerly known as StrataView Plus) or CiscoView
applications. At least one SES PNNI node is typically collocated with a NMS workstation, and
connected to the same Ethernet segment. That BPX often serves as the gateway for the IP relay (network
IP) inband communication with the other SES PNNI nodes.
The CLI is accessed through the PXM LAN port.
PXM Maintenance Port
The maintenance port provides modem access to the SES PNNI controller. It has an RJ45 connector
with the following configuration:
•
EIA/TIA 232
•
DTE mode
•
asynchronous interface 9600 baud
•
1 start bit
•
1 stop bit
•
no parity bits
Cisco SES PNNI Controller Software Configuration Guide
Release 1, Part Number 78-6123-05 Rev. A0, March 2001
4-3
Chapter4
SES PNNI Controller Setup and Initial Configuration
Attach the Interfaces at the BPX and the PNNI Controller
Through the maintenance port (which is sometimes referred to as the Modem Port), you can connect
either a single workstation running an IP-based application, or a terminal server that supports multiple
workstations. The workstation to be used must support either SLIP or PPP. Typically, use of this port
includes a modem because the switch resides at a remote location. The typical applications are software
and firmware download or tasks that require low-level access.
Both the maintenance port and LAN port support IP-based applications. You can access these ports to
run Telnet, TFTP, or SNMP.
•
Telnet supports CLI command execution from any IP-based application window as well as a
window in the Cisco WAN Manager application.
•
TFTP lets you download firmware and upload and download configuration information.
•
SNMP supports equipment management through the CiscoView application and connection
management through the Cisco WAN Manager application.
Figure4-3
User Interface (PXM UIA) Backcard
Attach the Interfaces at the BPX and the PNNI Controller
The PNNI Controller OC-3 or T3/E3 ATM uplink backcard (Figure4-4) must be connected to the BPX
switch at the BXM cards (Figure4-2). Both the active and standby PXMs must be connected to the
BPX.
The BPX BXM card may also need to be configured for SONET Automatic Protection Switching
(APS), as described in “Configure SES PNNI Redundancy” on page4-17.
Figure4-4
PXM OC-3 Backcard
Cisco SES PNNI Controller Software Configuration Guide
4-4
Release 1, Part Number 78-6123-05 Rev. A0, March 2001
Chapter4
SES PNNI Controller Setup and Initial Configuration
Perform Initial Configuration Tasks at the PNNI Controller
Perform Initial Configuration Tasks at the PNNI Controller
The initial configuration of the SES PNNI controller typically consists of the following task sequence:
1. Connect a Terminal to the PNNI Controller and Start the CLI
2. Configure IP Address
3. Update Backup Boot File and Runtime Controller Image
Connect a Terminal to the PNNI Controller and Start the CLI
Use the steps in this section to connect the PNNI Controller terminal to be used to access the PNNI
Controller CLI.
Connect your terminal to the RJ45 control port on the PXM-UIA backcard of the SES. Make sure your
terminal communication parameters are set to match the control port’s, using the following settings:
•
DCE mode (Control Port is configured as DTE)
•
Asynchronous interface 19,200 baud
•
1 start bit
•
1 stop bit
•
No parity
If you are using an ASCII terminal connected to the control port, the command prompt should now be
displayed on the terminal screen.
Note
If the display is skewed, make sure the terminal speed and user interface control
port speeds are the same.
Tips
If you need to load PXM firmware, go to the next section, entitled “Configure IP Address.”
Tips
If your PXM already has firmware loaded, go to the section entitled “Update Backup Boot
File and Runtime Controller Image.”
PNNI Controller Command Line Interface Overview
The PNNI Controller command line interface (CLI) provides access to the PNNI Controller and is
typically used during initial installation, troubleshooting, or any situation where low-level control is
useful.
The PNNI Controller command line prompt (Figure4-5) displays the name of the SES PNNI Controller,
the shelf number, the slot number and type for the current card, and the current status of the currently
displayed PXM.
Cisco SES PNNI Controller Software Configuration Guide
Release 1, Part Number 78-6123-05 Rev. A0, March 2001
4-5
Chapter4
SES PNNI Controller Setup and Initial Configuration
Perform Initial Configuration Tasks at the PNNI Controller
Figure4-5
Command Prompt Components
The example in Figure4-5 shows that an active PXM card is resident in slot 1 of the node known as
excel.
Note
A PXM card occupies only slot 1 and/or 2 in a PNNI Controller chassis.
The command notation and argument parameters comply with the following, standard programming
conventions
•
A space separates the command and each parameter.
•
Italic typeface indicates command variables.
•
Angular brackets delineate required arguments.
•
Square brackets delineate optional parameters.
•
The vertical bar character (|) represents the logical OR function.
You must type all command arguments, then press Return or Enter. If you need to view the syntax and
arguments for a command, type the command without arguments. The prompt will return the full range
of parameters for the specified command.
Bring Up the SES PXM Card
Check PXM Front Card/Back Card and BXM
Check to make sure the following components have identical port speed (for example, DS3/T3 vs.
OC-3 PXM):
•
front card daughter board
•
PXM back card
•
BXM on the BPX for SES uplink
For an OC-3 uplink, make sure the PXM backcard and uplink BXM port are using same type of fiber,
(for example, SMF vs. MMF). For Single Mode Fiber (SMF) used for uplink, the transmission range on
both PXM backcard and BXM uplink port must be identical. Other wise, you need an attenuator to
match the transmission power. Any mismatching on transmission speed, fiber type, or transmission
range will prevent PXM from coming up properly. Check the hardware thoroughly before you bring up
the software.
Cisco SES PNNI Controller Software Configuration Guide
4-6
Release 1, Part Number 78-6123-05 Rev. A0, March 2001
Chapter4
SES PNNI Controller Setup and Initial Configuration
Perform Initial Configuration Tasks at the PNNI Controller
Boot Up PXM
A new PXM card from the factory must be plugged into an SES shelf on slot 1 or 2. No other card should
be plugged into the SES.
Step 1
Plug the card into the shelf. If the card comes up as active with the Unknown.1.pxm.a > CLI prompt,
skip Step 2 through Step 4. If the card gets stuck at the pxm1> prompt, proceed to Step 2.
Step 2
Execute the sysClrallcnf command at the pxm1> prompt. This cleans up the old data base residing on
the card. The card will come up in BackUp boot prompt.
Step 3
Execute the sysVersionSet command on the backupboot prompt. If the name of the runtime image is
pxm1_001.000.000.000_ses.fw, execute the command sysVersionSet("001.000.000.000") on the
pxm1bkup > prompt.
Step 4
Execute the reboot command at the pxm1bkup > prompt to reboot the card.
The card comes up as active.
Use the steps in the following two sections to load runtime firmware onto a PXM that only has a boot
loader.
Configure the IP Address
There are three IP addresses that need to be configured on an SES node. They are as follows:
•
Boot IP—IP address assigned to Ethernet Port by the bootchange command.
•
Disk/Node IP—IP address assigned to LnPci0 interface by the ipifconfig command.
•
SNMP IP—IP address assigned to the atm0 interface by the ipifconfig command.
There are two options for setting the Boot and Disk IP address:
Tips
•
Only one IP is set for the Disk and Boot IP for both simplex and the redundant PXMs.
•
Two different IP addresses are assigned for Boot and Disk IP for redundant PXM cards.
Prior to the steps in this section, make sure the PNNI Controller is powered on, no alarm
LEDs are evident, and the terminal is connected to the Control Port on the PXM-UIA.
Assign One IP Address for both the Disk IP and Boot IP
To assign one IP address for both the Disk IP and Boot IP on the active card, follow these steps:
Step 1
Run the bootChange command to assign the Boot IP on the active card.
Step 2
Run the ipifconfig command to assign the Disk IP on the active card.
Cisco SES PNNI Controller Software Configuration Guide
Release 1, Part Number 78-6123-05 Rev. A0, March 2001
4-7
Chapter4
SES PNNI Controller Setup and Initial Configuration
Perform Initial Configuration Tasks at the PNNI Controller
If the standby PXM Boot IP address is the same as the disk/node IP address, then the standby ethernet
interface is deactivated. A user can access to the active card via telnet, but not to the standby card. The
standby card can be accessed either through the cc command from the active card, or through the
standby console port.
Assign Two Different IP Addresses for the Disk IP and the Boot IP
Two different IP addresses can be assigned to a redundant system. The IP addresses are assigned on the
active card as follows:
•
Assign IP # 1 to the Boot IP
•
Assign IP # 2 to the Disk IP
If the standby PXM Boot IP address is not the same as the Disk/Node IP address, both the active and
the standby ethernet interface are activated, and the user can telnet to the active and standby PXM at
the same time. A user can access to the active card through Disk IP, and to a standby card through Boot
IP.
Use the following procedure to assign two separate IP addresses.
Step 1
Run the bootChange command on the active card to set the IP address for the Ethernet LAN port on
the PXM.
>Active Card:
ses64.1.PXM.a > bootchange
'.' = clear field; '-' = go to previous field;
boot device
: lnPci
processor number
: 0
host name
:
file name
:
inet on Ethernet (e) : 172.29.37.41:ffffff00
inet on backplane (b):
host inet (h)
:
gateway inet (g)
: 172.29.37.1
user (u)
:
ftp password (pw) (blank = use rsh):superuser
flags (f)
: 0x0
target name (tn)
:
startup script (s)
:
other (o)
:
^D = quit
The PXM now has an IP address.
Cisco SES PNNI Controller Software Configuration Guide
4-8
Release 1, Part Number 78-6123-05 Rev. A0, March 2001
Chapter4
SES PNNI Controller Setup and Initial Configuration
Perform Initial Configuration Tasks at the PNNI Controller
Step 2
Run the bootChange command on the standby card to c onfigure the IP address of the gateway device
that connects the subnets.
>ses64.1.PXM.a > bootchange
'.' = clear field; '-' = go to previous field;
boot device
: lnPci
processor number
: 0
host name
:
file name
:
inet on Ethernet (e) : 172.29.37.41:ffffff00
inet on backplane (b):
host inet (h)
:
gateway inet (g)
: 172.29.37.1
user (u)
:
ftp password (pw) (blank = use rsh):superuser
flags (f)
: 0x0
target name (tn)
:
startup script (s)
:
other (o)
:
^D = quit
The gateway now has an IP address.
Step 3
Run the ipifconfig command on the lnPci0 interface.
ses64.1.PXM.a > ipifconfig lnPci0 172.29.50.64 netmask 255.255.255.0
broadcast 172.29.50.255
Step 4
Run the dspipif command on the active card to display all the IP addresses.
ses64.1.PXM.a > dspipif s
ses64
System Rev: 01.00
Oct. 12, 2000
17:09:44 PST
SES-CNTL
Node Alarm: NONE
IP INTERFACE CONFIGURATION
-------------------------------------------------------------------lnPci (unit number 0):
Flags: (0x63) UP BROADCAST ARP RUNNING
Internet address: 172.29.50.64
Broadcast address: 172.29.50.255
Netmask 0xffff0000 Subnetmask 0xffffff00
Ethernet address is 00:30:71:f8:08:b8
Metric is 0
Maximum Transfer Unit size is 1500
168471 packets received; 5389 packets sent
0 input errors; 0 output errors
0 collisions
DISK IP address: 172.29.50.64
Cisco SES PNNI Controller Software Configuration Guide
Release 1, Part Number 78-6123-05 Rev. A0, March 2001
4-9
Chapter4
SES PNNI Controller Setup and Initial Configuration
Perform Initial Configuration Tasks at the PNNI Controller
Step 5
Log into the standby card and run the dspipif command.
ses64.1.PXM.a > cc 2
ses64.2.PXM.s > dspipif
SES-CNTL
Node Alarm:
UNKNOWN
IP INTERFACE CONFIGURATION
-------------------------------------------------------------------lnPci (unit number 0):
Flags: (0x63) UP BROADCAST ARP RUNNING
Internet address: 172.29.50.100
Broadcast address: 172.29.255.255
Netmask 0xffff0000 Subnetmask 0xffff0000
Ethernet address is 00:10:29:30:01:58
Metric is 0
Maximum Transfer Unit size is 1500
163003 packets received; 3639 packets sent
0 input errors; 1 output errors
0 collisions
DISK IP address: 172.29.50.64
Update Backup Boot File and Runtime Controller Image
When a PXM card is booted up, a user will get one of the following prompts:
•
Backup boot prompt (pxm1bkup> —This means the system is booted up with backup boot. There
are two conditions which will cause the system to come up with backup boot: the existing run time
image failed to boot up.
•
pxm1> prompt—This means the run time image is loaded on the system but the system is not come
up fully.
•
CLI prompt—In this guide, spirit.1.PXM.a> represents the CLI prompt.)This means the system
is booted up with run time image (using cisco as default login and password).
The following sections are associated with updating the backup boot file and runtime controller image:
•
Prepare to Install the Backup Boot
•
Install the Runtime Image
Prepare to Install the Backup Boot File
The following items must be in place prior to attempting installation of the SES PNNI platform
software.
•
SES PNNI Controller shelf with installed PXM
•
OC-3 or T3/E3 Back Cards
•
Cable connection—OC-3 attached to BC port 1 and BXM OC-3 BC port 1
•
Backup boot image for flash
pxm1_001.000.011.001_bt.fw
•
Runtime controller image
pxm1_001.000.012.001_ses.fw
Cisco SES PNNI Controller Software Configuration Guide
4-10
Release 1, Part Number 78-6123-05 Rev. A0, March 2001
Chapter4
SES PNNI Controller Setup and Initial Configuration
Perform Initial Configuration Tasks at the PNNI Controller
The compatible backup boot image and run time image for different SES release is shown in Table 4-1.
Table4-1
Note
SES F/W Compatibility Matrix
Latest Boot Code Version
Minimum
Boot Code
Version
BXM
Firmware
SWSW
CWM
1.0.00
pxm1_001.000.000.000_bt.fw
1.0.00
MFC
9.2.33
10.2
PXM
1.0.01
pxm1_001.000.001.000_bt.fw
1.0.01
MFD
9.2.33
10.2
PXM
1.0.10
pxm1_001.000.000.000_bt.fw
1.0.01
MFH
9.3.10
10.3
PXM
1.0.11
pxm1_001.000.011.001_bt.fw
1.0.11
MFJ
9.3.10
10.4
PXM
1.0.12
pxm1_001.000.011.001_bt.fw
1.0.11
MFL
9.3.11
10.4
Board Pair
SES PNNI
Version
PXM
For correct SES backup boot image, SES run time image, BXM FW, SWSW image for
each release, please check with release note.
Check the PXM for the existing Backup Boot Image and Runtime Image:
•
If you are in the backup boot prompt or pxm1> prompt, enter the following commands:
pxm1bkup> cd C:/FW
pxm1bkup> ll
•
If you are in the CLI prompt, enter the following command:
spirit.1.PXM.a> dspversion
If you do not have the latest _bt.fw and _ses.fw in C:/FW directory, you do not have the latest backup
boot image or run time image in the PXM. Update your system image with the following procedures.
Otherwise, skip to the “Configure SES PNNI Controller Shelf Parameters” section.
Filename
Description
Command
pxm1_001.000.0 12.001_ses.fw
run time firmware image
setrev 1 1.0(12.1)
1.0(12.1) 1
pxm1_001.000.0 11.001_bt.fw
boot image
not applicable
1.
The setrev command will be incrementally updated according to subsequent releases of the SES. For
example, the setrev command for the next release will be setrev1.0(12).
Cisco SES PNNI Controller Software Configuration Guide
Release 1, Part Number 78-6123-05 Rev. A0, March 2001
4-11
Chapter4
SES PNNI Controller Setup and Initial Configuration
Perform Initial Configuration Tasks at the PNNI Controller
Install the Backup Boot
Follow these steps to install the backup boot:
Step 1
Put the image in the C drive for the PXM card. Enter the ftp command with the inet Ethernet IP address
you configured in the “Configure IP Address” section.
For example:
162.29.38.101
The FTP prompt appears.
$ftp
Step 2
Login to the system with your username and password.
ftp> cd “FW”
ftp > bin
ftp > put pxm1_001.000.011.001_bt.fw
Note
Step 3
Check to ensure there are no backup boot images other than the one you just
downloaded in the C:/FW/ directory.
Run the following command from the backup boot prompt to burn the backup boot image into the flash
memory:
pxm1bkup> sysFlashBootBurn (“C:/FW/pxm1_001.000.011.001_bt.fw”)
The system will look for the file
the flash.
Note
pxm1_001.000.011.001_bt.fw in
the C:/FW directory, and burn it onto
If you are in the CLI prompt and you want to burn the backup boot, go to the shell
prompt and issue the sysFlashBootBurn(“C:/FW/pxm1_001.000.011.001_bt.fw”)
command. To get to the shell prompt, type shellConn at the CLI prompt.
This new back up boot image should be brought up by rebooting the card.
The system will then come up in backup boot.
Install the Runtime Image
Use the following procedure t o install the runtime image.
Step 1
Enter the ftp command with the IP address you set at the ASCII terminal.
For example:
$ftp 162.29.38.101
The FTP prompt appears.
Login to the controller with the username as Cisco, and the default password.
Note
The password is not the default password when the controller is in backup boot
mode (at the pxm1bkup> prompt).
Cisco SES PNNI Controller Software Configuration Guide
4-12
Release 1, Part Number 78-6123-05 Rev. A0, March 2001
Chapter4
SES PNNI Controller Setup and Initial Configuration
Perform Initial Configuration Tasks at the PNNI Controller
Step 2
To change to the C:/FW directory, enter the cd command:
spirita.1.PXM.a > cd “FW”
Step 3
At the FTP prompt, enter the bin command.
spirita.1.PXM.a > bin
Step 4
To download the image into the C:/FW directory, enter the put command .
spirita.1.PXM.a > put pxm1_001.000.012.001_ses.fw
Step 5
To quit the FTP application, enter the quit command:
spirita.1.PXM.a > quit
Use the control terminal for Step 6 through Step 8.
Step 6
To locate the FW directory on the hard drive, enter the cd command at the console:
spirita.1.PXM.a > cd c:/FW
Step 7
To confirm that the firmware resides in the FW directory, enter the ll command:
spirita.1.PXM.a > ll
Step 8
Enter one of the following commands:
a.
If you are in the CLI Prompt, enter the setrev command:
spirita.1.PXM.a > setrev <slot> <primary version> <secondary version>
For example, setrev 1 1.0(12.1) 1.0(12.1)
The system will reboot.
b.
If you are in the backup boot prompt, enter the sysVersionSet command:
spirita.1.PXM.a > sysVersionSet “version”
version
The version number of the firmware. The name of a PXM firmware file has the
format pxm1_version_ses.fw.
For example, in pxm1_001.000.012.001_ses.fw, the version will be
001.000.012.001.
To reboot the system, enter the reboot command:
spirita.1.PXM.a > reboot
A login prompt appears on the console. The system is now in the same state as one that has a PXM
shipped with a runtime firmware image.
Cisco SES PNNI Controller Software Configuration Guide
Release 1, Part Number 78-6123-05 Rev. A0, March 2001
4-13
Chapter4
SES PNNI Controller Setup and Initial Configuration
Perform Initial Configuration Tasks at the PNNI Controller
Configure SES PNNI Controller Shelf Parameters
Use the PNNI Controller terminal to perform the following procedure.
Step 1
Type the default login and password:
login: username
password : user password
Step 2
Use the default (active) PXM.
•
To use the currently displayed PXM, press return.
•
To switch to the other installed PXM, type the slot number of the standby PXM at the prompt.
Because the PXM has not been configured with a name, the prompt appears similar to the following
example:
spirita.1.PXM.a >
The PNNI Controller prompt contains the node name, shelf number, slot number, and activity status of
the current PXM ().
Step 3
Enter the dspcds command to view the cards currently installed in the PNNI Controller:
spirita.1.PXM.a > dspcds
Note
Step 4
No service modules are resident in slots 3 through 7 of the PNNI Controller.
Enter the dspipif command to view the IP addresses in the system:
Unknown.1.PXM.a> dspipif
Step 5
Enter the ipifconfig command to modify IP addresses, as needed:
Unknown.1.PXM.a> ipifconfig <interface> <IP_Addr> [netmask Mask] [broadcast broad_addr]
interface
Indicate the interface to be configured.
lnPci0 = Ethernet (LAN AUI)
sl0 = SLIP (Maintenance port)
atm0 = ATM IP Address (for feeder application only)
BroadcastAddr
Note
Applicable only to the Ethernet interface.
Netmask is decided by the type of IP address entered into the system. If the
netmask option is used when ipifconfig CLI is issued, and Mask value is different
to the netmask, then the is set to be the Mask value entered. It is not recommended
to use the netmask option at all, unless you want to build a complicated SNMP
network by using subnet.
Cisco SES PNNI Controller Software Configuration Guide
4-14
Release 1, Part Number 78-6123-05 Rev. A0, March 2001
Chapter4
SES PNNI Controller Setup and Initial Configuration
Perform Initial Configuration Tasks at the PNNI Controller
Step 6
Enter the cnfname command to assign a name to the switch:
Unknown.1.PXM.a>
node name
cnfname
< node
name >
A case-sensitive character string of up to eight characters. The
configured node name will be identified in the CLI command
prompt.
Unknown.1.PXM.a> cnfname
nodename . 1 PXM a>
<nodename >
Step 7
Enter the cnfpasswd command to set a new password for the node.
Step 8
This step is optional.
Enter the cnftime <hh:mm:ss > command to configure the time of the system. Enter either the cnftmzn
or the cnftmzngmt command to configure a time zone for the node:
cnftime 12:20:30
If the node resides within the timezones of the Western Hemisphere, enter the cnftmzn command:
cisco22.1.PXM.a> cnftmzn
timezone
<timezone >
Value to indicate timezone to be used on the node.
GMT—Greenwitch Mean Time
EST—Eastern Standard Time
CST—Central Standard Time
MST—Mountain Standard Time
PST—Pacific Standard Time
If the node resides outside the timezones of the Western Hemisphere, enter the cnftmzngmt command.
cisco22.1.PXM.a>
cnftmzngmt < timeoffsetGMT >
timeoffsetGMT
Note
Step 9
Value to indicate GMT offset hours to be used on the node, in the
range -12 through +12.
Once the PNNI Controller is connected to the BPX switch, it will receive its date
and time from the BPX, if it is configured or available in the BPX.
Enter the cnfstatsmgr command to specify the IP address of the workstation that runs the Cisco WAN
Manager application. Before it sends statistics, the node must have the IP address of the workstation
with this application.
cnfstatsmgr < IP_Addr >
IP_Addr
IP address of the workstation.
If the node has a redundant PXM, it automatically receives the same IP addresses and configuration as
the primary PXM. With the IP addresses in place, you can configure the broadband (ATM uplink)
interface through the CiscoView application or the CLI.
Cisco SES PNNI Controller Software Configuration Guide
Release 1, Part Number 78-6123-05 Rev. A0, March 2001
4-15
Chapter4
SES PNNI Controller Setup and Initial Configuration
Perform Initial Configuration Tasks at the PNNI Controller
Bring Up the SES PNNI Controller
Use the procedure in this section to add the PNNI Controller at the BPX.
At the BPX CLI, perform the following steps:
Step 1
Enter the uptrk command to up the trunk between the BXM and the PNNI controller:
uptrk slot.port
Slot is the uplink BXM slot number in BPX, and port is the port number of the BXM used for uplink.
Step 2
Enter the cnfvsiif command at the BPX to configure the Service Class Template for the uplink (feeder
trunk).
Enter 1 for MPLS service template. Enter 2 for ATMF service template on port. Enter 3 for ATMF
service template on a trunk. For SES PNNI controller uplink, the service class template should be set
to 3. When SCT =3 is selected for uplink trunk, the traffic policing between SES and BPX is disabled.
This prevents the control traffic from getting dropped by the policing function.
cnfvsiif slot.port 3
Step 3
Enter the cnfrsrc command to configure resource on the trunk interface for the PNNI controller’s
control channels.
Since SES PNNI controller uplink uses VPI=3 to carry LMI (Annex-G) and IP Relay information
between the SES and BPX, VPI=3 must be avoided when VSI VPI range is assigned. The valid VSI VPI
range is 1-2 or 4-4095.No AutoRoute resource needs to be reserved in uplink.
cnfrsrc slot.port
Recommended values for resource configuration of a typical uplink are listed below:
Step 4
•
Maximum PVC LCNS = 0
•
Maximum PVC Bandwidth =0
•
Partition = 1
•
Partition State = Enabled
•
Minimum VSI LCNS =100
•
Maximum VSI LCNS =500
•
Start VSI VPI =4
•
End VSI VPI =4095
•
Minimum VSI Bandwidth =100,000
•
Maximum VSI Bandwidth =300,000
•
VSI ILMI Config = 0 (disabled)
Enter the addshelf command, with feeder type set to “x” (for aal5), to add the SES PNNI Controller to
the BPX and to enable the AnnexG protocol to run between the BPX and the SES PNNI Controller.
addshelf slot.port x
Cisco SES PNNI Controller Software Configuration Guide
4-16
Release 1, Part Number 78-6123-05 Rev. A0, March 2001
Chapter4
SES PNNI Controller Setup and Initial Configuration
Perform Initial Configuration Tasks at the PNNI Controller
Step 5
Enter the addctrlr command to enable VSI capabilities on the trunk interface.
addctrlr slot.port
Cntl_Id
2 for PNNI Controller
Part_Id
1 for partition #1
Control_VC_VPI
0
Control_VC_VCI
40 to reserve VCI Range 40 to 54 for control VCs
The VSI protocol will start operating and the VSI master in the PNNI controller will establish
communication with the VSI slaves running in the BXM cards at the BPX.
Initial configuration is not required from the PNNI controller. The default node name and address will
be used in the messages between the BPX and the PNNI Controller.
When the uplink is up, enter the dsplmilink command on the SES to display the current alarm status as
clear. Enter the dspcds command on the BPX to show all the active cards in the shelf, including uplink.
Configure SES PNNI Redundancy
A redundant card comprises two sets of front cards and back cards. One set of front and back cards is
known as the active pair and the other set is known as the standby pair. All the work is done by the
active pair of cards and the standby pair acts as a backup If the active front card fails, the standby front
and back card take over. If the active back card fails, manual intervention is needed. because the standby
back card won't take over automatically. There are three types of redundant configurations:
1. OC-3 Y-cable Redundancy
2. DS-3/E3 Y cable Redundancy
3. APS Redundancy
OC-3 Y-cable redundancy
Required Hardware
•
Two OC-3 SES-PXM front cards (one active and one standby)
•
Two OC-3 back cards (one for each front card)
•
Two OC-3 y-cables (Single Mode or Multi Mode, depending on whether the back card is Single
Mode or Multi Mode)
Take one Y-cable. Plug one SC-connector to the RX port of one back card and plug the other
SC connector to the RX port of the other back card. Plug the SC connectors of the other Y-cable to the
TX ports of the back cards
The other end has to be plugged to the BXM. So the RX cable from the SES goes to the TX port of the
BXM and the TX cable of the SES goes to the RX port of the BXM.
User Command (CLI) on the SES
None
Cisco SES PNNI Controller Software Configuration Guide
Release 1, Part Number 78-6123-05 Rev. A0, March 2001
4-17
Chapter4
SES PNNI Controller Setup and Initial Configuration
Perform Initial Configuration Tasks at the PNNI Controller
Commands on the BPX Side
Note
•
uptrk a.b (a.b is the port connected to the SES)
•
cnfrsrc a.b params
•
addshelf a.b x (for AAL 5)
•
addctrlr a.b params
Refer to the BPX 8600 documentation for details about these commands.
The uplink between the BPX and the SES is working if:
•
PORT1 LED on the active front card is green.
•
SIGNAL LEDs on both the back cards are green on executing the dsplmilink on the SES we come
to know about the BPX to which the SES is connected. The output of the command should look
similar to the following example
T
RK
1.1
Current Alarm Status
CLEAR
Other End
orpbpx/9.5
DS-3/E3 Y cable redundancy
Required Hardware
•
Two OC3 PXM-SES front cards (one active and one standby)
•
Two DS-3 or E3 back cards (one for each front card) depending on whether DS-3 or E3 uplink is
desired
•
Two coaxial Y cables.
Take one Y - cable. Plug one SMB connector to the RX port of one back card and plug the other SMB
connector to the RX port of the other back card. Plug the SMB connectors of the other Y-cable to the
TX ports of the back cards. The other end has to be plugged to the BXM. So the RX cable from the SES
goes to the TX port of the BXM and the TX cable of the SES goes to the RX port of the BXM.
User Command (CLI) on the SES
None
Commands on the BPX Side
Note
•
uptrk a.b (a.b is the port connected to the SES)
•
cnfrsrc a.b params
•
addshelf a.b x (for AAL 5)
•
addctrlr a.b params
For details about the commands mentioned above refer to the BPX manual.
Cisco SES PNNI Controller Software Configuration Guide
4-18
Release 1, Part Number 78-6123-05 Rev. A0, March 2001
Chapter4
SES PNNI Controller Setup and Initial Configuration
Perform Initial Configuration Tasks at the PNNI Controller
The BPX and the SES is working if
•
PORT1 LED on the active front card is green
•
SIGNAL LEDs on both the back cards are green on executing the dsplmilink on the SES we come
to know about the BPX to which the SES is connected. The output of the command should be
something like
TRK
Current Alarm Status
Other End
1.1
CLEAR
orpbpx1/4.2
APS Redundancy
SES supports dual back-card APS 1+1 mode redundancy. “Dual back-card” means that the protection
line must be on a back-card different from the working line's back-card. APS is supported only for line
1 and only for type OC-3 of the uplink.
It is possible to use the uplink (between the BPX and SES) both without and with APS. If APS is added
(enabled), it provides line- and card-level redundancy for the uplink. Therefore, if a single line or
back-card fails, the uplink will still carry traffic over the other line.
The APS line that was active before a front-card failure or front-card switchover continues to be the
active APS line after the transitions (if any) of the front-cards.
Required hardware
Note
•
Two OC-3 PXM-SES front-cards (one active, the other standby)
•
Two model B OC-3 back-cards (one each in slots 1 and 2)
The front-cards, daughter-cards and back-cards must have the same type (OC-3) and
number of ports (for example, 4). Additionally, the fiber cables (used to physically connect
the SES controller with the BPX) must match the type of the back-card(s) on the SES and
BPX. The two types of fiber cables are SMF (single-mode fiber) and MMF (multi-mode
fiber).
User commands (CLI) on the SES
•
addapsln can be used to enable APS (only on line 1).
•
delapsln can be used to disable APS (only on line 1).
•
cnfapsln can be used to configure the various parameters for APS (only on line 1).
•
switchapsln can be used to switch the active APS line between the working and protection lines.
•
dspapsln can be used to view the current APS status.
•
dspapscfg can be used to view the settings for the various APS parameters.
•
dspbecnt can be used to view the statistics for the (APS) bit-error counts.
•
clrbecnt can be used to clear the statistics for the (APS) bit-error counts.
For more details on the syntax and usage of these commands, please refer to Appendix C of this guide.
Cisco SES PNNI Controller Software Configuration Guide
Release 1, Part Number 78-6123-05 Rev. A0, March 2001
4-19
Chapter4
SES PNNI Controller Setup and Initial Configuration
Perform Initial Configuration Tasks at the PNNI Controller
Note
It is very important that the APS configurations on the SES match those on the BPX. For
example, an APS direction mismatch will result if APS on the BPX is configured in
bi-directional mode while APS on the SES is configured in uni-directional mode.
Here is a nominal sequence of commands that a user would typically use to set up APS on the SES:
a. addapsln 1 1 1 2 2
b. dspapsln
c. dspapscfg
d. cnfapsln 1 3 5 2 1 2 1
e. dspapsln
f. dspapscfg
For the purpose of this section, consider that the commands are run on an SES shelf that is named
“PSbench” (to do this, enter the cnfname command).
Step 1
addapsln
11122
This command adds (enables) APS in 1+1 dual back-card mode on line 1,with line 1 on slot 1 as the
working line and line 1 on slot 2 as the protection line.
Sample screen output:
PSbench.1.1.PXM.a >
addapsln
1 1 1 2 2
PSbench.1.1.PXM.a >
Step 2
dspapsln
This command displays the current APS configuration.
Sample screen output:
PSbench.1.PXM.a > dspapsln
SlotLine Type Act W_LINE P_LINE APS_ST CDType Dir Revt LastUsrSwReq
-----------------------------------------------------------------------1.1&2.1 1+1_2 1.1 OK
OK
OK
OC-3
UNI NRV NO_REQUEST
Step 3
dspapscfg
This command displays the values of the various APS parameters.
Sample screen output:
APSbench.1.PXM.a > dspapscfg
SlotLine Type
SFBER SDBER WTR Dir Revert K1K2
----------------------------------------------------1.1&2.1
1+1_2 3
5
1
UNI NRV
ENA
Cisco SES PNNI Controller Software Configuration Guide
4-20
Release 1, Part Number 78-6123-05 Rev. A0, March 2001
Chapter4
SES PNNI Controller Setup and Initial Configuration
Perform Initial Configuration Tasks at the PNNI Controller
Step 4
cnfapsln 1 3 9 2 1 2 1
This command configures APS for bi-directional revertive mode with K1/K2 bytes enabled, with the
following values for:
•
Wait-to-restore timer (WTR): 1 minute
•
Signal Failure (SF) threshold: 10^^-3
•
Signal Degrade (SD) threshold: 10^^-9
•
Sample screen output:
PSbench.1.1.PXM.a > cnfapsln 1 3 9 2 1 2 1
PSbench.1.1.PXM.a >
Step 5
dspapsln
This command displays the current APS configuration.
Sample screen output:
APSbench.1.PXM.a > dspapsln
SlotLine Type Act W_LINE P_LINE APS_ST CDType Dir Revt LastUsrSwReq
-----------------------------------------------------------------------1.1&2.1 1+1_2 1.1 OK
OK
OK
OC-3
BI RVE NO_REQUEST
Step 6
dspapscfg
This command displays the values of the various APS parameters.
Sample screen output:
APSbench.1.PXM.a > dspapscfg
SlotLine Type
SFBER SDBER WTR Dir Revert K1K2
----------------------------------------------------1.1&2.1
1+1_2 3
9
1
BI RVE
ENA
Cisco SES PNNI Controller Software Configuration Guide
Release 1, Part Number 78-6123-05 Rev. A0, March 2001
4-21
Chapter4
SES PNNI Controller Setup and Initial Configuration
Perform Initial Configuration Tasks at the PNNI Controller
Cisco SES PNNI Controller Software Configuration Guide
4-22
Release 1, Part Number 78-6123-05 Rev. A0, March 2001
C H A P T E R
5
Configuring ATM SVCs, PNNI Routing, and
SPVCs
Use this chapter to find out about the tasks typically performed to bring up the SES PNNI node. This
chapter assumes the following:
•
You have completed and verified the hardware installation at the BPX and the SES PNNI
Controller, as described in Chapter 5 of the Cisco SES Hardware Installation Guide.
•
You have completed the tasks described in Chapter4, “SES PNNI Controller Interface Connections
and Initial Configuration.”
After completing the installation and initial configuration tasks, you are ready to bring up the system,
using the task sequence shown in Figure5-1.
Figure5-1
Bringup Tasks for PNNI Controller
This chapter refers to commands that run from the BPX CLI, the SES CLI or CiscoView menus. The
BPX CLI commands are documented in detail in the Cisco WAN Switching Command Reference,
Release 9.3. The CiscoView menus are described in Chapter 7, “Network Management.”
Cisco SES PNNI Controller Software Configuration Guide
Release 1, Part Number 78-6123-05 Rev. A0, March 2001
5-1
Chapter5
Configuring ATM SVCs, PNNI Routing, and SPVCs
UNI Configuration
UNI Configuration
Use this section to find out how to use auto-configuration on the PNNI Controller, to set default PNNI
values and ILMI address registration on UNI ports.
Note
Auto configuration is enabled only if the attached ATM CPE supports ILMI. If the
attached ATM CPE does not support ILMI, you must bring up the port by using the
guidelines provided in the section Configuring a Port without AutoConfiguration and
ILMI, page 5-6.
Auto-configuration is comprised of AutoConfigure a UNI Port
AutoConfigure a UNI Port
Use the following procedure to connect an ATM UNI for auto-configuration using ILMI address
registration and the VSI protocol.
At the BPX CLI, perform the following steps:
Step 1
Connect the appropriate cable between the BPX BXM port and the ATM CPE.
Make sure the ATM CPE is configured for ILMI.
Step 2
Enter the upln command at the BPX CLI to up the line, the physical layer.
upln slot.port
Step 3
Enter addport command to add port .
addport slot.port
Step 4
Enter the upport command to up the port.
upport slot.port
Step 5
Enter the cnfvsiif command at the BPX to configure Service Class Template for the interface. 1 is for
MPLS, service template 2 is for ATMF service template on port, and 3 is for ATMF service template on
trunk. For PNNI SES UNI interface, the service class template should be set to 2. Detail of service class
template is found in Appendix C.
cnfvsiif slot.port 2
Cisco SES PNNI Controller Software Configuration Guide
5-2
Release 1, Part Number 78-6123-05 Rev. A0, March 2001
Chapter5
Configuring ATM SVCs, PNNI Routing, and SPVCs
UNI Configuration
Step 6
Enter the cnfrsrc command to set resources on the port.
A system response similar to the following example occurs:
---------------------------------------------------------------------------orbpx6
TN
Cisco
BPX 8620 9.3.1d
Sep. 18 2000
19:56 PDT
Port : 1.7
Maximum PVC LCNS:
PVC VPI RANGE [1]:
PVC VPI RANGE [3]:
0
-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
/15232
1
/255
95000 /95000
SET
Full Port Bandwidth: 96000
Maximum PVC Bandwidth: 0
(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: cnfrsrc 1.7 0 0 N Y 1 e 2000 15232 1 255 95000 95000
-------------------------------------------------------------------------------
Note
Step 7
For more information about the configure resources command, refer to the Cisco
WAN Switching Command Reference, Release 9.3.
Use the cnfport command to enable ILMI protocol to run on the BXM card and enable VSI ILMI to
PNNI controller.
Example for ILMI port configuration on a BXM card:
cnfport 10.4 353208 N H I 0 16 Y Y N 30 3 4 N N 0 N Y N
------------------------------------------------------------------------svcbpx16
TN
Cisco
BPX 8620 9.3.1d
Sep. 22 2000
14:47 PDT
Port:
10.4
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:
353208/0
Enabled
0
Disabled
0 %
Protocol:
ILMI
Protocol by Card: Yes
NbrDisc Enabled:
No
VPI.VCI:
0.16
Addr Reg Enab: Y
ILMI Polling Enabled:
Y
Trap Enabled:
N
T491 Polling Interval:
30
N491 Error Threshold:
3
N492 Event Threshold:
4
ILMI Reset Flag:N
----------------------------------------------------------------------------------
Cisco SES PNNI Controller Software Configuration Guide
Release 1, Part Number 78-6123-05 Rev. A0, March 2001
5-3
Chapter5
Configuring ATM SVCs, PNNI Routing, and SPVCs
UNI Configuration
Step 8
Use the cnfvsipart command to enable VSI ILMI support, as shown in the following example:
---------------------------------------------------------------------------sj862129
TN
Cisco
BPX 8620 9.3.10
Dec. 15 2000 01:12 GMT
Trunk: 10.1
Partn: 1
ILMI: D
Last Command: cnfvsipart 10.1 1 Y
ILMI protocol should run on the BXM card
Next Command:
-------------------------------------------------------------------------------
The BXM sends a VSI trap to the SES PNNI controller. When the SES PNNI controller receives the
trap, it sends a VSI passthrough back to the BXM enabling auto-configuration. The information in the
passthrough includes auto-configuration default parameters. Auto-configuration parameters include
details such as AutoConfiguration on, service registry on, address registration on, node prefix, and
others.
The BXM starts the ILMI protocol with the attached ATM CPE. The BXM then send the SES PNNI
controller the following port information: vpi/vci range, interface type, device type, ILMI version, and
UNI Signaling version.
The PNNI Controller then starts the UNI signaling stacks.
Note
All ILMI features on SES PNNI are default to be on. You do not need to use cnfaddrreg,
cnfautocnf to enable ILMI features on SES PNNI.
Modifying Port Parameters After AutoConfiguration
To modify port parameters after AutoConfiguration, perform the following steps at the SES PNNI
Controller CLI.
Note
Step 1
When using service-affecting parameters on a port already configured, the port must be
must be brought down prior to attempting modifications to port parameters.
Use the dnpnport command—either from CiscoView or the PNNI Controller CLI—to down the port.
This brings down the signaling stacks for the port.
Step 2
Change the appropriate parameter with one of the following cnf commands:
•
cnfpnportsig
•
cnfpnportrange
•
cnfilmienable
•
cnfaddrreg
•
cnfautocnf
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 CLI commands:
Cisco SES PNNI Controller Software Configuration Guide
5-4
Release 1, Part Number 78-6123-05 Rev. A0, March 2001
Chapter5
Configuring ATM SVCs, PNNI Routing, and SPVCs
UNI Configuration
Step 3
Step 4
•
cnfpnportcc
•
cnfpnportcac
•
addprfx
•
addaddr
Use one of the following display commands to see the current configurations:
•
dsppnportsig
•
dsppnportrange
•
dsppnilmi
•
dsppnportcc
•
dsppnportcac
•
dspprfx
•
dspaddr
Use the uppnport command to enable the port.
Pre-configuring a UNI Port with AutoConfiguration
Use the following procedure to pre-configure specific parameters before a port is brought up with
AutoConfiguration.
Use the SES PNNI Controller CLI to perform steps 1 through 3.
Step 1
Use the addpnport command at the PNNI Controller CLI to define an UNI port.
Note
Step 2
Step 3
Ports are administratively down, by default.
Modify the appropriate parameter with one of the following PNNI Controller cnf commands:
•
cnfpnportsig
•
cnfpnportrange
•
cnfilmienable
•
cnfaddrreg
•
cnfautocnf
Use the uppnport command to up the PNNI port.
Note
The signaling stacks are not yet brought up because the port configuration has not
yet been received from the BXM.
Use the BPX CLI to perform steps 4 through 8.
Step 4
Enter the upln command at the BPX CLI to bring up the line.
Step 5
Enter the addport command to add port.
Cisco SES PNNI Controller Software Configuration Guide
Release 1, Part Number 78-6123-05 Rev. A0, March 2001
5-5
Chapter5
Configuring ATM SVCs, PNNI Routing, and SPVCs
UNI Configuration
Step 6
Enter the upport command to bring up the port.
Step 7
Enter the cnfvsiif command at the BPX CLI to configure PNNI service template, 2.
Step 8
Enter the cnfrsrc command to set resources on the port.
Step 9
Enter the cnfport command to enable ILMI protocol on BXM port.
The following results occur:
a.
The BXM now sends a VSI trap to the SES PNNI controller.
b.
The PNNI Controller starts the UNI signaling stacks:
•
If AutoConfiguration is enabled , the SES PNNI controller will send a VSI passthrough to the
BXM. The BXM initiates ILMI with the ATM CPE. The BXM then sends VSI passthrough
back to the SES PNNI controller with port information, at which time the SES PNNI controller
starts the UNI signaling stacks.
•
If AutoConfiguration is disabled , the SES PNNI controller will start the UNI signaling stacks
for the port.
Configuring a Port without AutoConfiguration and ILMI
If the attached ATM CPE does not support ILMI, you must bring up the port without auto-configuration.
Use the BPX CLI to perform steps 1 through 4.
Step 1
Enter the upln command at the BPX CLI to up the line.
Step 2
Enter the addport command to add the port.
Step 3
Enter the upport command to up the port.
Step 4
Enter the cnfvsiif command at the BPX CLI to configure PNNI service template, 2.
Step 5
Enter the cnfrsrc command to set resources on the port.
The following results occur:
a.
The BXM now sends a VSI trap to the SES PNNI controller.
b.
The SES PNNI controller receives the BXM port configuration through VSI with ILMI disabled.
The SES PNNI controller brings up the UNI or PNNI signaling stacks.
Use the SES PNNI Controller CLI to perform step 5.
Step 6
Note
Enter the addaddr command at the PNNI Controller to set ATM addresses for the port. This step is
necessary because there is no automatic address registration from ILMI.
An address can only be provisioned on a UNI if ILMI address registration is disabled.
Cisco SES PNNI Controller Software Configuration Guide
5-6
Release 1, Part Number 78-6123-05 Rev. A0, March 2001
Chapter5
Configuring ATM SVCs, PNNI Routing, and SPVCs
NNI Trunk Configuration
NNI Trunk Configuration
Use this section to find out how to configure a PNNI trunk on BPX and SES PNNI Controller.
AutoConfigure an NNI Trunk
Use the following procedure to connect an ATM NNI trunk with auto-configuration using ILMI and the
VSI protocol.
At the BPX CLI, perform the following steps:
Step 1
Connect the appropriate cable between the BPX BXM ports.
Make sure the other BPX BXM port is configured for ILMI.
Step 2
Enter the uptrk command at the BPX CLI to up the trunk.
uptrk slot.port
Step 3
Enter the addtrk command at the BPX CLI to add AutoRoute on the trunk.
addtrk slot.port
Since AutoRoute is needed to provide IP connectivity, Time of Date, and Network Clocking for this
release of BPX/SES, it is essential to add AutoRoute partition in a trunk even if there is no “AutoRoute”
PVC service to be implemented. Limit resource is needed to be provisioned to carry IP connectivity,
Time of Date, and Network Clocking. Notice that when the AutoRoute service is added to the trunk, the
VPI = 0 and 1 will be reserved for AutoRoute. The available VPI for VSI (or PNNI) will start from
VPI = 2.
Step 4
Enter the cnfvsiif command at the BPX to configure Service Class Template for the interface. 1 is for
MPLS, service template 2 is for ATMF service template on port, and 3 is for ATMF service template
on trunk. For PNNI SES NNI trunk, the service class template should be set to 3. Detail of service class
template can be found in Appendix C.
cnfvsiif slot.port 3
Step 5
Enter the cnfrsrc command to set resources on the port.
A system response similar to the following example occurs:
jaaa8620
TN
Cisco
BPX 8620
9.3.10
Dec. 14 2000 16:55 PST
Trunk : 10.1
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
1000
/4000
2
/4095
0
/200000
CLR
Full Port Bandwidth: 353208
Maximum PVC Bandwidth: 148207
(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: cnfrsrc 10.1 256 148207 y 1 e 0 4000 2 4095 0 200000
Cisco SES PNNI Controller Software Configuration Guide
Release 1, Part Number 78-6123-05 Rev. A0, March 2001
5-7
Chapter5
Configuring ATM SVCs, PNNI Routing, and SPVCs
NNI Trunk Configuration
Note
Step 6
For more information about the configure resources command, refer to the Cisco WAN
Switching Command Reference for Release 9.3.
Enter the cnftrk command to enable ILMI protocol to run on the BXM card.
The following example shows ILMI port configuration on a BXM card:
----------------------------------------------------------------------------oriobpx3
TN
StrataCom
BPX 8620 9.2.3U
Feb. 17 2000 08:22 PST
TRK 1.2 Config
OC3
[353207cps]
Transmit Rate:
353208
Protocol By The Card: Yes
VC Shaping:
No
Hdr Type NNI:
Yes
Statistical Reserve: 1000
cps
Idle code:
7F hex
Connection Channels: 256
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
BXM slot:
1
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
Last Command:cnftrk 1.2 353208 y Y 1000 7F V,TS,NTS,FR,FST,CBR,NRT-VBR,ABR,RT-V BR N
TERRESTRIAL 10 0 N N Y Y Y N
----------------------------------------------------------------------------
Step 7
Enter the cnfvsipart command to enable VSI ILMI.
cnfvsipart slot.port partition_id Enable_ilmi [y/n]
Example:
---------------------------------------------------------------------------sj862129
TN
Cisco
BPX 8620 9.3.10
Dec. 15 2000 01:12 GMT
Trunk: 10.1
Partn: 1
ILMI: D
Last Command: cnfvsipart 10.1 1 Y
ILMI protocol should run on the BXM card
Next Command:
-------------------------------------------------------------------------------
The BXM now sends a VSI trap to the SES PNNI controller.
When the SES PNNI controller receives the trap, it sends a VSI passthrough back to the BXM to enable
auto-configuration. The information in the passthrough includes auto-configuration default parameters.
The BXM then starts the ILMI protocol with the attached BXM port. The BXM will then send the SES
PNNI controller the port information: vpi/vci range, interface type, device type, ILMI version, and NNI
Signaling version.
Finally, the PNNI Controller starts the PNNI signaling stacks.
Note that all ILMI features on SES PNNI are default to be on, there is NO need to use cnfautocnf to
enable ILMI features on SES PNNI.
Step 8
Enter the dspvsipartcnf command to view VSI ILMI functionality status (whether enabled or not) for
various VSI partitions on the interface.
Cisco SES PNNI Controller Software Configuration Guide
5-8
Release 1, Part Number 78-6123-05 Rev. A0, March 2001
Chapter5
Configuring ATM SVCs, PNNI Routing, and SPVCs
NNI Trunk Configuration
Example:
---------------------------------------------------------------------------oriobpx3
TN
StrataCom
BPX 8620 9.2.3U
Feb. 17 2000 08:29 PST
Trunk:1.2
Trunk:1.2
Trunk:1.2
Partn:1
Partn:2
Partn:3
ILMI:E
LCN:1
Topo:BPX NW IP
-- VSI partition DISABLED
-- VSI partition DISABLED
Sys_Id generated = 38.33.39.33.36.33
Last Command: dspvsipartcnf 1.2
----------------------------------------------------------------------------
Pre-configuring a NNI Trunk with AutoConfiguration
Use the following procedure to pre-configure an NNI trunk with AutoConfiguration.
Perform Steps 1 through 3 at the SES PNNI Controller. Perform steps 4 through 9 at the BPX.
Step 1
Enter the addpnport command at the PNNI Controller to define a PNNI port.
Note
Step 2
Enter one of the following commands to modify the appropriate parameters:
•
cnfpnportrange
•
cnfaddrreg
•
cnfautocnf
Note
Step 3
Ports are administratively down, by default.
The modified parameters will be used by AutoConfiguration to negotiate a
common parameters with its peer ILMI IME (Interface Management Entity).
Enter the uppnport command to up the PNNI port.
Note
The signaling stacks are not yet brought up because the port configuration has not
yet been received from the BXM.
Use the BPX CLI to perform steps 4 through 8.
Step 4
Enter the uptrk command at the BPX CLI to bring up the trunk.
Step 5
Enter the addtrk command at the BPX CLI to add AutoRoute.
Step 6
Enter the cnfvsiif command at the BPX CLI to configure PNNI service template, 3.
Step 7
Enter the cnfrsrc command to set resources on the port.
Cisco SES PNNI Controller Software Configuration Guide
Release 1, Part Number 78-6123-05 Rev. A0, March 2001
5-9
Chapter5
Configuring ATM SVCs, PNNI Routing, and SPVCs
Configuring Virtual Trunk on a BXM Port
Step 8
Enter the cnftrk command to enable ILMI protocol on BXM port.
Step 9
Enter the cnfvsipart command to bring up the port.
The following results occur:
•
The BXM sends a VSI trap to the SES PNNI controller.
•
The PNNI Controller starts the PNNI signaling stacks:
– If AutoConfiguration is enabled , the SES PNNI controller will send a VSI passthrough to the
BXM. The BXM initiates ILMI with the ATM CPE. The BXM then sends VSI passthrough
back to the SES PNNI controller with port information, at which time the SES PNNI controller
starts the PNNI signaling stacks.
– If AutoConfiguration is disabled , the SES PNNI controller will start the NNI signaling stacks
for the port.
Configuring Virtual Trunk on a BXM Port
Use the BPX CLI to configure VSI on BXM ports or trunks. For more information about the VSI
protocol, see Appendix B, “ Virtual Switch Interface.”
A default Service Class Template is assigned to a logical interface when you up the interface by entering
the uptrk and upport commands.
For example:
uptrk 1.1
uptrk 1.1.1 (virtual trunk, 1 -- 31)
upport 1.1
In the above example, the default template has the identifier of 1.
To change the default Service Class Template—from Service Class Template 1—to another Service
Class Template, use the following procedure:
Step 1
Enter the cnfvsiif command.
For example:
cnfvsiif 1.1 2
cnfvsiif 1.1.1 2
Step 2
Enter the dspvsiif command to view a template associated with a specified interface.
For example:
dspvsiif 1.1
dspvsiif 1.1.1
Step 3
Enter the cnfvsiif command to assign a selected Service Class Template to an interface (VI) by
specifying the template number:
cnfvsiif <slot.port.vtrk> <tmplt_id>
Step 4
Enter the dspvsiif command to display the type of Service Class Template assigned to an interface (VI):
dspvsiif <slot.port.vtrk>
Cisco SES PNNI Controller Software Configuration Guide
5-10
Release 1, Part Number 78-6123-05 Rev. A0, March 2001
Chapter5
Configuring ATM SVCs, PNNI Routing, and SPVCs
Configuring Virtual Trunk on a BXM Port
Configure the BXM Qbin
The default Service Class Template is assigned to the interface (VI) when an interface (VI) is activated
by entering the uptrk or upport commands. The corresponding Qbin template is then copied into the
data structure of that interface at the BXM.
You can change some of the Qbin parameters by entering the cnfqbin command. The Qbin is now “user
configured,” as opposed to “template configured.” Enter the dspqbin command to view this
information.
Qbin Dependencies
The available Qbin parameters are shown in Table5-1.
Qbins available for VSI are restricted to Qbins 10-15 for that interface.
All 32 possible virtual interfaces are provided with 16 Qbins.
Table5-1
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 described in Table5-2.
Table5-2
Service Class Template Commands
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.
Cisco SES PNNI Controller Software Configuration Guide
Release 1, Part Number 78-6123-05 Rev. A0, March 2001
5-11
Chapter5
Configuring ATM SVCs, PNNI Routing, and SPVCs
Configuring Virtual Trunk on a BXM Port
Table5-2
Service Class Template Commands (continued)
dspqbin
Enter this command to view Qbin parameters currently configured for
the virtual interface.
dspcd
Enter this command to view current card configuration
Enable VSI ILMI Functionality
Currently, VSI ILMI functionality can be enabled both on line (port) interfaces and trunk interfaces.
VSI ILMI functionality cannot be enabled on trunks to which feeders or VSI controllers are attached.
Enable VSI ILMI Functionality on Line (Port) Interfaces
Use the following procedure to enable VSI ILMI functionality on specified line or port:
Step 1
Enter the upln command to bring up a line interface.
Step 2
Enter the addport command to add a line interface.
Step 3
Enter the upport command to up the port interface.
Step 4
Enter the cnfvsiif slot.port 2 to set SCT = 2.
Step 5
Enter the cnfrsrc command to configure a VCI partition on the line interface.
Step 6
Enter the cnfport command to configure the port to enable ILMI protocol and to ensure that the
protocol runs on the BXM card by enabling the “protocol-by-the-card” option.
Enable VSI ILMI Functionality on Physical Trunk Interfaces
Use the following procedure to enable VSI functionality on specified trunk interfaces.
Step 1
Enter the uptrk command to bring up a specified trunk.
Step 2
Enter the addtrk command to add a specified trunk.
Step 3
Enter the cnfvsiif slot.port 3 to set SCT = 3
Step 4
Enter the cnfrsrc command to configure a VSI partition on the trunk interface.
Step 5
Enter the cnftrk command to configure the trunk to enable ILMI protocol to run on the BXM card by
enabling the “Protocol-by-the-card” option.
Step 6
Enter the cnfvsipart command to enable VSI ILMI functionality for the VSI partition.
Cisco SES PNNI Controller Software Configuration Guide
5-12
Release 1, Part Number 78-6123-05 Rev. A0, March 2001
Chapter5
Configuring ATM SVCs, PNNI Routing, and SPVCs
Configuring PNNI
Enable VSI ILMI Functionality on Virtual Trunk Interfaces
Use the following procedure to enable VSI ILMI functionality on virtual trunk interfaces.
Step 1
Enter the uptrk command to bring up a specified trunk
Step 2
Enter the cnfrsrc command to configure a VSI partition on the virtual trunk interface.
Step 3
Enter the cnftrk to configure the trunk VPI.
Step 4
Enter the cnfvsipart command to enable VSI ILMI functionality for the VSI partition.
Note
ILMI automatically runs on the BXM card for virtual trunks and, is therefore not
configurable.
Note
VSI ILMI can be enabled for only one VSI partition on trunk interfaces.
View VSI ILMI Functionality on Interfaces
Enter the dspvsipartcnf command to view VSI ILMI functionality status (whether enabled or not) for
various VSI partitions on the interface.
Configuring PNNI
The recommended configuration sequence for each SES PNNI node in the switched system is outlined
in Figure5-2.
All tasks are configurable using the SES PNNI Controller CLI. Some of the tasks, as indicated in
Figure5-2, can be configured using CiscoView.
Cisco SES PNNI Controller Software Configuration Guide
Release 1, Part Number 78-6123-05 Rev. A0, March 2001
5-13
Chapter5
Configuring ATM SVCs, PNNI Routing, and SPVCs
Configuring PNNI
Figure5-2
PNNI Configuration Sequence Overview
For more information about PNNI Controller commands, refer to the SES PNNI Command Reference .
For more information about SES PNNI Controller shelf commands, refer to “Shelf Operations
Commands” in the Cisco SES Controller Command Reference.
For more information about CiscoView PNNI menus, refer to WAN CiscoView 3.2 , Chapter7,
“Network Management.”
Cisco SES PNNI Controller Software Configuration Guide
5-14
Release 1, Part Number 78-6123-05 Rev. A0, March 2001
Chapter5
Configuring ATM SVCs, PNNI Routing, and SPVCs
Configuring PNNI
Configure the BPX PNNI Node
Use the addpnni-node and cnfpnni-node commands to set up the PNNI node and configure the
following parameters:
•
Node AESA
•
Administrative status
•
Node ID
•
Node PG ID
•
Level Indicator
•
Node representation
•
Transit restriction
•
Branching restriction
Before changing a node index configuration, the node index must be disabled. Enter the cnfpnni-node
-enable false command to disable the node index.
Enter the cnfpnni-node -enable true command to enable the node index.
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
Cisco SES PNNI Controller Software Configuration Guide
Release 1, Part Number 78-6123-05 Rev. A0, March 2001
5-15
Chapter5
Configuring ATM SVCs, PNNI Routing, and SPVCs
Configuring PNNI
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:
cnfpnni-election 1 -priority 1
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
Cisco SES PNNI Controller Software Configuration Guide
5-16
Release 1, Part Number 78-6123-05 Rev. A0, March 2001
Chapter5
Configuring ATM SVCs, PNNI Routing, and SPVCs
Configuring PNNI
Enter the cnfpnni-timer <node-index> <-parameter > < number > command to set PTSE refresh interval:
orioses1.1.1.PXM.a > cnfpnni-timer 1 -ptseRefreshInterval 1000
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
Release 1, Part Number 78-6123-05 Rev. A0, March 2001
5-17
Chapter5
Configuring ATM SVCs, PNNI Routing, and SPVCs
Configuring PNNI
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
5-18
Release 1, Part Number 78-6123-05 Rev. A0, March 2001
Chapter5
Configuring ATM SVCs, PNNI Routing, and SPVCs
Configuring PNNI
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 dsppnn i-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.
Cisco SES PNNI Controller Software Configuration Guide
Release 1, Part Number 78-6123-05 Rev. A0, March 2001
5-19
Chapter5
Configuring ATM SVCs, PNNI Routing, and SPVCs
Configuring PNNI
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)
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.
Cisco SES PNNI Controller Software Configuration Guide
5-20
Release 1, Part Number 78-6123-05 Rev. A0, March 2001
Chapter5
Configuring ATM SVCs, PNNI Routing, and SPVCs
Configuring PNNI
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
•
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
Release 1, Part Number 78-6123-05 Rev. A0, March 2001
5-21
Chapter5
Configuring ATM SVCs, PNNI Routing, and SPVCs
Setting Up SVCs
Setting Up SVCs
After setting up the UNI ports, NNI trunks, and PNNI, you are ready to setup SVC and SPVC in a
network. This section will explain how to set up an SVC. A two-node network is used to describe the
SVC set up procedure.
Figure5-3
SVC Set Up Example
Set up an SVC without ILMI Address Registration
Use the following procedure to set up an SVC without ILMI address registration.
In the example, the user sets up addresses on orioses1 and orioses3 before placing the SVC call. CPE
#1 has ATM address: 47.00918100000000d058ac26b6.000000010800.00, and CPE #2 has the
ATM address: 47.00918100000000107bc154b5.000000010300.00.
Add CPE #1 ATM address on orioses3 UNI port 1.3:
orioses3.1.1.PXM.a > addaddr 1.3 47.00918100000000d058ac26b6.000000010800.00 160
Add ATM summary address on orioses3:
orioses3.1.1.PXM.a > addpnni-summary-addr 1 47.00918100000000d058ac26b6 104
Step 1
Enter the addaddr command to add CPE #2 ATM address on orioses1 UNI port 1.8:
orioses1.1.1.PXM.a > addaddr 1.8 47.00918100000000107bc154b5.000000010300.00 160
Step 2
Enter the addpnni-summary-addr command to add an ATM summary address on orioses1:
orioses1.1.1.PXM.a > addpnni-summary-addr 1 47.00918100000000107bc154b5 104
Step 3
Enter dsppnni-reachable-addr network to see the summary address of the other node.
Step 4
Place a SVC call from CPE #1 to CPE #2 and enter the dsppncons command to display SVC connection
between two nodes.
-----------------------------------------------------------------------------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
------------------------------------------------------------------------------
Cisco SES PNNI Controller Software Configuration Guide
5-22
Release 1, Part Number 78-6123-05 Rev. A0, March 2001
Chapter5
Configuring ATM SVCs, PNNI Routing, and SPVCs
Set Up Address Filtering
Set up an SVC with ILMI Address Registration
Use the following procedure to setup an SVC with ILMI address registration:
Step 1
Enter the cnfport command to configure orioses3 UNI 1.3 with ILMI enabled.
Step 2
Enter the cnfport command to configure orioses1 UNI 1.8 with ILMI enabled.
Make sure both CPE#1 and CPE#2 have ILMI turned on.
Step 3
Enter the addprfx command to add Address Prefix on orioses3 and orioses1:
orioses3.1.1.PXM.a > addprfx 1.3 47.00918100000000d058ac26b6
orioses1.1.1.PXM.a > addprfx 1.8 47.00918100000000107bc154b5
Step 4
Enter the dsppnni-reachable-addr local command to see the registered address.
Step 5
Place an SVC call from CPE #1 to CPE #2 with ATM address:
47.00918100000000d058ac26b6.00d058ac4021.00
where 00d058ac4021 is the MAC addr of CPE#2
Set Up Address Filtering
Configure an Address Filter To Reject a Specific Called Party on the Ingress
Use the following procedure to configure an address filter to reject a specific called party on the ingress.
Step 1
Enter the addfltset command to c reate 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
Step 3
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
Step 4
Since no addresses have been added yet to the created firstfilter, the dspfltset -name
command does not show any information.
Enter the cnffltset command to add an address to a filter.
Cisco SES PNNI Controller Software Configuration Guide
Release 1, Part Number 78-6123-05 Rev. A0, March 2001
5-23
Chapter5
Configuring ATM SVCs, PNNI Routing, and SPVCs
Set Up Address Filtering
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 6).
espses1.1.PXM.a > cnffltset firstfilter -address 4722222222222222222222222222222
222222222 -length 160 -list called -accessMode deny
Step 5
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 6
Enter the cnfpnportacc command to attach the filter to a port. In the following example, 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 7
Enter the dsppnport command to display the port information and verify that the filter is correctly
bound to the port on the ingress. 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 3.
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 8
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
Cisco SES PNNI Controller Software Configuration Guide
5-24
Release 1, Part Number 78-6123-05 Rev. A0, March 2001
Chapter5
Configuring ATM SVCs, PNNI Routing, and SPVCs
Set Up Address Filtering
Configure an Address Filter To Reject a Specific Calling Party on the Ingress
Use the following procedure 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 >
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
Enter the cnfpnportacc command to 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
Cisco SES PNNI Controller Software Configuration Guide
Release 1, Part Number 78-6123-05 Rev. A0, March 2001
5-25
Chapter5
Configuring ATM SVCs, PNNI Routing, and SPVCs
Set Up Address Filtering
Configure an Address Filter To Reject a Specific Calling Party and Called Party
on the Ingress
Use the following procedure to configure an address filter to reject 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 >
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.
espses1.1.PXM.a > 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 cnfpnport command to attach the filter to the port:
espses1.1.PXM.a > cnfpnportacc 4.3 -in thirdfilter
Step 6
Make a call to ensure that address filtering is taking effect.
Cisco SES PNNI Controller Software Configuration Guide
5-26
Release 1, Part Number 78-6123-05 Rev. A0, March 2001
Chapter5
Configuring ATM SVCs, PNNI Routing, and SPVCs
Set Up Address Filtering
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.
Configure an Ingress 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
present in the SETUP message begins with a specific set of digits. The rest of the digits in the calling
party are not taken into account.
In the example, the user configures the filter to reject all calls whose calling party number begins with
the digits 47123. The user is adds address entries to the t hirdfilter . 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:
espses1.1.PXM.a > 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.
Cisco SES PNNI Controller Software Configuration Guide
Release 1, Part Number 78-6123-05 Rev. A0, March 2001
5-27
Chapter5
Configuring ATM SVCs, PNNI Routing, and SPVCs
Set Up Address Filtering
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
Configure an Ingress Filter to Reject all Calls Whose Calling Party Ends with a
Specific Set Of Digits
Use the following procedure to configure and ingress filter to reject all calls whose calling party number
in the SETUP message ends with the digits 56789.
In the example, the user is adding address entries to the already created thirdfilter . The filter is 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:
espses1.1.PXM.a > 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
Cisco SES PNNI Controller Software Configuration Guide
5-28
Release 1, Part Number 78-6123-05 Rev. A0, March 2001
Chapter5
Configuring ATM SVCs, PNNI Routing, and SPVCs
Set Up Address Filtering
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
--------------------------------------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 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.
Cisco SES PNNI Controller Software Configuration Guide
Release 1, Part Number 78-6123-05 Rev. A0, March 2001
5-29
Chapter5
Configuring ATM SVCs, PNNI Routing, and SPVCs
Set Up Address Filtering
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
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 deletes 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, the user may create a filter to reject calling addresses which do not match any entry in the
filter.
Cisco SES PNNI Controller Software Configuration Guide
5-30
Release 1, Part Number 78-6123-05 Rev. A0, March 2001
Chapter5
Configuring ATM SVCs, PNNI Routing, and SPVCs
Set Up Address Filtering
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
Step 5
Make a call and 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
Cisco SES PNNI Controller Software Configuration Guide
Release 1, Part Number 78-6123-05 Rev. A0, March 2001
5-31
Chapter5
Configuring ATM SVCs, PNNI Routing, and SPVCs
Set Up Address Filtering
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
5-32
Release 1, Part Number 78-6123-05 Rev. A0, March 2001
Chapter5
Configuring ATM SVCs, PNNI Routing, and SPVCs
Configuring an ATM SPVC
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 to be 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.
Configuring an ATM SPVC
You can provision an SPVC through the the SES PNNI Controller CLI, or through CWM. This section
describes how to use the PNNI Controller CLI to provision an SPVC. To provision an SPVC through
CWM, refer to Chapter 7, “Network Management.”
Cisco SES PNNI Controller Software Configuration Guide
Release 1, Part Number 78-6123-05 Rev. A0, March 2001
5-33
Chapter5
Configuring ATM SVCs, PNNI Routing, and SPVCs
Configuring an ATM SPVC
Configuring Node Prefix
Before setting up SPVCs, the SPVC Node Prefix (or Nodal SPVC prefix) must be configured. If it is
not, use the following procedures to configure it.
Step 1
Enter the
dspspvcprfx
command to display the SPVC Node Prefix:
pswpop4.1.1.PXM.a > dspspvcprfx
SPVC Node Prefix: 47.00918100000000107bc15339
Step 2
Enter cnfspvcprfx command to configure the SPVC Node Prefix:
pswpop4.1.1.PXM.a > cnfspvcprfx -prfx 4700918100000000c043002ddf
Step 3
Enter the
dspspvcprfx
command to confirm your SPVC prefix configuration:
pswpop4.1.1.PXM.a > dspspvcprfx
SPVC Node Prefix: 47.00918100000000c043002ddf
You can only configure an SPVC prefix when there is no connection on the node. The SPVC prefix must
be unique across the network.
Add an SPVC Connection
Figure 5-4 shows an example of an SPVC Setup.
Figure5-4
SPVC Setup Example
Use the following procedure to add an SPVC in a PNNI network.
Step 1
Enter the addcon command to add an SPVC Slave EndPoint.
pswpop9.1.PXM.a > addcon 9.8 111 111 1 2
LOCAL ADDR: 4700918100000000C043002DDF00000009080000.111.111
The LOCAL ADDR is the slave endpoint ATM address to be used at the master endpoint to setup an
SPVC to the slave endpoint.
Note
Service_type is selected to be 1 i.e. CBR service. The mastership is 2=slave.
Cisco SES PNNI Controller Software Configuration Guide
5-34
Release 1, Part Number 78-6123-05 Rev. A0, March 2001
Chapter5
Configuring ATM SVCs, PNNI Routing, and SPVCs
Configuring an ATM SPVC
Step 2
Enter the dspcon command to show the slave endpoint configuration.
pswpop9.1.PXM.a > dspcon 9.8 111 111
Port
Vpi Vci
Owner
State
------------------------------------------------------------------------Local 9:-1.8:-1
111.111
SLAVE
FAIL
Address: 47.00918100000000c043002ddf.000000090800.00
Remote Routed
0.0
MASTER
-Address: 00.000000000000000000000000.000000000000.00
-------------------- Provisioning Parameters -------------------Connection Type: VCC
Cast Type: Point-to-Point
Service Category: CBR
Conformance: CBR.1
Bearer Class: BCOB-X
Last Fail Cause: Invalid
Attempts: 0
Continuity Check: Disabled
Frame Discard: Disabled
L-Utils: 0
R-Utils: 0
Max Cost: 0
Routing Cost: 0
---------- Traffic Parameters ---------Tx PCR: 50
Rx PCR: 50
Tx SCR: 50
Rx SCR: 50
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:
------- SES Parameters only ---------Tx AIS: 1
Rx AIS: 0
Rx Abit:0
lpbk_type
: No Loopback
lpbk_dir
: ---lpbk_status
: None
round trip delay: 0 usec
Stats
: Disabled
Step 3
Enter the addcon command to add an SPVC Master EndPoint.
svcswp20.1.PXM.a > addcon 5.3 111 111 1 1
4700918100000000C043002DDF00000009080000.111.111
When the master endpoint is added, the SPVC manager on the SES controller will use the slave
endpoint ATM address to setup an SPVC towards the slave endpoint. The mastership is 1 = master.
Cisco SES PNNI Controller Software Configuration Guide
Release 1, Part Number 78-6123-05 Rev. A0, March 2001
5-35
Chapter5
Configuring ATM SVCs, PNNI Routing, and SPVCs
Configuring an ATM SPVC
The following example shows the master endpoint after the master SPVC is added.
svcswp20.1.PXM.a > dspcon 5.3 111 111
Port
Vpi Vci
Owner
State
------------------------------------------------------------------------Local 5:-1.3:-1
111.111
MASTER
OK
Address: 47.009181000000003071f8021e.000000050300.00
Remote Routed
111.111
SLAVE
-Address: 47.00918100000000c043002ddf.000000090800.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: 50
Rx PCR: 50
Tx SCR: 50
Rx SCR: 50
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:
------- 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
Cisco SES PNNI Controller Software Configuration Guide
5-36
Release 1, Part Number 78-6123-05 Rev. A0, March 2001
Chapter5
Configuring ATM SVCs, PNNI Routing, and SPVCs
Configuring an ATM SPVC
The following example shows the slave end point after a master SPVC has been added:
pswpop9.1.PXM.a > dspcon 9.8 111 111
Port
Vpi Vci
Owner
State
------------------------------------------------------------------------Local 9:-1.8:-1
111.111
SLAVE
OK
Address: 47.00918100000000c043002ddf.000000090800.00
Remote Routed
111.111
MASTER
-Address: 47.009181000000003071f8021e.000000050300.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: 50
Rx PCR: 50
Tx SCR: 50
Rx SCR: 50
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:
------- 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
Cisco SES PNNI Controller Software Configuration Guide
Release 1, Part Number 78-6123-05 Rev. A0, March 2001
5-37
Chapter5
Configuring ATM SVCs, PNNI Routing, and SPVCs
Configuring an ATM SPVC
Modify an SPVC Connection
Use the following procedure to modify an SPVC in a PNNI network. When an SPVC endpoint is
modified, the SPVC manager will re-establish the SPVC based on the new endpoint setup.
Step 1
Enter the cnfcon command to configure 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 > 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:
------- SES Parameters only ---------Tx AIS:0
Rx AIS:0
lpbk_type
:No Loopback
lpbk_dir
:---lpbk_status
:None
round_trip_delay:0
Stats
:Disabled
Step 3
Enter the cnfcon command to configure 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
Cisco SES PNNI Controller Software Configuration Guide
5-38
Release 1, Part Number 78-6123-05 Rev. A0, March 2001
Chapter5
Configuring ATM SVCs, PNNI Routing, and SPVCs
Configuring an ATM SPVC
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
-------------------------------------------------------------------------------
Delete an SPVC Connection
Enter the delcon slot.port <vpi> <vci> command to delete an SPVC endpoints. Delete the master
endpoint first, then delete the slave endpoint for each SPVC.
Cisco SES PNNI Controller Software Configuration Guide
Release 1, Part Number 78-6123-05 Rev. A0, March 2001
5-39
Chapter5
Configuring ATM SVCs, PNNI Routing, and SPVCs
Configuring SPVC Feeder Connection
Add an SPVP Connection
Use the following procedure to add an SPVP connection:
Step 1
Enter the addcon command to add a VCI of 0 to add an SPVP connection:
pswpop9.1.PXM.a > addcon 5.3 10 0 1 2
LOCAL ADDR:4700918100000000C043002DDF00000005030000.10.0
pswpop9.1.PXM.a > addcon 5.3 11 0 1 1
4700918100000000C043002DDF00000005030000.10.0
Step 2
Enter the dspcons command to verify the results:
pswpop9.1.PXM.a > dspcons
Local Port
Vpi.Vci
Remote Port
Vpi.Vci
State
Owner
----------------------------+-----------------------------+-------+-----5.3
2 200
5.3
3 300
OK
SLAVE
Local Addr:47.00918100000000c043002ddf.000000050300.00
Remote Addr:47.00918100000000c043002ddf.000000050300.00
5.3
3 300
5.3
2 200
OK
MASTER
Local Addr:47.00918100000000c043002ddf.000000050300.00
Remote Addr:47.00918100000000c043002ddf.000000050300.00
5.3
10 0
5.3
11 0
OK
SLAVE
Local Addr:47.00918100000000c043002ddf.000000050300.00
Remote Addr:47.00918100000000c043002ddf.000000050300.00
5.3
11 0
5.3
10 0
OK
MASTER
Local Addr:47.00918100000000c043002ddf.000000050300.00
Remote Addr:47.00918100000000c043002ddf.000000050300.00
In this example, the SPVP is looped back on the same port. An SPVP connection can not be added if a
VCC connection exists with same VPI.
Configuring SPVC Feeder Connection
Use the following procedure to setup SPVC feeder connections on the SES. Configure the feeder node
feeder trunk with Service Class Template (SCT) 3. This is required to disable the policing for SPVC
connections terminated on the feeder trunk. Configure feeder node feeder trunk as follows.
Set up the feeder trunk on the MGX 8850.
To configure the MGX 8850 feeder trunk, follow these steps:
Step 1
At the MGX 8850, configure the feeder node feeder trunk with LMI/Annex G enabled.
Step 2
Enter the following commands to configure the feeder trunk.
•
addln
•
addport
•
cnfswfunc
•
cnfifastrk
Cisco SES PNNI Controller Software Configuration Guide
5-40
Release 1, Part Number 78-6123-05 Rev. A0, March 2001
Chapter5
Configuring ATM SVCs, PNNI Routing, and SPVCs
Configuring SPVC Feeder Connection
An example of the all above commands listed below.
addport port# line# %BW min-vpi max-vpi
cnfswfunc -ndtype fdr
cnfifastrk slot.port if-type
jcfb8850.1.7.PXM.a > addln -sonet 7.1
Step 3
Enter the dspln command to display the new line’s parameters.
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 4
Enter the addport command to create a logical port.
jcfb8850.1.7.PXM.a > addport 1 1 100 0 4095
Step 5
Enter the dspports command to display the new logical port’s parameters.
jcfb8850.1.7.PXM.a > dspports
Port Status Line PctBw minVpi maxVpi maxRatePct
-----------------------------------------------------1
ON
1
100
0
4095
100
Step 6
Enter the cnfswfunc command to configure the software functionality.
jcfb8850.1.7.PXM.a > cnfswfunc -ndtype fdr
Step 7
Enter the dspifs command to display the interface parameters.
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, Part Number 78-6123-05 Rev. A0, March 2001
5-41
Chapter5
Configuring ATM SVCs, PNNI Routing, and SPVCs
Configuring SPVC Feeder Connection
Set up the Feeder trunk on the BPX
Use the following steps to configure the BPX feeder trunk.
Step 1
Enter the
uptrk
command on the BPX:
sjbpxbxm>uptrk 3.4
sj862241
TN
Cisco
BPX 8620
9.3.10
Nov. 10 2000 15:51 PST
Trunk: 3.4
Service Class Template ID: 3
VSI Partitions :
channels
Part E/D
min
max
1
D
0
0
2
D
0
0
3
D
0
0
Step 2
bw
min
0
0
0
vpi
start end
0
0
0
0
0
0
max
0
0
0
ilmi
D
D
D
Enter the cnfvsiif command:
sjbpxbxm> cnfvsiif 3.4 3
sj862241
TN
Cisco
BPX 8620
9.3.10
Nov. 10 2000 16:20 PST
Trunk : 3.4
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:
Step 3
/-1
/-1
Full Port Bandwidth: 353208
Maximum PVC Bandwidth: 98207
(Statistical Reserve: 5000)
PVC VPI RANGE [2]: -1
PVC VPI RANGE [4]: -1
1
Enabled
1000
/4000
4
/4095
100000 /250000
CLR
2
Disabled
0
/0
0
/0
0
/0
CLR
/-1
/-1
3
Disabled
0
/0
0
/0
0
/0
CLR
Enter the cnfrsrc command:
sjbpxbxm> cnfrsrc 3.4 256 100000 y 1 e 1000 4000 4 4095 100000 250000
sj862241
TN
Cisco
BPX 8620
9.3.10
Nov. 10 2000 16:28 PST
BPX 8620 Interface Shelf Information
Trunk
Name
Type
Part Id
Ctrl Id
3.4
10.4
jcfb8850
sjses58
AAL/5
AAL/5
1
2
Control_VC
VPI VCIRange
0
40-54
Alarm
MAJ
OK
Cisco SES PNNI Controller Software Configuration Guide
5-42
Release 1, Part Number 78-6123-05 Rev. A0, March 2001
Chapter5
Configuring ATM SVCs, PNNI Routing, and SPVCs
Configuring SPVC Feeder Connection
Step 4
Enter the addshelf command :
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
Step 5
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
Enter the cnftrk command:
sjbpxbxm> cnftrk 3.4 Y 5000 7F V,TS,NTS,FR,FST,CBR,NRT-VBR,ABR,RT-VBR N 10 N N
Cisco SES PNNI Controller Software Configuration Guide
Release 1, Part Number 78-6123-05 Rev. A0, March 2001
5-43
Chapter5
Configuring ATM SVCs, PNNI Routing, and SPVCs
Configuring SPVC Feeder Connection
Set up an SPVC 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:
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 dsppnports command:
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 to disable the OAM segment endpoint on the feeder trunk:
jceases.1.PXM.a > cnfoamsegep 3.4 no
Cisco SES PNNI Controller Software Configuration Guide
5-44
Release 1, Part Number 78-6123-05 Rev. A0, March 2001
Chapter5
Configuring ATM SVCs, PNNI Routing, and SPVCs
Configuring SPVC Feeder Connection
Step 4
Enter the dspoamsegep command to make sure the OAM segment endpoint is disabled:
jceases.1.PXM.a > dspoamsegep 3.4
Port
3.4
Step 5
OAM End Point
No
Enter the addcon command to add a connection.
At the slave endpoint:
sjses58.1.PXM.a > addcon 3.4 5 100 1 2
LOCAL ADDR: 47009181000000003071F8030D00000003040000.5.100
At the master endpoint:
sjses58.1.PXM.a > addcon 3.4 6 100 1 1 47009181000000003071F8030D00000003040000.5.100
Step 6
Enter the dspcons command to display all connections. Make sure the connection you added in Step 5
appears:
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
Set up the PVC segment on an MGX 8850 Feeder Node
Follow these steps to set up the PVC segment on feeder node (MGX 8850) for each Frame Relay port.
Step 1
Enter the cc command to change to card 3 (in the example, it is a FRSM card):
jcfb8850.1.7.PXM.a > cc 3
Step 2
Enter the addln command to change to add a line:
jcfb8850.1.3.FRSM.a > addln 1
Cisco SES PNNI Controller Software Configuration Guide
Release 1, Part Number 78-6123-05 Rev. A0, March 2001
5-45
Chapter5
Configuring ATM SVCs, PNNI Routing, and SPVCs
Configuring SPVC Feeder Connection
Step 3
Enter the dspln command on the new line to be sure the line was added:
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 1 1 2 1 7 1
Step 5
Enter the dspports command on the new line to be sure the port was added:
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 addconn command to add a new connection:
jcfb8850.1.3.FRSM.a > addcon 1 101 15360 1 1 1 1 jcfb8850.0.1.5.100 9
Step 7
Enter the dspchans command to be sure the connection was added properly:
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 t o set up the second PVC Connection on Second Service Module (Frame
Relay) Card #2.
Step 1
Enter the cc command to change to card 3 (in the example, it is a FRSM card):
jcfb8850.1.7.PXM.a > cc 2
Step 2
Enter the addln command to change to add a line:
jcfb8850.1.2.VHS2CT3.a > addln 1
Cisco SES PNNI Controller Software Configuration Guide
5-46
Release 1, Part Number 78-6123-05 Rev. A0, March 2001
Chapter5
Configuring ATM SVCs, PNNI Routing, and SPVCs
Configuring SPVC Feeder Connection
Step 3
Enter the addport command to change to add a port :
jcfb8850.1.2.VHS2CT3.a > addport 1 1 2 1 7 1
Step 4
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 5
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 :
jcfb8850.1.2.VHS2CT3.a > addcon 1 200 15360 1 1 2 1 1
jcfb8850.0.1.6.100
Step 6
Enter the dspconss command on the new connection to be sure it was added properly :
jcfb8850.1.2.VHS2CT3.a > dspcons
Line
ConnId
DE Type Alarm
---- --------------------- ----- ----1
jcfb8850.2.1.0.200
NIW
Yes
ChanNumNextAvailable:
Step 7
Chan EgrQ ServType
I/EQDepth
I/EQDEThre
I/EECNThre
Fst/
---- ---- --------- ---- ----- ----- ----- ----- ----- --21
n/a CBR
65535/65535 32767/32767
6553/6553
Dis/Dis
22
Enter the dspchans command to display all channels on the node:
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
Step 8
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
Enter the cc command to change to the card in slot 7:
jcfb8850.1.2.VHS2CT3.a > cc 7
(session redirected)
Cisco SES PNNI Controller Software Configuration Guide
Release 1, Part Number 78-6123-05 Rev. A0, March 2001
5-47
Chapter5
Configuring ATM SVCs, PNNI Routing, and SPVCs
Configuring SPVC Feeder Connection
Step 9
Step 10
Enter the dspcons command to display a summary of Soft PVCs on all ports:
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 in slot 3 (the PXM):
jcfb8850.1.7.PXM.a > cc 3
(session redirected)
Step 11
Enter the dspchans command to display all channels on card 3 (the FRSM):
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 12
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 16
TestDelay in progress.
TestDelay Passed with 41 ms.
Step 13
Enter the cc command to change to the card in slot 2 (the VHS card):
jcfb8850.1.3.FRSM.a > cc 2
(session redirected)
Step 14
Enter the dspchans command to display all connections on card 2:
jcfb8850.1.2.VHS2CT3.a > dspcons
Line
ConnId
DE Type Alarm
---- --------------------- ----- ----1
jcfb8850.2.1.0.200
NIW
No
ChanNumNextAvailable:
Chan EgrQ ServType
I/EQDepth
I/EQDEThre
I/EECNThre
Fst/
---- ---- --------- ---- ----- ----- ----- ----- ----- --26
n/a CBR
65535/65535 32767/32767
6553/6553
Dis/Dis
27
Cisco SES PNNI Controller Software Configuration Guide
5-48
Release 1, Part Number 78-6123-05 Rev. A0, March 2001
Chapter5
Configuring ATM SVCs, PNNI Routing, and SPVCs
Configuring Dynamic/Soft Partitioning
Step 15
Enter the tstdelay command to verify the continuity of the connection on the card in slot 3:
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
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 VPI/VCI range is being
altered, then ILMI experiences a “Loss of Connectivity” as a result of the change in VPI/VCI range.
Depending on how 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 following manner:
cnfilmiproto port_id -securelink no -attachmentpoint no
Configuring SPVC Stats Collection
Use the following procedure to enable SPVC stats collection on an SES:
Step 1
Check the SNMP configuration both on BCC and PXM (for example, community strings and Network
IP addresses and ATM IFIP).
Step 2
Use the cnfcdparm <slotId> <stat-level> command to set the stats level on BCC.
There should 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.
Step 3
Add an SPVC connections with stats enabled
To add SPVC connections with stats enabled, the -stats enable option must be enabled in the addcon
command. To enable stats on existing SPVCs, modify the connections with cnfcon and enable the
-stats enable option with this command.
Step 4
Stats configuration on CWM:
a.
Telnet to the PXM card and setup CWM's IP address for stats using cnfstatsmgr
In the SCM GUI (e.g. “runScmGui <host>”):
a.
Click the node tab.
b.
Navigate to a node; for example, nmsbpx14.
Cisco SES PNNI Controller Software Configuration Guide
Release 1, Part Number 78-6123-05 Rev. A0, March 2001
5-49
Chapter5
Configuring ATM SVCs, PNNI Routing, and SPVCs
Configuring SPVC Stats Collection
c.
Telnet to nmsbpx14.
d.
Run the following command: cnfstatmast <your scmctrlsvr host ip>
e.
Enable stats by edit default parameters.
f. Add the required stat id's and start collecting.
g.
Step 5
Wait more than 15 minutes to see if any stats file has been collected.
If no files are being collected after 30 minutes, check the error logs for any error messages.
For the installation of SCM GUI check the CWM configuration guide. There should be a section on the
following installations:
•
installation CWM.
•
add user information in node_info table.
•
install SCM.
•
run SCM GUI.
Cisco SES PNNI Controller Software Configuration Guide
5-50
Release 1, Part Number 78-6123-05 Rev. A0, March 2001
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
Figure6-1 shows the LEDs and switches available on the front of the PXM card. Table6-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, Part Number 78-6123-05 Rev. A0, March 2001
6-1
Chapter6
Viewing and Responding to Alarms
Viewing and Responding to Alarms using Physical Switch Controls
Figure6-1
Table6-1
PXM Front Card Controls
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, Part Number 78-6123-05 Rev. A0, March 2001
Chapter6
Viewing and Responding to Alarms
Viewing and Responding to Alarms using Physical Switch Controls
Table6-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, Part Number 78-6123-05 Rev. A0, March 2001
6-3
Chapter6
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, Part Number 78-6123-05 Rev. A0, March 2001
Chapter6
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 is an example 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, Part Number 78-6123-05 Rev. A0, March 2001
6-5
Chapter6
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 .
Cisco SES PNNI Controller Software Configuration Guide
6-6
Release 1, Part Number 78-6123-05 Rev. A0, March 2001
Chapter6
Viewing and Responding to Alarms
Displaying Error Information
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).
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:
dsperr
[-en <error slot>] [-sl<slot number>]
Cisco SES PNNI Controller Software Configuration Guide
Release 1, Part Number 78-6123-05 Rev. A0, March 2001
6-7
Chapter6
Viewing and Responding to Alarms
Displaying Error Information
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
6-8
Release 1, Part Number 78-6123-05 Rev. A0, March 2001
C H A P T E R
7
Network Management
This chapter describes the following network management tools you can use with Cisco SES PNNI
nodes and PNNI networks:
•
Cisco WAN Manager SES 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 network management workstation.
Hardware
This section lists the hardware requirements for a Cisco WAN Manager network management
workstation. Table7-1 lists the minimum workstation requirements. Using a workstation that meets
these requirements ensures sufficient performance.
Table7-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, Part Number 78-6123-05 Rev. A0, March 2001
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. Table7-2 describes the configuration for each platform.
Table7-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.
Table7-2 lists recommended CWM platforms based on the size of 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.
Software
This section lists the required software to install on the Cisco WAN Manager Network Management
workstation to manage the SES PNNI nodes and PNNI networks.
Cisco SES PNNI Controller Software Configuration Guide
7-2
Release 1, Part Number 78-6123-05 Rev. A0, March 2001
Chapter 7
Network Management
Installing and Configuring Cisco WAN Manager
•
Version 10.2 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.2
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.2 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.2 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.
Partitioning One 9-GB Disk
This section describes how to partition a CWM workstation’s single 9-GB disk drive. The following
procedure ensures that all but the final partition will be at a set size.
Cisco SES PNNI Controller Software Configuration Guide
Release 1, Part Number 78-6123-05 Rev. A0, March 2001
7-3
Chapter 7
Network Management
Installing and Configuring Cisco WAN Manager
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.
Table7-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, Part Number 78-6123-05 Rev. A0, March 2001
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 Table7-3.
Note
Do not partition the second disk. The second disk is automatically partitioned during the
CWM software installation.
Table7-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 SES 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!.
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.
Cisco SES PNNI Controller Software Configuration Guide
Release 1, Part Number 78-6123-05 Rev. A0, March 2001
7-5
Chapter 7
Network Management
WAN CiscoView 3.2
Configuring the SES PNNI Controllers
To configure a PXM-SES card, telnet to the card and execute 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 pnni 10
assumes a BXM in slot 9
Cisco WAN Manager SES PNNI Features
Cisco WAN Manager (CWM) provides the following features for the Cisco SES PNNI controller:
•
SPVC connection management between Release 1.0 Cisco SES PNNI 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 GU I
SPVC Overview
Table7-5 lists the types of SPVCs supported by the SES PNNI controller using CWM 10.2.
Table7-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 Cisco SES PNNI controller is managed through WAN CiscoView 3.2. WAN CiscoView 3.2
requires Release 5.1 o f the CiscoView Engine, which is included on the CWM 10.2 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 Cisco
SES PNNI 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 Cisco SES PNNI controller.
Cisco SES PNNI Controller Software Configuration Guide
7-6
Release 1, Part Number 78-6123-05 Rev. A0, March 2001
Chapter 7
Network Management
WAN CiscoView 3.2
Installing CiscoView
During the CWM 10.2 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 10.2 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
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.
Cisco SES PNNI Controller Software Configuration Guide
Release 1, Part Number 78-6123-05 Rev. A0, March 2001
7-7
Chapter 7
Network Management
WAN CiscoView 3.2
Main Menu Buttons
Table7-6 describes the Main Menu buttons.
Table7-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.
About
Displays the following information:
Help
•
CiscoView release version and copyrights
•
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
Table7-7 describes the options on the status bar and buttons.
Table7-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.
Cisco SES PNNI Controller Software Configuration Guide
7-8
Release 1, Part Number 78-6123-05 Rev. A0, March 2001
Chapter 7
Network Management
WAN CiscoView 3.2
Table7-7
CiscoView Status Bar and Buttons (continued)
Status Bar/Button
Description
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.
Cisco SES PNNI Controller Software Configuration Guide
Release 1, Part Number 78-6123-05 Rev. A0, March 2001
7-9
Chapter 7
Network Management
WAN CiscoView 3.2
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.
Popup Menu Options
Table7-8 describes the options on the popup menu.
Table7-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 have installed CiscoView and learned to navigate within it, you can perform various tasks.
Starting CiscoView
Depending on your platform, you can start CiscoView:
•
Within CWM 10.2, by selecting a device on the Topology map.
•
From the command line, by entering 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, Part Number 78-6123-05 Rev. A0, March 2001
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, Part Number 78-6123-05 Rev. A0, March 2001
7-11
Chapter 7
Network Management
WAN CiscoView 3.2
Device-Specific Buttons within Configure Menu
Table7-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.
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.
Cisco SES PNNI Controller Software Configuration Guide
7-12
Release 1, Part Number 78-6123-05 Rev. A0, March 2001
Chapter 7
Network Management
Testing Basic Connectivity and Setup
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
Troubleshooting
The following information describes 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.
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:
•
Polling Frequency (sec.): 60
•
SNMP Timeout (sec.): 20
•
SNMP Retry Count: 1
•
Show MIB Label as: Alias
Cisco SES PNNI Controller Software Configuration Guide
Release 1, Part Number 78-6123-05 Rev. A0, March 2001
7-13
Chapter 7
Network Management
Call Tracing
Call Tracing
The Cisco SES PNNI 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—Point-to-Point, or Point-to-Multipoint—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 a p2p call, and in addition endpoint reference for p2mp call. This
generates a TRACE CONNECTION message, which includes Trace Transit List (TTL) IE. This
message would always 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 call record of the existing connection, using CallRef and
EndPtRef (p2mp). The destination node makes the portId zero.
This feature is not supported on an IISP 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 out the path taken by an existing connection.
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. Feature is disabled and the node refuses to participate.
3. 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 SES PNNI Command Reference, Release 1 for command syntax details.
Cisco SES PNNI Controller Software Configuration Guide
7-14
Release 1, Part Number 78-6123-05 Rev. A0, March 2001
Chapter 7
Network Management
Call Tracing
conntrace Command
Refer to the the SES PNNI Command Reference, Release 1, for the full syntax of the conntrace
command
Figure7-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 (similar to as if its a UNI). This would enable the user
to complete a partial trace.
Figure7-1
Connection Trace in PNNI and IISP Network
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.
3. Call Clear/Retain (X): The call is cleared immediately after reaching the destination node if the flag
is enabled by sending Release/AddParty Reject and so on, else it is established by sending Connect.
These messages contain the TTL IE with proper status codes.
Note
This feature is not a safeguard against mis-configuration, to prevent the calls from being
released inadvertently.
Cisco SES PNNI Controller Software Configuration Guide
Release 1, Part Number 78-6123-05 Rev. A0, March 2001
7-15
Chapter 7
Network Management
Call Tracing
4. VPI/VCI values (V): If enabled, VPI/VCI values of the egress port are filled up in the TTL IE at
every node.
5. 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.
Path Trace Success
The information from the response message is displayed using show commands. This information
includes the TTL IEs 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:
•
pathtrace-node
•
pathtrace-if
•
pathtrace-ie
Their syntax is described in the SES PNNI Command Reference, Release 1, Chapter 2, “SVC, SPVC,
and PNNI Commands.”
pathtrace-node
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.
pathtrace-if
This command is for incoming calls on a source node. Signalling 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, Part Number 78-6123-05 Rev. A0, March 2001
Chapter 7
Network Management
Call Tracing
pathtrace-ie
This command is used for interoperability, when the Cisco SES PNNI controller is connected to
equipment which does not support path trace. It takes two options, described below.
•
removeIE
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 which 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.
•
insertIE
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.
Figure7-2 illustrates a sample network with pathtrace insert and remove IEs.
Figure7-2
Insert and Remove IEs
The Cisco SES PNNI 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 1MByte in size.
Cisco SES PNNI Controller Software Configuration Guide
Release 1, Part Number 78-6123-05 Rev. A0, March 2001
7-17
Chapter 7
Network Management
Call Tracing
Cisco SES PNNI Controller Software Configuration Guide
7-18
Release 1, Part Number 78-6123-05 Rev. A0, March 2001
A P P E N D I X
A
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
Physical specifications for the Service Expansion Shelf are listed in the Cisco Service
Expansion Shelf Hardware Installation Guide .
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.
The software must also be upgradable to support all enhancements defined in the PNNI V2.0, currently
being developed by the ATM Forum.
Other specifications to which the PNNI routing conforms are:
1.
ATM Forum, “PNNI Specification Version 1.0,” af-pnni-0055.000: March 1996
2.
ATM Forum, “PNNI V1.0 Errata and PICS,” March 1997, af-pnni-0081.000.
3.
ATM Forum, “Interim Inter-switch Signaling Protocol (IISP) Specification Version 1.0,” December
1994, af-pnni-0026.000.
4.
ATM Forum, “Interworking among ATM Networks (draft) Specification,” BTD-RA-IAN-01.07,
April 1998
5.
ATM Forum, “BISDN Inter Carrier Interface (B-ICI) Specification Version2.2,” February, 1997,
btd-bici-01.02.
Cisco SES PNNI Controller Software Configuration Guide
Release 1, Part Number 78-6123-05 Rev. A0, March 2001
A-1
AppendixA
Technical Specifications
ATM Signaling Compliance
ATM Signaling Compliance
The following ATM Forum signaling specifications are supported, and described in the following
sections:
Note
•
UNI 3.x Signaling
•
IISP Signaling
•
PNNI Signaling
•
ATM Signaling Interworking
ITU recommendations for B-ISDN DSS2 Signaling is not currently supported.
UNI 3.x Signaling
UNI 3.x Signaling is supported.
Capability
Reference
Network Equipment
Mandatory//Optional
Support
Point-to-point calls
5.5
M
x
Point-to-multipoint calls
5.6
M
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
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
Point-to-multipoint calls
6.6
M
Narrowband ISDN
6.3.2, 6.4.7
O
Associated signaling
6.5.2.2.1
O
x
Non-associated signaling
6.5.2.2.2
O
x
ATM Parameter Negotiation
6.5.2.3.4
O
QOS Parameter Selection
6.5.2.3.5
O
x
ABR Signaling
6.5.2.3.6
O
x
Cisco SES PNNI Controller Software Configuration Guide
A-2
Release 1, Part Number 78-6123-05 Rev. A0, March 2001
AppendixA
Technical Specifications
ATM Signaling Compliance
Capability
Reference
Network Equipment
Mandatory//Optional
Support
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
O
x
Frame Discard
In addition to the above, the following PNNI 2.0 capabilities are supported on an interface 1 .
Network Equipment
Mandatory//Optional
Capability
Reference
Support
Connection Tracing
6.7
x
Path Tracing
6.7
x
ATM Signaling Interworking
Interworking between all combinations of signaling protocol will be 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
UNI 3.0
x
x
x
x
x
UNI 3.1
x
x
x
x
x
IISP 1.0
x
x
x
x
x
PNNI 1.0
x
x
x
x
x
Networking Application Support
The following networking applications are supported
Application
Support
LANE
x
Classical IP over ATM
(RFC 1577)
x
MPOA
x
MARS
VTOA
x
SPVC Services
x
1. PNNI 2.0 is yet to be finalized. A pre-standard connection trace and path trace are supported in this release.
Cisco SES PNNI Controller Software Configuration Guide
Release 1, Part Number 78-6123-05 Rev. A0, March 2001
A-3
AppendixA
Technical Specifications
Processor Switching Module Specifications
LANE, Classical IP over ATM, and MPOA will not be implemented as part of the SVC services in the
SES PNNI controller, but will be supported when they are running on equipment directly or indirectly
connected to it.
VTOA is implemented on MGX8850 Release 1.0. BPX/SES will support VTOA when MGX8850
Release 1.0 become a feeder node for BPX/SES.
SPVC service is supported and implemented in BPX/SES PNNI Controller in this release.
Interoperability Support
The SES PNNI controller is interoperable with all standards-compliant networking equipment.
The SES PNNI controller is also backward compatible with ESP v2.X.
Processor Switching Module Specifications
TableA-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)
TableA-1
PXM Specifications
Category
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
Control access:
These ports exits on the
PXM-UI back card.
Number of logical ports:
32 across all physical ports on the uplink card.
Cisco SES PNNI Controller Software Configuration Guide
A-4
Release 1, Part Number 78-6123-05 Rev. A0, March 2001
AppendixA
Technical Specifications
Processor Switching Module Specifications
TableA-1
PXM Specifications (continued)
Category
Description
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):
•
Green means active and okay.
•
Red means active and local alarm.
•
Yellow means active and remote alarm.
•
No light means inactive or not provided.
LEDs on back cards:
Green means active. No light means inactive or not provided.
Synchronization:
8 KHz clock derived from the following sources:
These clock sources satisfy
Stratum 4 requirements.
BITS clock interface:
Trunk history counters:
•
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.
Cisco SES PNNI Controller Software Configuration Guide
Release 1, Part Number 78-6123-05 Rev. A0, March 2001
A-5
AppendixA
Technical Specifications
Processor Switching Module Specifications
TableA-1
PXM Specifications (continued)
Category
Connection capacities
supported by PXM:
Processor clock speed and
memory specifics:
Alarm indicators (audible
and visual):
Description
•
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 Mbytes.
•
DRAM: 64 Mbytes, upgradeable to 128 Mbytes.
•
Secondary cache: 512 Kbytes.
•
BRAM: 128 Kbytes.
•
Hard disk: 2.1 Gbytes.
Central office-compatible alarm indicators and controls through a
DB15 connector.
Maintenance features:
•
Internal isolation loopback.
External remote loopback.
Hot-pluggable.
Card dimensions:
•
Front card: 15.65 inches by 16.83 inches.
Back card: 7.25 inches by 4.125 inches.
Power:
Requires –48 VDC, dissipates 150 W.
Cisco SES PNNI Controller Software Configuration Guide
A-6
Release 1, Part Number 78-6123-05 Rev. A0, March 2001
A P P E N D I X
B
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. FigureB-1 provides a simple illustration of VSI master and slave
relationship.
Cisco SES PNNI Controller Software Configuration Guide
Release 1, Part Number 78-6123-05 Rev. A0, March 2001
B-1
Appendix B
Virtual Switch Interface
Virtual Switch Interface Protocol
FigureB-1
VSI, Controller and Slave VSIs
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 FigureB-2. When enabled, the VSI
slaves in turn establish links between each other.
FigureB-2
VSI Master and VSI Slave Example
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 (FigureB-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
(FigureB-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
B-2
Release 1, Part Number 78-6123-05 Rev. A0, March 2001
Appendix B
Virtual Switch Interface
Virtual Switch Interface Protocol
FigureB-3
BXM Virtual Interfaces and Qbins
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 have been 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 TableB-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).
TableB-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
Partition Criteria shows the VPI ranges available for partitions on a BXM card.
Cisco SES PNNI Controller Software Configuration Guide
Release 1, Part Number 78-6123-05 Rev. A0, March 2001
B-3
Appendix B
Virtual Switch Interface
Virtual Switch Interface Protocol
TableB-2
Partition Criteria
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:
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, as in the following example for active
VSI partition 1 on a port interface 13.1
cnfvsipart 13.1 1 y
Cisco SES PNNI Controller Software Configuration Guide
B-4
Release 1, Part Number 78-6123-05 Rev. A0, March 2001
Appendix B
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 using 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
Use 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, Part Number 78-6123-05 Rev. A0, March 2001
B-5
Appendix B
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
B-6
Release 1, Part Number 78-6123-05 Rev. A0, March 2001
Appendix B
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 provide 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 contains 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 (e.g. 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 (FigureB-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, Part Number 78-6123-05 Rev. A0, March 2001
B-7
Appendix B
Virtual Switch Interface
Class of Service Templates
FigureB-4
Service Class Template Overview
Service Class Template Structure
Each template table row includes an entry that defines the Qbin to be used for that class of service
(FigureB-5).
This mapping defines a relationship between the template and the interface Qbin’s configuration.
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.
Cisco SES PNNI Controller Software Configuration Guide
B-8
Release 1, Part Number 78-6123-05 Rev. A0, March 2001
Appendix B
Virtual Switch Interface
Class of Service Templates
Qbin templates only are used 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.
Cisco SES PNNI Controller Software Configuration Guide
Release 1, Part Number 78-6123-05 Rev. A0, March 2001
B-9
Appendix B
Virtual Switch Interface
Class of Service Templates
FigureB-5
Service Class Template and Associated Qbin Selection
Cisco SES PNNI Controller Software Configuration Guide
B-10
Release 1, Part Number 78-6123-05 Rev. A0, March 2001
Appendix B
Virtual Switch Interface
Class of Service Templates
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>
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.
Cisco SES PNNI Controller Software Configuration Guide
Release 1, Part Number 78-6123-05 Rev. A0, March 2001
B-11
Appendix B
Virtual Switch Interface
Class of Service Templates
Qbin Dependencies
The available Qbin parameters are shown in TableB-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
16Qbins.
TableB-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.
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.
Cisco SES PNNI Controller Software Configuration Guide
B-12
Release 1, Part Number 78-6123-05 Rev. A0, March 2001
Appendix B
Virtual Switch Interface
Supported Service Types
Connection Admission Control
For Release 9.2, when a connection request is received by the VSI Slave, 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. TableB-4 lists the supported service types.
TableB-4
Service Category Listing
Service Category
VSI Special Types
Service Type
Identifiers
Service Types
Associated
Qbin
0x0000
Null
-
0x0001
Default
10
0x0002
Signaling
15
Cisco SES PNNI Controller Software Configuration Guide
Release 1, Part Number 78-6123-05 Rev. A0, March 2001
B-13
Appendix B
Virtual Switch Interface
Supported Service Types
TableB-4
Service Category Listing (continued)
Service Category
ATMF Types
Service Type
Identifiers
Service Types
Associated
Qbin
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, Class of Service
(COS) 0, per-class service
10
Tag 1, Class of Service
(COS) 1, per-class service
12
0x0201
0x0202
0x0203
0x0204
0x0205
0x0206
0x0207
0x0210
Tag 2, Class of Service
(COS) 2, per-class service
11
13
10
Tag 3, Class of Service
(COS) 3, per-class service
11
Tag 4, Class of Service
(COS) 0, per-class service,
shadow
13
12
14
Tag 5, Class of Service
(COS) 1, per-class service
Tag 6, Class of Service
(COS) 2, per-class service
Tag 7, Class of Service
(COS) 3, per-class service,
shadow
MPLS Types
Tag ABR, (Tag w/ ABR
flow control)
A summary of the parameters associated with each of the Service Class Templates is provided in
TableB-5 through TableB-8. TableB-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.
TableB-5 lists the parameters associated with Default (0x0001) and Signaling (0x0002) Service Class
Template categories.
Cisco SES PNNI Controller Software Configuration Guide
B-14
Release 1, Part Number 78-6123-05 Rev. A0, March 2001
Appendix B
Virtual Switch Interface
Supported Service Types
TableB-5
VSI Special Service Types
Parameter
VSI
Defau
lt
(0x00 VSI Signalling
01)
(0x0002)
QBIN
Number
10
15
UPC Enable
0
*
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_m
ax/4
*
VC CLPhi
Threshold
75
*
VC CLPlo
Threshold
30
*
VC EPD
Threshold
90
*
VC EFCI
Threshold
60
*
VC discard
selection
0
*
Cisco SES PNNI Controller Software Configuration Guide
Release 1, Part Number 78-6123-05 Rev. A0, March 2001
B-15
Appendix B
Virtual Switch Interface
Supported Service Types
TableB-6 and TableB-7 lists the parameters associated with the PNNI Service Class Templates.
TableB-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
*
*
*
*
*
*
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
B-16
Release 1, Part Number 78-6123-05 Rev. A0, March 2001
Appendix B
Virtual Switch Interface
Supported Service Types
TableB-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
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
* indicates not applicable
TableB-8 lists the connection parameters and their default values for MPLS (Tag Switching) Service
Class Templates.
TableB-8
MPLS (Tag Switching) Service Types
Parameter
CoS 0/4
CoS 1/5
CoS 2/6
CoS3/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
Release 1, Part Number 78-6123-05 Rev. A0, March 2001
B-17
Appendix B
Virtual Switch Interface
Supported Service Types
TableB-8
MPLS (Tag Switching) Service Types (continued)
Parameter
CoS 0/4
CoS 1/5
CoS 2/6
CoS3/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
TableB-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.
TableB-9
Connection Parameter Descriptions and Ranges
Object Name
Range/Values
Template Units
10 - 15
Qbin #
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
QBIN Number
1 - Enabled GCRAs
2 - Enable GCRA #1
3 - Enable GCRA #2
Cisco SES PNNI Controller Software Configuration Guide
B-18
Release 1, Part Number 78-6123-05 Rev. A0, March 2001
Appendix B
Virtual Switch Interface
Supported Service Types
TableB-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 0 - Discard
#1)
1 - Set CLP bit
enumeration
2 - Set CLP of
untagged cells,
disc. tag’d cells
Policing Action (GCRA 0 - Discard
#2)
1 - Set CLP bit
enumeration
2 - Set CLP of
untagged cells,
disc. tag’d 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 Factor
(RRDF)
1 - 15
enumeration
Reduced Format Rate
Increase Factor (RRIF)
1 - 15
enumeration
Reduced Format Time
Between Fwd RM cells
(RTrm)
0-7
enumeration
Cut-Off Number of RM 1 - 4095
Cells (CRM)
cells
Cisco SES PNNI Controller Software Configuration Guide
Release 1, Part Number 78-6123-05 Rev. A0, March 2001
B-19
Appendix B
Virtual Switch Interface
Supported Service Types
Cisco SES PNNI Controller Software Configuration Guide
B-20
Release 1, Part Number 78-6123-05 Rev. A0, March 2001
A P P E N D I X
C
SNMP Management Information Base
The SES PNNI Controller SNMP implementation uses the MGX 8800’s 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 PNNI 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, etc., 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 which convey management
information between the agents and the management stations.
MIB Tree
FigureC-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, Part Number 78-6123-05 Rev. A0, March 2001
C-1
AppendixC
SNMP Management Information Base
SNMP Fundamentals
FigureC-1
MIB Tree
The following OIDs 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:
iso.internet.mgmt.mib-2.system.sysDescr.0
Or, numerically:
1.3.6.1.2.1.1.1.0
Some Table objects can have more than one instance, but that’s a separate topic .
Cisco SES PNNI Controller Software Configuration Guide
C-2
Release 1, Part Number 78-6123-05 Rev. A0, March 2001
AppendixC
SNMP Management Information Base
SNMP Fundamentals
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 practise,
either is usually called an object identifier or OID.
Object Definitions
An object definition contains 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
DefValPart ::=
“DEFVAL”
| empty
END
Cisco SES PNNI Controller Software Configuration Guide
Release 1, Part Number 78-6123-05 Rev. A0, March 2001
C-3
AppendixC
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 to 2147483647)
OCTET STRING
String of bytes of length 0 to 65,535
OBJECT IDENTIFIER
Numeric ASN-1-type object identifier
Integer32
Integer-valued information between
(-2147483648 to 2147483647)
Unsigned32
Unsigned Integer-valued information between
(0 to 2147483647)
Co unter32
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,
INTEGER (0..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 (SIZE (0..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
C-4
Release 1, Part Number 78-6123-05 Rev. A0, March 2001
AppendixC
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:
cbr1(1),
vbr1RT(2),
vbr2RT(3),
vbr3RT(4),
vbr1nRT(5),
vbr2nRT(6),
vbr3nRT(7),
ubr1(8),
ubr2(9),
abr(10),
cbr2(11), and
cbr3(12).
CiscoWanLpbkTypes
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
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.
CiscoWanTestStatus
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 oprational status of an endpoint. The valid values are:
operOk(1), operFail(2), 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, Part Number 78-6123-05 Rev. A0, March 2001
C-5
AppendixC
SNMP Management Information Base
SNMP Fundamentals
Data Type
Description
CiscoWanAlarmState
Defines possible alarms at an endpoint:
• 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 could be attributed to either routing failure or to a
maintenance operation initiated by the networking entity.
• interfaceFail(8): The interface to which this connection belongs has
failed.
• ccFail (16): The 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
CiscoWanXmtState
Defines possible transmit states of an endpoint:
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
CiscoWanRcvState
Defines possible receive states of an endpoint
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
CiscoWanERSConfg
Defines possible configuration for Explicit Rate Stamping (ERS):
None(1) : Disable the ERS on connection
enableIngress(2) : Enable ERS in the Ingress direction ONLY
enableEgress(3) : Enable ERS in the Engress direction ONLY
enableBoth(4) : Enable ERS in both direction
CiscoWanVSVDConfg
Defines possible VSVD configuration applicable to an endpoint:
vsvdOff (1) : Disable VSVD
vsvdOn(2) : Enable VSVD
switchDefault(3) : Use default settings on switch.
Cisco SES PNNI Controller Software Configuration Guide
C-6
Release 1, Part Number 78-6123-05 Rev. A0, March 2001
AppendixC
SNMP Management Information Base
MIBs Supported by the PNNI Controller
Data Type
Description
CiscoWanAisIW
Defines an SPVC endpoint’s AIS capability:
e2eAisCapable(1) : Endpoint capable of detecting/generating e2e AIS.
segAisCapable(2) : Endpoint capable of detecting/generating seg AIS.
AbrRateFactors
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. The
purpose is to notify the management stations of some unusual event. Traps provide management stations
with the following information:
•
The network management subsystem that generated the trap (Enterprise)—Identifies the network
management subsystem that generated that 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.
•
The 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).
MIBs Supported by the PNNI Controller
•
ATM MIB Objects
•
PNNI MIB Objects
•
Cisco WAN ATM MIB Objects
ATM MIB Objects
•
atmInterfaceConfTable
Cisco SES PNNI Controller Software Configuration Guide
Release 1, Part Number 78-6123-05 Rev. A0, March 2001
C-7
AppendixC
SNMP Management Information Base
MIBs Supported by the PNNI Controller
atmInterfaceConfTable
The atmInterfaceConfTable contains ATM local interface configuration parameters, one entry per ATM
interface port. Althought the are many attributes for the table, SES only supports
atmInterfaceMyNeighborIpAddress and atmInterfaceMyNeighborIfName both as read-only access.
.
TableC-1
atmInterfaceConfTable Entries
No.
Object Type
Access
Description
11
atmInterface
MyNeighborI
pAddress
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
atmInterface
read-write
MyNeighborIf
Name
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.
PNNI MIB Objects
•
pnniBaseGroup
•
pnniNodeTable
•
pnniNodePglTable
•
pnniNodeTimerTable
•
pnniNodeSvccTable
•
pnniScopeMappingTable
•
pnniLinkTable
•
pnniSummaryAddressTable
Cisco SES PNNI Controller Software Configuration Guide
C-8
Release 1, Part Number 78-6123-05 Rev. A0, March 2001
AppendixC
SNMP Management Information Base
MIBs Supported by the PNNI Controller
pnniBaseGroup
TableC-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.
Reference: ATM Forum PNNI 1.0 Section 5.6.1
2
pnniLowestVersion
Read
Only
The lowest version of the PNNI protocol that the
software in this switching system is capable of
executing.
Reference: 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 etc.) 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, etc.) 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
Read
Only
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 for which this switching
system was not the crankback destination, only
those crankbacks that were directed to this
switching system are counted here.
7
pnniAltRouteCountOriginator
Read
Only
The total number of alternate DTL stacks that
this switching system has computed and placed
into signaling messages as the DTL originator.
Cisco SES PNNI Controller Software Configuration Guide
Release 1, Part Number 78-6123-05 Rev. A0, March 2001
C-9
AppendixC
SNMP Management Information Base
MIBs Supported by the PNNI Controller
TableC-2
pnniBaseGroup (continued)
No.
Object Type
Access
Description
8
pnniAltRouteCountBorder
Read
Only
The total number of alternate partial DTL stacks
that this switching system has computed and
placed into signaling messages as a entry border
node.
9
pnniRouteFailCountOriginator
Read
Only
The total number of times where 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 where 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
ginator
Read
Only
The total number of times where 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
pnniRouteFailUnreachableBor
der
Read
Only
The total number of times where 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 collects attributes that affect the operation of a PNNI logical node.
Note
createAndWait is not supportedas a rowStatus value for the pnniNodeRowStatus attribute.
Cisco SES PNNI Controller Software Configuration Guide
C-10
Release 1, Part Number 78-6123-05 Rev. A0, March 2001
AppendixC
SNMP Management Information Base
MIBs Supported by the PNNI Controller
Reference: ATM Forum PNNI 1.0 Annex F.
TableC-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
The level of PNNI
hierarchy at which this
node exists. This
attribute is used to
determine the default
node ID and the default
peer group ID for this
node. This object may
only be written when
pnniNodeAdminStatus
has the value down.
Default
96
Reference: ATM Forum
PNNI 1.0 Section 5.3.1
Annex F.
Cisco SES PNNI Controller Software Configuration Guide
Release 1, Part Number 78-6123-05 Rev. A0, March 2001
C-11
AppendixC
SNMP Management Information Base
MIBs Supported by the PNNI Controller
TableC-3
pnniNodeTable (continued)
No.
Object Type
Access
Description
3
pnniNodeId
read-create
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.
Default
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, then the default
node ID takes the form
defined in Section 5.3.3
for logical group nodes,
with the first octet equal
to pnniNodeLevel, the
next fourteen octets equal
to the value of
pnniNodePeerGroupId
for the child node whose
election as PGL causes
this LGN to be
instantiated, the next six
octets equal to the ESI of
pnniNodeAtmAddress,
and the last octet equal to
zero.
Cisco SES PNNI Controller Software Configuration Guide
C-12
Release 1, Part Number 78-6123-05 Rev. A0, March 2001
AppendixC
SNMP Management Information Base
MIBs Supported by the PNNI Controller
TableC-3
pnniNodeTable (continued)
No.
Object Type
Access
Description
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.
Default
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, Part Number 78-6123-05 Rev. A0, March 2001
C-13
AppendixC
SNMP Management Information Base
MIBs Supported by the PNNI Controller
TableC-3
pnniNodeTable (continued)
No.
Object Type
Access
Description
8
pnniNodeAtmAddress
read-create
This node’s ATM End
System Address. Remote
systems wishing to
exchange PNNI protocol
packets with this node
should direct packets or
calls to this address.
Default
This attribute may only
be written when
pnniNodeAdminStatus
has the value down.
Reference: ATM Forum
PNNI 1.0 Section 5.2.2
9
pnniNodePeerGroupId
read-create
The Peer Group
Identifier of the peer
group that the given node
is to become a member
of.
The default value of this
attribute has the first
octet equal to
pnniNodeLevel, the next
pnniNodeLevel bits
equal to the
pnniNodeLevel bits
starting from the third
octet ofpnniNodeId, and
the remainder padded
with zeros.
This object may only be
written when
pnniNodeAdminStatus
has the value down.
Reference: ATM Forum
PNNI 1.0 Section 5.3.2,
Annex F
Cisco SES PNNI Controller Software Configuration Guide
C-14
Release 1, Part Number 78-6123-05 Rev. A0, March 2001
AppendixC
SNMP Management Information Base
MIBs Supported by the PNNI Controller
TableC-3
pnniNodeTable (continued)
No.
Object Type
10
pnniNodeRestrictedTransi read-create
t
Access
Description
Default
Specifies whether the
node is restricted to not
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.
Reference: ATM Forum
PNNI 1.0 Section 5.8.1.2.3
11
pnniNodeComplexRep
read-create
Specifies whether this
node uses the complex
node representation. A
value of ‘true’ indicates
that the complex node
representation is used,
whereas 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
pnniNodeRestrictedBranc
hing
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, and 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
Release 1, Part Number 78-6123-05 Rev. A0, March 2001
C-15
AppendixC
SNMP Management Information Base
MIBs Supported by the PNNI Controller
TableC-3
pnniNodeTable (continued)
No.
Object Type
Access
Description
13
pnniNodeDatabaseOverlo
ad
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.
Default
Reference: 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
To create, delete,
activate, and deactivate a
Node.
pnniNodePglTable
Peer group leader election information for a PNNI node in this switching system.
Cisco SES PNNI Controller Software Configuration Guide
C-16
Release 1, Part Number 78-6123-05 Rev. A0, March 2001
AppendixC
SNMP Management Information Base
MIBs Supported by the PNNI Controller
Reference: ATM Forum PNNI 1.0 Section 5.10.1.
TableC-4
pnniNodePglTable
No.
Object Type
Access
Description
1
pnniNodePglLeadershipPr
iority
read-create
The Leadership priority value this
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
Default
0
Reference: ATM Forum PNNI 1.0
Section 5.10.1.2
2
pnniNodeCfgParentNodeI read-create
ndex
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.
0
Reference: ATM Forum PNNI 1.0
Annex F
3
pnniNodePglInitTime
read-create
The amount of time in seconds this
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.
15
Reference: ATM Forum PNNI 1.0
Annex G PGLInitTime
4
pnniNodePglOverrideDela read-create
y
The amount of time in seconds a
node will wait for itself to be
declared the preferred PGL by
unanimous agreement among its
peers. In the absence of unanimous
agreement this will be the amount
of time that will pass before the
node considers a two thirds
majority as sufficient agreement to
declare itself peer group leader,
abandoning the attempt to get
unanimous agreement.
30
Reference: ATM Forum PNNI 1.0
Annex G OverrideDelay
Cisco SES PNNI Controller Software Configuration Guide
Release 1, Part Number 78-6123-05 Rev. A0, March 2001
C-17
AppendixC
SNMP Management Information Base
MIBs Supported by the PNNI Controller
TableC-4
pnniNodePglTable (continued)
No.
Object Type
Access
Description
5
pnniNodePglReelectTime
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.
6
pnniNodePglState
read-only
Default
15
Reference: ATM Forum PNNI 1.0
Annex G ReElectionInterval
Reference: 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.
Reference: ATM Forum PNNI 1.0
Section 5.10.1.1.2
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).
Reference: ATM Forum PNNI 1.0
Section 5.10.1.1.6
8
pnniNodePeerGroupLeade read-only
r
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
pnniNodeActiveParentNo
deId
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
C-18
Release 1, Part Number 78-6123-05 Rev. A0, March 2001
AppendixC
SNMP Management Information Base
MIBs Supported by the PNNI Controller
pnniNodeTimerTable
A table of initial PNNI timer values and significant change thresholds.
TableC-5
pnniNodeTimerTable
No.
Object Type
1
pnniNodePtseHolddown
Acces
s
read-c
reate
Description
Default
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-c
reate
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-c
reate
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
pnniNodeHelloInactiveFact
or
read-c
reate
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-c
reate
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
pnniNodePtseRefreshInterv
al
read-c
reate
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
Release 1, Part Number 78-6123-05 Rev. A0, March 2001
C-19
AppendixC
SNMP Management Information Base
MIBs Supported by the PNNI Controller
TableC-5
pnniNodeTimerTable (continued)
Acces
s
No.
Object Type
7
pnniNodePtseLifetimeFacto read-c
r
reate
Description
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-c
reate
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
pnniNodePeerDelaydAckInt read-c
erval
reate
The minimum amount of time between
transmissions of delayed PTSE
acknowledgement packets.
10
10
pnniNodeAvcrPm
The proportional multiplier used in the
algorithms that determine significant
change for AvCR parameters,
expressed as a percentage.
50
read-c
reate
Reference: ATM Forum PNNI 1.0 Section
5.8.5.2.5.4 Annex G AvCR_PM.
11
pnniNodeAvcrMt
read-c
reate
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-c
reate
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-c
reate
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
C-20
Release 1, Part Number 78-6123-05 Rev. A0, March 2001
AppendixC
SNMP Management Information Base
MIBs Supported by the PNNI Controller
pnniNodeSvccTable
The pnniNodeSvccTable is a table of variables related to SVCC-based routing control channels.
TableC-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
ime
read-create The amount of time this node will
wait for an SVCC, which it has
initiated establishment of as the
calling party, to become fully
established before giving up and
tearing it down.
35
Reference: ATM Forum PNNI 1.0
Annex G SVCCallingIntegrityTime
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.
50
Reference: ATM Forum PNNI 1.0
Annex G SVCCalledIntegrityTime
5
pnniNodeSvccTrafficDescriptio
rIndex
read-create A index into the
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
Cisco SES PNNI Controller Software Configuration Guide
Release 1, Part Number 78-6123-05 Rev. A0, March 2001
C-21
AppendixC
SNMP Management Information Base
MIBs Supported by the PNNI Controller
pnniScopeMappingTable
The pnniScopeTable 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.
TableC-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
pnniScopeLocalNetworkPlus
One
read-create
The highest level of PNNI
hierarchy (namely,
smallest PNNI routing
level) that lies within the
organizational scope
value
localNetwtorkPlusOne(1).
96
3
pnniScopeLocalNetworkPlus
Two
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
pnniScopeInteraSite
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
Cisco SES PNNI Controller Software Configuration Guide
C-22
Release 1, Part Number 78-6123-05 Rev. A0, March 2001
AppendixC
SNMP Management Information Base
MIBs Supported by the PNNI Controller
TableC-7
pnniScopeMappingTable (continued)
No.
Object Type
Access
Description
Default
7
pnniScopeOrganizationMinus read-create
One
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
pnniScropeOrganizationPlusO read-create
ne
The highest level of PNNI
hierarchy (namely, the
PNNI routing level) that
lies within the
organizational scope
value
organizationPlusOne(9).
64
10
pnniScopeCommunityMinusO read-create
ne
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
pnniScopeCommunityPlusOn
e
read-create
The highest level of PNNI
hierarchy (namely, the
smallest PNNI routing
level) that lies within the
organizational scope
communityPlusOne(1).
value
48
Cisco SES PNNI Controller Software Configuration Guide
Release 1, Part Number 78-6123-05 Rev. A0, March 2001
C-23
AppendixC
SNMP Management Information Base
MIBs Supported by the PNNI Controller
TableC-7
pnniScopeMappingTable (continued)
No.
Object Type
Access
Description
Default
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.
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.
TableC-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.
Default
Cisco SES PNNI Controller Software Configuration Guide
C-24
Release 1, Part Number 78-6123-05 Rev. A0, March 2001
AppendixC
SNMP Management Information Base
MIBs Supported by the PNNI Controller
TableC-8
pnniLinkTable (continued)
No.
Object Type
Access
Description
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
pnniLinkHelloStat
e
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.2
5
pnniLinkRemoteN
odeId
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 uplin,’ 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
pnniLinkRemotePo read-only
rtId
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.
Cisco SES PNNI Controller Software Configuration Guide
Release 1, Part Number 78-6123-05 Rev. A0, March 2001
C-25
AppendixC
SNMP Management Information Base
MIBs Supported by the PNNI Controller
TableC-8
pnniLinkTable (continued)
No.
Object Type
7
pnniLinkDerivedA read-only
ggrToken
Access
Description
Default
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.
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
pnniLinkUpnodeAt read-only
mAddress
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.
10
pnniLinkCommon
PeerGroupId
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.
For all other cases, the value of this
object is zero.
Cisco SES PNNI Controller Software Configuration Guide
C-26
Release 1, Part Number 78-6123-05 Rev. A0, March 2001
AppendixC
SNMP Management Information Base
MIBs Supported by the PNNI Controller
TableC-8
pnniLinkTable (continued)
No.
Object Type
Access
Description
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
pnniLinkRcvHello
s
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
pnniLinkXmtHello
s
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.
Default
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 supportedas a rowStatus value for the
pnniSummaryAddressRowStatus attribute.
Reference: ATM Forum PNNI 1.0 Section 5.9.2
TableC-9
pnniSummaryAddressTable
No.
Object Type
Access
Description
1
pnniSummaryAddressType
not-accessi
ble
The type (e.g. internal or exterior)
of summary being described.
2
pnniSummaryAddressAddress
not-accessi
ble
The ATM end system address
prefix for the summary.
3
pnniSummaryAddressPrefixLe not-accessi
ngth
ble
Default
The prefix length for the summary.
Cisco SES PNNI Controller Software Configuration Guide
Release 1, Part Number 78-6123-05 Rev. A0, March 2001
C-27
AppendixC
SNMP Management Information Base
MIBs Supported by the PNNI Controller
TableC-9
pnniSummaryAddressTable (continued)
No.
Object Type
Access
Description
Default
4
pnniSummaryAddressSuppres
s
read-create
Determines what is done with
false
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
pnniSummaryAddressRowStat read-create
us
To create, delete, activate, and
deactivate a summary
Cisco WAN SVC MIB Objects
•
ciscoWANSvcInfo
•
ciscoWANSpvcPort
ciscoWANSvcInfo
TableC-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
read-onl
y
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.
Administrative status of the standby controller.
This object is only used in the trap varbind.
Cisco SES PNNI Controller Software Configuration Guide
C-28
Release 1, Part Number 78-6123-05 Rev. A0, March 2001
AppendixC
SNMP Management Information Base
MIBs Supported by the PNNI Controller
TableC-10 SVC Information Group (continued)
No.
Object Type
Access
Description
8
cwspPnniControllerStatus
read-onl
y
Administrative status of the PNNI controller.
9
cwspPnniControllerPhySlot
read-onl
y
the PNNI controller physical location.
Default
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 use 3destroy 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.
TableC-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
,1,
,
•
inService(1) indicates that the interface is currently
operational.
•
outService(2) indicates that the interface is not
operational.
•
,
1ZQ
\kia
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
Cisco SES PNNI Controller Software Configuration Guide
Release 1, Part Number 78-6123-05 Rev. A0, March 2001
C-29
AppendixC
SNMP Management Information Base
MIBs Supported by the PNNI Controller
TableC-11 Interface Configuration Table Entries (continued)
No
Object Type
Access
Description
Default
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 true
turned on or off. If auto-configuration is enabled, the
interface comes up using the ILMI auto-configuration.
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
M aximum number of active VCI bits on this ATM
interface.
0
0
Cisco SES PNNI Controller Software Configuration Guide
C-30
Release 1, Part Number 78-6123-05 Rev. A0, March 2001
AppendixC
SNMP Management Information Base
MIBs Supported by the PNNI Controller
TableC-11 Interface Configuration Table Entries (continued)
No
Object Type
Access
Description
Default
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 true
turned on or off. If auto-configuration is enabled, the
interface comes up using the ILMI auto-configuration.
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, Part Number 78-6123-05 Rev. A0, March 2001
C-31
AppendixC
SNMP Management Information Base
MIBs Supported by the PNNI Controller
TableC-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
C-32
Release 1, Part Number 78-6123-05 Rev. A0, March 2001
AppendixC
SNMP Management Information Base
MIBs Supported by the PNNI Controller
TableC-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)
allowed on the interface, in the range 0 to 65535.
4095
22
cwspMinSvccVpi
read-create
Minimum SVCC VPI configured on the interface, in the
range 0 to 4095.
0
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
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
cwspConfigTableRowStatu
s
read-create
Used to either create or delete the interface.
30
cwspAddrPlanSupported
read-create
The ATM address plan supported on an interface:
aesa(2)
both(1), aesa(2) and e164(3). 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
32
cwspIlmiAttachmentPoint
read-create
Indicates whether detection of loss of attachment
true
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.
1
false
Cisco SES PNNI Controller Software Configuration Guide
Release 1, Part Number 78-6123-05 Rev. A0, March 2001
C-33
AppendixC
SNMP Management Information Base
MIBs Supported by the PNNI Controller
TableC-11 Interface Configuration Table Entries (continued)
No
Object Type
Access
Description
Default
33
cwspIlmiLocalAttrStd
read-create
Indicates whether on modification of local attributes,
procedures as recommended by ILMI 4.0 specification
are followed or cisco proprietery 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.
TableC-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.
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.
Cisco SES PNNI Controller Software Configuration Guide
C-34
Release 1, Part Number 78-6123-05 Rev. A0, March 2001
AppendixC
SNMP Management Information Base
MIBs Supported by the PNNI Controller
TableC-12 Port Call Statistics Table Entries
No
Object Type
Access
Description
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.
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.
Default
Cisco SES PNNI Controller Software Configuration Guide
Release 1, Part Number 78-6123-05 Rev. A0, March 2001
C-35
AppendixC
SNMP Management Information Base
MIBs Supported by the PNNI Controller
TableC-12 Port Call Statistics Table Entries
No
Object Type
Access
Description
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.
TableC-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
cwspUtilFactorR tVbr
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
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.
100
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
C-36
Release 1, Part Number 78-6123-05 Rev. A0, March 2001
AppendixC
SNMP Management Information Base
MIBs Supported by the PNNI Controller
TableC-13 Port CAC Configuration Table Entries (continued)
No.
Object Type
Access
Description
Default
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
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%.
12
cwspMinBwRtVbr
read-write
Minimum percentage bandwidth for 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%.
Cisco SES PNNI Controller Software Configuration Guide
Release 1, Part Number 78-6123-05 Rev. A0, March 2001
C-37
AppendixC
SNMP Management Information Base
MIBs Supported by the PNNI Controller
TableC-13 Port CAC Configuration Table Entries (continued)
No.
Object Type
Access
Description
Default
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%.
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%.
Cisco SES PNNI Controller Software Configuration Guide
C-38
Release 1, Part Number 78-6123-05 Rev. A0, March 2001
AppendixC
SNMP Management Information Base
MIBs Supported by the PNNI Controller
TableC-13 Port CAC Configuration Table Entries (continued)
No.
Object Type
Access
Description
Default
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 varlues 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 varlues 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 varlues 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%.
24
cwspMinVc Abr
read-write
Minimum number of VCs for ABR service percentage,
in the range 0 to 1000000.
0
The value of this varlues 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, Part Number 78-6123-05 Rev. A0, March 2001
C-39
AppendixC
SNMP Management Information Base
MIBs Supported by the PNNI Controller
TableC-13 Port CAC Configuration Table Entries (continued)
No.
Object Type
Access
Description
Default
25
cwspMinVcUbr
read-write
Minimum number of VCs for UBR service percentage, 0
in the range 0 to 1000000.
The value of this varlues 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, in the range 0 to 1000000.
0
28
cwspMaxVcBwNrtVbr
read-write
Maximum bandwidth allowed for non-real-time VBR
on a VC, in the range 0 to 1000000.
0
29
cwspMaxVcBwAbr
read-write
Maximum bandwidth allowed for ABR service on a
VC, int he range 0 to 1000000.
0
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
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.
Cisco SES PNNI Controller Software Configuration Guide
C-40
Release 1, Part Number 78-6123-05 Rev. A0, March 2001
AppendixC
SNMP Management Information Base
MIBs Supported by the PNNI Controller
TableC-14 Port Signaling Statistics Table Entries
No.
Object Type
Access
Description
Default
1
cwspSigCounterReset
read-write
Determines resetting of counters:
noop(1)
•
noop(1) = None of the following
•
re set(2) = Resetting
2
cwspCallProcRcv
read-only
Number of
interface
CALL P ROCEEDING
messages received on this
3
cwspConnectRcv
read-only
Number of
CONNECT
4
cwspConnectAckRcv
read-only
Number of
interface
CONNECT ACK
5
cwspSetupRcv
read-only
Number of
SETUP
6
cwspReleaseRcv
read-only
Number of
RELEASE
7
cwspReleaseComplRcv
read-only
Number of
interface.
RELEASE C OMPLETE
8
cwspRestartRcv
read-only
Number of
RESTART
9
cwspRestartAckRcv
read-only
Number of
interface.
RESTART ACK
10
cwspStatusRcv
read-only
Number of
STATUS
11
cwspStatusEngRcv
read-only
Number of
interface.
STATUS ENQUIRY
12
cwspNotifyRcv
read-only
Number of
NOTIF Y
13
cwspAlertRcv
read-only
Number of
ALER T
14
cwspProgressRcv
read-only
Number of
PR OGR ESS
15
cwspAddPtyRcv
read-only
Number of ADD PAR TY messages received on this interface.
16
cwspAddPtyAckRcv
read-only
Number of
interface.
ADD P ARTY AC K
17
cwspAddPtyRejRcv
read-only
Number of
interface.
ADD P ARTY
18
cwspDropPtyRcv
read-only
Number of
interface.
DROP PAR TY
20
cwspIncorrectMsgRcv
read-only
Number of incorrect messages received on this interface.
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 P ROCEEDING messages transmitted from
this interface.
25
cwspConnectXmt
read-only
Number of
interface.
26
cwspConnectAckXmt
read-only
Number of CONNECT ACK messages transmitted from this
interface.
messages received on this interface
messages received on this
messages received on this interface
messages received on this interface
messages received on this
messages received on this interface.
messages received on this
messages received on this interface.
messages received on this
messages received on this interface.
messages received on this interface.
CONNECT
messages received on this interface.
messages received on this
reject messages received on this
messages received on this
messages transmitted from this
Cisco SES PNNI Controller Software Configuration Guide
Release 1, Part Number 78-6123-05 Rev. A0, March 2001
C-41
AppendixC
SNMP Management Information Base
MIBs Supported by the PNNI Controller
TableC-14 Port Signaling Statistics Table Entries (continued)
No.
Object Type
Access
Description
Default
27
cwspSetupXmt
read-only
Number of SETUP messages transmitted from this interface.
28
cwspReleaseXmt
read-only
Number of RELEAS E messages transmitted from this
interface.
29
cwspReleaseComplXmt
read-only
Number of R ELEASE COM PLETE messages transmitted from
this interface.
30
cwspRestartXmt
read-only
Number of RESTART messages transmitted from this
interface.
31
cwspRestartAckXmt
read-only
Number of RESTART
interface.
32
cwspStatusXmt
read-only
Number of STATUS messages transmitted from this
interface.
33
cwspStatusEnqX mt
read-only
Number of STATUS
this interface.
34
cwspNotifyXmt
read-only
Number of NOTIFYmessages transmitted from this
interface.
35
cwspAlertXmt
read-only
Number of ALERT m essages transmitted from this
interface.
36
cwspProgressXmt
read-only
Number of PROGR ES S messages transmitted from this
interface.
37
cwspAddPtyXmt
read-only
Number of ADD PAR TY messages transmitted from this
interface.
38
cwspAddPtyAckXmt
read-only
Number of ADD P AR TY AC K messages transmitted from this
interface.
39
cwspAddPtyRejXmt
read-only
Number of ADD
this interface.
40
cwspDropPtyXmt
read-only
Number of DROP
interface.
42
cwspSscopStatus
read-only
SSCOP link status --up(1) or down(2) -- on an NNI
interface, object is meaningful along with
ciscoWANSscopLinkChange trap.
ACK
messages transmitted from this
ENQUIRY
messages transmitted from
PARTY REJECT
PARTY
messages transmitted from
messages transmitted from this
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 createAndGp/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.
Cisco SES PNNI Controller Software Configuration Guide
C-42
Release 1, Part Number 78-6123-05 Rev. A0, March 2001
AppendixC
SNMP Management Information Base
MIBs Supported by the PNNI Controller
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.
TableC-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:
•
NSAP E.164
•
NSAP DCC
•
NSAP ICD
6
cwspAddrScope
read-create
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.
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)
This object is meaningful only if the routing mechanism
(cwspAddrProto) is static.
8
cwspAddressRowStatus
read-create
Create or delete a reachable address
Cisco SES PNNI Controller Software Configuration Guide
Release 1, Part Number 78-6123-05 Rev. A0, March 2001
C-43
AppendixC
SNMP Management Information Base
MIBs Supported by the PNNI Controller
cwspLoadTable
The port loading table specifies the loa /cwsd information for each interface on the PNNI Controller.
TableC-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.
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
cwspLoadCdvC br
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.
Cisco SES PNNI Controller Software Configuration Guide
C-44
Release 1, Part Number 78-6123-05 Rev. A0, March 2001
AppendixC
SNMP Management Information Base
MIBs Supported by the PNNI Controller
TableC-16 Port Loading Table Entries (continued)
No.
Object Type
Access
Description
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
cwspLoadMinGurCrNrtV
br
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.
cwspConnTrace
Collection of objects that provide trace information about SVC/PNNI Connections.
•
cwspConnTraceAvail
•
cwspConnTraceCntlTable
•
cwspConnTraceTable
cwspConnTraceAvail
TableC-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.
Cisco SES PNNI Controller Software Configuration Guide
Release 1, Part Number 78-6123-05 Rev. A0, March 2001
C-45
AppendixC
SNMP Management Information Base
MIBs Supported by the PNNI Controller
cwspConnTraceNextIndex
TableC-18 Port Connection Trace If Index Entry
No.
Object Type
Access
Description
2
cwspConnTrace NextIndex read-only
NMS queries this object to obtain the index value to be used row
creation.
cwspConnTraceCntlTable
TableC-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
TableC-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.
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.
Cisco SES PNNI Controller Software Configuration Guide
C-46
Release 1, Part Number 78-6123-05 Rev. A0, March 2001
AppendixC
SNMP Management Information Base
MIBs Supported by the PNNI Controller
TableC-20 Port Connection Trace Control Table Entries (continued)
No.
Object Type
Access
Description
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.
Port Connection Data Table
This Table contains the objects which show the traversed node information in the existing SVC call.
TableC-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.
Cisco SES PNNI Controller Software Configuration Guide
Release 1, Part Number 78-6123-05 Rev. A0, March 2001
C-47
AppendixC
SNMP Management Information Base
MIBs Supported by the PNNI Controller
TableC-21 Port Connection Data Table
No.
Object Type
Access
Description
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
•
5 th byte = subslot
•
6th & 7th bytes = port
•
8 th byte= subport
cwspOperationTable
The interface operation table contains the runtime negotiated values between platform, PNNI controller,
and peer on an interface.
TableC-22 Interface Operation Table Entries
No
Object Type
Access
Description
‘
cwspOperIlmiEnable
read-only
Opera tional 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
C-48
Release 1, Part Number 78-6123-05 Rev. A0, March 2001
AppendixC
SNMP Management Information Base
MIBs Supported by the PNNI Controller
TableC-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 i s
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 value s
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
Release 1, Part Number 78-6123-05 Rev. A0, March 2001
C-49
AppendixC
SNMP Management Information Base
MIBs Supported by the PNNI Controller
TableC-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
C-50
Release 1, Part Number 78-6123-05 Rev. A0, March 2001
AppendixC
SNMP Management Information Base
MIBs Supported by the PNNI Controller
cwAtmChanCfgTable
Each entry in the cwAtmChanCfgEntry table corresponds to an endpoint on the PNNI Controller.
TableC-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
Release 1, Part Number 78-6123-05 Rev. A0, March 2001
C-51
AppendixC
SNMP Management Information Base
MIBs Supported by the PNNI Controller
TableC-23 cwAtmChanCfgTable
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
cwaChanLocalINSAPAdd read-only
r
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
cwaChanRemoteNSAPAd read-create
dr
Identifies the NSAP of the peer endpoint. The
cwaChanRemoteVpi, cwaChanRemoteVpi, and the
cwaChanRemoteNSAPAddr identify the peer endpoint in the
networking domain.
15
cwaChanControllerId
This object serves to associate an endpoint with a specific
controller. Usually resouce 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
beimplemented, in which case this object serves to tie
aspecific vpi-vci to a controller. The range is 1..255. The
default is 2.
read-create
1
Cisco SES PNNI Controller Software Configuration Guide
C-52
Release 1, Part Number 78-6123-05 Rev. A0, March 2001
AppendixC
SNMP Management Information Base
MIBs Supported by the PNNI Controller
TableC-23 cwAtmChanCfgTable
No.
Object Type
Access
16
cwaChanRoutingMastersh read-create
ip
Description
Default
If set to true(1), identifies this endpoint as the ‘master’
endpoint of the connection.
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).
18
cwaChanReroute
read-create
Used by the administrator to trigger the rerouting of the
connection
•
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.
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.
100
false (2)
false (2)
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 "micrseconds".
Cisco SES PNNI Controller Software Configuration Guide
Release 1, Part Number 78-6123-05 Rev. A0, March 2001
C-53
AppendixC
SNMP Management Information Base
MIBs Supported by the PNNI Controller
TableC-23 cwAtmChanCfgTable
No.
Object Type
Access
Description
Default
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.
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 vlaue 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
Cisco SES PNNI Controller Software Configuration Guide
C-54
Release 1, Part Number 78-6123-05 Rev. A0, March 2001
AppendixC
SNMP Management Information Base
MIBs Supported by the PNNI Controller
TableC-23 cwAtmChanCfgTable
No.
Object Type
Access
Description
Default
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
cwaChanRemotePercentU
til
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
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.
Larger values lead to faster rate increase.
Reference: ATM Forum Traffic Management Specification Version 4.0
Section 5.10.2
Cisco SES PNNI Controller Software Configuration Guide
Release 1, Part Number 78-6123-05 Rev. A0, March 2001
C-55
AppendixC
SNMP Management Information Base
MIBs Supported by the PNNI Controller
TableC-23 cwAtmChanCfgTable
No.
Object Type
Access
Description
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)
Default
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
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
Cisco SES PNNI Controller Software Configuration Guide
C-56
Release 1, Part Number 78-6123-05 Rev. A0, March 2001
AppendixC
SNMP Management Information Base
MIBs Supported by the PNNI Controller
TableC-23 cwAtmChanCfgTable
No.
Object Type
Access
Description
Default
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
47
cwaChanAbrVSVDEnable read-create
Configuration of an endpoint for explicit rate stamping.
none
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.
When set to true(1), this feature is enabled.
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.’
Cisco SES PNNI Controller Software Configuration Guide
Release 1, Part Number 78-6123-05 Rev. A0, March 2001
C-57
AppendixC
SNMP Management Information Base
MIBs Supported by the PNNI Controller
TableC-23 cwAtmChanCfgTable
No.
Object Type
Access
Description
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/disabing 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
e2eAisC
This object is used for achieving OAM inter-operability
apable(1
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).
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
CwAtmChanStateTable
Each entry in the cwAtmChanStateTable corresponds to a connection endpoint on the PNNI Controller.
TableC-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
cwaChanIngressR cvState
read-only
The state of the receive portion of the endpoint in the ingress direction
Cisco SES PNNI Controller Software Configuration Guide
C-58
Release 1, Part Number 78-6123-05 Rev. A0, March 2001
AppendixC
SNMP Management Information Base
MIBs Supported by the PNNI Controller
CwAtmChanTestTable
Each entry in the cwAtmChanTextTable corresponds to a connection endpoint on the PNNI Controller.
TableC-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.
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, Part Number 78-6123-05 Rev. A0, March 2001
C-59
AppendixC
SNMP Management Information Base
MIBs Supported by the PNNI Controller
Cisco SES PNNI Controller Software Configuration Guide
C-60
Release 1, Part Number 78-6123-05 Rev. A0, March 2001
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, Part Number 78-6123-05 Rev. A0, March 2001
GL-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
GL-2
Release 1, Part Number 78-6123-05 Rev. A0, March 2001
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, Part Number 78-6123-05 Rev. A0, March 2001
GL-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
GL-4
Release 1, Part Number 78-6123-05 Rev. A0, March 2001
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 isa 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, Part Number 78-6123-05 Rev. A0, March 2001
GL-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
GL-6
Release 1, Part Number 78-6123-05 Rev. A0, March 2001
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 216 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 2 16). 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.
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.
Cisco SES PNNI Controller Software Configuration Guide
Release 1, Part Number 78-6123-05 Rev. A0, March 2001
GL-7
Glossary
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
GL-8
Release 1, Part Number 78-6123-05 Rev. A0, March 2001
I N D E X
A
B
access levels, changing
3-13
ACO
BCC
See alarm cut-off
3-10
alarm cut-off
C
6-3
6-3
switch
3-8
bye command
administrator access, configuration
LED
cards
6-6
6-4
displaying redundancy status
displaying environment alarms
displaying node alarms
6-5
6-4
displaying slot alarms
managing redundancy
displaying switching alarms
3-19
types and locations
6-6
3-3
card states
LEDs, AXSM
6-4
cc command
3-9
LEDs,PXM45
6-1
CISCO_GP
3-11
switches, AXSM
6-4
Cisco user group
switches,PXM45
6-1
Cisco WAN Manager
ANYUSER user group
3-12
1-5
6-3
Audience
Also see StrataView Plus
management
xvii
cnfname
3-15
4-15
3-14
cnfname command
3-19
6-4
switches
xvii
3-23
cnfdate command
AXSM card
LEDs
3-11
clock sources
audible alarm indicator
card types
3-20
3-20
switching PXM cards
6-6
3-19
3-19
switching AXSM cards
6-4
displaying reports
for manual
6-4
displaying card alarms
displaying card alarms
arbiter
1-5
Minimum requirements
3-11
adduser command
alarms
3-19
back cards
cnfpasswd command
cnfsnmp command
6-4
cnftime command
cnftmzn
3-12
3-24
3-15
4-15
cnftmzn command
cnftmzngmt
3-15
4-15
Cisco SES PNNI Controller Software Configuration Guide
Release 1, Part Number 78-6123-05 Rev. A0, March 2001
IN-1
Index
3-15
cnftmzngmt command
cnfuser command
3-13
dspcd command
6-2
CNTRLR port LED
3-10
3-9
command line interface
3-7
3-4
dsplog command
6-6
6-6
6-4
3-19
dspred command
3-6
3-24
dspsnmp command
3-10
administrator access
ending a session
3-12
dspusers command
3-15
3-26
E
3-25
with directly-attached terminal
3-3
ending a session
controller
3-24
configuring for PNNI
3-8
6-3
ENET LED
critical alarm LED
6-6
dspswalms command
3-8
hardware worksheet
controller port LED
6-6
dspslotalms command
configuration
CR LED
6-5
dspndalms command
3-3
session startup from LAN
saving
dspipif command
dsplogs command
dial-up session startup
restoring
3-14
dspenvalms command
getting help
prompt
3-16
dspdate command
command entry
guidelines
6-4
dspcdalms command
environmental alarms, displaying
6-2
Ethernet
6-3
4-3
Ethernet LAN, CLI session startup
6-3
Ethernet LAN port
1-5
crosspoint switch matrix
6-5
3-6
1-5
external clock sources
managing
3-23
D
DC-A LED
6-3
DC-B LED
6-3
deleting users
F
3-14
date, setting and viewing
firmware
determining versions from filenames
3-14
deluser command
directory
3-14
3-7
dialup, CLI session startup
directly-attached terminal
3-3
directly-attached terminal session startup
3-21
managing versions
3-20
setting the version
3-23
verifying card versions
3-3
front cards
3-21
3-21
3-19
directories
firmware
log files
3-21
G
6-6
saved configurations
displaying Xbar alarms
3-25
GROUP1 user group
3-11
6-6
Cisco SES PNNI Controller Software Configuration Guide
IN-2
Release 1, Part Number 78-6123-05 Rev. A0, March 2001
Index
GROUP2 user group
3-11
GROUP3 user group
3-11
GROUP4 user group
3-12
GROUP5 user group
3-12
management
configuring network management through dial-up
port 3-5
configuring network management through LAN
port 3-4
SNMP configuration
H
6-3
MJ LED
help
6-3
minor alarm LED
hardware configuration worksheet
3-15
3-24
6-3
MN LED
3-10
3-10
help command
N
6-3
HIST LED
6-3
history LED
name, setting and viewing
1-12
Hitless Operations
3-14
network clock sources
management
I
3-23
1-4
Network congestion
network management
IISP
1-4, 1-11
configuring management through dial-up port
ILMI
configuring management through LAN port
How used
1-11
SNMP configuration
Interim Inter-switch Protocol
3-5
3-4
3-24
node
See IISP
6-4
displaying alarms
ipifconfig command
LAN port
3-4
P
3-5
maintenance port
passwords
L
changing
3-12
length
LAN, CLI session startup
LAN port
ll command
3-6
4-3
1-10
PNNI controller
3-22
configuration
log files
directory
PNNI
3-12
prompt, switch
6-6
3-24
3-3
PXM45 card
displaying information
low-speed data ports
6-6
1-5
LEDs
6-1
switches
6-1
PXM45 card types
3-19
M
major alarm LED
6-3
Cisco SES PNNI Controller Software Configuration Guide
Release 1, Part Number 78-6123-05 Rev. A0, March 2001
IN-3
Index
3-11
superuser user group
Q
3-20
switching, redundant AXSM cards
quickstart configuration
switching, redundant PXM cards
3-1
general switch features
switching alarms, displaying
6-6
3-3
switch prompt
switchredcc command
R
3-20
3-20
6-3
system status LED
redundant cards
3-19
displaying status
managing
T
3-19
3-20
switching AXSM cards
Telnet
3-20
switching PXM cards
terminal
Redundant SES PNNI Controllers
1-12
requirements
1-10
Resource partitioning
3-3
starting a configuration session
3-26
restoreallcnf command
3-6
time, setting and viewing
3-3
3-14
3-26
restoring, configuration
U
S
UNI port
3-25
saveallcnf command
saving, configuration
SERVICE_GP
Address limit
3-25
users
3-11
adding
3-11
service user group
changing passwords
3-6
CLI startup from LAN
starting dial-up CLI sessions
session starting
V
3-23
version levels, firmware
3-24
slot alarms, displaying
3-12
3-7
Simple Network Management Protocol
configuration
3-13
3-14
deleting
3-3
setrev command
determining from filenames
6-6
managing
software
setting
determining versions from filenames
3-21
verifying
3-21
3-20
3-23
3-21
3-21
managing versions
3-20
setting the version
3-23
verifying card versions
Stratum 3 system clocking
SUPER_GP
3-11
changing access levels
session
directory
1-4
W
3-21
1-5
whoami command
3-12
worksheet, hardware configuration
3-15
3-11
Cisco SES PNNI Controller Software Configuration Guide
IN-4
Release 1, Part Number 78-6123-05 Rev. A0, March 2001
Index
X
Xbar alarms, displaying
6-6
Cisco SES PNNI Controller Software Configuration Guide
Release 1, Part Number 78-6123-05 Rev. A0, March 2001
IN-5
Index
Cisco SES PNNI Controller Software Configuration Guide
IN-6
Release 1, Part Number 78-6123-05 Rev. A0, March 2001