Switch Diagnostics User's Guide for CBX 3500, CBX 500, GX ...

Beta Draft Confidential

Switch Diagnostics User’s Guide for CBX 3500, CBX 500, GX 550, and B-STDX 9000

Product Code: 80262Revision 000

September 2005

ii10/7/05 Switch Diagnostics User’s Guide for CBX 3500, CBX 500, GX 550, and B-STDX 9000


Copyright© 2005 Lucent Technologies. All Rights Reserved.

This material is protected by the copyright laws of the United States and other countries. It may not be reproduced, distributed, or altered in any fashion by any entity (either internal or external to Lucent Technologies), except in accordance with applicable agreements, contracts or licensing, without the express written consent of Lucent Technologies.

For permission to reproduce or distribute, please contact: Technical Publications, Data Networking Group at 978-692-2600.

Notice. Every effort was made to ensure that the information in this document was complete and accurate at the time of printing. However, information is subject to change.

Trademarks. All trademarks and service marks specified herein are owned by their respective companies.

Limited Warranty. Lucent Technologies provides a limited warranty to this product. For more information, see the software license agreement in this document.

Ordering Information. To order copies of this document, use the online ordering instructions later in this guide.

Support Telephone Numbers. For technical support and other services, see the customer support contact information in the “About This Guide” section of this document.

Switch Diagnostics User’s Guide for CBX 3500, CBX 500, GX 550, and B-STDX 9000 10/7/05iii


LUCENT TECHNOLOGIES END-USER LICENSE AGREEMENT

LUCENT TECHNOLOGIES IS WILLING TO LICENSE THE ENCLOSED SOFTWARE AND ACCOMPANYING USER DOCUMENTATION (COLLECTIVELY, THE “PROGRAM”) TO YOU ONLY UPON THE CONDITION THAT YOU ACCEPT ALL OF THE TERMS AND CONDITIONS OF THIS LICENSE AGREEMENT. PLEASE READ THE TERMS AND CONDITIONS OF THIS LICENSE AGREEMENT CAREFULLY BEFORE OPENING THE PACKAGE(S) OR USING THE LUCENT SWITCH(ES) CONTAINING THE SOFTWARE, AND BEFORE USING THE ACCOMPANYING USER DOCUMENTATION. OPENING THE PACKAGE(S) OR USING THE LUCENT SWITCH(ES) CONTAINING THE PROGRAM WILL INDICATE YOUR ACCEPTANCE OF THE TERMS OF THIS LICENSE AGREEMENT. IF YOU ARE NOT WILLING TO BE BOUND BY THE TERMS OF THIS LICENSE AGREEMENT, LUCENT IS UNWILLING TO LICENSE THE PROGRAM TO YOU, IN WHICH EVENT YOU SHOULD RETURN THE PROGRAM WITHIN TEN (10) DAYS FROM SHIPMENT TO THE PLACE FROM WHICH IT WAS ACQUIRED, AND YOUR LICENSE FEE WILL BE REFUNDED. THIS LICENSE AGREEMENT REPRESENTS THE ENTIRE AGREEMENT CONCERNING THE PROGRAM BETWEEN YOU AND LUCENT, AND IT SUPERSEDES ANY PRIOR PROPOSAL, REPRESENTATION OR UNDERSTANDING BETWEEN THE PARTIES.

1. License Grant. Lucent hereby grants to you, and you accept, a non-exclusive, non-transferable license to use the computer software, including all patches, error corrections, updates and revisions thereto in machine-readable, object code form only (the “Software”), and the accompanying User Documentation, only as authorized in this License Agreement. The Software may be used only on a single computer owned, leased, or otherwise controlled by you; or in the event of inoperability of that computer, on a backup computer selected by you. You agree that you will not pledge, lease, rent, or share your rights under this License Agreement, and that you will not, without Lucent’s prior written consent, assign or transfer your rights hereunder. You agree that you may not modify, reverse assemble, reverse compile, or otherwise translate the Software or permit a third party to do so. You may make one copy of the Software and User Documentation for backup purposes. Any such copies of the Software or the User Documentation shall include Lucent’s copyright and other proprietary notices. Except as authorized under this paragraph, no copies of the Program or any portions thereof may be made by you or any person under your authority or control.

2. Lucent’s Rights. You agree that the Software and the User Documentation are proprietary, confidential products of Lucent or Lucent's licensor protected under US copyright law and you will use your best efforts to maintain their confidentiality. You further acknowledge and agree that all right, title and interest in and to the Program, including associated intellectual property rights, are and shall remain with Lucent or Lucent's licensor. This License Agreement does not convey to you an interest in or to the Program, but only a limited right of use revocable in accordance with the terms of this License Agreement.

iv10/7/05 Switch Diagnostics User’s Guide for CBX 3500, CBX 500, GX 550, and B-STDX 9000


3. License Fees. The license fees paid by you are paid in consideration of the license granted under this License Agreement.

4. Term. This License Agreement is effective upon your opening of the package(s) or use of the switch(es) containing Software and shall continue until terminated. You may terminate this License Agreement at any time by returning the Program and all copies or portions thereof to Lucent. Lucent may terminate this License Agreement upon the breach by you of any term hereof. Upon such termination by Lucent, you agree to return to Lucent the Program and all copies or portions thereof. Termination of this License Agreement shall not prejudice Lucent's rights to damages or any other available remedy.

5. Limited Warranty. Lucent warrants, for your benefit alone, for a period of 90 days from the date of shipment of the Program by Lucent (the “Warranty Period”) that the program diskettes in which the Software is contained are free from defects in material and workmanship. Lucent further warrants, for your benefit alone, that during the Warranty Period the Program shall operate substantially in accordance with the User Documentation. If during the Warranty Period, a defect in the Program appears, you may return the Program to the party from which the Program was acquired for either replacement or, if so elected by such party, refund of amounts paid by you under this License Agreement. You agree that the foregoing constitutes your sole and exclusive remedy for breach by Lucent of any warranties made under this Agreement. EXCEPT FOR THE WARRANTIES SET FORTH ABOVE, THE PROGRAM IS LICENSED “AS IS”, AND LUCENT DISCLAIMS ANY AND ALL OTHER WARRANTIES, WHETHER EXPRESS, IMPLIED OR STATUTORY, INCLUDING, WITHOUT LIMITATION, ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE AND ANY WARRANTIES OF NONINFRINGEMENT.

6. Limitation of Liability. Lucent’s cumulative liability to you or any other party for any loss or damages resulting from any claims, demands, or actions arising out of or relating to this License Agreement shall not exceed the greater of: (i) ten thousand US dollars ($10,000) or (ii) the total license fee paid to Lucent for the use of the Program. In no event shall Lucent be liable for any indirect, incidental, consequential, special, punitive or exemplary damages or lost profits, even if Lucent has been advised of the possibility of such damages.

Switch Diagnostics User’s Guide for CBX 3500, CBX 500, GX 550, and B-STDX 9000 10/7/05v


7. Proprietary Rights Indemnification. Lucent shall at its expense defend you against and, subject to the limitations set forth elsewhere herein, pay all costs and damages made in settlement or awarded against you resulting from a claim that the Program as supplied by Lucent infringes a United States copyright or a United States patent, or misappropriates a United States trade secret, provided that you: (a) provide prompt written notice of any such claim, (b) allow Lucent to direct the defense and settlement of the claim, and (c) provide Lucent with the authority, information, and assistance that Lucent deems reasonably necessary for the defense and settlement of the claim. You shall not consent to any judgment or decree or do any other act in compromise of any such claim without first obtaining Lucent’s written consent. In any action based on such a claim, Lucent may, at its sole option, either: (1) obtain for you the right to continue using the Program, (2) replace or modify the Program to avoid the claim, or (3) if neither (1) nor (2) can reasonably be effected by Lucent, terminate the license granted hereunder and give you a prorata refund of the license fee paid for such Program, calculated on the basis of straight-line depreciation over a five-year useful life. Notwithstanding the preceding sentence, Lucent will have no liability for any infringement or misappropriation claim of any kind if such claim is based on: (i) the use of other than the current unaltered release of the Program and Lucent has provided or offers to provide such release to you for its then current license fee, or (ii) use or combination of the Program with programs or data not supplied or approved by Lucent to the extent such use or combination caused the claim.

8. Export Control. You agree not to export or disclose to anyone except a United States national any portion of the Program supplied by Lucent without first obtaining the required permits or licenses to do so from the US Office of Export Administration, and any other appropriate government agency.

9. Governing Law. This License Agreement shall be construed and governed in accordance with the laws and under the jurisdiction of the Commonwealth of Massachusetts, USA. Any dispute arising out of this Agreement shall be referred to an arbitration proceeding in Boston, Massachusetts, USA by the American Arbitration Association.

10. Miscellaneous. If any action is brought by either party to this License Agreement against the other party regarding the subject matter hereof, the prevailing party shall be entitled to recover, in addition to any other relief granted, reasonable attorneys’ fees and expenses of arbitration. Should any term of this License Agreement be declared void or unenforceable by any court of competent jurisdiction, such declaration shall have no effect on the remaining terms hereof. The failure of either party to enforce any rights granted hereunder or to take action against the other party in the event of any breach hereunder shall not be deemed a waiver by that party as to subsequent enforcement of rights or subsequent actions in the event of future breaches.

x

vi10/7/05 Switch Diagnostics User’s Guide for CBX 3500, CBX 500, GX 550, and B-STDX 9000


Switch Diagnostics User’s Guide for CBX 3500, CBX 500, GX 550, and B-STDX 9000 rvii


Contents

About This GuideWhat You Need to Know...........................................................................................xliiReading Path .............................................................................................................xliiiHow to Use This Guide.............................................................................................. xlvWhat’s New in This Guide .......................................................................................xlviConventions ..............................................................................................................xlixRelated Documents ....................................................................................................... li

Lucent ..................................................................................................................... liThird Party............................................................................................................. lii

Ordering Printed Manuals Online...............................................................................liiiCustomer Comments...................................................................................................liiiTechnical Support .......................................................................................................liii

Chapter 1 OverviewViewing Object Attributes...................................................................................1-2Viewing Object Operational Information............................................................1-3Viewing Summary Statistics ...............................................................................1-3

Generating Reports ....................................................................................................1-5

Chapter 2 Viewing Network, Switch, Module, and Physical Port DetailsViewing Networks .....................................................................................................2-1

Displaying a Network View................................................................................2-1View MPLS Traffic Profiles ...............................................................................2-3View MPLS Affinities.........................................................................................2-4View Tunnel Hoplists..........................................................................................2-5

Viewing A Switch......................................................................................................... 6Displaying a Switch.............................................................................................2-6

Displaying a Switch Tab in the Navigation Panel ........................................2-6Displaying a Switch With a Network Map...................................................2-7

Viewing Switch Attributes ..................................................................................2-9Viewing Switch Operational Information ...........................................................2-9

Before You Begin .........................................................................................2-9Viewing Switch Operational Information...................................................2-10

Viewing PNNI Nodes ..............................................................................................2-14

viii10/7/05 Switch Diagnostics User’s Guide for CBX 3500, CBX 500, GX 550, and B-STDX 9000

Contents


Displaying PNNI Nodes for a Switch ...............................................................2-14Viewing PNNI Node Attributes ........................................................................2-14Viewing PNNI Node Operational Information .................................................2-15

Before You Begin .......................................................................................2-15Viewing PNNI Node Signaling Statistics .........................................................2-16

Viewing Network Traffic Descriptors .....................................................................2-19Redundant Groups ...................................................................................................2-20

Viewing Redundant Groups ..............................................................................2-20Viewing Operational Status...............................................................................2-22

Viewing LDP Entities ..............................................................................................2-23View LDP Entities ......................................................................................2-23View LDP Entity Operational Information ................................................2-23

Viewing Tunnels ......................................................................................................2-27View MPLS (PSN) Tunnels ..............................................................................2-27

View MPLS (PSN) Tunnel Operational Information .................................2-29View MPLS Tunnel Statistics.....................................................................2-32

View Layer 2 Tunnels .......................................................................................2-35View Layer 2 Tunnel Operational Information ..........................................2-35Layer 2 Tunnel Statistics ............................................................................2-36

Front and Rear View Status Colors .........................................................................2-38Displaying a Switch in the Front/Rear Views ...................................................2-39IOM and Processor Module Colors...................................................................2-48Physical Port Colors ..........................................................................................2-48External Power Status Indicator Colors (GX 550)............................................2-49Alarm Status Indicator Colors ...........................................................................2-49Switch Status Indicator Colors ..........................................................................2-49Module Status Indicator Colors.........................................................................2-50Stby/Redundancy Status Indicator Colors.........................................................2-50Fan/Power Supply Status Indicator Colors .......................................................2-50MID Status Colors (CBX 3500) ........................................................................2-51

SNMP Failures.........................................................................................................2-52Displaying Error Log and Debugging Information .................................................2-53Viewing Modules.....................................................................................................2-54

Displaying Modules and Subcards ....................................................................2-54Displaying the Modules for a Switch .........................................................2-54Displaying GX 550 Subcards .....................................................................2-55

Viewing Processor Modules..............................................................................2-55Viewing CP Module Attributes ..................................................................2-55Viewing SP Module Attributes...................................................................2-56Viewing NP Module Attributes ..................................................................2-57Viewing CP, SP, or NP Operational Information .......................................2-58

Viewing System-Timing Options......................................................................2-62Viewing IOMs, BIOs, and Subcards .................................................................2-63

Viewing IOM and BIO Attributes ..............................................................2-63Viewing GX 550 Subcard Attributes..........................................................2-64Viewing IOM, BIO, and Subcard Operational Information .......................2-65Viewing Statistics for the 32-port Channelized T1/E1 Module on CBX 500 and CBX 3500 ............................................................................2-72

Contents

Switch Diagnostics User’s Guide for CBX 3500, CBX 500, GX 550, and B-STDX 9000 ix


Viewing Physical Ports ............................................................................................2-74Displaying Physical Ports and Subports............................................................2-74

Displaying the Physical Ports on a Module ................................................2-75Displaying the Physical Ports on a GX 550 Subcard..................................2-75Displaying the Subports on a GX 550 Subcard ..........................................2-76

Viewing IOM and BIO Physical Port Attributes...............................................2-76Viewing IOM Subport Attributes (Universal IOPs)..........................................2-77Viewing GX 550 Subcard Physical Port Attributes ..........................................2-78Viewing GX 550 Subcard Subport Attributes (OC48 and OC48c) ..................2-79Viewing Physical Port Operational Status ........................................................2-81

Viewing Operational Status for a Physical Port on an IOM or BIO...........2-81Viewing Operational Status for Physical Port Channels on the 1-port STM-1/E1 IMA Enhanced IOM .................................................................2-83Viewing Operational Status for a GX 550 Subcard Physical Port .............2-84Viewing Operational Status for a Subport ..................................................2-85

Viewing DS1 Channels............................................................................................2-86Displaying DS1 Channels .................................................................................2-86Viewing DS1 Channel Attributes......................................................................2-87Viewing Operational Status for a DS1 Channel................................................2-88

Before You Begin .......................................................................................2-88To View Operational Information for a DS1 Channel ...............................2-88

Viewing DS0 Channel Allocation ...........................................................................2-90Viewing E1 Channels ..............................................................................................2-91

Displaying E1 Channels ....................................................................................2-91Viewing E1 Channel Attributes ........................................................................2-92Viewing Operational Status for an E1 Channel ................................................2-92

Before You Begin .......................................................................................2-92To View Operational Information for an E1 Channel ................................2-93

Viewing IMA Groups ..............................................................................................2-94Displaying the IMA Groups on a Physical Port ................................................2-94Viewing IMA Group Attributes ........................................................................2-94Viewing Operational Status for an IMA Group ................................................2-95

Before You Begin .......................................................................................2-95To View Operational Information for an IMA Group ................................2-95

Viewing IMA Links.................................................................................................2-98Displaying the IMA Links on an IMA Group...................................................2-98Viewing IMA Link Attributes ...........................................................................2-98Viewing Operational Status for an IMA Link...................................................2-99

Before You Begin .......................................................................................2-99To View Operational Information for an IMA Link.................................2-100

Monitoring VP Shaping .........................................................................................2-101Monitoring VP Shaping on a B-STDX 9000 Switch ......................................2-101

Background...............................................................................................2-101To Monitor VP Shaping on B-STDX 9000 Switches...............................2-102Additional VP Shaping Monitoring..........................................................2-104

Monitoring VP Shaping on a CBX 500/3500 Switch .....................................2-104Background...............................................................................................2-104Restrictions ...............................................................................................2-104

x10/7/05 Switch Diagnostics User’s Guide for CBX 3500, CBX 500, GX 550, and B-STDX 9000

Contents


Displaying VP Shaping Information.........................................................2-105Description of VP Shaping Field ..............................................................2-105Additional VP Shaping Monitoring..........................................................2-106

Displaying FDL Information for a T1 Port............................................................2-106Viewing ATM TCA Parameters ............................................................................2-106Viewing Physical Port and Module Redundancy ..................................................2-107

Viewing Redundant Modules ..........................................................................2-107Viewing All Redundant Physical Ports Pairs on a Switch ..............................2-107Viewing Working and Protection Ports...........................................................2-108Viewing Physical Port APS Attributes............................................................2-108Issuing APS Commands..................................................................................2-108

Chapter 3 Generating Physical Port StatisticsSupported Statistics....................................................................................................3-1Viewing Physical Port and Subport Summary Statistics ...........................................3-2Viewing DS1 Channel Alarms and Statistics ............................................................3-5

Viewing DS1 Channel Alarms ............................................................................3-5Viewing DS1 Channel Summary Statistics.........................................................3-7

Viewing E1 Channel Summary Statistics ..................................................................3-8Viewing G.826 Statistics for B-STDX 4-Port E1 and B-STDX Channelized E1 Modules ................................................................................................................3-9Viewing RFC 1406 and G.826 Statistics for 12-Port E1, 32-Port E1, and 60-Port Channelized T1/E1 CE Modules .............................................................................3-11

Types of E1 Statistics Available .......................................................................3-11Viewing E1 Statistics ........................................................................................3-11

Viewing 2-port ULC Gigabit Ethernet Module Physical Port Summary Statistics ...................................................................................................................3-18Viewing IMA Group Summary Statistics................................................................3-23Viewing IMA Link Summary Statistics ..................................................................3-25

Chapter 4 Monitoring Physical Port PerformancePM Support on Physical Ports ...................................................................................4-2Setting PM Thresholds...............................................................................................4-3Viewing PM Data For a Physical Port or Subport .....................................................4-3

Opening the Performance Monitoring Statistics Dialog Box..............................4-3Viewing OC-n/STM-n Data ................................................................................4-4

Viewing Current, Interval, or Day Reports for OC-n/STM-n Data..............4-4Viewing Medium Reports for OC-n/STM-n Data ......................................4-11

Viewing DS3/E3 Data .......................................................................................4-12Viewing Current, Interval, Day, or Total Reports for DS3/E3 Data ..........4-12Viewing Configuration Reports for DS3/E3 Data ......................................4-18Viewing the DS3/E3 Configuration Line Status.........................................4-22Viewing the DS3/E3 Configuration PLCP Status ......................................4-23Viewing the DS3/E3 Configuration TC Status...........................................4-24

Viewing T1/E1 Data..........................................................................................4-24Viewing PM Data for a DS1 Channel......................................................................4-28Viewing PM Data for an E1 Channel ......................................................................4-33Viewing PM Data for IMA Groups and Links ........................................................4-38

Contents

Switch Diagnostics User’s Guide for CBX 3500, CBX 500, GX 550, and B-STDX 9000 xi


Viewing IMA Group Performance-Monitoring Statistics.................................4-38Viewing IMA Link Performance-Monitoring Statistics ...................................4-40

Chapter 5 Testing Modules, Ports, and ChannelsBackground Diagnostics ............................................................................................5-1

Problems Detected by Background Diagnostics .................................................5-1Viewing Background Diagnostics.......................................................................5-2Switching to a Redundant Unit ...........................................................................5-6

Redundancy Support on the CBX 3500........................................................5-6To Switch to a Redundant Unit.....................................................................5-7

Foreground Diagnostics .............................................................................................5-7Problems Detected by Foreground Diagnostics ..................................................5-7When to Run Foreground Diagnostics on a Physical Port or on Channels .........5-8External Loopback Connectors ...........................................................................5-8Changing the Admin Status Before Running Tests.............................................5-8

Changing an IOM’s or BIO’s Admin Status ................................................5-9Changing a Physical Port’s or Subport’s Admin Status ...............................5-9Changing a Channel’s Admin Status ..........................................................5-10Changing a Logical Port’s Admin Status ...................................................5-11

Viewing Foreground Diagnostics For an IOM or BIO .....................................5-12Viewing Foreground Diagnostics For a Physical Port or Subport ....................5-14Viewing Foreground Diagnostics For a Channel ..............................................5-15Viewing Foreground Diagnostics For an IMA Group ......................................5-17Viewing Foreground Diagnostics For a Logical Port .......................................5-19Viewing Foreground Diagnostics For a Logical Port on the 2-port ULCGigabit Ethernet Module ...................................................................................5-21

Running Loopback Tests .........................................................................................5-22Restrictions........................................................................................................5-23Loopback Tests For DS3/E3 Physical Ports......................................................5-23

Types of DS3/E3 Physical Port Loopback Tests ........................................5-23DS3/E3 Loopback Traps.............................................................................5-25Running a DS3/E3 Loopback Test .............................................................5-25

Loopback Tests for HSSI Physical Ports ..........................................................5-26Types of HSSI Physical Port Loopback Tests ............................................5-26Running a HSSI Loopback Test .................................................................5-27

Loopback Tests for OC-n/STM-n Physical Ports..............................................5-28Types of OC-n/STM-n Physical Port Loopback Tests ...............................5-28Running an OC-n/STM-n Loopback Test ..................................................5-28

Loopback Tests For Physical Ports on T1 or E1 Modules ................................5-30Modules Covered in This Section...............................................................5-30Types of T1/E1 Physical Port Loopback Tests...........................................5-30Network Response to a T1/E1 Loopback ...................................................5-32Running a Physical Port Loopback Test on a T1 or E1 Module ................5-33

Loopback Tests For T1 Physical Ports on the 32-Port Channelized T1/E1 FR/IP Module and 60-Port Channelized T1/E1 Circuit Emulation Module .....5-35

Types of T1 Physical Port Loopback Tests For the 32-Port and 60-Port Channelized T1/E1 Modules ......................................................................5-35Running a T1 Loopback Test (32-port and 60-port modules) ....................5-36

xii10/7/05 Switch Diagnostics User’s Guide for CBX 3500, CBX 500, GX 550, and B-STDX 9000

Contents


Loopback Tests For E1 Physical Ports on the 32-Port Channelized T1/E1 FR/IP Module and 60-Port Channelized T1/E1 Circuit Emulation Module .....5-39

Types of E1 Physical Port Loopback Tests For the 32-Port and 60-Port Channelized T1/E1 Modules ......................................................................5-39Running an E1 Near-End Loopback Test (32-port and 60-port modules).........................................................................................5-39

Near-End Loopback Tests for DS1 Channels ...................................................5-40About DS1 Channel Near-End Loopback Tests .........................................5-40Running a DS1 Channel Near-End Loopback Test ....................................5-42

Far-End Loopback Tests for DS1 Channels......................................................5-43About DS1 Channel Far-End Loopback Tests ...........................................5-43Running a DS1 Channel Far-End Loopback Test ......................................5-45

Near-End Loopback Tests for E1 Channels ......................................................5-47About E1 Channel Near-End Loopback Tests............................................5-47Running an E1 Channel Near-End Loopback Test.....................................5-47

Near-End Loopback Tests for DS0 Channels ...................................................5-48Modules Supported By DS0 Near-End Loopback Tests ............................5-49About DS0 Near End Loopback Tests........................................................5-49Running a DS0 Near-End Loopback Test ..................................................5-50

Far-End Loopback Tests for DS0 Channels......................................................5-51Modules Supported By DS0 Far-End Loopback Tests...............................5-51Logical Port Restrictions ............................................................................5-52About DS0 Far-End Loopback Tests..........................................................5-52Running a DS0 Far-End Loopback Test.....................................................5-53Test Pattern Generation ..............................................................................5-55

Layer 2 Tunnel OAM Loopback Tests..............................................................5-56Running BERTs .......................................................................................................5-57

E1/T1 Physical Port BERTs For 60-Port Channelized T1/E1 Circuit Emulation Modules ...............................................................................5-57

About Physical Port BERTs For 60-Port Channelized T1/E1Circuit Emulation Modules.........................................................................5-57BERT Patterns Available............................................................................5-58Running a BERT for a Physical Port on a 60-Port ChannelizedT1/E1 Circuit Emulation Module ...............................................................5-59

DS3 Physical Port BERTs For 8-Port Subrate DS3 FR/IP Modules ................5-63About Physical Port BERT For 8-Port Subrate DS3 FR/IP Modules....................................................................................5-63BERT Patterns Available............................................................................5-63Running a BERT for a Physical Port on an 8-Port Subrate DS3FR/IP Module .............................................................................................5-64

Physical Port BERTs for DS3 and POS Universal I/O Modules ......................5-66About Physical Port BERTs .......................................................................5-66BERT Patterns Available for DS3 and POS Universal I/O Modules .........5-66Running a BERT for a Physical Port on a DS3 or POS Universal I/O Module .................................................................................5-67

DS1 Channel BERTs for Channelized DS3 Modules .......................................5-70About DS1 Channel BERTs .......................................................................5-70BERT Patterns Available............................................................................5-70

Contents

Switch Diagnostics User’s Guide for CBX 3500, CBX 500, GX 550, and B-STDX 9000 xiii


Running a BERT for a DS1 Channel..........................................................5-71

E1 Channel BERTs for 1-Port Channelized STM-1/E1 IMA and IMA Enhanced Modules ...................................................................................5-73

About E1 Channel BERTs..........................................................................5-73BERT Patterns Available............................................................................5-73Running a BERT for an E1 Channel ..........................................................5-74

DS0 BERTs for Channelized T1/E1 and DS3/1/0 FR/IP Modules...................5-77About DS0 Channel BERTs .......................................................................5-77BERT Patterns Available............................................................................5-77Running a BERT for a DS0 Channel..........................................................5-78

Logical Port BERTs For 60-Port Channelized T1/E1 CircuitEmulation Modules ...........................................................................................5-82

About Logical Port BERTs For 60-Port Channelized T1/E1Circuit Emulation Modules.........................................................................5-82BERT Patterns Available............................................................................5-82Running a BERT for a 60-Port Channelized T1/E1 CircuitEmulation Module Logical Port .................................................................5-83

Troubleshooting BERT Failures .......................................................................5-87

Chapter 6 Logical Port AttributesDisplaying Logical Ports............................................................................................6-1

Restrictions..........................................................................................................6-1Displaying the Logical Ports That Belong to a Physical Port or Subport ...........6-2

Displaying the Logical Ports on an IOM/BIO Physical Port........................6-2Displaying the Logical Ports on a GX 550 Subcard Physical Port...............6-3Displaying the Logical Ports on a GX 550 OC48/OC48c Subcard Subport............................................................................................6-3Displaying the Logical Ports on a Physical Port DS1 or E1 Channel ..........6-4Displaying the Logical Ports on a Physical Port IMA Group.......................6-4

Displaying the Logical Ports That Belong to a Switch, Module, or Subcard .....6-5Displaying the Logical Ports That Belong to a Switch.................................6-5Displaying the Logical Ports That Belong to a Module ...............................6-6

Categories of Logical Port Attributes ........................................................................6-7Viewing Logical Port Attributes ..............................................................................6-10Viewing Logical Port QoS Parameters ....................................................................6-10Viewing Logical Port SVC Attributes .....................................................................6-15Viewing Logical Port SVC QoS Parameters ...........................................................6-15Viewing Logical Port SVC Traffic Descriptor Limits.............................................6-18Viewing Logical Port SVC Signaling Tuning Parameters ......................................6-19

Chapter 7 Monitoring ATM Logical PortsViewing Operational Status for an ATM Logical Port ..............................................7-1

Before You Begin................................................................................................7-1To View Operational Information for an ATM Logical Port..............................7-1Viewing 2-port ULC Gigabit Ethernet Logical Port Operational Status ............7-6

Viewing ATM Logical Port Summary Statistics .......................................................7-7Viewing 2-port ULC Gigabit Ethernet Logical Port Summary Statistics................7-17

xiv10/7/05 Switch Diagnostics User’s Guide for CBX 3500, CBX 500, GX 550, and B-STDX 9000

Contents


Viewing 2-port ULC Gigabit Ethernet LPort Object Summary Statistics ........7-17

Viewing 2-port ULC Gigabit Ethernet LPort Shaper Object SummaryStatistics.............................................................................................................7-19Viewing 2-port ULC Gigabit Ethernet LPort VLAN Profile Summary Statistics.............................................................................................................7-20

Viewing ATM PNNI and AINI Logical Port Signaling Statistics...........................7-22Viewing Management VPI/VCIs.............................................................................7-24

Chapter 8 Monitoring Frame Relay Logical PortsViewing Operational Status for a Frame Relay Logical Port ....................................8-1

Before You Begin................................................................................................8-1To View Operational Information for a Frame Relay Logical Port ....................8-1

Viewing Frame Relay Logical Port Summary Statistics ...........................................8-6Viewing RLMI Service Name Bindings..................................................................8-13Viewing Multicast DLCIs........................................................................................8-15Viewing Management DLCIs ..................................................................................8-16

Chapter 9 Monitoring IPDisplaying IP Objects ................................................................................................9-2

Overview of Procedures ......................................................................................9-2Procedure for Displaying IP Objects...................................................................9-3

Displaying IP Services Objects.....................................................................9-3Displaying BGP Objects ...............................................................................9-4Displaying OSPF Objects .............................................................................9-5Displaying Route Policy Objects ..................................................................9-6Displaying IP Servers ...................................................................................9-7Displaying IP Logical Ports ..........................................................................9-7Displaying IP Logical Port Objects ..............................................................9-8Displaying PPP IP Logical Port Objects.......................................................9-9Displaying IP Interface Address Objects......................................................9-9Displaying LSPs .........................................................................................9-10

Viewing IP Object Attributes...................................................................................9-10Viewing IP Object Operational Status .....................................................................9-11

Before You Begin..............................................................................................9-11Viewing BGP Operational Information ............................................................9-11Viewing Point-to-Point LSP Operational Information......................................9-12Viewing OSPF Operational Information...........................................................9-16

Viewing IP Object Summary Statistics....................................................................9-17Viewing RIP Summary Statistics ......................................................................9-18Viewing IP Logical Port Summary Statistics....................................................9-19Viewing PPP IP Logical Port Statistics.............................................................9-21Viewing IP Logical Port RSVP-TE Statistics ...................................................9-21Viewing Point-to-Point LSP Summary Statistics..............................................9-23Viewing BGP Peer Summary Statistics ............................................................9-24Viewing Fast Ethernet Logical Port Summary Statistics ..................................9-28

Viewing IP VPNs.....................................................................................................9-32Viewing IP Network Resources Assigned to a Specific IP VPN ............................9-33

Contents

Switch Diagnostics User’s Guide for CBX 3500, CBX 500, GX 550, and B-STDX 9000 xv


Overview ...........................................................................................................9-33Entering the Context of an IP VPN...................................................................9-33

Chapter 10 Monitoring TrunksDisplaying Trunks....................................................................................................10-2

Displaying the Trunks That Belong to a Network ............................................10-2Displaying the Trunks That Belong to a Switch ...............................................10-2Displaying the Trunks That Belong to a Logical Port.......................................10-3

Viewing Trunk Attributes ........................................................................................10-4Viewing Trunk Operational Information .................................................................10-5

Before You Begin..............................................................................................10-5To View the Operational Information of a Trunk .............................................10-5

Viewing Trunks on a Map .......................................................................................10-8Viewing Trunk Summary Statistics .......................................................................10-10Viewing PVC Usage ..............................................................................................10-12Running OAM Loopback Tests on ATM Over MPLS Trunks .............................10-13

Overview .........................................................................................................10-13To Run the OAM Loopback Test on an ATMoMPLS Trunks .......................10-13

Filtering Information Displayed Based on the VPN or Customer .........................10-15Viewing VNN Customers ......................................................................................10-16Viewing Layer2 VPNs...........................................................................................10-17Viewing VNN OSPF Loopback Addresses ...........................................................10-19Viewing VNN OSPF Area Aggregates..................................................................10-20Viewing VNN OSPF Virtual Links .......................................................................10-22Viewing VNN OSPF External Routes Aggregates................................................10-23Viewing PNNI Links .............................................................................................10-25

Chapter 11 Circuit AttributesDisplaying Circuits ..................................................................................................11-2Categories of Circuit Attributes ...............................................................................11-4Viewing Circuit Attributes.......................................................................................11-6Viewing SVC Attributes ..........................................................................................11-7

Viewing All Node Prefixes ...............................................................................11-7Viewing All Port Prefixes .................................................................................11-8Viewing All Port Addresses ..............................................................................11-9Viewing All Port User Parts ............................................................................11-10Viewing All Port Network IDs........................................................................11-12Viewing All Active SVCs ...............................................................................11-13Viewing Active SVC Attributes......................................................................11-14Viewing All ILMI Addresses ..........................................................................11-18Viewing SVC Failed Calls ..............................................................................11-19Viewing SVC Failed-Call Attributes ..............................................................11-21Viewing Closed User Groups..........................................................................11-25Viewing Closed User Group Members ...........................................................11-27Viewing Port Security Screens........................................................................11-28

xvi10/7/05 Switch Diagnostics User’s Guide for CBX 3500, CBX 500, GX 550, and B-STDX 9000

Contents


Chapter 12 Monitoring ATM CircuitsViewing Circuit Operational Status .........................................................................12-2

Before You Begin..............................................................................................12-2To View the Operational Status of an ATM Circuit .........................................12-2Viewing PWE3 Profile Operational Information ............................................12-16

Viewing Enhanced Connection Trace Information ...............................................12-18Overview of Enhanced Connection Trace.......................................................12-18Running Enhanced Connection Trace on a PVC or SVC ...............................12-20

Viewing Path Trace Information ...........................................................................12-20Overview of Path Trace Information...............................................................12-21

Purpose of Path Trace ...............................................................................12-21Differences Between Path Trace and Connection Trace ..........................12-21Circuits That Support Path Trace..............................................................12-21

Configuring Path Trace Information ...............................................................12-22Methods for Configuring Path Trace ........................................................12-22Configuring Path Trace Information on a Circuit (other than SVCs).......12-22Configuring Path Trace Information on a Logical Port ............................12-24

Displaying Path Trace Information for a Circuit.............................................12-26Displaying Path Trace Information for a Logical Port....................................12-30

Viewing ATM Circuit Summary Statistics............................................................12-34Viewing 2-port ULC Gigabit Ethernet LPort Circuit Summary Statistics forEthernet to ATM Endpoints...................................................................................12-42Viewing NTM and NDC Statistics ........................................................................12-51

Network Traffic Management .........................................................................12-51Measures of Congestion............................................................................12-51NTM Surveillance Measurements ............................................................12-52NTM State Change Notifications .............................................................12-52NTM Control Functions............................................................................12-52

Network Data Collection.................................................................................12-53Traffic Load Measurements......................................................................12-53UPC/NPC Disagreement Measurements ..................................................12-54Traffic Load and Congestion Measurements............................................12-54

Configuring NTM Attributes for a Feeder Logical Port .................................12-54Viewing NTM Attributes for a Logical Port ...................................................12-56Viewing NTM Logical Port Statistics .............................................................12-57Viewing NDC Logical Port Statistics .............................................................12-58Configuring NDC Attributes for a Point-to-Point Circuit...............................12-59Configuring NDC Attributes for a Point-to-Multipoint Circuit ......................12-61

Restrictions ...............................................................................................12-61To Configure the NDC Thresholds...........................................................12-62

Viewing NDC PVC Thresholds ......................................................................12-63Viewing NDC PVC Data ................................................................................12-64

Viewing ATM SVC Summary Statistics ...............................................................12-64SVC Statistics Overview .................................................................................12-64To View ATM SVC Summary Statistics ........................................................12-64

Viewing CAC Parameters for ATM Circuits.........................................................12-68Testing ATM Circuits ............................................................................................12-69

Circuit Testing Overview ................................................................................12-69

Contents

Switch Diagnostics User’s Guide for CBX 3500, CBX 500, GX 550, and B-STDX 9000 xvii


Before You Begin............................................................................................12-70OAM Connectivity Verification......................................................................12-70

OAM Cells Sent to a CBX 500/3500 or GX 550 UNI Port from an Attached Device ..........................................................................12-70OAM Loopback Cell Generation..............................................................12-71

Sequence of OAM Loopback Tests.................................................................12-71Setting the OAM Loopback Time Interval......................................................12-72Running an OAM Loopback Test on an ATM Circuit ...................................12-73

Offnet PVC Circuits...............................................................................................12-75Viewing PWE3 Offnet PVCs ..........................................................................12-75

To View an Offnet PWE3 PVC................................................................12-75Restarting Offnet PVCs...................................................................................12-76

Purpose......................................................................................................12-76To Restart an Offnet PVC.........................................................................12-76

ATM Round-trip Delay/Cell Loss Statistics..........................................................12-77Requirements...................................................................................................12-77Configuring ATM Round-trip Delay/Cell Loss Statistics...............................12-77

Configuring RTD/CLS for PVCs .............................................................12-78Configuring RTD/CLS for Point-to-point SPVCs (VNN AND PNNI) ...12-79Configuring RTD/CLS for SVCs (VNN and PNNI) ................................12-80

ATM Test Access Function ...................................................................................12-81ATAF Overview..............................................................................................12-81ATAF and PRAM ...........................................................................................12-82ATAF-Virtual Connection Access Configuration...........................................12-82Creating a TAP-VC Instance on the ATAF Monitoring Logical Port ............12-83Selecting a Cell Stream to be Monitored.........................................................12-84

Cell Stream Monitoring Restrictions ........................................................12-84Connecting a TAP-VC to a Cell Stream Resource ...................................12-85

Viewing TAP-VC Operational Status .............................................................12-86Viewing TAP-VC Statistics ............................................................................12-88Modifying a TAP-VC......................................................................................12-89Deleting a TAP-VC .........................................................................................12-91ATAF SDC Logging .......................................................................................12-91

Chapter 13 Monitoring Frame Relay CircuitsViewing Circuit Operational Status .........................................................................13-1

Before You Begin..............................................................................................13-1To View the Operational Status of a Frame Relay Circuit................................13-1

Viewing Frame Relay PVC Summary Statistics ...................................................13-11Frame Relay PVC Summary Statistics Overview...........................................13-11To View Frame Relay PVC Summary Statistics.............................................13-11

Viewing 2-port ULC Gigabit Ethernet LPort Circuit Summary Statistics forEthernet to Frame Relay Endpoints .......................................................................13-15Viewing CAC Parameters for Frame Relay Circuits .............................................13-24

About CAC......................................................................................................13-24To View CAC Parameters ...............................................................................13-24

Viewing Frame Relay SVC Summary Statistics ...................................................13-26SVC Summary Statistics Overview ................................................................13-26

xviii10/7/05 Switch Diagnostics User’s Guide for CBX 3500, CBX 500, GX 550, and B-STDX 9000

Contents


To View Frame Relay SVC Summary Statistics.............................................13-26Testing Frame Relay PVCs....................................................................................13-30

PVC Loopback Settings ..................................................................................13-30When to Use PVC Loopback ..........................................................................13-32Problems PVC Loopback Can Detect .............................................................13-32Setting a PVC Loopback .................................................................................13-32Checking the PVC Loopback Status ...............................................................13-34

Frame Relay OAM Testing on PVCs (6-Port Channelized DS3/1/0 FrameRelay I/O Modules)................................................................................................13-36

About Frame Relay OAM ...............................................................................13-36Types of Circuits Supported .....................................................................13-36Administrative Domains and Monitoring Points ......................................13-36Frame Relay OAM Measurements ...........................................................13-39

Configuring and Running Frame Relay OAM ................................................13-40Configuring the Monitoring Points...........................................................13-40Running Frame Relay OAM on a Circuit .................................................13-43

Disabling Frame Relay OAM Capabilities on a Logical Port.........................13-48Restarting Offnet PVCs .........................................................................................13-49

Purpose ............................................................................................................13-49To Restart an Offnet PVC ...............................................................................13-49

Chapter 14 Monitoring AlarmsDisplaying a List of Alarms.....................................................................................14-2

Viewing and Managing Alarms ........................................................................14-5Filtering the Alarms That Are Displayed.................................................................14-7

Overview ...........................................................................................................14-7Creating Filter Settings......................................................................................14-7Setting Alarm Count........................................................................................14-11Alarm Refresh Rate .........................................................................................14-12

Acknowledging/Unacknowledging Alarms...........................................................14-12Acknowledging or Unacknowledging an Individual Alarm ...........................14-13Acknowledging Selected Alarms ....................................................................14-13Acknowledging Filtered Alarms .....................................................................14-13Acknowledging All Alarms.............................................................................14-13Unacknowledging Selected Alarms ................................................................14-14Unacknowledging Filtered Alarms .................................................................14-14Unacknowledging All Alarms.........................................................................14-14

Viewing Alarm Details ..........................................................................................14-14Sorting the Alarms That Are Displayed.................................................................14-16Setting the Severity of Alarms...............................................................................14-18Saving Alarms........................................................................................................14-18

Saving Selected Alarms...................................................................................14-18Saving Acknowledged Alarms........................................................................14-19Saving Unacknowledged Alarms ....................................................................14-19Saving Filtered Alarms....................................................................................14-19Saving Unfiltered Alarms................................................................................14-19Saving All Alarms ...........................................................................................14-20

Deleting Alarms .....................................................................................................14-20

Contents

Switch Diagnostics User’s Guide for CBX 3500, CBX 500, GX 550, and B-STDX 9000 xix


Deleting Selected Alarms ................................................................................14-20Deleting Filtered Alarms .................................................................................14-20Deleting Unfiltered Alarms .............................................................................14-21Deleting All Alarms ........................................................................................14-21Deleting Acknowledged Alarms .....................................................................14-21Deleting Unacknowledged Alarms .................................................................14-21

Event Configuration...............................................................................................14-21Managing the Alarm Configuration for a Switch ..................................................14-22

Contact Alarm Relay Status ............................................................................14-22Alarm Transmit Rate .......................................................................................14-23Configuring the Alarm Configuration For a Switch .......................................14-23

Clearing the Alarm Relay ......................................................................................14-24

Chapter 15 Managing the Event LogAbout the Event Log................................................................................................15-2Event Log Structure .................................................................................................15-3

System Components ..........................................................................................15-3Importance Levels ...........................................................................................15-15

Configuration Process Overview ...........................................................................15-16Configuring Remote Event Logging With Navis EMS-CBGX.............................15-17Configuring I/O Modules for Event Logging ........................................................15-19

Setting Logroot Importance Level(s) ..............................................................15-19Help...........................................................................................................15-19Examples...................................................................................................15-19

Displaying Logroot Importance Level(s) ........................................................15-19Examples...................................................................................................15-19

Configuring Applications for Event Logging ........................................................15-20Setting Log Importance Level(s).....................................................................15-20

Help...........................................................................................................15-20Displaying Log Importance Level(s) ..............................................................15-21

Examples...................................................................................................15-21Configuring Tracing...............................................................................................15-21

Setting Trace Importance Level(s) ..................................................................15-21Help...........................................................................................................15-22

Displaying Trace Importance Level(s)............................................................15-22Examples...................................................................................................15-22

Defining Filters ......................................................................................................15-23Setting Log Filters ...........................................................................................15-23Displaying Log Filters.....................................................................................15-24

Example ....................................................................................................15-24Setting Trace Filters ........................................................................................15-24

Example ....................................................................................................15-25Displaying Trace Filters ..................................................................................15-25

Examples...................................................................................................15-25Working With Event Log.......................................................................................15-26

Displaying Log File Contents..........................................................................15-26Active SP/NP ............................................................................................15-26Standby SP/NP..........................................................................................15-26

xx10/7/05 Switch Diagnostics User’s Guide for CBX 3500, CBX 500, GX 550, and B-STDX 9000

Contents


Help...........................................................................................................15-26Examples...................................................................................................15-27

Event Log and the Syslog Utility ....................................................................15-27PRAM Sync and Upgrade Files................................................................15-27Switchover Files .......................................................................................15-28Help...........................................................................................................15-29

Filtering Log and Trace Files for Display .......................................................15-29Setting Log Filters ....................................................................................15-29Setting Trace Filters..................................................................................15-31Filtering Options .......................................................................................15-32

Enhanced Exception Logging .........................................................................15-32Toggling Trace On and Off .............................................................................15-32Deleting Log Files ...........................................................................................15-32

Examples...................................................................................................15-32Disabling the Event Log..................................................................................15-33

Chapter 16 Managing the Crash Dump SystemOverview ...........................................................................................................16-1Crash Dump System Components.....................................................................16-1

Crash Dump Manager .................................................................................16-2Crash Dump Targets ...................................................................................16-2Crash Dump Clients....................................................................................16-2

Crash Dump Files ..............................................................................................16-2Live Upload.......................................................................................................16-3Memory Regions ...............................................................................................16-3Dump Regions...................................................................................................16-3

Disk Storage Considerations....................................................................................16-4Using the Crash Dump System ................................................................................16-4

Getting a Crash Dump.......................................................................................16-4Retrieving Crash Dump Files from the Switch .................................................16-7Changing the Client Configuration ...................................................................16-8

Configuring the Crash Dump System ......................................................................16-9Configuring Crash System Switch Parameters .................................................16-9Viewing and Uploading a Crash Dump File ...................................................16-12Protecting and Unprotecting a Crash Dump File ............................................16-14Configuring Crash System Card Parameters...................................................16-14

Minimum Card Crash Dump Configuration.............................................16-14Modify Crash System Card Parameters....................................................16-15Displaying Dump Region Configuration as Viewed By The Switch .......16-18Configuring Dump Regions......................................................................16-20Viewing Dump Regions............................................................................16-22Deleting a Dump Region ..........................................................................16-24Displaying Memory Regions ....................................................................16-24Uploading Card Memory ..........................................................................16-25

Using Crash Dump Console Commands ...............................................................16-26Enabling Automatic Crash Dump File Protection from the Console ..............16-26Enabling Automatic Upload from the Console ...............................................16-26Setting Default Automatic Upload Pathname from the Console ....................16-27

Contents

Switch Diagnostics User’s Guide for CBX 3500, CBX 500, GX 550, and B-STDX 9000 xxi


Setting Automatic Upload IP Address from the Console................................16-27Enabling Crash Dump Client from the Console..............................................16-27Resetting Crash Dump Client State to the Default Valuefrom the Console .............................................................................................16-27Changing Crash Dump Client State from the Console....................................16-28Changing Target from the Console .................................................................16-28Changing Client Time-out from the Console ..................................................16-29Uploading Card Memory from the Console....................................................16-29Configuring Crash Dump Regions from the Console .....................................16-29Setting Client Configuration to the Default Region Set from the Console .....16-30Deleting Regions from the Console ................................................................16-30Restoring PRAM Client Configuration from the Console ..............................16-31Clearing Client Configuration from the Console ............................................16-31Protecting Crash Dump Files from the Console..............................................16-31Removing Crash Dump Files from the Console .............................................16-31Uploading Crash Dump Files from the Console .............................................16-31Synchronizing Crash Dump Components from the Console ..........................16-32Changing Target Size from the Console .........................................................16-32Enabling Targets from the Console.................................................................16-33Resetting Targets to the Default Value from the Console...............................16-33Aborting Crash Dump File Uploads from the Console ...................................16-34Displaying Crash Dump System Status from the Console..............................16-34Displaying Crash Dump Client Status from the Console................................16-34Displaying the Client Configuration from the Console...................................16-34Displaying Crash Dump File Status from the Console ...................................16-34Displaying Card Memory Regions from the Console .....................................16-35Displaying Crash Dump Target Status from the Console ...............................16-35Displaying Crash Dump Uploader Status from the Console...........................16-35Displaying Lastcrash Information for Cards from the Console ......................16-35

Crash Dump System Restrictions ..........................................................................16-36CBX 500 SPs...................................................................................................16-36Standby Cards..................................................................................................16-36

Chapter 17 Monitoring Switch ReliabilityEmergency Action Interface (EAI) ..........................................................................17-2

About the Emergency Action Interface (EAI) ..................................................17-2Console Commands Supported with theEmergency Action Interface (EAI) ...................................................................17-3Using the Emergency Action Interface (EAI)...................................................17-3

Using EAI with a Switch Console Session.................................................17-3Using EAI with a High-Priority Telnet Session .........................................17-4

PVC Establishment Rate Control.............................................................................17-5VC Overload Control and PVC Establishment Rate Control............................17-5

PVC Establishment Rate Control When VC Overload Control Is Enabled ...................................................................................................17-5PVC Establishment Rate Control When VC Overload Control Is Disabled ..................................................................................................17-5Viewing the Overload Control Setting and the Overload

xxii10/7/05 Switch Diagnostics User’s Guide for CBX 3500, CBX 500, GX 550, and B-STDX 9000

Contents


Severity Level .............................................................................................17-5Path Integrity............................................................................................................17-8

About Path Integrity ..........................................................................................17-8Path Integrity Console Commands....................................................................17-8Path Integrity Configuration Example ..............................................................17-9

Switch Configurations ................................................................................17-9Viewing Event Log Messages for Path Integrity Information ........................17-11

Enhanced Fault Manager .......................................................................................17-12Enhanced Fault Manager and Related Reliability Features ............................17-13

Enhanced Exception Logging ................................................................................17-13Enhanced Exception Logging and the Event Log ...........................................17-13

PRAM Consistency................................................................................................17-14About PRAM Consistency ..............................................................................17-14Running the PRAM Consistency Test.............................................................17-14Event Log Messages for the PRAM Consistency Feature ..............................17-16PRAM Consistency Test Console Commands................................................17-17

Enhanced Standby Hardware (ESHW) Tests ........................................................17-18About the Enhanced Standby Hardware Test..................................................17-18Running the Enhanced Standby Hardware Test for SP/NP andIOM/BIO Modules ..........................................................................................17-19Running the Enhanced Standby Hardware Test for SF Modules (GX 550) .....................................................................................17-20Enhanced Standby Hardware Test Console Commands .................................17-21

Chapter 18 Monitoring MIB ValuesMIB Overview .........................................................................................................18-1

SNMP Structure of Management Information ..................................................18-1MIB Information Example ................................................................................18-2MIB Structure....................................................................................................18-2

Object Identifier ..........................................................................................18-2Lucent MIB .......................................................................................................18-4

cascfr Group................................................................................................18-6Using the MIB Browser ...........................................................................................18-7

Displaying All Instances and Values of a MIB Object (Walk) .........................18-7Displaying the Value of a MIB Object Instance (Get) ......................................18-8Setting the Value of a MIB Object Instance (Set).............................................18-8

Appendix A Trap Alarm Condition Messages

Appendix B Summary of Error Codes

Appendix C Using SVC Failure InformationAbout SVC Cause Codes .......................................................................................... C-1Example .................................................................................................................... C-7

Appendix D Signalled QoS, BBC, ATC, and BEI Service Category MappingsDefinition of Specified QoS Classes.........................................................................D-2

Contents

Switch Diagnostics User’s Guide for CBX 3500, CBX 500, GX 550, and B-STDX 9000 xxiii


Definition of Unspecified QoS Class........................................................................D-4Support of Class X, Class A, and Class C ATM Transport Services .......................D-5

Guidelines on Use of Bearer Class, Traffic Parameters, and QoS .....................D-6BCOB-A (ATMF UNI 4.0 Section A9.1.1) ..................................................D-6BCOB-C (ATMF UNI 4.0 Section A9.1.2) ..................................................D-6BCOB-X (ATMF UNI 4.0 Section A9.1.3) ..................................................D-7Transparent VP Service (ATMF UNI 4.0 Section A9.1.4) ...........................D-7

Allowed Combination of Bearer Capabilities, Traffic Parameters, and QoS in ATM UNI 3.0/3.1 and Q.2931 ........................................................D-8Specific Service Category Mappings in ATM UNI 3.0/3.1 and Q.2931 .........D-10Determination of ATM Service Category in ATM UNI 4.0/PNNI 1.0 ...........D-15Allowed Combination of Bearer Capabilities, Traffic Parameters, and QoS in ATM UNI 4.0 and PNNI 1.0.........................................................D-18

Appendix E Using Disk Diagnostic UtilitiesUnderstanding Disk Boot Diagnostics...................................................................... E-2Using Disk Diagnostics at the Switch Console......................................................... E-3

Using the Scandisk Utility.................................................................................. E-4Using the Testdisk Utility................................................................................... E-5

Listing Files and Directories ..................................................................................... E-6

Abbreviations and AcronymsAbbreviations............................................................................................................A-1Acronyms..................................................................................................................A-3

Index

xxiv10/7/05 Switch Diagnostics User’s Guide for CBX 3500, CBX 500, GX 550, and B-STDX 9000

Contents


Contents

Switch Diagnostics User’s Guide for CBX 3500, CBX 500, GX 550, and B-STDX 9000 10/7/05xxv


List of Figures

Figure 1-1. Logical Ports on a Physical Port (IOM) ..........................................1-2Figure 1-2. View Logical Port Dialog Box ........................................................1-2Figure 1-3. View LPort Operational Status Dialog Box (ATM)........................1-3Figure 1-4. PVC Node Expanded.......................................................................1-3Figure 1-5. Circuit Statistics Monitoring Dialog Box ........................................1-4Figure 2-1. Networks Tab...................................................................................2-1Figure 2-2. Network Tree View .........................................................................2-2Figure 2-3. MPLS Traffic Profiles .....................................................................2-3Figure 2-4. View Diffserv Dialog Box...............................................................2-3Figure 2-5. View Intserv Dialog Box .................................................................2-4Figure 2-6. View Affinity Dialog Box ...............................................................2-4Figure 2-7. View Hoplist Dialog Box ................................................................2-5Figure 2-8. Network Tab ....................................................................................2-6Figure 2-9. Switch Object Tree Tab ...................................................................2-7Figure 2-10. Maps Tab .........................................................................................2-7Figure 2-11. Network Map View Window...........................................................2-8Figure 2-12. View Switch Dialog Box .................................................................2-9Figure 2-13. Switch Operational Information Dialog Box.................................2-10Figure 2-14. PNNI Nodes on a Switch...............................................................2-14Figure 2-15. View PNNI Node Configuration Dialog Box................................2-15Figure 2-16. PNNI Operational Information Dialog Box ..................................2-16Figure 2-17. PNNI Signalling Statistics Dialog Box..........................................2-17Figure 2-18. Traffic Descriptor Node Expanded................................................2-19Figure 2-19. View Traffic Descriptor Dialog Box .............................................2-19Figure 2-20. Group 1 Redundancy Dialog Box..................................................2-21Figure 2-21. Group 2 and 3 Redundancy Dialog Box........................................2-21Figure 2-22. Redundant Group Operational Information...................................2-22Figure 2-23. View LDP Entity Dialog Box........................................................2-23Figure 2-24. LDP Entity Operational Information .............................................2-24Figure 2-25. LDP Statistics ................................................................................2-25Figure 2-26. View Tunnel Dialog Box...............................................................2-27Figure 2-27. View Tunnel Dialog Box - RSVP-Lite Tab ..................................2-28Figure 2-28. View Tunnel Dialog Box - Static Tab ...........................................2-29Figure 2-29. MPLS Tunnel Operational Information.........................................2-30Figure 2-30. Tunnel Monitor Configuration Dialog Box...................................2-32Figure 2-31. MPLS Tunnel Statistics .................................................................2-33Figure 2-32. View Layer 2 Tunnel Dialog Box .................................................2-35Figure 2-33. Layer 2 Tunnel Operational Information.......................................2-36Figure 2-34. Layer 2 Tunnel Statistics ...............................................................2-37Figure 2-35. GX 550 Rear View ........................................................................2-40Figure 2-36. CBX 3500 Rear View....................................................................2-41Figure 2-37. CBX 500 Rear View......................................................................2-42Figure 2-38. B-STDX 9000 Rear View..............................................................2-43Figure 2-39. GX 550 Front View .......................................................................2-44

xxvi10/7/05 Switch Diagnostics User’s Guide for CBX 3500, CBX 500, GX 550, and B-STDX 9000

Contents


Figure 2-40. CBX 3500 Front View...................................................................2-45Figure 2-41. CBX 500 Front View.....................................................................2-46Figure 2-42. B-STDX 9000 Front View.............................................................2-47Figure 2-43. SNMP Error Window ....................................................................2-52Figure 2-44. Navis EMS-CBGX Console Window ...........................................2-53Figure 2-45. Modules on a Switch .....................................................................2-54Figure 2-46. Subcards on a GX 550 ...................................................................2-55Figure 2-47. View Card Dialog Box (CP)..........................................................2-56Figure 2-48. View Card Dialog Box (SP) ..........................................................2-57Figure 2-49. View Card Dialog Box (NP)..........................................................2-57Figure 2-50. View Card Operational Information Dialog Box (CP)..................2-58Figure 2-51. View System Timing Dialog Box..................................................2-63Figure 2-52. View Card Dialog Box ..................................................................2-64Figure 2-53. View Card Dialog Box (Universal IOP)........................................2-64Figure 2-54. View SubCard Dialog Box ............................................................2-65Figure 2-55. View Card Operational Information Dialog Box (IOM)...............2-66Figure 2-56. View SubCard Operational Information Dialog Box (GX 550)....2-71Figure 2-57. Objects on 32-port Channelized T1/E1 Module

(Monitor selected)..........................................................................2-73Figure 2-58. 32-port Channelized T1/E1 Module Statistics Monitoring

Dialog Box.....................................................................................2-73Figure 2-59. Physical Ports on a Module ...........................................................2-75Figure 2-60. Physical Ports on a GX 550 Subcard.............................................2-75Figure 2-61. Subports on a GX 550 Subcard .....................................................2-76Figure 2-62. View PPort Dialog Box .................................................................2-77Figure 2-63. View Subport Dialog Box (ATM Universal IOP) .........................2-78Figure 2-64. View PPort Dialog Box (GX 550 Subcard)...................................2-79Figure 2-65. View Subport Dialog Box (GX 550 Subcard)...............................2-80Figure 2-66. View PPort Operational Status Dialog Box (IOM or BIO) ...........2-81Figure 2-67. All Channels Oper Info Dialog Box ..............................................2-84Figure 2-68. View PPort Operational Status Dialog Box (GX 550 Subcard) ....2-85Figure 2-69. View PPort Operational Status Dialog Box (GX 550 Subport) ....2-86Figure 2-70. DS1 Channels on a Physical Port ..................................................2-87Figure 2-71. View Channel Dialog Box (DS1) ..................................................2-88Figure 2-72. View Channel Operational Dialog Box (DS1) ..............................2-89Figure 2-73. Channels Class Node .....................................................................2-90Figure 2-74. DS0 Allocation Dialog Box...........................................................2-90Figure 2-75. E1 Channels on a Physical Port .....................................................2-91Figure 2-76. View Channel Dialog Box (E1 Channel) ......................................2-92Figure 2-77. View PPort Operational Dialog Box (E1 Channel) .......................2-93Figure 2-78. IMA Group on Physical Port .........................................................2-94Figure 2-79. View IMA Group Dialog Box .......................................................2-95Figure 2-80. IMA Group Operational Info Dialog Box .....................................2-96Figure 2-81. IMA Links on an IMA Group........................................................2-98Figure 2-82. View IMA Link Dialog Box..........................................................2-99Figure 2-83. IMA Link Oper Info Dialog Box.................................................2-100Figure 2-84. View PPort: Administrative Tab .................................................2-102Figure 2-85. View Card: Traffic Engineering Tab...........................................2-105

Contents

Switch Diagnostics User’s Guide for CBX 3500, CBX 500, GX 550, and B-STDX 9000 10/7/05xxvii


Figure 2-86. Physical Port Pairings Dialog Box (Redundancy).......................2-107Figure 3-1. Monitoring Node on Physical Port ..................................................3-2Figure 3-2. PPort Statistics Monitoring Dialog Box ..........................................3-3Figure 3-3. Channels Class Node .......................................................................3-6Figure 3-4. Channel Alarm Status Dialog Box ..................................................3-6Figure 3-5. Channel Statistics Monitoring Dialog Box......................................3-7Figure 3-6. E1 Performance Monitoring Statistics Dialog Box

(G.826 Statistics) ...........................................................................3-10Figure 3-7. E1 Performance Monitoring Statistics Dialog Box .......................3-12Figure 3-8. 2-port ULC Gigabit Ethernet Module PPort Statistics

Monitoring Dialog Box..................................................................3-19Figure 4-1. Performance Monitoring Statistics Dialog Box

(OC-3n/STM-n) ...............................................................................4-4Figure 4-2. DS3/E3 Statistics Configuration Dialog Box ................................4-11Figure 4-3. Performance Monitoring Statistics Dialog Box (DS3/E3) ............4-13Figure 4-4. DS3/E3 Statistics Configuration Dialog Box ................................4-18Figure 4-5. DS3/E3 Configuration Line Status Dialog Box.............................4-22Figure 4-6. DS3/E3 Configuration PLCP Status Dialog Box ..........................4-23Figure 4-7. DS3/E3 Configuration TC Status Dialog Box...............................4-24Figure 4-8. Performance Monitoring Statistics Dialog Box (T1/E1) ...............4-25Figure 4-9. Performance Monitoring Statistics Dialog Box (DS1 Channel)....4-29Figure 4-10. Performance Monitoring Statistics Dialog Box (E1 channel) .......4-34Figure 4-11. IMA Group Performance Monitoring Statistics Dialog Box.........4-38Figure 4-12. IMA Link Performance Monitoring Statistics Dialog Box ...........4-40Figure 5-1. Card Diagnostics Dialog Box ..........................................................5-2Figure 5-2. Modify Card Dialog Box .................................................................5-9Figure 5-3. Modify PPort Dialog Box..............................................................5-10Figure 5-4. Modify Channel Dialog Box .........................................................5-11Figure 5-5. Modify Logical Port Dialog Box...................................................5-12Figure 5-6. Card Diagnostics Dialog Box ........................................................5-13Figure 5-7. PPort Diagnostics Dialog Box .......................................................5-14Figure 5-8. Channel Diagnostics Dialog Box...................................................5-16Figure 5-9. IMA Group Diagnostics Dialog Box.............................................5-17Figure 5-10. Diagnostics Dialog Box (Logical Port) .........................................5-20Figure 5-11. Diagnostics Dialog Box (Logical Port, 2-port ULC

Gigabit Ethernet Module) ..............................................................5-21Figure 5-12. PPort Diagnostics Dialog Box .......................................................5-25Figure 5-13. PPort Diagnostics Dialog Box .......................................................5-27Figure 5-14. PPort Diagnostics Dialog Box .......................................................5-29Figure 5-15. PPort Diagnostics Dialog Box .......................................................5-34Figure 5-16. PPort Diagnostics Dialog Box .......................................................5-37Figure 5-17. Near-End Diag Loopback ..............................................................5-41Figure 5-18. Near-End Loopback.......................................................................5-42Figure 5-19. Perform Foreground Channel Diagnostics Dialog Box.................5-42Figure 5-20. DS1 Far-End CSU/DSU Loopback ...............................................5-45Figure 5-21. DS1 Far-End NI Loopback............................................................5-45Figure 5-22. Perform Foreground Channel Diagnostics Dialog Box.................5-46Figure 5-23. PPort Diagnostics Dialog Box .......................................................5-48

xxviii10/7/05 Switch Diagnostics User’s Guide for CBX 3500, CBX 500, GX 550, and B-STDX 9000

Contents


Figure 5-24. DS0 Near-End Loopback...............................................................5-49Figure 5-25. Diagnostics Dialog Box.................................................................5-50Figure 5-26. DS0 Far-End Loopback .................................................................5-52Figure 5-27. Far-End Loopback Using Midspan Repeaters ...............................5-52Figure 5-28. Diagnostics Dialog Box (DS0 Far End) ........................................5-53Figure 5-29. Layer 2 Tunnel OAM ....................................................................5-56Figure 5-30. PPort Diagnostics Dialog Box .......................................................5-60Figure 5-31. PPort Diagnostics Dialog Box .......................................................5-64Figure 5-32. BERT PPort Dialog Box (Universal DS3 or POS IOM)...............5-68Figure 5-33. Channel Diagnostics Dialog Box...................................................5-71Figure 5-34. Channel Diagnostics Dialog Box...................................................5-75Figure 5-35. Diagnostics Dialog Box (logical port) ...........................................5-79Figure 5-36. Diagnostics Dialog Box (Logical Port) .........................................5-84Figure 6-1. Logical Ports on a Physical Port (IOM/BIO) ..................................6-2Figure 6-2. Logical Ports on a Physical Port (GX 550 subcard) ........................6-3Figure 6-3. Logical Ports on a Subport ..............................................................6-3Figure 6-4. Logical Ports on a Physical Port (DS1 or E1Channel) ....................6-4Figure 6-5. Logical Ports on a Physical Port (IMA Group) ...............................6-5Figure 6-6. Logical Ports on a Switch ................................................................6-5Figure 6-7. Logical Ports on a Module (IOM) ...................................................6-6Figure 6-8. View Logical Port Dialog Box ......................................................6-10Figure 6-9. View Logical QoS Parameters Dialog Box ...................................6-11Figure 6-10. Configure SVC Dialog Box...........................................................6-15Figure 6-11. View LPort SVC QoS Parameters Dialog Box .............................6-16Figure 6-12. TD Limits Dialog Box ...................................................................6-18Figure 6-13. SVC Signaling Tuning Dialog Box ...............................................6-19Figure 7-1. View LPort Operational Status Dialog Box (ATM)........................7-2Figure 7-2. View LPort Operational Status Dialog Box ....................................7-6Figure 7-3. LPort Statistics Monitoring Dialog Box ..........................................7-8Figure 7-4. Statistics Categories Under a Monitoring Node

(ATM Logical Port) .........................................................................7-8Figure 7-5. 2-port ULC Gigabit Ethernet Logical Port Statistics Monitoring

Dialog Box.....................................................................................7-18Figure 7-6. 2-port ULC Gigabit Ethernet Logical Port Shaper Statistics

Monitoring Dialog Box..................................................................7-20Figure 7-7. 2-port ULC Gigabit Ethernet Logical Port VLAN Profile

Statistics Monitoring Dialog Box ..................................................7-21Figure 7-8. NNI Signalling Statistics for LPort Dialog Box ............................7-23Figure 7-9. View Management VPI/VCI Dialog Box......................................7-25Figure 8-1. View LPort Operational Status Dialog Box

(Frame Relay UNI DCE) .................................................................8-2Figure 8-2. View LPort Operational Status Dialog Box (MLFR UNI DCE).....8-2Figure 8-3. LPort Statistics Monitoring Dialog Box ..........................................8-6Figure 8-4. Statistics Categories Under a Monitoring Node

(Frame Relay Logical Port) .............................................................8-7Figure 8-5. View Service Name Dialog Box (Frame Relay) ...........................8-14Figure 8-6. View Multicast DLCI Dialog Box.................................................8-15Figure 8-7. View Management DLCI Dialog Box...........................................8-16

Contents

Switch Diagnostics User’s Guide for CBX 3500, CBX 500, GX 550, and B-STDX 9000 10/7/05xxix


Figure 9-1. IP Services Class Nodes ..................................................................9-4Figure 9-2. BGP Objects ....................................................................................9-5Figure 9-3. OSPF Objects...................................................................................9-6Figure 9-4. Route Policy Objects .......................................................................9-6Figure 9-5. Modules on a Switch .......................................................................9-7Figure 9-6. IP Logical Port .................................................................................9-8Figure 9-7. IP Logical Port Objects....................................................................9-8Figure 9-8. PPP IP Logical Port .........................................................................9-9Figure 9-9. IP Interface Address Objects ...........................................................9-9Figure 9-10. LSPs Under a Network ..................................................................9-10Figure 9-11. BGP Parameters Operational Information Dialog Box .................9-12Figure 9-12. View Point-to-Point LSP Connection Operational Information

Dialog Box.....................................................................................9-13Figure 9-13. Operational Status Dialog Box ......................................................9-17Figure 9-14. RIP Statistics Monitoring Dialog Box...........................................9-18Figure 9-15. IP LPort Statistics Monitoring Dialog Box ...................................9-19Figure 9-16. IP LPort RSVP-TE Statistics .........................................................9-22Figure 9-17. Point to Point LSP Statistics Monitoring Dialog Box ...................9-23Figure 9-18. BGP Peer Statistics Monitoring Dialog Box .................................9-25Figure 9-19. Fast Ethernet Logical Port Monitoring Statistics Dialog Box .......9-29Figure 9-20. VPNs Node ....................................................................................9-32Figure 9-21. View VPN Dialog Box (IP VPN) ..................................................9-32Figure 9-22. Select IP VPN Name Dialog Box ..................................................9-33Figure 9-23. Navis EMS-CBGX Main Window ................................................9-34Figure 10-1. Trunk Nodes Under a Network......................................................10-2Figure 10-2. Trunk Nodes Under a Switch ........................................................10-3Figure 10-3. Trunk Nodes Under a Logical Port................................................10-3Figure 10-4. View Trunk Dialog Box ................................................................10-4Figure 10-5. View Trunk Operational Information............................................10-5Figure 10-6. Maps Tab .......................................................................................10-8Figure 10-7. Network Map View Window.........................................................10-9Figure 10-8. Trunk Statistics Monitoring Dialog Box .....................................10-10Figure 10-9. Show All PVCs on Trunk Dialog Box ........................................10-12Figure 10-10. Trunk OAM Dialog Box..............................................................10-13Figure 10-11. Networks......................................................................................10-15Figure 10-12. Select Layer2 Customer/VPN View Dialog Box ........................10-15Figure 10-13. VNN Customers Node.................................................................10-16Figure 10-14. View Customer Dialog Box.........................................................10-16Figure 10-15. VPNs Node ..................................................................................10-17Figure 10-16. View VPN Dialog Box ................................................................10-18Figure 10-17. VNN Loopback Addresses Node.................................................10-19Figure 10-18. View VNN Loopback Address Dialog Box ................................10-19Figure 10-19. VNN Area Aggregates Node .......................................................10-20Figure 10-20. View VNN OSPF Area Aggregate Dialog Box ..........................10-21Figure 10-21. VNN Virtual Links Node.............................................................10-22Figure 10-22. View VNN OSPF Virtual Link Dialog Box ................................10-22Figure 10-23. VNN External Route Aggregation Node .....................................10-23Figure 10-24. View VNN External Route Aggregation Dialog Box .................10-23

xxx10/7/05 Switch Diagnostics User’s Guide for CBX 3500, CBX 500, GX 550, and B-STDX 9000

Contents


Figure 10-25. PNNI Links Under a Switch ........................................................10-25Figure 11-1. Circuits Node .................................................................................11-2Figure 11-2. Redirect PVCs Node......................................................................11-2Figure 11-3. Offnet Circuits Node......................................................................11-2Figure 11-4. PMP Roots Node ...........................................................................11-3Figure 11-5. PMP Leafs Node............................................................................11-3Figure 11-6. Offnet PMP Roots Node ................................................................11-3Figure 11-7. Offnet PMP Leafs Node ................................................................11-3Figure 11-8. SPVC Node....................................................................................11-3Figure 11-9. View PVC Dialog Box ..................................................................11-6Figure 11-10. Node Prefixes Node.......................................................................11-7Figure 11-11. View SVC Node Prefix Dialog Box ..............................................11-7Figure 11-12. Port Prefixes Node .........................................................................11-8Figure 11-13. View SVC Port Prefix Dialog Box ................................................11-9Figure 11-14. Port Addresses Node......................................................................11-9Figure 11-15. View SVC Port Address Dialog Box...........................................11-10Figure 11-16. User Parts Node ...........................................................................11-11Figure 11-17. View User Part Dialog Box .........................................................11-11Figure 11-18. Network IDs Node .......................................................................11-12Figure 11-19. View Network ID Dialog Box .....................................................11-12Figure 11-20. Active SVCs Node.......................................................................11-13Figure 11-21. Active SVC in Details Panel........................................................11-14Figure 11-22. Active SVC Detailed Call Attributes Dialog Box .......................11-14Figure 11-23. Show ILMI Address List Dialog Box..........................................11-19Figure 11-24. Failed SVCs Node .......................................................................11-20Figure 11-25. Failed SVC in Details Panel ........................................................11-21Figure 11-26. Detailed Failed SVC Attributes Dialog Box ...............................11-21Figure 11-27. CUGs Node..................................................................................11-26Figure 11-28. View CUG Dialog Box................................................................11-27Figure 11-29. CUG Members Node ...................................................................11-28Figure 11-30. View CUG Member Dialog Box .................................................11-28Figure 11-31. Security Screens Node .................................................................11-29Figure 11-32. View Security Screen Dialog Box...............................................11-29Figure 12-1. PVC Operational Information Dialog Box ....................................12-3Figure 12-2. PWE3 PVC Operational Information Dialog Box.......................12-15Figure 12-3. View PWE3 Profile Operational Information Dialog Box..........12-17Figure 12-4. View Enhanced Connection Trace Info Dialog Box ...................12-19Figure 12-5. Modify PVC: Administrative Tab ...............................................12-23Figure 12-6. Modify Logical Port: Administrative Tab ...................................12-25Figure 12-7. View Path Trace Information Dialog Box (for a Circuit)............12-27Figure 12-8. View Path Trace Information Dialog Box (for a Logical Port) ...12-30Figure 12-9. PVC Monitor Node......................................................................12-34Figure 12-10. Circuit Statistics Monitoring Dialog Box ....................................12-35Figure 12-11. 2-port ULC Gigabit Ethernet LPort Circuit Statistics

Monitoring Dialog Box, ATM to Ethernet (Part 1) .....................12-43Figure 12-12. 2-port ULC Gigabit Ethernet LPort Circuit Statistics

Monitoring Dialog Box, ATM to Ethernet (Part 2) .....................12-44Figure 12-13. Modify Logical Port: NTM Tab ..................................................12-55

Contents

Switch Diagnostics User’s Guide for CBX 3500, CBX 500, GX 550, and B-STDX 9000 10/7/05xxxi


Figure 12-14. NTM Statistics in the LPort Statistics Monitoring Dialog Box...12-57Figure 12-15. NDC Statistics in the LPort Statistics Monitoring Dialog Box ...12-58Figure 12-16. Modify PVC Dialog Box: NDC Tab ...........................................12-60Figure 12-17. Add Point-to-Multipoint PVC Root: NDC Tab...........................12-62Figure 12-18. SVC Monitor Node......................................................................12-65Figure 12-19. SVC Statistics Monitoring Dialog Box .......................................12-66Figure 12-20. Set All CAC Parameters Dialog Box...........................................12-68Figure 12-21. OAM Loopback Process From UNI/NNI Interface.....................12-71Figure 12-22. OAM Loopback Process Through Lucent Network....................12-71Figure 12-23. View Menu ..................................................................................12-72Figure 12-24. Preferences Dialog Box ...............................................................12-72Figure 12-25. PVC OAM Loopback Dialog Box...............................................12-73Figure 12-26. View Offnet Circuit Dialog Box (Administrative Tab)...............12-76Figure 12-27. PVC OAM Loopback Dialog Box...............................................12-78Figure 12-28. Offnet OAM Loopback Dialog Box (SPVC) ..............................12-79Figure 12-29. SVC Diagnostics Dialog Box ......................................................12-80Figure 12-30. TAP VCs Node ............................................................................12-83Figure 12-31. Add TAP VC Identifiers Dialog Box ..........................................12-83Figure 12-32. TAP VCs Node Expanded ...........................................................12-85Figure 12-33. Connect TAP-VC ID Monitor Resources Dialog Box ................12-85Figure 12-34. TAP VCs Node Expanded ...........................................................12-86Figure 12-35. TAP VC ID Resource Info Dialog Box .......................................12-87Figure 12-36. TAP VC Monitor Node ...............................................................12-88Figure 12-37. TAP VC Statistics Monitoring Dialog Box .................................12-89Figure 12-38. TAP VCs Node Expanded ...........................................................12-90Figure 12-39. Modify TAP VC ID Identifiers Dialog Box ................................12-90Figure 12-40. TAP VCs Node Expanded ...........................................................12-91Figure 12-41. ATAF SDC Logging Dialog Box: SDC Logging Tab ................12-92Figure 12-42. ATAF SDC Logging Dialog Box: View SDC Log Tab..............12-94Figure 13-1. PVC Operational Information Dialog Box ....................................13-2Figure 13-2. PVC Monitor Node......................................................................13-11Figure 13-3. Circuit Statistics Monitoring Dialog Box ....................................13-12Figure 13-4. 2-port ULC Gigabit Ethernet LPort Circuit Statistics

Monitoring Dialog Box, Ethernet to Frame Relay (Part 1) .........13-16Figure 13-5. 2-port ULC Gigabit Ethernet LPort Circuit Statistics

Monitoring Dialog Box, Ethernet to Frame Relay (Part 2) .........13-17Figure 13-6. Set All CAC Parameters Dialog Box...........................................13-25Figure 13-7. SVC Monitor Node......................................................................13-26Figure 13-8. SVC Statistics Monitoring Dialog Box

(Frame Relay Endpoint 2) ...........................................................13-27Figure 13-9. PVC Endpoint A Set to Local, Endpoint B Set to None .............13-31Figure 13-10. PVC Endpoint A Set to None, Endpoint B Set to Local .............13-31Figure 13-11. PVC Endpoint A Set to Remote, Endpoint B Set to None ..........13-31Figure 13-12. PVC Endpoint A Set to None, Endpoint B Set to Remote ..........13-32Figure 13-13. Modify PVC Dialog Box: User Preference Tab ..........................13-33Figure 13-14. View PVC Dialog Box: User Preference Tab .............................13-35Figure 13-15. Administrative Domain: Single Lucent Network ........................13-37Figure 13-16. Administrative Domain: Multiple Lucent Networks ...................13-38

xxxii10/7/05 Switch Diagnostics User’s Guide for CBX 3500, CBX 500, GX 550, and B-STDX 9000

Contents


Figure 13-17. Administrative Domain: Lucent and Non-Lucent Network ........13-38Figure 13-18. Modify Logical Port, FRF.19 Tab ...............................................13-41Figure 13-19. FR OAM Dialog Box: Enable FROAM Tab...............................13-44Figure 13-20. FR OAM Dialog Box: Near End Tab ..........................................13-45Figure 13-21. FR OAM Dialog Box: Far End Tab ............................................13-46Figure 13-22. Modify Logical Port: FRF.19 Tab ...............................................13-48Figure 14-1. Selecting Alarms from Navis EMS-CBGX...................................14-2Figure 14-2. Alarm Indicator Window...............................................................14-2Figure 14-3. Alarm Browser Window................................................................14-4Figure 14-4. Alarm Browser Window Actions Menu ........................................14-6Figure 14-5. Alarm BrowserWindow View Menu.............................................14-6Figure 14-6. Alarm Filter Configuration Window .............................................14-8Figure 14-7. Set Alarm Count Window ...........................................................14-11Figure 14-8. Alarm Details Window................................................................14-15Figure 14-9. Alarm Sorting Configuration Window ........................................14-17Figure 14-10. Event Configuration Window......................................................14-22Figure 14-11. Modify Switch Alarm Window ...................................................14-23Figure 14-12. Clear Alarm Relay Window ........................................................14-24Figure 15-1. Event Log Structure.......................................................................15-3Figure 15-2. Modify Switch Dialog Box..........................................................15-17Figure 15-3. Sample Configuration Manager Output.......................................15-28Figure 15-4. Sample Redundancy Manager Output .........................................15-29Figure 16-1. Server Details Dialog Box .............................................................16-9Figure 16-2. Modify the Switch Crash Configuration Dialog Box ..................16-10Figure 16-3. Modify Card Crash Dump Dialog Box........................................16-15Figure 16-4. Crash Regions Node ....................................................................16-19Figure 16-5. On Switch Crash Dump Regions Dialog Box .............................16-19Figure 16-6. Crash Regions Node ....................................................................16-20Figure 16-7. Add Card Crash Dump Region....................................................16-21Figure 16-8. Crash Regions Node Expanded ...................................................16-22Figure 16-9. View Card Crash Dump Region ..................................................16-23Figure 16-10. Crash Regions Node Expanded ...................................................16-24Figure 16-11. Crash Regions Node ....................................................................16-24Figure 16-12. Available Regions on Card Dialog Box ......................................16-25Figure 16-13. Live Upload Dialog Box..............................................................16-25Figure 17-1. View Switch: Switch Control Tab.................................................17-6Figure 17-2. View Card Operational Information Dialog Box (IOM)...............17-7Figure 17-3. Reliability Features Dialog Box ..................................................17-14Figure 17-4. PRAM Consistency Test Dialog Box ..........................................17-15Figure 17-5. Reliability Features Dialog Box ..................................................17-19Figure 17-6. Reliability Features: Standby CPIO Dialog Box .........................17-19Figure 17-7. Reliability Features Dialog Box ..................................................17-20Figure 17-8. Reliability Features: Standby SF Dialog Box..............................17-21Figure 18-1. SNMP MIB Tree Hierarchy...........................................................18-5Figure 18-2. MIB Browser Window ..................................................................18-7Figure C-1. Transit ATM Network .................................................................... C-7Figure C-2. Two CBX 500 Networks (Direct or OPTimum Trunk).................. C-9

Contents

Switch Diagnostics User’s Guide for CBX 3500, CBX 500, GX 550, and B-STDX 9000 10/7/05xxxiii


List of Tables

Table 1-1. Commands Used to Generate Network Reports ..............................1-5Table 2-1. Network Map Status Colors.............................................................2-8Table 2-2. Switch Operational Information Dialog Box.................................2-10Table 2-3. PNNI Node Operational Information ............................................2-16Table 2-4. PNNI Node Signalling Statistics ...................................................2-17Table 2-5. Redundant Group Operational Information...................................2-22Table 2-6. LDP Entity Operational Information .............................................2-24Table 2-7. LDP Statistics ................................................................................2-25Table 2-8. MPLS Tunnel Operational Information.........................................2-31Table 2-9. Tunnel Monitor Configuration Dialog Box Field

Descriptions ...................................................................................2-32Table 2-10. MPLS Tunnel Statistics .................................................................2-34Table 2-11. Layer 2 Tunnel Operational Information.......................................2-36Table 2-12. Layer 2 Tunnel Statistics ...............................................................2-37Table 2-13. Module Colors ...............................................................................2-48Table 2-14. Physical Port Colors ......................................................................2-48Table 2-15. External Power Status Indicator Colors.........................................2-49Table 2-16. Alarm Status Indicator Colors .......................................................2-49Table 2-17. Switch Status Indicator Colors ......................................................2-49Table 2-18. Module Status Indicator Colors .....................................................2-50Table 2-19. Stby and Redundancy Status Indicator Colors ..............................2-50Table 2-20. Fan Module and Power Supply Colors ..........................................2-51Table 2-21. MID Status Colors .........................................................................2-51Table 2-22. Console Window Elements............................................................2-53Table 2-23. View Card Operational Information: General Tab

(processor modules).......................................................................2-59Table 2-24. View Card Operational Information: Hardware Tab

(processor modules).......................................................................2-60Table 2-25. View Card Operational Information: Software Tab

(processor modules).......................................................................2-60Table 2-26. View Card Operational Information: Mesh Status Tab

(SP90 on CBX 3500 only) .............................................................2-61Table 2-27. View Card Operational Information: Node Processor Tab

(NP on GX 550 only).....................................................................2-62Table 2-28. View Card Operational Information: General Tab

(IOM or BIO).................................................................................2-67Table 2-29. View Card Operational Information: Hardware Tab

(IOM or BIO).................................................................................2-69Table 2-30. View Card Operational Information: Software Tab

(IOM or BIO).................................................................................2-69Table 2-31. View Card Operational Information: Mesh Status Tab

(IOM on CBX 3500 only)..............................................................2-70Table 2-32. View SubCard Operational Information: General Tab..................2-71Table 2-33. View SubCard Operational Information: Hardware Tab...............2-72

xxxiv10/7/05 Switch Diagnostics User’s Guide for CBX 3500, CBX 500, GX 550, and B-STDX 9000

Contents


Table 2-34. View SubCard Operational Information: Software Tab ................2-72Table 2-35. 32-port Channelized T1/E1 Module Statistics...............................2-73Table 2-36. View PPort Operational Status Dialog Box...................................2-82Table 2-37. View Channel Operational Status Dialog Box (DS1) ...................2-89Table 2-38. DS0 Allocation Dialog Box...........................................................2-90Table 2-39. View PPort Operational Status Dialog Box (E1 Channel) ............2-93Table 2-40. IMA Group Operational Info Dialog Box .....................................2-96Table 2-41. IMA Link OperInfo Dialog Box Fields .......................................2-100Table 2-42. Traffic Shaper Fields ...................................................................2-103Table 2-43. VP Shaping ..................................................................................2-106Table 3-1. Physical Port Summary Statistics ....................................................3-3Table 3-2. DS3 ATM/CE Port AAL1 Statistics................................................3-4Table 3-3. DS1 Channel Alarm States ..............................................................3-6Table 3-4. DS1 Channel Summary Statistics ....................................................3-7Table 3-5. E1 Channel Summary Statistics.......................................................3-9Table 3-6. G.826 Statistics ..............................................................................3-10Table 3-7. E1 Configuration Statistics (RFC 1406 and G.826) ......................3-12Table 3-8. E1 Current Statistics (RFC 1406) ..................................................3-13Table 3-9. E1 Current Statistics (G.826).........................................................3-15Table 3-10. E1 Interval Statistics (RFC 1406)..................................................3-15Table 3-11. E1 Interval Statistics (G.826) ........................................................3-16Table 3-12. E1 Total Statistics (RFC 1406)......................................................3-17Table 3-13. E1 Total Statistics (G.826) ............................................................3-18Table 3-14. 2-port ULC Gigabit Ethernet Module PPort Statistics

Monitoring Summary Statistics .....................................................3-19Table 3-15. IMA Group Summary Statistics ....................................................3-24Table 3-16. IMA Link Summary Statistics .......................................................3-25Table 4-1. Performance Monitoring Fields Statistics Dialog Box

Informational Fields (OC-n/STM-n) ...............................................4-6Table 4-2. Performance Monitoring Statistics Dialog Box Fields

(OC-n/STM-n) .................................................................................4-6Table 4-3. DS3/E3 Statistics Configuration Dialog Box Fields .....................4-12Table 4-4. Performance Monitoring Statistics Dialog Box Informational

Fields (DS3/E3) .............................................................................4-14Table 4-5. Performance Monitoring Statistics Dialog

Box Fields (DS3/E3)......................................................................4-15Table 4-6. DS3/E3 Statistics Configuration Dialog Box Fields .....................4-18Table 4-7. DS3/E3 Configuration Line Status Dialog Box Fields..................4-22Table 4-8. DS3/E3 Configuration PLCP Status Dialog Box Fields................4-23Table 4-9. DS3/E3 Configuration TC Status Dialog Box Fields ....................4-24Table 4-10. Performance Monitoring Statistics Dialog Box (T1/E1) ..............4-26Table 4-11. Performance Monitoring Statistics Dialog Box (T1/E1) ..............4-26Table 4-12. Performance Monitoring Statistics Dialog Box Informational

Fields (DS1 Channel) ....................................................................4-30Table 4-13. Performance Monitoring Statistics Dialog Box Fields

(DS1 Channel) ...............................................................................4-30Table 4-14. Performance Monitoring Statistics Dialog Box Informational

Fields (E1 Channel) .......................................................................4-35

Contents

Switch Diagnostics User’s Guide for CBX 3500, CBX 500, GX 550, and B-STDX 9000 10/7/05xxxv


Table 4-15. Performance Monitoring Statistics Dialog Box Fields (E1 Channel) ..................................................................................4-35

Table 4-16. Performance Monitoring Statistics Dialog Box InformationalFields (IMA Group).......................................................................4-39

Table 4-17. Performance Monitoring Statistics Dialog Box Fields(IMA Group)..................................................................................4-39

Table 4-18. Performance Monitoring Statistics Dialog Box InformationalFields (IMA Link)..........................................................................4-41

Table 4-19. Performance Monitoring Statistics Dialog Box Fields (IMA Link) ....................................................................................4-41

Table 5-1. Card Diagnostics Dialog Box Fields ...............................................5-4Table 5-2. IMA Group Diagnostics Dialog Box Fields ..................................5-17Table 5-3. IMA Group Diagnostics Dialog Box Results ................................5-18Table 5-4. DS3/E3 Loopback Tests ................................................................5-24Table 5-5. HSSI Loopback Tests ....................................................................5-26Table 5-6. OC-n/STM-n Loopback Tests .......................................................5-28Table 5-7. T1/E1 Loopback Tests ...................................................................5-30Table 5-8. T1 Loopback Tests (32-Port and 60-Port modules) ......................5-35Table 5-9. DS1 Far-End Loopback Tests (32-Port and 60-Port modules)......5-36Table 5-10. E1 Loopback Tests (32-Port and 60-Port modules) ......................5-39Table 5-11. DS1 Near-End Loopback Tests .....................................................5-41Table 5-12. Far-End Loopback Tests................................................................5-44Table 5-13. DS0 Channel Selection Buttons.....................................................5-51Table 5-14. Diagnostics Dialog Box Configure Test Fields .............................5-54Table 5-15. Diagnostics Dialog Box Results Fields .........................................5-55Table 5-16. Layer 2 Tunnel OAM ....................................................................5-56Table 5-17. Physical Port (E1 Structured and Unstructured & T1

Structured) BERT Patterns ............................................................5-58Table 5-18. Physical Port (T1 Unstructured) BERT Patterns ...........................5-59Table 5-19. PPort Diagnostics Dialog Box Configure

Test Fields......................................................................................5-60Table 5-20. PPort Diagnostics Dialog Box BERT Results

Fields (T1/E1)................................................................................5-61Table 5-21. Physical Port (Subrate DS3) Bert Patterns ....................................5-63Table 5-22. PPort Diagnostics Dialog Box Configure Test Fields (DS3) ........5-65Table 5-23. PPort Diagnostics Dialog Box BERT Results Fields (DS3) .........5-65Table 5-24. Bert Test Patterns for Universal Modules Physical Ports..............5-66Table 5-25. Universal DS3 or POS IOM BERT Test Parameters ....................5-68Table 5-26. DS3 BERT Results ........................................................................5-69Table 5-27. DS1 Channel BERT Patterns.........................................................5-70Table 5-28. Channel Diagnostics Dialog Box Configure Test Fields (DS1)....5-72Table 5-29. Channel diagnostics Dialog Box BERT Results Fields (DS1)......5-72Table 5-30. E1 Channel BERT Patterns ...........................................................5-74Table 5-31. Channel Diagnostics Dialog Box Configure Test Fields (E1).......5-75Table 5-32. Channel Diagnostics Dialog Box BERT Results Fields (E1)........5-76Table 5-33. DS0 Channel BERT Patterns ........................................................5-77Table 5-34. DS0 BERT Test Parameters ..........................................................5-79Table 5-35. Diagnostics Dialog Box BERT Results Field (DS0) .....................5-80

xxxvi10/7/05 Switch Diagnostics User’s Guide for CBX 3500, CBX 500, GX 550, and B-STDX 9000

Contents


Table 5-36. Logical Port BERT Patterns ..........................................................5-83Table 5-37. Diagnostics Dialog Box Configure Test Fields

(Logical Port).................................................................................5-84Table 5-38. Diagnostics Dialog Box BERT Results Fields

(Logical Port).................................................................................5-85Table 5-39. Failure Indicators and Recommendations .....................................5-87Table 6-1. Service-specific Logical Port Attributes..........................................6-7Table 6-2. View Logical QoS Parameters Attributes......................................6-12Table 6-3. View LPort SVC QoS Parameters Attributes ................................6-16Table 7-1. View LPort Operational Status Dialog Box Fields (ATM) .............7-2Table 7-2. PNNI Hello Finite State Machine States .........................................7-4Table 7-3. View LPort Operational Status Dialog Box Elements ....................7-7Table 7-4. Statistics Categories for ATM Logical Ports...................................7-8Table 7-5. General Statistics (ATM logical port) .............................................7-9Table 7-6. General Statistics (CE logical port on 60-Port Channelized

T1/E1 CE Module) ........................................................................7-10Table 7-7. Q.2931 Statistics (ATM Logical Port)...........................................7-11Table 7-8. SAAL Statistics (ATM Logical Port) ............................................7-14Table 7-9. ILMI Statistics (ATM logical port) ...............................................7-15Table 7-10. PNNI Statistics (ATM logical port)...............................................7-15Table 7-11. Trunk Signalng and Node to Node (Control Channel) Statistics

(ATM Direct and OPTimum Trunk Logical Ports) .......................7-16Table 7-12. 2-port ULC Gigabit Ethernet Logical Port Statistics

Monitoring .....................................................................................7-18Table 7-13. 2-port ULC Gigabit Ethernet Logical Port Shaper Statistics

Monitoring .....................................................................................7-20Table 7-14. 2-port ULC Gigabit Ethernet Logical Port VLAN Profile

Statistics Monitoring......................................................................7-21Table 7-15. NNI Node Signalling Statistics for LPort ......................................7-23Table 8-1. View LPort Operational Status Dialog Box Fields

(Frame Relay non-MLFR) ...............................................................8-3Table 8-2. View LPort Operational Status Dialog Box Fields (MLFR) ...........8-5Table 8-3. Statistics Categories for Frame Relay Logical Ports .......................8-7Table 8-4. General Statistics (Frame Relay Logical Port) ................................8-8Table 8-5. Q.933 Statistics (Frame Relay Logical Port) .................................8-11Table 8-6. Q.922 Statistics (Frame Relay Logical Port) .................................8-12Table 9-1. IP Objects.........................................................................................9-2Table 9-2. BGP Operational Information Dialog Box ....................................9-12Table 9-3. View Point-to-Point LSP Connection Operational

Information Fields .........................................................................9-13Table 9-4. Point-to-Point LSP Connection Failure Reasons...........................9-14Table 9-5. OSPF Operational Status Dialog Box Elements............................9-17Table 9-6. RIP Statistics..................................................................................9-18Table 9-7. IP LPort Statistics ..........................................................................9-19Table 9-8. IP LPort RSVP-TE Statistics .........................................................9-22Table 9-9. Point to Point LSP Statistics ..........................................................9-23Table 9-10. BGP Peer Statistics ........................................................................9-25Table 9-11. BGP Error Codes ...........................................................................9-27

Contents

Switch Diagnostics User’s Guide for CBX 3500, CBX 500, GX 550, and B-STDX 9000 10/7/05xxxvii


Table 9-12. Fast Ethernet Logical Port Monitoring Statistics...........................9-29Table 10-1. View Trunk Operational Information Dialog Box Fields..............10-6Table 10-2. Trunk Color Status Indicators........................................................10-9Table 10-3. Trunk Summary Statistics............................................................10-11Table 10-4. Show All PVCs on Trunk Dialog Box Fields..............................10-12Table 10-5. Trunk OAM Dialog Box Fields ...................................................10-14Table 10-6. Trunk OAM Dialog Box Loopback Test Results ........................10-14Table 10-7. View Customer Dialog Box Fields..............................................10-17Table 10-8. View VPN Dialog Box Fields .....................................................10-18Table 10-9. View VNN Loopback Address Dialog Box Fields......................10-20Table 10-10. View VNN OSPF Area Aggregate Dialog Box Fields................10-21Table 10-11. View VNN OSPF Virtual Link Dialog Box Fields .....................10-22Table 10-12. View VNN External Route Aggregation Dialog Box Fields.......10-24Table 11-1. Circuit Attributes Categories .........................................................11-4Table 11-2. Active SVC Detailed Call Attributes: Destination Tab Fields ....11-15Table 11-3. Active SVC Detailed Call Attributes: Bearer Capability,

QoS Parameters, Traffic Parameters, ABR, and AINI Tabs .......11-16Table 11-4. Show ILMI Address List Dialog Box Fields ...............................11-19Table 11-5. Detailed Failed SVC Attributes: Failure Info Tab Fields ............11-22Table 11-6. Detailed Failed SVC Attributes: Bearer Capability,

QoS Parameters, Traffic Parameters, ABR, and AINI Tabs .......11-23Table 12-1. PVC Operational Information Dialog Box Fields .........................12-3Table 12-2. Redirect PVC Operational Information Dialog Box Fields...........12-5Table 12-3. View Offnet Circuit Operational Information Dialog

Box Fields ......................................................................................12-7Table 12-4. PMP Leaf Operational Information Dialog Box Fields.................12-8Table 12-5. Offnet Leaf Operational Information Dialog Box Fields ..............12-9Table 12-6. View SPVC Operational Information Fields .................................12-9Table 12-7. View PMP SPVC Leaf Operational Information Dialog

Box Fields ....................................................................................12-10Table 12-8. Inactive PVC Operational Information Codes.............................12-11Table 12-9. PWE3 PVC Operational Information Dialog Box Fields............12-16Table 12-10. View PWE3 Profile Operational Information Dialog Box

Fields............................................................................................12-17Table 12-11. Differences Between Path Trace and Connection Trace .............12-21Table 12-12. Modify PVC: Administrative Tab Path Trace Fields ..................12-23Table 12-13. Modify Logical Port: Administrative Tab Path Trace Fields ......12-25Table 12-14. View Path Trace Information Dialog Box Fields

(for a Circuit) ...............................................................................12-27Table 12-15. View Path Trace Information Dialog Box Fields

(for a Logical Port) ......................................................................12-30Table 12-16. Circuit Statistics Monitoring Dialog Box Fields (ATM).............12-35Table 12-17. Circuit Statistics Monitoring Dialog Box Fields (ATM).............12-38Table 12-18. Circuit Statistics Monitoring Dialog Box Fields

for ATM PMP PVC and Offnet Circuit Leaves ..........................12-39Table 12-19. 2-port ULC Gigabit Ethernet LPort Circuit Statistics

Monitoring, ATM to Ethernet......................................................12-44Table 12-20. Modify Logical Port: NTM Tab Fields .......................................12-55

xxxviii10/7/05 Switch Diagnostics User’s Guide for CBX 3500, CBX 500, GX 550, and B-STDX 9000

Contents


Table 12-21. View Logical Port: NTM Tab Fields...........................................12-56Table 12-22. NTM Logical Port Statistics ........................................................12-57Table 12-23. NDC Logical Port Statistics.........................................................12-58Table 12-24. Modify PVC Dialog Box: NDC Tab Fields ................................12-60Table 12-25. Add Point-to-Multipoint PVC Root Dialog Box: NDC Tab .......12-62Table 12-26. View PVC Dialog Box: NDC Tab Fields....................................12-63Table 12-27. SVC Statistics Monitoring Dialog Box Fields (ATM) ................12-66Table 12-28. PVC OAM Loopback Dialog Box Fields ....................................12-73Table 12-29. PVC OAM Loopback Dialog Box Test Results ..........................12-75Table 12-30. Supported Modules ......................................................................12-81Table 12-31. Add TAP VC Identifiers Dialog Box Fields...............................12-84Table 12-32. TAP VC ID Resource Info Dialog Box Fields ............................12-87Table 12-33. Modify TAP VC Identifiers Dialog Box Fields ..........................12-90Table 12-34. SDC Logging Tab Dialog Box Fields and Buttons .....................12-92Table 13-1. PVC Operational Information Dialog Box Fields .........................13-3Table 13-2. Redirect PVC Operational Information Dialog Box Fields...........13-4Table 13-3. View Offnet Circuit Operational Information

Dialog Box Fields ..........................................................................13-6Table 13-4. Inactive PVC Operational Information Codes...............................13-6Table 13-5. Circuit Statistics Monitoring Dialog Box Fields

(Frame Relay) ..............................................................................13-12Table 13-6. 2-port ULC Gigabit Ethernet LPort Circuit Statistics

Monitoring, Ethernet to Frame Relay..........................................13-17Table 13-7. SVC Statistics Monitoring Dialog Box Fields (Frame Relay) ....13-27Table 13-8. Valid PVC Loopback Combinations ...........................................13-34Table 13-9. Modify Logical Port: FRF.19 Tab Fields ....................................13-41Table 13-10. FR OAM: Enable FROAM Tab Fields........................................13-44Table 13-11. FR OAM: Near End Tab Fields...................................................13-45Table 13-12. FR OAM: Far End Tab ................................................................13-46Table 13-13. Frame Relay OAM Test Results..................................................13-47Table 14-1. Color Scheme in Alarm Indicator Window...................................14-3Table 14-2. Alarm Indicator Window Buttons .................................................14-4Table 14-3. Alarm Browser Window Columns ................................................14-5Table 14-4. Alarm Filter Configuration Window Settings ...............................14-8Table 14-5. Set Refresh Rate ..........................................................................14-12Table 14-6. Alarm Details Window ................................................................14-15Table 14-7. Alarm Sorting Configuration Window Settings ..........................14-17Table 14-8. Set Alarm Severity Commands ...................................................14-18Table 14-9. Switch Trap Configuration Attributes .........................................14-24Table 14-10. Clear Alarm Relay Conditions.....................................................14-25Table 15-1. Event Log Server Output ...............................................................15-4Table 15-2. Application Acronyms...................................................................15-4Table 15-3. Importance Level Settings ...........................................................15-15Table 15-4. Modify Switch: Event Log Tab Fields ........................................15-17Table 15-5. Log Filter Arguments ..................................................................15-23Table 15-6. Arguments for set evtrace filter Command .................................15-24Table 15-7. Event Log Help Commands.........................................................15-26Table 15-8. Syslog Help Commands ..............................................................15-29

Contents

Switch Diagnostics User’s Guide for CBX 3500, CBX 500, GX 550, and B-STDX 9000 10/7/05xxxix


Table 16-1. Modify the Switch Crash Configuration Dialog Box,Display-Only Fields.....................................................................16-11

Table 16-2. Modify the Switch Crash Configuration Dialog Box Fields .......16-12Table 16-3. Crash Dump File Fields ...............................................................16-13Table 16-4. Modify Card Crash Dump Dialog Box, Display-Only Fields .....16-16Table 16-5. Modify Card Crash Dump Dialog Box Field ..............................16-17Table 16-6. On Switch Crash Dump Regions Dialog Box Fields...................16-19Table 16-7. Add Card Crash Dump Region Dialog Box Fields .....................16-21Table 16-8. View Card Crash Dump Region Dialog Box Fields....................16-23Table 16-9. Available Regions on Card Dialog Box Fields............................16-25Table 17-1. Path Integrity Console Commands ................................................17-8Table 17-2. Path Integrity Switch Example ......................................................17-9Table 17-3. Path Integrity Event Logger Messages ........................................17-11Table 17-4. PRAM Consistency Event Log Messages ...................................17-16Table 17-5. PRAM Consistency Console Commands ....................................17-17Table 17-6. ESHW Test Console Commands.................................................17-22Table 18-1. Lucent MIB....................................................................................18-4Table 18-2. cascfr Group...................................................................................18-6Table 1-1. PM TCA IDs and Corresponding Thresholds ................................A-8Table 1-2. PVC Establishment Failure Reason Variables .............................A-16Table 1-3. PVC Fail Reason Variable Values................................................A-18Table 1-4. Frame Relay SVC Fail Reason Variable Values ..........................A-23Table 1-5. IMA Alarm Type Conditions........................................................A-25Table 1-6. Alarm Types .................................................................................A-31Table 1-7. RLMI Service Name Binding Operational States ........................A-35Table 1-8. Warm Boot Upgrade Fail Reason Variables ................................A-36Table 1-9. RLMI Logical Port Operational States .........................................A-50Table B-1. Summary of Error Codes for Background Diagnostics .................. B-2Table B-2. Summary of Miscellaneous Fatal Error Codes ............................. B-15Table C-1. SVC Setup Failure Causes.............................................................. C-2Table C-2. SVC Failure Location Information for Sample Transit Network... C-8Table C-3. SVC Failure Location Information for All CBX 500 Scenarios .... C-9Table D-1. Allowable Combinations of Traffic Related Parameters in

the SETUP Message (ATM UNI 3.0/3.1 and Q.2931)...................D-9Table D-2. CBX 500/CBX 3500/GX 550 ATM UNI Service Category

Mappings Based on Signalled QoS/BBC and BEI .......................D-11Table D-3. Derivation of ATM Service Categories From Signalling

Information (ATM UNI 4.0 and PNNI 1.0) .................................D-16Table D-4. Allowable Combinations of Traffic and QoS Parameters

in the SETUP Message (ATM UNI 4.0 and PNNI 1.0) ...............D-19

xl10/7/05 Switch Diagnostics User’s Guide for CBX 3500, CBX 500, GX 550, and B-STDX 9000

Contents


Switch Diagnostics User’s Guide for CBX 3500, CBX 500, GX 550, and B-STDX 9000 xli


About This Guide

The Switch Diagnostics User’s Guide for CBX 3500, CBX 500, GX 550, and B-STDX 9000 describes how to monitor activity and events on a Lucent switch network.

This guide supports the following Network Management Station (NMS) and switch software releases:

• Navis EMS-CBGX, Release 10.00.01.00 or greater

• CBX 3500 Multiservice Edge switch software Release 10.00.01.00 or greater

• CBX 500 Multiservice WAN switch software Release 10.00.01.00 or greater

• GX 550 Multiservice WAN switch software Release 10.00.01.00 or greater

• Prior supported releases of B-STDX 9000 Multiservice WAN switch software as noted in the Interoperability section of the Navis EMS-CBGX Software Release Notice (SRN).


xlii6/15/04 Switch Diagnostics User’s Guide for CBX 3500, CBX 500, GX 550, and B-STDX 9000

About This GuideWhat You Need to Know

What You Need to Know

As a reader of this guide, you should be familiar with UNIX and Navis EMS-CBGX.

This guide is written for system administrators who are responsible for monitoring the network and diagnosing network problems. This guide assumes that you have experience in managing Lucent switches and the NMS, and have already performed the following tasks:

• Installed Lucent switch hardware, NMS, and switch software

• Configured Input/Output Module (IOM) attributes and physical ports on your switch

See “Related Documents” on page li for a list of documents that describe these and other tasks.

Be sure to read the Software Release Notice (SRN) that accompanies this product. The SRN contains the most current product information and requirements.

Beta Draft Confidential About This GuideReading Path

Switch Diagnostics User’s Guide for CBX 3500, CBX 500, GX 550, and B-STDX 9000 6/15/04xliii

Reading Path

This section describes all of the documents that support the Navis EMS-CBGX and switch software.

Read the following documents to install and operate Navis EMS-CBGX Release 10.00.01.00 or greater and the associated switch software. Be sure to review the accompanying SRNs for any changes not included in these guides.

These guides describe how to install and set up the switch hardware, replace hardware modules, and interpret LED indicators.

This guide describes prerequisite tasks, hardware and software requirements, and instructions for installing and upgrading Solaris and Navis EMS-CBGX on the NMS.

Switch Hardware Installation Guides

Installation and Administration Guide

This guide describes how to start the Navis EMS-CBGX client on Windows and Solaris. It also provides a description of the Navis EMS-CBGX window components, how to access network and map configuration options, how to configure and manage Lucent switches and instructions for customizing Navis EMS-CBGX. Navis EMS-CBGX

Getting Started Guide


xliv6/15/04 Switch Diagnostics User’s Guide for CBX 3500, CBX 500, GX 550, and B-STDX 9000

About This GuideReading Path

This guide describes procedures for upgrading a Lucent switch to the current release.

This guide describes how to monitor and diagnose problems in your Navis EMS-CBGX switch network.

The following guides describe how to configure wide area network (WAN) services on the supported switch platforms:

• Frame Relay Services Configuration Guide for CBX 3500, CBX 500, and B-STDX 9000

• ATM Services Configuration Guide for CBX 3500, CBX 500, GX 550, and B-STDX 9000

• IP Services Configuration Guide for CBX 3500, CBX 500, and B-STDX 9000

This guide describes the processor and IOMs on each switch platform, and how to configure physical ports, timing, and other attributes through Navis EMS-CBGX.

Switch Module Configuration Guide

Switch Software Upgrade Guide

Configuration Guides

Diagnostics User’s Guides

Beta Draft Confidential About This GuideHow to Use This Guide

Switch Diagnostics User’s Guide for CBX 3500, CBX 500, GX 550, and B-STDX 9000 6/15/04xlv

How to Use This Guide

This guide contains the following information:

This guide contains reference lists and describes the switch console commands.

Console Command User’s Reference

Read To Learn About

Chapter 1 Using Navis EMS-CBGX to monitor and troubleshoot the network.

Chapter 2 Monitoring hardware details of switches, processor modules, IOMs, and physical ports.

Chapter 3 Monitoring statistics on physical port activity.

Chapter 4 Monitoring performance data on physical port activity.

Chapter 5 Running diagnostic tests and loopback tests on processor modules, IOMs, physical ports, and channels.

Chapter 6 Viewing the configured logical port attributes common to multiple network services.

Chapter 7 Monitoring ATM logical ports.

Chapter 8 Monitoring Frame Relay logical ports.

Chapter 9 Monitoring IP configuration parameters and statistics.

Chapter 10 Monitoring trunk status and statistics.

Chapter 11 Monitoring the configured attributes for circuits.

Chapter 12 Monitoring ATM circuits.

Chapter 13 Monitoring Frame Relay circuits.

Chapter 14 Monitoring alarms to inform you of network events.

Chapter 15 Managing the Event Log.

Chapter 16 Managing the Crash Dump System.


xlvi6/15/04 Switch Diagnostics User’s Guide for CBX 3500, CBX 500, GX 550, and B-STDX 9000

About This GuideWhat’s New in This Guide

What’s New in This Guide

This guide has been updated to include the following features and enhancements:

Chapter 17 Monitoring switch reliability for CBX 500, CBX 3500, and GX 550 switches.

Chapter 18 Monitoring MIB values.

Appendix A Interpreting trap alarm condition messages.

Appendix B Interpreting major and minor error codes that are displayed when you run background diagnostic tests.

Appendix C Understanding SVC failure information.

Appendix D Understanding signalled QoS, BBC, ATC, and BEI service category mappings.

Appendix E Using disk diagnostic utilities.

Read To Learn About

Beta Draft Confidential About This GuideWhat’s New in This Guide

Switch Diagnostics User’s Guide for CBX 3500, CBX 500, GX 550, and B-STDX 9000 6/15/04xlvii

Feature or

Enhancement

Description See...

New Features in This Release

2-port ULC Gigabit Ethernet module for CBX 3500

The 2-Port Gigabit Ethernet module (Universal IOP or Universal line Card and 2-Port Gigabit Ethernet IOA) handles the physical termination of Ethernet frames and allows for the delivery of Ethernet services to the ATM or MPLS core. The Ethernet Interworking services, which are based on the MPLS-FR Alliance Ethernet Interworking Specification, support the following features:

• Ethernet to Ethernet

• Ethernet to ATM

• Ethernet to Frame

Please note that all procedures associated with viewing the logical port attributes and statistics for this feature have been moved from Chapter 9, “Monitoring IP”, to Chapter 7, “Monitoring ATM Logical Ports”.

“Viewing 2-port ULC Gigabit Ethernet Module Physical Port Summary Statistics” on page 3-18

“Viewing Foreground Diagnostics For a Logical Port on the 2-port ULC Gigabit Ethernet Module” on page 5-21

“Viewing 2-port ULC Gigabit Ethernet Logical Port Summary Statistics” on page 7-17

“Viewing 2-port ULC Gigabit Ethernet Logical Port Operational Status” on page 7-6

“Viewing 2-port ULC Gigabit Ethernet LPort Object Summary Statistics” on page 7-17

“Viewing 2-port ULC Gigabit Ethernet LPort Shaper Object Summary Statistics” on page 7-19

“Viewing 2-port ULC Gigabit Ethernet LPort VLAN Profile Summary Statistics” on page 7-20

“Viewing 2-port ULC Gigabit Ethernet LPort Circuit Summary Statistics for Ethernet to ATM Endpoints” on page 12-42

“Viewing 2-port ULC Gigabit Ethernet LPort Circuit Summary Statistics for Ethernet to Frame Relay Endpoints” on page 13-15


xlviii6/15/04 Switch Diagnostics User’s Guide for CBX 3500, CBX 500, GX 550, and B-STDX 9000

About This GuideWhat’s New in This Guide

ATM Test AF (Phase 2)

Further ATAF functionality has been added to this release to enable non-intrusive testing of VCs or VPs. Specific VCs/VPs may be monitored during operation. With this feature, the receive port of the source connection endpoint is cross connected to a test port without impacting the established connection. For simultaneous monitoring of source and destination receive endpoints (in bi-directional VC/VP) two separate test ports are supported. This capability is based on the ATM Forum standard af-test-nm-0094.00 Feb 1998.

However, our implementation will involve ATAF-VC-ATAF and Virtual Connection Access ATAF-SDC-ATAF Signaling Data Captures for Virtual Connection. This feature is supported on the CBX 500, GX 550 and CBX 3500 platforms for all service categories including CBR, VBR-rt, VBR-nrt, ABR, and UBR.

“ATM Test Access Function” on page 12-81

“Creating a TAP-VC Instance on the ATAF Monitoring Logical Port” on page 12-83

“ATAF SDC Logging” on page 12-91

PNNI Statistics Enhancements

This feature adds support for the new PNNI statistics at the node and logical port levels:

“Viewing PNNI Node Signaling Statistics” on page 2-16

32-port Channelized T1/E1 Module Statistics Monitoring

Added support for statistics monitoring at the module level for the 32-port Channelized T1/E1 module.

“Viewing Statistics for the 32-port Channelized T1/E1 Module on CBX 500 and CBX 3500” on page 2-72

Point-to-Point LSP Statistics

Added support for statistics monitoring of IP Point-to-Point LSPs.

“Viewing Point-to-Point LSP Summary Statistics” on page 9-23

Aggregate Interval for Round Trip Delay (RTD)/Cell Loss Statistics (CLS)

Updated PVC OAM Loopback dialog box and table that display the Aggregate Interval field for RTD/CLS.

“Running an OAM Loopback Test on an ATM Circuit” on page 12-73

PWE3 Profile Operational Information

Added dialog box and field description table for PWE3 Profile Operational Information.

“Viewing PWE3 Profile Operational Information” on page 12-16

Logical Port QoS Incoming bandwidth (Reserved)

Added note to clairfy Incoming bandwidth (Reserved) field description for Logical QoS Parameters dialog box.

“Viewing Logical Port QoS Parameters” on page 6-10

Feature or

Enhancement

Description See...

Beta Draft Confidential About This GuideConventions

Switch Diagnostics User’s Guide for CBX 3500, CBX 500, GX 550, and B-STDX 9000 6/15/04xlix

Conventions

This guide uses the following conventions, when applicable:

Enhanced Connection Trace

Updated the View Enhanced Connection Trace Info dialog box and procedure.

“Running Enhanced Connection Trace on a PVC or SVC” on page 12-20

New Features from Previous Release

Listing Circuits on a Trunk

Added Show All PVCs on Trunk dialog box and field descriptions.

“Viewing PVC Usage” on page 10-12

IMA Physical Link Display

Added section on viewing operational status for physical port channels on the 1-port STM-1/E1 IMA Enhanced IOM.

“Viewing Operational Status for Physical Port Channels on the 1-port STM-1/E1 IMA Enhanced IOM” on page 2-83

ATM Round-trip Delay (RTD)/Cell Loss Statistics (CLS)

Added draft section on ATM RTD feature as originally documented in Release 9.1.0 Feature Guide. This section is intended as an introduction to the ATM Cell Loss Statistics (CLS), Phase 2 feature for this release. It has been updated to Navis EMS_CBGX.

“ATM Round-trip Delay/Cell Loss Statistics” on page 12-77

General Enhancements

List updated Updated bulleted list of software releases supported. page -xli

List updated Updated bulleted list of Lucent publications and product codes.

page -li

Extender Shelf Removed all text for GX 550 Extender Shelf support. Throughout Chapters 2 and 6.

Added note Added note to Appendix A, Trap Alarm Condition Messages, that refers user to Lucent TAC for all critical failure messages.

page A-1

Editing changes Editing changes were made throughout this guide. Throughout the guide.

Feature or

Enhancement

Description See...

Convention Indicates Example

Courier Regular System output, filenames, and command names.

Please wait...


l6/15/04 Switch Diagnostics User’s Guide for CBX 3500, CBX 500, GX 550, and B-STDX 9000

About This GuideConventions

<Courier Bold Italics>

Variable text input; user supplies a value.

Enter <cdrompath>/docs/atmcfg.pdf to display...

<Courier Italics> Variable text output. <cdrompath>/docs/atmcfg.pdf

Courier Bold User input. > show ospf names

Menu ⇒ Option A selection from a menu. Set Trap Severity ⇒ Major

Italics Book titles, new terms, and emphasized text.

CBX 3500 Multiservice Edge Switch Hardware Installation Guide

A box around text A note, caution, or warning. See examples below.

Convention Indicates Example

Note – Notes provide additional information or helpful suggestions that may apply to the subject text.

!Caution – Cautions notify the reader to proceed carefully to avoid possible equipment damage or data loss.

Warning – Warnings notify the reader to proceed carefully to avoid possible personal injury.

Beta Draft Confidential About This GuideRelated Documents

Switch Diagnostics User’s Guide for CBX 3500, CBX 500, GX 550, and B-STDX 9000 6/15/04li

Related Documents

This section lists the related Lucent and third-party documentation that may be helpful to read.

Lucent• CBX 3500 Multiservice Edge Switch Hardware Installation Guide

(Product Code: 80253)

• B-STDX 8000/9000 Multiservice WAN Switch Hardware Installation Guide(Product Code: 80005)

• CBX 500 Multiservice WAN Switch Hardware Installation Guide (Product Code: 80011)

• GX 550 Multiservice WAN Switch Hardware Installation Guide (Product Code: 80077)

• Navis EMS-CBGX Release 10.00.01.00 Getting Started Guide (Product Code: 86019)

• Switch Module Configuration Guide for CBX 3500, CBX 500, GX 550, and B-STDX 9000 (Product Code: 80263)

• Frame Relay Services Configuration Guide for CBX 3500, CBX 500, andB-STDX 9000 (Product Code: 86020)

• ATM Services Configuration Guide for CBX 3500, CBX 500, GX 550, and B-STDX 9000 (Product Code: 80260)

• IP Services Configuration Guide for CBX 3500, CBX 500, and B-STDX 9000 (Product Code: 80264)

• Switch Diagnostics User’s Guide for CBX 3500, CBX 500, GX 550, andB-STDX 9000 (Product Code: 80262)

• Console Command User’s Reference for CBX 3500, CBX 500, GX 550, and B-STDX 9000 (Product Code: 86021)

• Switch Software Upgrade Guide for CBX 3500, CBX 500, and GX 550 (Product code 80265)

• Navis EMS-CBGX Release 10.00.01.00 Installation and Administration Guide (Product Code: 86018)

• NavisXtend Statistics Server Release 10.00.01.00 User’s Guide (Product Code: 86017)

• NavisXtend Accounting Server Release 10.00.01.00 Administrator’s Guide (Product Code: 86024)

• NavisXtend Provisioning Server Release 10.00.01.00 User’s Guide(Product Code: 86013)


lii6/15/04 Switch Diagnostics User’s Guide for CBX 3500, CBX 500, GX 550, and B-STDX 9000

About This GuideRelated Documents

• NavisXtend Provisioning Server Release 10.00.01.00 Object Attribute Definitions User’s Reference (Product Code: 86014)

• NavisXtend Provisioning Server Release 10.00.01.00 Command Line Interface User’s Reference (Product Code: 86015)

• NavisXtend Provisioning Server Release 10.00.01.00 Error Codes User’s Reference (Product Code: 86016)

• NavisXtend Provisioning Server Release 10.00.01.00 C++ API User’s Reference (Product Code: 86027)

• NavisXtend Fault Server Release 10.00.01.00 User’s Guide (Product Code: 86025)

• NavisXtend Database Standby Server Release 10.00.01.00 User’s Guide (Product Code: 86026)

• Navis EMS-CBGX TMF 814 Adapter Implementation Reference Guide(Product Code: 86023)

• Navis EMS-CBGX TMF 814 Adapter Installation and Administration Guide (Product Code: 86022)

• NavisXtend Provisioning Server Legacy C API Reference (Product Code: 80163)

All Data Networking Group Release 10.00.01.00 manuals and the Master Glossary are available on the CBX and GX Release 10.00.01.00 Customer Documentation CD-ROM (Product Code: 80267).

Third Party• Solaris 9 Advanced Installation Guide

• Solaris 9 (SPARC Platform Edition) Release Notes

• Solaris 9 Sun Hardware Platform Guide

• Installation Guide Sybase Adaptive Server™ Enterprise on Sun Solaris

Beta Draft Confidential About This GuideOrdering Printed Manuals Online

Switch Diagnostics User’s Guide for CBX 3500, CBX 500, GX 550, and B-STDX 9000 6/15/04liii

Ordering Printed Manuals Online

You can order Data Networking manuals online. Use the following URL to access the Lucent Bookstore:

http://www.lucentdocs.com

Customer Comments

Customer comments are welcome. Please respond in one of the following ways:

• Fill out the Customer Comments form located at the back of this guide and return it to us.

• E-mail your comments to [email protected]

Technical Support

The Lucent Technical Assistance Center (TAC) is available to assist you with any problems encountered while using this Lucent product. Log on to our Customer Support Web site to obtain telephone numbers for the Lucent TAC in your region:

http://www.lucent.com/support


liv6/15/04 Switch Diagnostics User’s Guide for CBX 3500, CBX 500, GX 550, and B-STDX 9000

About This GuideTechnical Support

Switch Diagnostics User’s Guide for CBX 3500, CBX 500, GX 550, and B-STDX 9000 1-1


1

Overview

In a Lucent network, you monitor network objects, which include switches, IOMs, their physical ports, and the logical ports, trunks, and circuits that network services use for transferring data between switches. Lucent network services include:

• ATM

• Frame Relay

• IP

• SMDS

Note – SMDS is supported only on B-STDX 9000 Jade Releases M2.2MR1, M2.1MR4, and M1e.

Each switch supports one or more of these services. For information about supported services, see the hardware installation guide for your switch.

You use Navis EMS-CBGX to monitor Lucent network objects and to perform other network management tasks. Navis EMS-CBGX is a network management application.

This section gives an overview of three common monitoring functions:

• “Viewing Object Attributes” on page 1-2

• “Viewing Object Operational Information” on page 1-3

• “Viewing Summary Statistics” on page 1-3


1-2 Switch Diagnostics User’s Guide for CBX 3500, CBX 500, GX 550, and B-STDX 9000

Overview

Viewing Object Attributes

To view the configured attributes for an object, right-click on the object and select View from the popup menu. For example, Figure 1-1 shows a logical port object in the Navis EMS-CBGX Navigation Panel.

Figure 1-1. Logical Ports on a Physical Port (IOM)

Figure 1-2 shows the View Logical Port dialog box that would appear if you right-clicked on a logical port and selected View.

Figure 1-2. View Logical Port Dialog Box

Beta Draft ConfidentialOverview

Switch Diagnostics User’s Guide for CBX 3500, CBX 500, GX 550, and B-STDX 9000 10/7/051-3

Viewing Object Operational Information

To view the operational status for an object, right-click on the object and select Oper Info from the popup menu. For example, Figure 1-3 shows the View LPort Operational Status dialog box that would appear if you right-clicked on a logical port and selected Oper Info.

Figure 1-3. View LPort Operational Status Dialog Box (ATM)

Viewing Summary Statistics

To view the summary statistics for an object, expand the object, right-click on the Monitor node, and select Start from the popup menu. Figure 1-4 shows a PVC node expanded in the Navis EMS-CBGX Navigation Panel.

You can specify which statistics will be displayed by selecting or clearing the check boxes that appear under the Monitor node (Figure 1-4).

Figure 1-4. PVC Node Expanded



Overview

Figure 1-5 shows the Circuit Statistics Monitoring dialog box that would appear if you right-clicked on the Monitor node under an ATM PVC and selected Start.

Figure 1-5. Circuit Statistics Monitoring Dialog Box

Beta Draft ConfidentialOverview

Generating Reports


Generating Reports

You can use UNIX scripts or the Navis EMS-CBGX Report menu to generate reports at the network, node, circuit, trunk, SVC, or IP level.

Table 1-1 describes the UNIX scripts and associated commands that you can use to generate reports. You issue these commands at the UNIX prompt.

Note – You must have the Sybase SQR package installed before you can run these scripts. You must run the script from your home directory. The scripts listed in Table 1-1 will attempt to write to the current directory. Errors occur if you do not have write permission for the directory. These scripts create the report (with a .lis extension) in the directory where the report is run.

Table 1-1. Commands Used to Generate Network Reports

Report Script Command Report Name Description

/opt/Lucent/NavisEMS-CBGX/UtilServer/jakarta-tomcat-5.0.16/webapps/ROOT/nxtools/utils/cv-network-rpt.sh

allnetwork.lis Network report


allckt.lis Circuit report


allnode.lis Node report


alltrk.lis Trunk report


allsvc.lis SVC parameters report



OverviewGenerating Reports



2

Viewing Network, Switch, Module, and Physical Port Details

This chapter explains how to view a network and network Multiprotocol Label Switching (MPLS) settings. This chapter also describes how to view the status and hardware details of a switch, including its processor modules, Basic Input/Output (BIO) modules, Input/Output Modules (IOM), Input/Output Processor (IOP) modules, physical ports, channels, and Inverse Multiplexing for ATM (IMA) groups and links.

Viewing Networks

This section describes how to view the details for a network. This section includes:

• “Displaying a Network View” on page 2-1.

• “View MPLS Traffic Profiles” on page 2-3.

• “View MPLS Affinities” on page 2-4.

• “View Tunnel Hoplists” on page 2-5.

Displaying a Network View

To display the network view:

1. In the Network tab (Figure 2-1), expand the Networks list.

Figure 2-1. Networks Tab



Viewing Network, Switch, Module, and Physical Port DetailsViewing Networks

2. Select a network and expand the list to view it. Figure 2-2 shows an expanded network view.

Figure 2-2. Network Tree View

There are several network-wide MPLS settings that you can view from this network list. They include the following:

• MPLS Traffic Profiles - see “View MPLS Traffic Profiles” on page 2-3 for details.

• MPLS Affinities - see “View MPLS Affinities” on page 2-4 for details.

• Tunnel Hoplists - See “View Tunnel Hoplists” on page 2-5 for details.

Beta Draft ConfidentialViewing Network, Switch, Module, and Physical Port Details

Viewing Networks


View MPLS Traffic Profiles

MPLS tunnel traffic profiles (also called PSN tunnels) can be created with either IntServ profiles (one tunnel for each QOS class) or DiffServ profiles (one tunnel for all QOS classes).

To view these profiles:

1. Expand MPLS Traffic Profiles on the Networks tree to see a listing for each of these. See Figure 2-3.

Figure 2-3. MPLS Traffic Profiles

2. Expand Diffserv Profiles or Intserv Profiles to see a list of each profile type in the network.

3. Select one profile. Right-click and select View to see the profile details. Figure 2-4 shows a Diffserv profile and Figure 2-5 shows an Intserv profile.

Figure 2-4. View Diffserv Dialog Box




Figure 2-5. View Intserv Dialog Box

For additional information on MPLS tunnel traffic profiles and descriptions of the fields in these dialog boxes, see the ATM Services Configuration Guide for CBX 3500, CBX 500, GX 550, and B-STDX 9000.

View MPLS Affinities

MPLS affinities are selected when creating for RSVP-TE traffic for an MPLS (PSN) tunnel. Affinity mappings are maintained network-wide. To view MPLS affinities, expand the MPLS list under Networks. Right-click on an affinity and select View.

The View Affinity Dialog Box is displayed (Figure 2-6).

Figure 2-6. View Affinity Dialog Box

For additional information on MPLS Affinities and a description of this dialog box, see the ATM Services Configuration Guide for CBX 3500, CBX 500, GX 550, and B-STDX 9000.


Viewing Networks


View Tunnel Hoplists

An MPLS tunnel hoplist defines specific routes and nodes that must be followed in the network. Hoplists are used with Resource Reservation Protocol (RSVP) traffic and are intended for unicast only.

To view hoplists, expand the Tunnel Hoplists under Networks. Right-click on one list and select View. The View Hoplist Dialog Box is displayed (Figure 2-7).

Figure 2-7. View Hoplist Dialog Box

For additional information on Tunnel Hoplists and a description of this dialog box, see the ATM Services Configuration Guide for CBX 3500, CBX 500, GX 550, and B-STDX 9000.




Viewing A Switch

This section describes how to view the details for a switch. This section includes:

• “Displaying a Switch” on page 2-6

• “Viewing Switch Attributes” on page 2-9

• “Viewing Switch Operational Information” on page 2-9

Displaying a Switch

A switch can be displayed in the following ways:

• “Displaying a Switch Tab in the Navigation Panel” on page 2-6

• “Displaying a Switch With a Network Map” on page 2-7

Displaying a Switch Tab in the Navigation Panel

To display a switch in the navigation panel:

1. In the Network tab (Figure 2-8), expand the network that contains the switch.

Figure 2-8. Network Tab

2. If the switch is in a subnetwork of the network, expand the Subnets class node.

3. Expand the Switches class node.

4. Double-click on the switch.

The switch object tree tab appears in the Navigation Panel (Figure 2-9).


Viewing Networks


Figure 2-9. Switch Object Tree Tab

Displaying a Switch With a Network Map

To display a switch in a network map:

1. In the Maps tab, expand the Maps class node (Figure 2-10).

Figure 2-10. Maps Tab




2. Right-click on the map and select Open from the popup menu.

The Network Map View window appears (Figure 2-11).

Figure 2-11. Network Map View Window

3. Observe the color of the border around the switch. The status colors are described in Table 2-1. All switches are initially blue (“Unknown”) when the map is first opened, and change color when the first status update is received from the map server.

Table 2-1. Network Map Status Colors

Color Status

Blue Unknown

Green Up

Yellow Marginal

Red Down

Beige Unmanaged

Gray Inaccessible


Viewing Networks


Viewing Switch Attributes

To view the attributes that have been configured for the switch:

1. In either the switch object tree (“Displaying a Switch Tab in the Navigation Panel” on page 2-6) or in the network map (“Displaying a Switch With a Network Map” on page 2-7), right-click on the switch you want to view and select View from the popup menu.

The View Switch dialog box appears (Figure 2-12).

Figure 2-12. View Switch Dialog Box

2. Select the appropriate tab for the attributes you want to view. For a description of the tabs and fields that are available, see the Getting Started User's Guide for CBX 3500, CBX 500, GX 550, and B-STDX 9000.

3. When you are done viewing the switch attributes, choose Close.

The View Switch dialog box closes.

Viewing Switch Operational Information

This section describes how to view operational status for a switch.

Before You Begin

You cannot view operational information for a switch if you have set the switch to Unmanaged. The switch must be set to Manage.




When a switch is Unmanaged, the switch tab foreground color is blue. To set the switch to Manage, in the switch object tree (see “Displaying a Switch Tab in the Navigation Panel” on page 2-6), right-click on the switch and select Manage Switch from the popup menu.

Viewing Switch Operational Information

To view operational information for a switch:

1. In either the switch object tree (“Displaying a Switch Tab in the Navigation Panel” on page 2-6) or in the network map (“Displaying a Switch With a Network Map” on page 2-7), right-click on the switch you want to view and select Oper Info from the popup menu.

The Switch Operational Information dialog box appears (Figure 2-13).

Figure 2-13. Switch Operational Information Dialog Box

Table 2-2 describes the Switch Operational Information dialog box fields.

Table 2-2. Switch Operational Information Dialog Box

Field Description

Switch Name Displays the name of the switch.

Switch Type Displays the switch type.

Switch Status Displays the current operational status of the switch.

Switch Model Displays the model number of the switch.


Viewing Networks


Serial Number Displays the switch serial number.

Hardware Revision Displays the hardware revision level for the switch.

EPROM Revision Displays the erasable programmable read-only memory (EPROM) firmware revision number.

Software Revision Displays the revision number for the firmware currently running on the switch.

System Description Displays a description of the switch type.

IP Address The IP address of the primary Network Management Station (NMS). Traps and Trivial File Transfer Protocol (TFTP) requests will be directed to this address.

Secondary IP Address Displays alternate address that can be used in place of the node IP address when placing virtual circuits (VCs). This address is used when gracefully transitioning IP network numbers.

Bulk Stats Transfer State Displays the state of a bulk statistics raw data file transfer to the Statistics Server.

Num of Nonalarm Trap Discarded

Displays the number of non-alarm traps that have been discarded because of full queue conditions.

Num of Minor Trap Discarded

Displays the number of minor traps that have been discarded because of full queue conditions.

Num of Major Trap Discarded

Displays the number of major traps that have been discarded because of full queue conditions.

Reboot Count Displays the number of times this switch experienced a reboot condition since the last logged fatal error. If this value is greater than 3, information displayed in the Background Diagnostics dialog box is outdated.

Note: Although the number of Reboots counter is incremented with each reboot, there are instances where the hardware reboots or resets but the screen information does not change. These instances include: the switch powers off and on; the hardware resets (for example, when you use the latch to reset a module); and the processor modules continuously poll the modules for status. If a module does not respond, the processor module resets this module.

Reboot State Displays whether the switch is in a normal state or the type of rebooting that is in process.

Table 2-2. Switch Operational Information Dialog Box (Continued)

Field Description




ATM Accounting Operational Status

Displays the operational state of the ATM Accounting system at the switch. The options are:

• Disabled – Usage measurement is disabled.

• PVC Enabled – Usage measurement is enabled for PVCs only.

• SVC Enabled – Usage measurement is enabled for SVCs only.

• Enabled – Usage measurement is enabled for PVCs and SVCs only.

• Unknown – Status of usage measurement is not known.

ATM Accounting Server Communication Status

Displays the current state of communications to the ATM Accounting server. The options are:

• Red – File transfers have failed. The operational state of the ATM accounting for the switch is set to Disabled.

• Yellow – File transfers are experiencing significant failures. New data is continuing to be generated and queued up but the operational state of ATM Accounting is not set to Disabled yet.

• Green – File transfers are not experiencing significant failures. Any accounting data queued during failure periods has been successfully transported to the Accounting Server.

• Unknown – Status of communications to the ATM Accounting server is not known.

FR Accounting Operational Status

Displays the operational state of the Frame Relay (FR) Accounting system at the switch. The options are:

• Disabled – Usage measurement is disabled.

• PVC Enabled – Usage measurement is enabled for PVCs only.

• SVC Enabled – Usage measurement is enabled for SVCs only.

• Enabled – Usage measurement is enabled for PVCs and SVCs only.

• Unknown – Status of usage measurement is not known.


Field Description


Viewing Networks


2. If you want to update the operational information, choose Refresh.

3. When you are done viewing the operational information, choose Close.

The Switch Operational Information dialog box closes.

FR Accounting Server Communication Status

Displays the current state of communications to the Frame Relay (FR) Accounting server. The options are:

• Red – File transfers have failed. The operational state of the FR accounting for the switch is set to Disabled.

• Yellow – File transfers are experiencing significant failures. New data is continuing to be generated and queued up but the operational state of FR Accounting is not set to Disabled yet.

• Green – File transfers are not experiencing significant failures. Any accounting data queued during failure periods has been successfully transported to the Accounting Server.

• Unknown – Status of communications to the FR Accounting server is not known.

MPLS Operational Status The operational status of MPLS on the switch.

MPLS Admin Status The administrative status of MPLS on the switch.

Number of MPLS Tunnels Configured

The number of MPLS tunnels configured on the switch.

Number of MPLS Tunnels Active

The number of active MPLS tunnels on the switch.

RSVP-TE Router ID The RSVP-TE router ID of the switch.

Refresh Choose to refresh the display of operational information.

Close Choose to close the dialog box.


Field Description



Viewing Network, Switch, Module, and Physical Port DetailsViewing PNNI Nodes

Viewing PNNI Nodes

This section describes how to view the details for a PNNI Node. This section includes:

• “Displaying PNNI Nodes for a Switch” on page 2-14

• “Viewing PNNI Node Attributes” on page 2-14

• “Viewing PNNI Node Operational Information” on page 2-15

• “Viewing PNNI Node Signaling Statistics” on page 2-16

Displaying PNNI Nodes for a Switch

To display the PNNI Nodes that belong to a switch:

1. In the switch tab (see “Displaying a Switch Tab in the Navigation Panel” on page 2-6), expand the switch.

2. Expand the PNNI Nodes class node.

The PNNI Nodes that belong to the switch appear (Figure 2-14).

Figure 2-14. PNNI Nodes on a Switch

Viewing PNNI Node Attributes

To view the configured attributes for a PNNI Node:

1. Display the PNNI Nodes for a switch (see “Displaying PNNI Nodes for a Switch” on page 2-14).

2. Right-click on the PNNI Node and select View from the popup menu.

The View PNNI Node Configuration dialog box appears (Figure 2-15).

For a description of the attributes, see the ATM Services Configuration Guide for CBX 3500, CBX 500, GX 550, and B-STDX 9000.


Viewing PNNI Nodes


Figure 2-15. View PNNI Node Configuration Dialog Box

3. When you are done viewing the attributes, choose Close.

The View PNNI Node Configuration dialog box closes.

Viewing PNNI Node Operational Information

This section describes how to view operational status for PNNI Nodes.

Before You Begin

You cannot view operational information for a PNNI Node if you have set the switch to Unmanaged. The switch must be set to Manage.


To view operational information for a PNNI Node:


2. Right-click on the PNNI Node whose operational information you want to view and select Oper Info from the popup menu.

The PNNI Operational Information dialog box appears (Figure 2-16).




Figure 2-16. PNNI Operational Information Dialog Box

The fields in the PNNI Operational Information dialog box are described in Table 2-3.



The PNNI Operational Information dialog box closes.

Viewing PNNI Node Signaling Statistics

To view signaling statistics for a PNNI Node:


2. Right-click on the PNNI Nodes and select Signaling Statistics from the popup menu.

The PNNI Signalling Statistics dialog box appears (Figure 2-17).

Table 2-3. PNNI Node Operational Information

Field Description

Node Operational Status Displays the operational status of the PNNI Node (Up or Down).

Node ID in Hex Displays the PNNI Node ID of the switch. This ID is not configurable. The switch derives this ID by concatenating the PNNI Level, the hexadecimal value 0xA0, and the ATM address.

Number of PTSE Displays the number of PNNI Topology State Elements (PTSEs) in the topology database of the switch. A PTSE is a collection of PNNI topology information that is sent to all nodes in a peer group.


Viewing PNNI Nodes


Figure 2-17. PNNI Signalling Statistics Dialog Box

The fields in the PNNI Signalling Statistics dialog box are described in Table 2-4.

Table 2-4. PNNI Node Signalling Statistics

Field Description

Successful call attempts as a origination node

Displays the number of successful call attempts from this object as an orignation node.

Unsuccessful call attempts as a origination node

Displays the number of unsuccessful call attempts from this object as an orignation node.

Crank-backs directed to this node as a origination node

Displays the number of crank-backs directed to this object as an orignation node.

Successful call attempts as a border node

Displays the number of successful call attempts from this object as a border node.

Unsuccessful call attempts as a border node

Displays the number of unsuccessful call attempts from this object as a border node.

Crank-backs directed to this node as a border node

Displays the number of crank-backs directed to this object as a border node.

Successful PMP call attempts as a origination node

Displays the number of successful PMP call attempts from this object as an orignation node.

Unsuccessful PMP call attempts as a origination node

Displays the number of unsuccessful PMP call attempts from this object as an orignation node.




3. Choose Refresh to update these statistics.

4. When you are done viewing the signaling statistics, choose Close.

The PNNI Signalling Statistics dialog box closes.

To view PNNI LPort signaling statistics, see “” on page 7-16.

PMP Crank-backs directed to this node as a origination node

Displays the number of PMP crank-backs directed to this object as an orignation node.

Successful PMP call attempts as a border node

Displays the number of successful PMP call attempts from this object as a border node.

Unsuccessful PMP call attempts as a border node

Displays the number of unsuccessful PMP call attempts from this object as a border node.

PMP crank-backs directed to this node as a border node

Displays the number of PMP crank-backs directed to this object as a border node.

Table 2-4. PNNI Node Signalling Statistics (Continued)

Field Description


Viewing Network Traffic Descriptors


Viewing Network Traffic Descriptors

To view the configured attributes for a network traffic descriptor:

1. In the Network tab (Figure 2-18), expand the Networks class node.

Figure 2-18. Traffic Descriptor Node Expanded

2. Expand the network node.

3. Expand the Traffic Descriptors class node.

4. Right-click on the traffic descriptor you want to view and select View from the popup menu.

The View Traffic Descriptor dialog box appears (Figure 2-19).

For a description of the attributes, see the ATM Services Configuration Guide for CBX 3500, CBX 500, GX 550, and B-STDX 9000.

Figure 2-19. View Traffic Descriptor Dialog Box



Viewing Network, Switch, Module, and Physical Port DetailsRedundant Groups

Redundant Groups

The CBX 3500 switch supports two line card protection slots that allow universal modules to be configured in two 1:N warm redundancy groups. If a fatal error is detected an ATM Universal I/O module in a given redundancy group, the protection card for that group will failover and assume the failed card’s responsibilities. Each protection module consists of a Universal IOP and a Protection IOA installed in slot 15 and/or 16.

The CBX 3500 supports redundancy for the SP 90 and for the following Universal ATM I/O modules:

• 1-port OC-48c/STM-16 IOA (ATM)

• 4-port OC-12c/STM-4 IOA (ATM)

• 24-port DS3 ATM IOA

• 16-port OC-3c/STM-1 ATM

The redundancy groups are identified by the group Id numbers. Group 2 and Group 3 are for corresponding protection slots 15 and 16 respectively. Group 1 is exclusively for SP 90 redundancy. The three redundancy groups are added by default when a CBX 3500 switch is installed. Group 1 redundancy is enabled by default after the redundant SP 90 is configured. However, we need to explicitly add the line cards to either group 2 or 3, depending on whether the protection card is in slot 15 or 16 or both.

Viewing Redundant Groups

To view redundant groups information:

1. Expand the network that includes the desired switch.

2. Expand the switch node.

3. Expand Redundant Groups.

Group 2 if the Protection module is in slot 15 or Group 3 if the Protection IOA is in slot 16.

4. Right click on the desired group and click View on the popup menu.

The Redundancy dialog box is displayed. Figure 2-20 shows the Group 1 dialog box while Figure 2-21 shows the Group 2 and 3 dialog box.


Redundant Groups


Figure 2-20. Group 1 Redundancy Dialog Box

Figure 2-21. Group 2 and 3 Redundancy Dialog Box

For a definition of the fields in the Group 1, 2, and 3 dialog boxes, see the Switch Module Configuration Guide for CBX 3500, CBX 500, GX 550, and B-STDX 9000.



Viewing Network, Switch, Module, and Physical Port DetailsRedundant Groups

Viewing Operational Status

To view the operational status of a redundant group:



3. Expand Redundant Groups.

Group 2 if the Protection module is in slot 15 or Group 3 if the Protection IOA is in slot 16.

4. Right click on the desired group and click Oper Info on the popup menu.

The Redundant Group Operational Information dialog box (Figure 2-22) is displayed.

Figure 2-22. Redundant Group Operational Information

The fields in the Redundant Group Operational Information dialog box are shown in Figure 2-5.

Table 2-5. Redundant Group Operational Information

Field Description

Protection Slot Identifies the protection slot.

Operational Status The operational status of the redundant group.


Viewing LDP Entities



Label Distribution Protocol (LDP) sessions are configured on each switch for use with PWE3 connections. For additional details on LDP entities, see the ATM Services Configuration Guide for CBX 3500, CBX 500, GX 550, and B-STDX 9000.

View LDP Entities

To view an LDP entity:



3. Expand LDP Entities.

The View LDP Entity Dialog box is displayed (Figure 2-23).

Figure 2-23. View LDP Entity Dialog Box

For a description of the fields in this dialog box, see the ATM Services Configuration Guide for CBX 3500, CBX 500, GX 550, and B-STDX 9000.

View LDP Entity Operational Information

To view the operational status of an LDP entity:




4. Right-click on the desired entity and click Oper Info on the popup menu.

The LDP Entity Operational Information dialog box (Figure 2-24) is displayed.



Viewing Network, Switch, Module, and Physical Port DetailsViewing LDP Entities

Figure 2-24. LDP Entity Operational Information

The fields in the LDP Entity Operational Information dialog box are shown in Table 2-6.

LDP Entity Statistics

To monitor LDP statistics:




4. Expand the desired entity and right-click on the Monitor node.

5. Click Start on the popup menu.

The LDP Statistics dialog box (Figure 2-25) is displayed.

Table 2-6. LDP Entity Operational Information

Field Description

Admin Status The administrative status of this LDP Entity. If the status is disabled, then all contact with the peer is lost.

Session Status The current state of the session.




Figure 2-25. LDP Statistics

The fields in the LDP Statistics dialog box are shown in Table 2-7.

Table 2-7. LDP Statistics

Field Description

Session Rejected Label Range Errors

A count of the sessions rejected due to label range errors sent or received by this LDP entity.

Session Rejected Max PDU Errors

A count of the sessions rejected due to Max Pdu Length Errors sent or received by this LDP entity.

Session Rejected No Hello Errors

A count of the sessions rejected due to no Hello sent or received by this LDP entity.

Attempted Sessions The count of the total attempted sessions for this LDP entity.

Shutdown NotifSent This object counts the number of Shutdown Notifications sent related to sessions (past and present) associated with this LDP entity.

Shutdown NotifReceived This object counts the number of Shutdown Notifications received related to sessions (past and present) associated with this LDP entity.

Malformed TLV Value Errors

This object counts the number of Malformed TLV Value Fatal Errors detected by the sessions (past and present) associated with this LDP entity.



Viewing Network, Switch, Module, and Physical Port DetailsViewing LDP Entities

Bad TLV Length Errors This object counts the number of Bad TLV Length Fatal Errors detected by the sessions (past and present) associated with this LDP Entity.

Bad PDU Length Errors This object counts the number of Bad Pdu Length Fatal Errors detected by the sessions (past and present) associated with this LDP entity.

Bad Message Length Errors This object counts the number of Bad Message Length Fatal Errors detected by the sessions (past and present) associated with this LDP entity.

Bad LDP Identifier Errors This object counts the number of Bad LDP Identifier Fatal Errors detected by the sessions (past and present) associated with this LDP entity.

Keep Alive Timer Expired Errors

This object counts the number of Session Keep Alive Timer Expired Errors detected by the sessions (past and present) associated with this LDP entity.

Table 2-7. LDP Statistics

Field Description


Viewing Tunnels


Viewing TunnelsMPLS tunnels (also called PSN tunnels) are an important feature of the ATM over MPLS applications. These tunnels carry ATM traffic from multiple Lucent trunk virtual private networks (VPNs) between two nodes. MPLS tunnels can be configured to carry various types of traffic.

Layer 2 tunnels are end-to-end tunnels that carry ATM traffic through the MPLS tunnel.

For additional information on tunnels and the ATM over MPLS features, refer to ATM Services Configuration Guide for CBX 3500, CBX 500, GX 550, and B-STDX 9000.

View MPLS (PSN) Tunnels

To view an MPLS tunnel:



3. Expand MPLS Tunnels.

4. Right-click on the desired tunnel and select View.

The View Tunnel dialog box is displayed (Figure 2-26) with the General Tab.

Figure 2-26. View Tunnel Dialog Box



Viewing Network, Switch, Module, and Physical Port DetailsViewing Tunnels

Depending upon the traffic signalling protocol configured, several additional tabs are displayed in the View Tunnel dialog box. They include the following:

• RSVP-TE Tab - See Figure on page 2-28.

• Static Tab - See Figure 2-28 on page 2-29.

Figure 2-27. View Tunnel Dialog Box - RSVP-Lite Tab


Viewing Tunnels


Figure 2-28. View Tunnel Dialog Box - Static Tab

For a description of traffic signalling protocols and the fields in these dialog boxes, see the ATM Services Configuration Guide for CBX 3500, CBX 500, GX 550, and B-STDX 9000.

View MPLS (PSN) Tunnel Operational Information

To view operational information for an MPLS tunnel:




4. Right click on the desired tunnel and click Oper Info on the popup menu.

The MPLS Tunnel Operational Information dialog box (Figure 2-29) is displayed. Note that if the tunnel is bidirectional, information for both directions will be displayed.




Figure 2-29. MPLS Tunnel Operational Information

The fields in the MPLS Tunnel Operational Information dialog box are described in Table 2-8.


Viewing Tunnels


Table 2-8. MPLS Tunnel Operational Information

Field Description

Tunnel Index Displays the assigned tunnel index value.

Admin Stat Displays the administrative status of the tunnel. Values may be UP, DOWN, or TESTING.

Operational Status Displays the operational status of the tunnel. Values may be UP, DOWN, TESTING, UNKNOWN, DORMANT, or NOT PRESENT.

Failure Reason Displays the failure reason and code, if tunnel is down.

Up Time Displays the time (in seconds) that the tunnel is active.

Path Changes Displays the number of times the path has changed for this tunnel.

XConnect Admin Status Not applicable

XConnect Operational Status

Not applicable

Switch Role Displays the role of this switch in the tunnel. Switch can be HEAD (start of the tunnel), TRANSIT (located along the tunnel), or END (terminating the tunnel).

Resource MaxRate Displays the maximum bandwidth of the tunnel in units of 1000 bits/second.

Resource MeanRate Displays the mean bandwidth of the tunnel in units of 1000 bits/second.

Resource MaxBurstSize Displays the maximum burst size of the tunnel in bytes.

Resource MeanBurstSize Displays the mean burst size of the tunnel in bytes.

Resource ExcessBurstSize Displays the excess burst size of the tunnel in bytes.

InSegment IfIndex Displays the interface index for the incoming MPLS interface.

InSegment Label Displays the incoming label for the MPLS segment.

OutSegment IfIndex Displays the interface index for the outgoing MPLS interface.

OutSegment Label Displays the outgoing label for the MPLS segment.




View MPLS Tunnel Statistics

To view the statistics of an MPLS tunnel:




4. Expand the desired tunnel.

5. Right-click on the Monitor icon under the desired tunnel. Note that Configure and Start options are available. Select Configure to choose monitoring options.

The Tunnel Monitor Configuration dialog box opens. Figure 2-30 shows the Tunnel Monitor Configuration dialog box. Table describes the fields in this box.

Figure 2-30. Tunnel Monitor Configuration Dialog BoxT

Table 2-9. Tunnel Monitor Configuration Dialog Box Field Descriptions

Field Description

Switch IP Address The IP address of the selected switch.

Tunnel Name The name of the tunnel on the selected switch.

Timing Parameters

Polling Interval Select the desired monitor polling interval in seconds. The range is from 5 to 86400.

Schedule (From) Time frame parameters are not supported.


Viewing Tunnels


6. Close the Configuration dialog box after completing your selections.

7. Right-click on the Monitor icon again and select Start on the popup menu to begin statistics collection.

The MPLS Tunnel Statistics dialog box (Figure 2-31) is displayed.

Figure 2-31. MPLS Tunnel Statistics

Schedule (To) Time frame parameters are not supported.

Table 2-9. Tunnel Monitor Configuration Dialog Box Field Descriptions (Continued)

Field Description




The fields in the MPLS Tunnel Statistics Viewing dialog box are described in Table 2-10. Each MPLS tunnel can have one outsegment originating at this LSR, and/or one insegment terminating at this LSR.

8. Close the Monitoring dialog box when tunnel monitoring is complete.

Table 2-10. MPLS Tunnel Statistics

Field Description

MPLS Tunnel Forward and Backward Statistics

Tunnel Perf Errors Displays the number of errors detected.

Tunnel Perf Discard Bytes Displays the number of discarded bytes.

Tunnel Perf Discards Displays the number of discarded packets.

Tunnel Perf Bytes Displays the number of bytes transmitted.

Tunnel Perf Packets Displays the number of packets transmitted.

MPLS Tunnel Forward and Backward Resource

Tunnel Resource Exc Burst Size Displays the excess burst size of the tunnel in bytes.

Tunnel Resource Mean Burst Size Displays the mean burst size of the tunnel in bytes.

Tunnel Resource Max Burst Size Displays the maximum burst size of the tunnel in bytes.

Tunnel Resource Mean Rate Displays the average bandwidth of the tunnel in units of 1000 bits/second.

Tunnel Resource Max Rate Displays the maximum bandwidth of the tunnel in units of 1000 bits/second.


Viewing Tunnels


View Layer 2 Tunnels

To view a Layer 2 tunnel:



3. Expand Layer 2 Tunnels.

4. Right-click on the desired tunnel and select View from the menu.

The View Layer 2 Tunnel dialog box is displayed (Figure 2-32).

Figure 2-32. View Layer 2 Tunnel Dialog Box


View Layer 2 Tunnel Operational Information

To view the operational information about a Layer 2 tunnel:




4. Right click on the desired tunnel and click Oper Info on the popup menu.




The Layer 2 Tunnel Operational Information dialog box (Figure 2-33) is displayed.

Figure 2-33. Layer 2 Tunnel Operational Information

The fields in the Layer 2 Tunnel Operational Information dialog box are shown in Table 2-11.

Layer 2 Tunnel Statistics

To monitor Layer 2 tunnel statistics:




4. Expand the desired tunnel.

5. Right-click on the Monitor icon under the desired tunnel. Note that Configure and Start options are available. Select Configure to choose monitoring options.

The Tunnel Monitor Configuration dialog box opens. See Figure 2-30 on page 2-32 for a sample dialog box and field descriptions.

Table 2-11. Layer 2 Tunnel Operational Information

Field Description

Admin Status The administrative state of the Layer 2 tunnel.

Operational Status The operational state of the Layer 2 tunnel.

Tunnel Slot The logical slot where the Layer 2 tunnel is created.

Tunnel Parent LPort The logical port on which the Layer 2 tunnel is created.

Error Code Current error code of Layer 2 tunnel failures.


Viewing Tunnels


6. Close the Configuration dialog box after completing your selections.

7. Right-click on the Monitor icon and select Start on the popup menu to begin statistics collection.

The Layer 2 Tunnel View Statistics dialog box (Figure 2-34) is displayed.

Figure 2-34. Layer 2 Tunnel Statistics

The fields in the Layer 2 Tunnel Statistics dialog box are described in Table 2-12.

8. Close the Monitoring dialog box when tunnel monitoring is complete.

Table 2-12. Layer 2 Tunnel Statistics

Field Description

Number of Packets Number of packets forwarded by the tunnel.

Number of Bytes Number of bytes forwarded by the tunnel.

Number of Packets Discarded

Number of packets discarded by the tunnel.

Number of Bytes Discarded Number of bytes discarded by the tunnel.



Viewing Network, Switch, Module, and Physical Port DetailsFront and Rear View Status Colors

Front and Rear View Status Colors

This section describes how the status of components in the Front and Rear View panels is shown. This section contains the following information:

• “Displaying a Switch in the Front/Rear Views” on page 2-39

• “IOM and Processor Module Colors” on page 2-48

• “Physical Port Colors” on page 2-48

• “External Power Status Indicator Colors (GX 550)” on page 2-49

• “Alarm Status Indicator Colors” on page 2-49

• “Switch Status Indicator Colors” on page 2-49

• “Module Status Indicator Colors” on page 2-50

• “Stby/Redundancy Status Indicator Colors” on page 2-50

• “Fan/Power Supply Status Indicator Colors” on page 2-50

• “MID Status Colors (CBX 3500)” on page 2-51




Displaying a Switch in the Front/Rear Views

To display the Front or Rear View panel for a switch:

1. In either the switch object tree (“Displaying a Switch Tab in the Navigation Panel” on page 2-6) or in the network map (“Displaying a Switch With a Network Map” on page 2-7), right-click on the switch, and select Front/Back Panel Views from the popup menu.

The Rear View panel appears in the Navis EMS-CBGX window.

Figure 2-35 (GX 550), Figure 2-36 (CBX 3500), Figure 2-37 (CBX 500), and Figure 2-38 (B-STDX 9000) show the Rear View panel.

2. If you want to view the Front View panel, choose the Front/Rear View button on the toolbar (Figure 2-35). If you want to see the navigation panel with the Front/Rear View panel, choose the Hide/Show OL button on the toolbar.

Figure 2-39 (GX 550), Figure 2-40 (CBX 3500), Figure 2-41 (CBX 500), and Figure 2-42 (B-STDX 9000) show the Front View panel.




Figure 2-35. GX 550 Rear View

Slot Number

Physical Port

Power Feed A Status

Redundancy Status of Timing Processor

Timing Processor Status

External Power Status

Fan Tray 1 Status

Power Feed B Status

Front/Rear View

Hide/Show OL




Figure 2-36. CBX 3500 Rear View

Slot Number

Physical Port

Cooling Fan Module Status

MID Status




Figure 2-37. CBX 500 Rear View

Slot Number

Physical Port


Power Supply Status




Figure 2-38. B-STDX 9000 Rear View

Slot Number

Physical Port


Power Supply Status




Figure 2-39. GX 550 Front View

Node Processor Status

Fan Tray 4 Status

Alarm Status

Redundancy Status of Node Processor

Switch Fabric Status

Fan Tray 3 Status

Redundancy Status of Switch Fabric

Slot Number

BIO Module Status




Figure 2-40. CBX 3500 Front View

Slot Number

Switch Status

SP Module Status


IOP Module Status

Alarm Status

Redundancy Status of SP

Power Supply Status

MID Status




Figure 2-41. CBX 500 Front View

Slot Number

Switch Status

SP Module Status


IOP Module Status

Alarm Status

Redundancy Status of SP

Power Supply Status




Figure 2-42. B-STDX 9000 Front View

Slot Number

Switch Status

CP Module Status

Alarm Status

Redundancy Status of CP

Power Supply Status

IOP Module Status





IOM and Processor Module Colors

IOMs and processor modules in the Rear View panel display color to indicate their operational status. BIO subcards on GX 550 switches also use this color scheme. Table 2-13 describes the colors that are used.

Physical Port Colors

A colored border appears around physical ports in the Rear View panel to indicate their operational status. Table 2-14 describes the colors that are used.

To determine the specific logical ports that are down, check your trap event browser or log, or use Navis EMS-CBGX to check logical port status. See Chapter 14, “Monitoring Alarms” and Chapter 18, “Monitoring MIB Values” for more information on traps. See “Viewing Operational Status for an ATM Logical Port” on page 7-1 or “Viewing Operational Status for a Frame Relay Logical Port” on page 8-1 for more information on logical port status.

Table 2-13. Module Colors

Module Color Indicates

Red Module is bad or not present.

Yellow Module may be in marginal state or out of sync.

Gray Module is operational.

Table 2-14. Physical Port Colors

Port Color Indicates

Gray Unknown status. This condition usually occurs if the configuration has not been downloaded or if the NMS and PRAM configurations do not match. It also occurs when no logical port is configured.

Green All logical ports are operationally UP.

Red All logical ports are operationally Down.

Yellow When one or more (but not all) logical ports are operationally/administratively Down.




External Power Status Indicator Colors (GX 550)

External Power indicators appear in the Rear View panel for GX 550 switches. Table 2-15 describes the color scheme that is used for these indicators.

Figure 2-35 shows the Rear View panel for the GX 550.

Alarm Status Indicator Colors

Alarm status indicators appear for physical ports in the Front View panel. Table 2-16 describes the color scheme that is used for this indicator.

Switch Status Indicator Colors

The Switch Status indicator appears on the CP and SP modules in the Front View panel. Table 2-17 describes the color scheme that is used for this indicator.

Table 2-15. External Power Status Indicator Colors

Indicator Color Indicates

Green DC Input Power Protection Unit or AC to DC Rectifier is operational.

Red DC Input Power Protection Unit or AC to DC Rectifier is not operational.

Blue Unknown status for DC Input Power Protection Unit or AC to DC Rectifier.

Table 2-16. Alarm Status Indicator Colors


No indicator No alarm condition for the port.

Red Solid red in case of Red Alarms (e.g., LOS, OOF, LOF) and blinking red in case of Blue Alarms (e.g., AIS)

Yellow An LOS has been detected at remote equipment on the circuit for the port or the port receives any other Yellow Alarm.

Table 2-17. Switch Status Indicator Colors


Green Switch is operational.

Red Switch is not operational.




Module Status Indicator Colors

Module status indicators appear in the Front and Rear View panels. Table 2-18 describes the color scheme that is used for this indicator.

Stby/Redundancy Status Indicator Colors

Stby and Redundancy Status indicators appear in the Front and Rear View panels. Table 2-19 describes the color scheme that is used for this indicator.

Fan/Power Supply Status Indicator Colors

Fan module and power supply status indicators appear in the Front and Rear View panels. Table 2-20 describes the color scheme that is used for these indicators.

Yellow Switch is out of sync or the switch reports a module-type mismatch or a marginal state.

Blue Unknown status.

Table 2-17. Switch Status Indicator Colors (Continued)


Table 2-18. Module Status Indicator Colors


Green Module is operational.

Red Module is not operational.

Blue (for processor modules, fans, and power supply units)

Unknown status.

Table 2-19. Stby and Redundancy Status Indicator Colors


Green Module is the standby module.

Red Module is not the standby module.

Note – When an A or B DC power-feed fails on a CBX 500 switch, the green LEDs flash on all power supplies. Since all the LEDs are not synchronized, watch the LEDs of one power supply rather than focusing on the blinking pattern of all power supplies.




MID Status Colors (CBX 3500)

For the CBX 3500, a switch fabric sign appears at the bottom of each line module in the Front and Rear View panels. This sign indicates the status of the Mesh Interface Device (MID) for that module. Table 2-21 describes the colors that are used.

Table 2-20. Fan Module and Power Supply Colors


Green Fan or power supply unit is operational.

Red Fan or power supply unit is not operational.

Blue Unknown status.

Table 2-21. MID Status Colors

Port Color Indicates

Green MID is up.

Red MID is down.

White MID is not present.



Viewing Network, Switch, Module, and Physical Port DetailsSNMP Failures

SNMP Failures

A Simple Network Management Protocol (SNMP) failure results in the display of the Error window. The window lists the object that could not be modified, and gives an SNMP response for the failure reason.

Figure 2-43. SNMP Error Window

Choose one of the three buttons:

• Abort — Cancel the operation.

• Retry — Attempt the operation again.

• Ignore — Modify the database only and mark the object as out of sync.


Displaying Error Log and Debugging Information


Displaying Error Log and Debugging Information

The Console window (Figure 2-44) displays an error log of the Navis EMS-CBGX requests, displays debugging information, and can copy or print log or debugging information you have selected.

To open the Console window, select Console from the Tools menu (Figure 2-44).

Figure 2-44. Navis EMS-CBGX Console Window

In the Console window, the Error tab displays a log of the errors. When an SNMP failure occurs on a switch, the Console window displays part of the SNMP trace information and provides details about the error. The Debug tab displays debugging information concerning an error.

Table 2-22 describes the menus in the Console window.

Table 2-22. Console Window Elements

Menu Description

Log menu • Debug - Select the Debug box to either insert a check to display debug information or to remove the check to not display debug information.

• Print - Prints the contents of the current tab (Error or Debug).

• Clear All - Clears the contents of the current tab (Error or Debug).

• Close - Closes the Console window.

Edit menu • Copy - Copies the selected contents of the current tab (Error or Debug).

• Select All - Selects the entire contents of the current tab (Error or Debug).

Help Displays help information about the Console window.



Viewing Network, Switch, Module, and Physical Port DetailsViewing Modules

Viewing Modules

This section describes how to view the details for a module or subcard. This section includes:

• “Displaying Modules and Subcards” on page 2-54

• “Viewing Processor Modules” on page 2-55

• “Viewing System-Timing Options” on page 2-62

• “Viewing IOMs, BIOs, and Subcards” on page 2-63

Displaying Modules and Subcards

This section describes how to display modules and subcards in the Navigation Panel. This section includes:

• “Displaying the Modules for a Switch” on page 2-54

• “Displaying GX 550 Subcards” on page 2-55

Displaying the Modules for a Switch

To display the modules that belong to a switch:


2. Expand the Cards class node.

The modules that belong to the switch appear (Figure 2-45).

Figure 2-45. Modules on a Switch


Viewing Modules


Displaying GX 550 Subcards

To display the subcards for a GX 550 BIO:




Figure 2-46. Subcards on a GX 550

3. Expand the module that contains the subcard you want to view.

4. Expand the Subcards class node.

Viewing Processor Modules

This section describes how to view the details for a processor module:

• How to view the attributes that have been configured for a processor module. This includes:

– “Viewing CP Module Attributes” on page 2-55

– “Viewing SP Module Attributes” on page 2-56

– “Viewing NP Module Attributes” on page 2-57

• How to view the operational information for a processor module. See “Viewing CP, SP, or NP Operational Information” on page 2-58.

Viewing CP Module Attributes

To view the attributes that have been configured for a B-STDX 9000 Control Processor (CP):

1. Display the modules for a switch (see “Displaying the Modules for a Switch” on page 2-54).

2. Right-click on the module, and select View from the popup menu.

The View Card dialog box appears (Figure 2-47). For a description of the attributes, see the Switch Module Configuration Guide for CBX 3500, CBX 500, GX 550, and B-STDX 9000.




Figure 2-47. View Card Dialog Box (CP)


The View Card dialog box closes.

Viewing SP Module Attributes

To view the attributes that have been configured for a CBX 500 or CBX 3500 Switch Processor (SP):


2. Right-click on the module and select View from the popup menu.

The View Card dialog box appears (Figure 2-48). This example is for the CBX 500. For a description of the attributes of this dialog box and those for other switch processors, see the Switch Module Configuration Guide for CBX 3500, CBX 500, GX 550, and B-STDX 9000.


Viewing Modules


Figure 2-48. View Card Dialog Box (SP)



Viewing NP Module Attributes

To view the attributes that have been configured for a Node Processor (NP):



The View Card dialog box appears (Figure 2-49). For a description of the attributes, see the Switch Module Configuration Guide for CBX 3500, CBX 500, GX 550, and B-STDX 9000.

Figure 2-49. View Card Dialog Box (NP)






Viewing CP, SP, or NP Operational Information

This section describes how to view operational status for a processor module. The operational information dialog boxes also contain manufacturing information.

Before You Begin

You cannot view operational information for a module if you have set the switch to Unmanaged. The switch must be set to Manage.

When a switch is Unmanaged, the switch tab foreground color is blue. To set the switch to Manage:

• In the switch object tree (see “Displaying a Switch Tab in the Navigation Panel” on page 2-6), right-click on the switch and select Manage Switch from the popup menu.

To View Operational Information for a CP, SP, or NP


2. Right-click on the processor module and select Oper Info from the popup menu.

The View Card Operational Information dialog box appears (Figure 2-50).

Figure 2-50. View Card Operational Information Dialog Box (CP)

3. Select the tab for the operational parameters you want to view.

The fields in the General tab are described in Table 2-23.

The fields in the Hardware tab are described in Table 2-24.

The fields in the Software tab are described in Table 2-25.


Viewing Modules


The fields in the Mesh Status tab (SP90 on CBX 3500 only) are described in Table 2-26.

The fields in the Node Processor tab (NP on GX 550 only) are described in Table 2-27.

Table 2-23. View Card Operational Information: General Tab (processor modules)

Field Description

Type Displays the module type.

Operational Status Displays the operational status of this module (Up or Down).

Redundant Status Displays the redundancy status of this module (Connected, Not Connected, or N/A).

Actual Type Displays the actual module type from the switch.

Physical Slot ID Displays the number of the slot in which the module resides.

Card State Displays the state of the card.

Card State Displays the status of the module.

Module Category Displays the type of processor module.

Admin Status Displays one of the following options to set the module administration status:

• Up – (default) The module becomes fully operational at switch start-up. To become operational, the module gets its application code from the Personal Computer Memory Card International Association (PCMCIA) hard drive, which resides in the processor adapter module.

• Down – The module does not come online when you start the switch. The configuration is saved in the database, but is not downloaded to the switch. Use this option when running foreground diagnostics. This setting also enables you to erase PRAM when a module is out of sync.

Redundant Slot Displays the number of the slot of the redundant processor module, if applicable.

Defined Type Displays the configured model type for this module.

Logical Slot ID Displays the number of the slot in which this processor module is configured.




Capability (CP only) Displays the actual capability of the module (such as CP Basic or CP Plus).

Table 2-24. View Card Operational Information: Hardware Tab (processor modules)

Field Description

General:

Product Code Displays the product code of this module.

Manufacturing Part Number Displays the manufacturing part number for this module.

Hardware Revision Displays the hardware revision of this module.

Serial Number Displays the serial number of this module.

Total Memory Size (MB) Displays the total size of the module’s memory in MB.

Adapter Module:

Product Code Displays the product code of this adaptor module.

Manufacturing Part Number Displays the manufacturing part number for this adaptor module.

Hardware Revision Displays the hardware revision of this adaptor module.

Serial Number Displays the serial number of this adaptor module.


Table 2-25. View Card Operational Information: Software Tab (processor modules)

Field Description

General

EPROM Revision Displays the EPROM firmware revision number.

Table 2-23. View Card Operational Information: General Tab (processor modules) (Continued)

Field Description


Viewing Modules


Ethernet MAC Address Displays the Ethernet Media Access Control (MAC) address of this CP or SP in hexadecimal format.

Require Capability Bitmask Displays the required capability bitmask.

Oper Capability Bitmask Displays the operational capability bitmask.

Software

Revision Displays the module software version.

Revision ID Displays the ID of the module software version.

Build Date Displays the build date of the switch software version.

NRTS:

NRTS Oper State Displays the operational status of this Non-Real Time Services (NRTS) module.

NRTS Hardware Revision Displays the hardware revision of this NRTS module.

NRTS Out Cell Buffer Size Displays the out cell buffer size of this NRTS module.

Table 2-26. View Card Operational Information: Mesh Status Tab (SP90 on CBX 3500 only)

Field Description

Aggregated CLP0 Count Displays the total number of CLP=0 cells that are dropped by the MID.


Mesh Status Displays the status of the MID.

IOC-P Bus Status (CBX 3500 only)

Displays the status of the primary Oracle Call Interface (OCI) bus.

IOC-S Bus Status (CBX 3500 only)

Displays the status of the secondary OCI bus.

Table 2-25. View Card Operational Information: Software Tab (processor modules) (Continued)

Field Description






The View Card Operational Information dialog box closes.

Viewing System-Timing Options

To view the configured system-timing options for the CBX 500 or CBX 3500 SP or the GX 550 NP:


2. Right-click the NP or SP module and select View System Timing from the popup menu.

The View System Timing dialog box appears (Figure 2-51). For a description of the attributes, see the Switch Module Configuration Guide for CBX 3500, CBX 500, GX 550, and B-STDX 9000.

Table 2-27. View Card Operational Information: Node Processor Tab (NP on GX 550 only)

Field Description

Switch Fabric 1: Operational Status

Displays the operational status of this module (Up or Down).

Switch Fabric 2: Operational Status


Timing Module 1:Operational Status


Timing Module 2:Operational Status



Viewing Modules


Figure 2-51. View System Timing Dialog Box

3. When you are done viewing the system timing parameters, choose Close.

The View System Timing dialog box closes.

Viewing IOMs, BIOs, and Subcards

This section describes how to view the details for an IOM, BIO, or subcard. This section includes:

• How to view the attributes that have been configured for a module:

– “Viewing IOM and BIO Attributes” on page 2-63

– “Viewing GX 550 Subcard Attributes” on page 2-64

• How to view the operational information for a module:

– “Viewing IOM, BIO, and Subcard Operational Information” on page 2-65

• How to view statistics for a 32-port Channelized T1/E1module:

– “Viewing Statistics for the 32-port Channelized T1/E1 Module on CBX 500 and CBX 3500” on page 2-72

Viewing IOM and BIO Attributes

To view the configured attributes for an IOM, BIO, or subcard:






The View Card dialog box appears (Figure 2-52 or Figure 2-53).

Figure 2-52. View Card Dialog Box

Figure 2-53. View Card Dialog Box (Universal IOP)

3. Select the appropriate tab for the attributes you want to view. For a description of the tabs and fields that are available, see the Switch Module Configuration Guide for CBX 3500, CBX 500, GX 550, and B-STDX 9000.



Viewing GX 550 Subcard Attributes

To view the configured attributes for a GX 550 subcard:

1. Display the subcards for a BIO (see “Displaying GX 550 Subcards” on page 2-55).


Viewing Modules


2. Right-click on the subcard and select View from the popup menu.

The View SubCard dialog box appears (Figure 2-54). For a description of the attributes, see the Switch Module Configuration Guide for CBX 3500, CBX 500, GX 550, and B-STDX 9000.

Figure 2-54. View SubCard Dialog Box


The View SubCard dialog box closes.

Viewing IOM, BIO, and Subcard Operational Information

This section describes how to view operational status for CBX 500, CBX 3500, and B-STDX 9000 IOMs, and for GX 550 BIOs and subcards. The operational information dialog boxes also contain manufacturing information.

You cannot view operational information for a module or subcard if you have set the switch to Unmanaged. The switch must be set to Manage.


Viewing Operational Information for an IOM or BIO

To view operational information for an IOM or a BIO:


2. Right-click on the module whose operational information you want to view and select Oper Info from the popup menu.





Figure 2-55. View Card Operational Information Dialog Box (IOM)


Viewing Modules



• General tab, see Table 2-28

• Hardware tab, see Table 2-29

• Software tab, see Table 2-30

• Mesh Status tab (CBX 3500 only), see Table 2-31

Table 2-28. View Card Operational Information: General Tab(IOM or BIO)

Field Description



Redundant Oper Status Displays the redundancy status of this module (Active, Standby, or N/A).

Redundant Group Oper Status

Displays the redundancy status of this group.

Actual Type Displays the module type from the switch.


Actual IOA Type Displays the Input/Output Adapter (IOA) type for the module.

Capability (B-STDX and CBX 3500)

Displays the capability of the module (for example, ATM).

Overload Severity The overload severity of the module. The range is zero (0) to 100. Any value greater than zero indicates that the card is in overload. A severity of 100 indicates that the card is in the highest overload condition and an application must shed all new service requests.

Card State Displays the status of the card.

Module Category Displays the type of module, for example IOM1 or ULC1.




Admin Status Displays one of the following options to set the module administration status:

• Up – (default) The module becomes fully operational at switch start-up. To become operational, the module gets its application code from the Personal Computer Memory Card International Association (PCMCIA) hard drive, which resides in the processor adapter module.

• Down – The module does not come online when you start the switch. The configuration is saved in the database, but is not downloaded to the switch. Use this option when running foreground diagnostics. This setting also enables you to erase PRAM when a module is out of sync.

Redundant Slot ID Displays the number of the slot of the redundant processor module, if applicable.

Redundant Group ID Displays the ID of the redundant group.

Defined Type Displays the configured module’s model type.

Logical Slot ID Displays the number of the slot in which this module is configured.

Defined IOA Type Displays the configured IOA type.

Capability Displays the actual capability of the card, for example, ATM or POS.

Table 2-28. View Card Operational Information: General Tab(IOM or BIO) (Continued)

Field Description


Viewing Modules


Table 2-29. View Card Operational Information: Hardware Tab(IOM or BIO)

Field Description

General






Adapter Module

Product Code Displays the product code of this adaptor module.

Manufacturing Part Number Displays the manufacturing part number for this adaptor module.

Hardware Revision Displays the hardware revision of this adaptor module.

Serial Number Displays the serial number of this adaptor module.


Table 2-30. View Card Operational Information: Software Tab(IOM or BIO)

Field Description

General


Ethernet MAC Address Displays the Ethernet MAC address of this CP or SP in hexadecimal format.

Require Capability Bitmask Displays the required capability bitmask.

Oper Capability Bitmask Displays the operational capability bitmask.






The View Card Operational Information dialog box closes.

Viewing Operational Information for a GX 550 Subcard

To view operational information for a GX 550 subcard:

1. Display the subcards for a BIO (see “Displaying GX 550 Subcards” on page 2-55).

2. Right-click on the subcard and select Oper Info from the popup menu.

Software


Revision ID Displays the ID of the module software version.

Build Date Displays the build date of the switch software version.

NRTS

NRTS Oper State Displays the operational status of this NRTS module.

NRTS Hardware Revision Displays the hardware revision of this NRTS module.

NRTS Out Cell Buffer Size Displays the out cell buffer size of this NRTS module.

Table 2-31. View Card Operational Information: Mesh Status Tab(IOM on CBX 3500 only)

Field Description



Mesh Status Displays the status of the MID.

IOC-P Bus Status Displays the status of the primary OCI-P bus.

IOC-S Bus Status Displays the status of the secondary OCI-S bus.

Table 2-30. View Card Operational Information: Software Tab(IOM or BIO) (Continued)

Field Description


Viewing Modules


The View Subcard Operational Information dialog box appears (Figure 2-56).

Figure 2-56. View SubCard Operational Information Dialog Box (GX 550)


• General tab, see Table 2-32

• Hardware tab, see Table 2-33

• Software tab, see Table 2-34

Table 2-32. View SubCard Operational Information: General Tab

Field Description



Redundant Status Displays the redundancy status of this module (Active, Standby, or N/A).

Type Displays the module type from the switch.


Logical Slot ID Displays the number of the slot in which this module is configured.






The View SubCard Operational Information dialog box closes.

Viewing Statistics for the 32-port Channelized T1/E1 Module on CBX 500 and CBX 3500

You may monitor statistics for the 32-port Channelized T1/E1 module on CBX 500 and CBX 3500 switches.

Note – No other module has support for module-level statistics.

To monitor statistics for the 32-port Channelized T1/E1 module on CBX 500 and CBX 3500 switches:

1. Display the 32-port Channelized T1/E1 module for a CBX 500 or CBX 3500 switch (see “Displaying the Modules for a Switch” on page 2-54).

2. Expand the 32-port Channelized T1/E1 module class node .

The objects that belong to this module appear (Figure 2-57).

Table 2-33. View SubCard Operational Information: Hardware Tab

Field Description






Table 2-34. View SubCard Operational Information: Software Tab

Field Description

General


Software



Viewing Modules


Figure 2-57. Objects on 32-port Channelized T1/E1 Module (Monitor selected)

3. Right-click on the Monitor class node and choose Start from the pop-up menu. The 32-port Channelized T1/E1 Module Statistics Monitoring dialog box appears (Figure 2-58).

Figure 2-58. 32-port Channelized T1/E1 Module Statistics Monitoring Dialog Box

The fields in this dialog box are described in Table 2-35.

Table 2-35. 32-port Channelized T1/E1 Module Statistics

Field Description

FramesDiscarded Displays the number of frames discarded on this module due to exceeding the frame threshold value.

PeakBytesQueued5MinInterval Displays the peak number of bytes queued in the egress side of a connection during the last 5 minute interval.



Viewing Network, Switch, Module, and Physical Port DetailsViewing Physical Ports

4. Choose Reset to refresh the values in this dialog box.

5. When you are done viewing the statistics, choose Close.

The 32-port Channelized T1/E1 Module Statistics Monitoring dialog box closes.

Viewing Physical Ports

This section describes how to view the details for a physical port or subport. This section includes:

• How to display physical ports or subports:

– “Displaying Physical Ports and Subports” on page 2-74

• How to view the attributes that have been configured for a physical port or subport:

– “Viewing IOM and BIO Physical Port Attributes” on page 2-76

– “Viewing GX 550 Subcard Physical Port Attributes” on page 2-78

– “Viewing GX 550 Subcard Subport Attributes (OC48 and OC48c)” on page 2-79

• How to view the operational information for a physical port or subport:

– “Viewing Physical Port Operational Status” on page 2-81

Displaying Physical Ports and Subports

This section describes how to display physical ports and subports in the Navigation Panel. This section includes:

• “Displaying the Physical Ports on a Module” on page 2-75

• “Displaying the Physical Ports on a GX 550 Subcard” on page 2-75

• “Displaying the Subports on a GX 550 Subcard” on page 2-76

PeakFramesQueued5MinInterval Displays the peak number of frames queued in the egress side of a connection during the last 5 minute interval.

TotalBytesQueued Displays the total number of bytes queued on this module at any given instance.

TotalFramesQueued Displays the total number of frames queued for transmission on this module at any given instance.

Table 2-35. 32-port Channelized T1/E1 Module Statistics (Continued)

Field Description




Displaying the Physical Ports on a Module

To display the physical ports that belong to a module:




Figure 2-59. Physical Ports on a Module

3. Expand the module that contains the physical ports.

4. Expand the PPorts class node.

Displaying the Physical Ports on a GX 550 Subcard

To display the physical ports that belong to a GX 550 subcard:




Figure 2-60. Physical Ports on a GX 550 Subcard

3. Expand the module that contains the subcard.


5. Expand the subcard.





Displaying the Subports on a GX 550 Subcard

To display the subports that belong to a GX 550 subcard:




Figure 2-61. Subports on a GX 550 Subcard





7. Expand the physical port that contains the subport.

8. Expand the Subports class node.

Viewing IOM and BIO Physical Port Attributes

To view the configured attributes for a physical port:

1. Display the physical ports for the module (see “Displaying the Physical Ports on a Module” on page 2-75).

2. Right-click on the physical port and select View from the popup menu.

The View PPort dialog box appears (Figure 2-62).




Figure 2-62. View PPort Dialog Box



The View PPort dialog box closes.

Viewing IOM Subport Attributes (Universal IOPs)

To view the configured attributes for a subport on a Universal IOP:


2. Expand the desired PPorts node and the desired Subports node.

3. Right click on the subport and select View from the popup menu.

The View Subport dialog box appears (Figure 2-64).




Figure 2-63. View Subport Dialog Box (ATM Universal IOP)



The View Subport dialog box closes.

Viewing GX 550 Subcard Physical Port Attributes

To view the configured attributes for a physical port on a GX 550 subcard:

1. Display the physical ports for the subcard (see “Displaying the Physical Ports on a GX 550 Subcard” on page 2-75).






Figure 2-64. View PPort Dialog Box (GX 550 Subcard)




Viewing GX 550 Subcard Subport Attributes (OC48 and OC48c)

To view the configured attributes for a subport on a GX 550 subcard:

1. Display the subports for the subcard (see “Displaying the Subports on a GX 550 Subcard” on page 2-76).

2. Right-click on the subport and select View from the popup menu.

The View Subport dialog box appears (Figure 2-65).




Figure 2-65. View Subport Dialog Box (GX 550 Subcard)

3. Select the appropriate tab for the attributes you want to view. For a description of the tabs that are available, see the Switch Module Configuration Guide for CBX 3500, CBX 500, GX 550, and B-STDX 9000.


The View Subport dialog box closes.




Viewing Physical Port Operational Status

This section describes how to view operational status for physical ports and subports. You cannot view operational information for a physical port or subport if you have set the switch to Unmanaged. The switch must be set to Manage.


Viewing Operational Status for a Physical Port on an IOM or BIO

To view operational status for a physical port on an IOM or a BIO:


2. Right-click on the physical port and select Oper Info from the popup menu.

The View PPort Operational Status dialog box appears (Figure 2-66).

Figure 2-66. View PPort Operational Status Dialog Box (IOM or BIO)




Table 2-36 describes the View PPort Operational Status dialog box fields.

Table 2-36. View PPort Operational Status Dialog Box

Field Description

PPort ID Displays the physical port number.

MIB Interface Number Displays the MIB interface number for the physical port. The software assigns a unique number to each physical port on the switch.

Admin Status Displays the port administration status:

Up – The port is active.

Down – The port is disabled or offline.

Operational Status Indicates the operational status of the port, either Up or Down.

Loopback Status Displays the results of the loopback test.

Received FEAC Status (DS3 modules only)

Displays the Far-End Alarm and Control (FEAC) status received by the physical port if C-bit parity is enabled on the Application Mode field. The Received FEAC Status indicates the status of the physical port on the other end of the connection. If you are using M13 as the DS3 application mode, this field displays None.

Port Link Down Reason Displays the reason why a link is down. If the link is up, this field displays None.

Oper Clock Speed (Kbps)(Fast and Gigabit Ethernet modules only)

Displays the physical port’s data rate in kilobits per second (1000 Kbps equals 1 Mbps).

Oper MAC address(Fast and Gigabit Ethernet modules only)

Displays the MAC address that is burned into the module’s Read-Only Memory (ROM).

APS Operational Status

(Not supported on Gigabit Ethernet modules)

Displays the Automatic Protection Switching (APS) operational status.

PL Selector State


Displays the protection line selector state:

• Selected – indicates the protection line is active.

• Released – indicates the working line is active.






The View PPort Operational Status dialog box closes.

Viewing Operational Status for Physical Port Channels on the 1-port STM-1/E1 IMA Enhanced IOM

To view operational status for physical port channels on the 1-port STM-1/E1 IMA Enhanced IOM:


2. Right-click on the E1 Channels class node and select All Channels Oper Info from the pop-up menu. The All Channels Oper Info dialog box appears (Figure 2-67).

Optic Admin Type


Admin type of the pluggable optics. For the OC-48, OC-12, and OC-3, the options are:

• None – No optics

• lr – Single-mode, Long reach

• ir – Single-mode, Intermediate reach

• mm – Multi-mode, Short reach

Note: This field applies only to the Universal I/O modules since these are the only modules that have pluggable optics.

Optic Operational Stat


Same as Optic Admin Type.

Table 2-36. View PPort Operational Status Dialog Box (Continued)

Field Description




Figure 2-67. All Channels Oper Info Dialog Box

The following applies to this dialog box:

• Clicking on one of the 63 buttons in the All Channels Oper Info dialog box will bring up a channel Oper Status dialog box for that channel.

• E1 channels not assigned to IMA groups and not having an LPort remain gray.

• E1 channels not assigned to IMA groups but having an LPort show an X in the button and display red or green to show the status.

• E1 channels assigned to IMA groups display red or green status.

Viewing Operational Status for a GX 550 Subcard Physical Port

To view operational information for a physical port on a GX 550 subcard:

1. Display the physical ports for the subcard (see “Displaying the Physical Ports on a GX 550 Subcard” on page 2-75).

2. Right-click on the physical port and select Oper Info from the popup menu.






Figure 2-68. View PPort Operational Status Dialog Box (GX 550 Subcard)




Viewing Operational Status for a Subport

To view operational information for OC48 and OC48c subport on a GX 550 subcard and on a Universal IOP on the CBX 3500:

1. Display the subports for the subcard (see “Displaying the Subports on a GX 550 Subcard” on page 2-76) or the subport the CBX 3500 Universal IOP (see Viewing IOM Subport Attributes (Universal IOPs)).

2. Right-click on the subport and select Oper Info from the popup menu.

The View PPort Operational Status dialog box for the GX 550 (Figure 2-69) or the Subport Operational Status dialog box for the CBX 3500 appears.

Table 2-36 describes the View PPort Operational Status and the Subport Operational Status dialog box fields.



Viewing Network, Switch, Module, and Physical Port DetailsViewing DS1 Channels

Figure 2-69. View PPort Operational Status Dialog Box (GX 550 Subport)




Viewing DS1 Channels

This section describes how to view the details for a DS1 channel. This section includes:

• “Displaying DS1 Channels” on page 2-86

• “Viewing DS1 Channel Attributes” on page 2-87

• “Viewing Operational Status for a DS1 Channel” on page 2-88

Displaying DS1 Channels

To display the DS1 channels that belong to a physical port:







Figure 2-70. DS1 Channels on a Physical Port

3. Expand the module that contains the physical port and DS1 channel.


5. Expand the physical port.

6. Expand the Channels class node.

Viewing DS1 Channel Attributes

To view the configured attributes for a DS1 channel:

1. Display the DS1 channels for a physical port (see “Displaying DS1 Channels” on page 2-86).

2. Right-click on the channel and select View from the popup menu.

The View Channel dialog box appears (Figure 2-71).



Viewing Network, Switch, Module, and Physical Port DetailsViewing DS1 Channels

Figure 2-71. View Channel Dialog Box (DS1)



The View Channel dialog box closes.

Viewing Operational Status for a DS1 Channel

This section describes how to view operational status for a DS1 channel.

Before You Begin

You cannot view operational information for a channel if you have set the switch to Unmanaged. The switch must be set to Manage.



To View Operational Information for a DS1 Channel


2. Right-click on the channel and select Oper Info from the popup menu.




The View Channel Operational Status dialog box appears (Figure 2-72).

Figure 2-72. View Channel Operational Dialog Box (DS1)

Table 2-37 describes the View Channel Operational Status dialog box fields.



The View Channel Operational Status dialog box closes.

Table 2-37. View Channel Operational Status Dialog Box (DS1)

Field Description


Loopback Status Displays the current loopback status.

Channel Alarm Displays the reason the channel is down.



Viewing Network, Switch, Module, and Physical Port DetailsViewing DS0 Channel Allocation

Viewing DS0 Channel Allocation

To view the DS0 allocation on a physical port:


2. Expand the physical port (Figure 2-73).

Figure 2-73. Channels Class Node

3. Right-click on the Channels class node and select DS0 from the popup menu.

The DS0 Allocation dialog box appears (Figure 2-74).

Figure 2-74. DS0 Allocation Dialog Box

Table 2-38 describes the fields that appear on the dialog box.

Table 2-38. DS0 Allocation Dialog Box

Field Description

Switch Name Displays the name of the switch that this PPort is on.

Slot ID Displays the ID of the slot in which this PPort resides.

IP Address Displays the IP address for the physical port.

PPort ID Displays the number of the PPort.


Viewing E1 Channels


4. Select one of the following button options:

• LPort ID — Displays allocated DS0s marked with the LPort ID.

• LPort Interface — Displays allocated DS0s marked with the Interface Number.

5. If you want to update the information, choose Refresh.

6. When you are done viewing the information, choose Close.

The DS0 Allocation dialog box closes.

Viewing E1 Channels

This section describes how to view the details for an E1 channel. This section includes:

• “Displaying E1 Channels” on page 2-91

• “Viewing E1 Channel Attributes” on page 2-92

• “Viewing Operational Status for an E1 Channel” on page 2-92

Displaying E1 Channels

To display the E1 channels that belong to a physical port:




Figure 2-75. E1 Channels on a Physical Port

3. Expand the module that contains the physical port and E1 channel.



Viewing Network, Switch, Module, and Physical Port DetailsViewing E1 Channels


5. Expand the physical port.

6. Expand the E1 Channels class node.

Viewing E1 Channel Attributes

To view the configured attributes for a E1 channel:

1. Display the E1 channels for the physical port (see “Displaying E1 Channels” on page 2-91).

2. Right-click on the channel and select View from the popup menu.

The View Channel dialog box appears (Figure 2-76).

Figure 2-76. View Channel Dialog Box (E1 Channel)



The View Channel dialog box closes.

Viewing Operational Status for an E1 Channel

This section describes how to view operational status for an E1 channel.

Before You Begin

You cannot view operational information for an E1 channel if you have set the switch to Unmanaged. The switch must be set to Manage.


Viewing E1 Channels




To View Operational Information for an E1 Channel


2. Right-click on the channel and select Oper Info from the popup menu.


Figure 2-77. View PPort Operational Dialog Box (E1 Channel)





Table 2-39. View PPort Operational Status Dialog Box (E1 Channel)

Field Description

Admin Status Displays the E1 channel administration status:

Up – The port is active.

Down – The port is disabled or offline.


Port Link Down Reason Displays the reason why a link is down. If the link is up, this field displays None.



Viewing Network, Switch, Module, and Physical Port DetailsViewing IMA Groups

Viewing IMA Groups

This section contains the following information:

• “Displaying the IMA Groups on a Physical Port” on page 2-94

• “Viewing IMA Group Attributes” on page 2-94

• “Viewing Operational Status for an IMA Group” on page 2-95

Displaying the IMA Groups on a Physical Port

To display the IMA groups on a physical ports:




Figure 2-78. IMA Group on Physical Port



5. Expand the physical port that contains the IMA group.

6. Expand the IMA Groups class node.

Viewing IMA Group Attributes

To view the configured attributes for an IMA Group:

1. Display the IMA groups on a physical port (see “Displaying the IMA Groups on a Physical Port” on page 2-94).

2. Right-click on the IMA group and select View from the popup menu.

The View IMA Group dialog box appears (Figure 2-79).


Viewing IMA Groups


Figure 2-79. View IMA Group Dialog Box



The View IMA Group dialog box closes.

Viewing Operational Status for an IMA Group

This section describes how to view operational status for an IMA group.

Before You Begin

You cannot view operational information for an IMA group if you have set the switch to Unmanaged. The switch must be set to Manage.



To View Operational Information for an IMA Group

1. Display the MA groups on a physical port (see “Displaying the IMA Groups on a Physical Port” on page 2-94).

2. Right-click on the IMA group and select Oper Info from the popup menu.

The IMA Group Operational Info dialog box appears (Figure 2-80).



Viewing Network, Switch, Module, and Physical Port DetailsViewing IMA Groups

Figure 2-80. IMA Group Operational Info Dialog Box

Table 2-40 describes the IMA Group Operational Info dialog box fields.

Table 2-40. IMA Group Operational Info Dialog Box

Field Description

Name Displays the IMA Group Name for this IMA group.

IMA Group ID Indicates the IMA Group ID for this IMA group. The number must be unique on the physical port (the range of values is 1 to 14).

IMA Group Intf Num Identifies the logical interface number assigned to this IMA group.

NE State Indicates the current operational state of the near-end (that is, local end) IMA group. Possible states are:

• Operational

• Not configured

• Start up

• Insufficient links

• Config - Aborted

• Blocked

• Start-up-Ack

• Config aborted - unsupported M

• Config aborted - incompatible symmetry


Viewing IMA Groups




The IMA Group Operational Info dialog box closes.

FE State Indicates the current operational state of the far-end IMA group. Possible states are:

• Operational

• Not configured

• Start up


• Config - Aborted

• Blocked

• Start-up-Ack

• Config aborted - unsupported M

• Config aborted - incompatible symmetry

Failure Status Indicates the reason the IMA group is in the down state. Failure status is based on traffic exchange with the ATM layer.

• No failure

• Start up NE

• Start up FE


Last Change Displays the time-of-day the IMA group last changed operational state (that is, the value of the NE State field).

Tx Clock Mode FE Identifies the Common Transmit Clock (CTC) mode of the far-end IMA group. The transmit clocks of all the physical links within the IMA group are derived from the same clock source.

IMA ID Rx Displays the IMA group receive identifier. The range of values is 1 to 14.

Tx Frame Length FE Indicates the IMA Frame Size (M) to be used by the far-end IMA group in the transmit direction.

Table 2-40. IMA Group Operational Info Dialog Box (Continued)

Field Description



Viewing Network, Switch, Module, and Physical Port DetailsViewing IMA Links

Viewing IMA Links


• “Displaying the IMA Links on an IMA Group” on page 2-98

• “Viewing IMA Link Attributes” on page 2-98

• “Viewing Operational Status for an IMA Link” on page 2-99

Displaying the IMA Links on an IMA Group

To display the IMA links on an IMA group:




Figure 2-81. IMA Links on an IMA Group





7. Expand the IMA group.

8. Expand the IMA Links class node.

Viewing IMA Link Attributes

To view the configured attributes for an IMA link:


Viewing IMA Links


1. Display the IMA links on an IMA group (see “Displaying the IMA Links on an IMA Group” on page 2-98).

2. Right-click on the IMA link and select View from the popup menu.

The View IMA Link dialog box appears (Figure 2-82).

Figure 2-82. View IMA Link Dialog Box



The View IMA Link dialog box closes.

Viewing Operational Status for an IMA Link

This section describes how to view operational status for an IMA link.

Before You Begin

You cannot view operational information for an IMA link if you have set the switch to Unmanaged. The switch must be set to Manage.




Viewing Network, Switch, Module, and Physical Port DetailsViewing IMA Links

To View Operational Information for an IMA Link


2. Right-click on the IMA link and select Oper Info from the popup menu.

The IMA Link OperInfo dialog box appears (Figure 2-83).

Figure 2-83. IMA Link Oper Info Dialog Box

Table 2-41 describes the IMA LinkOper Info dialog box fields.

Table 2-41. IMA Link OperInfo Dialog Box Fields

Field Description

IMA Group Name Displays the IMA Group Name for this IMA group.

IMA Group ID Indicates the IMA Group ID for this IMA group. The number must be unique on the physical port (the range of values is 1 to 14).

Link If Index Indicates the index number assigned to this link in the IMA group link table.

TXLid Displays the transmit (outgoing) link identifier (LID) used on this link at the near end. The range of values is zero (0) to 31.

RxLid Displays the receive (incoming) link identifier (LID) used on this link at the far end. The range of possible values is zero (0) to 31.

NE Rx State Displays the current state of the near-end transmit link.

NE Tx State Displays the current state of the near-end receive link.

FE Rx State Displays the current state of the far-end transmit link, as reported by IMA Control Protocol (ICP) cells.


Monitoring VP Shaping




The IMA Link OperInfo dialog box closes.


ATM modules use VP shaping to control the transmission rate of cells in an ATM network. Both B-STDX 9000 switches and CBX 500/CBX 3500 switches support VP shaping. This section describes how to monitor VP shaping on both platforms.

Monitoring VP Shaping on a B-STDX 9000 Switch


• “Background” on page 2-101

• “To Monitor VP Shaping on B-STDX 9000 Switches” on page 2-102

• “Additional VP Shaping Monitoring” on page 2-104

Background

On B-STDX 9000 switches, VP shaping is supported by the ATM Internetworking Unit (IWU) module, the ATM CS module, and the 12-Port ATM T1/E1 module. The chip in each module contains 15 user-configurable shapers. Each shaper is responsible for controlling the transmission rate of cells across the circuits assigned to it.

FE Tx State Displays the current state of the far-end receive link, as reported by ICP cells.

NE Rx Failure status Displays the current link failure status of the near-end receive link.

FE Rx Failure status Displays the current link failure status of the far-end receive link.

Rel Delay Displays the current differential delay in milliseconds for this link relative to the link with the least delay in this IMA group.

Table 2-41. IMA Link OperInfo Dialog Box Fields (Continued)

Field Description



Viewing Network, Switch, Module, and Physical Port DetailsMonitoring VP Shaping

You can configure each shaper to perform the following types of shaping:

• VC — Shaping is performed on a circuit-by-circuit basis for each circuit assigned to the shaper.

• VP — Shaping is performed on an aggregate (that is, virtual path) basis for all of the circuits assigned to the shaper.

To Monitor VP Shaping on B-STDX 9000 Switches




Figure 2-84. View PPort: Administrative Tab




3. Select the Administrative tab.

Table 2-42 describes the Traffic Shaper fields in the Administrative tab.

4. When you are done viewing the Traffic Shaper fields, choose Close.


Table 2-42. Traffic Shaper Fields

Field Displays...

ID The shaper identifier.

Priority The priority assigned to the shaper. The switch services a shaper’s circuits only if there are no shapers of higher priority waiting to be served. Priority ranges from zero (highest) to 15 (lowest).

Type The type of shaping:

• VC – Shaping is performed on a circuit-by-circuit basis for each circuit assigned to the shaper.

• VP – Shaping is performed on an aggregate (that is, virtual path) basis for all of the circuits assigned to the shaper.

Sust. Cell Rate (cells/sec)

The SCR defines the average rate, in cells per second (CPS), at which the shaper transmits cells. The SCR must be less than or equal to the peak cell rate (PCR) for the shaper. If the SCR is less than the PCR, the shaping algorithm uses the maximum burst size (MBS) value as a credit mechanism to enable cells to be transmitted at the PCR.

Peak Cell Rate (cells/sec)

The peak cell rate (PCR). The PCR defines the maximum rate, in cells per second, at which the shaper transmits cells. The PCR must be greater than or equal to the SCR for the shaper. If the PCR is greater than the SCR, the shaping algorithm uses the maximum burst size (MBS) value as a credit mechanism to enable cells to be transmitted at the PCR.

Max Burst Size (cells) The maximum burst size (MBS) for the shaper, in number of cells. This value determines the maximum number of cells that can be transmitted at the PCR.



Viewing Network, Switch, Module, and Physical Port DetailsMonitoring VP Shaping

Additional VP Shaping Monitoring

You can monitor VP shaping on other logical port types associated with ATM IWU IOMs, ATM CS IOMs, and 12-Port ATM T1/E1 IOMs. VP shaping parameters appear when you monitor the administrative attributes for the following logical port types:

• ATM Direct Trunk

• ATM OPTimum Cell Trunk

• ATM OPTimum Frame Trunk

• ATM Network Internetworking for FR NNI

See “Viewing Logical Port Attributes” on page 6-10 for more information about monitoring logical port administrative attributes.

There are no VP shaping parameters to monitor for ATM UNI DTE/DCE logical ports associated with ATM IWU and ATM CS modules. Instead, shapers are assigned to PVCs that use these logical ports. See Chapter 11, “Circuit Attributes” for details.

Monitoring VP Shaping on a CBX 500/3500 Switch


• “Background” on page 2-104

• “Displaying VP Shaping Information” on page 2-105

• “Description of VP Shaping Field” on page 2-105

• “Additional VP Shaping Monitoring” on page 2-106

Background

On a CBX 500 or CBX 3500 switch, VP shaping is supported by the ATM Flow-Control Processor (ATM FCP) for ATM OPTimum trunks.

Each shaped VP has four transmission queues, one for each QoS class:

• Constant Bit Rate (CBR)

• Variable Bit Rate-Real Time (VBR-RT)

• Variable Bit Rate-Non-Real Time (VBR-NRT)

• Available/Unspecified Bit Rate (ABR/UBR)

VCCs (virtual channel connections) associated with a shaped VP are mapped to the queues according to their QoS classes.

Restrictions

VC shaping applies to the B-STDX 9000 switch only and is not supported on the CBX 500 or CBX 3500 switches.




Displaying VP Shaping Information

To display the VP shaping information:


2. Right-click on the module that is connected to the ATM OPTimum trunk and select View from the popup menu.

The View Card dialog box appears (Figure 2-85).

Figure 2-85. View Card: Traffic Engineering Tab

3. Select the Traffic Engineering tab.

The VP Shaping field is displayed. See “Description of VP Shaping Field” below for details.

4. When you are done viewing the VP shaping parameters, choose Close.


Description of VP Shaping Field

The VP Shaping fields in the Traffic Engineering tab displays the CLP 0+1 (cell loss priority 0+1) and EPD/CLP1 discard (early packet discard/cell loss priority 1 discard) thresholds for each queue in the shaped virtual path (VP).

The CLP 0+1 threshold enables you to reserve buffers before the maximum buffer capacity is reached. The EPD/CLP1 discard threshold is the threshold for both EPD and CLP1 discard.

EPD discard occurs when a cell causes the queue to exceed the threshold. The cells in the current packet are admitted to the queue. However, when the end of the current packet is detected, all of the cells in the next packet are discarded.



Viewing Network, Switch, Module, and Physical Port DetailsDisplaying FDL Information for a T1 Port

CLP1 discard occurs when a cell that has the CLP bit set to 1 causes the queue to exceed the threshold. EPD is not performed, and the cell is discarded.

Table 2-43 describes the VP Shaping fields.

Additional VP Shaping Monitoring

You can also monitor VP shaping on various types of logical ports associated with ATM OPTimum trunks on the CBX 500 or CBX 3500. VP shaping parameters appear when you monitor the administrative attributes of these logical ports. See “Viewing Logical Port Attributes” on page 6-10 for more information about monitoring logical port administrative attributes.

Displaying FDL Information for a T1 Port

If you configured a T1 physical port with Extended Superframe as its circuit type, you can view the facility data link (FDL) parameters, which provide information about the equipment connected to this T1 port.

To view the FDL parameters for a physical port, look in the FDL tab in the View PPort dialog box for the physical port (see “Viewing Physical Ports” on page 2-74). For a description of the parameters, see the Switch Module Configuration Guide for CBX 3500, CBX 500, GX 550, and B-STDX 9000.

Viewing ATM TCA Parameters

You can view Threshold Crossing Alarm (TCA) parameters for physical ports that handle ATM traffic. When TCA is enabled, threshold crossing provides support for traps that are generated by a variety of error conditions. This feature prevents the trap message log from receiving too many messages for the same trap condition.

Table 2-43. VP Shaping

Field Displays...

CBR The CLP 0+1 threshold and EPD/CLP1 discard threshold for the CBR queue.

VBR Real Time The CLP 0+1 threshold and EPD/CLP1 discard threshold for the VBR-RT queue.

VBR Non Real Time The CLP 0+1 threshold and EPD/CLP1 discard threshold for the VBR-NRT queue.

ABR/UBR The CLP 0+1 threshold and EPD/CLP1 discard threshold for the ABR/UBR queue.


Viewing Physical Port and Module Redundancy


To view the TCA parameters for a physical port, look in the TCA tab in the View PPort dialog box for the physical port (see “Viewing Physical Ports” on page 2-74). For a description of the parameters, see the Switch Module Configuration Guide for CBX 3500, CBX 500, GX 550, and B-STDX 9000.

Viewing Physical Port and Module Redundancy


• “Viewing Redundant Modules” on page 2-107

• “Viewing All Redundant Physical Ports Pairs on a Switch” on page 2-107

• “Viewing Working and Protection Ports” on page 2-108

• “Viewing Physical Port APS Attributes” on page 2-108

• “Issuing APS Commands” on page 2-108

Viewing Redundant Modules

To determine whether a module is part of a redundant pair, look in the Physical tab in the View Card dialog box for the module (see “Viewing Physical Ports” on page 2-74).

Viewing All Redundant Physical Ports Pairs on a Switch

To view all of the redundant physical port pairs that are configured on a switch:

1. Open the Rear View panel of the switch. See “Displaying a Switch in the Front/Rear Views” on page 2-39.

2. On the switch’s Rear View panel, right click on any module or filler panel and choose View Port Redundancy from the popup menu.

The Physical Port Pairings dialog box (Figure 2-86) appears.

Figure 2-86. Physical Port Pairings Dialog Box (Redundancy)



Viewing Network, Switch, Module, and Physical Port DetailsViewing Physical Port and Module Redundancy

The Physical Port Pairings dialog box lists all the configured redundant port pairs. You can click on each column heading to sort by the working port, protection port, or redundancy method. The selected sort criteria is shown in bold text.

For each pair, the dialog box lists:

• The port number of the working port.

• The port number of the protection (or backup) port.

• The redundancy method used to switch between ports.

3. When you are done viewing the physical port pairs, choose Close.

The Physical Port Pairings dialog box closes.

Viewing Working and Protection Ports

When you click on either a working or protection port on the switch’s Rear View panel (see “Displaying a Switch in the Front/Rear Views” on page 2-39), arrows appear that show the ports that complete the redundant pair. These arrows are distinguished as follows:

Green arrow – Indicates which physical port of the APS pair is selected and in use as the active port.

White arrow – Indicates which physical port of the APS pair is released and in use as the stand-by port.

Viewing Physical Port APS Attributes

To view the APS attributes for a physical port, look in the APS tab in the View PPort dialog box for the physical port (see “Viewing Physical Ports” on page 2-74). For a description of the attributes, see the Switch Module Configuration Guide for CBX 3500, CBX 500, GX 550, and B-STDX 9000.

Issuing APS Commands

APS commands enable you to clear Signal Fail (SF) and Signal Degrade (SD) conditions manually and to switch network traffic between the working port and the protection port.

To issue APS commands, go to the APS tab in the Modify PPort dialog box for the physical port. See the Switch Module Configuration Guide for CBX 3500, CBX 500, GX 550, and B-STDX 9000 for details.



3

Generating Physical Port Statistics

This chapter describes how to generate and view real-time physical port statistics to monitor and troubleshoot a Lucent switch network.

Supported Statistics

This section describes the types of available physical port statistics.

Physical port summary statistics are available for all input/output modules (IOMs) except for the 60-Port Channelized T1/E1 CE IOM. See “Viewing Physical Port and Subport Summary Statistics” on page 3-2 for details.

The following IOMs provide the additional statistics listed below on physical port activity:

• Channelized IOMs — Alarms and statistics specific to DS1/E1 channel activity on channelized IOMs. See “Viewing DS1 Channel Alarms and Statistics” on page 3-5 and “Viewing E1 Channel Summary Statistics” on page 3-8 for details.

• 4-Port Unchannelized E1 and Channelized E1 IOMs — ITU G.826 statistics. See “Viewing G.826 Statistics for B-STDX 4-Port E1 and B-STDX Channelized E1 Modules” on page 3-9 for details.

• 12-Port E1 IOMs — RFC 1406 statistics and G.826 statistics. See “Viewing RFC 1406 and G.826 Statistics for 12-Port E1, 32-Port E1, and 60-Port Channelized T1/E1 CE Modules” on page 3-11 for details.

• 60-Port Channelized T1/E1 CE IOMs — RFC 1406 statistics and G.826 statistics. See “Viewing RFC 1406 and G.826 Statistics for 12-Port E1, 32-Port E1, and 60-Port Channelized T1/E1 CE Modules” on page 3-11 for details.

• 32-Port E1 IOMs — RFC 1406 statistics and G.826 statistics. See “Viewing RFC 1406 and G.826 Statistics for 12-Port E1, 32-Port E1, and 60-Port Channelized T1/E1 CE Modules” on page 3-11 for details.

In addtion, summary statistics are provided in the following sections:



Generating Physical Port StatisticsViewing Physical Port and Subport Summary Statistics

• Figure “Viewing 2-port ULC Gigabit Ethernet Module Physical Port Summary Statistics” on page 3-18

• “Viewing IMA Group Summary Statistics” on page 3-23

• “Viewing IMA Link Summary Statistics” on page 3-25

For some IOMs, you can also view performance monitoring statistics. See Chapter 4, “Monitoring Physical Port Performance” for details.

Viewing Physical Port and Subport Summary Statistics

To view physical port or subport summary statistics:

1. Display the physical ports or subports for the module or subcard (see “Displaying Physical Ports and Subports” on page 2-74).

2. Expand the physical port or subport for which you want to view summary statistics (Figure 3-1).

Figure 3-1. Monitoring Node on Physical Port

3. Right-click on the Monitoring node, and select Start from the popup menu.

The PPort Statistics Monitoring dialog box appears (Figure 3-2).

The PPort Statistics Monitoring dialog box displays cumulative statistics and throughput data for the transmission and receipt of data on the physical port.

Table 3-1 describes the statistics. The statistics that appear vary, depending on the type of traffic on port. For example, if the physical port supports only ATM traffic, only cumulative statistics for cell traffic appear. If both ATM and Frame Relay traffic are supported, cumulative statistics for both cell and frame traffic appear.

Beta Draft ConfidentialGenerating Physical Port Statistics

Viewing Physical Port and Subport Summary Statistics


Figure 3-2. PPort Statistics Monitoring Dialog Box

Table 3-1. Physical Port Summary Statistics

Statistic Description

General Cumulative Statistics

Number of Octets The total number of octets (bytes) received and transmitted since the last reset.

Number of Frames The total number of frames received and transmitted since the last reset.

Frames Discarded The total number of frames discarded since the last reset. If the system is discarding frames, graceful discard is set to Off. The switch does not discard frames if graceful discard is set to On. The graceful discard option is set during circuit configuration.

Number of Errors The total number of frame errors. This value includes all green, amber, and red frame errors.

Number of Cells The total number of cells received and transmitted by the port since the last reset.

Error Cells The total number of cells that were received with a Header Error Control (HEC) error. An HEC error indicates a discrepancy between what the port expected in the header and what was actually received. The number of cell errors is indicated in the Received column. The Transmitted column does not apply.



Generating Physical Port StatisticsViewing Physical Port and Subport Summary Statistics

4. For a physical port on a 550 ES DS3 ATM/CE module, you can also view AAL1 statistics by selecting AAL1 Stats under the Monitor node. Table 3-2 describes the AAL1 statistics.

Output Buffer Discarded Cells

The number of discarded cells.

ThroughPut

Bits Per Sec The total number of bits received and transmitted each second.

Frames Per Sec The total number of frames received and transmitted each second.

Cells Per Sec The total number of cells received and transmitted each second.

Utilization

Utilization (%) The amount of traffic queued for transmission on a physical port, measured as a percentage of the physical port speed. This value does not measure the amount of bandwidth of the physical port in use. For this reason, the value can exceed 100%.

Table 3-2. DS3 ATM/CE Port AAL1 Statistics


Number of data cells received

The number of data cells received.

Number of data cells transmitted

The number of data cells that arrived successfully at the Circuit Emulation Service (CES) Interface.

Number of AAL1 header errors detected

The number of ATM adaptation layer 1 header errors detected, including correctable and uncorrectable Cyclic Redundancy Check (CRC) errors, and parity errors.

Number of instances in which SDT pointer not present

The number of events in which the AAL1 reassembler determined that a Structured Data Transfer (SDT) pointer has been misallocated, and must be reacquired.

Note: For unstructured CES modes, which do not use pointers, this number should be zero.

Table 3-1. Physical Port Summary Statistics (Continued)



Viewing DS1 Channel Alarms and Statistics


5. Choose Reset to set the current statistics to zero and begin a new collection of statistics, and to update the time in the Reset Time field.


The PPort Statistics Monitoring dialog box closes.


This section describes how to view alarm status and summary statistics for DS1 channels on Channelized DS3, DS3/1/0, and DS3/1/0 FR/IP IOMs. These IOMs are found on either B-STDX or CBX switches.

Viewing DS1 Channel Alarms

To view the alarm status of all DS1 channels on a physical port:

Number of parity check failures

The number of events in which the AAL1 reassembler expects a structured data pointer, but detects a parity check failure instead.


Number of incoming AAL1 SAR-PDU sequence number errors

The number of times that the sequence number of an incoming AAL1 Type 1 SAR-PDU causes a transition from the “sync” state to the “out-of-sequence” state, as defined by ITU-T I.363.1.

Number of lost cells The number of cells that were lost in the network, prior to processing by the CES Internetworking Function (IWF) layer.

Number of AAL1 sequence violations

The number of AAL1 sequence violations that the AAL Convergence sublayer interprets as misinserted cells, as defined by ITU-T I.363.1.

Number of buffer underflows

The number of times that the CES reassembly buffer underflows. A single buffer underflow is counted whenever there is a continuous underflow due to a loss of ATM cell flow.

If the CES IWF has multiple buffers (for example, a cell-level buffer and a bit-level buffer), then each of the buffer overflows is added to the total number.

Number of buffer overflows

The number of times that the CES reassembly buffer overflows.

If the CES IWF has multiple buffers (for example, a cell-level buffer and a bit-level buffer), then each of the buffer overflows is added to the total number.

Table 3-2. DS3 ATM/CE Port AAL1 Statistics (Continued)




Generating Physical Port StatisticsViewing DS1 Channel Alarms and Statistics


2. Expand the physical port for which you want to view DS1 channel alarms (Figure 3-3).

Figure 3-3. Channels Class Node

3. Right-click on the Channels class node, and select Chan Alarm Status from the popup menu.

The Channel Alarm Status dialog box appears (Figure 3-4).

Figure 3-4. Channel Alarm Status Dialog Box

Table 3-3 describes the possible alarm states.

4. Choose the Refresh button to refresh the dialog box.

Table 3-3. DS1 Channel Alarm States

Alarm State Description

Normal Normal operating state

Red Loss of frame (LOF) or loss of signal (LOS)

Yellow Far end is in a red alarm state

Blue Downstream equipment failure




5. When you are done viewing the alarm status, choose Close.

The Channel Alarm Status dialog box closes.

Viewing DS1 Channel Summary Statistics

To view summary statistics for selected DS1 channels on Channelized DS3 or DS3/1/0 FR/IP modules:


2. Expand the DS1 channel for which you want to view summary statistics.


The Channel Statistics Monitoring dialog box appears (Figure 3-5).

Table 3-4 describes the statistics.

Figure 3-5. Channel Statistics Monitoring Dialog Box

Table 3-4. DS1 Channel Summary Statistics



Number Of Octets The total number of octets (bytes) received and transmitted since the last reset.

Number Of Frames The total number of frames received and transmitted since the last reset.



Generating Physical Port StatisticsViewing E1 Channel Summary Statistics



The Channel Statistics Monitoring dialog box closes.

Viewing E1 Channel Summary Statistics

To view summary statistics for selected E1 channels on 1-Port Channelized STM-1/E1 IMA modules:


2. Expand the channel for which you want to view summary statistics.


The PPort Statistics Monitoring dialog box appears.


Number Of Discards The total number of frames discarded since the last reset.

Number Of Errors The total number of frame errors. This value includes all green, amber, and red frame errors.

ThroughPut

Throughput Bits per Sec The total number of bits received and transmitted each second.

Throughput Frames per Sec The total number of frames received and transmitted each second.

Utilization

Utilization The amount of traffic queued for transmission on a channel measured, as a percentage of the channel speed. This value does not measure the amount of bandwidth of the channel in use. For this reason, the value can exceed 100%.

Table 3-4. DS1 Channel Summary Statistics (Continued)



Viewing G.826 Statistics for B-STDX 4-Port E1 and B-STDX Channelized E1 Modules




The PPort Statistics Monitoring dialog box closes.

Viewing G.826 Statistics for B-STDX 4-Port E1 and B-STDX Channelized E1 Modules

This section describes how to view G.826 statistics for physical ports on the B-STDX 4-Port E1 module and on B-STDX channelized E1 modules. These statistics provide performance information for digital transmission paths.

To view G.826 statistics for B-SDX 12-Port E1 modules, see “Viewing RFC 1406 and G.826 Statistics for 12-Port E1, 32-Port E1, and 60-Port Channelized T1/E1 CE Modules” on page 3-11.

Table 3-5. E1 Channel Summary Statistics

Field Description

Cumulative Statistics

Number of Cells Displays the total number of octets (bytes) received and transmitted since the last reset.

Error Cells Displays the total number of cell errors received and transmitted since the last reset.

Output Buffer Discarded Cells

Displays the total number of cells discarded since the last reset. If the system is discarding cells, graceful discard is set to Off. The switch does not discard cells if graceful discard is set to On. The graceful discard option is set during the configuration of a circuit.

ThroughPut

Cells per Sec Displays the total number of bits received and transmitted each second.

Utilization

Utilization Displays the amount of traffic queued for transmission on a physical port, measured as a percentage of the physical port speed. This value does not measure the amount of physical port bandwidth being used. For this reason, the value displayed in this field can exceed 100%.



Generating Physical Port StatisticsViewing G.826 Statistics for B-STDX 4-Port E1 and B-STDX Channelized E1 Modules

To view G.826 statistics:


2. Right-click on the physical port for which you want to view G.826 statistics, and select E1 Statistics from the popup menu.

The E1 Performance Monitoring Statistics dialog box appears (Figure 3-6).

Figure 3-6. E1 Performance Monitoring Statistics Dialog Box (G.826 Statistics)

Table 3-6 describes the G.826 statistics.

Table 3-6. G.826 Statistics


E1 Current Statistics

Error Block Count A count of detected block errors within a 15-minute interval. Block errors occur in frames that have CRC or framing errors.

Error Seconds Count A count of one-second intervals with one or more errored blocks or at least one defect within a 15-minute interval.

Severely Error Seconds Count

A count of one-second periods with either 30% errored blocks or at least one defect within a 15-minute interval.

Background Block Errors Count

A count of block errors that were detected but did not occur as part of a severely errored second within a 15-minute interval.

Error Seconds Ratio A ratio of accumulated errored seconds to total seconds in the available time.

Severely Error Seconds Ratio

A ratio of accumulated severely errored seconds to total seconds in the available time.


Viewing RFC 1406 and G.826 Statistics for 12-Port E1, 32-Port E1, and 60-Port Channelized T1/E1 CE


3. Choose Refresh to set the current statistics to zero, and begin a new collection of statistics, and update the time in the Refresh Time field.


The E1 Performance Monitoring Statistics dialog box closes.

Viewing RFC 1406 and G.826 Statistics for 12-Port E1, 32-Port E1, and 60-Port Channelized T1/E1 CE Modules

This section describes how to view RFC 1406 and G.826 statistics for E1 physical ports on the 12-Port E1, 32-Port E1, and 60-Port Channelized T1/E1 CE modules.

Types of E1 Statistics Available

For each physical port on a 12-Port E1, 32-Port E1, and 60-Port Channelized T1/E1 CE modules, you can view statistics based on:

• RFC 1406

• ITU G.826

The following categories of statistics are available:

• Configuration — E1 configuration statistics.

• Current — Up-to-date statistics. The counter tracks errors encountered by the E1 interface during the previous 15-minute interval.

• Interval — Statistics for the previous 24 hours based on a specified number of 15-minute intervals.

• Total — Statistics for the sum of all intervals and the current interval. The counter tracks errors encountered by the E1 interface in the previous 24-hour interval.

Viewing E1 Statistics

To view the RFC 1406 and G.826 E1 statistics:


Background Block Error Ratio

A ratio of background block errors to total received blocks (E1 frames) in the available time.

Table 3-6. G.826 Statistics (Continued)




Generating Physical Port StatisticsViewing RFC 1406 and G.826 Statistics for 12-Port E1, 32-Port E1, and 60-Port Channelized T1/E1 CE

2. Right-click on the physical port for which you want to view G.826 statistics, and select E1 Statistics from the popup menu.

The E1 Performance Monitoring Statistics dialog box appears (Figure 3-7).

Figure 3-7. E1 Performance Monitoring Statistics Dialog Box

3. Select RFC 1406 or ITU G.826 from the PM Standard pull-down list.

4. Select one of the following types of statistics:

• Configuration — View configuration statistics, including error and performance statistics. See Table 3-7 on page 3-12.

• Current — View statistics accumulating in the present interval. See Table 3-8 on page 3-13 for RFC 1406 statistics, and Table 3-9 on page 3-15 for G.826 statistics.

• Interval — View statistics that were collected during previous, user-specified 15-minute intervals. If you select this option, you must specify a polling interval. The Interval (1...96) function sets the time interval for collecting statistical data during the current session of Navis EMS-CBGX. Specify a number between 1 and 96 in the Interval (1...96) field. For example, interval 4 displays statistics from the previous hour. See Table 3-10 on page 3-15 for RFC 1406 statistics, and Table 3-11 on page 3-16 for G.826 statistics.

• Total — View statistics for the sum of all intervals and the current interval.

See Table 3-12 on page 3-17 for RFC 1406 statistics, and Table 3-13 on page 3-18 for G.826 statistics.

Table 3-7. E1 Configuration Statistics (RFC 1406 and G.826)


If Index The unique interface number for this interface on the switch.

Time Elapsed The number of elapsed seconds since the start of the current error-measurement period.




Valid Intervals The number of previous intervals for which valid data was collected.

Line Type The E1 link framing method implemented on this circuit (for example, E1 CRC MF, which is the same as TS16 enabled and CRC4 enabled).

Line Coding The type of zero code suppression used on the link. The E1 link uses High-Density Bipolar 3 (HDB3). Another option is alternate mark inversion (AMI), also known as jammed-bit Zero encoding.

Circuit Identifier The transmission vendor’s circuit identifier.

Loopback Config The current loopback status of the E1 interface (for example, No Loop).

Line Status The interface line status (for example, No Alarm). Contains loopback, failure, received alarm, and transmitted alarm information.

Signal Mode The E1 signal mode, which indicates the method used to reserve bits for signaling. A value of None means that no bits are reserved for signaling.

Transmit Clock Source The source of transmit clock (for example, Local Timing, which is the same as Internal).

Table 3-8. E1 Current Statistics (RFC 1406)


Current Errored Seconds

The number of errored seconds (ES) encountered by the E1 interface in the current 15-minute interval.

An ES is a one-second interval with any path code violations, out-of-frame defects, controlled slips, or alarm indication signal (AIS) defects.

Current Severely Errored Seconds

The number of p-bit severely errored seconds (SES) encountered by the E1 interface in the current 15-minute interval.

SES is a one-second interval with:

• (For E1-CRC) 832 or more path code violations or any out-of-frame defects.

• (For E1, non-CRC) 2048 or more line coding violations.

Table 3-7. E1 Configuration Statistics (RFC 1406 and G.826) (Continued)





Current Severely Errored Framing Seconds

The number of severely errored framing seconds (SEFS) encountered by the E1 interface in the current 15-minute interval.

A SEFS is a one-second interval with any out-of-frame defects or AIS defects.

Current Unavailable Seconds

The number of unavailable seconds (UAS) encountered by the E1 interface in the current 15-minute interval.

See the RFC 1406 Internet standard for details.

Current Controlled Slip Seconds

The number of controlled slip (CS) seconds encountered by the E1 interface in the current 15-minute interval.

A CS second is a one-second interval with any replications or deletions of the payload bits of a DS1 frame.

Current Path Coding Violations

The number of path coding violations encountered by the E1 interface in the current 15-minute interval.

A path coding violation (PCV) is a:

• (For E1-CRC) Cyclic redundancy check error.

• (For E1, non-CRC) Frame synchronization bit error.

Current Line Errored Seconds

The number of line errored seconds (LES) encountered by the E1 interface in the current 15-minute interval.

LES is a one-second interval with any line code violations.

Current Bursty Errored Seconds

The number of bursty errored seconds (BES) encountered by the E1 interface in the current 15-minute interval.

BES is a one-second interval with 1 to 319 path coding violations (but no severely errored frame defects, incoming AIS defects, or controlled slips).

Current Degraded Minutes

The number of degraded minutes encountered by the E1 interface in the current 15-minute interval.

A degraded minute is a one-minute interval in which the line error rate is between 1 bit error per thousand bits and 1 bit error per one million bits.

Current Line Code Violations

The number of line code violations (LCVs) encountered by the E1 interface in the current 15-minute interval.

LCV is either a bipolar violation (BPV) or excessive zeroes (EXZ) error.

Table 3-8. E1 Current Statistics (RFC 1406) (Continued)





Table 3-9. E1 Current Statistics (G.826)


Errored Seconds Count A count of one-second intervals with one or more errored blocks or at least one defect within the current 15-minute interval.

Severely Errored Seconds Count

A count of one-second periods with either 30% errored blocks or at least one defect within the current 15-minute interval.

Errored Block Count The number of block errors encountered by the E1 interface in the current 15-minute interval. Block errors occur in frames that have CRC or framing errors.


A count of block errors that were detected but did not occur as part of a SES within the current 15-minute interval.

Errored Seconds Ratio A ratio of accumulated ES to total seconds within the current 15-minute interval.

Severely Errored Seconds Ratio

A ratio of accumulated SES to total seconds within the current 15-minute interval.

Background Block Errors Ratio

A ratio of background block errors to total received blocks (E1 frames) within the current 15-minute interval.

Table 3-10. E1 Interval Statistics (RFC 1406)


Interval Number The specified interval number.

Interval Errored Seconds

The number of ES encountered by the E1 interface over the user-specified interval.

See Table 3-8 on page 3-13 for more information about ES.

Interval Severely Errored Seconds

The number of SES encountered by the E1 interface over the user-specified interval.

See Table 3-8 on page 3-13 for more information about SES.

Interval Severely Errored Framing Seconds

The number of SEFS encountered by the E1 interface over the user-specified interval.

See Table 3-8 on page 3-13 for more information about SEFS.

Interval Unavailable Seconds

The number of UAS encountered by the E1 interface over the user-specified interval.

See Table 3-8 on page 3-13 for more information about UAS.




Interval Controlled Slip Seconds

The number of CS seconds encountered by the E1 interface over the user-specified interval.

See Table 3-8 on page 3-13 for more information about CS seconds.

Interval Path Coding Violations

The number of PCV encountered by the E1 interface over the user-specified interval.

See Table 3-8 on page 3-13 for more information about PCV.

Interval Line Errored Seconds

The number of LES encountered by the E1 interface over the user-specified interval.

See Table 3-8 on page 3-13 for more information about LES.

Interval Bursty Errored Seconds

The number of BES encountered by the E1 interface over the user-specified interval.

See Table 3-8 on page 3-13 for more information about BES.

Interval Degraded Minutes

The number of degraded minutes encountered by the E1 interface over the user-specified interval.

See Table 3-8 on page 3-13 for more information about degraded minutes.

Interval Line Code Violations

The number of LCV encountered by the E1 interface over the user-specified interval.

See Table 3-8 on page 3-13 for more information about LCV.

Table 3-11. E1 Interval Statistics (G.826)


Interval Number The specified interval number.

Errored Seconds Count A count of one-second intervals with one or more errored blocks or at least one defect within the user-specified interval.


A count of one-second periods with either 30% errored blocks or at least one defect within the user-specified interval.

Errored Block Count The number of block errors encountered by the E1 interface within the user-specified interval. Block errors occur in frames that have CRC or framing errors.


A count of block errors that were detected but did not occur as part of a SES within the user-specified interval.

Table 3-10. E1 Interval Statistics (RFC 1406) (Continued)





Table 3-12. E1 Total Statistics (RFC 1406)


Total Errored Seconds The number of ES encountered by the E1 interface for the sum of all intervals.

See Table 3-8 on page 3-13 for more information about ES.

Total Severely Errored Seconds

The number of severely errored seconds encountered by the E1 interface for the sum of all intervals.

See Table 3-8 on page 3-13 for more information about severely errored seconds.

Total Severely Errored Framing Seconds

The number of SEFS encountered by the E1 interface for the sum of all intervals.

See Table 3-8 on page 3-13 for more information about SEFS.

Total Unavailable Seconds

The number of UAS encountered by the E1 interface for the sum of all intervals.

See Table 3-8 on page 3-13 for more information about UAS.

Total Controlled Slip Seconds

The number of CS seconds encountered by the E1 interface for the sum of all intervals.

See Table 3-8 on page 3-13 for more information about CS seconds.

Total Path Coding Violations

The number of PCV encountered by the E1 interface for the sum of all intervals.

See Table 3-8 on page 3-13 for more information about PCV.

Total Line Errored Seconds

The number of LES encountered by the E1 interface for the sum of all intervals.

See Table 3-8 on page 3-13 for more information about LES.

Total Bursty Errored Seconds

The number of BES encountered by the E1 interface for the sum of all intervals.

See Table 3-8 on page 3-13 for more information about BES.

Total Degraded Minutes

The number of degraded minutes encountered by the E1 interface for the sum of all intervals.

See Table 3-8 on page 3-13 for more information about degraded minutes.

Total Line Code Violations

The number of LCV encountered by the E1 interface for the sum of all intervals.

See Table 3-8 on page 3-13 for more information about LCV.



Generating Physical Port StatisticsViewing 2-port ULC Gigabit Ethernet Module Physical Port Summary Statistics

Viewing 2-port ULC Gigabit Ethernet Module Physical Port Summary Statistics

To view physical port summary statistics for the 2-port ULC Gigabit Ethernet module:

1. Follow steps 1-3 in “Viewing Physical Port and Subport Summary Statistics” on page 3-2. The 2-port ULC Gigabit Ethernet Module PPort Statistics Monitoring dialog box appears (Figure 3-8).

Table 3-13. E1 Total Statistics (G.826)


Errored Seconds Count A count of one-second intervals with one or more errored blocks or at least one defect for the sum of all intervals.


A count of one-second periods with either 30% errored blocks or at least one defect for the sum of all intervals.

Errored Block Count The number of block errors encountered by the E1 interface for the sum of all intervals. Block errors occur in frames that have CRC or framing errors.


A count of block errors that were detected but did not occur as part of a SES for the sum of all intervals.




Figure 3-8. 2-port ULC Gigabit Ethernet Module PPort Statistics Monitoring Dialog Box

Table 3-14 describes the summary statistics in this screen.

Table 3-14. 2-port ULC Gigabit Ethernet Module PPort Statistics Monitoring Summary Statistics



FramesOKHigh The total (high) number of good frames received and transmitted since the last reset.

FramesOKLow The total (low) number of good frames received and transmitted since the last reset.

OctetsOKHigh The total (high) number of good octets (bytes) received and transmitted since the last reset.




OctetsOKLow The total (low) number of good octets (bytes) received and transmitted since the last reset.

FramesHigh The total (high) number of frames received and transmitted since the last reset.

FramesLow The total (low) number of frames received and transmitted since the last reset.

OctetsHigh The total (high) number of octets (bytes) received and transmitted since the last reset.

OctetsLow The total (low) number of octets (bytes) received and transmitted since the last reset.

UnicastFramesOKHigh The total (high) number of good Unicast frames received and transmitted since the last reset.

UnicastFramesOKLow The total (low) number of good Unicast frames received and transmitted since the last reset.

MulticastFramesOKHigh The total (high) number of good Multicast frames received and transmitted since the last reset.

MulticastFramesOKLow The total (low) number of good Multicast frames received and transmitted since the last reset.

BroadcastFramesOKHigh The total (high) number of good Broadcast frames received and transmitted since the last reset.

BroadcastFramesOKLow The total (low) number of good Broadcast frames received and transmitted since the last reset.

UnicastFramesHigh The total (high) number of Unicast frames received and transmitted since the last reset.

UnicastFramesLow The total (low) number of Unicast frames received and transmitted since the last reset.

MulticastFramesHigh The total (high) number of Multicast frames received and transmitted since the last reset.

MulticastFramesLow The total (low) number of Multicast frames received and transmitted since the last reset.

BroadcastFramesHigh The total (high) number of Broadcast frames received and transmitted since the last reset.

Table 3-14. 2-port ULC Gigabit Ethernet Module PPort Statistics Monitoring Summary Statistics (Continued)





BroadcastFramesLow The total (low) number of Broadcast frames received and transmitted since the last reset.

TaggedFramesOKHigh The total (high) number of good Tagged frames received and transmitted since the last reset.

TaggedFramesOKLow The total (low) number of good Tagged frames received and transmitted since the last reset.

TaggedFramesHigh The total (high) number of Tagged frames received and transmitted since the last reset.

TaggedFramesLow The total (low) number of Tagged frames received and transmitted since the last reset.

Frames64OctetsHigh The total (high) number of frames, 64 octets long, received and transmitted since the last reset.

Frames64OctetsLow The total (low) number of frames, 64 octets long, received and transmitted since the last reset.

Frames65to127OctetsHigh The total (high) number of frames, 65 to 127 octets long, received and transmitted since the last reset.

Frames65to127OctetsLow The total (low) number of frames, 65 to 127 octets long, received and transmitted since the last reset.





Frames512to1023OctetsHigh

The total (high) number of frames, 512 to 1023 octets long, received and transmitted since the last reset.

Frames512to1023OctetsLow

The total (low) number of frames, 512 to 1023 octets long, received and transmitted since the last reset.

Frames1024to1518OctetsHigh

The total (high) number of frames, 1024 to 1518 octets long, received and transmitted since the last reset.






Frames1024to1518OctetsLow

The total (low) number of frames, 1024 to 1518 octets long octets long, received and transmitted since the last reset.

Frames1519toMAXOctetsHigh

The total (high) number of frames, 1519 to MAX octets long, received and transmitted since the last reset.

Frames1519toMAXOctetsLow

The total (low) number of frames, 1519 to MAX octets long, received and transmitted since the last reset.

JumboOctetsOKHigh Need attribute description.

JumboOctetsOKLow Need attribute description.

FrameCheckSequenceErrors

The total number of frames, 64 to 1518 octets long, that had either a bad Frame Check Sequence (FCS) with an integral number of octets (FCS Error) or a bad FCS with a nonintegral number of octets (Alignment Error), received and transmitted since the last reset.

SymbolError Need attribute description.

InRangeLengthErrors Need attribute description.

FramesTooLongErrors The total number of oversized frames, longer than 1518 octets, received and transmitted since the last reset.

Jabbers The total number of frames, longer than 1518 octets, that had either a bad Frame Check Sequence (FCS) with an integral number of octets (FCS Error) or a bad FCS with a nonintegral number of octets (Alignment Error), received and transmitted since the last reset.

Fragments The total number of frames, shorter than 64 octets, that had either a bad Frame Check Sequence (FCS) with an integral number of octets (FCS Error) or a bad FCS with a nonintegral number of octets (Alignment Error), received and transmitted since the last reset.

UndersizedFrames The total number of undersized frames, shorter than 64 octets, received and transmitted since the last reset.

InvalidPAUSEFrames The total number of invalid PAUSE frames (related to Flow Control) received and transmitted since the last reset.

PAUSEMACControlFramesOKHigh

The total (high) number of good MAC PAUSE control frames (related to Flow Control) received and transmitted since the last reset




Viewing IMA Group Summary Statistics




The 2-port ULC Gigabit Ethernet module PPort Statistics Monitoring dialog box closes.

Viewing IMA Group Summary Statistics

To view summary statistics for an IMA group:


2. Expand the IMA group for which you want to view summary statistics.


The IMA Group Statistics Monitoring dialog box appears.


MACControlFramesOKHigh

The total (high) number of good MAC control frames with unsupported opcodes received and transmitted since the last reset.

SystemError

MACPAUSEControlFrames The total number of MAC PAUSE control frames (related to Flow Control) received and transmitted since the last reset.

MACControlFrames The total number of MAC control frames with unsupported opcodes received and transmitted since the last reset.

ThroughPut

Bits Per Sec The total number of bits received and transmitted each second.

Utilization

Utilization (%) The amount of traffic queued for transmission on a physical port, measured as a percentage of the physical port speed. This value does not measure the amount of bandwidth of the physical port in use. For this reason, the value can exceed 100%.





Generating Physical Port StatisticsViewing IMA Group Summary Statistics

Table 3-15. IMA Group Summary Statistics


Running Seconds The amount of time (in seconds) since the last reset time.

Unavailable Seconds Count of one-second intervals where the IMA Group Traffic State Machine is down.

NE Group Failures The number of times a near-end group failure (Config-Aborted, Insufficient-Links) has been reported since power-up or reboot.

FE Group Failures The number of times a far-end group failure (Config-Aborted-FE, Insufficient-Links-FE, Blocked-FE) has been reported since power-up or reboot. This is an optional attribute.

Available Tx Cell Rate The current cell rate (truncated value in CPS) provided by this IMA group in the transmit direction, considering all the transmit links in the Active state.

Available Rx Cell Rate The current cell rate (truncated value in CPS) provided by this IMA group in the receive direction, considering all the receive links in the Active state.

Active Links Transmitting

The number of links that are configured to transmit and are currently Active in this IMA group.

Active Links Receiving The number of links that are configured to receive and are currently Active in this IMA group.

Transmit Timing Reference Link

The Interface Index of the transmit timing reference link to be used by the near-end for IMA data cell clock recovery from the ATM layer.

Receive Timing Reference Link

The Interface Index of the receive timing reference link to be used by the near-end for IMA data cell clock recovery toward the ATM layer.

Maximum Differential Delay

The maximum number of milliseconds of differential delay among the links that will be tolerated on this interface.

Beta Draft ConfidentialGenerating Physical Port StatisticsViewing IMA Link Summary Statistics




The IMA Group Statistics Monitoring dialog box closes.

Viewing IMA Link Summary Statistics

To view summary statistics for an IMA link:


2. Expand the IMA link for which you want to view summary statistics.


The IMA Link Statistics Monitoring dialog box appears.


Valid Day The number of previous 15-minute intervals for which valid data was collected. The value is 96 unless the IMA group table entry was created within the last 24 hours, in which case the value is the number of completed 15-minute intervals since the IMA group table entry was created.

In the case where the agent is a proxy, it is possible that some intervals are unavailable. In this case, this value is the maximum interval number for which valid data is available.

This attribute is only mandatory when the IMA Group Interval Statistics and/or IMA Group Total Statistics objects are implemented.

Day Time Elapsed The number of seconds that have elapsed since the beginning of the current measurement period. This field is displayed only when the IMA Group Current Statistics are implemented.

Table 3-15. IMA Group Summary Statistics (Continued)


Table 3-16. IMA Link Summary Statistics


IMA Violations IV-IMA Control Protocol Cell (ICP) violations: count of errored, invalid or missing ICP cells; except during SES-IMA or UAS-IMA conditions in the current 15 minute interval.



Generating Physical Port StatisticsViewing IMA Link Summary Statistics

OIF Anomalies The number of out of IMA frame (OIF) anomalies, except during SES-IMA or UAS-IMA conditions, at the near-end in the current 15 minute interval. This is an optional attribute.

NE Severe Errored Seconds

Count of one second intervals containing 30% or more of the ICP cells counted as IV-IMAs, or one or more link defects, loss of IMA frame (LIF) defects, or link out of delay synchronization (LODS) defects, except during UAS-IMA condition. Examples of link defects include LOS, out-of-frame alarm/loss of framing (OOF/LOF), AIS, or loss of cell delineation (LCD).

FE Severe Errored Seconds

Count of one second intervals containing one or more remote defect indicator-IMA (RDI-IMA) defects, except during UAS-IMA far end (FE) condition.

NE Unavailable Seconds

Count of unavailable seconds at near-end (NE). Unavailability begins at the onset of 10 contiguous SES-IMA seconds and ends at the onset of 10 contiguous seconds with no SES-IMA.

FE Unavailable Seconds

Count of unavailable seconds at far-end. Unavailability begins at the onset of 10 contiguous SES-IMA-FE seconds and ends at the onset of 10 contiguous seconds with no SES-IMA-FE.

NE Tx Unusable Seconds

Count of Tx unusable seconds (UUS) at the near-end Tx link state machine (LSM).

NE Rx Unusable Seconds

Count of Rx UUS at the near-end Rx LSM.

FE Tx Unusable Seconds

Count of UUS with Tx unusable indications from the FE Tx LSM.

FE Rx Unusable Seconds

Count of UUS with Rx unusable indications from the FE Rx LSM.

NE Tx Number Failures The number of times an NE transmit failure alarm condition has been entered on this link.

NE Rx Number Failures

The number of times an NE receive failure alarm condition has been entered on this link.

FE Tx Number Failures The number of times a FE transmit failure alarm condition has been entered on this link.

FE Rx Number Failures The number of times a FE receive failure alarm condition has been entered on this link.

Table 3-16. IMA Link Summary Statistics (Continued)


Beta Draft ConfidentialGenerating Physical Port StatisticsViewing IMA Link Summary Statistics




The IMA Link Statistics Monitoring dialog box closes.

Tx Stuffs Count of stuff events inserted in the transmit direction.

Rx Stuffs Count of stuff events detected in the receive direction.

Valid Interval The number of intervals for which data is available.

Invalid Interval The number of intervals for which data is unreliable due to the occurrence of link defects (for example, LOS).

Time Elapsed The time elapsed in the current time period.

Day Time Elapsed The number of seconds that have elapsed since the beginning of the current measurement period. This field is displayed only when the IMA Group Current Statistics are implemented.

Valid Day The number of previous 15-minute intervals for which valid data was collected. The value is 96 unless the IMA group table entry was created within the last 24 hours, in which case the value is the number of completed 15-minute intervals since the IMA group table entry was created.

In the case where the agent is a proxy, it is possible that some intervals are unavailable. In this case, this value is the maximum interval number for which valid data is available.

This attribute is only mandatory when the IMA Group Interval Statistics and/or IMA Group Total Statistics objects are implemented.

Table 3-16. IMA Link Summary Statistics (Continued)




Generating Physical Port StatisticsViewing IMA Link Summary Statistics



4

Monitoring Physical Port Performance

This chapter describes how to view or retrieve performance monitoring (PM) data (parameters, thresholds, and statistics) from the physical ports, channels, and IMA groups and links on Lucent switches. See the next section, “PM Support on Physical Ports” on page 4-2, to determine whether PM data is available for a specific physical port.

For a detailed description of PM, see:

• American National Standard for Telecommunications - Digital Hierarchy – Layer 1 In-Service Digital Transmission Performance Monitoring Specification (ANSI T1.231-1993)

• Internet Engineering Task Force (IETF) Request for Comment (RFC) 1595, Definitions of Managed Objects for the SONET/SDH Interface Type (Bellcore/SONET MIB)



Monitoring Physical Port PerformancePM Support on Physical Ports

PM Support on Physical Ports

To verify that a particular physical port supports PM data, access the data as described in “Viewing PM Data For a Physical Port or Subport” on page 4-3. If the PM Thresholds and PM Statistics buttons are either grayed out or not visible, the physical port does not support PM data.

Examples of Input/Output Modules (IOMs) and Basic Input/Output (BIO) cards with physical ports that provide PM data include:

• GX 550 Multiservice WAN Switch BIO cards

• GX 550 Extender Shelf (ES) DS3 ATM/CE transports

• CBX 500 ATM OC-n/STM-n

• CBX 3500 ATM OC-n/STM-n ATM and POS Universal IOPs

• B-STDX ATM IWU

• B-STDX ATM CS

• DS3/E3 (except for 1-Port ATM DS3/E3 IOMs)

• Channelized DS3 and DS3/1/0 FR/IP ports and their DS1 channels

• 4-Port 24-Channel Fractional T1

• 8-Port T1/E1 ATM

• 32-Port Channelized T1/E1

• 3-Port Channelized DS3/1 IMA and IMA Enhanced

• 8-Port Subrate DS3 FR/IP

• 1-Port Channelized STM-1/E1 IMA and IMA Enhanced

• 60-Port Channelized T1/E1 CE

• 6-Port Channelized DS3/1/0 Frame Relay

• 24-Port DS3 ATM Universal IOP

Beta Draft ConfidentialMonitoring Physical Port Performance

Setting PM Thresholds


Setting PM Thresholds

You can set PM thresholds to generate traps whenever the thresholds are exceeded. PM statistics are measured in 15-minute and one-day thresholds. These thresholds do not have to be set to view PM statistics.

See the Switch Module Configuration Guide for CBX 3500, CBX 500, GX 550, and B-STDX 9000 for more information about PM thresholds and their configuration.

Viewing PM Data For a Physical Port or Subport

This section describes how to view PM parameters and statistics for a physical port or subport. This includes the following:

• “Opening the Performance Monitoring Statistics Dialog Box” on page 4-3

• “Viewing OC-n/STM-n Data” on page 4-4

• “Viewing DS3/E3 Data” on page 4-12

• “Viewing T1/E1 Data” on page 4-24

Opening the Performance Monitoring Statistics Dialog Box

To open the Performance Monitoring Statistics dialog box for a physical port or a subport:

1. Display the physical ports or subports for the module or subcard (see “Displaying Physical Ports and Subports” on page 2-74).

2. Right-click on the physical port or subport for which you want to view PM data, and select PM Statistics from the popup menu.

The Performance Monitoring Statistics dialog box appears (Figure 4-1).



Monitoring Physical Port PerformanceViewing PM Data For a Physical Port or Subport

Figure 4-1. Performance Monitoring Statistics Dialog Box (OC-3n/STM-n)

Viewing OC-n/STM-n Data

This section describes how to view PM data for OC-n/STM-n physical ports or subports. This section includes:

• “Viewing Current, Interval, or Day Reports for OC-n/STM-n Data” on page 4-4

• “Viewing Medium Reports for OC-n/STM-n Data” on page 4-11

Viewing Current, Interval, or Day Reports for OC-n/STM-n Data

To view Current, Interval, or Day Reports for OC-n/STM-n PM data for a physical port or subport:

1. At the Performance Monitoring Statistics dialog box (see “Opening the Performance Monitoring Statistics Dialog Box” on page 4-3), select one of the following reports from the Report Type field:

• Current — (default) To view real-time current interval data updated at the specified polling frequency (Figure 4-1 on page 4-4) shows a Current statistics example).




• Interval — To view an interval report based on an interval value from 1–96 you specify in the Nth Most Recent Interval field, with 1 indicating the most recent.

• Day — To view a report based on the option you specify select one of the following from the pull-down list: Current (default), Previous, or Recent (two days ago).

• Medium — To view a dialog box that displays Sonet/SDH medium statistics. If you choose this option, proceed to “Viewing Medium Reports for OC-n/STM-n Data” on page 4-11 for more information.

2. If you want to change the default polling interval (5 seconds) for the collection and retrieval of the performance monitoring statistics, enter a value from 1 to 900 in the Poll Interval field.

3. If you choose Interval in the Report Type field, specify an interval value (from 1 to 96) in the Nth Most Recent Interval field.

If you choose Day in the Report Type field, select one of the following options from the Day field’s pull-down list: Current, Recent, or Previous.

4. Choose Apply to view the data.

Table 4-1 describes the informational fields at the top of the Performance Monitoring Statistics dialog box, and Table 4-2 describes the PM parameters and associated thresholds and statistics. If a field in Table 4-2 does not appear or is grayed out in the dialog box, then that field is not applicable to the physical port or subport.

Note – If you are monitoring performance statistics for a physical port or subport on an OC48 or OC48c module, the APS Performance field is grayed out.

If you are monitoring performance statistics for a physical port on an OC48 or OC48c module, the Near End Path Performance field and the Far End Path Performance field are also grayed out.




Table 4-1. Performance Monitoring Fields Statistics Dialog BoxInformational Fields (OC-n/STM-n)

Field Displays...

Reset Time The time statistics were last reset.

Current Time The current time.

Status Data Valid if these statistics are valid; Data Invalid if there is no valid data for the specified time period; displays all zeroes when there is no valid data.

SES Threshold Setting A read-only field that indicates the standard (ANSI or Bellcore) for calculating the severely-errored seconds (SES) values. This is the option you selected when you configured the performance thresholds.

Valid Intervals (Interval reports only)

The number of intervals for which data is available.

Table 4-2. Performance Monitoring Statistics Dialog Box Fields(OC-n/STM-n)

Field Threshold Description

Near End Section Performance Parameter

Code Violations CV-S A count of bit interleaved parity (BIP-8) errors that are detected at the section layer of the incoming signal. Section CV counters increment for each BIP-8 error detected. That is, each BIP-8 can detect up to eight errors per synchronous transport signal level N (STS-N) frame with each error incrementing the CV counter. CVs for the section layer are collected using the BIP-8 in the B1 byte located in the section overhead of STS-1 number 1.

Errored Seconds ES-S A count of 1-second intervals in which one or more BIP-8 errors (B1 byte) occurred, one or more severely errored frame (SEF) defects were detected, or one or more loss of signal (LOS) defects were detected.




Severely Errored Seconds

SES-S A count of 1-second intervals in which x or more BIP-8 errors (B1 byte) occurred, one or more SEF defects were detected, or one or more LOS defects were detected.

Note: The SES Threshold standard sets the value of x for SES-S. For ANSI standards, this value is 8800; for Bellcore standards, this value is 63; for SONET, this value is 32.

Severely Errored Frame Seconds

N/A A count of 1-second intervals in which one or more SEF defects were detected.

Errored Seconds Type A

N/A A count of 1-second intervals in which one BIP-8 (B1 byte) error occurred, and no SEF or LOS condition was detected.

Errored Seconds Type B

N/A A count of 1-second intervals in which two or more BIP-8 (B1 byte) errors occurred, and no SEF or LOS condition was detected.

Loss of Signal Seconds

N/A A count of 1-second intervals in which one or more LOS conditions were detected.

Near End Line Performance Parameter

Code Violations CV-L A count of the BIP-8 errors detected at the line layer of the incoming signal. The line CV counter increments for each BIP-8 error detected. Each line BIP-8 can detect up to eight errors per STS-1 frame with each error incrementing the CV counter. Line layer CVs are collected using the BIP-8s in the B2 byte located in the line overhead of each STS-1.

Errored Seconds ES-L A count of 1-second intervals in which one or more BIP-8 errors (B2 byte) occurred, or one or more alarm indication signal (AIS) defects were detected.


SES-L A count of 1-second intervals in which x or more BIP-8 errors (B2 byte) occurred, or one or more AIS defects were detected.

Note: The SES Threshold standard sets the value of x for SES-L. For ANSI, this value is 10,000; for Bellcore, this value is 124.

Table 4-2. Performance Monitoring Statistics Dialog Box Fields(OC-n/STM-n) (Continued)





Unavailable Seconds

UAS-L A count of 1-second intervals for which the SONET/SDH line is unavailable, which begins at the onset of 10 contiguous SES-Ls. The unavailable time period includes the 10 SES-Ls.

Once the SONET line is unavailable, it becomes available at the onset of 10 contiguous seconds with no SES-Ls. The 10 seconds with no SES-Ls are excluded from the unavailable time period.

AIS Seconds N/A A count of 1-second intervals in which one or more AIS defects were detected.

Failure Count N/A A count of near-end line failure (AIS-L) events.


N/A A count of 1-second intervals in which one line BIP-8 (B2 byte) error occurred, and no alarm indication signal (AIS-L) defects were detected.


N/A A count of 1-second intervals in which two or more BIP-8 (B2 byte) errors occurred, and no alarm indication signal (AIS-L) defects were detected.

Near-End Path Performance Parameters

Code Violations CV-P A count of BIP-8 errors that are detected at the STS path layer of the incoming signal. The CV counters increment for each BIP-8 error detected. CVs for the STS path layer are collected using the BIP-8 in the B3 byte located in the STS path overhead.

Errored Seconds ES-P A count of 1-second intervals in which one or more BIP-8 path errors (B3 byte) occurred, one or more AIS-P (alarm indication signal path) defects were detected, or one or more LOP-P (loss of pointer path) defects were detected.


SES-P A count of 1-second intervals in which x or more BIP-8 path errors (B3 byte) occurred, one or more LOP-P defects were detected, or one or more AIS-P defects were detected. The default value of x for the STS-1 and STS-3c synchronous payload envelope (SPE) is 2400.

Note: The SES Threshold standard sets the value of x for SES-P. For ANSI standards, this value is 8800; for Bellcore standards, this value is 63.






Unavailable Seconds

UAS-P A count of 1-second intervals for which the SONET STS path is unavailable, which begins at the onset of 10 contiguous SES. The unavailable time period includes the 10 SES.

Once the SONET STS-path is unavailable, it becomes available at the onset of 10 contiguous seconds with no SES. The 10 seconds with no SES are excluded from the unavailable time period.

Width N/A A value that indicates the type of SONET/SDH path.

For SONET, the assigned types are the STS-Nc SPEs, where N equals one of the following values: 1, 3, 12, 24, and 48. STS-1 is equal to 51.84 Mbps; STS-3 is equal to 51.84*3 or 155.52 Mbps; STS-12 is equal to 622.08 Mbps, and so on.

For SDH, the assigned types are the STM-Nc VCs, where N equals one of the following values: 1, 4, and 16.

Failure Count N/A A count of near-end STS path failure (LOP-P or AIS-P) events.


N/A A count of 1-second intervals in which one BIP-8 (B3 byte) error occurred, and no AIS-P or LOP defects were detected.


N/A A count of 1-second intervals in which two or more BIP-8 (B3 byte) errors occurred, and no AIS-P or LOP defects were detected.

AIS/LOP Seconds

N/A A count of 1-second intervals in which one or more AIS-P or LOP path conditions were detected.

APS Performance Parameter

Protection Switch Count

N/A The number of switching events on the working line and the protection line.

Protection Switch Duration

N/A The length of time, in seconds, when a working line is out of service due to a protection-switching event, or the length of time a protection line is in service due to a protection-switching event.

Far End Line Performance Parameter

FEBE errors CV-LFE Far-end block line errors.






Errored Seconds ES-LFE A count of 1-second intervals in which one or more far-end line BIP errors occurred, or one or more RDI-L conditions were detected.


SES-LFE A count of 1-second intervals in which the far-end line BIP errors exceed the SES-LFE threshold, or RDI-L conditions were detected.

Unavailable Seconds

UAS-LFE A count of far-end line unavailable seconds. Each far-end line unavailable second begins at the onset of 10 consecutive far-end severely errored seconds (SES-LFE seconds).

AIS Seconds N/A A count of 1-second intervals in which one or more RDI-L conditions were detected.

Failure Count N/A A number of far-end line failure (RFI-L) events.


N/A A count of 1-second intervals in which one far-end line BIP error occurred, and no RDI-L conditions were detected.


N/A A count of 1-second intervals in which two or more far-end line BIP errors occurred, the far-end line BIP errors were less than the SES-LFE threshold x, and no RDI-L conditions were detected.

Far End Path Performance Parameter

FEBE errors CV-PFE Far-end block path errors.

Errored Seconds ES-PFE A count of 1-second intervals in which one or more far-end BIP errors occurred, or one or more RDI-P conditions were detected.


SES-PFE A count of 1-second intervals in which the number of far-end path BIP errors exceed the SES-PFE threshold x, or RDI-P conditions were detected.

Unavailable Seconds

UAS-PFE A count of far-end path unavailable seconds. A far-end path unavailable second begins at the onset of 10 consecutive far-end SES.

AIS/LOP Seconds

N/A A count of 1-second intervals in which one or more RDI path conditions were detected.

Failure Count N/A A count of far-end STS path failure (RFI-P) events.






5. Choose Reset to update these statistics.


The Performance Monitoring Statistics dialog box closes.

Viewing Medium Reports for OC-n/STM-n Data

To view Medium Reports for OC-n/STM-n PM data for a physical port or subport:

1. At the Performance Monitoring Statistics dialog box (see “Opening the Performance Monitoring Statistics Dialog Box” on page 4-3), choose Medium in the Report type field.

The DS3/E3 Statistics Configuration dialog box appears (Figure 4-2).

Figure 4-2. DS3/E3 Statistics Configuration Dialog Box

Table 4-3 describes the DS3/E3 Statistics Configuration dialog box. If a parameter in Table 4-3 does not appear or is grayed out in the dialog box, then that field is not applicable to the physical port or subport.


N/A A count of 1-second intervals in which one far-end path BIP error occurred, and no RDI-P condition was detected.


N/A A count of 1-second intervals in which two or more far-end BIP errors occurred, the far-end path BIP errors were less than the SES-PFE threshold x, and no RDI-P conditions were detected.







TheDS3/E3 Statistics Configuration dialog box closes.

Viewing DS3/E3 Data

This section describes how to view performance monitoring data for DS3 or E3 physical ports. This section includes:

• “Viewing Current, Interval, Day, or Total Reports for DS3/E3 Data” on page 4-12

• “Viewing Configuration Reports for DS3/E3 Data” on page 4-18

• “Viewing the DS3/E3 Configuration Line Status” on page 4-22

• “Viewing the DS3/E3 Configuration PLCP Status” on page 4-23

• “Viewing the DS3/E3 Configuration TC Status” on page 4-24

Viewing Current, Interval, Day, or Total Reports for DS3/E3 Data

To view Current, Interval, Day, or Total Reports for DS3/E3 PM data for a physical port, see Figure 4-3:

1. At the Performance Monitoring Statistics dialog box (see “Opening the Performance Monitoring Statistics Dialog Box” on page 4-3), select one of the following reports from the Report Type field:

Current — (default) To view real-time current 15-minute interval counters, updated at the specified polling frequency. (Figure 4-3 on page 4-13 shows a Current statistics example.)

Table 4-3. DS3/E3 Statistics Configuration Dialog Box Fields

Statistic Displays...

Refresh Time The time statistics were last reset.

Medium Type One (1) in the value field.

Medium Time Elapsed

The number of seconds, including partial seconds, that have elapsed since the beginning of the current error-measurement period.

Medium Valid Intervals

The number of previous intervals for which valid data has been stored.

Medium Line Type Four (4) in the value field.

Medium Line Coding

The line coding for this interface: Other, B3ZA, CMI, NRZ, RZ.

Medium Circuit Identifier

The transmission vendor’s company name or ID, which you can use for troubleshooting.




Interval — To view counters for a previous 15-minute interval, based on the interval value from 1–96 you specify in the Nth Most Recent Interval field, with 1 indicating the most recent.

Day — To view a report based on the option you specify, select one of the following from the pull-down list: Current (default), Previous, or Recent (two days ago). The Day report contains a snapshot of each counter's totals for a 24-hour period (per ANSI T1.231). These reports are updated every 24 hours by totaling all 15 intervals from the previous 24 hours.

Total — To view the rolling total count of all the counters in the last 24-hour period. Effectively, it is the total count of the past 96 15-minute interval counters. These are updated at 15-minute intervals, starting from the current interval.

Config — To view the current configuration information. If you choose this option, proceed to “Viewing Configuration Reports for DS3/E3 Data” on page 4-18 for more information.

Figure 4-3. Performance Monitoring Statistics Dialog Box (DS3/E3)

2. If you choose Interval, specify an interval value (from 1 to 96) in the Nth Most Recent Interval field.

If you choose Day, select one of the following options: Current, Recent, or Previous.






Table 4-4 describes the informational fields at the top of the Performance Monitoring Statistics dialog box, and Table 4-5 describes the performance-monitoring parameters (and associated thresholds and statistics) of the Performance Monitoring Statistics dialog box for DS3/E3. If a field in Table 4-5 does not appear or is grayed out in the dialog box, that field is not applicable to the physical port or subport.

Note – If you are monitoring performance statistics for a physical port on a Channelized DS3/E3 or DS3/1/0 FR/IP IOM, the ATM Direct Mapping Parameters, PLCP Parameters, and Far-End Block Error Parameters are grayed out or not displayed.

If you are monitoring performance statistics for a physical port on the 8-Port Subrate DS3 FR/IP IOM, the ATM Direct Mapping Parameters, physical layer convergence protocol (PLCP) Parameters, and Far-End Block Parameters are grayed-out or not displayed.

Table 4-4. Performance Monitoring Statistics Dialog Box InformationalFields (DS3/E3)

Field Displays...



Status Data Valid if these statistics are valid; Data Invalid if there is no valid data for the specified time period, or displays all zeroes if there is no valid data.

Time Elapsed The time elapsed in the current time period.

Valid Intervals(Interval reports only)


Far End Status Problems with remote/far-end equipment that could affect the accuracy of this data.




Table 4-5. Performance Monitoring Statistics DialogBox Fields (DS3/E3)



Code Violations CV-L A count of both bipolar violations (BPVs) and excessive zeros (EXZs) occurring over the accumulation period.

Errored Seconds ES-L A count of 1-second intervals containing one or more BPVs, one or more EXZs, or one or more loss of signal defects (LOS).


N/A A count of 1-second intervals containing one BPV or EXZ and no LOS defects.

Error Seconds Type B

N/A A count of 1-second intervals containing more than one, but less than x BPVs plus EXZs, and no LOS defects.


SES-L A count of 1-second intervals with more than x BPVs plus EXZs, or one or more LOS defects.

LOS Seconds N/A A count of 1-second intervals containing one or more LOS defects.

Near End Path Performance Parameter

P-bit Code Violations CVP-P A count of error events occurring in the accumulation period.

P-bit Errored Seconds ESP-P A count of 1-second intervals containing the occurrence of one or more P-bit parity errors, one or more SEF defects, or one or more AIS defects.

P-bit Errored Seconds Type A

N/A The count of 1-second intervals containing exactly one P-bit parity error and no SEF or AIS defects.

P-bit Errored Seconds Type B

N/A The count of 1-second intervals containing more than one, but less than x P-bit parity errors, and no SEF or AIS defects.

P-bit Severely Errored Seconds

SESP-P A count of 1-second intervals containing more than x P-bit parity errors, one or more SEF defects, or one or more AIS defects.

P-bit Severely Errored Frame Seconds

SEFP-P A count of 1-second intervals containing one or more SEF defects or one or more AIS defects.

P-bit Unavailable Seconds

UASP-P A count of 1-second intervals for which the DS3 path is unavailable. The DS3/E3 path becomes unavailable at the onset of 10 contiguous SESP-Ps.

CP-bit Code Violations CVCP-P A count of error events occurring in the accumulation period.




CP-bit Errored Seconds(C-bit for chan. DS3)

ESCP-P A count of 1-second intervals containing one or more M-frames with the three FEBE bits not all set to 1, or one or more far-end SEF/AIS defects.

CP-bit Errored Seconds Type A

N/A The count of 1-second intervals containing one CP-bit parity error and no SEF or AIS defects.

CP-bit Errored Seconds Type B

N/A The count of 1-second intervals containing more than one, but less than x CVCP-Ps, and no SEF or AIS defects.

CP-bit Severely Errored Seconds

SESCP-P A count of 1-second intervals containing more than x CP-bit parity errors, one or more SEF defects, or one or more AIS defects.

CP-bit Unavailable Seconds(C-bit for chan. DS3)

UASCP-P A count of 1-second intervals for which the DS3 path is unavailable. The DS3 path becomes unavailable at the onset of 10 contiguous SESCP-Ps.

AIS Seconds SASCP-P A count of 1-second intervals containing one or more AIS defects.

Failure Count N/A A count of the number of occurrences of near-end path failure events, with the failure event defined as follows:

• A near-end path failure event begins when either a loss of framing (LOF) or AIS failure is declared.

• A near-end path failure event ends when both LOF and AIS failures are cleared.

ATM Direct Mapping Parameter

OCD Errored Seconds N/A Count of 1-second intervals containing Out of Cell Delineation (OCD).

LCD Errored Seconds N/A Count of 1-second intervals containing Loss of Cell Delineation (LCD).

PLCP Parameter

Bit Interleaved Parity N/A The number of PLCP-BIP errors in the current 15-minute interval.

Loss of Frame Errored Seconds

N/A The number of PLCP-LOF errors in the current 15-minute interval.

Yellow Errored Seconds

N/A The number of PLCP-YEL errors in the current 15-minute interval.

Code Violations N/A The number of PLCP-CV errors in the current 15-minute interval.









Errored Seconds N/A The number of PLCP-ES errors in the current 15-minute interval.


N/A The number of PLCP-SES errors in the current 15-minute interval.

Severely Errored Frames

N/A The number of PLCP-SEF errors in the current 15-minute interval.

Unavailable Seconds N/A The number of PLCP-UAS errors in the current 15-minute interval.

Far End Block Errors PLCP-FEBE The number of PLCP-FEBE errors in the current 15-minute interval.

Far End Block Errored Seconds

PLCP-FEBE-ES The number of PLCP-FEBE errors in the current 15-minute interval.

Far End Block Error Parameter

Far End Block Error FEBE-P The number of FEBE errors in the current 15-minute interval.

Code Violations N/A The number of FEBE-CV errors in the current 15-minute interval.

Errored Seconds ESCP-P The number of FEBE-ES errors in the current 15-minute interval.


N/A The number of FEBE-ESA errors in the current 15-minute interval.


N/A The number of FEBE-ESB errors in the current 15-minute interval.


SESCP-P The number of FEBE-SES errors in the current 15-minute interval.

Severely Errored Frames

N/A The number of FEBE-SEFS errors in the current 15-minute interval.

Unavailable Seconds UASCP-P The number of FEBE-UAS errors in the current 15-minute interval.

Failure Count N/A The number of FEBE-FC errors in the current 15-minute interval






Viewing Configuration Reports for DS3/E3 Data

To view Configuration Reports for DS3/E3 PM data for a physical port:

1. At the Performance Monitoring Statistics dialog box (see “Opening the Performance Monitoring Statistics Dialog Box” on page 4-3), select Configuration.

The DS3/E3 Statistics Configuration dialog box appears (Figure 4-4).

Figure 4-4. DS3/E3 Statistics Configuration Dialog Box

Table 4-6 describes the DS3/E3 Statistics Configuration dialog box fields. If a field in Table 4-6 does not appear or is grayed out in the dialog box, that element is not applicable to the physical port or subport.


Field Description

Refresh Time The time statistics were last reset.

DS3/E3 Standard MIB

Line Index The DS3 or E3 interface index identifier on a managed device.

Interface Index The value of ifIndex from the Interface table of MIB II.

Time Elapsed The number of seconds elapsed since the beginning of the current error measurement period.

Valid Intervals The number of previous near-end intervals for which valid data was collected.




Line Type The DS3 C-bit or E3 applications implementing this interface:

1 – Other (undefined) DS3 interface2 – M23 (defined in ANSI T1.107-1988)3 – SYNTRAN (defined in ANSI T1.107-1988)4 – C-bit Parity (defined in ANSI T1.107a-1989)5 – Clear Channel (defined in ANSI T1.102-1987)6 – Other (undefined) E3 interface7 – Framed (defined in CCITT G.751)8 – PLCP (defined in ETSI T/NA (91) 18)

Note: The Clear Channel value means that C-bits are not used except for sending and receiving AIS.

Line Coding The type of Zero Code Suppression on this interface:

1 – Other (undefined) from of Zero Code Suppression2 – B3ZS (for DS3 links)3 – HDB3 (for E3 links)

Note: B3ZS and HDB3 refer to the use of specified patterns of normal bits and bipolar violations which are used to replace sequences of zero bits of a specified length.

Send Code The type of code the device sends across the DS3/E3 interface:

1 – Send no code (that is, send looped or normal data)2 – Send line code (that is, send a request for a line loopback)3 – Send payload code (that is, send a request for a payload loopback)4 – Send reset code (that is, send a loopback deactivation request)5 – Send DS1 loop code (that is, request to loopback to a particular

DS1/E1 within a DS3/E3 frame)6 – Send test pattern (that is, send a test pattern)

Circuit Identifier The transmission vendor’s circuit identifier.

Loopback Configuration

The loopback configuration of the DS3/E3 interface:

1 – No loop (that is, not in the loopback state)2 – Payload loop (that is, the received signal is looped through the

device)3 – Line loop (that is, the received signal does not go through this

interface but is looped back out)4 – Other (undefined) loopback


Field Description




Line Status The line status of the interface. This field is a bit map that represents a sum and, therefore, can represent multiple failures and a loopback. The various bit positions (and their MIB variables and descriptions) include:

1 – No alarm (dsx3NoAlarm)2 – Receiving indication of a yellow/remote alarm

(dsx3RcvRAIFailure)4 – Transmitting yellow/remote alarm indication

(dsx3XmitRAIAlarm)8 – Receiving AIS failure state (dsx3RcvAIS)

16 – Transmitting AIS (dsx3XmitAIS)32 – Receiving LOF failure state (dsx3LOF)64 – Receiving LOS failure state (dsx3LOS)

128 – Looping the received signal (dsx3LoopbackState)256 – Receiving a test pattern (dsx3RcvTestCode)512 – Undefined line status (dsx3OtherFailure)

Transmit Clock Source

The source of the transmit clock:

1 – Loop timing2 – Local timing3 – Through timing

DS3/E3 Supplement MIB

Config Index The DS3 or E3 interface index identifier on a managed device.

Day Time Elapsed

The number of seconds that have elapsed since the beginning of the measurement period.

Valid Day Interval

The number of previous intervals for which valid data was collected. This value is 3 unless the interface was brought online within the last three days, in which case the value is equal to the number of complete one-day intervals since the interface has been online.

Enable All TCAs Indicates whether threshold crossing alerts (TCAs) can be sent across the interface:

1 – True (TCAs can be sent)2 – False (TCAs cannot be sent)

PLCP Alarm State

The current PLCP alarm state.

TC Alarm State The current TC alarm state.

AIC Signal The type of application (C-bit or M23/SYNTRAN) based on the application identification channel (AIC) signal received by the DS3 interface:

1 – C-bit2 – M23/SYNTRAN


Field Description





3. To view the Line Status, PLCP Status, or TC Status of the associated interface, see one of the following sections:

• “Viewing the DS3/E3 Configuration Line Status” on page 4-22

• “Viewing the DS3/E3 Configuration PLCP Status” on page 4-23

• “Viewing the DS3/E3 Configuration TC Status” on page 4-24

Idle Signal Indicates whether an Idle signal is being received:

1 – No idle2 – Receiving idle

PLCP Status The current PLCP status:

1 – No status2 – Receiving LOF4 – Receiving YEL8 – Receiving AIS

16 – Receiving FEBE

TC Status The current TC status:

1 – No status2 – Receiving OCD4 – Receiving LCD

Far End Block Error

Indicates whether a FEBE is being received:

1 – No FEBE2 – Receiving FEBE

Far End Alarm Code

Indicates whether a FEAC is being received:

1 – No FEAC2 – Equipment failure4 – LOS8 – Out of frame

16 – AIS received32 – Idle received64 – Non-service affecting equipment failure

128 – Common equipment failure256 – Loopback received512 – DS1 service affecting equipment failure

1024 – DS1 non-service affecting equipment failure2048 – Single DS1 LOS4096 – Multiple DS1 LOS


Field Description




4. When you are done viewing the statistics configuration, choose Close.

The DS3/E3 Statistics Configuration dialog box closes.

Viewing the DS3/E3 Configuration Line Status

To view the line status error conditions for a physical port:

1. At the DS3/E3 Statistics Configuration dialog box (see “Viewing Configuration Reports for DS3/E3 Data” on page 4-18), choose the Line Status button.

The DS3/E3 Configuration Line Status dialog box appears (Figure 4-5).

The line status error condition is grayed out unless the error condition applies to the DS3/E3 physical port.

Figure 4-5. DS3/E3 Configuration Line Status Dialog Box

Table 4-7 describes the DS3/E3 configuration line status error conditions. If a field in Table 4-7 does not appear or is grayed out in the dialog box, that field is not applicable to the physical port or subport.

Table 4-7. DS3/E3 Configuration Line Status Dialog Box Fields

Field Description

No Alarm No alarm present.

Receiving Yellow/Remote Far-end SEF/AIS detected.

Transmitting Yellow/Remote Transmitting a yellow/remote alarm.

Receiving AIS Failure Near-end SEF/AIS detected.

Transmitting AIS Transmitting an alarm indication signal.

Receiving LOF Failure Receiving loss of frame condition.

Receiving LOS Failure Receiving loss of signal. No signal detected.

Looping the Received Signal Loopback enabled/disabled.

Receiving a Test Pattern FEAC (Far end alarm code) signal received.




2. When you are done viewing the line status, choose OK.

The DS3/E3 Configuration Line Status dialog box closes.

Viewing the DS3/E3 Configuration PLCP Status

To view the PLCP status error conditions for a physical port:

1. At the DS3/E3 Statistics Configuration dialog box (see “Viewing Configuration Reports for DS3/E3 Data” on page 4-18), choose the PLCP Status button.

The DS3/E3 Configuration PLCP Status dialog box appears (Figure 4-6).

The PLCP status error condition is grayed out unless the error condition applies to the DS3/E3 physical port.

Figure 4-6. DS3/E3 Configuration PLCP Status Dialog Box

Table 4-8 describes the DS3/E3 configuration PLCP error conditions. If a field in Table 4-8 does not appear or is grayed out in the dialog box, that field is not applicable to the physical port or subport.

2. When you are done viewing the PLCP status, choose OK.

The DS3/E3 Configuration PLCP Status dialog box closes.

Other Failure Any failures not covered by the above conditions.

Table 4-8. DS3/E3 Configuration PLCP Status Dialog Box Fields

Field Description

No PLCP Status No PLCP status condition is detected.

Receiving LOF Failure Receiving notification of a loss of frame (LOS) failure.

Receiving Yellow Receiving a yellow alarm.

Receiving AIS Failure Receiving notification of an AIS failure.

Receiving FEBE Failure Receiving notification of a FEBE failure.

Table 4-7. DS3/E3 Configuration Line Status Dialog Box Fields (Continued)

Field Description




Viewing the DS3/E3 Configuration TC Status

To view the TC status error conditions for a physical port:

1. At the DS3/E3 Statistics Configuration dialog box (see “Viewing Configuration Reports for DS3/E3 Data” on page 4-18), choose the TC Status button.

The DS3/E3 Configuration TC Status dialog box appears (Figure 4-7).

The TC status error condition is grayed out unless the error condition applies to the DS3/E3 physical port.

Figure 4-7. DS3/E3 Configuration TC Status Dialog Box

Table 4-9 describes the DS3/E3 Configuration TC Status conditions. If a field in Table 4-9 does not appear or is grayed out in the dialog box, that field is not applicable to the physical port or subport.

2. When you are done viewing the TC status, choose OK.

The DS3/E3 Configuration TC Status dialog box closes.

Viewing T1/E1 Data

To view Current, Interval, or Day Reports for T1/E1 PM data for a physical port (see Figure 4-8):

1. At the Performance Monitoring Statistics dialog box (see “Opening the Performance Monitoring Statistics Dialog Box” on page 4-3), select one of the following reports:

Current — (default) To view real-time current interval data updated at the specified polling frequency (Figure 4-8 shows a Current statistics example).

Interval — To view an interval report based on the interval value from 1–96 you specify in the Nth Most Recent Interval field, with 1 indicating the most recent.

Table 4-9. DS3/E3 Configuration TC Status Dialog Box Fields

Field Description

No TC Status No TC status condition is detected.

Receiving OCD Failure Receiving notification of an OCD failure.

Receiving LCD Failure Receiving notification of an LCD failure.




Day — To view a Totals report select one of the three options: Current (default), Recent (two days ago), or Previous.

Figure 4-8. Performance Monitoring Statistics Dialog Box (T1/E1)


If you choose Day, choose one of the following options: Current, Recent, or Previous.



Table 4-10 describes the informational fields at the top of the Performance Monitoring Statistics dialog box, and Table 4-11 describes performance-monitoring parameters (and associated thresholds and statistics) of the T1/E1 Performance Monitoring Statistics dialog box. If a field in Table 4-11 does not appear or is grayed out in the dialog box, that field is not applicable to the physical port or subport.

Note – When you are monitoring performance statistics for a physical port on the 32-Port Channelized T1/E1 FR/IP IOM, the Far End Line and the Far End Path Performance fields are grayed-out or not displayed.




Table 4-10. Performance Monitoring Statistics Dialog Box (T1/E1)

Field Displays...






Table 4-11. Performance Monitoring Statistics Dialog Box (T1/E1)



Code Violations N/A A count of both BPVs and EXZs occurring over the accumulation period. For a B8ZS-coded signal, BPVs that are part of the zero substitution code, as defined in ANSI T1.102, are excluded from the count.

Errored Seconds ES-L A count of 1-second intervals with one or more BPVs, one or more EXZs, or one or more LOS (loss of signal) defects. For a B8ZS-coded signal, BPVs that are part of the zero substitution code, as defined in ANSI T1.102, are excluded.


N/A A count of 1-second intervals with 1544 or more BPVs plus EXZs, or one or more LOS defects. For a B8ZS-coded signal, BPVs that are part of the zero substitution code, as defined in ANSI T1.102, are excluded.

LOS - Loss of Signal Seconds

N/A A count of 1-second intervals with one or more LOS defects.


Code Violations CV-P A count of frame synchronization bit errors (FE) in the SF (Superframe) format, or a count of cyclic redundancy check (CRC)-6 errors in the ESF (Extended Superframe) format occurring during the accumulation period.




Errored Seconds ES-P In the case of DS1 ESF, a count of 1-second intervals containing one or more CRC-6 errors, one or more CS events, or one or more SEF or AIS defects. In the case of DS1 SF, this parameter is a count of 1-second intervals containing one or more FE events, one or more SEF or AIS defects, or one or more CS events.


N/A This field applies to DS1 ESF paths only. A count of 1-second intervals with exactly one CRC-6 error and no SEF or AIS defects.


N/A This field applies to DS1 ESF paths only. A count of 1-second intervals with no less than 2, and not more than 319 CRC-6 errors, no SEF defects, and no AIS defects.


SES-P This field applies to both SF and ESF frame formats of DS1. In the case of ESF, it is a count of 1-second intervals with 320 or more CRC-6 errors, or one or more SEF or AIS defects. In the case of SF, it is a count of 1-second intervals with eight or more FE events (if Ft and F8 bits are measured) or four or more FE events (if

Ft bits only are measured), or an SEF or AIS defect.

SEF/AIS Seconds SAS-P A count of 1-second intervals containing one or more SEF defects or one or more AIS defects.

AIS Seconds N/A A count of 1-second intervals containing one or more AIS defects.

Controlled Slip Seconds

CSS-P A count of 1-second intervals containing one or more controlled slips. Counts of controlled slips can be made accurately only in the path-terminating network element of the DS1 signal, where the controlled slip takes place.

Unavailable Seconds

UAS-P A count of 1-second intervals for which the DS1 path is unavailable. The DS1 path becomes unavailable at the onset of 10 contiguous SESs. The 10 SESs are included in the unavailable time period. Once it is unavailable, the DS1 path becomes available at the onset of 10 contiguous seconds with no SESs. The 10 seconds with no SESs are excluded from the unavailable time period.

Failure Count N/A A count of Loss of Frame or AIS events within the accumulation period.


Table 4-11. Performance Monitoring Statistics Dialog Box (T1/E1) (Continued)




Monitoring Physical Port PerformanceViewing PM Data for a DS1 Channel




Viewing PM Data for a DS1 Channel

To view Current, Interval, or Day Reports for PM data for a DS1 channel:


2. Right-click on the DS1 channel for which you want to view PM data, and select PM Statistics from the popup menu.

Errored Seconds N/A A count of 1-second PRM intervals containing an LV=1.


Code Violations N/A A count of the number of far end CVs occurring during the accumulation period.

Errored Seconds N/A A count of 1-second Performance Report Messages (PRM) intervals containing a G1, G2, G3, G4, G5, or G6 or SE or SL=1, or an RAI (yellow alarm) signal.


N/A A count of 1-second PRM intervals containing a G1=1 and SE=0.


N/A A count of 1-second PRM intervals containing a G2, G3, G4, or G5=1, and SE=0.


N/A A count of 1-second PRM intervals containing a G6 or SE=1, or an RAI signal.


N/A A count of 1-second PRM intervals containing an SE=1.


N/A A count of 1-second PRM intervals containing an SL=1.

Unavailable Seconds

N/A A count of 1-second intervals for which the DS1 path is unavailable.

Failure Count N/A Count of Remote Alarm Identification (RAI) (yellow alarm) events within the accumulation period.

Table 4-11. Performance Monitoring Statistics Dialog Box (T1/E1) (Continued)






Figure 4-9. Performance Monitoring Statistics Dialog Box (DS1 Channel)

3. Select one of the following reports:

Current — (default) To view real-time current interval data updated at the specified polling frequency (Figure 4-9 shows a Current statistics example).


Day — To view a Totals report select from one of the three options: Current (default), Recent (two days ago), or Previous.





Table 4-12 describes the informational fields at the top of the dialog box, and Table 4-13 describes performance-monitoring fields (and associated thresholds and statistics) of the DS1 Channel Performance Monitoring Statistics dialog box. If a field in Table 4-13 does not appear or is grayed out in the dialog box, that element is not applicable to the channel.




Note – For channels on Channelized DS3/E3 and DS3/1/0 FR/IP IOMs, the Far-End Line Performance field and the Far-End Path Performance field are grayed out or not displayed.

For channels configured on the 3-Port Channelized DS3/1 IMA IOM, the Far-End Line Performance field is enabled only if facility data link (FDL) is enabled.

Table 4-12. Performance Monitoring Statistics Dialog Box InformationalFields (DS1 Channel)

Field Displays...






Table 4-13. Performance Monitoring Statistics Dialog Box Fields (DS1 Channel)



Code Violations N/A A count of both BPVs (bipolar violations) and EXZs (excessive zeros) occurring over the accumulation period. For a B8ZS-coded signal, BPVs that are part of the zero substitution code, as defined in ANSI T1.102, are excluded from the count.






N/A A count of 1-second intervals with 1544 or more BPVs plus EXZs, or one or more LOS defects. For a B8ZS-coded signal, BPVs that are part of the zero substitution code, as defined in ANSI T1.102, are excluded.

LOS - Loss of Signal Seconds

N/A A count of 1-second intervals with one or more LOS defects.

Near-End Path Performance Parameter




N/A This field applies to DS1 ESF paths only. A count of 1-second intervals with exactly one CRC-6 error and no SEF or AIS defects.


N/A This field applies to DS1 ESF paths only. A count of 1-second intervals with no less than 2 and not more than 319 CRC-6 errors, no SEF defects, and no AIS defects.


SES-P This field applies to both SF and ESF frame formats of DS1. In the case of ESF, it is a count of 1-second intervals with 320 or more CRC-6 errors, or one or more SEF or AIS defects. In the case of SF, it is a count of 1-second intervals with eight or more FE events (if Ft and F8 bits are measured) or four or more FE events (if Ft bits only are

measured), or an SEF or AIS defect.

SEF/AIS Seconds SAS-P A count of 1-second intervals containing one or more SEF defects or one or more AIS defects.

AIS Seconds N/A A count of 1-second intervals containing one or more AIS defects.

Table 4-13. Performance Monitoring Statistics Dialog Box Fields (DS1 Channel) (Continued)






CSS-P A count of 1-second intervals containing one or more controlled slips. Counts of controlled slips can be made accurately only in the path-terminating network element of the DS1 signal, where the controlled slip takes place.

Unavailable Seconds UAS-P A count of 1-second intervals for which the DS1 path is unavailable. The DS1 path becomes unavailable at the onset of 10 contiguous SESs. The 10 SESs are included in the unavailable time period. Once it is unavailable, the DS1 path becomes available at the onset of 10 contiguous seconds with no SESs. The 10 seconds with no SESs are excluded from the unavailable time period.

Failure Count N/A A count of LOF or AIS events within the accumulation period.


Errored Seconds ES-LFE A count of 1-second Performance Report Messages (PRM) intervals containing an LV=1.

Note: This parameter displays only if FDL is enabled.


Code Violations CV-PFE A count of the number of far end CVs occurring during the accumulation period.

Errored Seconds ES-PFE A count of 1-second PRM intervals containing a G1, G2, G3, G4, G5, or G6 or SE or SL-1, or an RAI signal.


ESA-PFE A count of 1-second PRM intervals containing a G1=1 and SE=0.

Errored SecondsType B

ESB-PFE A count of 1-second PRM intervals containing a G2, G3, G4, or G5=1, and SE=0.


SES-PFE A count of 1-second PRM intervals containing a G6 or SE=1, or an remote alarm identification (RAI) signal.


SEFS-PFE A count of 1-second PRM intervals containing an SE=1.




Viewing PM Data for an E1 Channel






To view Current, Interval, or Day Reports for PM data for an E1 channel:


2. Right-click on the E1 channel for which you want to view PM data, and select PM Statistics from the popup menu.



CSS-PFE A count of 1-second PRM intervals containing an SL=1.

Unavailable Seconds UAS-PFE A count of 1-second intervals for which the DS1 path is unavailable.

Failure Count FC-PFE A count of RAI (yellow alarm) events within the accumulation period.





Monitoring Physical Port PerformanceViewing PM Data for an E1 Channel

Figure 4-10. Performance Monitoring Statistics Dialog Box (E1 channel)

3. At the Performance Monitoring Statistics dialog box, select one of the following reports:

Current — (default) To view real-time current interval data updated at the specified polling frequency.


Day — To view a Totals report, select from one of the three options: Current (default), Recent (two days ago), or Previous.








Table 4-14 describes the informational fields at the top of the dialog box, and Table 4-15 describes performance-monitoring parameters (and associated thresholds and statistics) of the DS1 Channel Performance Monitoring Statistics dialog box. If a parameter in Table 4-15 does not appear or is grayed out in the dialog box, that element is not applicable to the channel.

Table 4-14. Performance Monitoring Statistics Dialog Box InformationalFields (E1 Channel)

Field Displays...






Table 4-15. Performance Monitoring Statistics Dialog Box Fields (E1 Channel)



Code Violations CV-L A count of both BPVs (bipolar violations) and EXZs (excessive zeros) occurring over the accumulation period. For a B8ZS-coded signal, BPVs that are part of the zero substitution code, as defined in ANSI T1.102, are excluded from the count.



SES-L A count of 1-second intervals with 1544 or more BPVs plus EXZs, or one or more LOS defects. For a B8ZS-coded signal, BPVs that are part of the zero substitution code, as defined in ANSI T1.102, are excluded.



Monitoring Physical Port PerformanceViewing PM Data for an E1 Channel





ESA-P This field applies to DS1 ESF paths only. A count of 1-second intervals with exactly one CRC-6 error and no SEF or AIS defects.


ESB-P This field applies to DS1 ESF paths only. A count of 1-second intervals with no less than 2 and not more than 319 CRC-6 errors, no SEF defects, and no AIS defects.


SES-P This field applies to both SF and ESF frame formats of DS1. In the case of ESF, it is a count of 1-second intervals with 320 or more CRC-6 errors, or one or more SEF or AIS defects. In the case of SF, it is a count of 1-second intervals with eight or more FE events (if Ft and F8 bits are measured) or

four or more FE events (if Ft bits only are

measured), or an SEF or AIS defect.

Unavailable Seconds UAS-P A count of 1-second intervals for which the DS1 path is unavailable. The DS1 path becomes unavailable at the onset of 10 contiguous SESs. The 10 SESs are included in the unavailable time period. Once it is unavailable, the DS1 path becomes available at the onset of 10 contiguous seconds with no SESs. The 10 seconds with no SESs are excluded from the unavailable time period.

Failure Count FC-P A count of LOF or AIS events within the accumulation period.

Table 4-15. Performance Monitoring Statistics Dialog Box Fields (E1 Channel) (Continued)









Errored Seconds ES-LFE A count of one second Performance Report Messages (PRM) intervals containing an LV=1.

Note: This parameter displays only if FDL is enabled.


Errored Seconds ES-PFE A count of 1-second PRM intervals containing a G1, G2, G3, G4, G5, or G6 or SE or SL-1, or an RAI signal.


ESA-PFE A count of 1-second PRM intervals containing a G1=1 and SE=0.


ESB-PFE A count of 1-second PRM intervals containing a G2, G3, G4, or G5=1, and SE=0.


SES-PFE A count of 1-second PRM intervals containing a G6 or SE=1, or an remote alarm identification (RAI) signal.

Unavailable Seconds UAS-PFE A count of 1-second intervals for which the DS1 path is unavailable.

Failure Count FC-PFE A count of RAI (yellow alarm) events within the accumulation period.

Table 4-15. Performance Monitoring Statistics Dialog Box Fields (E1 Channel) (Continued)




Monitoring Physical Port PerformanceViewing PM Data for IMA Groups and Links

Viewing PM Data for IMA Groups and Links

This section describes how to view performance-monitoring (PM) parameters and statistics for an IMA group or link. This includes the following:

• “Viewing IMA Group Performance-Monitoring Statistics” on page 4-38

• “Viewing IMA Link Performance-Monitoring Statistics” on page 4-40

Viewing IMA Group Performance-Monitoring Statistics

To view Current, Interval, Total, or Day Reports for PM data for an IMA group:


2. Right-click on the IMA group for which you want to view PM data, and select PM Statistics from the popup menu.

The IMA Group Performance Monitoring Statistics dialog box appears. See Figure 4-11.

Figure 4-11. IMA Group Performance Monitoring Statistics Dialog Box

3. Select one of the following reports from the Report Type field:












Table 4-16 describes the informational fields at the top of the dialog box, and Table 4-17 describes the performance-monitoring parameters (and associated thresholds and statistics) of the IMA Group Performance Monitoring Statistics dialog box.

Table 4-16. Performance Monitoring Statistics Dialog Box InformationalFields (IMA Group)

Field Description

Name The selected IMA group name.

IMA Group ID The selected IMA group number.

IMA Group Intf Num

The group interface number of the selected IMA group.

Table 4-17. Performance Monitoring Statistics Dialog Box Fields(IMA Group)


Unavailable Seconds UAS A count of 1-second intervals where the IMA Group Traffic State Machine is down.

NE Group Failures FCNE The number of times a near-end group failure (config-aborted or insufficient links) has been reported since power-up or reboot.

FE Group Failures FCFE The number of times a far-end group failure (config-aborted-FE, insufficient-links-FE, or blocked-FE) has been reported since power-up or reboot.







Viewing IMA Link Performance-Monitoring Statistics

To view Current, Interval, Total, or Day Reports for PM data for an IMA link:


2. Right-click on the IMA link for which you want to view PM data, and select PM Statistics from the popup menu.

The Performance Monitoring Statistics dialog box appears. See Figure 4-12.

Figure 4-12. IMA Link Performance Monitoring Statistics Dialog Box

3. At the Performance Monitoring Statistics dialog box, select one of the following reports from the Report Type field:












Table 4-18 describes the informational fields at the top of the dialog box, and Table 4-19 describes the performance monitoring parameters on the IMA Link Performance Monitoring Statistics dialog box.

Table 4-18. Performance Monitoring Statistics Dialog Box InformationalFields (IMA Link)

Field Description

IMA Group Name The selected IMA group name to which the link belongs.

IMA Group ID The selected IMA group number to which the link belongs.

Link If Index The If index number of the IMA group link.

Table 4-19. Performance Monitoring Statistics Dialog Box Fields (IMA Link)

Field Description

IMA Violations A count of errored, invalid, or missing ingress cell processing (ICP) cells, except during seconds where a SES or UAS condition is reported.

OIF Anomalies A count of OIF anomalies, except during SES or UAS conditions.

NE Severe Errored Sec. A count of one second intervals containing 30% or more of the ICP cells counted as IV-IMAs, or one or more link defects (for example, LOS, OOF/LOF, AIS, or LCD), LIF defects, or LODS defects, except during a UAS-IMA condition.

FE Severe Errored Sec. Count of one second intervals containing one or more RDI-IMA defects, except during a UAS-IMA-FE condition.







NE Unavailable Sec. A count of unavailable seconds at near-end. Unavailability begins at the onset of 10 contiguous SES-IMA and ends at the onset of 10 contiguous seconds with no SES-IMA.

FE Unavailable Sec. A count of unavailable seconds at far-end. Unavailability begins at the onset of 10 contiguous SES-IMA-FE and ends at the onset of 10 contiguous seconds with no SES-IMA-FE.

NE Tx Unusable Sec. A count of Tx unusable seconds at the near-end Tx LSM.

FE Tx Unusable Sec. A count of seconds with Tx unusable indications from the far-end Tx LSM.

NE Rx Unusable Sec. A count of Rx unusable seconds at the near-end Rx LSM.

FE Rx Unusable Sec. A count of seconds with Rx unusable indications from the far-end Rx LSM.

NE Tx Number Failures The number of times a near-end transmit failure alarm condition has been entered on this link.

FE Tx Number Failures The number of times a far-end transmit failure alarm condition has been entered on this link.

NE Rx Number Failures

The number of times a near-end receive failure alarm condition has been entered on this link.

FE Rx Number Failures The number of times a far-end receive failure alarm condition has been entered on this link.

Table 4-19. Performance Monitoring Statistics Dialog Box Fields (IMA Link) (Continued)

Field Description



5

Testing Modules, Ports, and Channels

This chapter describes how to test hardware modules (including processor, I/O, and BIO modules), physical ports, and channels. Navis EMS-CBGX diagnostic and loopback tests help you to detect potential failures or problems with your switch hardware.

You can obtain node-level diagnostic information for a selected switch, as well as physical and logical port-level diagnostic information. Navis EMS-CBGX provides the following diagnostic programs:

Background Diagnostics — Run continuously in background to monitor the switches for potential failures or problems. Background diagnostics execute automatically and do not interfere with switch operations.

Foreground Diagnostics — Provide current status for all active switches and enable you to test physical and logical port integrity.

Background Diagnostics

This section describes the problems detected by background diagnostics and how to view background diagnostic information in Navis EMS-CBGX. This section includes:

• “Problems Detected by Background Diagnostics” on page 5-1

• “Viewing Background Diagnostics” on page 5-2

• “Switching to a Redundant Unit” on page 5-6

Problems Detected by Background Diagnostics

Background diagnostics can alert you to the following types of problems that can occur on an active switch:

• Corruption of different data structures

• Corruption of code space



Testing Modules, Ports, and ChannelsBackground Diagnostics

Background diagnostics provide real-time status information, categorized by fatal and non-fatal errors.

Fatal errors — Includes those conditions that cause the switch to fail and reboot and may also include user-initiated outages, such as a requested reboot, synchronization, or software download. Document and report any non-user initiated fatal errors to the Lucent Technical Assistance Center (TAC).

Non-fatal errors — Includes those conditions whereby system resources are strained by some event, either internally or externally. Non-fatal errors are also reported to the NMS via trap alarms and viewed through the Lucent Events browser. See Chapter 18, “Monitoring MIB Values,” for information about trap alarms.

Viewing Background Diagnostics

To run background diagnostics for a switch:


2. Right-click on the module and select Diagnostics from the popup menu.

The Card Diagnostics dialog box appears (Figure 5-1).

Figure 5-1. Card Diagnostics Dialog Box

3. If the module is an IOM or BIO, choose the Background button.

Note – This guide does not describe how to resolve a fatal error.

Beta Draft ConfidentialTesting Modules, Ports, and Channels



(For processor modules, the Background button is enabled by default, and you cannot change it.)

4. If the module is a processor module (NP, SP, or CP), choose either the Active or Stand By button, depending on whether you want to test the active or the standby module.

5. Choose Start.

The results of the test are displayed in the Card Diagnostics dialog box.

Table 5-1 describes the Card Diagnostics dialog box results.




Table 5-1. Card Diagnostics Dialog Box Fields

Field Displays...

Fatal Error Information about the conditions that caused the switch to fail and reboot.

System Uptime – The System Uptime value at the time the error occurred. For example, if the System Uptime value was 0 days, 22 hours, 24 minutes, and 30 seconds when the error occurred, this field displays: 0 days 22:24:30.

Diagnostics Source – The source from which Navis EMS-CBGX collected the error information. Options include: system level (NP/SP/CP), card level, redundancy manager, BD Heap (Frame-heap memory), power-on diagnostics, background diagnostics, Fault, and Device driver level.

Error Number – The error number containing the major and minor error codes in the format of X.Y (X being the major code and Y being the minor code). See Table B-1 on page B-2 for a list of background diagnostics error codes. For error codes from other sources, contact the TAC.

Number of Reboots – The number of times this switch experienced a reboot condition since the last logged fatal error. If this value is greater than 3, information displayed in the Card Diagnostics dialog box is outdated.

Note: Although the number of Reboots counter is incremented with each reboot, there are instances where the hardware reboots or resets but the screen information does not change. These instances include: the switch powers off and on; the hardware resets (for example, when you use the latch to reset a CBX 500/3500 module); and the CP, SP, or NP continuously polls the modules for status. If a module does not respond, the CP, SP, or NP resets this module.

Crash Address – A crash address for certain types of fatal error conditions. The Lucent TAC uses this address for debugging purposes. If the background diagnostics indicate a crash address, make a note of the address and contact the TAC. This guide does not describe how to resolve a fatal error.

Error String – A text string for the error that may contain more detailed information about the error. See Table B-1 on page B-2 for a description of any text string information that can appear with an error.




Non-Fatal Error Information about those conditions that strain system resources.

System Uptime – The System Uptime value at the time the error occurred. For example, if the System Uptime value was 0 days, 22 hours, 24 minutes, and 30 seconds when the error occurred, this field displays: 0 days 22:24:30.

Diagnostics Source – The source from which Navis EMS-CBGX collected the error information. Options include: system level (NP/SP/CP), card level, redundancy manager, BD Heap (Frame-heap memory), power-on diagnostics, background diagnostics, Fault, and Device driver level.

Error Number – The error number containing the major and minor error codes in the format of X.Y (X being the major code and Y being the minor code). See Table B-1 on page B-2 for a list of background diagnostics error codes. For error codes from other sources, contact the TAC.

Number of Reboots – The number of times this switch experienced a reboot condition since the last logged non-fatal error. If this value is greater than 3, information displayed in the Card Diagnostics dialog box is outdated.

Note: Although the number of Reboots counter is incremented with each reboot, there are instances where the hardware reboots or resets but the screen information does not change. These instances include: the switch powers off and on; the hardware resets (for example, when you use the latch to reset a CBX 500/3500 module); and the CP, SP, or NP continuously polls the modules for status. If a module does not respond, the CP, SP, or NP resets this module.

Error String – A text string for the error that may contain more detailed information about the error. See Table B-1 on page B-2 for a description of any text string information that can appear with an error.

System Uptime The amount of time that the module has been active since its last reboot. For example, if this field displays “7 days 22:31:01,” then 7 days, 22 hours, 31 minutes and 1 second have elapsed since the module’s last reboot.

Number of Tests The number of tests that have occurred on the selected switch.

Pass Count The number of background diagnostic tests that have passed without error.

Fail Count The number of tests that produced an error condition. The failed diagnostics are displayed in the fatal or non-fatal area.

Table 5-1. Card Diagnostics Dialog Box Fields (Continued)

Field Displays...




6. Choose Clear to set the test results to zero, and begin a new test by choosing Start.

7. When you are done viewing the results, choose Close.

The Card Diagnostics dialog box closes.

8. If it appears that a BIO module or NP is failing, consider switching to a redundant module or NP if one is available. See “Switching to a Redundant Unit” on page 5-6 for more information.

Switching to a Redundant Unit

If background diagnostics indicate that an IOM, NP (and accompanying switching fabric and timing module), SP, or CP is failing, switch to a redundant unit if one is available. You should also switch to a redundant unit before removing an active unit.

Redundancy Support on the CBX 3500

The CBX 3500 supports redundancy for the SP 90 and for the following Universal ATM I/O modules:

• 1-Port OC-48c/STM-16 IOA (ATM)

• 4-Port OC-12c/STM-4 IOA (ATM)

• 24-Port DS3 ATM IOA

• 16-port OC-3c/STM-1 ATM

For information on how to configure redundant SP 90s and Universal ATM I/O modules, see the Switch Module Configuration Guide for CBX 3500, CBX 500, GX 550, and B-STDX 9000 for more information.

Remaining Memory (bytes)

The amount of available heap memory on the selected module.

AAL5 Errors Count (ATM modules only)

A count of ATM Adaptation Layer 5 (AAL5) errors.

Total Invalid ATM Cells Received (CBX ATM modules only)

The total number of invalid VPI/VCI ATM cells received on this module.

Last Received Invalid VPI/VCI (CBX ATM modules only)

The last invalid VPI/VCI cell received on a per-module basis. In this case, invalid cell traffic is defined as cells that are received on a physical port that does not have a corresponding PVC or SVC mapped to the received cell’s VPI or VCI.

Table 5-1. Card Diagnostics Dialog Box Fields (Continued)

Field Displays...


Foreground Diagnostics


To Switch to a Redundant Unit


2. Right-click on the module and select Switch to Redundant Unit from the popup menu.

A message appears, stating that this action will activate the redundant card.

3. Choose Yes.


You can run foreground diagnostics on an IOM, a physical port, a channel, an IMA and IMA Enhanced group, or a logical port. You cannot run foreground diagnostics on a CP, SP, or NP.

You use foreground diagnostics to test for problems indicated by background diagnostics (non-fatal errors) or to collect statistical data. You can also run foreground diagnostics to verify that new equipment functions properly.

This section includes:

• “Problems Detected by Foreground Diagnostics” on page 5-7

• “When to Run Foreground Diagnostics on a Physical Port or on Channels” on page 5-8

• “External Loopback Connectors” on page 5-8

• “Changing the Admin Status Before Running Tests” on page 5-8

• “Viewing Foreground Diagnostics For an IOM or BIO” on page 5-12

• “Viewing Foreground Diagnostics For a Physical Port or Subport” on page 5-14

• “Viewing Foreground Diagnostics For a Channel” on page 5-15

• “Viewing Foreground Diagnostics For an IMA Group” on page 5-17

• “Viewing Foreground Diagnostics For a Logical Port” on page 5-19

• “Viewing Foreground Diagnostics For a Logical Port on the 2-port ULC Gigabit Ethernet Module” on page 5-21

Problems Detected by Foreground Diagnostics

Foreground diagnostics enable you to:

• Determine whether an IOM, physical port, channel, or logical port is transmitting data properly at the physical link level.

• Isolate the cause of a transmission stall error (error codes 27.1 and 27.2).



Testing Modules, Ports, and ChannelsForeground Diagnostics

Foreground diagnostics provide more information about non-fatal error conditions. The following foreground diagnostic tests are available depending on the component you are testing:

• Internal — Tests the IOM hardware only. You can use this test on all IOMs. This checks the internal hardware of a specific physical port.

• External — Performs an external test that directs signals back toward the source along a communications path to test the ability to send and receive data. This test requires an external loopback connector, which you install on the physical port being tested.

• Loopback — Tests the ability of physical ports, channels, and logical ports to send and receive data. See “Running Loopback Tests” on page 5-22 for more information.

When to Run Foreground Diagnostics on a Physical Port or on Channels

It is recommended that you run foreground diagnostics on a physical port only if it appears red on the Switch Back Panel dialog box.

Do not run foreground diagnostics at the physical port level if individual DS1 or DS0 channels are malfunctioning, but other channels are functioning properly. Instead, run foreground diagnostics on the specific channels.

External Loopback Connectors

The Channelized DS3 IOM requires an external loopback connector to pass internal foreground diagnostic tests. All other IOMs (including the DS3/1/0 FR/IP IOM) do not require an external loopback connector to pass internal foreground diagnostic tests.

Changing the Admin Status Before Running Tests

Before you run foreground diagnostics tests or loopback tests, you must perform the following tasks:

• Set the applicable IOM, physical port, channel, or logical port Admin Status field to Down.

• For physical port and channel tests, review the Transmit Clock Source field on the Modify PPort dialog box and verify that Internal is selected from the pull-down list.

The procedures in this section describe how to modify the admin status and Transmit Clock Source.




Changing an IOM’s or BIO’s Admin Status


2. Right-click on the module and select Modify from the popup menu.

The Modify Card dialog box appears (Figure 5-2).

Figure 5-2. Modify Card Dialog Box

3. From the Admin Status field, select Down.

4. Choose OK to save the changes.

The Modify Card dialog box closes.

Changing a Physical Port’s or Subport’s Admin Status

1. Display the physical port or subports for the module or subcard (see “Displaying Physical Ports and Subports” on page 2-74).

2. Right-click on the physical port or subport and select Modify from the popup menu.

The Modify PPort or Modify Subport dialog box appears (Figure 5-3).




Figure 5-3. Modify PPort Dialog Box

3. Select the General tab in the dialog box, and choose the Admin Status: Down button.

4. If the Transmit Clock Source field does not display Internal, select Internal from the pull-down list.


The dialog box closes.

Changing a Channel’s Admin Status

1. Display the DS1 channels (see “Displaying DS1 Channels” on page 2-86) or the E1 channels (see “Displaying E1 Channels” on page 2-91) for the physical port.

2. Right-click on the channel and select Modify from the popup menu.

The Modify Channel dialog box appears (Figure 5-4).




Figure 5-4. Modify Channel Dialog Box

3. Select the General tab in the Modify Channel dialog box, and choose the Admin Status field’s Down button.

4. If the Transmit Clock Source field does not display Internal, select Internal from the pull-down list.


The Modify Channel dialog box closes.

Changing a Logical Port’s Admin Status

1. Display the module or subcard that holds the logical port (see “Displaying Modules and Subcards” on page 2-54). For a logical port on a 550 ES subcard, display the BIO module that holds the downlink module to the 550 ES.

2. Expand the LPorts class node.

3. Right-click on the logical port and select Modify from the popup menu.

The Modify Logical Port dialog box appears (Figure 5-5).




Figure 5-5. Modify Logical Port Dialog Box

4. Select the General tab in the Modify Logical Port dialog box, and choose the Admin Status field’s Down button.


The Modify Logical dialog box closes.

Viewing Foreground Diagnostics For an IOM or BIO

To view foreground diagnostics for a module:

1. Set the Admin Status field of the module to Down (see “Changing an IOM’s or BIO’s Admin Status,” on page 5-9) if you have not already done so.


3. Right-click on the module and select Diagnostics from the popup menu.

The Card Diagnostics dialog box appears (Figure 5-6).




Figure 5-6. Card Diagnostics Dialog Box

4. Choose the Foreground button in the Type of Diagnostics field.

5. Choose one of the following buttons from the Type of Test field:

Internal – Performs an internal loopback test that checks the module’s hardware only. You can use this test on all IOMs.

External – Performs a test that directs signals back toward the source along a communications path to test the ability of the physical ports on the IOM to send and receive data. This test requires an external loopback connector, which you install on the physical ports you are testing. You can also install the external loopback connector on an external device such as a data server unit (DSU) or router.

6. Choose Start.

The diagnostics results are displayed in the Test Result field.

7. Choose Clear to set the test results to zero, and begin a new test by choosing Start.

8. Choose Stop to end the test.

9. Choose Close.

The Card Diagnostics dialog box closes.

10. When you are finished running foreground diagnostics, reset the IOM’s Admin Status field to Up.




Viewing Foreground Diagnostics For a Physical Port or Subport

To view foreground diagnostics for a physical port or subport:

1. Set the Admin Status field of the physical port or subport to Down and the Transmit Clock Source field to Internal (see “Changing a Physical Port’s or Subport’s Admin Status,” on page 5-9) if you have not already done so.

2. Display the physical ports or subports on the module or subcard (see “Displaying Physical Ports and Subports” on page 2-74).

3. Right-click on the physical port or subport and select Diagnostics from the popup menu.

The PPort Diagnostics dialog box appears (Figure 5-7).

Figure 5-7. PPort Diagnostics Dialog Box

4. Choose the Foreground button for the Type of Diagnostics.




5. Choose one of the following buttons from the Type of Test (available test types differ depending on the module that you are monitoring and the operation mode selected for a T1/E1 module):

Internal – Performs an internal loopback test that checks the module’s hardware only. You can use this test on all IOMs.

External – Performs a test that directs signals back toward the source along a communications path to test the ability of the physical port to send and receive data. This test requires an external loopback connector, which you install on the physical port you are testing. You can also install the external loopback connector on an external device such as a DSU or router.

Loopback – Various loopback tests are listed, depending on the type of physical port selected. See “Running Loopback Tests” on page 5-22 for more information. For some physical ports, such as Fast Ethernet physical ports, loopback tests are not available.

BERT – Bit Error Rate Testing (BERT) generates and monitors BERT patterns and measures the quality of data transmission. See “Running BERTs” on page 5-57 for more information.

6. Choose Start. The results appear in the Results field.

7. When you are done viewing the results, choose Close.

The PPort Diagnostics dialog box closes.

8. After running foreground diagnostics, reset the physical port’s or subport’s Admin Status field to Up and set the physical port’s Transmit Clock Source field back to its original value.

Viewing Foreground Diagnostics For a Channel

To view foreground diagnostics for a channel:

1. Set the Admin Status field of the channel to Down (see “Changing a Channel’s Admin Status,” on page 5-10) and the Transmit Clock Source field to Internal if you have not already done so.

2. Display the DS1 channels (see “Displaying DS1 Channels” on page 2-86) or the E1 channels (see “Displaying E1 Channels” on page 2-91) for a physical port.

3. Right-click on the channel and select Diagnostics from the popup menu.

The Channel Diagnostics dialog box appears (Figure 5-8).




Figure 5-8. Channel Diagnostics Dialog Box

4. Choose one of the following Type of Test fields (available test types differ depending on the I/O module that you are monitoring):

• Internal

• External

• Loopback — See “Running Loopback Tests” on page 5-22 for more information.

• BERT— See “Running BERTs” on page 5-57 for more information.

5. Choose Start.


7. Choose Close.

The Channel Diagnostics dialog box closes.

8. After running foreground diagnostics, reset the channel’s admin status to Up and set the channel’s Transmit Clock Source back to its original value.

Note – You cannot run internal/external foreground diagnostics for a DS1 (T1) channel or an E1 channel if the channel is configured as an IMA or an IMA Enhanced group link.




Viewing Foreground Diagnostics For an IMA Group

To view foreground diagnostics for an IMA or an IMA Enhanced group:


2. Right-click on an active IMA group and select Diagnostics from the popup menu.

The IMA Group Diagnostics dialog box appears (Figure 5-9).

Figure 5-9. IMA Group Diagnostics Dialog Box

3. Complete the fields in the IMA Group Diagnostics dialog box as described in Table 5-2.

Table 5-2. IMA Group Diagnostics Dialog Box Fields

Field Action/Description

Test Mode Select one of the following options:

Automatic – (default) Changes the test pattern automatically every 10 seconds, starting with a randomly chosen pattern.

Manual – Enables you to select a test pattern. The range of available patterns is 1 to 254.




4. Choose the T1 or E1 link button that corresponds to the interface over which the test pattern will be transmitted, and choose Start.

The results appear in the Link field. Table 5-3 describes the IMA Group Diagnostics dialog box results.

Test Pattern (1...254)

When Manual Test Mode is enabled, you can choose a value in the range 1 to 254, which specifies the test pattern in an IMA group loopback operation.

The test pattern procedure verifies the connectivity of a link within an IMA group. The test pattern starts with the selected link and then verifies the connectivity to the rest of the links in the IMA group.

The test pattern loops over all the other links in the IMA group at the far end (FE). The test pattern value is carried over IMA Control Protocol (ICP) cells that are exchanged between both ends of the IMA virtual links.

For more information about test patterns, see The ATM Forum Technical Committee Inverse Multiplexing for ATM (IMA) Specification Version 1.1 (AF-PHY-0086.001).

Table 5-3. IMA Group Diagnostics Dialog Box Results


Group

Tx Link Interface Identifies the first in the series of IMA link interfaces over which the test pattern is transmitted.

Test Pattern Identifies the test pattern received in the ICP cell on the link during the IMA test pattern procedure. This value can be compared to the transmitted test pattern.

Status Displays the current state of the test pattern procedure for the specified link interface.

Time Reported Displays the timestamp for the current state of the active test pattern. The time is updated every 6 seconds.

Link

T1 or E1 Link Buttons

Choose one of the T1 or E1 links participating in the IMA group. The range is from 1 to 8. Starting with the selected link, all the other links in the IMA group are tested in turn.

Interface Displays the link interface over which the test pattern is transmitted.

Table 5-2. IMA Group Diagnostics Dialog Box Fields (Continued)





5. Chose Stop to end the test.

6. Choose Close.

The IMA Group Diagnostics dialog box closes.

Viewing Foreground Diagnostics For a Logical Port

To view foreground diagnostics for a logical port:

1. Set the Admin Status field of the logical port to Down (see “Changing a Logical Port’s Admin Status,” on page 5-11) if you have not already done so.

2. Display the module or subcard that holds the logical port (see “Displaying Modules and Subcards” on page 2-54).


4. Right-click on the logical port and select Diagnostics from the popup menu.

The Diagnostics dialog box appears (Figure 5-10).

Test Pattern Identifies the test pattern received in the ICP cell on the link during the IMA test pattern procedure. This value can be compared to the transmitted test pattern.

Status Displays the current state of the link test pattern procedure.

Time Reported Displays the timestamp for the current state of the active test pattern. The time is updated every 6 seconds.

Table 5-3. IMA Group Diagnostics Dialog Box Results (Continued)





Figure 5-10. Diagnostics Dialog Box (Logical Port)

5. Choose one of the following buttons from the Type of Test field (available test types differ depending on the I/O module that you are monitoring):

Internal – Performs an internal loopback test that checks the hardware of the IOM used by the logical port only. You can use this test on all modules.

External – Performs an external test that enables you to direct signals back toward the source along a communications path to test the port’s ability to send and receive data. This test requires an external loopback connector, which you install on the physical port that is used by the logical port you are testing. You can also install the external loopback connector on an external device such as a DSU or router.

Loopback – See “Running Loopback Tests” on page 5-22 for more information.

BERT tests –See “Running BERTs” on page 5-57 for more information.

6. Choose Start.

The results appear in the Results area.

7. Choose Stop.

8. Choose Close.

The Diagnostics dialog box closes.

9. After running foreground diagnostics, reset the logical port’s Admin Status to Up.




Viewing Foreground Diagnostics For a Logical Port on the 2-port ULC Gigabit Ethernet Module

To view foreground diagnostics for a logical port on the 2-port ULC Gigabit Ethernet module):

1. Set the Admin Status field of the logical port to Down (see “Changing a Logical Port’s Admin Status,” on page 5-11) if you have not already done so. Set the Admin Status field of the physical port to Up.



4. Display the LPort Statistics Monitoring dialog box (see “Viewing 2-port ULC Gigabit Ethernet LPort Object Summary Statistics” on page 7-17).

5. Choose the Diagnostics command button.


Figure 5-11. Diagnostics Dialog Box (Logical Port, 2-port ULC Gigabit Ethernet Module)

6. Choose one of the following buttons from the Type of Test field :

Internal – Performs an internal loopback test that checks the hardware of the IOM used by the logical port only. You can use this test on all modules.



Testing Modules, Ports, and ChannelsRunning Loopback Tests

External – Performs an external test that enables you to direct signals back toward the source along a communications path to test the port’s ability to send and receive data. This test requires an external loopback connector, which you install on the physical port that is used by the logical port you are testing. You can also install the external loopback connector on an external device such as a DSU or router.

7. In the Diagnostic Test Run panel, enter the number of packets to be tested in the Number of Diag Packets: (1-50) field.

8. Choose Start.

The results appear in the Diagnostic Test Result (Correct/Incorrect Packets Received) and Results (Passed/Failed) panels.

9. Choose Stop.

10. Choose Close.


11. After running foreground diagnostics, reset the logical port’s Admin Status to Up.

Running Loopback Tests

This section describes how to initiate and monitor loopback diagnostic functions. Loopback testing can be used on physical ports, channels, and logical ports as a means of verifying data integrity and for general troubleshooting purposes. You can run a loopback test online or offline, depending on the loopback type.

Lucent switches support the following hardware loopback tests:

• “Loopback Tests For DS3/E3 Physical Ports” on page 5-23

• “Loopback Tests for HSSI Physical Ports” on page 5-26

• “Loopback Tests for OC-n/STM-n Physical Ports” on page 5-28

• “Loopback Tests For Physical Ports on T1 or E1 Modules” on page 5-30

• “Loopback Tests For T1 Physical Ports on the 32-Port Channelized T1/E1 FR/IP Module and 60-Port Channelized T1/E1 Circuit Emulation Module” on page 5-35

• “Loopback Tests For E1 Physical Ports on the 32-Port Channelized T1/E1 FR/IP Module and 60-Port Channelized T1/E1 Circuit Emulation Module” on page 5-39

• “Near-End Loopback Tests for DS1 Channels” on page 5-40

• “Far-End Loopback Tests for DS1 Channels” on page 5-43

• “Near-End Loopback Tests for E1 Channels” on page 5-47

• “Near-End Loopback Tests for DS0 Channels” on page 5-48

• “Far-End Loopback Tests for DS0 Channels” on page 5-51




Restrictions

The following restrictions apply to loopback tests:

• The applicable module, physical port, channel, or logical port Admin Status fields must be set to Down, and the Transmit Clock Source field must be set to Internal for physical ports and channels. See “Changing the Admin Status Before Running Tests” on page 5-8.

• All DS0, DS1, and DS3 loopback tests are latching loopback tests.

• Do not attempt to modify a physical port or channel while it is undergoing loopback testing.

Loopback Tests For DS3/E3 Physical Ports


• “Types of DS3/E3 Physical Port Loopback Tests” on page 5-23

• “DS3/E3 Loopback Traps” on page 5-25

Types of DS3/E3 Physical Port Loopback Tests

Table 5-4 lists and describes the types of DS3/E3 physical port loopback tests on the B-STDX 9000 and CBX 500/3500 modules. Some DS3/E3 modules do not support all of the loopback tests described in Table 5-4.




Table 5-4. DS3/E3 Loopback Tests

Loopback Test Description

Near-end line Loops the receiver to the transmitter to loop the incoming signal back to the far-end.

Far-end line Sends a code to request the far-end to set itself into loopback mode.

This type of loopback involves sending an in-band FEAC loop-up signal to the device attached to the physical port. When you start this test, the attached device responds by placing itself in the FEAC loop-up state (assuming the attached device supports FEAC loop-up and down signaling). The attached device will remain in that state until you stop the test (which causes a FEAC loop-down signal to be sent). Running this test has no effect on the DS3 physical port (other than the attached device entering a FEAC loop-up state).

This loopback test can be used in conjunction with the external loopback test, as the attached device can first be placed in a FEAC loop-up state using the far-end loopback test, and then the external loopback test can be run. The fact that the attached device will be in a FEAC loop-up state means that if the transmission path is good, the test should pass.

Note – Enabling/Disabling of the FEAC loopback option is not supported on the 4-port Channelized DS3 module. Although FEAC loopback functionality is supported—the switch still processes the FEAC command and puts the physical port in loopback—enabling/disabling functionality is not supported on this module.

Payload A near-end loopback in which the signal transmitted beyond the loopback point (the forward signal) when the loopback is activated is the same as the received signal at the loopback point.

This type of loopback is similar to a near-end line loopback in that the incoming signal from the device attached to the physical port is looped back. However, with the payload loopback, the loopback is made after the physical port framer device, such that the signal from the outside traverses the framer device and is then looped back. This is a more comprehensive test than the near-end line loopback because when you verify the integrity of the signal passing through the loopback, the integrity of the CBX 500/3500 card framer is also verified. The physical port remains in this state until you stop the test.

Near-end diag Loops the transmitter to the receiver to loop the outgoing signal back to the DS3 port. This test enables the module to test itself.




DS3/E3 Loopback Traps

The NMS generates a trap when a DS3 interface changes its loopback state. For more information about the type of trap that the NMS generates, see Appendix A, “Trap Alarm Condition Messages.”

Running a DS3/E3 Loopback Test

To run a DS3/E3 physical port loopback test:

1. Set the Admin Status field of the physical port to Down and the Transmit Clock Source field to Internal (see “Changing a Physical Port’s or Subport’s Admin Status,” on page 5-9) if you have not already done so.

2. Display the physical ports on the module or subcard (see “Displaying Physical Ports and Subports” on page 2-74).

3. Right-click on the physical port and select Diagnostics from the popup menu.



4. Choose the Loopback button from Type of Test field.

5. From the Loopback Type field’s pull-down list, select the type of loopback test you want to generate. the options are:

• Near-end line

• Far-end line

• Payload (ATM DS3 modules only)

• Near-end diag (Channelized DS3 modules and 24-Port DS3 only)




Table 5-4 on page 5-24 describes each of these loopback tests.

6. Choose Start to start the test pattern generation.

Test results appear in the Results field at the bottom of the PPort Diagnostics dialog box.

7. Choose Stop to return to a normal state.

8. Choose Close.


9. After running the loopback test, reset the physical port’s Admin Status field to Up and set the physical port’s Transmit Clock Source field back to its original value.

Loopback Tests for HSSI Physical Ports


• “Types of HSSI Physical Port Loopback Tests” on page 5-26

• “Running a HSSI Loopback Test” on page 5-27

Types of HSSI Physical Port Loopback Tests

High-Speed Serial Interface (HSSI) loopbacks on the B-STDX 9000 are initiated by the DTE through the HSSI LA/LB interface signals. The B-STDX 9000 switch drives these signals when you initiate the loopback from the NMS.

Table 5-5 lists and describes the types of HSSI physical port loopback tests on the B-STDX 9000.

Note – The loopback state is not stored in PRAM. If you reboot the module, the DS3/E3 module returns to a normal state.

Table 5-5. HSSI Loopback Tests


External Local DTE Sends a signal to the DSU to indicate that the DTE (switch) is performing a loopback test on the HSSI interface.

External Local Line Sends a signal to the DSU to indicate that the DTE (switch) is performing a loopback test on the DSU DS3 interface.

External Remote Line Sends a signal to the DSU to indicate that the DTE (switch) is performing a loopback test on the DSU DS3 interface.




Running a HSSI Loopback Test

To run a HSSI physical port loopback test:


2. Display the physical ports on the module (see “Displaying Physical Ports and Subports” on page 2-74).




4. Choose the Loopback button from the Type of Test field.

5. From the Loopback Type pull-down list, select the type of loopback test you want to generate:

• Ext Local DTE Loopback

• External Local Line

• External Remote Line





8. Choose Close.






Loopback Tests for OC-n/STM-n Physical Ports


• “Types of OC-n/STM-n Physical Port Loopback Tests” on page 5-28

• “Running an OC-n/STM-n Loopback Test” on page 5-28

Types of OC-n/STM-n Physical Port Loopback Tests

Table 5-6 lists and describes the types of OC-n/STM-n physical port loopback tests that are available.

Running an OC-n/STM-n Loopback Test

To run an OC-n/STM-n physical port loopback test:

1. Set the Admin Status field of the physical port or subport to Down and the Transmit Clock Source field to Internal (see “Changing a Physical Port’s or Subport’s Admin Status,” on page 5-9) if you have not already done so.



Table 5-6. OC-n/STM-n Loopback Tests


Near-End Line Loopback

Enables the input/output adapter (IOA) component of the module to transmit received cells back to the sender, without passing the cells to the module. When you initiate a line loopback, the entire physical port is put into the loopback from the near-end. This enables you to generate and receive line loopback code from the physical port of these modules.

Note: This is the only option available for Universal OC-n/STM-n IOAs.

Internal Loopback Sets up a cell loopback signal between the IOM component of the module and the IOA component of the module. This signal does not go “off card.” Use this test to check IOM and IOA internal hardware.

External Loopback Performs a cell loopback test that directs a signal back towards the source. This tests the ability of the port to send and receive data. You must install a fiber optic loopback connector on the physical port you are testing.







5. From the Loopback Type pull-down list, select the type of loopback test you want to generate:

• Near End Line Loopback (only option for Universal OC-n/STM-n IOAs.)

• Internal Loopback

• External Loopback





Note – The loopback state is not stored in PRAM. If you reboot the module, the module returns to a normal state.




8. Choose Close.



Loopback Tests For Physical Ports on T1 or E1 Modules


• “Modules Covered in This Section” on page 5-30

• “Types of T1/E1 Physical Port Loopback Tests” on page 5-30

• “Network Response to a T1/E1 Loopback” on page 5-32

• “Running a Physical Port Loopback Test on a T1 or E1 Module” on page 5-33

Modules Covered in This Section

This section applies to modules that have T1 or E1 physical ports, but not to modules that have a configurable operation mode that lets them function as either T1 modules or E1 modules. This section therefore does not apply to either the 32-Port Channelized T1/E1 FR/IP or the 60-Port Channelized T1/E1 Circuit Emulation modules.

Types of T1/E1 Physical Port Loopback Tests

The type of loopback tests that are available for the T1 and E1 modules (including 10-Port DSX modules on the B-STDX 9000) depends on the physical port’s configured circuit type (Superframe or Extended Superframe) and the specific module on which it resides.

Table 5-7 describes the types of T1/E1 loopback tests. Some T1/E1 modules do not support all of the tests described in Table 5-7.

Table 5-7. T1/E1 Loopback Tests

Test Circuit Type Description

Metallic (ATM IOMs only)

Superframe & Extended Superframe

Performs a cell loopback test that checks the IOM and IOA component of the module.




Payload loopback


Similar to a near-end line loopback in that the incoming signal from the device attached to the physical port is looped back. However, with the payload loopback, the loopback is made after the physical port framer device such that the signal from the outside traverses the framer device and is then looped back.

This payload loopback test (unlike the near-end line loopback), simultaneously verifies the integrity of the switch framer when it verifies the integrity of the signal passing through the loopback.

The physical port remains in this state until you stop the test.

Line

(Near-End)


A near-end loopback where the external data stream is looped back prior to clock recovery and framing. The external device therefore receives its own clocked signal back.

Framed inband line


A static loopback command mode where the far-end equipment is commanded into line loopback via the previously selected in-band line loopback code channel service unit (CSU) or Network Interface (NI). Using this command, framed loopback control commands are sent to the far end.

• Choose Start Test to send loop-up code for 5 seconds; the far-end equipment responds by initiating a line loopback.

• Choose Stop Test to send loop-down code for 5 seconds; the far-end equipment responds by terminating the line loopback mode.

Unframed inband line


A static loopback command mode where the far-end equipment is commanded into line loopback via the previously selected in-band line loopback code CSU or NI. Using this command, unframed loopback control commands are sent to the far end.

• Choose Start Test to send loop-up code for 5 seconds; the far-end equipment responds by initiating a line loopback.

• Choose Stop Test to send loop-down code for 5 seconds; the far-end equipment responds by terminating the line loopback mode.

Table 5-7. T1/E1 Loopback Tests (Continued)





Network Response to a T1/E1 Loopback

The following list outlines the network’s response to a T1/E1 line or payload loopback.

1. The T1/E1 port receives a line or payload T1/E1 loop activate code from the network.

2. The framer detects the loop code and interrupts the processor.

3. The processor responds by activating the desired loopback.

4. The polling mechanism detects an active loopback status and the port operating status is changed to Down.

ESF FDL line (ANSI)

Extended Superframe

A static loopback command mode where the far-end equipment is commanded into line loopback via the T1 extended service frame (ESF) out-of-band facility data link (FDL) loopback control commands. This option is available only if you configure the physical port with Extended Superframe ESF and FDL enabled.

• Choose Start Test to send loop-up code; the far-end equipment responds by initiating a line loopback.

• Choose Stop Test to send loop-down code; the far-end equipment terminates the line loopback mode.

ESF FDL payload (ANSI)

Extended Superframe

A static loopback command mode where the far-end equipment is commanded into payload loopback via the T1 ESF out-of-band FDL loopback control commands. This option is available only if you configure the physical port with Extended Superframe ESF and FDL enabled.

• Choose Start Test to send loop-up code; the far-end equipment responds by initiating a payload loopback.

• Choose Stop Test to send loop-down code; the far-end equipment terminates the payload loopback mode.

Table 5-7. T1/E1 Loopback Tests (Continued)


Note – Lucent only supports a CSU-type loopback code from the network.




5. A trap is issued to the NMS indicating the change in loopback status. For more information about the type of trap that the NMS generates, see Appendix A, “Trap Alarm Condition Messages.”

6. The loopback status is updated on the PPort Attributes dialog box and the PPort Foreground Diagnostics dialog box.

7. A user at the far-end can initiate tests to test the link that has just looped back.

8. After completion of tests, a loop deactivate code is sent to the near-end port.

9. The framer detects the loop code and interrupts the processor.

10. The processor responds by deactivating the specified loopback.

11. The polling mechanism detects the change to a Normal operating status and the port operating status changes to Up.

12. The system updates the loopback status on the PPort Attributes dialog box and the PPort Foreground Diagnostics dialog box.

Running a Physical Port Loopback Test on a T1 or E1 Module

To run a T1 or E1 physical port loopback test:










5. From the Loopback Type field’s pull-down list, select the type of loopback test you want to generate. The options are:

• Metallic Loopback (ATM IOMs only)

• Payload loopback

• Near-End Line Loopback

• Framed inband line loopback

• Unframed inband line loopback

• ESF FDL line loopback (ANSI)

• ESF FDL payload loopback (ANSI)



Test results appear in the Results box at the bottom of the PPort Diagnostics dialog box.


8. Choose Close.







Loopback Tests For T1 Physical Ports on the 32-Port Channelized T1/E1 FR/IP Module and 60-Port Channelized T1/E1 Circuit Emulation Module


• “Types of T1 Physical Port Loopback Tests For the 32-Port and 60-Port Channelized T1/E1 Modules” on page 5-35

• “Running a T1 Loopback Test (32-port and 60-port modules)” on page 5-36

Types of T1 Physical Port Loopback Tests For the 32-Port and 60-Port Channelized T1/E1 Modules

The T1 loopback tests described in this section are available for physical ports on 32-Port Channelized T1/E1 FR/IP and 60-Port Channelized T1/E1 Circuit Emulation modules configured in T1 operation mode.

Table 5-8 lists and describes the types of T1 loopback tests that are available.

Table 5-9 describes the types of far-end loopback tests that you can generate and receive if you select DS1 Far End Loopback as the Loopback Type.

Table 5-8. T1 Loopback Tests (32-Port and 60-Port modules)


Payload Loopback A near-end loopback in which the incoming DS1 payload is looped back toward the network after extracting and reinserting the framing pattern into the transmitted DS1 data stream.

Near End Line Loopback

A near-end loopback that operates upon receipt of a specific framed pulse pattern. The line loopback pulse codes and functions are either Activate or Deactivate.

Near End Diag Loopback

A near-end loopback in which the transmitted signal is returned as the received signal. This test is internal to the module and does not require a CSU/DSU.

DS1 Far End Loopback A far-end loopback test to loop data from the switch to the DACS/MUX or CSU/DSU and back to the originating switch.




Running a T1 Loopback Test (32-port and 60-port modules)

To run a T1 physical port near-end loopback test on the 32-Port Channelized T1/E1 FR/IP and 60-Port Channelized T1/E1 Circuit Emulation modules:

Table 5-9. DS1 Far-End Loopback Tests (32-Port and 60-Port modules)


Activate Framed CSULine Loopback

Requested by the CSU; returns information to the switch on the receive line.

Release Framed CSULine Loopback

Sends a CSU code to stop the far-end loopback and return to normal two-way traffic.

Activate NI Line Loopback

Requested by the network interface (NI); returns information to the switch on the receive line.

Release NI Line Loopback

Sends an NI code to stop the far-end loopback.

Activate ESF ANSI Line Loopback

Requested by Extended Superframe Format (ESF); returns information to the switch on the receive line.

Release ESF ANSI Line Loopback

Sends an ESF code to stop the far-end loopback.

Activate ESF ANSI Payload Loopback

Requested by ESF; returns information to the switch as framed data.

Release ESF ANSI Payload Loopback

Sends an ESF American National Standards Institute (ANSI) code to stop the far-end payload loopback.

Activate Unframed CSU Line Loopback


Release Unframed CSU Line Loopback

Sends a CSU code to stop the far-end line loopback and return to normal two-way traffic.

Activate Unframed NI Line Loopback

Requested by the NI; returns information to the switch on the receive line.

Release Unframed NI Line Loopback

Sends an NI code to stop the far-end line loopback.

Activate OOB NI Line Loopback

Requested by an out of band (OOB) NI; returns information to the switch on the receive line.

Release OOB NI Line Loopback

Sends an out of band NI code to stop the far-end line loopback.










Note – Make sure the physical port you are testing resides on a 32-Port or 60-Port Channelized T1/E1 configured in T1 operation mode.




5. From the Loopback Type field’s pull-down list, select the type of loopback test you want to generate. The options include:

• Payload Loopback

• Near End Line Loopback

• Near End Diag Loopback

• DS1 Far End Loopback

Do not select the Clear Loopback option at this point. This option is for stopping a test.


6. If you selected DS1 Far End Loopback in step 5, select the type of far end loopback test you want to run from the Far End Loop back Test Type field’s pull-down list. The options include:

• Activate Framed CSU Line Loopback

• Activate NI Line Loopback

• Activate ESF ANSI Line Loopback

• Activate ESF ANSI Payload Loopback

• Activate Unframed CSU Line Loopback

• Activate Unframed NI Line Loopback

• Activate OOB NI Line Loopback

See Table 5-9 on page 5-36 for a description of these options.

Do not select a Release [Test Type] Loopback option (for example, Release NI Line Loopback) at this point. The Release options are for stopping a test.

7. Choose Start to begin the test.

The loopback test takes approximately 15 seconds to complete. Test results appear in the Loopback Status field.

8. To stop the test, select Release [Test Type] Loop back (for example, Release NI Line Loopback) in the Far End Loopback Test Type field’s pull-down list and choose Start.

9. Choose Close.


Note – If you choose Close before stopping the test, the test will continue to run and the Port Admin Status field will remain Down. To stop the test, you must select Release [Test Type] Loopback in the Far End Loop back Test Type field’s pull-down list and then choose Start.





Loopback Tests For E1 Physical Ports on the 32-Port Channelized T1/E1 FR/IP Module and 60-Port Channelized T1/E1 Circuit Emulation Module


• “Types of E1 Physical Port Loopback Tests For the 32-Port and 60-Port Channelized T1/E1 Modules” on page 5-39

• “Running an E1 Near-End Loopback Test (32-port and 60-port modules)” on page 5-39

Types of E1 Physical Port Loopback Tests For the 32-Port and 60-Port Channelized T1/E1 Modules

The E1 near-end loopback tests described in this section are available for physical ports on 32-Port Channelized T1/E1 FR/IP and 60-Port Channelized T1/E1 Circuit Emulation modules configured in E1 operation mode. Table 5-10 lists and describes the types of E1 near-end loopback tests that are available.

Running an E1 Near-End Loopback Test (32-port and 60-port modules)

To run an E1 physical port near-end loopback test on the 32-Port Channelized T1/E1 FR/IP and 60-Port Channelized T1/E1 Circuit Emulation modules:


Table 5-10. E1 Loopback Tests (32-Port and 60-Port modules)


Payload Loopback A near-end loopback in which the incoming E1 payload is looped back toward the network after extracting and reinserting the framing pattern into the transmitted E1 data stream.

Near End Line Loopback

A near-end loopback that operates upon receipt of a specific framed pulse pattern. The line loopback pulse codes and functions are either Activate or Deactivate.

Near End Diag Loopback

A near-end loopback in which the transmitted signal is returned as the received signal. This test is internal to the 32-Port Channelized T1/E1 FR/IP IOM and does not require a CSU/DSU.







4. Choose Loopback button from the Type of Test field.

5. From the Loopback Type field pull-down list, select the type of loopback test you want to generate. The options include:


• Near End Line Loopback

• Near End Diag Loopback

Do not select the Clear Loopback option at this point. This option is for stopping a test.


6. Choose Start to begin the test pattern generation.



8. Choose Close.



Near-End Loopback Tests for DS1 Channels


• “About DS1 Channel Near-End Loopback Tests” on page 5-40

• “Running a DS1 Channel Near-End Loopback Test” on page 5-42

About DS1 Channel Near-End Loopback Tests

The DS1 channel near-end loopback option enables you to test the physical path for data transmission. When you initiate the test, the entire DS1 channel of the physical port is put into loopback mode from the near-end. The DS1 channel near-end loopback test is available for channelized DS3 and channelized DS3/1/0 modules.

Note – Make sure the physical port you are testing resides on a 32-Port or 60-Port Channelized T1/E1 configured in E1 operation mode.




Table 5-11 lists and describes the types of DS1 near-end loopback tests that are available.

Figure 5-17 illustrates a near-end loopback test in which the test pattern originates at the CSU/DSU and passes through the DACS/MUX. The multiplexer (MUX) joins the 28 DS1 channels and combines them into one DS3 signal. The signal is looped back at the DS3 port and returned to the CSU/DSU.

Figure 5-17. Near-End Diag Loopback

Figure 5-18 illustrates a near-end loopback test in which the test pattern originates at the CSU/DSU and passes through the DACS/MUX. The multiplexer (MUX) joins the 28 DS1 channels and combines them into one DS3 signal. The signal is looped back at the DS3 port and returned to the CSU/DSU.

Table 5-11. DS1 Near-End Loopback Tests


Payload (Channelized DS3 modules only.) A near-end loopback in which the incoming DS1 payload is looped back toward the network after extracting and reinserting the framing pattern into the transmitted DS1 data stream.

Line Loopback A near-end loopback that operates upon receipt of a specific framed pulse pattern. The line loopback pulse codes and functions are either Activate or Deactivate. You can perform line loopback tests on each of the 28 DS1 channels.

Diagnostic Loopback

A near-end loopback in which the transmitted signal is returned as the received signal. This test is internal to the Channelized DS3 module, Channelized T1/E1 FR/IP module, or DS3/1/0 FR/IP module and does not require a CSU/DSU. Figure 5-17 illustrates a DS1 near-end diag loopback in which the test pattern generation originates at the Channelized DS3 module and loops back to the Channelized DS3 module. This test is internal to the module.

The near-end diag loopback test takes place at the switch. This example illustrates a test pattern generation originating from the Channelized DS3 module and looped back to the module. This test is internal to the Channelized DS3 module. You can use thistest without a CSU/DSU.

Looped-back DS3 Port

CSU/DSU

28 DS1s

B-STDX

DS3

MUX /DACS




Figure 5-18. Near-End Loopback

Running a DS1 Channel Near-End Loopback Test

To run a DS1 near-end loopback test:

1. Set the Admin Status field of the DS1 channel to Down and the Transmit Clock Source field to Internal (see “Changing a Channel’s Admin Status,” on page 5-10) if you have not already done so.

2. Display the DS1 channels (see “Displaying DS1 Channels” on page 2-86) for a physical port.


The Perform Foreground Channel Diagnostics dialog box appears (Figure 5-19).

Figure 5-19. Perform Foreground Channel Diagnostics Dialog Box

The near-end loopback test takes place at the switch. This example illustrates a test pattern generation originating from the CSU/DSU.


28 DS1s

CSU/DSU

B-STDX

DS3

MUX /DACS




4. Choose DS1 Near End Loopback button from the Type of Test field.

5. From the Select Loopback Type field’s pull-down list, select the type of loopback test you want to generate:

• Line Loopback

• Diagnostic Loopback





7. To stop the test, select Clear Loopback from the Select Loopback Type field’s pull-down list, and then choose Start.

8. Choose Close.

The Perform Foreground Channel Diagnostics dialog box closes.

9. After running the test, reset the channel’s Admin Status field to Up and set the channel’s Transmit Clock Source field back to its original value.

Far-End Loopback Tests for DS1 Channels


• “About DS1 Channel Far-End Loopback Tests” on page 5-43

• “Running a DS1 Channel Far-End Loopback Test” on page 5-45

About DS1 Channel Far-End Loopback Tests

Use the far-end loopback option to loop data from the switch to the DACS/MUX or CSU/DSU and back to the originating switch.

Table 5-12 lists and describes the types of far-end loopback tests you can generate and receive from the DS1 channel (the default Test Type is Send No Code).

Note – If you choose Close before stopping the test, the test will continue to run and the channel Admin Status field will remain Down. To stop the test, select Clear Loopback from the pull-down list in the Select Loopback Type field and then choose Start.




Figure 5-20 illustrates a far-end CSU/DSU loopback that takes place at the CSU/DSU.

Table 5-12. Far-End Loopback Tests


Activate Framed CSULine Loopback


Release Framed CSULine Loopback

Sends a CSU code to stop the far-end loopback and return to normal two-way traffic.

Activate NI Line Loopback


Release NI Line Loopback

Sends an NI code to stop the far-end loopback.

Activate ESF ANSI Line Loopback

Requested by ESF ANSI; returns information to the switch on the receive line.

Release ESF ANSI Line Loopback

Sends an ESF code to stop the far-end loopback.

Activate ESF ANSI Payload Loopback

Requested by ESF; returns information to the switch as framed data.

Release ESF ANSI Payload Loopback

Sends an ESF ANSI code to stop the far-end payload loopback.

Activate Unframed CSU Line Loopback


Release Unframed CSU Line Loopback

Sends a CSU code to stop the far-end line loopback and return to normal two-way traffic.

Activate Unframed NI Line Loopback


Release Unframed NI Line Loopback

Sends an NI code to stop the far-end line loopback.

Activate OOB NI Line Loopback

Requested by an out of band NI; returns information to the switch on the receive line.

Release OOB NI Line Loopback

Sends an out of band NI code to stop the far-end line loopback.




Figure 5-20. DS1 Far-End CSU/DSU Loopback

Figure 5-21 illustrates a DS1 far-end NI loopback using Smartjacks and/or a Midspan Repeater. The NI loopback originates at the CSU/DSU and test pattern generation originates at the switch.

Figure 5-21. DS1 Far-End NI Loopback

Running a DS1 Channel Far-End Loopback Test

To run a DS1 far-end loopback test:




The Perform Foreground Channel Diagnostics dialog box appears (Figure 5-22).

The far-end CSU/DSU loopback test takes place atthe CSU/DSU. This example illustrates a CSU/DSU in loopback and a test pattern generation originating from the switch.


28 DS1s

CSU/DSU

B-STDX

MUX /DACS


1 DS3

28 DS1s SmartjackorMidspanRepeater

CSU/DSU

B-STDX

MUX /DACS




Figure 5-22. Perform Foreground Channel Diagnostics Dialog Box

4. Choose DS1 Far End Loopback button from the Type of Test field.

5. From the Select Loopback Type field’s pull-down list, select the type of loopback test you want to generate:

• Activate Framed CSU Line Loopback

• Activate NI Line Loopback

• Activate ESF ANSI Line Loopback

• Activate ESF ANSI Payload Loopback

• Activate Unframed CSU Line Loopback

• Activate Unframed NI Line Loopback

• Activate OOB NI Line Loopback


Do not select Release [Test Type] Loopback from the Select Loopback Type field’s pull-down list at this time. This option is for stopping a test.



7. To stop the test, select Release [Test Type] Loopback from the Select Loopback Type field’s pull-down list, and then choose Start.

8. Choose Close.

Note – If you choose Close before releasing the test, the test will continue to run and the channel Admin Status field will remain Down. To stop the test, select Release [Test Type] Loopback, and then choose Start.




The Perform Foreground Channel Diagnostics dialog box closes.


Near-End Loopback Tests for E1 Channels


• “About E1 Channel Near-End Loopback Tests” on page 5-47

• “Running an E1 Channel Near-End Loopback Test” on page 5-47

About E1 Channel Near-End Loopback Tests

The E1 channel near-end loopback option enables you to test the physical path for data transmission. When you initiate the test, the entire E1 channel of the physical port is put into loopback mode from the near-end. The ES1 channel near-end loopback test is available for the 1-Port Channelized STM-1/E1 IMA and IMA Enhanced Module.

Running an E1 Channel Near-End Loopback Test

To run an E1 near-end loopback test:

1. Set the Admin Status field of the E1 channel to Down and the Transmit Clock Source field to Internal (see “Changing a Channel’s Admin Status,” on page 5-10) if you have not already done so.

2. Display the E1 channels (see “Displaying E1 Channels” on page 2-91) for a physical port.








Near End Line Loopback is displayed in the Loopback Type field.


Test results appear in the Loopback Status field.


7. Choose Close.


8. After running the loopback test, reset the channel’s Admin Status field to Up and set the channel’s Transmit Clock Source field back to its original value.

Near-End Loopback Tests for DS0 Channels


• “Modules Supported By DS0 Near-End Loopback Tests” on page 5-49

• “About DS0 Near End Loopback Tests” on page 5-49

• “Running a DS0 Near-End Loopback Test” on page 5-50





Modules Supported By DS0 Near-End Loopback Tests

The DS0 near-end loopback test is available for:

• Channelized T1 modules

• 4-Port Channelized DS3 FR/IP modules

• 4-Port DSX modules

• 32-Port Channelized T1/E1 FR/IP module in either the T1 or E1 mode.

The DS0 near-end loopback test is not available for the 60-Port Channelized T1/E1 Circuit Emulation Module.

About DS0 Near End Loopback Tests

The DS0 near-end loopback option enables you to test the transmission path of a logical port by looping back traffic in one or both directions. You can initiate a DS0 near-end loopback over one or more contiguous DS0 channels of a logical port. Use the DS0 near-end loopback option to loop back traffic from the office channel unit (OCU), CSU, or DSU.

Figure 5-24 illustrates a DS0 near-end loopback.

Figure 5-24. DS0 Near-End Loopback

Near-end loopback takes place at the B-STDX.

Test pattern generation originates at the OCU, CSU, or DSU.

This example illustrates test pattern generation originating from the OCU.

24 DS0s

CSU/DSU

B-STDX

OCU

Looped Back Port




Running a DS0 Near-End Loopback Test

To run a DS0 near-end loopback test:


2. Display the module or subcard that holds the logical port to which the DS0 is assigned (see “Displaying Modules and Subcards” on page 2-54).




Figure 5-25. Diagnostics Dialog Box

5. Choose DS0 Near End from the Type of Test field.

6. Select the channels on which you want to perform a DS0 near-end loopback. A Y indicates a DS0 is in a loopback state.

You can select one or more channels by clicking on each channel or by using the channel selection buttons in the Allocated Channels field, as described in Table 5-13.

For B-STDX 9000 modules, select consecutive DS0 channels. DS0 loopback on the B-STDX 9000 does not support noncontiguous DS0 channels.




7. Choose Start to start the test.

Test results appear in the Loopback Status field at the bottom of the Diagnostics dialog box.


9. Choose Close.


10. After running the loopback test, reset the logical port’s Admin Status field to Up.

Far-End Loopback Tests for DS0 Channels


• “Modules Supported By DS0 Far-End Loopback Tests” on page 5-51

• “Logical Port Restrictions” on page 5-52

• “About DS0 Far-End Loopback Tests” on page 5-52

• “Running a DS0 Far-End Loopback Test” on page 5-53

• “Test Pattern Generation” on page 5-55

Modules Supported By DS0 Far-End Loopback Tests

The DS0 far end loopback test is available for:

• Channelized T1 modules

• 4-Port Channelized DS3 FR/IP modules

• 6-Port Channelized DS3/1/0 FR modules

• 4-Port DSX modules

• 32-Port Channelized T1/E1 FR/IP modules in the T1 mode.

Table 5-13. DS0 Channel Selection Buttons

Button Function

Select All Selects all channels.

De-select All Deselects all channels.

Note – The loopback state is not stored in PRAM. If you reboot the module, the DS0 returns to a normal state.




The DS0 far-end loopback test is not available for the 60-Port Channelized T1/E1 Circuit Emulation Module.

Logical Port Restrictions

You can activate a DS0 far-end loopback test from a logical port only if that logical port has only one DS0 channel assigned to it.

About DS0 Far-End Loopback Tests

The DS0 far-end loopback option enables you to test the transmission path of a logical port by looping back traffic in one or both directions. Use the DS0 far-end loopback option to specify that data from a switch should be looped from the switch to the OCU, CSU, or DSU and back to the originating switch. Figure 5-26 illustrates a DS0 far-end loopback that occurs at the OCU.

Figure 5-26. DS0 Far-End Loopback

In a far-end loopback, up to three midspan repeaters may be used to boost the signal between the OCU and the CSU/DSU. Figure 5-27 illustrates the use of midspan repeaters in a far-end loopback.

Figure 5-27. Far-End Loopback Using Midspan Repeaters

Far-end loopback takes place at the OCU, CSU, or DSU.

Test pattern generation originates at the B-STDX.

B-STDX24 DS0s

OCU CSU/DSU

B-STDX

OCU CSU/DSUM M M

M indicates midspan repeater use.




Running a DS0 Far-End Loopback Test

To run a DS0 far-end loopback test:


2. Display the module or subcard that holds the logical port to which the DS0 is assigned (see “Displaying Modules and Subcards” on page 2-54).




Figure 5-28. Diagnostics Dialog Box (DS0 Far End)

5. Choose DS0 Far End from the Type of Test field.

6. Select the DS0 channel that is assigned to the logical port.

A Y appears in the DS0 channel.

7. Select the configure test fields described in Table 5-14.

Note – If the logical port resides on a 32-Port Channelized T1/E1 module, make sure the module is configured in T1 operation mode.




8. Choose Activate Loopback to activate a DS0 loopback.

9. Choose Start to begin the test pattern generation from the switch associated with the selected logical port.

The system then displays the DS0 far-end loopback statistics. Table 5-15 describes the DS0 far-end loopback statistics.

Table 5-14. Diagnostics Dialog Box Configure Test Fields

Field Description

Far End Loopback Type From the pull-down list, select one of the following loopback test types:

OCU — Specifies an Office Channel Unit (OCU) loopback type that interfaces to the 56/64 Kilobytes per second span.

CSU — Specifies that the DS0 loopback should loop back the CSU at the customer premise; however, this loopback has the capability to disable any intermediate loopbacks and “punch through” the midspan repeaters and/or smartjacks that are used to boost the signal.

DSU — Specifies that the loopback starts at the DSU device that is closest to the customer equipment (possibly a single CSU/DSU device).

Mid Span Repeaters This function applies to CSU loopbacks only. From the pull-down list, specify the number of mid span repeaters in your network configuration. Select a value of 1, 2, or 3 to specify the number of midspan repeaters that your configuration uses.

If you are not sure of the number of midspan repeaters that your system uses, and you know that there are three or less, select a value of 3. Selecting 3 will not affect the loopback if you only have one or two midspan repeaters. However, the loopback will not provide valid data if you have more than three repeaters in your configuration.

If you select a value for this field, the system will “punch-through” and disable the loopback at intermediate midspan repeaters in the configuration.




10. You can optionally choose Insert Error to insert a bit error into the test pattern. The purpose of the Insert Error button is to validate the activation of a loopback test or to verify that a connection to remote equipment is operating successfully.

11. Choose Stop to end the test pattern generation.

12. Choose Deactivate Loopback to return to a normal state.

13. Choose Close.


14. When you are finished running the test, reset the logical port’s Admin Status field to Up.

Test Pattern Generation

The Start button on the Perform Foreground Diagnostic Test dialog box enables you to generate and receive a test traffic pattern. The test pattern for a DS0 loopback is 2047.

You can start a test traffic pattern as part of a DS0 far-end loopback test or by using external equipment to generate and receive the test pattern. If you are not performing a loopback test but are using external equipment for the test, choose the Start button to generate test traffic on any selected set of consecutive DS0 channels. You can also receive the test pattern on the same set of consecutive DS0 channels.

Table 5-15. Diagnostics Dialog Box Results Fields

Field Description

Bit Error Count The total number of accumulated bit errors that are received while running the loopback test.

Errored Seconds The number of seconds during the loopback test that errors occur. The system counts one or more bit errors in any one second increment as an errored second.

Test Pattern Sync Status Indicates any loss of pattern synchronization that occurs during the test.

Error Free Seconds The number of seconds during testing in which no bit errors occur.

Note – The loopback state is not stored in PRAM. If you reboot the module, the DS0 returns to a normal state. However, the end device (OCU, DSU, or CSU) remains in a loopback state.




Layer 2 Tunnel OAM Loopback Tests

To run OAM loopback tests on a Layer 2 tunnel:




4. Right click on the desired tunnel and click OAM on the popup menu. The Layer 2 Tunnel OAM dialog box (Figure 5-29) is displayed.

Figure 5-29. Layer 2 Tunnel OAM

The fields in the Layer 2 Tunnel OAM dialog box are shown in Figure 5-16.

Table 5-16. Layer 2 Tunnel OAM

Field Description

Name Name of tunnel.

Loopback Source Source of loopback signal.

Loopback Direction Send OAM cells Across Partner Network.

Loopback Type Send signal across the network to circuit endpoint.

Number of OAM Cells To Send

Specify number of OAM cells to send. Initially send a small number, for example 10.

QoS Class QoS Class options are:

• CBR

• VBR (Real Time)

• VBR (Non Real Time)

• UBR


Running BERTs


Running BERTs

Bit Error Rate Tests (BERTs) generate and monitor test patterns and measure the quality of data transmission for physical ports, channels, and logical ports. This section includes:

• “E1/T1 Physical Port BERTs For 60-Port Channelized T1/E1 Circuit Emulation Modules” on page 5-57

• “DS3 Physical Port BERTs For 8-Port Subrate DS3 FR/IP Modules” on page 5-63

• “DS1 Channel BERTs for Channelized DS3 Modules” on page 5-70

• “E1 Channel BERTs for 1-Port Channelized STM-1/E1 IMA and IMA Enhanced Modules” on page 5-73

• “DS0 BERTs for Channelized T1/E1 and DS3/1/0 FR/IP Modules” on page 5-77

• “Logical Port BERTs For 60-Port Channelized T1/E1 Circuit Emulation Modules” on page 5-82

• “Troubleshooting BERT Failures” on page 5-87

E1/T1 Physical Port BERTs For 60-Port Channelized T1/E1 Circuit Emulation Modules


• “About Physical Port BERTs For 60-Port Channelized T1/E1 Circuit Emulation Modules” on page 5-57

• “BERT Patterns Available” on page 5-58

• “Running a BERT for a Physical Port on a 60-Port Channelized T1/E1 Circuit Emulation Module” on page 5-59

About Physical Port BERTs For 60-Port Channelized T1/E1

Response Time (msec) Lowest, average, and Highest response time in milliseconds.

Responses The number of responses received and the number of responses that timed out.

Table 5-16. Layer 2 Tunnel OAM

Field Description



Testing Modules, Ports, and ChannelsRunning BERTs

Circuit Emulation Modules

BERTs generate and monitor test patterns and measure the quality of data transmission on a 60-Port Channelized T1/E1 Circuit Emulation Module physical port. The generation and monitoring functions are independent and can be run separately or together. The errors in the pattern of transmitted bits are counted to determine the Bit Error Rate (BER).

BERTs automatically detect any repetitive pattern of specified length (rather than looking for the selected pattern). You should compare the pattern that you select to the pattern automatically detected in the BERT.

You use the BERT in conjunction with the loopback test to qualify new physical port services or debug problems with existing services. You can insert bit errors (by choosing the Insert Error button) into the defined physical port data stream when you are performing a loopback test by inserting a single bit error.

BERT Patterns Available

The BERT patterns that are available depend on whether the module’s Operation Mode is set to E1 or T1 (see “Viewing IOM and BIO Attributes” on page 2-63), and whether the physical port Service Type is set to Unstructured CE or Structured CE (see “Viewing IOM and BIO Physical Port Attributes” on page 2-76).

Table 5-17 describes the types of BERT patterns that you can generate and receive for E1 Structured and Unstructured and T1 Structured physical ports on the 60-Port Channelized T1/E1 Circuit Emulation Module.

Table 5-18 describes the types of BERT patterns that you can generate and receive for a T1 Unstructured physical port on the 60-Port Channelized T1/E1 Circuit Emulation Module.

Table 5-17. Physical Port (E1 Structured and Unstructured & T1 Structured)BERT Patterns

BERT Pattern Description Detected Pattern in Hexadecimal

All Zeros Generates and receives data as all zeros. 00000000

All Ones Generates and receives data as all ones. 11111111

One Zero Generates and expects data to alternate between 1 and 0.

10101010, 01010101

One One Zero Zero Generates and expects data to alternate between two 1s and two 0s.

11001100, 00110011

One of Eight Generates and receives data in which each successive group of eight bits contains a single bit (in any position) that is set to 1.

For example, 00000040 (equal to a binary value of 01000000)


Running BERTs


Running a BERT for a Physical Port on a 60-Port ChannelizedT1/E1 Circuit Emulation Module

To run a BERT for a physical port on a 60-Port Channelized T1/E1 Circuit Emulation Module:


Three Of Twenty Four Generates and receives data in which each successive group of 24 bits contains three bits (in any position) that are set to 1.

For example, 0000000D (equal to a binary value of 000000000000000000001101)

QRSS (2^20-1) Standard quasi-random pattern with bit stuffing. ITU-T O.151 pseudo-random pattern; QRSS bit equals 1.

Random pattern is displayed.

1 Byte User Pattern Repeated user-defined 1-byte (8-bit) pattern. 11

2 Byte User Pattern Repeated user-defined 2-byte (16-bit) pattern. 2F2F

3 Byte User Pattern Repeated user-defined 3-byte (24-bit) pattern. 3A4B5C3A4B5C

2^15-1 ITU-T O.151 pseudo-random pattern. Random pattern is displayed.


Table 5-17. Physical Port (E1 Structured and Unstructured & T1 Structured)BERT Patterns (Continued)


Table 5-18. Physical Port (T1 Unstructured) BERT Patterns





2^7-1 (XOR) ITU-T O.151 pseudo-random pattern. Random pattern is displayed.

2^7-1 (XNOR) ITU-T O.151 pseudo-random pattern. Random pattern is displayed.






2. Display the physical ports on the module (see “Displaying the Physical Ports on a Module” on page 2-75).




4. Choose BERT from the Type of Test field.

5. Complete the Configure Test fields as described in Table 5-19.

Table 5-19. PPort Diagnostics Dialog Box Configure Test Fields

Field Description

BERT Pattern From the pull-down list, select the BERT pattern for the test. The default test pattern is All Zeros.

Table 5-17 describes the types of BERT patterns that you can generate and receive for E1 Structured and Unstructured and T1 Structured physical ports.

Table 5-18 describes the types of BERT patterns that you can generate and receive for a T1 Unstructured physical ports.


Running BERTs



Table 5-20 describes the BERT results.

BERT Error Rate From the pull-down list, select one of the following options to set the BERT error rate:

Single – Select this option to inject a single bit error while the BERT is running.

One Per Thousand – Select this option to inject errors continuously every one thousand bits.

One Per Million – Select this option to inject errors continuously every one million bits.

Note: To inject continuous errors, you must select One Per Thousand or One Per Million before starting the BERT.

BERT Polarity Select the polarity of the Pseudo Random Binary Sequence (PRBS). Options are: Normal or Inverse. The default is Normal.

Table 5-20. PPort Diagnostics Dialog Box BERT Results Fields (T1/E1)


Pattern Detected The BERT pattern detected.

BERT Mode Not Applicable.

BERT Error Rate Select one of the following options to set the BERT error rate:

None/Single – Select this option to inject a single bit error while the BERT is running.



Note: To inject continuous errors, you must select One per Thousand or One per Million before starting the BERT.

BERT Polarity Select the polarity of the Pseudo Random Binary Sequence (PRBS). Options are: Normal or Inverse. The default is Normal.

Table 5-19. PPort Diagnostics Dialog Box Configure Test Fields (Continued)

Field Description




7. Choose Insert Error to inject a bit error and detect a loss of pattern synchronization.

Test results appear in the BERT Bit Count and BERT Error Count fields. Compare the displayed BERT Error Count to the expected count.

Note – When you choose the Insert Error button, the Clear Counter button becomes active. Choosing Clear Counter will clear the BERT Bit Count and BERT Error Count fields, return the values to zero, and re-start the BERT testing.


9. Choose Close.


BERT Status The current BERT state (Unavailable, Out of Frame, Available, or In-Frame).

BERT Bit Count The number of received bits.

Errored Seconds A count of 1-second intervals with one or more BPVs, one or more EXZs, or one or more LOS (loss of signal) defects. For a B8ZS-coded signal, BPVs that are part of the zero substitution code, as defined in ANSI T1.102, are excluded.

Pattern Sync Loss Seconds

The number of seconds the patterns is out of sync after the initial synchronization.

Available Sec. The number of seconds the interface is available after the initial pattern synchronization.

Avg. Bit Error Rate The average of all of the bit error rates during the BERT (starting after initial pattern synchronization), regardless of whether the calculation is for available or unavailable seconds. The BERT bit error rate is the ratio of bit errors to bits received during a one-second interval.

BERT Error Count Displays the number of received bit errors.


A count of 1-second intervals with 1544 or more BPVs plus EXZs, or one or more LOS defects. For a B8ZS-coded signal, BPVs that are part of the zero substitution code, as defined in ANSI T1.102, are excluded.

Error Free Seconds(%) The percentage of error free seconds during the BERT test.

Unavailable Sec The number of seconds the interface is unavailable after the initial pattern synchronization.

Table 5-20. PPort Diagnostics Dialog Box BERT Results Fields (T1/E1) (Continued)



Running BERTs


10. After running the test, reset the physical port’s Admin Status field to Up and set the physical port’s Transmit Clock Source field back to its original value.

DS3 Physical Port BERTs For 8-Port Subrate DS3 FR/IP Modules


• “About Physical Port BERT For 8-Port Subrate DS3 FR/IP Modules” on page 5-63


• “Running a BERT for a Physical Port on an 8-Port Subrate DS3 FR/IP Module” on page 5-64

About Physical Port BERT For 8-Port Subrate DS3 FR/IP Modules

BERTs generate and monitor test patterns and measures the quality of data transmission on an 8-Port Subrate DS3 FR/IP physical port. The generation and monitoring functions are independent and can be run separately or together. The errors in the pattern of transmitted bits are counted to determine the Bit Error Rate.




Table 5-21 lists and describes the types of BERT patterns you can generate and receive from the physical port.

Table 5-21. Physical Port (Subrate DS3) Bert Patterns

BERT Test Pattern Description Detected Pattern

All Zeros Generates and expects data in zeros. 0

All Ones Generates and expects data in ones. FF

One Zero Alternates ones and zeros. AA,55

One One Zero Zero Alternates between two (1s) and two (0s).

66,99,CC,33

One of Eight Each byte is “10000000”, “00100000”. 1,2,4,8,10,20,40,80




Running a BERT for a Physical Port on an 8-Port Subrate DS3FR/IP Module

To run a BERT for a physical port on an 8-Port Subrate DS3 FR/IP Module:








Three of Twenty four Generates and expects the hexadecimal pattern.

11,111,1110,1000,8880,88...

QRSS Standard Quasi Random pattern with bit stuffing.

(No random pattern displayed.)

1 Byte User Pattern Repeated user defined byte pattern. 11

2 Byte User Pattern Repeated user-defined 2-byte (16-bit) pattern.

2 Byte User Pattern

Table 5-21. Physical Port (Subrate DS3) Bert Patterns (Continued)



Running BERTs





8. Choose Close.



Table 5-22. PPort Diagnostics Dialog Box Configure Test Fields (DS3)



See Table 5-21 on page 5-63 for a description of the available BERT patterns.






BERT User Pattern Bytes (HEX)

Enter any value of the 1-byte or 2-byte user pattern. This field is active only if the BERT Pattern field is set to 1 Byte User Pattern or 2 Byte User Pattern.

Table 5-23. PPort Diagnostics Dialog Box BERT Results Fields (DS3)

Field Displays...



BERT Status The BERT state (Unavailable, Out of Frame, Available, or In-Frame).

BERT Error Count The number of received bit errors.




Physical Port BERTs for DS3 and POS Universal I/O Modules


• “About Physical Port BERTs” on page 5-66

• “BERT Patterns Available for DS3 and POS Universal I/O Modules” on page 5-66

• “Running a BERT for a Physical Port on a DS3 or POS Universal I/O Module” on page 5-67

About Physical Port BERTs

BERTs generate and monitor test patterns and measures the quality of data transmission on a module’s physical port. The generation and monitoring functions are independent and can be run separately or together. The errors in the pattern of transmitted bits are counted to determine the Bit Error Rate.

BERTs automatically detect any repetitive pattern of specified length (rather than looking for the selected pattern). You should compare the pattern that you select to the pattern automatically detected in the BERT test.


BERT Patterns Available for DS3 and POS Universal I/O Modules

Table 5-21 lists and describes the types of BERT patterns you can generate and receive from the physical port of DS3 and POS PPorts.

Table 5-24. Bert Test Patterns for Universal Modules Physical Ports





One One Zero Zero Alternates between two (1s) and two (0s).

66,99,CC,33


Three of Twenty Four Generates and expects the hexadecimal pattern.

11,111,1110,1000,8880,88...


Running BERTs


Running a BERT for a Physical Port on a DS3 or POS Universal I/O Module

To run a BERT for a physical port on a Universal I/O Module:





QRSS (2 ^ 20 - 1) Standard Quasi Random pattern with bit stuffing.

(no random pattern displayed)



2 Byte User Pattern


3 Byte User Pattern

2 ^ 15 - 1 ITU-T O.151 pseudo-random pattern. Random pattern is displayed

2 ^ 20 - 1 ITU-T O.151 pseudo-random pattern. Random pattern is displayed

Table 5-24. Bert Test Patterns for Universal Modules Physical Ports (Continued)





Figure 5-32. BERT PPort Dialog Box (Universal DS3 or POS IOM)

4. Select BERT from the Type of Test field.

5. Configure the test parameters as described in Table 5-25.

Table 5-25. Universal DS3 or POS IOM BERT Test Parameters

Field Description




Single – Select this option to inject a single bit error while the BERT test is running.





Running BERTs





8. Choose Close.



Table 5-26. DS3 BERT Results

Field Displays...

Pattern Detected BERT pattern detected.

BERT Bit Count Number of received bits.

Errored Seconds The number of seconds during the BERT test that errors occur. The system counts one or more bit errors in any one second increment as an errored second.


The number of seconds the interface is available after the initial pattern synchronization.

Available Seconds The number of seconds the interface is available after the initial pattern synchronization.

Avg. Bit Error Rate Displays the average of all of the bit error rates during the BERT test (starting after initial pattern synchronization), regardless of whether the calculation is for available or unavailable seconds. The BERT bit error rate is the ratio of bit errors to bits received during a one-second interval.

BERT Status BERT state (Unavailable, Out of Frame, Available, or In-Frame).

BERT Error Count Number of received bit errors.



Error Free Seconds(%)

The percentage of error free seconds during the BERT test.

Unavailable Seconds The number of seconds the interface is unavailable after the ini-tial pattern synchronization.




DS1 Channel BERTs for Channelized DS3 Modules


• “About DS1 Channel BERTs” on page 5-70


• “Running a BERT for a DS1 Channel” on page 5-71

About DS1 Channel BERTs

BERTs generate and monitor test patterns and measures the quality of data transmission on any DS1 channel on a Channelized DS3 module. (The DS channel BERT is not supported on DS3/1/0 modules.) The generation and monitoring functions are independent and can be invoked separately or together. The errors in the pattern of transmitted bits are counted to determine the Bit Error Rate.

BERTs automatically detect any repetitive pattern of specified length (rather than looking for the selected pattern). You should compare the pattern that you select to the pattern automatically detected in the BERT test.

You use the BERT test in conjunction with the loopback test to qualify new T1 services or debug problems with existing services. You can insert bit errors (by choosing the Insert Error button) into the DS1 data stream when you are performing a loopback test by inserting a single or continuous bit error.


Table 5-27 lists and describes the types of BERT patterns you can generate and receive from the DS1 channel.

Table 5-27. DS1 Channel BERT Patterns

BERT Pattern Description Detected Pattern




One One Zero Zero Alternates between two ones (1s) and two zeros (0s).

66,99,CC,33


Three of Twenty Four Generates and expects the hexadecimal pattern.

11,111,1110,1000,8880,88...

QRSS (2^20-1) Standard Quasi Random pattern with bit stuffing.

(No random pattern displayed)


Running BERTs


Running a BERT for a DS1 Channel

To run a BERT for a DS1 channel:








2 Byte User Pattern


3 Byte User Pattern

2^15-1 Standard pattern with bit stuffing. (No random pattern displayed.)

2^23-1 Standard pattern with bit stuffing. (No random pattern displayed.)

Table 5-27. DS1 Channel BERT Patterns (Continued)

BERT Pattern Description Detected Pattern








Table 5-28. Channel Diagnostics Dialog Box Configure Test Fields (DS1)





Single – Select this option to inject a single bit error while the BERT test is running.




BERT User Pattern Enter any value of the 1-byte or 2-byte user pattern. This field is active only if the BERT Pattern field is set to 1 Byte User Pattern or 2 Byte User Pattern.

Table 5-29. Channel diagnostics Dialog Box BERT Results Fields (DS1)

Field Displays...






Running BERTs



Test results appear in the BERT Bit Count and BERT Error Count fields. Compare the displayed BERT Error Count to the expected count. For example, the BERT Error count should increase by one each time you choose Insert Error if you are using the QRSS test pattern.



9. Choose Close.



E1 Channel BERTs for 1-Port Channelized STM-1/E1 IMA and IMA Enhanced Modules


• “About E1 Channel BERTs” on page 5-73


• “Running a BERT for an E1 Channel” on page 5-74

About E1 Channel BERTs

BERTs generate and monitor test patterns and measure the quality of data transmission on an E1 channel on the 1-Port Channelized STM-1/E1 IMA IOM. The generation and monitoring functions are independent, and can be run separately or together. The errors in the pattern of transmitted bits are counted to determine the bit error rate (BERT).

You use the BERT in conjunction with the Near-end Line Loopback test to qualify new services on an E1 channel or debug problems with existing services.



Table 5-30 describes the types of BERT patterns that you can generate and receive from an E1 channel on the 1-Port Channelized STM-1/E1 IMA IOM.




Running a BERT for an E1 Channel

To run a BERT for an E1 channel:

1. Set the Admin Status field of the E1 channel to Down and the Transmit Clock Source field to Internal (see “Changing a Channel’s Admin Status,” on page 5-10) if you have not already done so.

2. Display the E1 channels (see “Displaying E1 Channels” on page 2-91) for a physical port.



Table 5-30. E1 Channel BERT Patterns


All Zeros Generates and receives data as all zeros. This is the default test pattern.

00000000

All Ones Generates and receives data as all ones. 11111111


10101010, 01010101


11001100, 00110011



Three Of Twenty Four Generates and receives data in which each successive group of 24 bits contains three bits (in any position) that are set to 1.


QRSS (2^20-1) Standard quasi-random pattern with bit stuffing. ITU-T O.151 and ITU-T O.152 pseudo-random pattern; QRSS bit equals 1.


1 Byte User Pattern Repeated user-defined byte (8-bit) pattern. 11

2 Byte User Pattern Repeated user-defined 2-byte (16-bit) pattern. 2F2F

3 Byte User Pattern Repeated user-defined 3-byte (24-bit) pattern. 3A4B5C3A4B5C

2 ^15-1 ITU-T O.151 and ITU-T O.152 pseudo-random pattern.


2^23-1 ITU-T O.151 and ITU-T O.152 pseudo-random pattern.



Running BERTs





Table 5-31. Channel Diagnostics Dialog Box Configure Test Fields (E1)




BERT User Pattern Bytes (HEX)

Enter any value of the 1-byte, 2-byte, or 3-byte user pattern. This field is active only if the BERT Pattern field is set to 1 Byte User Pattern, 2 Byte User Pattern, or 3 Byte User Pattern.












8. Choose Close.



Table 5-32. Channel Diagnostics Dialog Box BERT Results Fields (E1)

Field/Button Displays...



Note: The BERT Bit Count stops counting at 4 billion.

BERT Status The current BERT state: Unavailable, Out of Frame, Available, or In-Frame.



Running BERTs


DS0 BERTs for Channelized T1/E1 and DS3/1/0 FR/IP Modules


• “About DS0 Channel BERTs” on page 5-77


• “Running a BERT for a DS0 Channel” on page 5-78

About DS0 Channel BERTs

BERTs generate and monitor test patterns and measures the quality of data transmission on any logical port associated with DS0 channels on Channelized T1/E1 and DS3/1/0 FR/IP modules. The generation and monitoring functions are independent, and can be run separately or together. The errors in the pattern of transmitted bits are counted to determine the Bit Error Rate.


You use the BERT in conjunction with the loopback test to qualify new logical port services or debug problems with existing services. You can insert bit errors(by choosing the Insert Error button) into the defined logical port data stream when you are performing a loopback test by inserting a single or continuous bit error.


Table 5-33 lists and describes the types of BERT patterns you can generate and receive from the DS0 channels.



All Zeros Generates and receives data as all zeros.

00000000

All Ones Generates and receives data as all ones.

11111111


10101010, 01010101


11001100, 00110011




Running a BERT for a DS0 Channel

To run a BERT for a DS0 channel that is associated with a logical port:








Three Of Twenty Four)

Generates and receives data in which each successive group of 24 bits contains three bits (in any position) that are set to 1.


QRSS (2^20-1) Standard Quasi Random pattern with bit stuffing. ITU-T O.151 pseudo-random pattern; QRSS bit equals 1.


1 Byte User Pattern Repeated user-defined1- byte (8-bit) pattern.

11


2F2F


3A4B5C3A4B5C

2 ^15-1(DS3 CE LPorts only)

ITU-T O.151 pseudo-random pattern.


2^23-1(DS3 CE LPorts only)

ITU-T O.151 pseudo-random pattern.





Running BERTs


Figure 5-35. Diagnostics Dialog Box (logical port)



Table 5-34. DS0 BERT Test Parameters

Field Action

Allocated Channels Select the DS0 channels on which you want to run the test. The selected channels are marked with a Y.

If you are using the DS0 BERT in conjunction with a DS0 far-end loopback test, select only one DS0 channel.

You cannot select a DS0 channel that is not allocated to the logical port (the channels that are marked with an X).

BERT Test Choose one of the following buttons for the mode of the BERT:

Full

Partial






BERT Pattern From the pull-down list, select the BERT pattern for the test. The default test pattern is All Zeros. If you selected Partial for the BERT Test, fewer BERT patterns will be available.


BERT User Pattern Byte (HEX)

Enter any value of the 1-byte, 2-byte, 3-byte, or 4-byte user pattern. This field is active only if the BERT Pattern field is set to 1 Byte User Pattern, 2 Byte User Pattern, 3 Byte User Pattern, or 4 Byte User Pattern.

BERT Error Rate

(6-port Channelized DS3 Frame Relay Module only)

From the pull-down list, select one of the following options to set the BERT error rate:


One Per Ten – Select this option to inject errors continuously every ten bits.

One Per Hundred – Select this option to inject errors continuously every one hundred bits.


One Per Ten Thousand – Select this option to inject errors continuously every ten thousand bits.

One Per Hundred Thousand – Select this option to inject errors continuously every hundred thousand bits.


One Per Million – Select this option to inject errors continuously every ten million bits.

Note: To inject continuous errors, you must select one of the multiple BERT error rates before starting the BERT.

Table 5-35. Diagnostics Dialog Box BERT Results Field (DS0)

Field Displays...



Table 5-34. DS0 BERT Test Parameters (Continued)

Field Action


Running BERTs






Note – The following fields apply to the 6-port Channelized DS3 Frame Relay module only.

BERT Mode The current mode of the BERT for this channel, which depends on how many BERT tests are running. Values can be:

BERT Full Available

BERT Partial Available

None





Avg Bit Error Rate Displays the average of all of the bit error rates during the BERT test (starting after initial pattern synchronization), regardless of whether the calculation is for available or unavailable seconds. The BERT bit error rate is the ratio of bit errors to bits received during a one-second interval.



Error Free Seconds(%) The percentage of error free seconds during the BERT.

Unavailable Seconds The number of seconds the interface is unavailable after the initial pattern synchronization.

Table 5-35. Diagnostics Dialog Box BERT Results Field (DS0) (Continued)

Field Displays...






10. Choose Close.


11. After running the test, reset the logical port’s Admin Status field to Up.

Logical Port BERTs For 60-Port Channelized T1/E1 CircuitEmulation Modules


• “About Logical Port BERTs For 60-Port Channelized T1/E1 Circuit Emulation Modules” on page 5-82


• “Running a BERT for a 60-Port Channelized T1/E1 Circuit Emulation Module Logical Port” on page 5-83

About Logical Port BERTs For 60-Port Channelized T1/E1Circuit Emulation Modules

BERTs generate and monitor test patterns and measure the quality of data transmission on any logical port associated with 60-Port Channelized T1/E1 Circuit Emulation Modules. The generation and monitoring functions are independent, and can be run separately or together. The errors in the pattern of transmitted bits are counted to determine the Bit Error Rate.


You use the BERT test in conjunction with the loopback test to qualify new logical port services or debug problems with existing services. You can insert bit errors(by choosing the Insert Error button) into the defined logical port data stream when you are performing a loopback test by inserting a single bit error.


Table 5-36 describes the types of BERT patterns that you can generate and receive for a logical port on the 60-Port Channelized T1/E1 Circuit Emulation Module.


Running BERTs


Running a BERT for a 60-Port Channelized T1/E1 CircuitEmulation Module Logical Port

To run a BERT for a 60-Port Channelized T1/E1 Circuit Emulation Module logical port:


2. Display the module that holds the logical port (see “Displaying the Modules for a Switch” on page 2-54).




Table 5-36. Logical Port BERT Patterns





2^7-1 (XOR) ITU-T O.151 pseudo-random pattern. Random pattern is displayed.

2^7-1 (XNOR) ITU-T O.151 pseudo-random pattern. Random pattern is displayed.






Figure 5-36. Diagnostics Dialog Box (Logical Port)



Table 5-37. Diagnostics Dialog Box Configure Test Fields (Logical Port)










Running BERTs




BERT Polarity Select the polarity of the Pseudo Random Binary Sequence (PRBS), which can be Normal or Inverse. The default is Normal.

Table 5-38. Diagnostics Dialog Box BERT Results Fields (Logical Port)

Field Description

Pattern Detected Displays the BERT pattern detected.

BERT Mode Not Applicable.

BERT Error Rate Select one of the following options to set the BERT error rate:

None/Single – Select this option to inject a single bit error while the BERT test is running.

One per Thousand – Select this option to inject errors continuously every one thousand bits.

One per Million – Select this option to inject errors continuously every one million bits.


BERT Polarity Select the polarity of the Pseudo Random Binary Sequence (PRBS) which can be normal or inverse. The default is normal.

BERT Status Indicates the current BERT state (Unavailable, Out of Frame, Available, or In-Frame).

BERT Bit Count Displays the number of received bits.





Table 5-37. Diagnostics Dialog Box Configure Test Fields (Logical Port) (Continued)









10. Choose Close.


11. After running the test, reset the logical port’s Admin Status field to Up.

Avg Bit Error Rate

Displays the average of all of the bit error rates during the BERT test (starting after initial pattern synchronization), regardless of whether the calculation is for available or unavailable seconds. The BERT bit error rate is the ratio of bit errors to bits received during a one-second interval.

BERT Error Count

Displays the number of received bit errors.



Error Free Seconds(%)

The percentage of error free seconds during the BERT.

Unavailable Seconds

The number of seconds the interface is unavailable after the ini-tial pattern synchronization.

Table 5-38. Diagnostics Dialog Box BERT Results Fields (Logical Port) (Continued)

Field Description


Running BERTs


Troubleshooting BERT Failures

Table 5-39 describes failure indicators that may appear during BERT testing and recommendations for correcting the failure.

Table 5-39. Failure Indicators and Recommendations

Indicator Recommendations

BERT Status field displays BERT Out of Frame after you start the test.

• Check the cable connection.

• Check the test equipment mode; it should be set to “pass-through” mode for simplicity.

• Check the downlink-to-uplink cable connection.

• Determine whether the cable length is appropriately matched to the line build out (LBO).

• Verify that the port LED is not red. If it is red, the commands for initializing the Framer chip might not have been received.

• Switch to active downlink if uplink redundancy is in effect.

BERT Status field displays BERT In-Frame, but the system does not update the Bert Error Count field after error injection.

• Check the test equipment mode. If it is not in “pass-through” mode, the generation of errors stops.






6

Logical Port Attributes

This chapter describes how to view the configured attributes for logical ports. Subsequent chapters provide service-specific information for monitoring logical ports.

This chapter includes:

• “Displaying Logical Ports” on page 6-1

• “Categories of Logical Port Attributes” on page 6-7

• “Viewing Logical Port Attributes” on page 6-10

• “Viewing Logical Port QoS Parameters” on page 6-10

• “Viewing Logical Port SVC Attributes” on page 6-15

• “Viewing Logical Port SVC QoS Parameters” on page 6-15

• “Viewing Logical Port SVC Traffic Descriptor Limits” on page 6-18

• “Viewing Logical Port SVC Signaling Tuning Parameters” on page 6-19

Displaying Logical Ports

This section describes different methods for displaying logical ports in the switch tab. This section includes:

• “Displaying the Logical Ports That Belong to a Physical Port or Subport” on page 6-2

• “Displaying the Logical Ports That Belong to a Switch, Module, or Subcard” on page 6-5

Restrictions

MLFR logical ports can only be displayed from the module level.



Logical Port AttributesDisplaying Logical Ports

Displaying the Logical Ports That Belong to a Physical Port or Subport

This section describes how to display logical ports that belong to a particular physical port or subport. This section includes:

• “Displaying the Logical Ports on an IOM/BIO Physical Port” on page 6-2

• “Displaying the Logical Ports on a GX 550 Subcard Physical Port” on page 6-3

• “Displaying the Logical Ports on a GX 550 OC48/OC48c Subcard Subport” on page 6-3

• “Displaying the Logical Ports on a Physical Port DS1 or E1 Channel” on page 6-4

• “Displaying the Logical Ports on a Physical Port IMA Group” on page 6-4

Displaying the Logical Ports on an IOM/BIO Physical Port

To display the logical ports that belong to a physical port on an Input/Output Module (IOM) or Base Input/Output (BIO) module:

1. In the switch tab (see “Displaying a Switch Tab in the Navigation Panel” on page 2-6), expand the switch (Figure 6-1).

Figure 6-1. Logical Ports on a Physical Port (IOM/BIO)


The modules that belong to the switch appear.



5. Expand the physical port that contains the logical ports.


Beta Draft ConfidentialLogical Port AttributesDisplaying Logical Ports


Displaying the Logical Ports on a GX 550 Subcard Physical Port

To display the logical ports that belong to a physical port on a GX 550 subcard:


Figure 6-2. Logical Ports on a Physical Port (GX 550 subcard)







7. Expand the physical port that contains the logical ports.


Displaying the Logical Ports on a GX 550 OC48/OC48c Subcard Subport

To display the logical ports that belong to a subport on a GX 550 OC48 or OC48c subcard:


Figure 6-3. Logical Ports on a Subport










7. Expand the physical port that contains the subport.

8. Expand the Subports class node.

9. Expand the subport that contains the logical ports.


Displaying the Logical Ports on a Physical Port DS1 or E1 Channel

To display the logical ports that belong to a physical port on a DS1 or E1 channel:


Figure 6-4. Logical Ports on a Physical Port (DS1 or E1Channel)



3. Expand the module that contains the physical port and DS1 or E1 channel.


5. Expand the physical port that contains the channel.

6. Expand the DS1 or E1 Channels class node.

7. Expand the channel that contains the logical ports.


Displaying the Logical Ports on a Physical Port IMA Group

To display the logical ports that belong to a physical port on an IMA group:


Beta Draft ConfidentialLogical Port AttributesDisplaying Logical Ports


Figure 6-5. Logical Ports on a Physical Port (IMA Group)







7. Expand the IMA group that contains the logical ports.


Displaying the Logical Ports That Belong to a Switch, Module, or Subcard

This section describes how to display logical ports that belong to a particular switch, module, or subcard. This section includes:

• “Displaying the Logical Ports That Belong to a Switch” on page 6-5

• “Displaying the Logical Ports That Belong to a Module” on page 6-6

Displaying the Logical Ports That Belong to a Switch

To display the logical ports that belong to a switch:


Figure 6-6. Logical Ports on a Switch





Displaying the Logical Ports That Belong to a Module

To display the logical ports that belong to a module, perform the following steps.


Figure 6-7. Logical Ports on a Module (IOM)



3. Expand the module that contains the logical ports.


5. The logical ports that belong to the module appear.

Beta Draft ConfidentialLogical Port Attributes

Categories of Logical Port Attributes



Logical port attributes vary, depending on the type of logical port you are monitoring. Table 6-1 lists the categories of logical port attributes that you can view, the service or logical port types to which the attributes apply, the dialog box and tab in which you view the attributes, and the procedure for viewing the attributes.

Table 6-1. Service-specific Logical Port Attributes

Attribute Category Service/LPort Type Supported

Dialog Box and Tab Procedure for Viewing Attributes

General All services and their logical port types.

View Logical Port — General

“Viewing Logical Port Attributes” on page 6-10

Administrative All services and their logical port types.

View Logical Port— Administrative


Congestion Control Frame Relay (all port types), Multilink Frame Relay Trunks, Direct Line Trunks, ATM Direct Trunks (B-STDX ports only), and SMDS (SSI-DTE and DXI/SNI ports).

View Logical Port — Congestion


CES CE logical ports on the 60-Port Channelized T1/E1 Circuit Emulation Module

View Logical Port — CES Parameters


Trap Control Frame Relay (all port types), Multilink Frame Relay Trunks, Frame Relay OPTimum PVC, Direct Line Trunks, ATM Direct Trunks (B-STDX ports only), SMDS (all port types), and Ethernet.

View Logical Port — Trap Control


ATM ATM View Logical Port — ATM


FCP ATM View Logical Port — FCP


Frame Relay OAM Frame Relay UNI/NNI and MLFR UNI/NNI on the 6-Port Channelized DS3/1/0 Frame Relay Module

View Logical Port — FRF.19


ILMI/OAM ATM View Logical Port — ILMI/OAM




Logical Port AttributesCategories of Logical Port Attributes

Link Management Frame Relay View Logical Port — Link Management


MLFR Frame Relay ML Member, and UNI/NNI for 6-Port Channelized DS3/1/0 Frame Relay Module

View Logical Port — MLFR LPort Bind


MLFR MLFR UNI/NNI on 6-Port Channelized DS3/1/0 Frame Relay Module

View Logical Port — MLFR Configuration


MLFR MLFR UNI/NNI and MLFR Trunk Bundle

View Logical Port — MLFR Member Bind


AINI AINI Lport View Logical Port — AINI


PNNI ATM NNI View Logical Port — PNNI


Point-to-Point Point-to-Point View Logical Port — Point-to-Point


Priority Frame Frame Relay View Logical Port — Priority Frame


QoS ATM and Frame Relay View Logical QoS Parameters

“Viewing Logical Port QoS Parameters” on page 6-10

VPI Range ATM OPTimum Cell Trunk View Logical Port — VPI Range


VP Shaping Rate ATM OPTimum Cell Trunk View Logical Port — Tunnel VP Shaping Rate


Traffic Descriptors ATM UNI View Logical Port — TDs


Traffic Descriptors ATM Direct Line and OPTimum Cell Trunk

View Logical Port — ILMI/OAM


Traffic Descriptors ATM NNI View Logical Port — PNNI and ILMI/OAM


Table 6-1. Service-specific Logical Port Attributes (Continued)






Discard/Congestion Mapping

The following logical ports when associated with ATM IWU IOMs and ATM CS IOMs on B-STDX 9000 switches:

• ATM Direct Line Trunk

• ATM OPTimum Cell Trunk

• ATM OPTimum Frame Trunk

View Logical Port — Discard/Priority


SVC General ATM Configure SVC — General ATM

“Viewing Logical Port SVC Attributes” on page 6-15

SVC General Frame Relay Configure SVC — General Frame Relay


SVC QoS ATM and Frame Relay View Logical QoS Parameters

“Viewing Logical Port SVC QoS Parameters” on page 6-15

SVC Signaling ATM Configure SVC — Signaling ATM


SVC Signaling Frame Relay Configure SVC — Signaling Frame Relay


SVC Address ATM Configure SVC — Address ATM


SVC Address Frame Relay Configure SVC — Address Frame Relay


SVC Connection ID ATM and Frame Relay Configure SVC — Connection ID


SVC CUG ATM

Frame Relay

Configure SVC — CUG


SVC TD Limits ATM and Frame Relay TD Limits “Viewing Logical Port SVC Traffic Descriptor Limits” on page 6-18

SVC Signaling Tuning

ATM and Frame Relay Tuning “Viewing Logical Port SVC Signaling Tuning Parameters” on page 6-19

Table 6-1. Service-specific Logical Port Attributes (Continued)





Logical Port AttributesViewing Logical Port Attributes

Viewing Logical Port Attributes

To view the configured attributes for a logical port:

1. Display the logical ports on the switch, module, subcard, or physical port (see “Displaying Logical Ports” on page 6-1).

2. Right-click on the logical port and select View from the popup menu.

The View Logical Port dialog box appears (Figure 6-8).

Figure 6-8. View Logical Port Dialog Box

3. Select the appropriate tab for the attributes you want to view. For a description of the tabs and fields that are available, see the ATM Services Configuration Guide for CBX 3500, CBX 500, GX 550, and B-STDX 9000, the Frame Relay Services Configuration Guide for CBX 3500, CBX 500, and B-STDX 9000, or the IP Services Configuration Guide for CBX 3500, CBX 500, and B-STDX 9000.


The View Logical Port dialog box closes.

Viewing Logical Port QoS Parameters

To view the configured QoS attributes for a logical port:


2. Right-click on the logical port and select QoS Statistics from the popup menu.




The View Logical QoS Parameters dialog box appears (Figure 6-9).

Table 6-2 describes the View Logical Port QoS (and SVC QoS) Parameters dialog box fields.

Figure 6-9. View Logical QoS Parameters Dialog Box



Logical Port AttributesViewing Logical Port QoS Parameters

Table 6-2. View Logical QoS Parameters Attributes

Field Displays...

Configured – The configured QoS values (CBR, VBR-RT, VBR-NRT, VFR-RT, VFR-NRT, ABR/UBR, UFR) for the logical port.

Bandwidth Allocation A value of Dynamic or Fixed for each service class.

Dynamic – Enables the bandwidth allocation to change dynamically according to bandwidth demands. Dynamic bandwidth allocation pools the remaining bandwidth for this logical port. This includes bandwidth that has not already been allocated to a specific queue or assigned to a connection.

Fixed – Specifies the percentage of bandwidth that is reserved for the service class. If the network requests a circuit that exceeds the fixed value, the circuit cannot be created. If all four service classes are set to Fixed, all four values should equal 100% bandwidth.

For Frame Relay, if the UFR service class is Fixed, that amount of service is guaranteed for the UFR queue if the VFR queues are not oversubscribed. Bandwidth is not actually allocated for UFR connections, so the port allows more connections into the UFR queue than it can service.

Note: For Frame Relay, if there are service classes set to Dynamic, any remaining bandwidth percentage is allocated to those service classes as needed. For example, if UFR is Fixed at 55%, and the two VFR classes are set to Dynamic, the remaining 45% of bandwidth is dynamically allocated between the two VFR service classes.

Fixed at % The percentage of bandwidth that is reserved for the service class if the Bandwidth Allocation is set to Fixed.

Routing Metric The routing metric configured for the logical port. Routing metrics allow the switch to select less congested paths and avoid congested paths when transferring data.

Note: For Frame Relay, routing metrics apply only if the port is configured as a UNI DCE or UNI DTE logical port.

Routing metric options are:

Cell/Frame Delay Variation – Measures the average variation in delay between one cell/frame and the next, measured in fractions of a second. When emulating a circuit, cell/frame delay variation measurements allow the network to determine if cells are arriving too fast or too slow.

End-to-End Delay – Measures the time (propagation and transmission delay) it takes a cell/frame to get from one end of a connection to the other. It is measured when the port initially comes up; it does not include queueing delays, so it does not affect port congestion.

Admin Cost – Measures the administrative cost associated with the logical port. The administrative cost is specified by the administrator, enabling you to adjust path selection manually.




Oversubscription (%) A minimum value of 100% to indicate the virtual bandwidth available for a service class. A value of 100% ensures that the port will deliver all user data for that service class without unanticipated delays or excessive cell loss. A value of 200% effectively doubles the virtual bandwidth available for that service class. However, if all network traffic attempts to use the network resources at precisely the same time (for example, during multiple file transfer sessions over the same trunk), some traffic may be delayed or dropped.

Note: The Oversubscription value for CBR (for ATM) and CFR (for Frame Relay) is always set at 100% and cannot be modified.

Outgoing Bandwidth (Reserved) – For each ATM or Frame Relay QoS class, this frame of the dialog box displays the egress values for allocated bandwidth and virtual available bandwidth. The bandwidth is expressed as both the actual bandwidth and the percentage of the total logical port bandwidth.

Constant Bit Rate(ATM only)

The allocated bandwidth and virtual bandwidth egress values assigned to the CBR QoS class. This class handles digital information, such as video and digitized voice, which must be represented by a continuous stream of bits. CBR traffic requires guaranteed throughput rates and service levels.

Constant Frame Rate(Frame Relay only)

The allocated bandwidth and virtual bandwidth egress values assigned to control traffic, which is not a QoS class that you can configure.

Variable (Bit/Frame) Rate (VBR/VFR) Real Time

The allocated bandwidth and virtual bandwidth egress values assigned to either the VBR-RT or VFR-RT QoS class. These classes are designed for packaging special delay-sensitive applications, such as packet video, that require low cell/frame delay variation between endpoints.

Variable (Bit/Frame) Rate (VBR/VFR) Non-Real Time

The allocated bandwidth and virtual bandwidth egress values assigned to either the VBR-NRT or VFR-NRT QoS class. These classes handle packaging for transfer of long, bursty data streams over a pre-established connection. These classes are also used for short, bursty data, such as LAN traffic. CPE protocols adjust for any delay or loss incurred through the use of VBR-NRT or VFR-NRT.

Available/Unspecified (Bit/Frame) Rate (ABR/UBR/UFR)

The allocated bandwidth and virtual bandwidth egress values assigned to the ABR/UBR or UFR QoS class. These classes are primarily used for LAN traffic. The CPE should compensate for any traffic delay or loss.

Total The total allocated egress bandwidth.

Incoming Bandwidth (Reserved) – For each ATM QoS class, this field of the dialog box displays the ingress values for allocated bandwidth and virtual available bandwidth (ingress values do not apply to Frame Relay logical ports). The bandwidth is expressed as both the actual bandwidth and the percentage of the total logical port bandwidth.

Note – Ingress values do not apply to direct trunk logical ports. Since each side of the trunk enforces its outgoing bandwidth allocation, the opposite side of the trunk does not have to enforce incoming bandwidth allocation.

Constant Bit Rate The allocated bandwidth and virtual bandwidth ingress values assigned to the CBR QoS class.

Table 6-2. View Logical QoS Parameters Attributes (Continued)

Field Displays...



Logical Port AttributesViewing Logical Port QoS Parameters


The View Logical QoS Parameters dialog box closes.

Variable Bit Rate (VBR) Real Time

The allocated bandwidth and virtual bandwidth ingress values assigned to the VBR-RT QoS class.

Variable Bit Rate (VBR) Non-Real Time

The allocated bandwidth and virtual bandwidth ingress values assigned to the VBR-NRT QoS class.

Available/Unspecified Bit Rate (ABR/UBR)

The allocated bandwidth and virtual bandwidth ingress values assigned to the ABR/UBR QoS class.

Total The total allocated ingress bandwidth.

Bandwidth Usage as per Lport Subscription Factor - This field of the dialog box displays the allocated ingress and egress bandwidth and the available ingress and egress bandwidth for Frame Relay logical ports. These bandwidth values are calculated with formulas based on whether Subscription Factor is enabled or disabled for the logical port.

Ingress Allocated Bandwidth (Kbps)

The allocated ingress bandwidth usage for the configured logical port.

Ingress Available Bandwidth (Kpbs)

The available ingress bandwidth usage for the configured logical port.

Egress Allocated Bandwidth (Kbps)

The allocated egress bandwidth usage for the configured logical port.

Egress Available Bandwidth (Kpbs)

The available egress bandwidth usage for the configured logical port.

Table 6-2. View Logical QoS Parameters Attributes (Continued)

Field Displays...


Viewing Logical Port SVC Attributes


Viewing Logical Port SVC Attributes

To view the configured SVC attributes for a logical port:


2. Right-click on the logical port and select Configure SVCs from the popup menu.

The Configure SVC dialog box appears (Figure 6-10).

Figure 6-10. Configure SVC Dialog Box

3. Select the appropriate tab for the attributes you want to view. For a description of the tabs and fields that are available, see the ATM Services Configuration Guide for CBX 3500, CBX 500, GX 550, and B-STDX 9000 or the Frame Relay Services Configuration Guide for CBX 3500, CBX 500, and B-STDX 9000.


The Configure SVC dialog box closes.

Viewing Logical Port SVC QoS Parameters

To view the configured SVC QoS attributes for a logical port:


2. Right-click on the logical port and select SVC QoS Parameters from the popup menu.



Logical Port AttributesViewing Logical Port SVC QoS Parameters

The View LPort SVC QoS Parameters dialog box appears (Figure 6-11).

Table 6-3 describes the View LPort SVC QoS Parameters dialog box elements.

Figure 6-11. View LPort SVC QoS Parameters Dialog Box

Table 6-3. View LPort SVC QoS Parameters Attributes

Fields Displays...

Configured – The configured QoS values (CBR, VBR-RT, VFR-RT, VBR-NRT, VFR-NRT, ABR/UBR, UFR) for the logical port.

SVC Allowed (%) This field specifies the percentage of the VFR-RT, VFR-NRT, or UFR bandwidth that is allocatable to SVCs on this logical port.

Outgoing Bandwidth (Reserved) – For each ATM or Frame Relay QoS class, this field of the dialog box displays the egress values for allocated bandwidth and virtual available bandwidth. The bandwidth is expressed as both the actual bandwidth and the percentage of the total logical port bandwidth.

Constant Bit Rate(ATM only)

The allocated bandwidth and virtual bandwidth egress values assigned to the CBR QoS class. This class handles digital information, such as video and digitized voice, which must be represented by a continuous stream of bits. CBR traffic requires guaranteed throughput rates and service levels.

Constant Frame Rate(Frame Relay only)

The allocated bandwidth and virtual bandwidth egress values assigned to control traffic, which is not a QoS class that you can configure.

Variable (Bit/Frame) Rate (VBR/VFR) Real Time

The allocated bandwidth and virtual bandwidth egress values assigned to either the VBR-RT or VFR-RT QoS class. These classes are designed for packaging special delay-sensitive applications, such as packet video, that require low cell/frame delay variation between endpoints.

Variable (Bit/Frame) Rate (VBR/VFR) Non-Real Time

The allocated bandwidth and virtual bandwidth egress values assigned to either the VBR-NRT or VFR-NRT QoS class. These classes handle packaging for transfer of long, bursty data streams over a pre-established connection. These classes are also used for short, bursty data, such as LAN traffic. CPE protocols adjust for any delay or loss incurred through the use of VBR-NRT or VFR-NRT.


Viewing Logical Port SVC QoS Parameters


Available/Unspecified (Bit/Frame) Rate (ABR/UBR/UFR)

The allocated bandwidth and virtual bandwidth egress values assigned to the ABR/UBR or UFR QoS class. These classes are primarily used for LAN traffic. The CPE should compensate for any traffic delay or loss.

Total The total allocated egress bandwidth.

Incoming Bandwidth (Reserved) – For each ATM QoS class, this field of the dialog box displays the ingress values for allocated bandwidth and virtual available bandwidth (ingress values do not apply to Frame Relay logical ports). The bandwidth is expressed as both the actual bandwidth and the percentage of the total logical port bandwidth.

Constant Bit Rate The allocated bandwidth and virtual bandwidth ingress values assigned to the CBR QoS class.

Variable Bit Rate (VBR) Real Time

The allocated bandwidth and virtual bandwidth ingress values assigned to the VBR-RT QoS class.

Variable Bit Rate (VBR) Non-Real Time

The allocated bandwidth and virtual bandwidth ingress values assigned to the VBR-NRT QoS class.

Available/Unspecified Bit Rate (ABR/UBR)

The allocated bandwidth and virtual bandwidth ingress values assigned to the ABR/UBR QoS class.

Total The total allocated ingress bandwidth.

Table 6-3. View LPort SVC QoS Parameters Attributes (Continued)

Fields Displays...



Logical Port AttributesViewing Logical Port SVC Traffic Descriptor Limits


The View LPort SVC QoS Parameters dialog box closes.

Viewing Logical Port SVC Traffic Descriptor Limits

To view the configured SVC traffic descriptor limits for a logical port:

1. At the Configure SVC dialog box (see “Viewing Logical Port SVC Attributes” on page 6-15), choose the Specify Limits button in the General tab.

The TD Limit dialog box appears (Figure 6-12). For a description of the attributes, see the ATM Services Configuration Guide for CBX 3500, CBX 500, GX 550, and B-STDX 9000 or Frame Relay Services Configuration Guide for CBX 3500, CBX 500, and B-STDX 9000.

Figure 6-12. TD Limits Dialog Box


The TD Limit dialog box closes.


Viewing Logical Port SVC Signaling Tuning Parameters


Viewing Logical Port SVC Signaling Tuning Parameters

To view the configured SVC signaling tuning parameters for a logical port:

1. At the Configure SVC dialog box (see “Viewing Logical Port SVC Attributes” on page 6-15), choose the Tuning Parameters button in the Signaling tab.

The SVC Signaling Tuning dialog box appears (Figure 6-13). For a description of the attributes, see the ATM Services Configuration Guide for CBX 3500, CBX 500, GX 550, and B-STDX 9000 or Frame Relay Services Configuration Guide for CBX 3500, CBX 500, and B-STDX 9000.

Figure 6-13. SVC Signaling Tuning Dialog Box


The SVC Signaling Tuning dialog box closes.



Logical Port AttributesViewing Logical Port SVC Signaling Tuning Parameters



7

Monitoring ATM Logical Ports

This chapter describes monitoring ATM logical port operational information and statistics. This chapter includes:

• “Viewing Operational Status for an ATM Logical Port” on page 7-1

• “Viewing ATM Logical Port Summary Statistics” on page 7-7

• “Viewing 2-port ULC Gigabit Ethernet Logical Port Summary Statistics” on page 7-17

• “Viewing ATM PNNI and AINI Logical Port Signaling Statistics” on page 7-22

• “Viewing Management VPI/VCIs” on page 7-24

Viewing Operational Status for an ATM Logical Port

This section describes how to view operational status for an ATM logical port.

Before You Begin

You cannot view operational information for a logical port if you have set the switch to Unmanaged. The switch must be set to Manage.



To View Operational Information for an ATM Logical Port1. Display the logical ports on the switch, module, subcard, or physical port (see

“Displaying Logical Ports” on page 6-1).

2. Right-click on the logical port and select Oper Info from the popup menu.



Monitoring ATM Logical PortsViewing Operational Status for an ATM Logical Port

The View LPort Operational Status dialog box appears (Figure 7-1).

Table 7-1 describes the View LPort Operational Status dialog box fields.

Table 7-2 describes the PNNI HELLO STATUS values that can appear for an NNI logical port.

Figure 7-1. View LPort Operational Status Dialog Box (ATM)

Table 7-1. View LPort Operational Status Dialog Box Fields (ATM)

Field Displays...

Failure Reason The reason for failure if the logical port is down.

Admin Status The logical port administration status:

Up – The logical port is active.

Down – The logical port is disabled or offline.

Operational Status The operational status of the logical port, either Up or Down.

Beta Draft ConfidentialMonitoring ATM Logical Ports



ILMI Admin Status (UNI DCE/DTE and NNI logical ports only)

ILMI Administrative status:

Enabled – Reserves a percentage of bandwidth in the VBR-NRT QoS class for ILMI. You can override the default values for bandwidth and QoS class by choosing the Traffic Descriptors button to assign traffic descriptors for the ILMI channel. To receive ILMI Virtual Channel Connection (VCC) status traps from non-Lucent ATM UNI 3.1 devices, Admin Status must be set to Enabled. For information about ILMI VCC trap support, see the ATM Services Configuration Guide for CBX 3500, CBX 500, GX 550, and B-STDX 9000.

Disabled – (default) Disables ILMI for the logical port, and does not reserve the bandwidth. If the attached device does not support ILMI, you should disable ILMI.

Note: If you are using line loopback diagnostics, you must disable ILMI support.

ILMI Operational Status

The current operational status of the ILMI control circuit.

Signalling Admin Status

(UNI DCE/DTE and NNI logical ports only)

Signalling Administrative status:

Enabled – Reserves a percentage of bandwidth in the VBR-NRT QoS class to support the UNI signaling protocol. You can override the default values for bandwidth and QoS class by choosing the Traffic Descriptors button to assign traffic descriptors for the signaling channel.

Disabled – (default) Disables signaling for the logical port, and does not reserve the bandwidth. If the attached device does not support UNI signaling, you should disable signaling.

Note: If you are using line loopback diagnostics, you must disable signaling support.

Signalling Operational Status

The current operational status of the signaling control circuit.

Table 7-1. View LPort Operational Status Dialog Box Fields (ATM) (Continued)

Field Displays...




PNNI HELLO STATUS

(NNI logical ports only)

The state of the PNNI Hello Finite State Machine (FSM) associated with the logical port you are monitoring. This state machine manages the exchange of hello packets between the switch and its neighbor. Neighboring nodes exchange these packets to discover and verify each other’s identity and to determine the status of the links that connect them. See Table 7-2 on page 7-4 for a description of the hello states that appear in this field.

PNNI Neighbor Node ID in Hex

(NNI logical ports only)

The hexadecimal node ID of the neighbor with which the switch communicates over the physical interface associated with the logical port. Each logical port on the switch communicates with a single neighbor that is reached over the physical interface (for example, OC-12c/STM-4) associated with the logical port.

PNNI Neighbor Port ID (NNI logical ports only)

The port ID that the neighbor assigns to its point of attachment to the logical link between the neighbor and the switch. A logical link represents the connectivity between two nodes. The connectivity includes individual physical links, individual virtual path connections, and parallel physical links or virtual path connections.

A value of zero indicates that the neighbor node has not assigned a port.

Table 7-2. PNNI Hello Finite State Machine States

Hello State Description

Down No PNNI routing packets are sent or received over the link.

This state is the initial state of the Hello FSM. This state is also reached when lower-level protocols have indicated that the link is not usable. For example, Down is reported if the physical link (for example, a DS3 link) to the neighbor is down, or the switch or its neighbor is not fully configured or operational.

Table 7-1. View LPort Operational Status Dialog Box Fields (ATM) (Continued)

Field Displays...




Attempt Either no Hello packets or Hello packets containing information that does not match have been received. For example, a mismatch occurs when a switch receives a Hello packet from a neighbor that does not contain the same peer group ID as the switch. If this state persists, check the PNNI routing configuration information on the switch and the neighbor for mismatches.

While in the attempt state, the switch attempts to contact the neighbor by periodically sending Hello packets.

One-way inside The switch has received Hello packets from the neighbor on this logical port. From the information in the packets, the switch establishes that both nodes are members of the same peer group. The remote node ID and port ID in the received Hello packets are set to zero.

Two-way inside The switch has recently received Hello packets from the neighbor, indicating that both nodes are members of the same peer group. The packets include the correct remote node ID and the correct port ID.

When the Hello FSM reaches this state, the switch and its neighbor can perform bidirectional communication over the link. Database summary packets, PNNI Topology State Element (PTSE) request packets, PNNI Topology State Packets (PTSPs), and PTSE acknowledgment packets can be transmitted only over links that are in this state. For physical links and virtual path connections (VPCs), only those links that are in this state can be advertised by the switch in PTSEs as horizontal links.

One-way outside The switch has received Hello packets from the neighbor on this logical port, and the information in the packets indicate that the neighbor node belongs to a different peer group. The remote node ID and port ID in the received Hello packets are set to 0.

While in this state, and while in the two-way outside state, the switch searches for a common peer group that contains both the switch and the neighbor.

Two-way outside The switch has recently received Hello packets from the neighbor, and the packets indicate that the neighbor node belongs to a different peer group. The packets include the correct remote node ID and remote port ID fields, but the nodal hierarchy list does not include any common peer group.

While in this state, and while in the one-way outside state, the switch searches for a common peer group that contains both the switch and the neighbor.

Table 7-2. PNNI Hello Finite State Machine States (Continued)







The View LPort Operational Status dialog box closes.

Viewing 2-port ULC Gigabit Ethernet Logical Port Operational Status

To view the operational information of a 2-port ULC Gigabit Ethernet logical port:

1. Display the logical port (see “Displaying Logical Ports” on page 6-1).

2. Right-click on the logical port object and select Oper Info from the popup menu

The View LPort Operational Status dialog box appears for the logical port (Figure 7-2).

Table 7-3 describes the View LPort Operational Status dialog box elements.

Figure 7-2. View LPort Operational Status Dialog Box

Common Outside The switch and its neighbor have found a common level of the routing hierarchy, and have achieved full bidirectional communication. Links that have achieved the Common Outside state can be advertised in PTSEs as uplinks, which connect border nodes and upnodes.

Not Applicable PNNI is not supported for this logical port.

Table 7-2. PNNI Hello Finite State Machine States (Continued)



Viewing ATM Logical Port Summary Statistics






To view summary statistics for an ATM logical port:


2. Expand the logical port for which you want to view summary statistics.


The LPort Statistics Monitoring dialog box appears (Figure 7-3).

Table 7-3. View LPort Operational Status Dialog Box Elements

Element Description

LPort Name Displays the name of the logical port.

Service Type Displays the type of module.

LPort Type Displays the typ of interface (UNI or NNI).

Failure Reason Displays the code for a failure if applicable.

Admin Status Displays whether the administrative status of the port is Up or Down.

Operational Status Displays whether the operational status of the port is Up or Down.



Monitoring ATM Logical PortsViewing ATM Logical Port Summary Statistics

Figure 7-3. LPort Statistics Monitoring Dialog Box

4. To view a particular category of statistics, select the appropriate category under the Monitoring node (Figure 7-4).

Figure 7-4. Statistics Categories Under a Monitoring Node (ATM Logical Port)

Table 7-4 lists the statistics categories that are available and where to find the descriptions of those statistics.

Table 7-4. Statistics Categories for ATM Logical Ports

Category Description of Statistics are in ...

General Table 7-5 on page 7-9

General (ATM CE Logical Port on 60-Port Channelized T1/E1 module)

Table 7-6 on page 7-10




5. Choose Reset to set the current statistics to zero and begin a new collection of statistics.


The LPort Statistics Monitoring dialog box closes.

Q.2931 Table 7-7 on page 7-11

SAAL Table 7-8 on page 7-14

ILMI Table 7-9 on page 7-15

NDC “Viewing NTM and NDC Statistics” on page 12-51

PNNI Table 7-10 on page 7-15

NTM “Viewing NTM and NDC Statistics” on page 12-51

Trunk Signaling Table 7-11 on page 7-16

Node to Node Table 7-11 on page 7-16

Table 7-5. General Statistics (ATM logical port)



Number of Octets The number of octets (bytes) received and transmitted since the last reset.


The number of inbound and outbound packets (frames) discarded since the last reset.

Number of Packet Errors

The number of packet errors received and transmitted since the last reset.

Number of Unicast Packets

The number of unicast packets received and transmitted since the last reset.

Number of Cells The total number of cells received and transmitted by the port since the last reset.

ThroughPut

Throughput Bits per Second

The total number of bits received and transmitted by the port each second.

Throughput Cells per Second

The total number of cells received and transmitted by the port each second.

Table 7-4. Statistics Categories for ATM Logical Ports





ABR

IOM Multicast Discard The total number of incoming cells on the port’s multicast circuits that were discarded by the ATM Flow-Control Processor (FCP).

ATM FCP RM Cells The total number of RM cells that the ATM FCP received on the logical port.

Table 7-6. General Statistics (CE logical port on 60-Port Channelized T1/E1 CE Module)

Field Displays...

General CES Statistics

Attribute Name and Value fields The names of the attributes, listed below, and the value for each attribute.

Parity check failure The number of events in which the AAL1 reassembler expects a structured data pointer, but detects a parity check failure instead.


Instances in which SDT pointer not present

Number of events in which the AAL1 reassembler found that a structured data transfer (SDT) pointer was not where expected and so the pointer has to be reacquired. This statistic applies only to Structured CES mode.

Note: For unstructured Circuit Emulation Service (CES) modes, which do not use pointers, this number should be zero.

AAL1 header errors detected The number of AAL1 header errors detected. These errors include correctable and uncorrectable CRC and bad parity.

Data cells received Number of data cells received. The count does not include cells that were not used because they were considered misinserted and cells that were discarded while the reassembler was achieving synchronization.

AAL1 sequence violations Number of AAL1 sequence violations which are interpreted as misinserted cells as defined in ITU-T I.363.I.

Table 7-5. General Statistics (ATM logical port) (Continued)





Lost cells The number of lost cells as, for example, detected by the AAL1 sequence number processing.

Buffer overflows The number of time the CES reassembly buffer overflows.

Buffer underflows The number of time the CES reassembly buffer underflows. A continuous underflow caused by loss of ATM cell flow is counted as one underflow.

Incoming AAL1 SAR-PDU sequence number errors

The number of times that the sequence number of an incoming AAL1 type 1 SAR-PDU causes a transition from the “sync” state to the “out of sequence” state as defined by ITU-T I.363.I.

Table 7-7. Q.2931 Statistics (ATM Logical Port)



Number of SVC Failures

The total number of SVC failures on this logical port resulting from the transmission or reception of RELEASE, ADD PARTY REJECT, or DROP PARTY PDUs with abnormal cause codes.

Last Cause Code The last received and transmitted cause code. Cause codes are listed in the ATM/UNI Forum specifications. The reset statistics function (that you select by using the Reset button) does not update this statistic.

Setup PDUs The number of Setup protocol data units (PDUs). A Setup PDU is used to place a call.

Call Proceeding PDUs The number of local acknowledgments of a Setup PDU. The local acknowledgment specifies that the call is being processed.

Connect PDUs The number of Connect PDUs. A Connect PDU is used to accept a call.

Connect Acknowledge PDUs

The number of local acknowledgments to Connect PDUs.

Release PDUs The number of Release PDUs. A Release PDU is used to terminate calls. A value in this field that exceeds the value for the number of Connect PDUs indicates that the system is dropping calls.

Table 7-6. General Statistics (CE logical port on 60-Port Channelized T1/E1 CE Module) (Continued)

Field Displays...




Release Complete PDUs

The number of Release Complete PDUs. A Release Complete PDU is a local acknowledgment that the Release PDU was received.

Add Party PDUs The number of Add Party PDUs. An Add Party PDU is used to add a leaf to a point-to-multipoint (PMP) connection.

Add Party Acknowledge PDUs

The number of Add Party Acknowledgment PDUs. An Add Party Acknowledgment PDU is a local acknowledgment that the Add party PDU was received.

Add Party Reject PDUs The number of Add Party Reject PDUs. An Add Party Reject PDU is used to reject an Add Party request.

Drop Party PDUs The number of Drop Party PDUs. A Drop Party PDU is a PDU used to terminate a leaf from a PMP connection.

Drop Party Acknowledge PDUs

The number of Drop Party Acknowledgment PDUs. A Drop Party Acknowledgment PDU is a local acknowledgment that the Drop Party PDU was received.

Status Enquiry PDUs The number of Status Enquiry PDUs. A Status Enquiry PDU is an unsolicited status request for a call. One endpoint signals that the connection seems valid and expects verification from the other endpoint.

Status PDUs The number of Status PDUs. A Status PDU is a response to a Status Enquiry PDU. The PDU indicates the state of the call.

Restart PDUs The number of Restart PDUs. A Restart PDU is used to restart a single call or the entire signaling VC.

Restart Acknowledge PDUs

The number of Restart Acknowledgment PDUs. A Restart Acknowledgment PDU is a local acknowledgment of a Restart PDU.

Notify PDUs The number of Notify PDUs. A Notify PDU delivers notification when notification does not coincide with call/connection establishment procedures or call/connection clearing procedures. In addition, a Notify PDU is sent or received by the user or by the network only after the first response to a Setup PDU has been sent or received and before clearing of the call reference is initiated.

Progress PDUs The number of Progress PDUs. Progress PDUs are used when a B-ISDN channel is used as a transit network for multiple ISDN networks.

Table 7-7. Q.2931 Statistics (ATM Logical Port) (Continued)





Alerting PDUs The number of Alerting PDUs. The user sends an Alerting PDU on a point-to-point SVC when it determines that sufficient call setup information has been received from the network and compatibility requirements have been satisfied. The network sends an Alerting PDU in response to an Alerting PDU from the user.

If the network receives an Alerting PDU, but does not receive a Connect PDU or Release PDU before the expiration of T301 (or a corresponding internal alerting supervision timing function), then the network may initiate call clearing procedures toward the user.

Party Alerting PDUs The number of Party Alerting PDUs. A Party Alerting PDU is sent on a PMP circuit to indicate that alerting has begun at the called party.

Party Alerting PDUs have the same function as Alerting PDUs, but Party Alerting PDUs are sent on PMP circuits and Alerting PDUs are sent on point-to-point circuits.

Q2931 Statistics

Number of SVCs established

The total number of SVCs established since the IOM became active.

Number of Active SVCs

The number of SVCs that are currently active. The reset statistics function (that you select by using the Reset button) does not update this statistic.

Table 7-7. Q.2931 Statistics (ATM Logical Port) (Continued)





Table 7-8. SAAL Statistics (ATM Logical Port)



Discards The number of discards.

Errors The number of errors.

Begin PDUs The number of Begin PDUs, which request establishment of signaling ATM adaption layer (SAAL) connections.

Begin Acknowledge PDUs

The number of Begin Acknowledgment PDUs, which acknowledge the acceptance of connection requests (Begin PDUs).

Begin Reject PDUs The number of Begin Reject PDUs, which reject SAAL connection requests.

End PDUs The number of End PDUs, which terminate SAAL connections.

End Acknowledge PDUs

The number of End Acknowledgment PDUs, which confirm termination of SAAL connections.

Resynchronization PDUs

The number of Resynchronization PDUs, which resynchronize system resources and states on both endpoints if they are out-of-sync.

Resync. Acknowledge PDUs

The number of Resynchronization Acknowledgment PDUs, which acknowledge acceptance of Resynchronization PDUs.

Error Recovery PDUs The number of Error Recovery PDUs, which are sent to correct protocol errors.

Error Recovery Ack. PDUs

The number of Error Recovery Acknowledgment PDUs, which acknowledge Error Recovery PDUs (acknowledge recovery from a protocol error).

Sequenced Data PDUs The number of Sequenced Data PDUs, which are sequentially numbered PDUs containing user-provided information fields.

Polling PDUs The number of Poll PDUs, which are sent as keep alive (KA) signals for the SAAL connection. Poll PDUs request status information about the other end of the connection.

Status PDUs The number of Status PDUs, which respond to Poll PDUs.

Unsolicited Status PDUs

The number of Unsolicited Status PDUs, which inform the sender of one or more missing Sequenced Data PDUs.

Unnumbered User PDUs and Unnumbered Mgmt PDUs

Not used.




Signaling Channel Octets

The number of octets transmitted or received on the SAAL connection.

SAAL Statistics

Transmit Window Depth

The current depth of the SAAL transmit window, which represents the current number of outstanding, unacknowledged Sequenced Data PDUs.

Table 7-9. ILMI Statistics (ATM logical port)



Number of Octets The total number of octets received and transmitted by the port.

Number of PDUs The total number of PDUs that were received with a proper format and transmitted.

Number of UME Entity Polls

The total number of ILMI received status polls issued by the User Management Entity (UME) at this port.

ILMI Statistics

Errors Transmitted The total number of PDUs that were received with an improper format.

Table 7-10. PNNI Statistics (ATM logical port)


Link Hellos The number of hello packets transmitted and received. These packets contain information that neighboring nodes exchange to discover and verify each other’s identity and to determine the status of the links that connect them.

Table 7-8. SAAL Statistics (ATM Logical Port) (Continued)





Table 7-11. Trunk Signalng and Node to Node (Control Channel) Statistics(ATM Direct and OPTimum Trunk Logical Ports)


Number of Cells The total number of ATM cells received and transmitted on the control channel.

Passed CLP=0 Cells The number of ATM CLP=0 cells that were received and transmitted on the control channel that passed UPC.

Passed CLP=1 Cells The number of ATM CLP=1 cells that were received and transmitted on the control channel that passed UPC.

Discarded CLP=0 Cells The number of ATM CLP=0 cells that were received on the control channel, but were discarded due to UPC failure. Ignore the value in the Transmitted column.

Note: If you notice that CLP=0 cells are discarded consistently, consider increasing the Maximum Burst Size (MBS) for the control circuit. See the ATM Services Configuration Guide for CBX 3500, CBX 500, GX 550, and B-STDX 9000 for more information.

Discarded CLP=1 Cells The number of ATM CLP=1 cells that were received on the control channel, but were discarded due to UPC failure. Ignore the value in the Transmitted column.

Note: If you notice that CLP=1 cells are discarded consistently, consider increasing the MBS for the control circuit. See the ATM Services Configuration Guide for CBX 3500, CBX 500, GX 550, and B-STDX 9000 for more information.

Tagged Cells The number of tagged ATM cells received. Ignore the value in the Transmitted column.

Note: If you notice that cells are tagged consistently, consider increasing the MBS for the control circuit. See the ATM Services Configuration Guide for CBX 3500, CBX 500, GX 550, and B-STDX 9000 for more information.

OAM CLP=0 Cells The number of ATM OAM CLP=0 cells transmitted. Ignore the value in the Received column.

OAM CLP=1 Cells The number of ATM OAM CLP=1 cells transmitted. Ignore the value in the Received column.


Viewing 2-port ULC Gigabit Ethernet Logical Port Summary Statistics



The 2-port ULC Gigabit Ethernet module supports service interworking connections via EVCs (ethernet virtual circuits) between the following endpoints over ATM or MPLS core:

• Ethernet to Ethernet

• Ethernet to ATM

• Ethernet to Frame

For further details on the 2-port ULC Gigabit Ethernet module, see the ATM Services Guide for CBX 3500, CBX 500, GX 550, and B-STDX 9000.

You may view 2-port ULC Gigabit Ethernet logical port summary statistics in the following sections:

• “Viewing 2-port ULC Gigabit Ethernet LPort Object Summary Statistics” on page 7-17

• “Viewing 2-port ULC Gigabit Ethernet LPort Shaper Object Summary Statistics” on page 7-19

• “Viewing 2-port ULC Gigabit Ethernet LPort VLAN Profile Summary Statistics” on page 7-20

Viewing 2-port ULC Gigabit Ethernet LPort Object Summary Statistics

To view 2-port ULC Gigabit Ethernet LPort object summary statistics:

1. Display the logical ports on the selected physical port (see “Displaying Logical Ports” on page 6-1).

2. Expand the 2-port ULC Gigabit Ethernet logical port for which you want to view summary statistics.

3. Right-click on the Monitoring node for the LPort object, and choose Start from the popup menu.

The LPort Statistics Monitoring dialog box appears (Figure 7-5) for the 2-port ULC Gigabit Ethernet module. Table 7-12 describes the statistics for the LPort Statistics Monitoring dialog box.



Monitoring ATM Logical PortsViewing 2-port ULC Gigabit Ethernet Logical Port Summary Statistics

Figure 7-5. 2-port ULC Gigabit Ethernet Logical Port Statistics Monitoring Dialog Box

Table 7-12. 2-port ULC Gigabit Ethernet Logical Port Statistics Monitoring



EthOctetsHigh Displays the high number of octets received on this port since the last reset.

EthOctetsLow Displays the low number of octets received on this port since the last reset.




4. Choose Diagnostics to test packet transmissions on this port (See “Viewing Foreground Diagnostics For a Logical Port on the 2-port ULC Gigabit Ethernet Module” on page 5-21).

5. Choose Close to close this dialog box.

Viewing 2-port ULC Gigabit Ethernet LPort Shaper Object Summary Statistics

To view 2-port ULC Gigabit Ethernet LPort object summary statistics:



3. Right-click on the Monitoring node for the LPort Shaper object, and choose Start from the popup menu.

The LPort Shaper Statistics Monitoring dialog box appears (Figure 7-6) for the 2-port ULC Gigabit Ethernet module. Table 7-13 describes the statistics for the LPort Shaper Statistics Monitoring dialog box.

EthDiscardedOctetsHigh Displays the high number of octets discarded on this port since the last reset

EthDiscardedOctetsLow Displays the low number of octets discarded on this port since the last reset

EthArpThresholdDiscards Displays the number of frames discarded on this port due to ARP threshold failure since the last reset

EthMulticastBroadcastThresholdDiscards

Displays the number of frames discarded on this port due to Multicast Broadcast threshold failure since the last reset

EthLookupFailureDiscards Displays the number of frames discarded on this port due to Lookup failure since the last reset

General Statistics

Not applicable

ThroughPut

ThroughputEthOctetsPerSec

Displays the number of octets per second processed through this port since the last reset.

Table 7-12. 2-port ULC Gigabit Ethernet Logical Port Statistics Monitoring (Continued)




Monitoring ATM Logical PortsViewing 2-port ULC Gigabit Ethernet Logical Port Summary Statistics

Figure 7-6. 2-port ULC Gigabit Ethernet Logical Port Shaper Statistics Monitoring Dialog Box

Viewing 2-port ULC Gigabit Ethernet LPort VLAN Profile Summary Statistics

To view 2-port ULC Gigabit Ethernet LPort VLAN profile summary statistics:



Table 7-13. 2-port ULC Gigabit Ethernet Logical Port Shaper Statistics Monitoring


General Statistics

OutFrames Displays the number of Ethernet frames of EVCs transmitted from this port since the last reset.

OutDiscardedFrames Displays the number of Ethernet frames discarded from this port due to buffer overflow since the last reset.

OutOctetsLow Displays the low number of Ethernet octets of EVCs transmitted from this port since the last reset.

OutOctetsHigh Displays the high number of Ethernet octets of EVCs transmitted from this port since the last reset.




3. Right-click on the Monitoring node for the VLAN profile object, and choose Start from the popup menu.

The VLAN Profile Statistics Monitoring Statistics dialog box appears (Figure 7-7) for the 2-port ULC Gigabit Ethernet module. Table 7-14 describes the statistics for the VLAN Profile Statistics Monitoring dialog box.

Figure 7-7. 2-port ULC Gigabit Ethernet Logical Port VLAN Profile Statistics Monitoring Dialog Box

Table 7-14. 2-port ULC Gigabit Ethernet Logical Port VLAN Profile Statistics Monitoring


General Statistics

ethVLANInUnicastHighOctets

Displays the total number of unicast octets received on this VLAN. This represents the most significant 32 bits.

ethVLANInUnicastLowOctets

Displays the total number of unicast octets received on this VLAN. This represents the least significant 32 bits.

ethVLANInBroadMulticastHighOctets

Displays the total number of broadcast and multicast octets received on this VLAN. This represents the most significant 32 bits.



Monitoring ATM Logical PortsViewing ATM PNNI and AINI Logical Port Signaling Statistics

For additional information on 2-port ULC Gigabit Ethernet LPort circuit summary statistics, see “Viewing 2-port ULC Gigabit Ethernet LPort Circuit Summary Statistics for Ethernet to ATM Endpoints” on page 12-42 and “Viewing 2-port ULC Gigabit Ethernet LPort Circuit Summary Statistics for Ethernet to Frame Relay Endpoints” on page 13-15.

Viewing ATM PNNI and AINI Logical Port Signaling Statistics

To view signaling statistics for an ATM PNNI or AINI logical port:


2. Expand the logical port for which you want to view signaling statistics.

3. Right-click on the logical port instance node, and select NNI Signaling Statistics from the popup menu.

The NNI Signaling Statistics for LPort dialog box appears (Figure 7-3).

ethVLANInBroadMulticastLowOctets

Displays the total number of broadcast and multicast octets received on this VLAN. This represents the least significant 32 bits.

ethVLANInUnknownTypeFrames

Displays the total number of broadcast and multicast octets received on this VLAN.

ethVLANOutFrames Displays the total number of frames sent out on this VLAN.

ethVLANOutHighOctets Displays the total number of octets sent out on this VLAN. This represents the most significant 32 bits.

ethVLANOutLowOctets Displays the total number of octets sent out on this VLAN. This represents the least signficant 32 bits.

ethVLANBufferDiscards Displays the total number of frames discarded due to buffer allocation problems.

ethVLANFilteringDiscards Displays the total number of frames discarded due to MAC filtering.

ethVLANInUnicastframes Displays the total number of unicast frames received on this VLAN

Table 7-14. 2-port ULC Gigabit Ethernet Logical Port VLAN Profile Statistics Monitoring (Continued)



Viewing ATM PNNI and AINI Logical Port Signaling Statistics


Figure 7-8. NNI Signalling Statistics for LPort Dialog Box

The fields in the PNNI Signalling Statistics dialog box are described in Table 7-15.

Table 7-15. NNI Node Signalling Statistics for LPort

Field Description

Successful call attempts as a origination node

Displays the number of successful call attempts from this object as an orignation node.

Unsuccessful call attempts as a origination node

Displays the number of unsuccessful call attempts from this object as an orignation node.

Crank-backs directed to this node as a origination node

Displays the number of crank-backs directed to this object as an orignation node.

Successful call attempts as a border node

Displays the number of successful call attempts from this object as a border node.

Unsuccessful call attempts as a border node

Displays the number of unsuccessful call attempts from this object as a border node.

Crank-backs directed to this node as a border node

Displays the number of crank-backs directed to this object as a border node.

Crank-backs initiated Displays the number of crank-backs initiated by this port.



Monitoring ATM Logical PortsViewing Management VPI/VCIs


5. When you are done viewing the signaling statistics, choose Close.

The PNNI Signalling Statistics dialog box closes.

Viewing Management VPI/VCIs

To view the configured attributes for a Management VPI/VCI:


2. Expand the logical port for which you want to view a Management VPI/VCI.

3. Expand the Mgmt VPI/VCI class node.

4. Right-click on the Management VPI/VCI, and select View from the popup menu.

The View Management VPI/VCI dialog box appears (Figure 7-9). For a description of the attributes, see the ATM Services Configuration Guide for CBX 3500, CBX 500, GX 550, and B-STDX 9000.

Successful PMP call attempts as a origination node

Displays the number of successful PMP call attempts from this object as an orignation node.

Unsuccessful PMP call attempts as a origination node

Displays the number of unsuccessful PMP call attempts from this object as an orignation node.

PMP Crank-backs directed to this node as a origination node

Displays the number of PMP crank-backs directed to this object as an orignation node.

Successful PMP call attempts as a border node

Displays the number of successful PMP call attempts from this object as a border node.

Unsuccessful PMP call attempts as a border node

Displays the number of unsuccessful PMP call attempts from this object as a border node.

PMP crank-backs directed to this node as a border node

Displays the number of PMP crank-backs directed to this object as a border node.

PMP crank-backs initiated Displays the number of PMP crank-backs initiated by this port.

Table 7-15. NNI Node Signalling Statistics for LPort

Field Description

Beta Draft ConfidentialMonitoring ATM Logical PortsViewing Management VPI/VCIs


Figure 7-9. View Management VPI/VCI Dialog Box


The View Management VPI/VCI dialog box closes.



Monitoring ATM Logical PortsViewing Management VPI/VCIs



8

Monitoring Frame Relay Logical Ports

This chapter describes monitoring Frame Relay logical port operational information and statistics. This chapter includes;

• “Viewing Operational Status for a Frame Relay Logical Port” on page 8-1

• “Viewing Frame Relay Logical Port Summary Statistics” on page 8-6

• “Viewing Multicast DLCIs” on page 8-15

• “Viewing Management DLCIs” on page 8-16

Viewing Operational Status for a Frame Relay Logical Port

This section describes how to view operational status for a Frame Relay logical port.

Before You Begin

You cannot view operational information for a logical port if you have set the switch to Unmanaged. The switch must be set to Manage.



To View Operational Information for a Frame Relay Logical Port1. Display the logical ports on the switch, module, subcard, or physical port (see

“Displaying Logical Ports” on page 6-1).



Monitoring Frame Relay Logical PortsViewing Operational Status for a Frame Relay Logical Port

2. Right-click on the logical port and select Oper Info from the popup menu.

The View LPort Operational Status dialog box appears. Figure 8-1 shows the dialog box for a Frame Relay UNI DCE, and Figure 8-2 shows the dialog box for an MLFR UNI DCE.

Table 8-1 describes the View LPort Operational Status dialog box fields for Frame Relay non-MLFR logical ports.

Table 8-2 describes the View LPort Operational Status dialog box fields for MLFR logical ports.

Figure 8-1. View LPort Operational Status Dialog Box (Frame Relay UNI DCE)

Figure 8-2. View LPort Operational Status Dialog Box (MLFR UNI DCE)

Beta Draft ConfidentialMonitoring Frame Relay Logical Ports



Table 8-1. View LPort Operational Status Dialog Box Fields (Frame Relay non-MLFR)

Field Displays...

Failure Reason The reason the LPort failed (if any).

Admin Status One of the following:

Up – The LPort is active.

Down – The LPort is inactive or off line.

Operational Status The operational status of the selected port as Up or Down, or Unknown, which indicates that the NMS is unable to contact the switch to retrieve status.

Last Invalid DLCI The last invalid DLCI that the switch detected. If a value appears in this field, either the switch or the CPE was not configured properly. Check this value if you have a DLCI that is not receiving traffic.

Q922 Operational Status The current state of Q.922 signaling. This field displays Disabled or, if Q.922 is Enabled, one of the following signaling states:

Uninitialized – Q.922 (or Q.933) signaling is disabled because it is not initialized.

TEI-Assigned – A DLCI has been assigned to the link but the connection has not been established.

Awaiting-Establishment – The DLCI has been assigned and both sides of the connection are waiting for the connection to be established.

Multiple-Frame-Established – The connection is established. Acknowledged data transfer requests are now possible.

Timer-Recovery – The T200 time has expired. The connection returns to the Multiple-Frame-Established state after the timer recovery procedure is complete.

Awaiting-Release – One side of the connection issued a connection release request. The connection then returns to the terminal endpoint identifier (TEI)-Assigned state.



Monitoring Frame Relay Logical PortsViewing Operational Status for a Frame Relay Logical Port

RLMI Operational Status The current RLMI operational status. Options are:

None – (default) No RLMI operational status.

Idle – Waiting for link switch parameters.

Protect Init – State entered when the RLMI link starts initialization as the protection link whenever a preferred/working switchover occurs.

Protect Down – State entered when the protection link receives a message from the LMI that the LMI’s operational state is down due to excessive errors (for example, the LMI is down, the LPort is disabled, or a card is down).

Protect Up – State entered when the protection link receives a message from the LMI that the LMI’s operational state is up.

Working Init – State entered when the RLMI link starts initialization as the working link whenever a preferred/working switchover occurs.

Working Down – State entered when the working link receives an indication from the LMI that the LMI’s operational state is down due to excessive errors (for example, the LMI is down, the LPort is disabled, a card is down).

Working Up – State entered when the protection link receives a message from the LMI that the LMI’s operational state is up.

RLMI Full Status Attempts The number of LMI Full Status Enquiry attempts for bringing up the working interface. This number cannot exceed the value that is set in the RLMI Max Full Status Attempts field.

FRF.19 Active FrOam Session Count

(6-Port Channelized DS3/1/0 Frame Relay Module only)

The number of Frame Relay OAM-enabled circuits on the LPort.

Table 8-1. View LPort Operational Status Dialog Box Fields (Frame Relay non-MLFR) (Continued)

Field Displays...







Restart State The global restart state for the logical port. The logical port can be in one of the following global restart states:

Null – No restart conditions exist.

Restart Request – The logical port sent a restart request to its UNI/NNI peer, but has not received an acknowledgment. Restart request messages are usually sent as part of data link initialization.

Restart – The logical port received a restart request from its UNI/NNI peer, but has not sent a response.

Table 8-2. View LPort Operational Status Dialog Box Fields (MLFR)

Field Displays...

Failure Reason The reason the LPort failed (if any).

Admin Status One of the following:

Up – The LPort is active.

Down – The LPort is inactive or off-line.

Operational Status The operational status of the selected port as Up or Down, or Unknown, which indicates that the NMS is unable to contact the switch to retrieve status.

MLFR Bundle Available Bandwidth

The available bandwidth of the MLFR bundle expressed in kilobits per second (Kbps).

Number of Allocated Member Links

The number of links that are allocated for ML Member logical ports to bind to this MLFR bundle.

Number of Active Member Links

The number of active member links in the MLFR bundle.

Bound Member Lports Operational Status or MLFR Member Link Status

The member link state as either up (green) or down (red).

Table 8-1. View LPort Operational Status Dialog Box Fields (Frame Relay non-MLFR) (Continued)

Field Displays...



Monitoring Frame Relay Logical PortsViewing Frame Relay Logical Port Summary Statistics

Viewing Frame Relay Logical Port Summary Statistics

To view summary statistics for a Frame Relay logical port:


2. Expand the logical port for which you want to view summary statistics.


The LPort Statistics Monitoring dialog box appears (Figure 8-3).

Figure 8-3. LPort Statistics Monitoring Dialog Box




4. To view a particular category of statistics, select the appropriate category under the Monitoring node (Figure 8-4).

Table 8-3 lists the statistics categories that are available and where to find the descriptions of those statistics.

The statistics in the General category depend on the type of logical port:

• UNI/NNI logical port — The system displays both DTE and DCE statistics.

• UNI-DCE logical port — The system displays only DCE statistics.

• UNI-DTE logical port — The system displays only DTE statistics.

If the link management interface (LMI) protocol is disabled, the system does not display DTE or DCE statistics for a logical port. You set the LMI interface protocol when you define the parameters for a logical port. See the Frame Relay Services Configuration Guide for CBX 3500, CBX 500, and B-STDX 9000 for more information about defining the LMI protocol.

Figure 8-4. Statistics Categories Under a Monitoring Node (Frame Relay Logical Port)




Table 8-3. Statistics Categories for Frame Relay Logical Ports


General Table 8-4 on page 8-8






Table 8-4. General Statistics (Frame Relay Logical Port)



Number of Octets The number of octets (bytes) received and transmitted since the last reset.

Number of Packet Errors

The number of packet (frame) errors since the last reset.


The number of packets (frames) discarded since the last reset.

Number of Unicast Packets

The number of unicast packets (frames) received and transmitted since the last reset.

General Statistics

CLLM PDUs Count The number of transmitted CLLM PDUs.

DCE Poll Frames Received

The total number of LMI Status Enquiry frames received on this logical port. This statistic includes both LIV and Full Status Enquiry messages.

DCE Error Frames Received

The number of LMI Status Enquiry frames received (either LIV or Full) that contain either an invalid receive sequence number (Nr) or an invalid send sequence number (Ns).

LMI Oper Status The state of the connection between the two communication devices for which you are collecting statistics. If the logical port is functioning properly, this value should display as Up.

If LMI Operator Status is Down, but the operating status of the logical port is Up, there is a link management problem, not a physical link problem.

Whenever the LMI Operator Status is not set to Down, you must determine whether the DCE Poll Timer at the logical port is set to a value that is less than the “keep-alive” value set on the FRAD (router). If the switch does not receive a poll before this timer expires, LMI will not come up.

LMI Error Frames Received

The number of LMI error frames that were received. If you are collecting statistics for a UNI/NNI logical port, this value is the sum of all DCE and DTE error frames.

DTE Oper Status The state of the data terminal equipment.




DCE Fail Counts The number of times that the LMI protocol declares the link to be down. The protocol declares the link as down if N392 out of N393 events are in error. The DCE Status Enquiry Frames Error Count statistic outlines the reasons for counting a condition as an error.

DCE Poll Error Counts The total number of LMI errors on this logical port, including the following:

• The number of times that a Status Enquiry frame (LIV and Full) was not received during a T392 second interval.

• The number of times that the LMI protocol declares the link to be down. See the description of the DCE Fail Count field for more information.

Any value other than zero in this field indicates a problem.

DCE Async Status Frames Transmitted

The number of asynchronous LMI Status frames transmitted on this logical port. For logical ports configured for ANSI Annex D or CCITT Annex A, this count includes only Status frames with a report type of Async. For logical ports configured for LMI Revision 1, this count includes only Update Status messages.

DCE Full Status Frames Transmitted

The number of LMI Status frames transmitted on this logical port from the DCE device. This statistic includes all Status frames with a report type of Full. Full Status frames include the status (for example, active or inactive) of each PVC configured on this logical port.

DCE Status Frames Transmitted

The number of LMI Status frames transmitted on this logical port. This statistic includes all Status frames with a report type of link integrity verification (LIV).

DTE Fail Count The number of times the LMI protocol declares the link to be down. The protocol declares the link as down if N392 out of N393 events are in error. The DTE Status Enquiry Frames Error Count statistic outlines the reasons for counting a condition as an error.

DTE Poll Error Count The total number of LMI errors on this logical port, including the following:

• Error frames received from the DCE device.

• The number of times a Status frame (LIV and Full) was not received in response to a Status Enquiry. An error is counted each time a Status Enquiry is transmitted, if a Status message was not received since the last Status Enquiry was sent.


Table 8-4. General Statistics (Frame Relay Logical Port) (Continued)





DTE Poll Frames Transmitted

The number of LMI Status Enquiry frames transmitted on this logical port. This includes both LIV and Full Status Enquiry messages.

DTE Error Frames Received

The number of LMI Status frames received (either LIV or Full) that contained either an invalid receive sequence number (Nr) or an invalid send sequence number (Ns).


DTE Async Status Frames Received

The number of Asynchronous LMI Status frames received on this logical port from the DCE device. For logical ports configured for ANSI Annex D or CCITT Annex A, this count includes only Status frames with a report type of Async. For logical ports configured for LMI Revision 1, this count includes only the number of Update Status messages received from the DCE device.

DTE Full Status Frames Received

The number of LMI Status frames received on this logical port from the DCE device. This only includes Status frames with a report type of full. Full Status frames include the status (for example, active or inactive) of each PVC configured on the DCE device for this link.

DTE Status Frames Received

The number of LMI Status frames received on this logical port from the DCE device. This only includes Status frames with a report type of LIV.

Utilization

Utilization (%) (Received)

The amount of traffic received on a logical port as a percentage of the committed information rate (CIR). It does not measure the amount of bandwidth of the logical port, so the value that the system displays in this field can exceed 100%.

Utilization (%) (Transmitted)

The amount of traffic queued for transmission on a logical port as a percentage of the CIR. It does not measure the amount of bandwidth of the logical port, so the value that the system displays in this field can exceed 100%.

Table 8-4. General Statistics (Frame Relay Logical Port) (Continued)





Table 8-5. Q.933 Statistics (Frame Relay Logical Port)


Q933 Cumulative Statistics

Last Cause Code The last received and transmitted cause code. Cause codes are listed in the ITU Q.850 specification.

Setup PDUs The number of Setup protocol data units (PDUs). A setup PDU is used to place a call.

Call Proceeding PDUs The number of local acknowledgments that the requested call has initiated. The local acknowledgment specifies that the call is being processed.

Connect PDUs The number of Connect PDUs. A Connect PDU is used to accept a call, making the call state “active.”

Disconnect PDUs The number of Disconnect PDUs. A Disconnect PDU is used to terminate a call that has reached the “active” state.

Release PDUs The number of Release PDUs. A Release PDU is used to terminate a call that has not reached the “active” state. It is also used as a local acknowledgment that the Disconnect PDU was received.

Release Complete PDUs

The number of Release Complete PDUs. A Release Complete PDU is used to reject a received SETUP message. It is also used as a local acknowledgment that the Release PDU was received.

Status Enquiry PDUs The number of Status Enquiry PDUs. One endpoint signals that the connection seems valid by sending the Status Enquiry PDU, and expects verification from the other endpoint in a received Status PDU.

Status PDUs The number of Status PDUs. A Status PDU is a response to a Status Enquiry PDU or may be an unsolicited status indication. The PDU indicates the state of the call and information about the cause.

Restart PDUs The number of Restart PDUs. A Restart PDU is used to restart the entire signaling VC. All SVCs are cleared.

Restart Acknowledge PDUs

The number of Restart Acknowledgment PDUs. A Restart Acknowledgment PDU is a local acknowledgment of a Restart PDU.




Q933 Statistics

Total Connections The total number of SVCs established since the IOM became active.

Active Connections The number of SVCs that are currently active.

Table 8-6. Q.922 Statistics (Frame Relay Logical Port)


Number of Octets The total number of octets that the logical report has received and transmitted. Each PDU consists of octets.

SABME PDUs The number of PDUs that the logical port has received and transmitted that contain Set Asynchronous Balanced Mode Extended (SABME) unnumbered commands. These commands place the data link into module 128 multiple-frame acknowledged operation.

UA PDUs The number of PDUs containing Unnumbered Acknowledgment (UA) responses that the logical port has received and transmitted. UAs acknowledge receipt and acceptance of SABMEs and Disconnects (DISCs).

DM PDUs The number of PDUs containing Disconnected Mode (DM) responses that the logical port has received and transmitted. DMs acknowledge SABMEs and DISCs, and indicate that the entity is unable to enter multiple-frame acknowledge operation.

DISC PDUs The number of PDUs containing DISC unnumbered commands that the logical port has received and transmitted. DISCs are requests for connection termination.

RR PDUs The number of PDUs containing receive ready (RR) commands and responses that the logical port has received and transmitted. RRs perform the following functions:

• Indicate that the logical port is ready to receive an information (I) frame.

• Acknowledge a certain number of previously received I frames.

• Clear a busy condition.

Table 8-5. Q.933 Statistics (Frame Relay Logical Port) (Continued)



Viewing RLMI Service Name Bindings


Viewing RLMI Service Name Bindings

To view the information for a service name:


2. Expand the logical port for which you want to view a service name.

3. Expand the Service Names class node.

The service names that belong to the LPort appear.

4. Right-click on the service name and select View from the popup menu.

RNR PDUs The number of PDUs containing receive not ready (RNR) commands and responses that the logical port has received and transmitted. The logical port sends an RNR to notify the other end of the connection that it is too busy to accept additional I frames.

REJ PDUs The number of PDUs containing Reject (REJ) commands and responses that the logical port has received and transmitted. The logical port sends an REJ to request retransmission of one or more I frames.

I PDUs The number of information (I) PDUs (also known as I frames) that the logical port has received and transmitted. These PDUs carry user data.

FRMR PDUs The number of PDUs containing frame reject (FRMR) responses that the logical port has received and transmitted. FRMRs report error conditions resulting from the receipt of an invalid frame, including:

• Receipt of a command or response control field that is undefined.

• Receipt of a supervisory or unnumbered frame with incorrect length.

• Receipt of an invalid N (R).

• Receipt of a frame with an information field that exceeds the maximum established length.

Table 8-6. Q.922 Statistics (Frame Relay Logical Port) (Continued)




Monitoring Frame Relay Logical PortsViewing RLMI Service Name Bindings

The View Service Name dialog box appears (Figure 8-5). For a description of the attributes, see the Frame Relay Services Configuration Guide for CBX 3500, CBX 500, and B-STDX 9000.

Figure 8-5. View Service Name Dialog Box (Frame Relay)


The View Service Name dialog box closes.


Viewing Multicast DLCIs


Viewing Multicast DLCIs

To view the configured attributes for a Multicast DLCI:


2. Expand the logical port for which you want to view a Multicast DLCI.

3. Expand the Multicast DLCI class node.

4. Right-click on the multicast DLCI, and select View from the popup menu.

The View Multicast DLCI dialog box appears. (Figure 8-6). For a description of the attributes, see the Frame Relay Services Configuration Guide for CBX 3500, CBX 500, and B-STDX 9000.

Figure 8-6. View Multicast DLCI Dialog Box


The View Multicast DLCI dialog box closes.



Monitoring Frame Relay Logical PortsViewing Management DLCIs

Viewing Management DLCIs

To view the configured attributes for a Management DLCI:


2. Expand the logical port for which you want to view a Management DLCI.

3. Expand the Mgmt DLCI class node.

4. Right-click on the management DLCI and select View from the popup menu.

The View Management DLCI dialog box appears. (Figure 8-7). For a description of the attributes, see the Frame Relay Services Configuration Guide for CBX 3500, CBX 500, and B-STDX 9000.

Figure 8-7. View Management DLCI Dialog Box


The View Management DLCI dialog box closes.



9

Monitoring IP

This chapter describes how to retrieve status information about various Lucent IP objects. This chapter includes:

• “Displaying IP Objects” on page 9-2

• “Viewing IP Object Attributes” on page 9-10

• “Viewing IP Object Operational Status” on page 9-11

• “Viewing IP Object Summary Statistics” on page 9-17

• “Viewing IP VPNs” on page 9-32

• “Viewing IP Network Resources Assigned to a Specific IP VPN” on page 9-33

For more information on IP Services, see the IP Services Configuration Guide for CBX 3500, CBX 500, and B-STDX 9000.



Monitoring IPDisplaying IP Objects

Displaying IP Objects

This section describes how to display each type of IP object. This section includes:

• A listing of all the IP objects and a reference to the procedure that describes how to display each object (“Overview of Procedures” on page 9-2).

• The procedures that describe how to display each type of IP object (“Procedure for Displaying IP Objects” on page 9-3).

Overview of Procedures

Table 9-1 lists the IP objects and the procedure that describes how to display that type of object.

Table 9-1. IP Objects

To locate these IP objects... Refer to this procedure ...

BGP Parameter “Displaying BGP Objects” on page 9-4

BGP Neighbor “Displaying BGP Objects” on page 9-4

BGP Aggregates “Displaying BGP Objects” on page 9-4

BGP Peer Group “Displaying BGP Objects” on page 9-4

DLCI(Frame Relay only)

“Displaying IP Logical Port Objects” on page 9-8

Forward Policy “Displaying IP Services Objects” on page 9-3

IP Interface Address “Displaying IP Logical Port Objects” on page 9-8

IP Loopback Address “Displaying IP Services Objects” on page 9-3

IP LPort “Displaying IP Logical Ports” on page 9-7

IP Pkt Filter “Displaying IP Services Objects” on page 9-3

IP Network Access Filter “Displaying Route Policy Objects” on page 9-6

IP Network Filter “Displaying Route Policy Objects” on page 9-6

IP Route Map “Displaying Route Policy Objects” on page 9-6

IP Server “Displaying IP Servers” on page 9-7

IP Static Route “Displaying IP Services Objects” on page 9-3

LSPs “Displaying LSPs” on page 9-10

OSPF Interface “Displaying IP Interface Address Objects” on page 9-9

Beta Draft ConfidentialMonitoring IP



Procedure for Displaying IP Objects

This section describes how to display IP objects. This section includes:

• “Displaying IP Services Objects” on page 9-3

• “Displaying BGP Objects” on page 9-4

• “Displaying OSPF Objects” on page 9-5

• “Displaying Route Policy Objects” on page 9-6

• “Displaying IP Servers” on page 9-7

• “Displaying IP Logical Ports” on page 9-7

• “Displaying IP Logical Port Objects” on page 9-8

• “Displaying IP Interface Address Objects” on page 9-9

• “Displaying LSPs” on page 9-10

Displaying IP Services Objects

To display objects that are under the IP Services node:


OSPF Neighbor “Displaying OSPF Objects” on page 9-5

OSPF Area Aggregate “Displaying OSPF Objects” on page 9-5

OSPF Virtual Link “Displaying OSPF Objects” on page 9-5

OSPF Router ID “Displaying OSPF Objects” on page 9-5

OSPF External Route Aggregation

“Displaying OSPF Objects” on page 9-5

RIP “Displaying IP Interface Address Objects” on page 9-9

Static ARP Entries “Displaying IP Services Objects” on page 9-3

VPI/VCI(ATM only)

“Displaying IP Logical Port Objects” on page 9-8

VPN Cloud Interface(If VPN is other than public)

“Displaying IP Services Objects” on page 9-3

Table 9-1. IP Objects (Continued)

To locate these IP objects... Refer to this procedure ...




Figure 9-1. IP Services Class Nodes

2. Expand the IP Services class node.

The class nodes are displayed for the following:

• Forward Policy

• IP Loopback Addresses

• IP Pkt Filter

• Static ARP Entries

• IP Static Route

3. Expand the class node for the type of object you want to list.

Figure 9-1 shows the Forward Policy class node expanded.

Displaying BGP Objects

To display the Border Gateway Protocol (BGP) objects:





Figure 9-2. BGP Objects


3. Expand the BGP class node.


• BGP Parameter

• BGP Neighbor

• BGP Aggregates

• BGP Peer Group


Displaying OSPF Objects

To display the OSPF objects:





Figure 9-3. OSPF Objects


3. Expand the OSPF class node.


• OSPF Neighbor

• OSPF Area Aggregates

• OSPF Virtual Link

• OSPF Router ID

• OSPF External Route Aggregation


Displaying Route Policy Objects

To display the Route Policy objects:


Figure 9-4. Route Policy Objects




2. Expand the Route Policy node.


• IP Network Filter

• IP Network Access Filter

• IP Route Map


Displaying IP Servers

To display IP Servers:




Figure 9-5. Modules on a Switch

3. Expand the module to which the IP Server belongs.

4. Expand the IP Server class node.

Displaying IP Logical Ports

To display the IP logical ports:

1. Display the logical ports on the switch, module, or physical port (see “Displaying Logical Ports” on page 6-1).

2. Expand the logical port (Figure 9-6) to which the IP logical ports belong.




Figure 9-6. IP Logical Port

3. Expand the IP LPort class node.

Displaying IP Logical Port Objects

To display the objects that belong to an IP logical port:


2. Expand the logical port (Figure 9-7) to which the IP logical ports belong.

Figure 9-7. IP Logical Port Objects

3. Expand the IP LPort class node.

4. Expand the IP LPort.


• IP Interface Address

• VPI/VCI (ATM only)

• DLCI (Frame Relay only)





Displaying PPP IP Logical Port Objects


2. Expand the logical port (Figure 9-8) to which the PPP IP logical ports belong.

Figure 9-8. PPP IP Logical Port

3. Expand the IP Lport class node under PPP Logical Port.

4. Open the desired PPP IP Lport instance.

Displaying IP Interface Address Objects

To display the objects that belong to an IP interface address:


2. Expand the logical port (Figure 9-9).

Figure 9-9. IP Interface Address Objects

3. Expand the IP Lport class node.

4. Expand the IP LPort to which the interface addresses belong.



Monitoring IPViewing IP Object Attributes

5. Expand the IP Interface Address class node.


• OSPF Interface

• RIP


Displaying LSPs

To display the label switched path (LSPs) that belong to a network:

1. In the Network tab, expand the Network class node (Figure 9-10).

Figure 9-10. LSPs Under a Network

2. Expand the network that contains the trunks.

3. Expand the LSPs class node.

Viewing IP Object Attributes

To view the configured attributes for an IP object:

1. Display the IP object (see “Displaying IP Objects” on page 9-2).

2. Right-click on the object and select View from the popup menu.

The view dialog box appears for the object. For a description of the attributes, see the IP Services Configuration Guide for CBX 3500, CBX 500, and B-STDX 9000.


Viewing IP Object Operational Status



This section describes how to view the operational status for IP objects. This section includes the following:

• “Before You Begin” on page 9-11

• “Viewing BGP Operational Information” on page 9-11

• “Viewing Point-to-Point LSP Operational Information” on page 9-12

• “Viewing OSPF Operational Information” on page 9-16

Before You Begin

You cannot view operational information for an object if you have set the switch to Unmanaged. The switch must be set to Manage.



Viewing BGP Operational Information

To view operational information for a BGP object:

1. Display the BGP object (see “Displaying BGP Objects” on page 9-4).

2. Expand the BGP object for which you want to view operational information.

3. Right-click on the BGP object and select Oper Info from the popup menu.

The Operational Information dialog box appears for the BGP object (Figure 9-11).

Table 9-2 describes the Operational Information dialog box information for BGP objects.



Monitoring IPViewing IP Object Operational Status

Figure 9-11. BGP Parameters Operational Information Dialog Box



The Operational Status dialog box closes.

Viewing Point-to-Point LSP Operational Information

To view operational information for an LSP:

1. Display the LSPs (see “Displaying LSPs” on page 9-10).

2. Right-click on the LSP and select Oper Info from the popup menu.

The Operational Information dialog box appears for the LSP (Figure 9-12).

Table 9-3 describes the Operational Information dialog box fields for LSPs.

Table 9-4 describes the point-to-point LSP connection failure reasons in alphabetical order. Failure reasons are displayed in the Fail Reason field.

Table 9-2. BGP Operational Information Dialog Box

Field Description

Name Displays the witch name and location on the network tree.

Type Displays the type of switch.

ID Displays the switch IP address.

Route Reflector Indicates if this switch is a route reflector, sending or reflecting received route information to all internal neighbors.




Figure 9-12. View Point-to-Point LSP Connection Operational Information Dialog Box

Table 9-3. View Point-to-Point LSP Connection Operational Information Fields

Field Displays...

End The connection endpoints.

Switch Name The name of switch 1 and switch 2.

Type The switch type for each switch listed.

IP Address The IP address for each switch listed.

Group ID The group identifier for each switch listed.

Managed State The managed state for each switch listed.

General Operational Information

LSP Name The name of the point-to-point LSP (label switch path).

Oper Info Up or Down to indicate the current operational status of a selected point-to-point connection.

User Defined Path Indicator for using a defined path:

Yes – The point-to-point connection uses a user-defined path.

No – The path uses the point-to-point connection that is automatically defined by the Virtual Network Navigator (VNN).




Fail Reason None if there is no failure, or displays the failure reason that is reported by the switch to the NMS. Table 9-11 displays a list of possible fail reasons.

Failed Node Indicator for failed node:

No Failed Node – There is no failure.

A Node ID value – There is a failure in the displayed node ID.

Failed Port Indicator for failed port:

No failed port – There is no failure.

Logical Port Interface Number – The number that identifies a logical port interface (that point-to-point LSPs use to access the switch) in the event of a failure.

Point-to-Point LSP Actual Path

The actual path for a selected point-to-point LSP connection.

Hop Count The number of hops in the path for a selected point-to-point LSP connection.

Table 9-4. Point-to-Point LSP Connection Failure Reasons

Failure Reason Description

AbrNoAltOption The defined path and alternate path failed at the area border router.

ADD RVC VNN could not add a reassembly virtual circuit (RVC).

ATM FR LSP is cell-only and the port is frame.

Confirm Timeout The confirm timer has expired.

Dead Hello packets are not being received.

Disable The point-to-point LSP is disabled.

FR ATM LSP is frame-only and the port is cell.

Grooming A better path exists in the network.

Illegal Port The port cannot support the LSP signal.

Impure path There is a shorter mixed (cell/frame) path.

IN Act An inactive trunk was found.

Table 9-3. View Point-to-Point LSP Connection Operational Information Fields (Continued)

Field Displays...




Invalid Trunk An invalid trunk was found in the path.

ip routed OSPF found a better IP-routed path.

Max Port The port number exceeds the maximum.

MGT Only There can be only a management trunk in the path.

Multi 9000 all 9000 cannot be a cell-only transit node.

No bandwidth There is a bandwidth allocation failure.

No Path The route lookup yielded no valid path.

No Port The port does not exist.

No resource There is a resource failure.

NO RIDS There are no more RIDs available at this node.

Node type Node type identification in progress. This is a normal condition.

None There is no failure condition.

OPTIPTROOT The OPTimum trunk border node cannot be a root for a point-to-point LSP.

OPTITRNSPTVPI The OPTimum trunk transit node Multipoint-to-Point Tunnel (MPT) VPI is not available. Check configuration to ensure that a VPI is properly configured.

Path Clear There is an OSPF Path Clear condition.

Path Registering There has been a failure to register a path with OSPF.

PTPDISABLE Point-to-point LSPs are disabled at the switch.

Receiver died The Reassembly Virtual Circuit (RVC) died.

Route Lookup There is a route lookup failure.

TD Change The tleaf td changed.

Tpcalling VNN detected an LSP port calling error.

Tpdead There is a dead LSP port.

Trunk Down There is a trunk down.

Unknown The error condition that the switch reported does not match any of the error conditions in this table.

Table 9-4. Point-to-Point LSP Connection Failure Reasons (Continued)








Viewing OSPF Operational Information

To view operational information for an OSPF object:

1. Display the OSPF object (see “Displaying OSPF Objects” on page 9-5).

2. Expand the OSPF object for which you want to view operational information.

3. Right-click on the OSPF object and select Oper Info from the popup menu

The Operational dialog box appears for the OSPF object (Figure 9-13).

Table 9-5 describes the Operational Status dialog box information for OSPF objects.

Vcalling VNN detected a circuit endpoint calling error.

VCC Allocate VNN could not allocate a VCC.

VCEXHAUST There are no more VC entries left to be allocated. VC entries are used during call signaling for each VC along the path. There is a fixed amount of resources. Once these resources are allocated, LSPs are unable to set up.

Vcmgr suspended LSPs are disabled.

VPC Allocate VNN could not allocate a virtual path connection (VPC).

VPICHANGE The OPTimum trunk has a configured conflicting VPI.

Table 9-4. Point-to-Point LSP Connection Failure Reasons (Continued)



Viewing IP Object Summary Statistics


Figure 9-13. Operational Status Dialog Box





This section describes how to monitor IP statistics. This section includes:

• “Viewing RIP Summary Statistics” on page 9-18

• “Viewing IP Logical Port Summary Statistics” on page 9-19

• “Viewing IP Logical Port RSVP-TE Statistics” on page 9-21

Table 9-5. OSPF Operational Status Dialog Box Elements

Element Description

IP VPN Name Displays the name of the IP VPN.

OSPF Interface Operational Status

Displays the type of OSPF interface.

Designated Router Displays the IP address of the designated router for this interface.

Backup Designated Router

Displays the IP address of the designated backup router for this interface.

Number of Events Displays the number of events on this interface.



Monitoring IPViewing IP Object Summary Statistics

• “Viewing Point-to-Point LSP Summary Statistics” on page 9-23

• “Viewing Fast Ethernet Logical Port Summary Statistics” on page 9-28

Viewing RIP Summary Statistics

To view Routing Information Protocol (RIP) summary statistics:

1. Display the RIP objects (see “Displaying IP Interface Address Objects” on page 9-9).

2. Expand the RIP for which you want to view summary statistics.


The RIP Statistics Monitoring dialog box appears (Figure 9-14). Table 9-6 describes the statistics.

Figure 9-14. RIP Statistics Monitoring Dialog Box

Table 9-6. RIP Statistics


General

Number of Sent Updates The number of triggered RIP updates sent from this interface. This counter does not include full updates that were sent containing new information.

Number of Received Bad Routes

The number of routes (in valid RIP packets) that were ignored for any reason (for example, an unknown address family or an invalid metric).




Viewing IP Logical Port Summary Statistics

To view IP logical port summary statistics:

1. Display the IP logical port (see “Displaying IP Logical Ports” on page 9-7).

2. Expand the IP logical port for which you want to view summary statistics.


The IP LPort Statistics Monitoring dialog box appears (Figure 9-15).

Figure 9-15. IP LPort Statistics Monitoring Dialog Box

Table 9-7 describes the IP LPort statistics.

Number of Received Bad Packets

The number of RIP response packets received by the RIP process that were discarded for any reason (for example, a version 0 packet or an unknown command type).

Interface Status The status of the RIP logical port interface.

Table 9-6. RIP Statistics (Continued)


Table 9-7. IP LPort Statistics


Number of Octets The number of octets received since the last reset.

Number of Unicast Packets The number of unicast packets received since the last reset.




Number of Non Unicast Packets

The number of nonunicast packets received since the last reset.


The number of packets (frames) received and discarded since the last reset.

Number of Packet Errors The number of packet errors received since the last reset.

Throughput Bits per Second

The total number of bits received and transmitted each second.

Logical Port Utilization (%)

The amount of traffic queued for transmission on a logical port as a percentage of the committed information rate (CIR). This statistic does not measure the amount of bandwidth of the logical port. For this reason, the displayed value can exceed 100%.

Number of Fragmented Inbound Packets

The number of received IP packets that were fragmented because the packet size was greater than the transmit Maximum Transit Unit (MTU) size.

Number of Unreachable Inbound Packets

The number of inbound packets that had a destination unreachable condition. The router had no route to the IP destination indicated by the Destination Address (DA) in the IP packet.

Number of Exceeded TTL Inbound Packets

The number of inbound packets that had a Time-to-Live (TTL) Exceeded condition. This counter is decremented at each hop. If the counter equals zero, the packet is discarded. The purpose of TTL is to prevent packets from endlessly circulating on the network.

Number of Fault Parameters Inbound Packets

The number of inbound packets that had a Parameter Errors condition. A parameter error is any value in the header that either appears incorrectly or cannot be interpreted.

Number of Unknown Protocol Inbound Packets

The number of unknown protocol inbound packets. This counter does not apply to traffic that passes through the router (or Lucent switch). Instead, it applies to traffic destined for any IP entity (such as a router or an end station). This counter is incremented when the IP protocol stack has no packet destination (because there is no IP entity that is interested in this protocol).

Packets accepted by an IP Filter

The number of packets that arrived at the port with inbound/outbound IP filters and were accepted because the IP filter matched the packet and specified acceptance of the packet as a result of the match.

Table 9-7. IP LPort Statistics (Continued)





Viewing PPP IP Logical Port Statistics

To view PPP IP logical port summary statistics:

1. Display the PPP IP logical port (see “Displaying PPP IP Logical Port Objects” on page 9-9).

2. Expand the PPP IP logical port for which you want to view summary statistics.


The PPP IP Lport Statistics dialog box is displayed. For a description of this dialog box and fields, see Figure 9-15 on page 9-19.

Viewing IP Logical Port RSVP-TE Statistics

To view IP logical port RSVP-TE statistics:

1. Display the IP logical port (see “Displaying IP Logical Ports” on page 9-7).

2. Expand the IP logical port for which you want to view summary statistics.

3. Expand the RSVP-TE node, and expand the RSVP-TE instance.


The IP LPort RSVP-TE Statistics dialog box (Figure 9-16) is displayed.

Packets rejected by an IP Filter

The number of packets that arrived at the port with inbound/outbound IP filters and were rejected because the IP filter matched the packet and specified rejection of the packet as a result of the match.

Packets traced by an IP Filter

The number of packets that arrived at the port with inbound/outbound IP filters and were traced because the IP filter matched the packet and specified packet tracing as a result of the match.

Length of Output Packet Queue

The length of the output packet queue, in packets.

Table 9-7. IP LPort Statistics (Continued)





Figure 9-16. IP LPort RSVP-TE Statistics

Table 9-8 describes the IP LPort RSVP-TE statistics.

Table 9-8. IP LPort RSVP-TE Statistics


Path Number of PATH messages transmitted and received on this interface.

Number of Reservation Number of RESV messages transmitted and received on this interface.

Number of Path Tear Number of Path Tear messages transmitted and received on this interface.

Number of Path Error Number of Path Error messages transmitted and received on this interface.

Number of Reservation Tear

Number of RESV Tear messages transmitted and received on this interface.

Number of Reservation Error

Number of RESV Error messages transmitted and received on this interface.

Number of Confirmed Reservation

Number of RESV Confirmation messages transmitted and received on this interface.

Number of Summary Refresh

Number of Summary Refresh messages transmitted and received on this interface.

Number of Acknowledgement

Number of ACK (and/or NACK) messages transmitted and received on this interface.




Viewing Point-to-Point LSP Summary Statistics

To view Point-to-Point LSP summary statistics:

1. Display the LSPs (see “Displaying LSPs” on page 9-10).

2. Expand the LSP for which you want to view summary statistics.

3. Right-click on the Monitoring node and select Start from the popup menu.

The Point-to-Point LSP Statistics Monitoring dialog box appears (Figure 9-17).

Figure 9-17. Point to Point LSP Statistics Monitoring Dialog Box


Table 9-9. Point to Point LSP Statistics



Total Octets Rx The total number of octets received from the originating endpoint (A) to the destination endpoint (B) and from the destination endpoint to the originating endpoint since the last reset.

Total Octets Tx The total number of octets transmitted from the originating endpoint (A) to the destination endpoint (B) and from the destination endpoint to the originating endpoint since the last reset.




Viewing BGP Peer Summary Statistics

To view BGP peer summary statistics:

1. Display the BGP peers (see “Displaying BGP Objects” on page 9-4).

2. Expand the BGP peer for which you want to view summary statistics.


The BGP Peer Monitoring Statistics dialog box appears (Figure 9-18).

Throughput

Bits Per Second Rx The bits per second received from the originating endpoint (A) to the destination endpoint (B) and from the destination endpoint to the originating endpoint since the last reset.

Bits Per Second Tx The bits per second transmitted from the originating endpoint (A) to the destination endpoint (B) and from the destination endpoint to the originating endpoint since the last reset.

Circuit Utilization Rx

The amount of traffic queued for transmission on a circuit as a percentage of the PCR. For this reason the value displayed in Circuit Utilization Rx can exceed 100%.

Circuit Utilization Tx

The amount of traffic queued for transmission on a circuit as a percentage of the PCR. For this reason the value displayed in Circuit Utilization Tx can exceed 100%.

Table 9-9. Point to Point LSP Statistics (Continued)





Figure 9-18. BGP Peer Statistics Monitoring Dialog Box


Table 9-11 lists the error codes related to BGP.

Table 9-10. BGP Peer Statistics



Number of Update Messages

The number of BGP update messages this connection transmitted or received.

Total Number of Messages

The total number of messages this connection transmitted to or from a remote peer.

BGP Peer Local Port The local port that establishes a TCP connection between the BGP peers.

BGP Peer Local Addr

The local IP address of this entry’s BGP connection.

BGP Peer Negotiated Version

The negotiated version of BGP running between two peers.




BGP Peer State One of the BGP peer connection states:

Idle – BGP waits for the operator to initiate a start event. BGP initiates a TCP connection and listens for a connection, which may be initiated by a peer. After BGP is initialized, it advances to the Connect state.

Connect – BGP waits for TCP to complete. If the TCP connection completes, BGP advances to the Opensent state. If the TCP connection fails, BGP advances to the Active state.

Active – BGP tries to establish peering through a TCP connection. If the connection is successful, BGP transmits an Open message and advances to the Opensent stage. If the TCP connection retry timer expires, BGP restarts the connection timer and retreats to the Connect state.

Opensent – BGP sends an Open message to its peer and waits for an Open message. After the message is received, the message is checked for correctness, which includes checks for router ID, BGP version, AS number, and hold timer. If errors occur, the system sends an error notification message and returns to the Idle state. If there are no errors, BGP sends keep-alive messages.

Openconfirm – BGP waits for keep-alive messages from its peer. If the message is received, the session advances to the Established state.

Established – The final state of the BGP connection state.

BGP Peer Identifier The 4-byte unsigned integer that indicates the sender’s ID.

BGP Peer Update Elapsed Time (in seconds)

The number of seconds since this peer received the last BGP update message.

BGP Peer FSM Established Time (in seconds)

A timer (in seconds) for the peer Established state; one of the following:

• Duration that this peer has been in the Established state.

• Duration since this peer was last in the Established state.

The timer is set to zero when you configure a new peer or you boot the router.

BGP Peer FSM Established Transitions

The total number of times the BGP Finite State Machine (FSM) transitioned into the Established state. The BGP FSM is a process that BGP goes through to determine its connection state.

Table 9-10. BGP Peer Statistics (Continued)





BGP Peer Last Error The last error code seen by this peer. An error code is part of the notification message that is sent whenever an error occurs. See Table 9-11 for more information.

BGP Peer Remote AS

The remote AS number.

BGP Peer Remote Port

The remote port that establishes a TCP connection between the BGP peers.

Table 9-11. BGP Error Codes

Last Error Code Last Error Subcode

1 – Message Header Error 1 – Connection Not Synchronized

2 – Bad Message Length

3 – Bad Message Type

2 – OPEN Message Error 1 – Unsupported Version Number

2 – Bad Peer AS

3 – Bad BGP Identifier

4 – Unsupported Optional Parameter

5 – Authentication Failure

6 – Unacceptable Hold Timer

Table 9-10. BGP Peer Statistics (Continued)





Viewing Fast Ethernet Logical Port Summary Statistics

To view Fast Ethernet logical port summary statistics:


2. Expand the Fast Ethernet logical port for which you want to view summary statistics.


The LPort Monitoring Statistics dialog box appears (Figure 9-19). Table 9-12 describes the statistics for Fast Ethernet modules.

3 – UPDATE Message Error 1 – Malformed Attribute List

2 – Unrecognized Well-Known Attribute

3 – Missing Well-Known Attribute

4 – Attribute Flags Error

5 – Attribute Length Error

6 – Invalid Origin Attribute

7 – AS Routing Loop

8 – Invalid NEXT_HOP Attribute

9 – Optional Attribute Error

10 – Invalid Network Field

11 – Malformed AS_path

4 – Hold Timer Expired Not applicable

5 – Finite State Machine Error (for errors detected by the FSM)

Not applicable

6 – Cease (for fatal errors in addition to those already listed)

Not applicable

Table 9-11. BGP Error Codes (Continued)

Last Error Code Last Error Subcode




Figure 9-19. Fast Ethernet Logical Port Monitoring Statistics Dialog Box

Table 9-12. Fast Ethernet Logical Port Monitoring Statistics



Number of Unicast Packets Cumulative transmitted and received statistics for unicast packets.

Number of Non-unicast Packets

Cumulative transmitted and received statistics for non-unicast packets.

General Statistics




Dot3 Stats Internal Mac Transmit Errors

The number of frames for which transmission on a particular interface fails due to an internal Media Access Control (MAC) sublayer transmission error.

Dot3 Stats Excessive Collisions

The number of frames for which transmission on a particular interface fails due to excessive collisions.

Dot3 Stats Late Collisions The number of frames for which transmission on a particular interface fails due to late collisions.

Dot3 Stats Deferred Transmissions

The number of frames for which transmission on a particular interface fails because of deferred transmission.

SQE Test Errors The number of times that the SQE TEST ERROR message is generated by the PLS sublayer.

Multiple Collision Frames The number of successfully transmitted frames for which transmission is inhibited by more than one collision.

Single Collision Frames The number of successfully transmitted frames for which transmission is inhibited by a single collision.

FCS Errors The number of frames received that are an integral number of octets (bytes) in length but do not pass the Frame Check Sequence (FCS) check.

Alignment Errors The number of received frames that are not an integral number of octets in length and that do not pass the FCS check.

Queue Length Transmitted The transmit queue length, in number of packets, for each priority transmit queue.

Physical Address The Ethernet address of the interface.

If MTU Displays the maximum transfer unit (MTU) size of the packet that can be sent over this Lport.

Lport Congestion Rate The congestion rate for the logical port.

Lport Absolutely Congested State Count

Number of times that the logical port’s congestion state has changed from Severe to Absolute since the last reset.

Lport Severely Congested State Count

Number of times that the logical port’s congestion state has changed from Mild to Severe since the last reset.

Table 9-12. Fast Ethernet Logical Port Monitoring Statistics (Continued)





Lport Error Type The type of error last detected on the Ethernet interface:

1 – Frame too short.2 – Abort.3 – Residual bit.4 – CRC Error.5 – Receive long.6 – Receive overrun.7 – Transmit underrun.8 – Unknown error.

Lport Error Time The amount of time the Ethernet interface had been up when the last error was detected.

Lport QP4 Length The transmit queue length, in number of packets, for Priority 4 transmissions.




Congestion State One of the following congestion states for the logical port: Normal (1), Mild (2), Severe (3), or Absolute (4).

ThroughPut

Unicast Packets Per Sec The number of unicast packets transmitted and received per second.

Non Unicast Packets Per Sec

The number of non-unicast packets transmitted and received per second.

Table 9-12. Fast Ethernet Logical Port Monitoring Statistics (Continued)




Monitoring IPViewing IP VPNs

Viewing IP VPNs

To view IP VPNs:


Figure 9-20. VPNs Node

2. Expand the network.

3. Expand the VPNs class node.

4. Right-click on the IP VPN whose attributes you want to view, and select View from the popup menu.

The View VPN dialog box appears (Figure 9-21).

Figure 9-21. View VPN Dialog Box (IP VPN)

5. Select the appropriate tab for the attributes you want to view. For a description of the tabs and fields that are available, see the IP Services Configuration Guide for CBX 3500, CBX 500, and B-STDX 9000.

6. When you have completed viewing the IP VPN attributes, choose Close.

The View VPN dialog box closes.


Viewing IP Network Resources Assigned to a Specific IP VPN


Viewing IP Network Resources Assigned to a Specific IP VPN

Overview

Once an IP VPN has been created (see the IP Services Configuration Guide for CBX 3500, CBX 500, and B-STDX 9000), you can choose to see only the IP network resources that belong to a specific IP VPN by entering the context of that IP VPN.

Entering the Context of an IP VPN

To enter the context of an IP VPN:

1. Right-click on the switch and select Select IP VPN Name from the popup menu (see “Displaying a Switch Tab in the Navigation Panel” on page 2-6).

The Select IP VPN Name dialog box appears (Figure 9-22).

Figure 9-22. Select IP VPN Name Dialog Box

2. Select an IP VPN.

3. Choose OK to save the changes and close the dialog box.

Monitoring operations you perform will now only display IP network resources if they belong to the selected IP VPN. The IP VPN name appears in the IP VPN Context field in the Status Bar at the bottom of the Navis EMS-CBGX window (Figure 9-23).



Monitoring IPViewing IP Network Resources Assigned to a Specific IP VPN

Figure 9-23. Navis EMS-CBGX Main Window



10

Monitoring Trunks

This chapter describes how to monitor trunks for a specified switch. In a Lucent network, a trunk is a permanent link between logical port endpoints on two separate Lucent switches. A trunk represents a permanent link from one Lucent switch to another Lucent switch, for transporting user traffic, routing updates, network management pools, and other management traffic.

Lucent supports several types of trunks, including:

• ATM Direct Line — A dedicated line between the switches. Data is transferred using ATM protocols.

• ATM OPTimum Cell/Frame — A connection between the switches through a switched public data network (PDN). Data is transferred using ATM protocols.

• Frame Relay Direct Line — A dedicated line between the switches. Data is transferred using Frame Relay protocols.

• Frame Relay OPTimum PVC — A connection between the switches through a switched PDN. Data is transferred using Frame Relay protocols.

• Multilink Frame Relay (MLFR) — A connection (similar to a Frame Relay Direct Line trunk), that combines up to 32 separate Frame Relay trunks into a single, aggregate Frame Relay trunk. The aggregate trunk is called a bundle; the individual trunks that make up the bundle are called members. Each bundle is configured as a logical port, and each member is also configured as a logical port.

• SMDS OPTimum — A connection between the switches through an SMDS network.



Monitoring TrunksDisplaying Trunks

Displaying Trunks

This section describes different methods for displaying trunks. This section includes:

• “Displaying the Trunks That Belong to a Network” on page 10-2

• “Displaying the Trunks That Belong to a Switch” on page 10-2

• “Displaying the Trunks That Belong to a Logical Port” on page 10-3

Displaying the Trunks That Belong to a Network

To display the trunks that belong to a network:


Figure 10-1. Trunk Nodes Under a Network

2. Expand the network that contains the trunks.

3. Expand the Trunks class node.

Displaying the Trunks That Belong to a Switch

To display the trunks that belong to a switch:


Beta Draft ConfidentialMonitoring Trunks

Displaying Trunks


Figure 10-2. Trunk Nodes Under a Switch


Displaying the Trunks That Belong to a Logical Port

To display the trunks that belong to a logical port:

1. Display the logical port (see “Displaying Logical Ports” on page 6-1).

2. Expand the logical port that the trunk belongs to (Figure 10-3).

Figure 10-3. Trunk Nodes Under a Logical Port




Monitoring TrunksViewing Trunk Attributes

Viewing Trunk Attributes

To view the configured attributes for a trunk:

1. Display the trunk (see “Displaying Trunks” on page 10-2).

2. Right-click on the trunk and select View from the popup menu.

The View Trunk dialog box appears (Figure 10-4).

Figure 10-4. View Trunk Dialog Box

3. Select the appropriate tab for the attributes you want to view. For a description of the attributes, see the ATM Services Configuration Guide for CBX 3500, CBX 500, GX 550, and B-STDX 9000 or the Frame Relay Services Configuration Guide for CBX 3500, CBX 500, and B-STDX 9000.


The View Trunk dialog box closes.


Viewing Trunk Operational Information



This section describes how to view operational status for a trunk.

Before You Begin

You cannot view operational information for a trunk if you have set the switch to Unmanaged. The switch must be set to Manage.



To View the Operational Information of a Trunk1. Display the trunk (see “Displaying Trunks” on page 10-2).

2. Right-click on the trunk and select Oper Info from the popup menu.

The View Trunk Operational Information dialog box appears for the trunk (Figure 10-5).

Figure 10-5. View Trunk Operational Information

Table 10-1 describes the View Trunk Operational Information dialog box fields.



Monitoring TrunksViewing Trunk Operational Information

Table 10-1. View Trunk Operational Information Dialog Box Fields

Field Description

Trunk Name Displays the name of the trunk.

Trunk Type Displays the trunk type, either Normal, Primary, or Backup.

Trunk Status Displays the current status of the selected trunk. Options include:

• Up – The trunk is up and operational between the two switches.

• Down – The switches cannot establish a communication link.

• Attempt – A switch is attempting to contact another switch but has not yet received a response.

• Init – A one-way communication exists between the two switches.

• Two-way – A bi-directional communication exists between the two switches.

• Exchange Start – The two switches are exchanging network topology.

• Exchange – The two switches are exchanging network topology.

• Loading – The two switches are requesting the most recent link state information.

• Unknown – The NMS cannot communicate with one or both switch endpoints that make up this trunk.

• Backed-up – A primary trunk exists and is ready for backup.

• Defined – A backup trunk is ready for backup.

Trunk Revision Displays the revision of link trunk protocol software at each endpoint.

PVC Manager Revision Displays the PVC manager software revision.

Static Delay Represents the measured one-way delay in units of 100 microseconds. This measurement is taken when the trunk initializes and it is only updated when the trunk changes state from down to up. The static delay value is used in conjunction with the end-to-end delay routing metric to enable you to route circuits over trunks with the lowest end-to-end delay.






The View Trunk Operational Information dialog box closes.

Dynamic Delay Represents the measured one-way delay in units of 100 microseconds. This measurement is made continually on operational trunks. Under most conditions, the dynamic delay value will match the static delay value. However, if some characteristics of the underlying transmission media for the trunk change such that the dynamic delay changes, this value may differ from the static delay.

No. of VCs Displays The total number of PVCs, SVCs, SPVCs, LSPs, and any other type of VC traversing the trunk.

Available Bandwidth Displays the amount of bandwidth, in Kbps, available for circuit configuration and allotment on the selected trunk.

Protection Slot Displays the slot number that holds the protection port for endpoint 1 and endpoint 2.

Protection Port Displays the physical port number of the protection port for endpoint 1 and endpoint 2.

Working Endpoint Status Displays the status of the working endpoint for endpoints 1 and 2.

Protection Endpoint Status Displays the status of the protection endpoint for endpoints 1 and 2.

Table 10-1. View Trunk Operational Information Dialog Box Fields (Continued)

Field Description



Monitoring TrunksViewing Trunks on a Map

Viewing Trunks on a Map

To view the status of trunks with a network map:

1. In the Maps tab, expand the Maps class node (Figure 10-6).

Figure 10-6. Maps Tab

2. Right-click on the map and select Open from the popup menu.

The Network Map View window appears (Figure 10-7).

Table 10-2 describes the color scheme used to identify the status of a trunk connection on the network map.


Viewing Trunks on a Map


Figure 10-7. Network Map View Window

Table 10-2. Trunk Color Status Indicators

Color Status

Red Trunk is down.

Blue Trunk status is Unknown or Unmanaged.

Yellow Trunk connection is marginal.

Green Trunk connection is up.

Beige Trunk is unmanaged.

Gray Trunk is inaccessible.



Monitoring TrunksViewing Trunk Summary Statistics

Viewing Trunk Summary Statistics

To view trunk summary statistics:


2. Expand the trunk for which you want to view summary statistics.


The Trunk Statistics Monitoring dialog box appears. Figure 10-8 shows an example of ATM OPTimum Trunk statistics.

Figure 10-8. Trunk Statistics Monitoring Dialog Box

Table 10-3 describes the statistics. The fields that appear vary, depending on the type of trunk.


Viewing Trunk Summary Statistics


Table 10-3. Trunk Summary Statistics


Number of VC (A) The number of VCs that the trunk supports from endpoint A to B.

Number of VC (B) The number of VCs that the trunk supports from endpoint B to A.


Number of Cells/Packets The total number of cells/packets transmitted from one endpoint to the other.

Throughput

Bits per second The total number of bits per second (bps) transmitted from one endpoint to the other.

Cells/Packets per second The total number of cells/packets per second (pps) transmitted from one endpoint to the other.

Utilization (%) The percentage of trunk speed that is being used from one endpoint to the other.

Priority Bandwidth

Bandwidth Priority 0-15 The bandwidth priority (0-15), where zero is the highest priority and 15 is the lowest priority. In the event of network problems, the trunk will favor VCs assigned a higher bandwidth priority (for example, zero) over VCs assigned a lower bandwidth priority (for example, 15).

Number of VCs The number of VCs in each priority bandwidth class from one endpoint to the other.

Allocated BW The amount of virtual bandwidth in Kilobits per second allocated for each priority bandwidth class from one endpoint to the other. Virtual bandwidth is bandwidth that is available for circuit configuration and allotment on the selected trunk.



Monitoring TrunksViewing PVC Usage

Viewing PVC Usage

To view all the PVCs and Redirect PVCs passing over a particular trunk:

1. Display the trunk (see “Displaying the Trunks That Belong to a Network” on page 10-2).

2. Right-click on the trunk and select Show All PVCs from the drop-down menu. The Show All PVCs on Trunk dialog box will be displayed (Figure 10-9).

Figure 10-9. Show All PVCs on Trunk Dialog Box

The Show All PVCs dialog box lists all PVCs on the selected trunk and displays the following information in Table 10-4 for each PVC.

Table 10-4. Show All PVCs on Trunk Dialog Box Fields

Field Description

Name Name of the PVC, redirect PVC, or offnet circuit.

Admin Status Status of the circuit (up or down)

Alias Name Name assigned to the circuit as an alias. (optional)

Switch 1 Name of the switch on which endpoint 1 resides.

Endpoint 1 Name of the first logical port endpoint of the circuit.

Switch 2 Name of the switch on which endpoint 2 resides.

Endpoint 2 Name of the second logical port endpoint of the circuit.

Endpoint 1 Lport Type Type of logical port on endpoint 1 (ATM UNI DCE, ATM UNI DTE, etc.)

Endpoint 2 Lport Type Type of logical port on endpoint 2 (ATM UNI DCE, ATM UNI DTE, etc.)

Layer2 vpn If applicable, the name of the Layer 2 VPN with which this circuit is associated.

Customer The name of the customer.


Running OAM Loopback Tests on ATM Over MPLS Trunks


Running OAM Loopback Tests on ATM Over MPLS Trunks

This section describes OAM Loopback tests on ATM over MPLS (ATMoMPLS) trunks.

Overview

Each ATM over MPLS (ATMoMPLS) trunk can have up to 32 virtual path connections, which use four different QoS LSP paths in the Multi_Protocol Label Switching (MPLS) core. You can use the OAM loopback function to generate cells for the purposes of verifying connectivity across the four paths.

To Run the OAM Loopback Test on an ATMoMPLS Trunks

To run an OAM loopback test on an ATMoMPLS trunk:


2. Right-click on the trunk and select OAM from the popup menu.

The Trunk OAM dialog box appears (Figure 10-10).

Figure 10-10. Trunk OAM Dialog Box

3. Configure the OAM loopback test fields as described in Table 10-5.

Template Whether a circuit is a template or not. If it is designated as a template, “yes” will be displayed. If not, then “-” will be displayed in this field.

Table 10-4. Show All PVCs on Trunk Dialog Box Fields (Continued)

Field Description



Monitoring TrunksRunning OAM Loopback Tests on ATM Over MPLS Trunks


Table 10-6 describes the trunk OAM loopback test results.


6. Choose Close.

The Trunk OAM dialog box closes.

Table 10-5. Trunk OAM Dialog Box Fields


Loopback Source Choose either Endpoint 1 or Endpoint 2 as the source of the loopback signal.

Loopback Direction

Only one loopback direction is available for an ATMoMPLS trunk. Across the Partner Network enables you to send the OAM cells over the trunk onto the connected Juniper MPLS router.

Loopback Type Only one loopback type is available for an ATMoMPLS trunk: Across Partner Network. This sends a signal across the network to the circuit endpoint.

Number Of OAM Cells To Send

Specify the number of OAM cells to send. Initially, send a minimal number of cells; for example, 10 cells.

QoS Class From the pull-down list, select the kind of QoS class that is applied to the loopback cells. Options are: CBR, VBR (Real Time), VBR (Non Real TIme), or UBR.

Table 10-6. Trunk OAM Dialog Box Loopback Test Results

Result Description

Response Time (msec)

Displays the lowest, the average, and the highest response times to the loopback signal.

Responses Received

The number of responses that were received during the OAM test.

Responses Timed-Out

The number of responses that timed-out during the OAM test.


Filtering Information Displayed Based on the VPN or Customer


Filtering Information Displayed Based on the VPN or Customer

To limit the logical port, circuit, and trunk information that is displayed to only the information that pertains to a specific layer 2 VPN or customer:


Figure 10-11. Networks

2. Right-click on the network and select Select L2 VPN/VNN Customer from the popup menu.

The Select Layer2 Customer/VPN dialog box appears (Figure 10-12).

Figure 10-12. Select Layer2 Customer/VPN View Dialog Box

3. In the Current Selection field, select one of the following from the pull-down list:

• Layer2 VPN — Lets you select a VPN from the Layer2 VPN Name list.

• Customer — Lets you select a customer from the Customer Name list.

4. In the Customer Name or Layer2 VPN field, select an entry.


The Select Layer2 Customer/VPN View dialog box closes. Only information that applies to the selected layer 2 VPN or customer will be displayed for logical ports, circuits, or trunks.



Monitoring TrunksViewing VNN Customers

Viewing VNN Customers

To view information for a Virtual Network Navigator (VNN) customer:


Figure 10-13. VNN Customers Node


3. Expand the VNN Customers class node.

4. Right-click on the VNN customer and select View from the popup menu.

The View Customer dialog box appears (Figure 10-14).

Figure 10-14. View Customer Dialog Box

Table 10-7 describes the fields in the View Customer dialog box.


Viewing Layer2 VPNs


5. When you have completed viewing the VNN customer attributes, choose Close.

The View Customer dialog box closes.

Viewing Layer2 VPNs

To view information for a Layer2 VPN:


Figure 10-15. VPNs Node


3. Expand the VPNs class node.

4. Right-click on the VPN and select View from the popup menu.

The View VPN dialog box appears (Figure 10-16).

Table 10-8 describes the fields in the View VPN dialog box.

Table 10-7. View Customer Dialog Box Fields

Field Displays...

Name The customer name.

Customer ID The customer ID.

Phone # The phone number for the customer.

Contact Information Information for the customer contact.

Comments Any comments about this customer.

VPN Name The VNN name to which this customer belongs.



Monitoring TrunksViewing Layer2 VPNs

Figure 10-16. View VPN Dialog Box

5. When you have completed viewing the VPN attributes, choose Close.

The View VPN dialog box closes.

Table 10-8. View VPN Dialog Box Fields

Field Displays...

Type Layer2.

Name The name for the VPN.

Comments Any comments about this VPN.

Set PNNI Policy Routing Attributes

Whether PNNI policy routing attributes are set. This is a check box.

Ne-NSC The policy Network Entity NSC advertised for this VPN.

Rp-NSC The Resource Partition NSC advertised for this VPN, if available.

Is Public NeNSC? Whether this Ne-NSC is a public Ne-NSC.


Viewing VNN OSPF Loopback Addresses


Viewing VNN OSPF Loopback Addresses

To view information for a VNN OSPF loopback address:


Figure 10-17. VNN Loopback Addresses Node

2. Expand the VNN class node.

3. Expand the VNN Loopback Addresses class node.

4. Right-click on the VNN loopback address and select View from the popup menu.

The View VNN Loopback Address dialog box appears (Figure 10-18).

Table 10-9 describes the fields in the View VNN Loopback Address dialog box.

Figure 10-18. View VNN Loopback Address Dialog Box



Monitoring TrunksViewing VNN OSPF Area Aggregates

5. When you have completed viewing the VNN loopback address attributes, choose Close.

The View VNN Loopback Address dialog box closes.

Viewing VNN OSPF Area Aggregates

To view information for a VNN OSPF area aggregate:


Figure 10-19. VNN Area Aggregates Node


3. Expand the VNN Area Aggregates class node.

4. Right-click on the VNN area aggregate and select View from the popup menu.

The View VNN OSPF Area Aggregate dialog box appears (Figure 10-20).

Table 10-9. View VNN Loopback Address Dialog Box Fields

Field Description

Loopback Address

The loopback IP address (for example, 152.148.30.5).

Area ID The ID (x.x.x.x) of the area in which the node is located. Area 0.0.0.0 is the network backbone. Areas are collections of networks, hosts, and routers. The area ID identifies the area.

Note: Area 1 is reserved for Lucent switches.


Viewing VNN OSPF Area Aggregates


Figure 10-20. View VNN OSPF Area Aggregate Dialog Box

Table 10-10 describes the fields in the View VNN OSPF Area Aggregate dialog box.

5. When you have completed viewing the VNN OSPF area aggregate attributes, choose Close.

The View VNN OSPF Area Aggregate dialog box closes.

Table 10-10. View VNN OSPF Area Aggregate Dialog Box Fields

Field Description

Area ID The ID (x.x.x.x) of the area in which the IP address range is located. Area 0.0.0.0 is the network backbone.

Areas are collections of networks, hosts, and routers; the area ID identifies this area.

LSDB Type The link state database (LSDB) type to which this address aggregate applies; for VNN, it is always Summary.

Summary – Area border routers generate summary link advertisements, which describe inter-area routes (routes between areas) to networks.

Network The IP address of the network or subnetwork that encompasses the range of addresses that you want to advertise.

Net Mask The subnetwork mask that pertains to the network or subnetwork.

Advertise Matching

Indicator for the advertising of subnetworks:

A selected check box indicates that subnetworks included by the ranges trigger the advertisement of the indicated aggregate.

A cleared check box indicates that subnetworks are not advertised outside of the area.



Monitoring TrunksViewing VNN OSPF Virtual Links

Viewing VNN OSPF Virtual Links

To view VNN OSPF virtual links:


Figure 10-21. VNN Virtual Links Node


3. Expand the VNN Virtual Links class node.

4. Right-click on the VNN virtual link and select View from the popup menu.

The View VNN OSPF Virtual Link dialog box appears (Figure 10-22).

Figure 10-22. View VNN OSPF Virtual Link Dialog Box

Table 10-11 describes the fields in the View VNN OSPF Virtual Link dialog box.

Table 10-11. View VNN OSPF Virtual Link Dialog Box Fields

Field Description

Area ID The area ID (x.x.x.x) of the transit area, which is the non-backbone area that the virtual link traverses to connect to the backbone area. This ID cannot be 0.0.0.0 (the area ID of the backbone area).

Areas are collections of networks, hosts, and routers. The area ID identifies this area.

Neighbor Router ID The VNN OSPF router ID of the switch (that is, the neighbor) on the other end of the virtual link. For the VNN instance of OSPF, the router ID is the same as the internal switch ID.


Viewing VNN OSPF External Routes Aggregates


5. When you have completed viewing the VNN OSPF virtual link attributes, choose Close.

The View VNN OSPF Virtual Link dialog box closes.

Viewing VNN OSPF External Routes Aggregates

To view VNN OSPF external routes aggregates:


Figure 10-23. VNN External Route Aggregation Node


3. Expand the VNN External Route Aggregation class node.

4. Right-click on the VNN external route aggregation and select View from the popup menu.

The View VNN External Route Aggregation dialog box appears (Figure 10-24).

Figure 10-24. View VNN External Route Aggregation Dialog Box

Table 10-12 describes the fields in the View VNN External Route Aggregation dialog box.



Monitoring TrunksViewing VNN OSPF External Routes Aggregates

Table 10-12. View VNN External Route Aggregation Dialog Box Fields

Field Description

Network The IP address of the net or subnet.

Net Mask The subnet mask for the net or subnet.

External Metric Type

Indicator for the admin cost calculation of the external network:

Type 1 – The total cost is equal to the cost specified by the preferred routing table entry for the autonomous system border router (ASBR) or forwarding address plus the cost specified in the link state advertisement LSA.

Type 2 – The total cost is equal to the cost specified by the link state component of the route plus the total cost of the

Advertise Matching

Indicator for advertising net/mask combination:

A selected check box indicates that the net/mask you specified for the given area is “leaked” (that is, advertised), making it available to the rest of the network.

A cleared check box indicates the net/mask for the given area is hidden.

Beta Draft ConfidentialMonitoring TrunksViewing PNNI Links


Viewing PNNI Links

To display the PNNI links that belong to a switch:


Figure 10-25. PNNI Links Under a Switch

2. Expand the PNNI Link class node.

3. To view the active PVCs that pass through a specific PNNI link:

a. Expand the PNNI link.

The PVCs class node appears under the PNNI link.

b. Expand the PVCs class node.

The active PVCs that pass through the PNNI link appear.



Monitoring TrunksViewing PNNI Links



11

Circuit Attributes

This chapter describes how to view the configured attributes for circuits.


• “Displaying Circuits” on page 11-2

• “Categories of Circuit Attributes” on page 11-4

• “Viewing Circuit Attributes” on page 11-6

• “Viewing SVC Attributes” on page 11-7



Circuit AttributesDisplaying Circuits

Displaying Circuits

To display the circuits that belong to a switch or to a logical port:

1. Expand the switch (“Displaying a Switch Tab in the Navigation Panel” on page 2-6) or the logical port (“Displaying Logical Ports” on page 6-1) that the circuit is on.

2. Expand the Circuits class node (Figure 11-1 shows the Circuits class node under a switch).

Figure 11-1. Circuits Node

3. Expand the class node for the type of circuit you want to display:

• PVCs (Figure 11-1)

• Redirect PVCs (Figure 11-2)

• Offnet Circuits (Figure 11-3)

• PMP Roots (Figure 11-4)

• PMP Leafs (Figure 11-5)

• Offnet PMP Roots (Figure 11-6)

• Offnet PMP Leaf (Figure 11-7)

• SPVCs (Figure 11-8)

Figure 11-2. Redirect PVCs Node

Figure 11-3. Offnet Circuits Node

Beta Draft ConfidentialCircuit AttributesDisplaying Circuits


Figure 11-4. PMP Roots Node

Figure 11-5. PMP Leafs Node

Figure 11-6. Offnet PMP Roots Node

Figure 11-7. Offnet PMP Leafs Node

Figure 11-8. SPVC Node



Circuit AttributesCategories of Circuit Attributes

Categories of Circuit Attributes

Circuit attributes vary, depending on the type of circuit you are monitoring.

Table 11-1 lists the categories of circuit attributes that you can view, the type of circuit to which the attribute categories apply, the service that supports the attributes, and the procedure for viewing the attributes.

Table 11-1. Circuit Attributes Categories

Attribute Category Circuit Type Supported Service Supported Procedure for Viewing Attributes

Administrative Point-to-Point PVCs

Redirect PVCs

Point-to-Multipoint PVCs

Point-to-Point Offnet PVCs

Point-to-Multipoint Offnet PVCs

Point-to-Point SPVCs

Point-to-Multipoint SPVCs

ATM and Frame Relay

“Viewing Circuit Attributes” on page 11-6

Traffic Type Point-to-Point PVCs

Redirect PVCs

Point-to-Multipoint PVCs (roots only)


Point-to-Multipoint Offnet PVCs (roots only)

Point-to-Point SPVCs

Point-to-Multipoint SPVCs (roots only)

ATM and Frame Relay


User Preference Point-to-Point PVCs

Redirect PVCs


ATM and Frame Relay


Traffic Management Point-to-Point PVCs

Redirect PVCs


ATM only “Viewing Circuit Attributes” on page 11-6

Beta Draft ConfidentialCircuit Attributes

Categories of Circuit Attributes


NDC Point-to-Point PVCs

Redirect PVCs



ATM (at least one endpoint)


Accounting Point-to-Point PVCs

Redirect PVCs




ATM and Frame Relay


FRF.5 Point-to-Point Offnet PVCs Frame Relay (at least one endpoint)


Path Point-to-Point PVCs


ATM and Frame Relay


Table 11-1. Circuit Attributes Categories (Continued)

Attribute Category Circuit Type Supported Service Supported Procedure for Viewing Attributes



Circuit AttributesViewing Circuit Attributes

Viewing Circuit Attributes

To view the configured attributes for a circuit:

1. Display the circuit whose attributes you want to view (see “Displaying Circuits” on page 11-2).

2. Right-click on the circuit and select View from the popup menu.

The view PVC dialog box appears (Figure 11-9).

Figure 11-9. View PVC Dialog Box

3. Select the appropriate tab for the attributes you want to view. For a description of the tabs and fields that are available, see the ATM Services Configuration Guide for CBX 3500, CBX 500, GX 550, and B-STDX 9000 or the Frame Relay Services Configuration Guide for CBX 3500, CBX 500, and B-STDX 9000.


The view circuit dialog box closes.


Viewing SVC Attributes



This section describes how to view the attributes for SVC objects in a Lucent network. You can check the status of configured SVC parameters and view active and failed SVCs. For more information on ATM SVCs, see the ATM Services Configuration Guide for CBX 3500, CBX 500, GX 550, and B-STDX 9000.

Viewing All Node Prefixes

Node prefixes apply to all logical ports on the switch and are used for routing aggregation. To view all node prefix formats on a switch:


Figure 11-10. Node Prefixes Node

2. Expand the Node Prefixes class node.

3. Right-click on the node prefix and select View from the popup menu.

The View SVC Node Prefix dialog box appears (Figure 11-11). For a description of the attributes, see the ATM Services Configuration Guide for CBX 3500, CBX 500, GX 550, and B-STDX 9000.

Figure 11-11. View SVC Node Prefix Dialog Box



Circuit AttributesViewing SVC Attributes

4. When you have completed viewing the Node Prefix attributes, choose Close.

The View SVC Node Prefix dialog box closes.

Viewing All Port Prefixes

SVC port prefixes define how calls are routed to a logical port. To view all port prefixes defined for a selected logical port or switch:

1. Perform one of the following:

• In the switch tab (see “Displaying a Switch Tab in the Navigation Panel” on page 2-6), expand the switch.

• Display the logical port (see “Displaying Logical Ports” on page 6-1), and expand the logical port.

2. Expand the SVC class node under the switch or under the logical port.

Figure 11-12 shows the SVC class node expanded under the switch.

Figure 11-12. Port Prefixes Node

3. Expand the Port Prefixes class node.

4. Right-click on the port prefix and select View from the popup menu.

The View SVC Port Prefix dialog box appears (Figure 11-13). For a description of the attributes, see the ATM Services Configuration Guide for CBX 3500, CBX 500, GX 550, and B-STDX 9000.




Figure 11-13. View SVC Port Prefix Dialog Box

5. When you have completed viewing the Port Prefix attributes, choose Close.

The View SVC Port Prefix dialog box closes.

Viewing All Port Addresses

SVC addresses can be configured for all logical ports on a physical port if the device attached to the physical port does not support address registration. To view all SVC port addresses:






Figure 11-14. Port Addresses Node

3. Expand the Port Addresses class node.

4. Right-click on the port address and select View from the popup menu.




The View SVC Port Address dialog box appears (Figure 11-15). For a description of the attributes, see the ATM Services Configuration Guide for CBX 3500, CBX 500, GX 550, and B-STDX 9000.

Figure 11-15. View SVC Port Address Dialog Box

5. When you have completed viewing the Port Address attributes, choose Close.

The View SVC Port Address dialog box closes.

Viewing All Port User Parts

The user part of an ATM End System Address (AESA) is used for DTE (user) ports on a Lucent switch. The user part is used to construct the address table on the DCE device attached to the public side of the UNI. When the DCE broadcasts its network prefixes, the DTE responds by sending its configured user parts; this enables the DCE to build the ILMI address table. For more information, see the ATM Services Configuration Guide for CBX 3500, CBX 500, GX 550, and B-STDX 9000.

To view all user parts defined for a logical port or switch:









Figure 11-16. User Parts Node

3. Expand the User Parts class node.

4. Right-click on the user part and select View from the popup menu.

The View User Part dialog box appears (Figure 11-17). For a description of the attributes, see the ATM Services Configuration Guide for CBX 3500, CBX 500, GX 550, and B-STDX 9000.

Figure 11-17. View User Part Dialog Box

5. When you have completed viewing the user part attributes, choose Close.

The View User Part dialog box closes.




Viewing All Port Network IDs

Network IDs can be defined for specific logical ports. To view all port network IDs defined for a selected logical port or on a switch:






Figure 11-18. Network IDs Node

3. Expand the Network IDs class node.

4. Right-click on the network ID and select View from the popup menu.

The View Network ID dialog box appears (Figure 11-19). For a description of the attributes, see the ATM Services Configuration Guide for CBX 3500, CBX 500, GX 550, and B-STDX 9000.

Figure 11-19. View Network ID Dialog Box




5. When you have completed viewing the network ID attributes, choose Close.

The View Network ID dialog box closes.

Viewing All Active SVCs

To view a list of active SVCs for a logical port:


2. Expand the logical port for which you want to view active SVCs (Figure 11-20).

Figure 11-20. Active SVCs Node

3. Expand the Active SVCs class node.

The active SVCs for the logical port are listed under the Active SVCs class node.




Viewing Active SVC Attributes

To view the attributes for an active SVCs:

1. Display the active SVCs for the logical port (see “Viewing All Active SVCs” on page 11-13).

2. Select the SVC whose attributes you want to view.

In the Details Panel, the time at which the connection was established appears in the Creation Time column (Figure 11-21).

Figure 11-21. Active SVC in Details Panel

3. Right-click on the SVC, and select View from the popup menu.

The Active SVC Detailed Call Attributes dialog box appears (Figure 11-22).

Table 11-2 describes the fields in the Destination tab.

Figure 11-22. Active SVC Detailed Call Attributes Dialog Box




Table 11-2. Active SVC Detailed Call Attributes: Destination Tab Fields

Field Description

Switch Name The name of the switch that the SVC is traversing.

PPort Id The number of the physical port that the SVC is traversing.

VPI (ATM only) The ID of the virtual path between the SVC endpoints.

This number is equivalent to the VPI value in the ATM cell header and is used to route cell traffic. See the ATM Services Configuration Guide for CBX 3500, CBX 500, GX 550, and B-STDX 9000 for more information.

VCI (ATM only) The ID of the virtual channel between the SVC endpoints.

This number is equivalent to the VCI value in the ATM cell header.

See the ATM Services Configuration Guide for CBX 3500, CBX 500, GX 550, and B-STDX 9000 for more information.

DLCI (Frame Relay only) The unique Data Link Connection Identifier (DLCI) that the selected logical port uses to identify the SVC. Each endpoint uses a DLCI to recognize the SVC. Typically, the DLCI has local significance only. For example, one end of the SVC may use a DLCI of 120 to recognize the SVC, while the other end of the SVC may use DLCI 40 to recognize the SVC.

See the Frame Relay Services Configuration Guide for CBX 3500, CBX 500, and B-STDX 9000 for more information.

Slot ID The slot number of the IOM used by the logical port that the SVC is traversing.

LPort Name The name of the logical port that the SVC is traversing.

Calling Party: Number The entire SVC calling party address.

Calling Party: Format The SVC calling party address type.

Called Party: Number The entire SVC called party address.

Called Party: Format The SVC called party address type.




4. Select another tab in the Active SVC Detailed Call Attributes dialog box to view other SVC attributes. Table 11-3 describes the tabs.

Actual Path The path the SVC took from the source to the destination and the hop count.

If the path is over Private Network-to-Network Interface (PNNI) links, the path is displayed from that PNNI Lport to the destination. For this reason, if an ATM SVC traverses multiple peer groups, or traverses both PNNI and OSPF links, the path from that PNNI Lport is displayed. And if the active SVCs are viewed on the AINI Lport, the actual path till that AINI node is displayed and not beyond.

Table 11-3. Active SVC Detailed Call Attributes: Bearer Capability, QoS Parameters, Traffic Parameters, ABR, and AINI Tabs

Tab Displays...

Bearer Capability

The contents of the broadband bearer capability information element from the SETUP or ADD PARTY message. For more information about ATM broadband bearer capabilities, see Appendix D, “Signalled QoS, BBC, ATC, and BEI Service Category Mappings.”

QoS Parameters

The configured forward and reverse QoS class: either CBR, VBR-RT, VBR-NRT, or Unspecified. For more information about ATM QoS parameters, see Appendix D, “Signalled QoS, BBC, ATC, and BEI Service Category Mappings.” and the ATM Services Configuration Guide for CBX 3500, CBX 500, GX 550, and B-STDX 9000.

The signalled QoS parameters are displayed only. Under some conditions, the signalled QoS received by the switch may be different from the actual QoS in the switch.

Traffic Parameters

The forward and reverse ATM traffic descriptors. For more information about ATM traffic descriptors, see Appendix D, “Signalled QoS, BBC, ATC, and BEI Service Category Mappings.” and the ATM Services Configuration Guide for CBX 3500, CBX 500, GX 550, and B-STDX 9000.

Table 11-2. Active SVC Detailed Call Attributes: Destination Tab Fields (Continued)

Field Description




ABR (ATM only)

The configured forward and reverse ABR parameters for the SVC:

FRMRTT – The ABR fixed resource management (RM) round trip time (in microseconds) for this SVC.

ICR (cells/sec) – The initial cell rate (ICR) is the rate (in cells per second) at which the source may send.

RIF – The Rate Increase Factor (RIF) controls how much the cell transmission rate may increase upon receipt of an RM cell. RIF is a power of two ranging from 1/32768 to 1.

RDF – The Rate Decrease Factor (RDF) controls the decrease in the cell transmission rate. RDF is a power of two ranging from 1/32768 to 1.

TBE (cells) – The transient buffer exposure (TBE) is the negotiated number of cells that the network would like to limit the source to sending during start-up periods – before the first RM cell returns. Values range from 0 to 16,777,215.

NRM – The maximum number of cells a source may send for each forward RM cell. Normal response mode (Nrm) is a power of 2 that ranges from 2 to 256.

MRM – Controls allocation of bandwidth between forward RM cells, backward RM cells, and data cells. MRM is a constant fixed at 2.

CDF – The cutoff decrease factor (CDF) controls the decrease in ACR (available cell rate) associated with CRM (missing RM-cell count).

ADTF – The ACR decrease time factor (ADTF) is the time (in seconds) allowed between sending RM cells before the rate is decreased to ICR.

Note: For more information about ABR parameters, see the ATM Services Configuration Guide for CBX 3500, CBX 500, GX 550, and B-STDX 9000 and the ATM Forum Traffic Management Specification, Version 4.0. You can access the ATM Forum Web site at: http://www.atmforum.com.

Table 11-3. Active SVC Detailed Call Attributes: Bearer Capability, QoS Parameters, Traffic Parameters, ABR, and AINI Tabs (Continued)

Tab Displays...




5. When you are done viewing the SVC details, choose Close.

The Active SVC Detailed Call Attributes dialog box closes.

Viewing All ILMI Addresses

To view dynamic address (that is, ILMI) information for a logical port:


2. Right-click on the instance node for the LPort for which you want to view ILMI address information, and select Show ILMI Addresses from the popup menu.

The Show ILMI Address List dialog box appears (Figure 11-23).

AINI (AINI/UNI 4.0 Lports only)

The NCCI type and NCCI value associated with the call on the AINI/UNI4.0 Lports.

Preceding AINI/UNI4.0 endpoint:

NCCI Type:

Local - Saved in local, if it is assigned locally or received in setup message.

Remote - Saved in Remote, if it is received in connect message.

NCCI Value:

Local - Saved the locally assigned NCCI value if not received in setup message. Saved the received value if it is present in setup message. If the action is set to discard, then it saved the NCCI value only if it is received in setup message.

Remote - NCCI value received in connect message

Succeeding AINI/UNI4.0 end point:

NCCI Type:

Local: Saved in local, only when it is locally assigned.

Remote: Saved in remote, only when it is received in setup message.

NCCI Value:

Local: Saved the locally assigned NCCI value irrespective of whether it is received in setup message or not.

Remote: Saved the NCCI value received in setup message.

Table 11-3. Active SVC Detailed Call Attributes: Bearer Capability, QoS Parameters, Traffic Parameters, ABR, and AINI Tabs (Continued)

Tab Displays...




Figure 11-23. Show ILMI Address List Dialog Box

Table 11-4 describes the Show ILMI Address List dialog box fields.

3. When you are done viewing the ILMI address information, choose Close.

The Show ILMI Address List dialog box closes.

Viewing SVC Failed Calls

To view a list of failed SVCs for a logical port:

Table 11-4. Show ILMI Address List Dialog Box Fields

Field Description

LPort Name The name of the logical port that the SVC is traversing.

Service Type Displays the service type assigned to the logical port.

LPort Type Displays the logical port type.

Slot Id The slot number of the IOM used by the logical port that the SVC is traversing.

Interface Id A number assigned by the NMS to the logical port.

PPort Id The physical port for which this logical port is configured.

ILMI Admin Status Indicates whether ILMI is configured on the logical port.

Address Type The type of the ILMI address.

Numbering Plan The ILMI address format.

ILMI Address The dynamic ILMI address.





2. Expand the logical port for which you want to view failed SVCs (Figure 11-24).

Figure 11-24. Failed SVCs Node

3. Expand the Failed SVCs class node.

The failed SVCs for the logical port are listed under the Failed SVCs class node.




Viewing SVC Failed-Call Attributes

To view information for a failed SVC:

1. Display the failed SVCs for the logical port (see “Viewing SVC Failed Calls” on page 11-19).

2. Select the SVC whose attributes you want to view.

In the Details Panel, the time at which the connection terminated appears in the Termination Time column (Figure 11-25).

Figure 11-25. Failed SVC in Details Panel

3. Right-click on the SVC whose attributes you want to view, and select View from the popup menu.

The Detailed Failed SVC Attributes dialog box appears (Figure 11-26).

Figure 11-26. Detailed Failed SVC Attributes Dialog Box

Table 11-5 describes the SVC call attributes in the Failure Info tab.




4. Select another tab in the Detailed Failed SVC Attributes dialog box to view other SVC attributes. Table 11-6 describes the other tabs in the Detailed Failed SVC Attribute dialog box.

Table 11-5. Detailed Failed SVC Attributes: Failure Info Tab Fields

Field Description

Failure Code The standard ATM Forum UNI signaling cause codes for the failure.

Failure Cause A message describing this failure. The failure cause text is based on the standard ATM Forum UNI signaling cause codes. See Chapter C, “Using SVC Failure Information” for more information.

Diagnostics Field The hexadecimal and ASCII values from the release message diagnostic field. This information may help diagnose certain types of SVC failures.

Repeat Information The dates and times of the failure’s first occurrence and most recent occurrence. Also displays the number of consecutive times this same failure has occurred on this port.

Termination Direction and PDU The type of signaling PDU used to terminate the call and whether it was sent from or received by the logical port.

Failure Location Gives the location of the failure: the Switch Name, Slot Id, PPort Id, LPort Name, Interface Id, and End Reference.

Calling Party: Number The entire SVC calling party address.

Calling Party: Format The SVC calling party address type.

Called Party: Number The entire SVC called party address.

Called Party: Format The SVC called party address type.




Table 11-6. Detailed Failed SVC Attributes: Bearer Capability, QoS Parameters, Traffic Parameters, ABR, and AINI Tabs

Tab Displays...

Bearer Capability

The contents of the broadband bearer capability information element from the SETUP or ADD PARTY message. For more information about ATM broadband bearer capabilities, see Appendix D, “Signalled QoS, BBC, ATC, and BEI Service Category Mappings.”

QoS Parameters

The configured forward and reverse QoS class: either CBR, VBR-RT, VBR-NRT, or Unspecified. For more information about ATM QoS parameters, see Chapter D, “Signalled QoS, BBC, ATC, and BEI Service Category Mappings” and the ATM Services Configuration Guide for CBX 3500, CBX 500, GX 550, and B-STDX 9000.

The signalled QoS parameters are displayed only. Under some conditions, the signalled QoS received by the switch may be different from the actual QoS in the switch.

Traffic Parameters

The forward and reverse ATM traffic descriptors. For more information about ATM traffic descriptors, see Chapter D, “Signalled QoS, BBC, ATC, and BEI Service Category Mappings” and the ATM Services Configuration Guide for CBX 3500, CBX 500, GX 550, and B-STDX 9000.




ABR (ATM only)

The configured forward and reverse ABR parameters for the SVC:

FRMRTT – The ABR fixed RM round trip time (in microseconds) for this SVC.

ICR (cells/sec) – ICR is the rate (in cells per second) at which the source may send.

RIF – RIF controls how much the cell transmission rate may increase upon receipt of an RM cell. RIF is a power of two ranging from 1/32768 to 1.

RDF – RDF controls the decrease in the cell transmission rate. RDF is a power of two ranging from 1/32768 to 1.

TBE (cells) – TBE is the negotiated number of cells that the network would like to limit the source to sending during start-up periods – before the first RM cell returns. Values range from 0 to 16,777,215.

NRM – The maximum number of cells a source may send for each forward RM cell. NRM is a power of 2 that ranges from 2 to 256.

MRM – Controls allocation of bandwidth between forward RM cells, backward RM cells, and data cells. MRM is a constant fixed at 2.

CDF – CDF controls the decrease in available cell rate (ACR) associated with CRM (missing RM-cell count).

ADTF – The ACR decrease time factor (ADTF) is the time (in seconds) allowed between sending RM cells before the rate is decreased to ICR.

Note: For more information about ABR parameters, see the ATM Services Configuration Guide for CBX 3500, CBX 500, GX 550, and B-STDX 9000 and the ATM Forum Traffic Management Specification, Version 4.0. You can access the ATM Forum Web site at: http://www.atmforum.com.

Table 11-6. Detailed Failed SVC Attributes: Bearer Capability, QoS Parameters, Traffic Parameters, ABR, and AINI Tabs (Continued)

Tab Displays...




5. When you are done viewing the SVC failure details, choose Close.

The Detailed Failed SVC Attributes dialog box closes.

Viewing Closed User Groups

To view the Closed User Groups (CUGs) in a network:


AINI (AINI/UNI 4.0 Lports only)

The NCCI type and NCCI value associated with the call on the AINI/UNI4.0 Lports.

Preceding the AINI/UNI4.0 endpoint:

NCCI Type:

Local - Saved in local, if it is assigned locally or received in setup message.

Remote - Saved in Remote, if it is received in connect message.

NCCI Value:

Local - Saved the locally assigned NCCI value if not received in setup message. Saved the received value if it is present in setup message. If the action is set to discard, then it saved the NCCI value only if it is received in setup message.

Remote - NCCI value received in connect message

Succeeding the AINI/UNI4.0 end point:

NCCI Type:

Local: Saved in local, only when it is locally assigned.

Remote: Saved in remote, only when it is received in setup message.

NCCI Value:

Local: Saved the locally assigned NCCI value irrespective of whether it is received in setup message or not.

Remote: Saved the NCCI value received in setup message.

Table 11-6. Detailed Failed SVC Attributes: Bearer Capability, QoS Parameters, Traffic Parameters, ABR, and AINI Tabs (Continued)

Tab Displays...




Figure 11-27. CUGs Node

2. Expand the network that contains the CUGs.

3. Expand the SVC Security class node.

4. Expand the CUGs class node.

5. Right-click on the CUG whose attributes you want to view, and select View from the popup menu.

The View CUG dialog box appears (Figure 11-28). For a description of the attributes, see the ATM Services Configuration Guide for CBX 3500, CBX 500, GX 550, and B-STDX 9000.




Figure 11-28. View CUG Dialog Box

6. When you have completed viewing the CUG attributes, choose Close.

The View CUG dialog box closes.

Viewing Closed User Group Members

To view the CUG members in a network:





Figure 11-29. CUG Members Node

2. Expand the network that contains the CUG members.


4. Expand the CUG Members class node.

5. Right-click on the CUG member whose attributes you want to view, and select View from the popup menu.

The View CUG Member dialog box appears (Figure 11-30). For a description of the attributes, see the ATM Services Configuration Guide for CBX 3500, CBX 500, GX 550, and B-STDX 9000.

Figure 11-30. View CUG Member Dialog Box

6. When you have completed viewing the CUG member attributes, choose Close.

The View CUG Member dialog box closes.

Viewing Port Security Screens

To view port security screens:





Figure 11-31. Security Screens Node

2. Expand the network that contains the security screens.


4. Expand the Security Screens class node.

5. Right-click on the security screen whose attributes you want to view, and select View from the popup menu.

The View Security Screen dialog box appears (Figure 11-32). For a description of the attributes, see the ATM Services Configuration Guide for CBX 3500, CBX 500, GX 550, and B-STDX 9000.

Figure 11-32. View Security Screen Dialog Box

6. When you have completed viewing the security screen attributes, choose Close.

The View Security Screen dialog box closes.






12

Monitoring ATM Circuits

This chapter describes how to monitor ATM circuits. Lucent switches support ATM communications over the following types of circuits:

• Point-to-Point Permanent Virtual Circuits (PVCs)

• Redirect PVCs

• Offnet PVCs

• Point-to-Multipoint (PMP) PVCs

• PMP Offnet PVCs

• Point-to-Point Soft PVCs (SPVCs)

• PMP SPVCs

• Switched Virtual Circuits (SVCs)

• PMP SVCs



Monitoring ATM CircuitsViewing Circuit Operational Status

Viewing Circuit Operational Status

This section describes how to view operational status for an ATM circuit.

Before You Begin

You cannot view operational information for a circuit if you have set the switch to Unmanaged. The switch must be set to Manage.



To View the Operational Status of an ATM Circuit1. Display the circuit (see “Displaying Circuits” on page 11-2).

2. Right-click on the circuit and select Oper Info from the popup menu.

The PVC Operational information dialog box appears (Figure 12-1).

The operational information dialog box fields are described in the following tables:

• PVCs: Table 12-1 on page 12-3

• Redirect PVCs: Table 12-2 on page 12-5

• Offnet circuits (including PWE3 Offnet Circuits): Table 12-3 on page 12-7

• PMP circuit leaves: Table 12-4 on page 12-8

• Offnet PMP circuit leaves: Table 12-5 on page 12-9

• SPVCs: Table 12-6 on page 12-9

• PMP circuit soft leaves: Table 12-7 on page 12-10

The operational information dialog box for the PWE3 tab (for PVCs only) is shown in Figure 12-2 on page 12-15. The PWE3 operational information is described in Table 12-9 on page 12-16.

Beta Draft ConfidentialMonitoring ATM Circuits



Figure 12-1. PVC Operational Information Dialog Box

Table 12-8 on page 12-11 describes the endpoint fail reasons that can appear.

Table 12-1. PVC Operational Information Dialog Box Fields

Field Displays...

Operational Status The current operational status of the selected circuit. Messages include:

• Active – The circuit is operational through the network end-to-end.

• Inactive – The circuit is not operational. Check the Failure Reason at Endpoint 1 or Endpoint 2 fields for possible explanations.

• Unknown – Navis EMS-CBGX cannot reach the higher-numbered node for status. (If the circuit is an intra-switch PVC, then Navis EMS-CBGX cannot reach the highest-numbered logical port.)

• Invalid – The circuit definition is not found in the higher-numbered node. You may need to save the circuit definition; it may also be necessary to PRAM synch the host card.




PVC Delay The duration (in microseconds) before the network initiates call clearing after a circuit goes down.

A value of zero causes the network to initiate call clearing immediately, and this can trigger the switchover between a working redirect PVC endpoint and its primary or secondary endpoint. Increasing the value can minimize the PVC redirection that results from temporary data terminal equipment (DTE) state changes.

Failure Reason at Endpoint 1 and 2

Displays the reason a selected circuit failed (if any) for a given endpoint. For CBX 500/3500 and GX 550 endpoints, also displays the failed LPort name, node ID, and IfIndex.

See Table 12-8 on page 12-11 for information about operational status codes.

Actual Path: Trunk The actual trunk path that is selected for this circuit to get to its destination. (If the Connection Trace button is active, choose the button to display information in the Actual Path fields.)

Actual Path: Switch The actual switches that this circuit traverses to get to its destination.

Hop Count The number of hops in the circuit.


Field Displays...




Table 12-2. Redirect PVC Operational Information Dialog Box Fields

Field Displays...



• Inactive – The circuit is not operational. Check the Failure Reason at Endpoint 1 or Endpoint 2 fields for possible explanations.

• Unknown – Navis EMS-CBGX cannot reach the higher-numbered node for status. (If the circuit is an intra-switch PVC, then Navis EMS-CBGX cannot reach the highest-numbered logical port.)



A value of 0 causes the network to initiate call clearing immediately, and this can trigger the switchover between a working redirect PVC endpoint and its primary or secondary endpoint. Increasing the value can minimize the PVC redirection that results from temporary data terminal equipment (DTE) state changes.

Last Switchover Action The action taken at the most recent switchover. This diagnostic information can include the following resolutions:

• gopri-manual – switched over to primary endpoint, manually.

• gopri-ondemand – switched over to primary endpoint, automatically.

• gosec-manual – switched over to secondary endpoint, manually.

• gosec-ondemand – switched over to secondary endpoint, automatically.

Working Endpoint 2 The endpoint to which the PVC is currently established from the pivot endpoint (Endpoint 1). The working endpoint can be either the primary or the secondary endpoint.




Backup-Up Whether the circuit has a backup circuit (Yes or No).

Failure Reason at Pivot Endpoint

The reason a selected circuit failed (if any) for a the pivot endpoint. For CBX 500/3500 and GX 550 endpoints, also displays the failed LPort name, node ID, and IfIndex.

See Table 12-8 on page 12-11 for information about operational status codes.

Failure Reason at Endpoint 2 (Primary or Secondary)

Displays the reason a selected circuit failed (if any) for the endpoint 2 primary or secondary endpoint. (Choose the Primary or Secondary tab to see the information for that endpoint.)

For CBX 500/3500 and GX 550 endpoints, also displays the failed LPort name, node ID, and IfIndex.

See Table 12-8 on page 12-11 for operational information codes.





Field Displays...




Table 12-3. View Offnet Circuit Operational Information DialogBox Fields

Field Displays...



• Inactive – The circuit is not operational. Check the Failure Reason for Endpoint 1 or Endpoint 2 fields for possible explanations.

• Unknown – The higher-numbered node cannot reached for status.


Failure Reason The reason a selected circuit failed (if any). For CBX 500/3500 and GX 550 endpoints, also displays the failed LPort name, node ID, and IfIndex.








Table 12-4. PMP Leaf Operational Information Dialog Box Fields

Field Displays...




• Unknown – The NMS cannot reach the higher-numbered node for status. (If the circuit is an intra-switch PVC, then the NMS cannot reach the highest-numbered logical port.)


Failure Reason The reason a selected circuit failed (if any). For CBX 500/3500 and GX 550 endpoints, also gives the failed LPort name, node ID, and IfIndex.


Actual Path: Trunk The actual trunk path that is selected for this circuit to get to its destination.






Table 12-5. Offnet Leaf Operational Information Dialog Box Fields

Field Displays...




• Unknown – The NMS cannot reach the higher-numbered node for status. (If the circuit is an intra-switch PVC, then the NMS cannot reach the highest-numbered logical port.)


Failure Reason The reason a selected circuit failed (if any). For CBX 500/3500 and GX 550 endpoints, also gives the failed LPort Name, Node ID, and IfIndex.


Actual Path The actual path that OSPF selected for this circuit to get to its destination.


Table 12-6. View SPVC Operational Information Fields

Field Displays...


• Connected – The circuit is operational through the network end-to-end.

• Failed – An attempt to establish the SPVC has failed. Check the Failure Reason and Failure Diagnostics fields for possible explanations.

• Setup in Progress – An attempt to set up the SPVC is in progress.

• Other – The SPVC is not active.




Failure Reason The reason a selected circuit failed (if applicable).


Failure Diagnostics The information about the cause of the failure (if applicable).



Retry Timer The current value of the retry timer, in seconds. When the timer reaches zero, the switch attempts to establish the SPVC.

Retry Failures The number of failed attempts the switch has made to establish an SPVC since the last reset.


Table 12-7. View PMP SPVC Leaf Operational Information DialogBox Fields

Field Displays...


• Connected – The circuit is operational through the network end-to-end.

• Failed – An attempt to establish the circuit has failed. Check the Failure Reason and Failure Diagnostics fields for possible explanations.

• Setup in Progress – An attempt to set up the circuit is in progress.

• Other – The circuit is not active.

Failure Reason The reason a selected circuit failed (if applicable).


Failure Diagnostics The information about the cause of the failure (if applicable).

Table 12-6. View SPVC Operational Information Fields

Field Displays...






Retry Timer The current value of the retry timer, in seconds, for this connection.

Retry Failures The number of failed attempts the switch has made to establish an SPVC since the last reset.

Hop Count The number of hops in the circuit to reach the destination.

Table 12-8. Inactive PVC Operational Information Codes

Fail Reason Description Solution

Circuit Admin Status is Down

Circuit activity is disabled; the admin status is set to Down.

Reconfigure the circuit’s admin status to Up.

Internal Error: No VC Buffer at [node]

A shortage of virtual circuit buffers exists at the node.

Serious Error! Report problem to the Lucent Technical Assistance Center (TAC).

Not enough bandwidth on trunk at [node]

One of the trunks in the circuit path does not have enough bandwidth to accommodate the circuit.

Reconfigure the circuit to a lower bandwidth or increase the physical or virtual bandwidth of the trunk. You can also add more parallel trunks.

Keep in mind that increasing the physical or virtual trunk bandwidth will temporarily disrupt traffic on the trunk.

Destination node is unreachable at [node]

The destination node is not accessible from the higher numbered node.

Troubleshoot a possible connectivity problem with the unreachable switch.

Table 12-7. View PMP SPVC Leaf Operational Information DialogBox Fields

Field Displays...




Lucent circuit segment call has timed out

Attempts to establish the circuit (PVC) through the network have failed and timed out.

This problem may occur on a defined path where the alternate path option is disabled.

Internal error: No circuit PDU buffer at [node]

A shortage of protocol buffers exists.

Serious Error! Report problem to the Lucent TAC.

OPTimum path flow is blocked at [node]

Data flow through the public data network is temporarily blocked due to the flow-control mechanism.

This condition should correct itself. If the problem persists, check for congestion in the OPTimum path.

Trunk is down at [node]

A trunk line in the circuit path is down.

The circuit automatically reroutes if alternate paths are defined.

UNI/NNI is down at [node, lport]

The UNI or NNI is down at the node/interface number (ifnum).

Verify that the switch is connected to the user device. Display traffic in and out of the port by generating summary statistics.

PVC segments are not ready to receive beyond [lport, node]

(NNI specific problem.) The PVC segments beyond this logical port sent a flow block message stating that it cannot receive data.

A trunk line in the circuit path may be down. Check the status of all PVC segments in the network beyond the logical port noted in the Fail Reason.

Warning: Defined Path is not available. The alternate path is in use. PVC segments are inactive beyond [lport, node]

The caller node cannot be reached through the defined path. This problem may be caused by a connection failure.

Verify the integrity of the trunk that is being used on the defined circuit path. Once the defined path is re-established, the circuit is routed back to the defined path within 20 seconds of availability.

IOP/IOM is down An input/output processor (IOP) or IOM used by the circuit is down.

Check the status of the IOM. See Chapter 2, “Viewing Network, Switch, Module, and Physical Port Details” for more information.

Table 12-8. Inactive PVC Operational Information Codes (Continued)





No PVC Manager PDU msg buffer

The PVC manager has no user message buffer for the protocol data unit (PDU).


Port is not configured

No logical port is configured for use by the PVC.

Configure a logical port for the PVC. See the ATM Services Configuration Guide for CBX 3500, CBX 500, GX 550, and B-STDX 9000 for details.

Mis-configuration Configuration error. Check the PVC attributes. See “Viewing Circuit Attributes” on page 11-6.

SVC setup failed Soft PVC (SPVC) setup failed. Check the SPVC attributes and statistics. See “Viewing Circuit Attributes” on page 11-6 and “Viewing ATM Circuit Summary Statistics” on page 12-34.

Source is in a ‘backup’ condition

The PVC switched over to a backup.

Check PVC attributes and statistics. See “Viewing Circuit Attributes” on page 11-6 and “Viewing ATM Circuit Summary Statistics” on page 12-34.

Source is unknown The PVC source is unknown. Check PVC attributes and statistics. See “Viewing Circuit Attributes” on page 11-6 and “Viewing ATM Circuit Summary Statistics” on page 12-34.

Destination is unknown

The PVC destination is unknown.


Node running incompatible version of switch software exists in circuit path

A switch that is running an incompatible version of software is in the circuit path.

Verify that all switches in the circuit path are running compatible versions of switch software.






SMDS management trunk

The PVC attempted to traverse an SMDS management trunk.

Reroute the PVC so that it does not traverse an SMDS management trunk.

Endpoint never called

The PVC connection was never established.

Check PVC attributes and statistics. See “Viewing Circuit Attributes” on page 11-6 and “Viewing ATM Circuit Summary Statistics” on page 12-34

Both endpoints in ‘backup’

Both PVC endpoints are in a backup condition (that is, they are switching to backup PVCs).


Attempting to route through management trunk

The PVC attempted to traverse a management trunk.

Reroute the PVC so that it does not traverse a management trunk.

Multipoint parent not found

No multipoint circuit parent (that is, the circuit root) was found.

Check multipoint PVC attributes to see if the parent (that is, the circuit root) was defined. See “Viewing Circuit Attributes” on page 11-6.

Route changed during setup

The PVC route failed because it changed during PVC setup.

Verify that the PVC route is stable during PVC setup.

No VPI or VCI is available

No VPI or VCI is available for the ATM PVC.

Configure an available VPI or VCI for the PVC. See the ATM Services Configuration Guide for CBX 3500, CBX 500, GX 550, and B-STDX 9000 for more information.

SVC cleared by user The soft PVC was cleared by the user.

Re-establish the soft PVC connection.

Circuit path registration failed

Problems were encountered during PVC path registration.







Figure 12-2. PWE3 PVC Operational Information Dialog Box

Selected channel cannot be allocated

The ATM channel selected by the PVC cannot be allocated.

Check ATM PVC attributes. See “Viewing Circuit Attributes” on page 11-6.

No available bandwidth in reverse direction

No bandwidth in the reverse direction is available.

Check the PVC configuration to see if sufficient bandwidth is available.

Disrupted due to priority routing

High priority VCI is in the PVC’s path. The PVC is disrupted due to priority routing.

Network congestion or other problems initiated priority-routing algorithms, which disrupted the PVC. This condition should clear as soon as the problems are corrected.

Couldn’t allocate negative priority bandwidth

No negative priority bandwidth could be allocated.

Check the PVC configuration to see if there is sufficient bandwidth available.






Table 12-9. PWE3 PVC Operational Information Dialog Box Fields

3. If the Connection Trace button is active, choose the button to display information in the Actual Path.



The operational information dialog box closes.

Viewing PWE3 Profile Operational Information

To view PWE3 Profile operations information:

1. Expand the switch (“Displaying a Switch Tab in the Navigation Panel” on page 2-6) that the PWE3 Profile is on.

2. Expand the PWE3 Profiles class node.

3. Right-click on a PWE3 Profile instance node and choose Oper Info from the popup menu. The View PWE3 Profile Operational Information dialog box appears (Figure 12-3).

Field Displays...

PW Service Type The type of PWE3 service.

Remote Control Word The remote control word, if applicable, used in some encapsulations.

Remote Concat Cell This field is not applicable.

End Point 1 The InBound Label and OutBound Label for End Point 1.

End Point 2 The InBound Label and OutBound Label for End Point 2.

Failure Reason at Endpoint 1 The failure reason, if applicable.

Failure Reason at Endpoint 1 The failure reason, if applicable.

Actual Path The actual PSN tunnel ID and tunnel name.

Hop Count The number of hops in the tunnel.




Figure 12-3. View PWE3 Profile Operational Information Dialog Box

The fields in this dialog box are described in Table 12-10.

Table 12-10. View PWE3 Profile Operational Information Dialog Box Fields

Field Displays...

ID The numerical identifier for this profile.

Peer Address The IP address for this profile.

Type The type of service connection for this profile.

Owner Specifies if label is allocated statically by user or dynamically using LDP.

Outbound Tunnel ID The five-digit identifier of the outbound tunnel for this profile.

Remote Outbound Tunnel ID The five-digit identifier of the remote outbound tunnel for this profile.

Admin Status The administrative status--Up or Down--of this profile.

Oper Status The operational status of this profile.

Outbound Label The outbound label for this profile.

Inbound Label The inbound label for this profile.



Monitoring ATM CircuitsViewing Enhanced Connection Trace Information




For a description of PWE3 Profiles, see the ATM Services Configuration Guide for CBX 3500, CBX 500, GX 550, and B-STDX 9000.

Viewing Enhanced Connection Trace Information


• “Overview of Enhanced Connection Trace” on page 12-18

• “Running Enhanced Connection Trace on a PVC or SVC” on page 12-20

Overview of Enhanced Connection Trace

The Enhanced Connection Trace feature enables you to determine the logical nodes and logical links along a PVC or SVC path. For each hop on a the circuit, the connection trace returns the switch name and IP address, slot and physical port, interface ID, and VPI/VCI.

You specify the portion of the circuit on which you want to collect Enhanced Connection Trace information. You do this by choosing a source node and a destination node from a list of the nodes on the circuit path.

Enhanced Connection Trace is supported both in Private Network-to-Network Interface (PNNI) routing domains and in combined PNNI/Virtual Network Navigator (VNN) networks.

An example of using Enhanced Connection Trace is to establish a session to tap a particular circuit using the ATAF feature. You would need to know the VPI/VCI value at a particular switch along the path, and the Enhanced Connection Trace feature would give you that information.

To open the View Enhanced Connection Trace Info dialog box for a PVC:

1. Display the PVC (see “Displaying Circuits” on page 11-2).


The PVC Operational Information dialog box appears (Figure 12-1).

3. Choose Enhanced Connection Trace.

The View Enhanced Connection Trace Info dialog box appears (Figure 12-4).


Viewing Enhanced Connection Trace Information


Figure 12-4. View Enhanced Connection Trace Info Dialog Box

4. Continue with “Running Enhanced Connection Trace on a PVC or SVC” on page 12-20.

To open the View Enhanced Connection Trace Info dialog box for an SVC:

1. Display the active SVCs (see “Viewing All Active SVCs” on page 11-13).

2. Right-click on the circuit and select Enhanced Connection Trace from the popup menu.

The View Enhanced Connection Trace Info dialog box appears (Figure 12-4).

3. Continue with “Running Enhanced Connection Trace on a PVC or SVC” on page 12-20.



Monitoring ATM CircuitsViewing Path Trace Information

Running Enhanced Connection Trace on a PVC or SVC

To run Enhanced Connection Trace on a PVC or SVC:

1. In the View Enhanced Connection Trace Info Dialog box (Figure 12-4), select an item in the Connection Trace Information field, and choose the Node A button.

The information for this node appears in the Source Node fields, and this node will be the starting point of the Enhanced Connection Trace on the PVC.

2. Select an item in the Connection Trace Information field, and choose the Node B button.

The information for this node appears in the Destination Node fields, and this node will be the ending point of the Enhanced Connection Trace on the PVC.

3. Choose Initiate Connection Trace.

The Hop Name, Interface, VPI, and VCI appear for each hop in the Forward Connection Trace and Reverse Connection Trace fields.

4. If the last hop is for an offnet PNNI circuit (see “Offnet PVC Circuits” on page 12-75), enter the Termination IP in the text field provided. If the last hop is VNN, this field will be greyed out.

5. Choose Start. The Connection Trace Information (Hop Name and Node ID) are displayed on the upper left panel of the dialog box. (Note that the Initiate Connection Trace and Refresh buttons are now active and the Start button is greyed out.)

6. Select any two hops to see the Forward Connection Trace and Reverse Connection Trace. The requested trace information is displayed.

7. If you want to update the information, choose Refresh.

8. When you are done viewing the information, choose Close.

The View Enhanced Connection Trace Info dialog box closes.

Viewing Path Trace Information

This section describes how to view path trace information for a circuit. This section includes:

• “Overview of Path Trace Information” on page 12-21

• “Configuring Path Trace Information” on page 12-22

• “Displaying Path Trace Information for a Circuit” on page 12-26

• “Displaying Path Trace Information for a Logical Port” on page 12-30




Overview of Path Trace Information


• “Purpose of Path Trace” on page 12-21

• “Differences Between Path Trace and Connection Trace” on page 12-21

• “Circuits That Support Path Trace” on page 12-21

Purpose of Path Trace

The path trace feature is used to view the paths for new and existing connections. You can use the path trace feature to track the logical ports and logical nodes that a hypothetical point-to-point circuit would traverse in a network. Path trace can track even failed connections and report all paths attempted.

Path trace supports the following:

• Test connection tracing of point-to-point PVCs, SPVCs, and offnet circuits

• Test connections with “clear call,” PVCs and SPVCs created for path tracing purposes only, then deleted after a specified time period

• Administrative action — path tracing of all circuits (PVC, SPVC, or SVC) coming into or originating on a particular logical port

• Frame Relay and ATM endpoints

• Pure VNN networks, PNNI routing domains, and VNN/PNNI combined networks

VNN information will not be recorded when a path trace request originates from a switch other than a Lucent CBX 500/3500 or GX 550.

Differences Between Path Trace and Connection Trace

Table 12-11 shows the differences between Path Trace and Connection Trace.

Circuits That Support Path Trace

You can configure path trace for the following circuit types:

• ATM point-to-point PVCs

• ATM point-to-point offnet circuits

Table 12-11. Differences Between Path Trace and Connection Trace

Path Trace Connection Trace

Available for active or failed connections Available for active connections only

Reports all attempted paths Reports only the final path




• ATM point-to-point SPVCs

• ATM SVCs (by enabling path trace on a logical port)

Configuring Path Trace Information


• “Methods for Configuring Path Trace” on page 12-22

• “Configuring Path Trace Information on a Circuit (other than SVCs)” on page 12-22

• “Configuring Path Trace Information on a Logical Port” on page 12-24

Methods for Configuring Path Trace

Path trace is configured either by configuring the circuit itself for tracing, or by configuring a logical port so that all circuits that pass through or originate on the logical port are traced. The only way to configure path tracing on SVCs is to configure path tracing on the originating logical port.

Configuring Path Trace Information on a Circuit (other than SVCs)

To configure path tracing on a circuit other than an SVC (for SVCs, configure path tracing on the logical port):

1. Access the Administrative attributes for a circuit with either of the following methods:

• If you are adding a new circuit, go to the Administrative tab (see the ATM Services Configuration Guide for CBX 3500, CBX 500, GX 550, and B-STDX 9000).

• If the circuit already exists:

– Right-click on the circuit (see “Displaying Circuits” on page 11-2) and select Modify from the popup menu. The Modify PVC dialog box appears (Figure 12-5).

– Select the Administrative tab.




Figure 12-5. Modify PVC: Administrative Tab

2. Set the Path Trace as described in Table 12-12.

Table 12-12. Modify PVC: Administrative Tab Path Trace Fields

Field Action

Enable Path Trace Select the check box to enable path tracing on this circuit.

Clear Call at Destination (Only active when adding a circuit)

Select the check box to delete the circuit from the switch after the specified path trace timeout period. Path trace information for this circuit will also be made available for the timeout period.

Clear the check box so that the circuit will not be deleted from the switch after the specified path trace timeout period.




3. When you are done modifying or adding the circuit, choose OK.

The Modify PVC dialog box closes.

Configuring Path Trace Information on a Logical Port

To configure a logical port so that path trace information is collected on all circuits that either come into or originate on the logical port (this is the only method for configuring path tracing on SVCs):

1. Access the Administrative attributes for a logical port with either of the following methods:

• If you are adding a new logical port, go to the Administrative tab (see the ATM Services Configuration Guide for CBX 3500, CBX 500, GX 550, and B-STDX 9000).

• If the logical port already exists:

– Right-click on the logical port (see “Displaying Logical Ports” on page 6-1) and select Modify from the popup menu. The Modify Logical Port dialog box appears (Figure 12-6).

– Select the Administrative tab.

Crankback Info Required Select the check box to enable collection of crankback information for the circuit. Crankback information is information about dynamic rerouting of call setups around failed nodes or links (or links with insufficient resources) on the traced path.

Clear the check box (default) to disable crankback information collection.

Pass Along Request Select the check box to enable (default) path trace to continue through nodes that do not support the path trace feature, causing the path trace results to contain some gaps.

Clear the check box to disable pass along request. The path trace will terminate at any switch that does not support the path trace feature. A partial path trace will be returned.

Path Trace Timeout (sec)

(1 -65535)

Enter the number of seconds for the path trace function to time out, that is, for the trace results to be maintained in the switch. The default is 10 minutes (600 seconds).

Table 12-12. Modify PVC: Administrative Tab Path Trace Fields (Continued)

Field Action




Figure 12-6. Modify Logical Port: Administrative Tab

2. Set the Path Trace as described in Table 12-13.

Table 12-13. Modify Logical Port: Administrative Tab Path Trace Fields

Field Action

Enable Path Trace Select the check box to enable path tracing on circuits that pass through this logical port.

Crankback Info Required

Select the check box to enable collection of crankback information for circuits that pass through this logical port. Crankback information is information about dynamic rerouting of call setups around failed nodes or links (or links with insufficient resources) on the traced path.

Clear the check box (default) to disable crankback information collection.

Pass Along Request Select the check box to enable (default) pass along request for circuits that pass through this logical port. This allows the circuit path trace to continue through nodes that do not support the path trace feature, causing the path trace results to contain some gaps.

Clear the check box to disable pass along request for circuits that pass through this logical port. The path trace will terminate at any switch that does not support the path trace feature. A partial path trace will be returned.




3. When you are done modifying or adding the logical port, choose OK.

The Modify Logical Port dialog box closes.

Displaying Path Trace Information for a Circuit

To display path trace information for a circuit:

1. Display the circuit (see “Displaying Circuits” on page 11-2).

2. Right-click on the circuit and select View Path Trace Info from the popup menu.

The View Path Trace Information dialog box appears (Figure 12-7).

Table 12-14 describes the View Path Trace Information dialog box fields.

Path Trace Timeout (1-65535)

Select the number of seconds for the path trace function to time out, that is, for the trace results to be maintained in the switch. The default is 10 minutes (600 seconds).

Maximum Records (1-200)

Enter the number of trace records that can be present for this logical port. Enter a value between 1 and 200, or accept the default value (20).

Path Trace Boundary If this is a PNNI logical port, you can set it to be a path trace boundary.

Select the check box to cause the logical port to be a path trace boundary. If it is the incoming logical port of a traced call, then this node will be the trace source node. Path trace requests for calls coming in through this logical port will not be honored. This switch will not add any trace information and will not forward the trace request any further. If it is the outgoing logical port, then this node will be the trace destination node. It is assumed that the path trace request has reached its destination and has completed normally. This switch will add its trace information, but it will not forward the trace request further.

If this is not a PNNI logical port, this check box will be active.

Table 12-13. Modify Logical Port: Administrative Tab Path Trace Fields (Continued)

Field Action




Figure 12-7. View Path Trace Information Dialog Box (for a Circuit)

Table 12-14. View Path Trace Information Dialog Box Fields(for a Circuit)

Field Description

Trace Status The return status of the path trace on this connection. Possible values are:

• In Progress – trace is in progress

• Completed Normally – trace has been received from the trace destination

• Incomplete – trace request did not reach the trace destination

• Exceeded IE Length Limitations – the length of the trace transit list information field exceeded the maximum length

• Exceeded Message Length Limitations – the message length exceeded the maximum allowed

• Lack Resource – there is a lack of resource at an intermediate node

Trace Failure Cause The reason for the call failure.

• No cause – the trace completed normally and therefore returned no fail cause.

• SVC setup failure causes – see Appendix C, “Using SVC Failure Information” for a complete list.

Trace Source Port ID The PNNI logical port ID identifying the trace source interface. The value zero indicates that no trace source port ID was returned in the Trace transit list.

Trace Time Stamp The time when this path trace entry was created.




Enable Path Trace A selected check box indicates that path trace is enabled for this circuit.

Trace Diag The value of the diagnostic information from the cause field of the cause information field.

Clear Call at Destination A selected check box indicates that the circuit will be deleted from the switch after the specified path trace timeout period. Path trace information for this circuit will also be made available for the timeout period.

A cleared check box indicates that the circuit will not be deleted from the switch after the specified path trace timeout period.

(This field is set in the Add dialog box for the circuit.)

Crankback Info Required A selected check box indicates that the switch will collect and maintain the crankback information on the traced path.

A cleared check box indicates that the crankback information will not be collected.

Pass Along Request A selected check box indicates that the path trace will continue through nodes that do not support the path trace feature, causing the trace results to contain some gaps.

A cleared check box indicates that the path trace will terminate at any switch that does not support the path trace feature. A partial path trace will be returned.

Path Trace Timeout (sec) Displays the number of seconds that the trace results will be maintained in the switch.

Path The nodes and ports traversed by this connection.

Crankback Cause The PNNI crankback cause.

This is displayed only if the Crankback Info Required check box is selected.

Crankback Gap “Yes” Indicates that the trace was propagated beyond the node identified, but was cranked back and no trace information was returned by the node initiating the crankback.


Table 12-14. View Path Trace Information Dialog Box Fields(for a Circuit) (Continued)

Field Description




3. If you want to update the information, choose Update.

4. If you want to delete path trace data, choose Purge Path Trace.

5. When you are done viewing the path trace data, choose Close.

The View Path Trace Information dialog box closes.

Blocked Transit Type If a call is blocked at the corresponding node, the type of blockage will be identified. Possible values are:

• Blocked Incoming Link – call has been blocked at the node displayed

• Blocked Node – call has been blocked at this node

• Blocked Outgoing Link – call has been blocked at this link


Blocked Transit Indicator Contents of the Blocked Transit Trace information field from the Trace Transit List Information field. The format of this field depends on the value of the Blocked Transit Type field.

• When the Blocked Transit Type has a value of Blocked Incoming Link, this field is NULL.

• When the Blocked Transit Type has a value of Blocked Node, this field identifies the logical node at which the connection has been blocked.

• When the Blocked Transit Type has a value of Blocked Outgoing Link, this field indicates:

– The blocked link’s preceding node identifier (the logical node preceding a link at which the connection has been blocked).

– The blocked link’s port identifier (the logical port of the blocked link’s preceding node identifier).

– The blocked link’s succeeding node identifier (the logical node succeeding a link at which the connection has been blocked).


Table 12-14. View Path Trace Information Dialog Box Fields(for a Circuit) (Continued)

Field Description




Displaying Path Trace Information for a Logical Port

To display path trace information for a circuit:

1. Right-click on the logical port (see “Displaying Logical Ports” on page 6-1) and select View Path Trace Info from the popup menu.

The View Path Trace Information dialog box appears (Figure 12-8).

Figure 12-8. View Path Trace Information Dialog Box (for a Logical Port)

2. Select a circuit from the list that appears under Circuit Name.

The path trace information for that circuit appears in the dialog box. Table 12-15 describes the View Path Trace Information dialog fields.

Table 12-15. View Path Trace Information Dialog Box Fields(for a Logical Port)

Field Description

Trace Status The return status of the path trace on this connection. Possible values are:

• In Progress – trace is in progress

• Completed Normally – trace has been received from the trace destination

• Incomplete – trace request did not reach the trace destination

• Exceeded IE Length Limitations – the length of the trace transit list information field exceeded the maximum length

• Exceeded Message Length Limitations – the message length exceeded the maximum allowed

• Lack Resource – there is a lack of resource at an intermediate node




Trace Failure Cause The reason for the call failure.

• No cause – the trace completed normally and therefore returned no fail cause.

• SVC setup failure causes – see Appendix C, “Using SVC Failure Information” for a complete list.

Trace Time stamp The time when this path trace entry was created.

Trace Diag The value of the diagnostic information from the cause field of the cause information field.

Enable Path Trace A selected check box indicates that path trace is enabled for this circuit.

Connection Type Indicates whether the test connection is one of the following:

• PVC

• SVC incoming

• SVC outgoing

• SPVC call initiator

• SPVC target

• Unknown

Connection Cast Type The connection topology type of the test connection:

• P2P (point-to-point circuit)

• P2MP Root (point-to-multipoint root)

• P2MP Leaf (point-to-multipoint leaf)

• Unknown

Service Category The service category used by the call:

• CBR

• VBR-nrt

• VBR-rt

• ABR

• UBR

• Other

• Unknown

Table 12-15. View Path Trace Information Dialog Box Fields(for a Logical Port) (Continued)

Field Description




Calling Party The address of the calling part in the connection, when available.

Called Party The address of the called party in the connection, when available.

Clear Call at Destination A selected check box indicates that the circuit will be deleted from the switch after the specified path trace timeout period. Path trace information for this circuit will also be made available for the timeout period.

A cleared check box indicates that the circuit will not be deleted from the switch after the specified path trace timeout period.

(This field is set in the Add dialog box for the circuit.)

Crankback Info Required A selected check box indicates that the switch will collect and maintain the crankback information on the traced path.

A cleared check box indicates that the crankback information will not be collected.

Pass Along Request A selected check box indicates that the path trace will continue through nodes that do not support the path trace feature, causing the trace results to contain some gaps.

A cleared check box indicates that the path trace will terminate at any switch that does not support the path trace feature. A partial path trace will be returned.

Path Trace Timeout Displays the number of seconds that the trace results will be maintained in the switch.

Path The nodes and ports traversed by this connection.

Crankback Cause The PNNI crankback cause.


Crankback Gap “Yes” indicates that the trace was propagated beyond the node identified, but was cranked back and no trace information was returned by the node initiating the crankback.



Field Description




3. If you want to update the information, choose Update.

4. If you want to delete path trace data, choose Purge Path Trace.

5. When you are done viewing the path trace data, choose Close.

The View Path Trace Information dialog box closes.

Blocked Transit Type If a call is blocked at the corresponding node, the type of blockage will be identified. Possible values are:

• Blocked Incoming Link – call has been blocked at the node displayed

• Blocked Node – call has been blocked at this node

• Blocked Outgoing Link – call has been blocked at this link


Blocked Transit Indicator Contents of the Blocked Transit Trace information field from the Trace Transit List Information field. The format of this field depends on the value of the Blocked Transit Type field.

• When the Blocked Transit Type has a value of Blocked Incoming Link, this field is NULL.

• When the Blocked Transit Type has a value of Blocked Node, this field identifies the logical node at which the connection has been blocked.

• When the Blocked Transit Type has a value of Blocked Outgoing Link, this field indicates:

– The blocked link’s preceding node identifier (the logical node preceding a link at which the connection has been blocked).

– The blocked link’s port identifier (the logical port of the blocked link’s preceding node identifier).

– The blocked link’s succeeding node identifier (the logical node succeeding a link at which the connection has been blocked).



Field Description



Monitoring ATM CircuitsViewing ATM Circuit Summary Statistics

Viewing ATM Circuit Summary Statistics

ATM circuit summary statistics display the number of cells a circuit has sent and received, the round-trip delay, and other QoS statistics for the circuit.

Summary statistics are available for the following:

• PVCs

• Redirect PVCs

• Offnet circuits

• PMP PVC leaves

• PMP offnet circuit leaves

• SPVCs

• PMP SPVC leaves

Resource Management (RM) cells are counted as passed CLP 0 or passed CLP 1 cells. The logical port statistics dialog box provides separate RM cell statistics on a per logical port basis (see “Viewing ATM Logical Port Summary Statistics” on page 7-7).

To view summary statistics for an ATM circuit:

1. Display the circuit or circuit leaf for which you want to view summary statistics (see “Displaying Circuits” on page 11-2).

2. Expand the circuit or leaf (Figure 12-9).

Figure 12-9. PVC Monitor Node


The statistics monitoring dialog box appears (Figure 12-10). The summary statistics are described in the following tables:

• PVCs and Redirect PVCs: Table 12-16 on page 12-35




• Offnet circuits: Table 12-17 on page 12-38

• PMP PVC and offnet circuit leaves: Table 12-18 on page 12-39

For Frame-to-ATM circuits, ATM statistics appear for the ATM end of the circuit, and Frame Relay statistics appear for the Frame Relay end of the circuit. See “Viewing Frame Relay PVC Summary Statistics” on page 13-11 for a description of Frame Relay circuit statistics.


Table 12-16. Circuit Statistics Monitoring Dialog Box Fields (ATM)

Field Description


Passed CLP=0 Cells The total number of cells that were received and transmitted.




Passed CLP=1 Cells The total number of CLP=1 cells received at the port. This does not include CLP=0 cells that are received and then tagged as CLP=1 cells because they violated the defined traffic descriptor (TD). They are counted as tagged cells.

Discarded CLP=0 Cells The total number of received CLP=0 cells that are discarded because the cells violated the defined TD.

Note: Consistently high values in the Discarded CLP=0 Cells, Discarded CLP=1 Cells, and Tagged Cells fields indicate that either the source may need to slow transmission or that you should reconfigure the TDs to reflect the source speed.

Discarded CLP=1 Cells The total number of CLP=1 cells that are discarded because the cells violated the defined TD.


Non-Conforming CLP=0 Cells(GX 550 only)

The total number of CLP=0 cells that are tagged or discarded because the cells violated the defined TD.


The total number of CLP=1 cells that are discarded because the cells violated the defined TD.

Tagged Cells The total number of CLP=0 cells that are tagged as CLP=1 cells because they did not conform to the defined TD for the circuit.


Packets Discarded The total number of packets discarded.

ATM FCP CLP=0 Cells The total number of CLP=0 cells that are received and discarded by the ATM flow control processor (FCP).

ATM FCP CLP=1 Cells The total number of CLP=1 cells that are received and discarded by the ATM FCP.

Table 12-16. Circuit Statistics Monitoring Dialog Box Fields (ATM) (Continued)

Field Description




Buffer Discarded CLP=0 Cells

The total number of CLP=0 cells that were transmitted or received, and then discarded by buffer management.


The total number of CLP=1 cells that were transmitted or received, and then discarded by buffer management.

Buffer Discarded Cells EPD Threshold (OC48c BIO only)

The total number of AAL5 cells that were transmitted and discarded because they violated the early packet discard (EPD) threshold.

OAM CLP=0 Cells The total number of F4 and F5 OAM CLP=0 cells that were transmitted by the circuit.


OAM CLP 0+1 Cells The total number of F4 and F5 OAM CLP=0 and CLP=1 cells that were transmitted by the circuit.

Throughput

Bits per second The total number of bits received and transmitted by the circuit each second.

Cells per second The total number of cells received and transmitted by the circuit each second.

Utilization

Circuit Utilization A (%) The amount of traffic queued for transmission on a circuit as a percentage of the PCR. For this reason the value displayed in circuit utilization A can exceed 100%.

Circuit Utilization B (%) The amount of traffic queued for transmission on a circuit as a percentage of the PCR. For this reason the value displayed in circuit utilization B can exceed 100%.

NDC Statistics For a description of the NDC statistics, see “Network Data Collection” on page 12-53.

Table 12-16. Circuit Statistics Monitoring Dialog Box Fields (ATM) (Continued)

Field Description





Field Description



Passed CLP=1 Cells The total number of CLP=1 cells received at the port. This does not include CLP=0 cells that are received and then tagged as CLP=1 cells because they violated the defined traffic descriptor (they are counted as tagged cells).

Discarded CLP=0 Cells The total number of received CLP=0 cells that are discarded because the cells violated the defined traffic descriptor.

Note: Consistently high values in the Discarded CLP=0 Cells, Discarded CLP=1 Cells, and Tagged Cells fields indicate that either the source may need to slow transmission or that you should reconfigure the traffic descriptors to reflect the source speed.

Discarded CLP=1 Cells The total number of CLP=1 cells that are discarded because the cells violated the defined traffic descriptor.



The total number of CLP=0 cells that are tagged or discarded because the cells violated the defined traffic descriptor.


The total number of CLP=1 cells that are discarded because the cells violated the defined traffic descriptor.

Tagged Cells The total number of CLP=0 cells that are tagged as CLP=1 cells because they did not conform to the defined traffic descriptor for the circuit.


Packets Discarded The total number of packets discarded.




ATM FCP Discarded CLP=0 Cells

The total number of CLP=0 cells that are received and discarded by the ATM Flow Control Processor (FCP).


The total number of CLP=1 cells that are received and discarded by the ATM FCP.



Throughput Statistics

Bits per second The total number of bits received and transmitted by the circuit each second.

Cells per second The total number of cells received and transmitted by the circuit each second.

Utilization Statistics

Circuit Utilization A (%) The amount of traffic queued for transmission on a circuit as a percentage of the PCR. For this reason the value displayed in circuit utilization A can exceed 100%.

Circuit Utilization B (%) The amount of traffic queued for transmission on a circuit as a percentage of the PCR. For this reason the value displayed in circuit utilization B can exceed 100%.

Table 12-18. Circuit Statistics Monitoring Dialog Box Fieldsfor ATM PMP PVC and Offnet Circuit Leaves

Field Description

Circuit Root

Switch Name and ID The name and number of the switch associated with the circuit root.

VPI The VPI associated with the circuit root.

VCI The VCI associated with the circuit root.

LPort Name The name of the logical port associated with the circuit root.

Slot The slot number of the IOM used by the logical port.


Field Description




PPort The number of the physical port to which the logical port is mapped.

Interface The logical port’s internal interface number.

ID The logical port’s ID.

PMP Circuit Leaf

Switch Name and ID The name and number of the switch associated with the circuit leaf.

VPI The VPI associated with the circuit leaf.

VCI The VCI associated with the circuit leaf.

LPort Name The name of the logical port associated with the circuit leaf.

Slot The slot number of the IOM used by the logical port.

PPort The number of the physical port to which the logical port is mapped.

Interface The logical port’s internal interface number.

ID The logical port’s ID.

Leaf Cumulative Statistics

Cells The total number of cells that were received and transmitted.

Tagged Cells The total number of CLP=0 cells that were tagged as CLP=1 cells. Cells are tagged if they do not conform to the defined traffic descriptor for the circuit.

Note: Consistently high values in the Discarded CLP=0, Discarded CLP=1 Cells, and Tagged Cells Fields indicate that either the source may need to slow transmission or that you need to reconfigure the traffic descriptors to reflect the source speed.

Table 12-18. Circuit Statistics Monitoring Dialog Box Fieldsfor ATM PMP PVC and Offnet Circuit Leaves (Continued)

Field Description






The Circuit Statistics Monitoring dialog box closes.

Discarded CLP=0 Cells The total number of received CLP=0 cells that are dropped because the cell violates the defined traffic descriptor.


Discarded CLP=1 Cells The total number of CLP=1 cells that are discarded because the cells violate the defined traffic descriptor.


Passed CLP=0 Cells The total number of received CLP=0 cells that were passed for transmission.

Passed CLP=1 Cells The total number of CLP=1 cells received at the port. This does not include CLP=0 cells that were received and then tagged at CLP=1 cells because of a traffic descriptor violation (they were counted as tagged cells).

CLP=0 Cells The number of CLP=0 cells that were transmitted.

CLP=1 Cells The number of cells that were tagged as CLP=1 and transmitted.

Table 12-18. Circuit Statistics Monitoring Dialog Box Fieldsfor ATM PMP PVC and Offnet Circuit Leaves (Continued)

Field Description



Monitoring ATM CircuitsViewing 2-port ULC Gigabit Ethernet LPort Circuit Summary Statistics for Ethernet to ATM Endpoints

Viewing 2-port ULC Gigabit Ethernet LPort Circuit Summary Statistics for Ethernet to ATM Endpoints

To view 2-port ULC Gigabit Ethernet LPort circuit summary statistics for ethernet to ATM endpoints:

1. Display the circuit or circuit leaf for which you want to view summary statistics (see “Displaying Circuits” on page 11-2).

2. Expand the circuit or leaf (Figure 12-9 on page 12-34).

3. Right-click on the Monitoring node for the LPort ethernet to ATM circuit, and choose Start from the popup menu.

The LPort Circuit Statistics Monitoring dialog box appears (Figure 12-11 and Figure 12-12) for the 2-port ULC Gigabit Ethernet module. (Note: You must use the vertical scroll bar to see all of the fields in this dialog box.) Table 12-19 describes the fields for the LPort Circuit Statistics Monitoring dialog box.




Figure 12-11. 2-port ULC Gigabit Ethernet LPort Circuit Statistics Monitoring Dialog Box, ATM to Ethernet (Part 1)




Figure 12-12. 2-port ULC Gigabit Ethernet LPort Circuit Statistics Monitoring Dialog Box, ATM to Ethernet (Part 2)

Table 12-19. 2-port ULC Gigabit Ethernet LPort Circuit Statistics Monitoring, ATM to Ethernet

Field Description

EndPoint 1

Properties

SwitchName: Displays the name of the switch where endpoint 1 is configured.

BW(Kbps) Specifies the bandwidth of this endpoint.

LPortName Displays the name assigned to this Lport.

LPort Type Displays the service type at this Lport.




Slot_id: Specifies the switch slot number that the endpoint 1 module occupies.

PPortid: Specifies the physical port number from which the logical port at endpoint 1 is configured.

Channelid: Specifies the channel (time slot) number, when applicable, for a channelized port configured at endpoint 1.

QoS:

QoS: Displays the quality of service parameter for endpoint 1.

TrafficDescriptor:

Type: Displays the category of traffic descriptor for endpoint 1.

PCR (cells/sec): Specifies the peak cell rate (PCR). The PCR defines the maximum rate, in cells per second, at which cells are transmitted from endpoint 1.

SCR (cells/sec): Specifies the sustainable cell rate (SCR). The SCR defines the average rate, in cells per second (CPS), at which cells are transmitted from endpoint 1. The SCR must be less than or equal to the peak cell rate (PCR) for endpoint 1.

MBS (cells): Specifies the maximum burst size (MBS) for endpoint 1, in number of cells. This value determines the maximum number of cells that can be transmitted at the PCR.

MCR (cells/sec): Specifies the minimum cell rate (MCR) in cells per second (CPS), at which cells are transmitted from endpoint 1.

MDCR (cells/sec): Need description.


Passed CLP=0 Cells Displays the number of ATM CLP=0 cells that were received and transmitted on endpoint 1 that passed UPC.

Passed CLP=1 Cells Displays the number of ATM CLP=1 cells that were received and transmitted on endpoint 1 that passed UPC.

Discarded CLP=0 Cells Displays the number of ATM CLP=0 cells that were received on endpoint 1, but were discarded due to UPC failure. Ignore the value in the Transmitted column.

Table 12-19. 2-port ULC Gigabit Ethernet LPort Circuit Statistics Monitoring, ATM to Ethernet (Continued)

Field Description




Discarded CLP=1 Cells Displays the number of ATM CLP=1 cells that were received on endpoint 1, but were discarded due to UPC failure. Ignore the value in the Transmitted column.

OAM CLP=0 Cells Displays the number of ATM OAM CLP=0 cells transmitted. Ignore the value in the Received column.

OAM CLP=1 Cells Displays the number of ATM OAM CLP=1 cells transmitted. Ignore the value in the Received column.

OAM CLP 0 Cells Need description

Tagged Cells Displays the number of tagged ATM cells received. Ignore the value in the Transmitted column.

Cells Discarded Need description

ATM FCP CLP=0 Cells Displays the total number of CLP=0 cells that are received and discarded by the ATM flow control processor (FCP).

ATM FCP CLP=1 Cells Displays the total number of CLP=1 cells that are received and discarded by the ATM flow control processor (FCP).


Displays the total number of CLP=0 cells that were transmitted or received, and then discarded by buffer management.


Displays the total number of CLP=1 cells that were transmitted or received, and then discarded by buffer management.

Throughput

Bits per second Displays the total number of bits received and transmitted by the circuit each second.

Cells per second Displays the total number of cells received and transmitted by the circuit each second.

Utilization

Circuit Utilization Displays the amount of traffic queued for transmission on the circuit as a percentage of the PCR.

NDC Statistics

NDC History Choose the network data collection (NDC) history from the pull-down list for Current, 1st 15 Minute, and 2nd 15 Minute statistics.


Field Description




Timed Elapsed Displays the time elapsed since the last NDC history was set.

Lport Cumulative Statistics

NumberofCellErrors Displays the total number of cells that were received with a Header Error Control (HEC) error. An HEC error indicates a discrepancy between what the port expected in the header and what was actually received. The number of cell errors is indicated in the Received column. The Transmitted column does not apply.

NumberofOctets Displays the total number of octets (bytes) received and transmitted since the last reset.

NumberofCellsDiscarded Displays the total number of discarded cells since the last reset.

NumberofUnicast Cells Displays the total number of unicast cells received and transmitted since the last reset.

NumberofCells Displays the total number of cells received and transmitted by the port since the last reset.

NumberofRMCells Displays the total number of RM cells that the ATM circuit received on the logical port.

Lport Throughput

ThroughPutCellsPerSecond Displays the throughput at the endpoint 1 Lport in cells per second.

ThroughPutBitsPerSecond Displays the throughput at the endpoint 1 Lport in bits per second.

Lport Utilization (%)

Utilization(%) Displays the amount of traffic received and transmitted on a logical port as a percentage of the committed information rate (CIR). It does not measure the amount of bandwidth of the logical port, so the value that the system displays in this field can exceed 100%.

EndPoint 2

Properties



Field Description










QoS:


TrafficDescriptor:

CIR(Kbps): Displays the committed information rate for this logical port.

CBS(Kbps): Need description

EIR(Kbps): Need description

EBS(Kbps): Need description






Field Description




Red Frames Displays the total number of red frames received and transmitted over the specified logical ports since the last reset.

Red packets are forwarded with the DE bit set when the Graceful Discard feature is set to On. When the Graceful Discard feature is set to Off, red packets are discarded. Red packets are designated as those bits received during the current time interval that exceed the committed burst size and excess burst size thresholds, including the current frame.

NumberOfFrames Displays the total number of frames received and transmitted over the specified logical ports since the last reset.

Amber Octets Displays the total number of amber octets (bytes) received and transmitted over the specified logical ports since the last reset. Amber octets are eligible for discard if they pass through a congested node.

Red Octets Displays the total number of red octets (bytes) received and transmitted over the specified logical ports since the last reset.

Red octets are forwarded with the DE bit set when the Graceful Discard feature is set to On. When the Graceful Discard feature is set to Off, red octets are discarded.

NumberOfOctets Displays the total number of octets (bytes) received and transmitted over the specified logical ports since the last reset.

Amber Octets High Displays the high number of amber octets (bytes) received and transmitted over the specified logical ports since the last reset.

Red Octets High Displays the high number of red octets (bytes) received and transmitted over the specified logical ports since the last reset.

Throughput


Utilization



Field Description




For additional information on circuit summary statistics for ethernet to Frame Relay endpoints, see “Viewing 2-port ULC Gigabit Ethernet LPort Circuit Summary Statistics for Ethernet to Frame Relay Endpoints” on page 13-15.

CongestionStatistics

FECNFrames Displays the number of frames that were received or transmitted with the Forward Explicit Congestion Notification (FECN) bit set to 1. The network sets an FECN bit to 1 if the network is encountering congestion. FECN frames indicate that there may not be sufficient network resources to continue handling the submitted traffic at the current rate.

BECNFrames Displays the number of frames that were received or transmitted with the Backward Explicit Congestion Notification (BECN) bit set to 1. The network sets a BECN bit to 1 if the network is encountering congestion. BECN frames indicate that there may not be sufficient network resources to continue handling the submitted traffic at the current rate.






Lport Throughput



Utilization(%) Displays the amount of traffic received and transmitted on this logical port as a percentage of the committed information rate (CIR). It does not measure the amount of bandwidth of the logical port, so the value that the system displays in this field can exceed 100%.


Field Description


Viewing NTM and NDC Statistics



This section describes how to configure and use network traffic management (NTM) and Network Data Collection (NDC) on CBX 500/3500 and GX 550 switches. NTM and NDC provide you with statistics on point-to-point PVC and point-to-multipoint PVC traffic. Lucent has based the functional requirements for NTM and NDC on the Bellcore GR-1248 specification [GR1248].

NTM and NDC are disabled by default. To enable NTM and NDC, you first configure the NTM congestion thresholds for the “feeder” logical port. The feeder port can be any UNI, Direct trunk, or NNI logical port. Then, you set the NDC thresholds on a per-PVC basis. You can then monitor the NTM and NDC data that the logical port and PVC collect. You can enable the NTM and NDC functions when you first configure your switch, or you can take the logical port/PVCs offline to enable these functions once you establish a basic switch-to-NMS configuration.

Network Traffic Management

The purpose of NTM is to improve PVC traffic performance during overloads and failures in the network. NTM provides the following functions:

• Measures of congestion (MOC) — Defined at the ATM level based on percentage of cell loss.

• NTM surveillance measurements — Used to detect overloads based on MOCs.

• NTM state change notification — Used to send a trap when the MOC exceedes the severe congestion threshold.

• NTM control functions — Used to regulate/reroute the traffic flow during overloads.

Measures of Congestion

NTM applies a MOC to all congestable ATM modules. A congestable ATM module is any entity within an ATM Network Element (ATM NE) that can experience traffic congestion. The Lucent switch MOC is based on the count of CLP=0+1 cells discarded due to congestion in the output process. This count is sampled at each feeder logical port every 20 milliseconds.

Note – On the GX 550, counts of cells that are discarded due to output buffer congestion are not available. Instead, Navis EMS-CBGX displays the cell rate passing through the logical port, so configurable NDC thresholds on GX 550 logical ports are more useful for monitoring levels of traffic, rather than congestion.



Monitoring ATM CircuitsViewing NTM and NDC Statistics

To prevent traffic bursts from corrupting the measurement, a MOC is subject to a smoothing algorithm that averages the congestion measurement over a period of time. The smoothed MOC is subject to four congestion thresholds (CT0-CT3), which you define for the logical port.

The thresholds default to zero, which prevents the accumulation of congestion statistics. CT3 is designated as the severe congestion threshold, and CT0 is designated as the severe congestion abatement threshold. The CT1 – CT3 thresholds define four corresponding machine congestion levels, MC0 – MC3.

NTM Surveillance Measurements

The NTM surveillance measurements are based on 5-minute intervals. The timestamp of the counts corresponds to the end of the 5-minute interval.

For each logical port, the following counts are maintained for the 5-minute period:

• Total number of discarded CLP=0+1 cells.

• For each MC0 - MC3 level, the number of 20-millisecond periods spent in that level (from 0 to 15,000).

• For each MC0 - MC3 level, the number of times (based on 20-millisecond

sampling) this level was entered (from 0 to 7,500). This includes transitions from both the higher and lower levels.

For each logical port, Navis EMS-CBGX provides a variety of NTM statistics, including the current plus three 5-minute history counts, as well as the timestamps for the history counts and the time elapsed (measured in seconds) in the current 5-minute period. The timestamps use the Universal Coordinated Time (UCT) available on the switch and have a 1-second resolution.

NTM State Change Notifications

When the smoothed MOC exceeds CT3 and stays above CT0 for the specified time interval (T), an SNMP trap is issued to the NMS. Once this first trap is sent, when the smoothed MOC falls below CT0, another SNMP trap is sent. The interval T defaults to 30 seconds. Traps are issued within 5 seconds of the respective event detection.

NTM Control Functions

Only automatic NTM control functions are used to alleviate congestion. The NMS is not used to specify alternate routes. Currently, the hardware output process implements selective cell discards without software intervention.




Network Data Collection

You configure the NDC measurements to detect any violation of PVC service subscription parameters and establish trends in network traffic patterns and loads. Scheduled measurements are taken on a regular basis as soon as the ATM NE is put into service. The measurements monitor the usage and health of the network.

Lucent switches support NDC scheduled measurements for up to 360 simultaneously monitored circuits per IOM.

For each feeder port and PVC, Navis EMS-CBGX provides a variety of NDC statistics including:

• The current plus two 15-minute history counts.

• The timestamps for the history counts (taken at the end of respective 15-minute periods). The timestamps use the Universal Coordinated Time (UCT) available on the switch and have a 1-second resolution.

• The time elapsed in the current 15-minute period.

There are three types of NDC scheduled measurements:

• Traffic load measurements — Count the number of incoming/outgoing cells on a per-interface and per-VC basis.

• UPC/NPC disagreement measurements — Collect the number of cells discarded due to UPC/network parameter control (NPC) violations on a per-VC basis.

• Traffic load and congestion measurements — Count the cells processed and discarded by a congestable ATM NE module, respectively. These counts do not include cells discarded due to UPC/NPC disagreements.

Traffic Load Measurements

The traffic load measurements count all NDC-valid cells. These are all user+OAM cells submitted to UPC/NPC before policing actions occur. Traffic load measurements maintain a count of the number of incoming/outgoing CLP=0+1 user+OAM cells in a 15-minute period for all UNI and NNI logical ports.

For the PVC endpoint you select, these measurements also maintain a count of the following user/OAM cells at the ingress/egress node in a 15-minute period:

• Number of incoming CLP=0+1 cells

• Number of outgoing CLP=0+1 cells




UPC/NPC Disagreement Measurements

The UPC/NPC disagreement measurements count the number of cells the network discards due to peak cell rate (PCR) violation at the UNI (UPC) and at ingress VC at B-ICI (NPC). Two counts of incoming cells that are discarded due to traffic descriptor violations are collected on a per-VC basis:

• Number of incoming discarded CLP=0+1 cells.

• Number of incoming discarded high-priority (CLP=0) cells, including cells tagged as CLP=1 and then dropped; performed only if the ATM NE supports loss priority.

In these two cases, NDC measurements count both the user and OAM cells. These measurements are applied to selected PVC endpoints.

If the ATM NE implements cell tagging, NDC measurements count the number of CLP=0 cells that are tagged as CLP=1 cells.

Traffic Load and Congestion Measurements

The NDC MOC is based on the number of CLP=0+1 cells discarded per-port. The sampling period is 20 ms, same as for NTM. The NDC uses the same congestion thresholds CT1 - CT3, and consequently the same machine congestion levels MC0 - MC3 as defined for NTM. This enables a simple accumulation of the 5-minute NTM values to provide the 15-minute value.

The following counts of user+OAM cells per port are maintained in the 15-minute period:

• Number of discarded CLP=0+1 cells.

• For each MC0 - MC3 level, number of 20-millisecond periods spent in that level

(from 0 to 45,000).

• For each MC0 - MC3 level, number of times (based on 20-millisecond sampling)

this level is entered (from 0 to 22,500), including transitions from both the higher and lower levels.

Configuring NTM Attributes for a Feeder Logical Port

To define the NTM attributes for a feeder logical port:

1. Right-click on the logical port (see “Displaying Logical Ports” on page 6-1) and select Modify from the popup menu.





Figure 12-13. Modify Logical Port: NTM Tab

2. Select the NTM tab.

3. Complete the NTM tab fields as described in Table 12-20.

Table 12-20. Modify Logical Port: NTM Tab Fields

Field Action

Disable NTM box Clear the check box to enable NTM.

Severe Congestion: CT3 (cells/sec)

Move the slider to set the severe congestion CT3 threshold. Choose the Set Defaults button to set the default values for the Severe Congestion and Minor Congestion fields.

Severe Congestion: CT0 (cells/sec)

Move the slider to set the severe congestion CT0 threshold. Choose the Set Defaults button to set the default values for the Severe Congestion and Minor Congestion fields.

Minor Congestion: CT2 (cells/sec)

Move the slider to set the minor congestion CT2 threshold. Choose the Set Defaults button to set the default values for the Severe Congestion and Minor Congestion fields.

Minor Congestion: CT1 (cells/sec)

Move the slider to set the minor congestion CT1 threshold. Choose the Set Default button to set the default values for the Severe Congestion and Minor Congestion fields.




4. When you have finished completing the NTM attributes, choose OK.

The attributes you entered are saved, and the Modify Logical Port dialog box closes.

Viewing NTM Attributes for a Logical Port

To view the NTM attributes for a feeder logical port:

1. Right-click on the logical port (see “Displaying Logical Ports” on page 6-1) and select View from the popup menu.

The View Logical Port dialog box appears.

2. Select the NTM tab.

The NTM tab fields are described in Table 12-21.

3. When you have finished viewing the NTM attributes, choose Close.

The View Logical Port dialog box closes.

Traffic Notification Time (1-86400 sec)

Enter the minimum severe congestion period during which an alarm is generated on an IOM. The default value is 30.

Set Defaults Choose this button to set the defaults for the Severe Congestion, Minor Congestion and Traffic Notification Time fields.

Table 12-20. Modify Logical Port: NTM Tab Fields (Continued)

Field Action

Table 12-21. View Logical Port: NTM Tab Fields

Field Description

Disable NTM box A cleared check box indicates NTM is enabled.

Severe Congestion: CT3 Displays the severe congestion CT3 threshold.

Severe Congestion: CT0 Displays the severe congestion CT0 threshold.

Minor Congestion: CT2 Displays the minor congestion CT2 threshold.

Minor Congestion: CT1 Displays the minor congestion CT1 threshold.

Traffic Notification Time Displays the minimum severe congestion period during which an alarm is generated on an IOM.




Viewing NTM Logical Port Statistics

To view NTM logical port statistics:

1. Open the LPort Statistics Monitoring dialog box and select the NTM statistics category (see “Viewing ATM Logical Port Summary Statistics” on page 7-7).

The NTM logical port statistics appear (Figure 12-14).

The statistics are described in Table 12-22.

Figure 12-14. NTM Statistics in the LPort Statistics Monitoring Dialog Box

Table 12-22. NTM Logical Port Statistics


Enter Level Red The number of 20-millisecond periods spent in the MC3 congestion level.

Enter Level Orange The number of 20-millisecond periods spent in the MC2 congestion level.

Enter Level Yellow The number of 20-millisecond periods spent in the MC1 congestion level.

Enter Level Green The number of 20-millisecond periods spent in the MC0 congestion level.

Count Level Red The number of times that the MC3 congestion level was entered.

Count Level Orange The number of times that the MC2 congestion level was entered.

Count Level Yellow The number of times that the MC1 congestion level was entered.

Count Level Green The number of times that the MC0 congestion level was entered.







Viewing NDC Logical Port Statistics

To view NDC logical port statistics:

1. Open the LPort Statistics Monitoring dialog box and select the NDC statistics category (see “Viewing ATM Logical Port Summary Statistics” on page 7-7).

The NDC logical port statistics appear (Figure 12-15).

Figure 12-15. NDC Statistics in the LPort Statistics Monitoring Dialog Box

The statistics are described in Table 12-23.

Outgoing Discarded CLP=0+1

The number of outgoing discarded CLP=0+1 cells.

Table 12-22. NTM Logical Port Statistics (Continued)


Table 12-23. NDC Logical Port Statistics


Enter Level Red The number of 20-millisecond periods spent in the MC3 congestion level.

Enter Level Orange The number of 20-millisecond periods spent in the MC2 congestion level.

Enter Level Yellow The number of 20-millisecond periods spent in the MC1 congestion level.







Configuring NDC Attributes for a Point-to-Point Circuit

You can configure NDC thresholds and attributes for both logical port endpoints on a circuit. To configure the NDC thresholds and attributes:

1. Display the circuit whose attributes you want to configure (see “Displaying Circuits” on page 11-2).

2. Right-click on the circuit and select Modify from the popup menu.

The Modify PVC dialog box appears (Figure 12-16).

Enter Level Green The number of 20-millisecond periods spent in the MC0 congestion level.

Count Level Red The number of times that the MC3 congestion level was entered.

Count Level Orange The number of times that the MC2 congestion level was entered.

Count Level Yellow The number of times that the MC1 congestion level was entered.

Count Level Green The number of times that the MC0 congestion level was entered.

Outgoing Discarded CLP=0+1

The number of outgoing discarded CLP=0+1 cells.

Table 12-23. NDC Logical Port Statistics (Continued)





Figure 12-16. Modify PVC Dialog Box: NDC Tab

3. Select the NDC tab.

4. Complete the NDC tab fields as described in Table 12-24.

Table 12-24. Modify PVC Dialog Box: NDC Tab Fields

Field Description

Total PVCs Enabled on Card (Endpoint 1 and Endpoint 2)

Displays the current number of NDC-enabled endpoints for the card at each endpoint.

Limit of PVCs Enabled on Card (Endpoint 1 and Endpoint 2)

Displays the limit of NDC-enabled endpoints you can configure on a module at each endpoint. The limits are:

CBX 500 switches – 360CBX 3500 – 16000GX 550 switches – 1440

Network Data Collection (Endpoint 1 and Endpoint 2)

Select this check box to enable NDC statistics collection for this circuit endpoint.




5. When you are done modifying the NDC attributes, choose OK.


Configuring NDC Attributes for a Point-to-Multipoint Circuit

This section describes how to configure the NDC attributes for a point-to-multipoint circuit (PMP).

Restrictions

You can only configure NDC attributes for a (PMP) circuit when you initially define a circuit root. Once you create the root, you cannot enable or modify the NDC attributes.

Incoming Discarded Thresholds (Endpoint 1 and Endpoint 2)

Enter a value between zero and 1500000.

These thresholds apply to the number of incoming CLP=0 and CLP=0+1 cells that have been discarded. If the number of discarded cells for this endpoint exceeds the value you configure, a trap is generated.

Table 12-24. Modify PVC Dialog Box: NDC Tab Fields

Field Description




To Configure the NDC Thresholds

To configure the NDC thresholds and attributes for a circuit root:

1. While adding a new circuit root, go to the Administrative tab (see the ATM Services Configuration Guide for CBX 3500, CBX 500, GX 550, and B-STDX 9000).

The Add Point-to-Multipoint PVC Root dialog box appears (Figure 12-17).

Figure 12-17. Add Point-to-Multipoint PVC Root: NDC Tab


3. Complete the NDC tab fields as described in Table 12-25.

Table 12-25. Add Point-to-Multipoint PVC Root Dialog Box: NDC Tab

Field Description

Total PVCs Enabled on Card Displays the current number of NDC-enabled endpoints for the module associated with the circuit root.

Limit of PVCs Enabled on Card Displays the limit of NDC-enabled endpoints you can configure on a module associated with the circuit root. The limits are:

CBX 500 switches – 360 CBX 3500 – 16000GX 550 switches – 1440

Network Data Collection Select this check box to enable NDC statistics collection for this circuit.




4. Continue with the process of adding the circuit root.

Viewing NDC PVC Thresholds

To view NDC thresholds for either endpoint of a PVC:

1. Display the circuit whose NDC thresholds you want to view (see “Displaying Circuits” on page 11-2).


The View PVC dialog box appears.


The NDC tab fields are described in Table 12-26.

4. When you have finished viewing the NTM attributes, choose Close.

The View PVC dialog box closes.

Table 12-26. View PVC Dialog Box: NDC Tab Fields

Field Description

Total PVCs Enabled on Card (Endpoint 1 and Endpoint 2)

Displays the current number of NDC-enabled endpoints for the card at each endpoint.

Limit of PVCs Enabled on Card (Endpoint 1 and Endpoint 2)

Displays the limit of NDC-enabled endpoints you can configure on a module at each endpoint. The limits are:

CBX 500 switches – 360 CBX 3500 – 16000GX 550 switches – 1440

Network Data Collection (Endpoint 1 and Endpoint 2)

Select this check box if NDC statistics collection is enabled for this circuit endpoint.

Incoming Discarded Thresholds (Endpoint 1 and Endpoint 2)

Enter a value between zero and 1500000.

These thresholds apply to the number of incoming CLP=0 and CLP=0+1 cells that have been discarded. If the number of discarded cells for this endpoint exceeds the value you configure, a trap is generated.



Monitoring ATM CircuitsViewing ATM SVC Summary Statistics

Viewing NDC PVC Data

To display NDC PVC statistics for the endpoints, see “Viewing ATM Circuit Summary Statistics” on page 12-34. The NDC statistics are described in “Network Data Collection” on page 12-53.

Viewing ATM SVC Summary Statistics


• “SVC Statistics Overview” on page 12-64

• “To View ATM SVC Summary Statistics” on page 12-64

SVC Statistics Overview

This section describes how to monitor ATM SVCs in a Lucent network. You can check the status of configured SVC parameters and view statistics on SVC activity. For more information on ATM SVCs, see the ATM Services Configuration Guide for CBX 3500, CBX 500, GX 550, and B-STDX 9000.

For ATM SVCs, Resource Management (RM) cells are counted as passed CLP=0 or passed CLP=1 cells. The Logical Port Statistics dialog box provides separate RM cell statistics on a per logical port basis (see “Viewing ATM Logical Port Summary Statistics” on page 7-7).

To View ATM SVC Summary Statistics

To view ATM SVC summary statistics:

1. Display the active SVC for which you want to view summary statistics (see “Viewing All Active SVCs” on page 11-13).

2. Expand the SVC (Figure 12-18).




Figure 12-18. SVC Monitor Node


The SVC Statistics Monitoring dialog box appears (Figure 12-19).

The summary statistics are described in Table 12-27 on page 12-66:

For Frame-to-ATM circuits, ATM statistics appear for the ATM end of the circuit, and Frame Relay statistics appear for the Frame Relay end of the circuit. See “Viewing Frame Relay SVC Summary Statistics” on page 13-26 for a description of Frame Relay SVC statistics.



Monitoring ATM CircuitsViewing ATM SVC Summary Statistics

Figure 12-19. SVC Statistics Monitoring Dialog Box

Table 12-27. SVC Statistics Monitoring Dialog Box Fields (ATM)

Field Displays...



Passed CLP=1 Cells The total number of CLP=1 cells received at the port. This does not include CLP=0 cells that were received and then tagged as CLP=1 cells because of a traffic descriptor violation (they are counted as tagged cells).

Note: Consistently high values in the Discarded CLP=0, Discarded CLP=1 Cells, and Tagged Cells fields indicate that either the source may need to slow transmission, or that you should reconfigure the traffic descriptors to reflect the source speed.




Discarded CLP=0 Cells The total number of received CLP=0 cells that are dropped because the cell violates the defined traffic descriptor.


Discarded CLP=1 Cells The total number of CLP=1 cells that are discarded because the cells violate the defined traffic descriptor.


Tagged Cells The total number of CLP=0 cells that were tagged as CLP=1 cells. Cells are tagged if they do not conform to the defined traffic descriptor for the circuit.


The total number of received CLP=0 cells that are received and discarded by the ATM Flow Control Processor (FCP).


The total number of CLP=1 cells that are received and discarded by the ATM FCP.



Throughput

Bits per Second The number of bits transmitted and/or received each second.

Cells per Second The number of cells transmitted and/or received each second.

Utilization

Utilization (%) The amount of traffic queued for transmission on a circuit as a percentage of link speed. Therefore, the circuit utilization value can exceed 100%.

Table 12-27. SVC Statistics Monitoring Dialog Box Fields (ATM) (Continued)

Field Displays...



Monitoring ATM CircuitsViewing CAC Parameters for ATM Circuits



The SVC Statistics Monitoring dialog box closes.

Viewing CAC Parameters for ATM Circuits

To view the Lucent Call Admission Control (CAC) parameters that have been configured for circuits on a switch:

1. In the switch tab (see “Displaying a Switch Tab in the Navigation Panel” on page 2-6), right-click on the switch and select Set CAC Parameters from the popup menu.

The Set All CAC Parameters dialog box appears (Figure 12-20). For a description of the attributes, see the ATM Services Configuration Guide for CBX 3500, CBX 500, GX 550, and B-STDX 9000.

Figure 12-20. Set All CAC Parameters Dialog Box

2. When you have completed viewing the CAC parameters, choose Cancel.

The Set All CAC Parameters dialog box closes.


Testing ATM Circuits



This section describes how to test an ATM circuit. This section includes:

• “Circuit Testing Overview” on page 12-69

• “Before You Begin” on page 12-70

• “OAM Connectivity Verification” on page 12-70

• “Sequence of OAM Loopback Tests” on page 12-71

• “Setting the OAM Loopback Time Interval” on page 12-72

• “Running an OAM Loopback Test on an ATM Circuit” on page 12-73

Circuit Testing Overview

The CBX 500, CBX 3500, and GX 550 support the Operation, Administration, and Maintenance (OAM) functions described in the ATM Forum UNI 3.0/3.1/4.0 Specifications.

On the CBX 500/3500 and GX 550, OAM functions test connectivity on the following circuit types:

• ATM PVCs

• ATM Redirect PVCs

• ATM SVCs

• ATM offnet circuits

• ATM Point-to-Point SPVCs

This section describes how OAM cells are used with ATM layer fault management to provide the following functions:

• OAM connectivity verification

• OAM alarm surveillance

The CBX 500/3500 and GX 550 do not support OAM performance monitoring (PM) functions.

For more information about OAM, see the ATM Forum UNI 3.0, 3.1 or 4.0 Specifications.



Monitoring ATM CircuitsTesting ATM Circuits

Before You Begin

Before you run an OAM loopback test, verify that all of the equipment to be tested supports OAM. You should also be aware of a phenomenon called an OAM storm. OAM storms are characterized by an IOM/IOP physical port receiving OAM cells at a rate greater than one OAM cell per second (CPS) per virtual circuit. This event is extremely rare and is caused by defective equipment.

Lucent switches protect against OAM storms. If a physical port receives OAM cells at a rate that exceeds approximately 800 cells per second for any particular VC on that port, the VC shuts down for two minutes. When the shutdown occurs, the switch sends the following trap to the NMS:

OAM overload detected on [circuit name] at [switch name] on lport [lport name]

If the OAM storm is temporary, the circuit resumes normal operation after two minutes. If the OAM storm persists, the circuit remains down, and the trap continues to appear every two minutes. In this case, you can either delete the circuit or change the Admin Status of the physical port to Down.

In the event of an OAM storm, you should determine why the attached device is sending OAM cells at a rate that triggers the protection circuitry. No network conditions should ever cause such a fast rate of OAM cells to be sent to the switch.

OAM Connectivity Verification

The CBX 500/3500 and GX 550 support two types of OAM connectivity verification:

• OAM cells sent to a CBX 500/3500 or GX 550 UNI/NNI port from an attached device

• OAM loopback cell generation

OAM Cells Sent to a CBX 500/3500 or GX 550 UNI Port from an Attached Device

When OAM virtual path (VP) (F4) or virtual channel (VC) (F5) segment loopback cells are sent to a CBX 500/3500 or GX 550 UNI logical port, the cell’s Loopback Indication field decrements and the switch sends the cell back to the originating device (in most cases). If no VP or VC associated with the VPI or VCI of the OAM cell exists on the UNI logical port that received the cell, the OAM cell is discarded. The OAM cell is also discarded if it is improperly formatted.




In most cases, the CBX 500/3500 or GX 550 assumes the role of an intermediate switch from an OAM perspective. If OAM F4 or F5 end-to-end (not segment) loopback cells are sent to a CBX 500/3500 or GX 550 UNI port, the cells are passed through the switch unmodified over the VP or VC. Since the CBX 500/3500 or GX 550 is only the intermediate switch for the VP or VC, no action is taken. The device at the circuit’s terminating point performs the loopback action for an end-to-end loopback cell.

OAM Loopback Cell Generation

You can generate loopbacks on PVCs, SVCs, and SPVCs. Using the OAM loopback function, you can generate OAM loopback cells from a CBX 500/3500 or GX 550 UNI/NNI interface toward the attached device as shown in Figure 12-21, or into the Lucent network as shown in Figure 12-22.

Figure 12-21. OAM Loopback Process From UNI/NNI Interface

Figure 12-22. OAM Loopback Process Through Lucent Network

Sequence of OAM Loopback Tests

To run the OAM loopback test, use the following sequence:

1. (Optional) Change the OAM loopback time interval from the default polling interval of 5 seconds (page 12-72).

2. Run the OAM loopback test (page 12-73).

Router

CBX 500

CBX 500 CBX 500

Trun Trun Trun




Setting the OAM Loopback Time Interval

Navis EMS-CBGX monitors the progress of the loopback once per polling interval. Slow response time indicates network congestion.

To set a time interval other than the default interval (5 seconds):

1. Select Preferences from the View menu (Figure 12-23).

The Preferences dialog box appears (Figure 12-24).

Figure 12-23. View Menu

Figure 12-24. Preferences Dialog Box

2. In the OAM Poll Interval field, enter the new time interval (in seconds) for collecting loopback diagnostics. Enter a value from 0 to 9999.

3. Choose OK.

The change is saved, and the Preferences dialog box closes.




Running an OAM Loopback Test on an ATM Circuit

To run the OAM loopback test on an ATM PVC, offnet circuit, SPVC, or SVC:

1. Display the circuit (see “Displaying Circuits” on page 11-2 or “Viewing All Active SVCs” on page 11-13).

2. Right-click on the circuit and select OAM from the popup menu.

The PVC OAM Loopback dialog box appears (Figure 12-25).

Figure 12-25. PVC OAM Loopback Dialog Box

3. Complete the PVC OAM Loopback dialog fields as described in Table 12-28.

Table 12-28. PVC OAM Loopback Dialog Box Fields

Field Action

Loopback Source Choose either Endpoint 1 or Endpoint 2 as the source of the loopback signal.

Note – Endpoint 1 is not applicable for MPVC and MSPVC circuits. Endpoint 2 is not applicable for SPVC and SVC circuits.

Loopback Direction

Choose one of the following loopback types:

• Out Interface — Enables you to send the OAM cells out the UNI/NNI port to the attached ATM device, such as a router.

• Across Network — Enables you to send the OAM cells over the trunk to the connected Lucent switch.





Table 12-29 describes the PVC OAM Loopback dialog box test results.

Loopback Type Choose one of the following loopback types:

• End-To-End — Sends a signal across the network to the circuit endpoint.

• Segment — Sends OAM loopback segment cells to the next attached device, or across as many hops as you specify in the Hop Count field.

Note – Segment cells are not generated for the circuits in the PNNI domain.

Hop Count Specify the number of hops to send OAM loopback cells. This option is available only if you select Across Network in the Loopback Direction field and Segment in the Loopback Type field. Initially, you specify a small number of hops and gradually increase the number until you isolate the problem.

Number Of OAM Cells To Send

Specify the number of OAM cells to send. Initially, send a minimal number of cells; for example, 10 cells.

ATM Round Trip Delay

Choose one of the following:

Enable — OAM cells are sent to measure the round trip delay of the circuit.

Disable — (default) OAM cells are not sent to measure the round trip delay of the circuit.

For a description of the ATM Round Trip Delay feature, see “ATM Round-trip Delay/Cell Loss Statistics” on page 12-77.

Aggregate Interval

Choose from the pull-down menu the amount of time (in minutes) over which the round trip delay/cell loss statistics (RTD/CLS) are accumulated inside the switch. The options are as follows: 5, 10, 15 (default), 20, 30, 60. This interval should be the same as BulkStats interval time.

CLS Status Displays the current Cell Loss Statistics (CLS) status (Up/Down) of the circuit. If signaling is successful, this field will indicate the correct ATM Round Trip Delay (Enable/Disable) setting.

CLS Failure Code

Displays the reason (default, None) for current CLS configuration failure for the circuit.

CLS Int Period Displays the interval period for CLS/RTD, that is, the last successfully set value for the Aggregate Interval field.

Table 12-28. PVC OAM Loopback Dialog Box Fields (Continued)

Field Action


Offnet PVC Circuits



6. Choose Close.

The PVC OAM Loopback dialog box closes.

Offnet PVC Circuits

CBX 500, GX 550, and B-STDX 9000 switches support Frame Relay-to-ATM interworking of offnet circuits (that is, proprietary SPVCs) across either PNNI or ATM OSPF/PNNI networks. This capability is provided by the Offnet PVC circuit type and is based on the Frame Relay Forum FRF.5 implementation agreement.

To view an offnet PVC circuit, refer to “Displaying Circuits” on page 11-2.

Viewing PWE3 Offnet PVCs

Pseudo Wire Edge-to-Edge Emulation (PWE3) enables carriers to offer scalable and flexible service over a packet switched network. A PWE3 circuit is created between two label edge routers (LERs) on the edge of the IP/MPLS network, and traffic is encapsulated and routed over a provider’s IP/MPLS backbone.

To View an Offnet PWE3 PVC

To view an offnet PWE3 PVC:

1. Display the offnet PVC circuit (see “Displaying Circuits” on page 11-2).

2. Right-click on the offnet PVC and select View from the popup menu. The View Offnet Circuit screen appears (Figure 12-26). Note that the Admin tab in this screen has a checkbox labeled Enable PWE3 Signalling. If this box is checked, the circuit is PWE3.

Table 12-29. PVC OAM Loopback Dialog Box Test Results

Result Displays...

Response Time (msec)

The Lowest, Average, and Highest response times to the loopback signal.

Responses: Received

The number of responses that were received during the OAM test.

Responses: Timed-Out

The number of responses that timed-out during the OAM test.



Monitoring ATM CircuitsOffnet PVC Circuits

Figure 12-26. View Offnet Circuit Dialog Box (Administrative Tab)


Restarting Offnet PVCs

This section describes how to restart an offnet PVC.

Purpose

When Restart is selected from the popup menu for an offnet PVC, an Admin Down and Admin Up command is sent to the offnet PVC. The Restart function is only available if the offnet PVC’s administrative state is Up.

To Restart an Offnet PVC

To restart an offnet PVC:


2. Right-click on the offnet PVC and select Restart from the popup menu.

A message appears, asking if you are sure you want to restart the offnet PVC.

3. Choose Yes.

An Admin Down and then an Admin Up command are sent to the offnet PVC.


ATM Round-trip Delay/Cell Loss Statistics



Round-trip delay (RTD) statistics measure the time it takes for a cell to be transmitted from one endpoint to the receiving endpoint and back to the originating endpoint. When the cell is received back, the RTD values are calculated and sent to the NavisXtend Statistics Server. Round-trip delay is measured in microseconds and one cell per minute is sent on each of the selected circuits.

In conjunction with round-trip delay, the cell loss statistic (CLS) is calculated on PVC, SPVC, and SVC endpoints for diagnostics or service level agreements (SLA). This statistic provides a cell count to determine lost cells during a looped round-trip interval. The difference between the cell count sent from one endpoint and the cell count received by the other endpoint, during a flow in a particular direction, provides the value of the cells lost. As with round-trip delay, CLS values are calculated and sent to the NavisXtend Statistics Server. For more information on the NavisXtend Statistics Server, see the NavisXtend Statistics Server User’s Guide.

Requirements

In order to access this feature, the software requirements are Solaris 8 operating system and Release 10.00.01.00 or later for NMS and switch software versions.

This feature will be supported on IOM1, IOM4, IOM4a, BIO1 and BIO2 on the CBX 3500, CBX 500, and GX 550 switches and ULC1 on the CBX 3500 switch. It is also supported on PSAX switches with Release V11.00.C00.00. For more information on PSAX, see the Release Note for Release 11.0.0 of the PacketStar® PSAX 4500, PSAX 2300, PSAX 1250, and PSAX 1000 Multiservice Media Gateways, Issue 1, July 29, 2005 (Doc. No.: 255-700-707R11.0).

Configuring ATM Round-trip Delay/Cell Loss Statistics

The RTD/CLS may be collected on the following circuits with ATM endpoints:

• Point-to-point PVCs

• Redirect PVCs

• Point-to-point SPVCs (VNN and PNNI)

• SVCs (VNN and PNNI)

The ATM RTD/CLS may be enabled or disabled through Navis EMS-CBGX. These statistics may be accessed via the NavisXtend Statistics Server. For more information on the NavisXtend Statistics Server, see the NavisXtend Statistics Server User’s Guide.



Monitoring ATM CircuitsATM Round-trip Delay/Cell Loss Statistics

Configuring RTD/CLS for PVCs

To configure RTD/CLS for point-to-point or redirect PVCs:


2. Right-click on the circuit and select OAM from the popup menu.

The PVC OAM Loopback dialog box appears (Figure 12-27).

Figure 12-27. PVC OAM Loopback Dialog Box

3. Choose the ATM Round Trip Delay Enable radio button to enable the RTD/CLS collection (Disable is the default).

For a description of the OAM loopback process and the fields in the PVC OAM Loopback dialog box, see “Running an OAM Loopback Test on an ATM Circuit” on page 12-73.

Note – The ATM Round Trip Delay and Aggregate Interval fields are active both at the originating endpoint and at the destination endpoint of a connection. However, no values will be displayed in the CLS Status, CLS Failure Code and CLS Int Period fields at the originating endpoint and at the destination endpoint of a connection.




Configuring RTD/CLS for Point-to-point SPVCs (VNN AND PNNI)

To configure RTD/CLS for point-to-point SPVCs:


2. Right-click on the Offnet PVC circuit and select OAM from the popup menu.

The OffNet OAM Loopback dialog box appears (Figure 12-28).

Figure 12-28. Offnet OAM Loopback Dialog Box (SPVC): Originating Endpoint


For a description of the OAM loopback process and the fields in the PVC OAM Loopback dialog box, see “Running an OAM Loopback Test on an ATM Circuit” on page 12-73. The loopback and ATM RTD/CLS fields are identical to those in the Offnet OAM Loopback dialog box.

Note – The ATM Round Trip Delay and Aggregate Interval fields are active only at the originating endpoint of a connection. They are greyed out at the destination endpoint of a connection. Likewise, values will be displayed in the CLS Status, CLS Failure Code and CLS Int Period fields only at the originating endpoint of a connection.



Monitoring ATM CircuitsATM Round-trip Delay/Cell Loss Statistics

Configuring RTD/CLS for SVCs (VNN and PNNI)

To configure RTD/CLS for SVCs:

1. Display the circuit (see “Viewing All Active SVCs” on page 11-13).

2. Right-click on the circuit and choose Diagnostics from the popup menu.

The SVC Diagnostics dialog box appears (Figure 12-29).

Figure 12-29. SVC Diagnostics Dialog Box: Destination Endpoint


For a description of the OAM loopback process and the fields in the PVC OAM Loopback dialog box, see “Running an OAM Loopback Test on an ATM Circuit” on page 12-73. The loopback and ATM RTD/CLS fields are identical to those in the SVC Diagnostics dialog box.

Note – The ATM Round Trip Delay and Aggregate Interval fields are active only at the originating endpoint of a connection. They are greyed out at the destination endpoint of a connection. Likewise, values will be displayed in the CLS Status, CLS Failure Code and CLS Int Period fields only at the originating endpoint of a connection.l

Beta Draft ConfidentialMonitoring ATM CircuitsATM Test Access Function


ATM Test Access Function

The ATM Test Access Function (ATAF) is supported on CBX 3500, CBX 500, and GX 550 switches. This section describes this feature and how to configure it.

ATAF Overview

Navis EMS-CBGX and the Provisioning Server support the Virtual Connection method of ATAF (ATAF-VC) and the Signaling Data Capture method of ATAF (ATF-SDC). The purpose of ATAF is to identify methods of access to an ATM cell stream. As specified by the ATM Forum’s ATM Test Access Function (ATAF) Version 1.0 specification, ATAF-VC provides the capability to access one or more connections (VPC or VCC) via a remotely accessible test access port. All user cells from a chosen cell stream will be replicated and sent to the ATAF test port. On Lucent CBX 500/3500 and GX 550 switches, this is achieved by modifying the port bit map/thread of the existing circuit on the ingress card to replicate the cells and send them to the designated test port. Replicating the cells based on the port bit map is non-intrusive.

Since the interface, VPI, and VCI used by a given circuit can change at the transit nodes due to re-routing, the monitoring will be stopped when the circuit to be monitored goes down or comes up on a different VPI/VCI at the transit switch.

To support ATAF, Navis EMS-CBGX provides ATAF services on logical ports that will be used exclusively in ATAF functions. The ATAF-enabled logical port will have functionality and configuration ability to support ATAF only.

The Test Access Path for an ATAF-VC connection (TAP-VC) is an ATM layer connection that carries an ATM layer cell stream under test from the ATM network element (ATM NE) to the ATM test equipment. Navis EMS-CBGX lets you add TAP-VCs to the ATAF-enabled logical port.

ATAF can be enabled on ATM UNI DCE and ATM UNI DTE logical port types while you are adding the logical port. You cannot enable ATAF on an existing logical port. Table 12-30 lists the modules on which an ATAF logical port can be created.

Table 12-30. Supported Modules

CBX 3500 IOMs CBX 500 IOMs GX BIO1/BIO2

24-port DS3 ULC ATM 4-port OC-3/STM-1 4-port OC-3/STM-1 Phy

16-port OC-3/STM-1 ULC ATM 1-port OC-12/STM-4 1-port OC-12/STM-4

4-port OC-12/STM-4 ULC ATM 8-port T1/E1 ATM

4-port OC-3/STM-1 8-port DS3/E3 ATM

8-port DS3/E3 ATM



Monitoring ATM CircuitsATM Test Access Function

The following restrictions apply to ATAF logical ports:

• Only one ATAF logical port can be configured per switch.

• ATAF can be enabled on the logical port only while adding the logical port, not while modifying it.

• An ATAF logical port can not be a virtual logical port.

• An ATAF logical port can not be a feeder logical port for other virtual logical ports.

• An ATAF logical port can not be configured on a card on which FCP is enabled.

• An ATAF logical port can not be used for normal call processing or in a PVC, SPVC, or SVC.

• Bandwidth specified after creating an ATAF logical port cannot be modified.

• An ATAF logical port will not support diagnostic testing.

• An ATAF logical port can not be configured on a Automatic Protection Switching (APS) link. An ATAF logical port can be configured on the same phy module where APS is configured, but the ATAF logical port cannot be configured on the same port as APS is configured.

• A maximum of 64 TAP-VC VPI/VCI instances can be created on an ATAF logical port.

• Once a logical port is configured to support ATAF services, that logical port must be deleted to disable the ATAF functionality. Additionally, runtime modifications to enable or disable the ATAF services are not available.

• ATAF logical ports cannot be created on IOM2, IOM4, IOM7, IOM6, and BIO5 cards.

• An ATAF enabled logical port will have functionality and configuration ability to support ATAF only.

• For ATAF-SDC logging, there shall be 100 records for UNI logical ports and 1000 records for NNI logical ports.

ATAF and PRAM

Adding, modifying, deleting, connecting, and disconnecting an ATAF TAP-VC will have no effect on PRAM functionality.

The TAP-VC objects will not be a part of the switch PRAM, but are instead maintained in the NMS database only. The switch will learn of the TAP-VC only when the user connects the ATAF TAP-VC to the resource cell stream.

ATAF-Virtual Connection Access Configuration

Use the following sequence to set up an ATAF-VC configuration:



Creating a TAP-VC Instance on the ATAF Monitoring Logical Port

To create a TAP VC Identifier in the Add TAP VC Identifiers dialog box:


2. Expand the ATAF logical port.

The TAP VCs class node appears (Figure 12-30).

Figure 12-30. TAP VCs Node

3. Right-click on the TAP VCs class node and select Add from the popup menu.

The Add TAP VC Identifiers dialog box appears (Figure 12-30).

Figure 12-31. Add TAP VC Identifiers Dialog Box

4. Complete the Add TAP VC Identifiers dialog box fields, as described in Table 12-31.

Step 1. Configure an ATAF monitoring logical port on a switch (see the ATM Services Configuration Guide for CBX 3500, CBX 500, GX 550, and B-STDX 9000).

Step 2. Create a TAP-VC instance on the ATAF monitoring logical port (see “Creating a TAP-VC Instance on the ATAF Monitoring Logical Port” on page 12-83).

Step 3. Select a cell stream to be monitored and connect to an available TAP-VC (see “Selecting a Cell Stream to be Monitored” on page 12-84).




5. When you are done configuring the TAP VC, choose OK.

The Add TAP VC Identifiers dialog box closes.

Selecting a Cell Stream to be Monitored

Once you have created the ATAF TAP-VC, you may connect it to a cell stream resource for monitoring.

Cell Stream Monitoring Restrictions

The following restrictions apply while connecting to a resource cell stream:

• Circuits can be monitored on the modules listed in Table 12-30 on page 12-81.

• Circuits passing through IOM2, IOM7, IOM6 or BIO-C modules cannot be monitored.

• Circuits passing through FCP-enabled cards cannot be monitored.

• Management VCs cannot be monitored.

• VC endpoint logical ports cannot be deleted if an ATAF TAP-VC is connected to that VC with the logical port as its endpoint.

Table 12-31. Add TAP VC Identifiers Dialog Box Fields

Field Action

TAP-VC ID (1-64) Enter a unique alphanumeric name to identify the TAP-VC. The TAP-VC ID will be assigned once the TAP-VC is created.

Connection Type Choose VCC or VPC. When VCC is selected, you must specify the TAP-VC VPI and TAP-VC VCI for the TAP-VC. When VPC is selected, only the TAP-VC VPI must be entered.

Access Mode Select the access mode for this TAP-VC from the following options in the pull-down list:

• Monitor Ingress Traffic. The cell stream is replicated on the ATAF Lport.

• Full Splitting Mode (Ingress). The cell stream is completely diverted to the ATAF Lport, with no cells going to the egress side.

Note – The Full Splitting Mode is only applicable to the IOM1 module on the CBX 3500.

TAP-VC VPI (0-15) Enter the TAP-VC VPI for this TAP-VC.

TAP-VC VCI (32-1023) Enter the TAP-VC VCI for this TAP-VC.



• A maximum of 64 cell streams may be monitored simultaneously in one switch, but a single TAP VC can be used to monitor a single cell stream.

• The VPI/VCI values for the cell stream to be monitored must be known to avoid failed connections.

• There may be a traffic disruption on the monitored cell stream, but it will be less than 50 ms.

Connecting a TAP-VC to a Cell Stream Resource

To connect the TAP-VC to a cell stream resource:




Figure 12-32. TAP VCs Node Expanded

3. Expand the TAP VCs class node.

4. Right-click on the TAP VC and select Connect from the popup menu.

The Connect TAP-VC Id Monitor Resources dialog box appears (Figure 12-33).

Figure 12-33. Connect TAP-VC ID Monitor Resources Dialog Box

5. In the LPorts Name column, select a logical port that you wish to monitor with the ATAF TAP-VC.




Note that the ATAF TAP-VC cell stream monitoring supports circuits traversing or originating on FAST APS 1+1 ports. Monitoring is available for the FAST APS 1+1 Working port. There is no monitoring option available directly on the Protection port. However, when a FAST APS 1+1 Working port switches to a Protection port, the configured ATAF TAP-VC automatically monitors the cell stream over the Protection port. The FAST APS 1+1 ports should be listed in the LPorts Name column when the TAP-VC is connected to the ATAF LPort.

6. Enter the Cell Stream VPI and Cell Stream VCI. These values are the identifiers used by the logical ports listed, which form the endpoints for the circuit to be monitored.

7. Choose OK.

The Connect TAP-VC Id Monitor Resources dialog box closes.

Viewing TAP-VC Operational Status

The following conditions apply to accessing the operational status of a TAP-VC:

• If the Admin status is Down for the module on which the ATAF logical port is configured, the operational information is disconnected.

• If the Admin status is Down for the physical port or logical port on which the ATAF TAP-VC is configured, the operational information is connected.

To view the operational status of a TAP-VC:






4. Right-click on the TAP VC and select Oper Info from the popup menu.

The TAP VC ID Resource Info dialog box appears (Figure 12-35).



Figure 12-35. TAP VC ID Resource Info Dialog Box

Table 12-32 describes the TAP-VC ID Resource Info dialog box information.

Table 12-32. TAP VC ID Resource Info Dialog Box Fields

Field Description

Connection Status Displays the status of the ATAF connection. Possible values are:

• Unused

• Connecting

• Connected

• Failed

• Down

Traffic Descriptor Displays the traffic descriptor combination, which specifies the traffic parameters used for traffic control on the monitored ATM cell stream.

QoS Displays the Quality of Service for the monitored ATM cell stream.

PCR Displays the Peak Cell Rate, which is the maximum allowed cell transmission rate (in cells per second). This object is used to qualify the forward PCR signaled at this ingress logical port and the backward PCR signaled at this egress logical port.

SCR Displays the Sustained Cell Rate, which is the maximum allowed cell transmission rate that is allowed over a given period of time on a given circuit. This parameter applies only to VBR traffic. It does not apply to CBR or UBR/ABR traffic.






The TAP VC ID Resource Info dialog box closes.

Viewing TAP-VC Statistics

The Statistics option will only be available if the TAP-VC is connected to a resource cell stream. To view the statistics of the number of ATM cells transmitted on the ATAF TAP-VC:




Figure 12-36. TAP VC Monitor Node

MBS Displays the Maximum Burst Size, which is the maximum number of cells that can be received at the peak cell rate. This allows a burst of cells to arrive at a rate higher than the SCR.

If the burst is larger than anticipated, the additional cells are either tagged or dropped. This parameter applies only to VBR traffic. It does not apply to CBR or UBR traffic.

Fail Reason Displays the reason a connection to the ATM cell stream failed, if any.

Effective BW Displays the effective bandwidth being utilized by this connection.

Available BW Displays the total available bandwidth for this connection.

Table 12-32. TAP VC ID Resource Info Dialog Box Fields (Continued)

Field Description




4. Expand the TAP VC.


The Statistics Monitoring dialog box appears (Figure 12-37).

Figure 12-37. TAP VC Statistics Monitoring Dialog Box

The AtafTapVcOutCells field displays the number of cells transmitted on the monitored cell stream.

6. If you want to reset the statistics to zero and begin a new collection of statistics, choose Reset.

7. When you are done viewing statistics, choose Close.

The Statistics Monitoring dialog box closes.

Modifying a TAP-VC

To modify a TAP-VC:








3. Expand the class node for the TAP VCs.

4. Right-click on a TAP VC instance node and select Modify from the popup menu.

The Modify TAP VC Identifiers dialog box appears (Figure 12-39).

Figure 12-39. Modify TAP VC ID Identifiers Dialog Box

5. Complete the Modify TAP VC Identifiers dialog box fields, as described in Table 12-33.

Note: The Connection Type and Access Mode fields are not supported when the TAP VC instance node is connected to a cell stream resource.

6. When you are done modifying the attributes, choose OK.

The Modify TAP VC Identifiers dialog box closes.

Table 12-33. Modify TAP VC Identifiers Dialog Box Fields

Field Action

TAP-VC VPI (0-15) Enter the TAP-VC VPI for this TAP-VC.

TAP-VC VCI (32-1023) Enter the TAP-VC VCI for this TAP-VC.



Deleting a TAP-VC

A TAP-VC can be deleted only if the resource being monitored has been disconnected. To delete a TAP-VC:





3. Expand the class node for the TAP VCs.

4. Right-click on a TAP VC instance node and select Delete from the popup menu.

A message appears, asking if you are sure you want to delete the selected object.

5. Choose OK.

ATAF SDC Logging

ATAF Signal Data Capture (SDC) involves the data capture activity on both receive and transmit sides of ATM access and interoffice signaling channels. It consists of maintaining a log of SSCOP PDUs and information about related timer expiration events. This feature is supported on IOM1, BIO1, BIO2, BIO-C, and IOM4 modules only.

To access ATAF SDC Logging:

1. Enable Signaling and ATAF SDC Status in the Configure SVC dialog box on the applicable LPort. (Refer to “Configuring SVC Parameters” in the ATM Services Guide for CBX 3500, CBX 500, GX 550, and B-STDX 9000.)

2. Right click on the selected LPort and choose the ATAF SDC Logging option from the pop-up menu. The ATAF SDC Logging dialog box appears (Figure 12-41).




Figure 12-41. ATAF SDC Logging Dialog Box: SDC Logging Tab

Table 12-11 describes the fields and buttons of the SDC Logging tab on the ATAF SDC Logging dialog box.

Table 12-34. SDC Logging Tab Dialog Box Fields and Buttons

Field Description

Filter Mask Select the type of message to be logged by checking the appropriate box.

Upload IP The IP address where the logging data file is stored.

Upload Path The path where the SDC Logging data is to be stored, that is, where the SDC log data is uploaded from switch to NMS.

When SDC Logging is started, the data is captured and is stored in the switch. When SDC Logging is stopped and an upload is done, the NMS gets this log file from the switch and stores it in the NMS file space.



3. Enable (check) the Poll and Stat checkboxes if these message types are desired. Otherwise, these checkboxes are disabled by default.

4. Choose Start. The SDC logging process begins.

5. Choose Stop. The SDC logging process stops.

6. Choose Upload. Binary files from the configured module are uploaded and the Upload IP and Upload Path fields are populated.

Oper Status Displays the status of the logging function.

Refresh Refreshes the operational information of ATAF SDC that can be viewed in the View SDC Logging tab dialog box for the selected Lport .

Start Starts SDC Logging. Before starting SDC Log-ging, select the type of message(s) you want to log. After the logging is started, the “Start” button is disabled. Note: You cannot start SDC logging if the Opera-tional Status is “Failed”.

Stop This button, which stops SDC Logging, is enabled after the logging starts.

Upload Uploads the logged data to the network management system.

Note: The logging has to be stopped before uploading the file.

The log file is placed under the /tftpboot directory. The system provides the unique file name under it to locate the uploaded log file. This file name is then sent to the NMS for it to view the logged data.

View Displays the specific file under the /tftpboot directory in the SDC View Log tab.

Note: If an uploaded file exists in the /tftpboot directory, then the “View” button is enabled and the file can be viewed in the View SDC Log tab.

On subsequent launches of the ATAF SDC Logging dialog box, the system checks if the /tftpboot directory contains an uploaded file and accordingly enables or disables the “View” button.

Close Closes the dialog box.

Table 12-34. SDC Logging Tab Dialog Box Fields and Buttons (Continued)

Field Description




7. Choose View. The View SDC Log tab opens (see Figure 12-42) with converted binary files for viewing.

Figure 12-42. ATAF SDC Logging Dialog Box: View SDC Log Tab

The View SDC Log tab displays the logging messages (operational information) for the types selected on the SDC Logging tab. Use the vertical scroll bar to view the messages.

Note: For PDU messages larger than 250 bytes, the last 32 bytes are captured in the logging process.



13

Monitoring Frame Relay Circuits

This chapter describes how to monitor Frame Relay circuits. Lucent switches support Frame Relay communications over the following types of circuits:

• Permanent Virtual Circuits (PVCs)

• Redirect PVCs

• Offnet PVCs

• Switched virtual circuits (SVCs)


This section describes how to view operational status for a Frame Relay circuit.

Before You Begin

You cannot view operational information for a circuit if you have set the switch to Unmanaged. The switch must be set to Manage.



To View the Operational Status of a Frame Relay Circuit1. Display the circuit (see “Displaying Circuits” on page 11-2).


The PVC Operational Information dialog box appears (Figure 13-1). The operational information dialog box fields are described in the following tables:



Monitoring Frame Relay CircuitsViewing Circuit Operational Status

• PVCs: Table 13-1 on page 13-3

• Redirect PVCs: Table 13-2 on page 13-4

• Offnet circuits: Table 13-3 on page 13-6

Table 13-4 on page 13-6 describes the inactive PVC operational information codes.

Figure 13-1. PVC Operational Information Dialog Box

Beta Draft ConfidentialMonitoring Frame Relay CircuitsViewing Circuit Operational Status



Field Displays...

Operational Status Displays the current operational status of the selected circuit. Messages include:

Active – The circuit is operational through the network end-to-end.

Inactive – The circuit is not operational. Check the Failure Reason at Endpoint 1 or Endpoint 2 fields for possible explanations.

Unknown – Navis EMS-CBGX cannot reach the higher-numbered node for status. (If the circuit is an intra-switch PVC, then Navis EMS-CBGX cannot reach the highest-numbered logical port.)

Invalid – The circuit definition is not found in the higher-numbered node. You may need to save the circuit definition; it may also be necessary to PRAM synch the host card.



Failure Reason at Endpoint 1 and Endpoint 2

The reason a selected circuit failed (if any) for a given endpoint. For CBX 500/3500 and GX 550 endpoints, also displays the failed LPort Name, Node ID, and IfIndex.









Field Displays...



Inactive – The circuit is not operational. Check the Failure Reason at Endpoint 1 or Endpoint 2 fields for possible explanations.

Unknown – Navis EMS-CBGX cannot reach the higher-numbered node for status. (If the circuit is an intra-switch PVC, then Navis EMS-CBGX cannot reach the highest-numbered logical port.)




Last Switchover Action The action taken at the most recent switchover. This diagnostic information can include the following resolutions:

• gopri-manual – switched over to primary endpoint, manually.

• gopri-ondemand – switched over to primary endpoint, automatically.

• gosec-manual – switched over to secondary endpoint, manually.

• gosec-ondemand – switched over to secondary endpoint, automatically.



Working Endpoint 2 The endpoint to which the PVC is currently established from the pivot endpoint (Endpoint 1). The working endpoint can be either the primary or the secondary endpoint.

Backup-Up Whether the circuit has a backup circuit (Yes or No).

Failure Reason at Pivot Endpoint The reason a selected circuit failed (if any) for a the pivot endpoint. For CBX 500/3500 and GX 550 endpoints, also displays the failed LPort Name, Node ID, and IfIndex.


Failure Reason at Endpoint 2 (Primary or Secondary)

The reason a selected circuit failed (if any) for the Endpoint 2 primary or secondary endpoint. (Choose the Primary or Secondary tab to see the information for that endpoint.)

For CBX 500/3500 and GX 550 endpoints, also displays the failed LPort Name, Node ID, and IfIndex.





Table 13-2. Redirect PVC Operational Information Dialog Box Fields (Continued)

Field Displays...




Table 13-3. View Offnet Circuit Operational InformationDialog Box Fields

Field Displays



Inactive – The circuit is not operational. Check the Failure Reason for Endpoint 1 or Endpoint 2 fields for possible explanations.

Unknown – The higher-numbered node cannot be reached for status.


Failure Reason The reason a selected circuit failed (if any). For CBX 500/3500 and GX 550 endpoints, also displays the failed LPort Name, Node ID, and IfIndex.





Table 13-4. Inactive PVC Operational Information Codes


Circuit Admin Status is Down

Circuit activity is disabled; the admin status is set to Down.

Reconfigure the circuit’s admin status to Up.

Internal Error: No VC Buffer at [node]

A shortage of virtual circuit buffers exists at the node.

Serious Error! Report problem to the Lucent Technical Assistance Center (TAC).



Not enough bandwidth on trunk at [node]

One of the trunks in the circuit path does not have enough bandwidth to accommodate the circuit.

Reconfigure the circuit to a lower bandwidth or increase the physical or virtual bandwidth of the trunk. You can also add more parallel trunks.

Keep in mind that increasing the physical or virtual trunk bandwidth will temporarily disrupt traffic on the trunk.

Destination node is unreachable at [node]

The destination node is not accessible from the higher numbered node.

Troubleshoot a possible connectivity problem with the unreachable switch.

Lucent circuit segment call has timed out

Attempts to establish the circuit (PVC) through the network have failed and timed out.

This problem may occur on a defined path where the alternate path option is disabled.

Internal error: No circuit PDU buffer at [node]

A shortage of protocol buffers exists.


OPTimum path flow is blocked at [node]

Data flow through the public data network is temporarily blocked due to the flow-control mechanism.

This condition should correct itself. If the problem persists, check for congestion in the OPTimum path.

Trunk is down at [node]

A trunk line in the circuit path is down.

The circuit automatically reroutes if alternate paths are defined.

UNI/NNI is down at [node, lport]

The UNI or NNI is down at the node/interface number (ifnum).

Verify that the switch is connected to the user device. Display traffic in and out of the port by generating summary statistics.

PVC segments are not ready to receive beyond [lport, node]

(NNI specific problem.) The PVC segments beyond this logical port sent a flow block message stating that it cannot receive data.

A trunk line in the circuit path may be down. Check the status of all PVC segments in the network beyond the logical port noted in the Fail Reason.






Warning: Defined Path is not available. The alternate path is in use. PVC segments are inactive beyond [lport, node]

The caller node cannot be reached through the defined path. This problem may be caused by a connection failure.

Verify the integrity of the trunk that is being used on the defined circuit path. Once the defined path is re-established, the circuit is routed back to the defined path within 20 seconds of availability.

IOP/IOM is down An input/output processor (IOP) or input/output module (IOM) used by the circuit is down.

Check the status of the IOM. See Chapter 2, “Viewing Network, Switch, Module, and Physical Port Details” for more information.

No PVC Manager PDU msg buffer

The PVC manager has no user message buffer for the protocol data unit (PDU).


Port is not configured

No logical port is configured for use by the PVC.

Configure a logical port for the PVC. See the Frame Relay Services Configuration Guide for CBX 3500, CBX 500, and B-STDX 9000 for details.

Mis-configuration Configuration error. Check the PVC attributes. See “Viewing Circuit Attributes” on page 11-6.

Source is in a ‘backup’ condition

The PVC switched over to a backup.

Check PVC attributes and statistics. See “Viewing Circuit Attributes” on page 11-6 and “Viewing Frame Relay SVC Summary Statistics” on page 13-26.

Source is unknown The PVC source is unknown. Check PVC attributes and statistics. See “Viewing Circuit Attributes” on page 11-6 and “Viewing Frame Relay SVC Summary Statistics” on page 13-26.

Destination is unknown

The PVC destination is unknown.






DLCI collision on backup

DLCI collision occurred during backup.


Node running incompatible version of switch software exists in circuit path

A switch that is running an incompatible version of software is in the circuit path.

Verify that all switches in the circuit path are running compatible versions of switch software.

SMDS management trunk

The PVC attempted to traverse an SMDS management trunk.

Reroute the PVC so that it does not traverse an SMDS management trunk.

Endpoint never called

The PVC connection was never established.


Both endpoints in ‘backup’

Both PVC endpoints are in a backup condition (that is, they are switching to backup PVCs).


Attempting to route through management trunk

The PVC attempted to traverse a management trunk.

Reroute the PVC so that it does not traverse a management trunk.

Route changed during setup

The PVC route failed because it changed during PVC setup.

Verify that the PVC route is stable during PVC setup.

Circuit path registration failed

Problems were encountered during PVC path registration.


No available bandwidth in reverse direction

No bandwidth in the reverse direction is available.

Check the PVC configuration to see if sufficient bandwidth is available.






3. If the Connection Trace button is active, choose the button to display information in the Actual Path.




PVC reset internally – reuse path

The PVC reset internally as a result of multicast DLCI configuration problems.

Check the multicast DLCI configuration. See “Viewing Multicast DLCIs” on page 8-15.

Disrupted due to priority routing

High priority circuit is in the PVC’s path. The PVC is disrupted due to priority routing.

Network congestion or other problems initiated priority-routing algorithms, which disrupted the PVC. This condition should clear as soon as the problems are corrected.

Couldn’t allocate negative priority bandwidth

No negative priority bandwidth could be allocated.

Check the PVC configuration to see if there is sufficient bandwidth available.



Beta Draft ConfidentialMonitoring Frame Relay Circuits

Viewing Frame Relay PVC Summary Statistics



Frame Relay circuit summary statistics display the packets a circuit has sent and received, the round-trip delay, and other QoS statistics for the circuit.


• “Frame Relay PVC Summary Statistics Overview” on page 13-11

• “To View Frame Relay PVC Summary Statistics” on page 13-11

Frame Relay PVC Summary Statistics Overview

Frame Relay circuit summary statistics display the number of cells a circuit has sent and received, the round-trip delay, and other Quality of Service statistics for the circuit.

Summary statistics are available for the following:

• PVCs

• Redirect PVCs

• Offnet PVCs

To View Frame Relay PVC Summary Statistics

To view summary statistics for a Frame Relay circuit:

1. Display the circuit for which you want to view summary statistics (see “Displaying Circuits” on page 11-2).

2. Expand the circuit (Figure 13-2).

Figure 13-2. PVC Monitor Node



Monitoring Frame Relay CircuitsViewing Frame Relay PVC Summary Statistics


The circuit statistics monitoring dialog box appears (Figure 13-3).

The fields for the circuit statistics monitoring dialog box are described in Table 13-5 on page 13-12.

For Frame-to-ATM circuits, ATM statistics appear for the ATM end of the circuit, and Frame Relay statistics appear for the Frame Relay end of the circuit. See “Viewing ATM Circuit Summary Statistics” on page 12-34 for a description of ATM circuit statistics.


Table 13-5. Circuit Statistics Monitoring Dialog Box Fields (Frame Relay)

Field Description

Circuit Name The name of the circuit.


Number of Frames The total number of frames received and transmitted over the specified logical ports since the last reset.




Green Frames The total number of green frames received and transmitted over the specified logical ports since the last reset.

Green frames are never discarded by the network, except under extreme circumstances (such as node or link failure). Green frames identify packets where the number of bits received during the current time interval, including the current frame, is less than the committed burst size.

Amber Frames The total number of amber frames received and transmitted over the specified logical ports since the last reset.

Amber frames are forwarded with the discard eligible (DE) bit set and are eligible for discard if they pass through a congested node. Amber frames identify packets where the number of bits received during the current time interval, including the current frame, is greater than the committed burst size, but less than the excess burst size.

Red Frames The total number of red frames received and transmitted over the specified logical ports since the last reset.

Red packets are forwarded with the DE bit set when the Graceful Discard feature is set to On. When the Graceful Discard feature is set to Off, red packets are discarded.

Red packets are designated as those bits received during the current time interval that exceed the committed burst size and excess burst size thresholds, including the current frame.

Number of Octets The total number of octets (bytes) received and transmitted over the specified logical ports since the last reset.

Green Octets The total number of green octets (bytes) received and transmitted over the specified logical ports since the last reset.

Green octets are never discarded by the network, except under extreme circumstances (such as node or link failure).

Amber Octets The total number of amber octets (bytes) received and transmitted over the specified logical ports since the last reset.

Amber octets are eligible for discard if they pass through a congested node.

Red Octets The total number of red octets (bytes) received and transmitted over the specified logical ports since the last reset.


Table 13-5. Circuit Statistics Monitoring Dialog Box Fields (Frame Relay) (Continued)

Field Description



Monitoring Frame Relay CircuitsViewing Frame Relay PVC Summary Statistics


Frames Discarded The number of frames discarded. Congested nodes within the network that must discard packets use the color designations to determine which frames to discard. Red frames are discarded first, followed by amber and green.

Throughput


Packets per second The number of packet frames transmitted and/or received each second.

Utilization (%)

Endpoint 1 Utilization A

The amount of traffic queued for transmission on a circuit as a percentage of the CIR. For this reason, the value displayed in circuit utilization A can exceed 100%.

Endpoint 2 Utilization B

The amount of traffic queued for transmission on a circuit as a percentage of the CIR. For this reason, the value displayed in circuit utilization B can exceed 100%.

Congestion Statistics

FECN Frames The number of frames that were received or transmitted with the Forward Explicit Congestion Notification (FECN) bit set to 1. The network sets a FECN bit to 1 if the network is encountering congestion. FECN frames indicate that there may not be sufficient network resources to continue handling the submitted traffic at the current rate.

BECN Frames The number of frames that were received or transmitted with the Backward Explicit Congestion Notification (BECN) bit set to 1. The network sets a BECN bit to 1 if the network is encountering congestion. BECN frames indicate that there may not be sufficient network resources to continue handling the submitted traffic at the current rate.

Table 13-5. Circuit Statistics Monitoring Dialog Box Fields (Frame Relay) (Continued)

Field Description


Viewing 2-port ULC Gigabit Ethernet LPort Circuit Summary Statistics for Ethernet to Frame Relay End-



The Circuit Statistics Monitoring dialog box closes.

Viewing 2-port ULC Gigabit Ethernet LPort Circuit Summary Statistics for Ethernet to Frame Relay Endpoints

To view 2-port ULC Gigabit Ethernet LPort circuit summary statistics for ethernet to Frame Relay endpoints:



3. Right-click on the Monitoring node for the LPort ethernet to Frame Relay circuit, and choose Start from the popup menu.

The LPort Circuit Statistics Monitoring dialog box appears (Figure 13-4 and Figure 13-5) for the 2-port ULC Gigabit Ethernet module. (Note: You must use



Monitoring Frame Relay CircuitsViewing 2-port ULC Gigabit Ethernet LPort Circuit Summary Statistics for Ethernet to Frame Relay End-

the vertical scroll bar to see all of the fields in this dialog box.) Table 13-6 describes the fields for the LPort Circuit Statistics Monitoring dialog box.

Figure 13-4. 2-port ULC Gigabit Ethernet LPort Circuit Statistics

Monitoring Dialog Box, Ethernet to Frame Relay (Part 1)




Figure 13-5. 2-port ULC Gigabit Ethernet LPort Circuit Statistics Monitoring Dialog Box, Ethernet to Frame Relay (Part 2)

Table 13-6. 2-port ULC Gigabit Ethernet LPort Circuit Statistics Monitoring, Ethernet to Frame Relay

Field Description

EndPoint 1

Properties











QoS:


TrafficDescriptor:

CIR(Kbps): Displays the committed information rate for this logical port.

CBS(Kbps): Need description

EIR(Kbps): Need description

EBS(Kbps): Need description






Red packets are forwarded with the DE bit set when the Graceful Discard feature is set to On. When the Graceful Discard feature is set to Off, red packets are discarded. Red packets are designated as those bits received during the current time interval that exceed the committed burst size and excess burst size thresholds, including the current frame.

Table 13-6. 2-port ULC Gigabit Ethernet LPort Circuit Statistics Monitoring, Ethernet to Frame Relay (Continued)

Field Description





Amber Octets Displays the total number of amber octets (bytes) received and transmitted over the specified logical ports since the last reset. Amber octets are eligible for discard if they pass through a congested node.




Amber Octets High Displays the high number of amber octets (bytes) received and transmitted over the specified logical ports since the last reset.

Red Octets High Displays the high number of red octets (bytes) received and transmitted over the specified logical ports since the last reset.

Throughput


Utilization


NDC Statistics

NDC History Choose the network data collection (NDC) history from the pull-down list for Current, 1st 15 Minute, and 2nd 15 Minute statistics.

Timed Elapsed Displays the time elapsed since the last NDC history was set.



Field Description








Lport Throughput



Utilization(%) Displays the amount of traffic received and transmitted on this logical port as a percentage of the committed information rate (CIR). It does not measure the amount of bandwidth of the logical port, so the value that the system displays in this field can exceed 100%.

EndPoint 2

Properties








QoS:



Field Description




TrafficDescriptor:

CIR(Kbits): Displays the committed information rate for this logical port.

BC(Kbits): Displays the committed burst size for this logical port.

BE(Kbits): Displays the excess burst size for this logical port.

SCR(cells/sec): Specifies the sustainable cell rate (SCR). The SCR defines the average rate, in cells per second (CPS), at which cells are transmitted from endpoint 2. The SCR must be less than or equal to the peak cell rate (PCR) for endpoint 2.

MBS(cells/sec): Specifies the maximum burst size (MBS) for endpoint 2, in number of cells. This value determines the maximum number of cells that can be transmitted at the PCR.

PCR(cells/sec): Specifies the peak cell rate (PCR). The PCR defines the maximum rate, in cells per second, at which cells are transmitted from endpoint 2.



Green Frames Displays the total number of green frames received and transmitted over the specified logical ports since the last reset.


Amber Frames Displays the total number of amber frames received and transmitted over the specified logical ports since the last reset.

Amber frames are forwarded with the discard eligible (DE) bit set and are eligible for discard if they pass through a congested node. Amber frames identify packets where the number of bits received during the current time interval, including the current frame, is greater than the committed burst size, but less than the excess burst size.


Field Description







Frames Discarded Displays the number of frames discarded. Congested nodes within the network that must discard packets use the color designations to determine which frames to discard. Red frames are discarded first, followed by amber and green.


Green Octets Displays the total number of green octets (bytes) received and transmitted over the specified logical ports since the last reset.


Amber Octets Displays the total number of amber octets (bytes) received and transmitted over the specified logical ports since the last reset.




Throughput


Frames per second Displays the total number of frames received and transmitted by the circuit each second.


Field Description




Utilization


CongestionStatistics

FECNFrames Displays the number of frames that were received or transmitted with the Forward Explicit Congestion Notification (FECN) bit set to 1. The network sets an FECN bit to 1 if the network is encountering congestion. FECN frames indicate that there may not be sufficient network resources to continue handling the submitted traffic at the current rate.

BECNFrames Displays the number of frames that were received or transmitted with the Backward Explicit Congestion Notification (BECN) bit set to 1. The network sets a BECN bit to 1 if the network is encountering congestion. BECN frames indicate that there may not be sufficient network resources to continue handling the submitted traffic at the current rate.


NumberOfFrameErrors Displays the total number of frames that were received with a Header Error Control (HEC) error. An HEC error indicates a discrepancy between what the port expected in the header and what was actually received. The number of frame errors is indicated in the Received column. The Transmitted column does not apply.

NumberOfOctets Displays the total number of octets (bytes) received and transmitted since the last reset.

NumberOfFramesDiscarded Displays the total number of discarded frames since the last reset.

NumberOfUnicastFrames Displays the total number of unicast frames received and transmitted since the last reset.

Lport Throughput

ThroughPutFramesPerSecond

Displays the throughput at the endpoint 2 Lport in frames per second.



Field Description



Monitoring Frame Relay CircuitsViewing CAC Parameters for Frame Relay Circuits

For additional information on circuit summary statistics for ethernet to ATM endpoints, see “Viewing 2-port ULC Gigabit Ethernet LPort Circuit Summary Statistics for Ethernet to ATM Endpoints” on page 12-42 .

Viewing CAC Parameters for Frame Relay Circuits


• “About CAC” on page 13-24

• “To View CAC Parameters” on page 13-24

About CAC

ATM and Frame Relay I/O modules that support Priority FrameTM share common Call Admission Control (CAC) QoS objectives that can be configured and monitored through Navis EMS-CBGX.

The switch uses a fixed average frame size and Frame Relay traffic descriptors to calculate the maximum burst size (MBS), sustained frame rate (SFR) and peak frame rate (PFR) for each circuit, as follows:

MBS = Bc/Avg. Frame SizeSFR = CIR/Avg. Frame SizePFR = (CIR + EIR)/Avg. Frame SizeEIR = Be/Tc (where Tc = Bc/CIR)

EIR is the information rate during excess traffic periods.

To View CAC Parameters

To view the Lucent CAC parameters that have been configured for circuits on a switch:


Utilization(%) Displays the amount of traffic received and transmitted on a logical port as a percentage of the committed information rate (CIR). It does not measure the amount of bandwidth of the logical port, so the value that the system displays in this field can exceed 100%.


Field Description


Viewing CAC Parameters for Frame Relay Circuits


1. In the switch tab (see “Displaying a Switch Tab in the Navigation Panel” on page 2-6), right-click on the switch and select Set CAC Parameters from the popup menu.

The Set All CAC Parameters dialog box appears (Figure 13-6). For a description of the attributes, see the ATM Services Configuration Guide for CBX 3500, CBX 500, GX 550, and B-STDX 9000.

Figure 13-6. Set All CAC Parameters Dialog Box

2. When you have completed viewing the CAC parameters, choose Cancel.

The Set All CAC Parameters dialog box closes.



Monitoring Frame Relay CircuitsViewing Frame Relay SVC Summary Statistics

Viewing Frame Relay SVC Summary Statistics


• “SVC Summary Statistics Overview” on page 13-26

• “To View Frame Relay SVC Summary Statistics” on page 13-26

SVC Summary Statistics Overview

This section describes how to monitor Frame Relay SVCs in a Lucent network. You can check the status of configured SVC parameters and view statistics on SVC activity. For more information on Frame Relay SVCs, see the Frame Relay Services Configuration Guide for CBX 3500, CBX 500, and B-STDX 9000.

To View Frame Relay SVC Summary Statistics

To view Frame Relay SVC summary statistics:

1. Display the active SVC for which you want to view summary statistics (see “Viewing All Active SVCs” on page 11-13).

2. Expand the SVC (Figure 13-7).

Figure 13-7. SVC Monitor Node


The SVC Statistics Monitoring dialog box appears (Figure 13-8), showing statistics for a Frame Relay Endpoint 2.

The SVC Statistics Monitoring dialog box fields are described in Table 13-7 on page 13-27.




For Frame-to-ATM circuits, ATM statistics appear for the ATM end of the circuit, and Frame Relay statistics appear for the Frame Relay end of the circuit. See “Viewing ATM SVC Summary Statistics” on page 12-64 for a description of ATM SVC statistics.

Figure 13-8. SVC Statistics Monitoring Dialog Box (Frame Relay Endpoint 2)

Table 13-7. SVC Statistics Monitoring Dialog Box Fields (Frame Relay)

Field Description


Total Frames The total number of frames received and transmitted over the specified logical ports since the last reset.

Green Frames The total number of green frames received and transmitted over the specified logical ports since the last reset.




Monitoring Frame Relay CircuitsViewing Frame Relay SVC Summary Statistics

Amber Frames The total number of amber frames received and transmitted over the specified logical ports since the last reset.

Amber frames are forwarded with the Discard Eligible (DE) bit set and are eligible for discard if they pass through a congested node. Amber frames identify packets where the number of bits received during the current time interval, including the current frame, is greater than the committed burst size, but less than the excess burst size.

Red Frames The total number of red frames received and transmitted over the specified logical ports since the last reset.



Total Octets The total number of octets (bytes) received and transmitted over the specified logical ports since the last reset.

Green Octets The total number of green octets (bytes) received and transmitted over the specified logical ports since the last reset.


Amber Octets The total number of amber octets (bytes) received and transmitted over the specified logical ports since the last reset.


Red Octets The total number of red octets (bytes) received and transmitted over the specified logical ports since the last reset.


Frames Discarded The number of frames discarded. Congested nodes within the network that must discard packets use the color designations to determine which frames to discard. Red frames are discarded first, followed by amber and green.

Throughput


Table 13-7. SVC Statistics Monitoring Dialog Box Fields (Frame Relay) (Continued)

Field Description






The SVC Statistics Monitoring dialog box closes.

Packets per second

The number of packet frames transmitted and/or received each second.

Congestion Statistics

FECN Frames The number of frames that were received or transmitted with the Forward Explicit Congestion Notification (FECN) bit set to 1. The network sets a FECN bit to 1 if the network is encountering congestion. FECN frames indicate that there may not be sufficient network resources to continue handling the submitted traffic at the current rate.

BECN Frames The number of frames that were received or transmitted with the Backward Explicit Congestion Notification (BECN) bit set to 1. The network sets a BECN bit to 1 if the network is encountering congestion. BECN frames indicate that there may not be sufficient network resources to continue handling the submitted traffic at the current rate.

Utilization (%)

Endpoint 1 Utilization (%)

The amount of traffic queued for transmission on a circuit as a percentage of the CIR. For this reason, the value displayed in circuit utilization A can exceed 100%.

Endpoint 2 Utilization (%)

The amount of traffic queued for transmission on a circuit as a percentage of the CIR. For this reason, the value displayed in circuit utilization B can exceed 100%.

Table 13-7. SVC Statistics Monitoring Dialog Box Fields (Frame Relay) (Continued)

Field Description



Monitoring Frame Relay CircuitsTesting Frame Relay PVCs

Testing Frame Relay PVCs

PVC loopback is a diagnostic tool for testing the transmission of data across a Frame Relay PVC at the UNI/NNI. The PVC loopback test loops back all data frames at the configured endpoint. You can set either endpoint of a PVC as a loopback endpoint. This means that all data sent to the PVC can be routed along the entire customer transmission path and be received on either the local or remote PVC endpoint.

PVC Loopback Settings

You can configure each PVC endpoint with one of the following loopback settings:

• None — No loopback is in effect.

• Local — Traffic arriving on the logical port from a CPE should be looped back to that CPE on the same logical port. See Figure 13-9 and Figure 13-10 for two examples of local PVC loopbacks.

• Remote — Traffic arriving from a far-end logical port/CPE should be looped back to that logical port/CPE. See Figure 13-11 and Figure 13-12 for two examples of remote PVC loopbacks.

• Both — Both remote and local traffic should loop back.

• Remote Ignore Local — This enhanced PVC loopback setting allows you to configure both ends of a PVC to remote loopback without regarding the status of the physical UNI/NNI port. In this state, the VC is enabled to count once-a-minute QoS packets. In previous releases, these packets could not be counted because they did not represent user traffic. This setting enables you to provision and test PVCs before making physical UNIs operational.

Note – PVC loopback can be used on an ATM PVC if one end of the PVC resides on a B-STDX 9000 switch. PVC loopback is not available for ATM PVCs when both endpoints reside on either a CBX 500, a CBX 3500 switch or a GX 550 Multiservice WAN Switch. In this case, use the OAM Loopback test instead. See “Testing ATM Circuits” on page 12-69 for more information.

Note – Note that physical and logical port statistics on the UNI port will not reflect traffic on the PVC.




Figure 13-9 illustrates a PVC loopback that has Endpoint A set to Local and Endpoint B set to None.

Figure 13-9. PVC Endpoint A Set to Local, Endpoint B Set to None

Figure 13-10 illustrates a PVC loopback that has Endpoint A set to None and Endpoint B set to Local.

Figure 13-10. PVC Endpoint A Set to None, Endpoint B Set to Local

Figure 13-11 illustrates a PVC loopback that has Endpoint A set to Remote and Endpoint B set to None.

Figure 13-11. PVC Endpoint A Set to Remote, Endpoint B Set to None

Note – In all following figures that illustrate the PVC loopback settings, Router 1 and Router 2 transmit data over the PVC.

Graceful Discard must be set to On for the PVC loopback function to operate correctly.

Router 1 Router 2A B

Local None


LocalNone


Remote None




Figure 13-12 illustrates a PVC loopback that has Endpoint A set to None and Endpoint B set to Remote.

Figure 13-12. PVC Endpoint A Set to None, Endpoint B Set to Remote

When to Use PVC Loopback

PVC loopback can be used with active PVCs only, if any of the following problems exist:

• Data is not successfully transmitting from one endpoint to the other endpoint of a defined circuit.

• There is slow response across a circuit path.

• Frames are being lost across a circuit path.

Problems PVC Loopback Can Detect

PVC loopback enables you to determine the following circuit problems:

• If the logical level of a circuit path is functioning properly

• Where a fault may exist in the circuit path

• If a congestion problem exists on the circuit path

See “Setting a PVC Loopback” on page 13-32 to set a PVC loopback. See “Checking the PVC Loopback Status” on page 13-34 to view PVC loopback status.

Setting a PVC Loopback

When you add a PVC, the system automatically assigns a PVC state of None to each endpoint. Use the following steps to set the state of each PVC endpoint:

1. Display the PVC for which you want to configure the loopback (see “Displaying Circuits” on page 11-2).

2. Right-click on the circuit and select Modify from the popup menu.

The Modify PVC dialog box appears (Figure 13-13).


RemoteNone




Figure 13-13. Modify PVC Dialog Box: User Preference Tab

3. Select the User Preference tab.

4. Select a PVC loopback status from the PVC Loopback Status fields pull-down list in both the forward and reverse directions. The possible choices are:

• None

• Local

• Remote

• Both

• Remote Ignore Local

Table 13-8 lists the valid PVC loopback combinations for the forward and reverse loopback specifications.

See “PVC Loopback Settings” on page 13-30 for a complete description of the settings.

It is not possible to set the loopback status to Remote at both endpoints of a PVC at the same time, unless you choose the Remote Ignore Local - Remote Ignore Local option. In addition, the Remote and Remote Ignore Local loopback settings do not apply to circuits that originate and terminate in the same switch.

If both ends of a PVC terminate to user ports on the same node, use only those combinations marked with an asterisk (*) in Table 13-8.




5. When you are done setting the loopback status, choose OK.


6. To monitor a PVC loopback results, view the summary statistics for the PVC (see “Viewing Frame Relay PVC Summary Statistics” on page 13-11).

Checking the PVC Loopback Status

To determine whether a PVC loopback status is in effect:

1. Display the PVC for which you want to view the loopback status (see “Displaying Circuits” on page 11-2).


The View PVC dialog box appears (Figure 13-13).

Table 13-8. Valid PVC Loopback Combinations

Loopback Status for Forward Direction

Loopback Status forReverse Direction

None None*

Local None*

None Local*

Remote None

None Remote

Both None

None Both

Local Local*

Remote Ignore Local None

Remote Ignore Local Remote Ignore Local




Figure 13-14. View PVC Dialog Box: User Preference Tab

3. Select the User Preference tab.

4. The PVC loopback is displayed in the PVC Loopback Status field for both the forward and reverse directions.

5. When you are done viewing the loopback status, choose OK.

The View PVC dialog box closes.



Monitoring Frame Relay CircuitsFrame Relay OAM Testing on PVCs (6-Port Channelized DS3/1/0 Frame Relay I/O Modules)

Frame Relay OAM Testing on PVCs (6-Port Channelized DS3/1/0 Frame Relay I/O Modules)

This section describes how to configure and run Frame Relay Operations, Administration, and Maintenance (OAM) circuit testing on the 6-Port Channelized DS3/1/0 Frame Relay I/O Module. Frame Relay OAM is not available on other Lucent modules.

This section includes the following sections:

• “About Frame Relay OAM” on page 13-36

• “Configuring and Running Frame Relay OAM” on page 13-40

• “Disabling Frame Relay OAM Capabilities on a Logical Port” on page 13-48

About Frame Relay OAM

The Frame Relay OAM features (FRF.19) provide a way to test, diagnose, and measure the quality of Frame Relay circuits.

This section includes the following topics:

• “Types of Circuits Supported” on page 13-36

• “Administrative Domains and Monitoring Points” on page 13-36

• “Frame Relay OAM Measurements” on page 13-39

Types of Circuits Supported

The following Frame Relay circuits support Frame Relay OAM on the 6-Port Channelized DS3/1/0 Frame Relay IOM:

• PVCs

• Offnet PVCs

• SVCs

Administrative Domains and Monitoring Points

Configuring 6-Port Channelized DS3/1/0 Frame Relay I/O Modules for Frame Relay OAM measurements involves monitoring points and administrative domains.

Monitoring Points

The Frame Relay OAM activities on a circuit take place between monitoring points (MPs), which you define on UNI DCE, UNI DTE, and NNI LPorts on 6-Port Channelized DS3/1/0 Frame Relay IOMs. MLFR and point-to-point LPorts cannot be configured as MPs. Other Lucent modules do not support Frame Relay OAM MPs.




When you begin Frame Relay OAM monitoring on a circuit, you identify the near-end and far-end MPs that will be used in the monitoring process.

Figure 13-15 shows MPs configured on two circuits within a Lucent network.

Figure 13-15. Administrative Domain: Single Lucent Network

Administrative Domains

In order to monitor the Frame Relay OAM circuit activity between two MPs, the MPs must be in the same administrative domain. This is accomplished by assigning the same Domain ID to each MP through the Add Logical Port dialog box.

An administrative domain may consist of one Lucent network (Figure 13-15), multiple Lucent networks managed by the same Navis EMS-CBGX system (Figure 13-16), or a Lucent network and a piece of equipment in a non-Lucent network (Figure 13-17).

By default, the Domain ID assigned to a logical port is the most significant two octets of the switch IP address. The default Domain ID values may not be used when the administrative domain consists of multiple Lucent networks or a Lucent network and a non-Lucent network, because the Domain IDs would not all be identical. For example, in Figure 13-16, the default Domain IDs for the MPs at CBX 1 and CBX 4 are not identical. The values need to be changed in order for the MPs to belong to the same administrative domain.

CBX 1

CBX 2

CBX 36 Port FR DS3/1/0 Module

MP

MP

MP

MP

6 Port FR DS3/1/0 Modules

Circuit A

Circuit B




Figure 13-16. Administrative Domain: Multiple Lucent Networks

Figure 13-17. Administrative Domain: Lucent and Non-Lucent Network

CBX 1


MPMP

CBX 2

Segment A

Lucent Network A

CBX 3


MPMP

CBX 4

Segment B

Lucent Network B

Non-Lucent network

Non-Lucent Equipment

MP

Non-Lucent Network

6 Port FR DS3/1/0 Module

MP

CBX

Lucent Network




Location ID for an MP

Each MP is assigned a Location ID in the Add Logical Port dialog box, and that Location ID must be unique for each MP within an administrative domain. By default, the Location ID for a logical port is a combination of the least significant two octets of the switch IP address and the interface number of the logical port.

When the administrative domain is formed by multiple Lucent networks or a Lucent and a non-Lucent network, you must change the default Location IDs for the MPs if they are not unique. You make this change in the Modify Logical Port dialog box.

Boundary Location MPs

You can define an MP as a “Boundary Location,” which means that it will not forward any OAM frames intended for that administrative domain. For example, if the MP on CBX 2 in Figure 13-16 is enabled as a Boundary Location, then OAM frames will not be forwarded to the MPs on CBX 3 and CBX 4. If a boundary point MP receives any OAM frame intended for a different administrative domain, it will forward those frames.

Frame Relay OAM Measurements

Measurements that can be made with Frame Relay OAM:

• Frame Transfer Delay

The Frame Transfer Delay (FTD) measurement reports the time required to transport Frame Relay data through the network. The FTD measurement is the difference in milliseconds between the time a frame exits a source and the time the same frame enters the destination. Once started, the FTD measurement is periodically made between the near-end and far-end MPs configured in that circuit.

• Frame Delivery Ratio

The Frame Delivery Ratio (FDR) measurement reports the network’s effectiveness in transporting an offered Frame Relay load in one direction of a circuit. The FDR is a ratio of successful frame receptions to attempted frame transmissions. Once started, the FDR measurement is periodically made between the near-end and far-end MPs configured in that circuit.

• Data Delivery Ratio

The Data Delivery Ratio (DDR) measurement reports the network’s effectiveness in transporting offered data in one direction of a circuit. The DDR is the ratio of the successful payload octets received to the attempted payload octets transmitted. Once started, the DDR measurement is periodically made between the near-end and far-end MPs configured in that circuit.

• Loopback Testing

Frame Relay OAM loopback testing is performed on a circuit between the near-end and far-end MPs. Two types of loopback testing are supported:




– Non-Latching Loopback — The non-latching loopback message causes only the non-latching loopback message itself to be looped back to the initiator, without affecting the data traffic in the circuit. Navis EMS-CBGX reports whether or not the loopback message that was sent to the far-end MP was successfully returned to the near-end MP.

– Latching Loopback — The latching loopback removes the circuit from service. All frames on the circuit arriving at the near-end MP (forward direction) will be discarded there. All frames on the circuit arriving at the far-end MP (reverse direction) will be discarded there. The far-end MP will still process the Frame Relay OAM frames from the near-end MP, as usual. Other circuits passing through these logical ports are not affected. Test frames will be generated from the near-end MP, transmitted towards the far-end MP, and looped back at the far-end MP towards the near-end MP. Navis EMS-CBGX reports the number of test frames that were transmitted and the number of test frames that were looped back.

Configuring and Running Frame Relay OAM

The steps involved in Frame Relay OAM include:

1. Configure the MPs (see “Configuring the Monitoring Points” on page 13-40).

2. Run Frame Relay OAM (see “Running Frame Relay OAM on a Circuit” on page 13-43)

Configuring the Monitoring Points

To configure a UNI DCE, UNI DTE, or NNI logical port on the 6-Port Channelized DS3/1/0 Frame Relay I/O Module as an MP, perform the following steps:

1. Access the FRF.19 attributes for a logical port with either of the following methods:

• If you are adding a new logical port, go to the FRF.19 tab (see the Frame Relay Services Configuration Guide for CBX 3500, CBX 500, and B-STDX 9000).

• If the logical port already exists:

– Right-click on the logical port (see “Displaying Logical Ports” on page 6-1) and select Modify from the popup menu. The Modify Logical Port dialog box appears (Figure 13-18).

– Select the FRF.19 tab.




Figure 13-18. Modify Logical Port, FRF.19 Tab

2. Complete the Modify Logical Port dialog box fields as described in Table 13-9:

Table 13-9. Modify Logical Port: FRF.19 Tab Fields


FTD Support Select the check box to enable FTD measurements for circuits that pass through this logical port.

Clear the check box (default) to disable FTD measurements.

FTD measurements can be made only if both the near end and far end MPs for a Frame Relay OAM test have FTD enabled.

See “Frame Relay OAM Measurements” on page 13-39 for more information.

FDR Support Select the check box to enable FDR measurements for circuits that pass through this logical port.

Clear the check box (default) to disable FDR measurements.

FDR measurements can be made only if both the near end and far end MPs for a Frame Relay OAM test have FDR enabled.

See “Frame Delivery Ratio” on page 13-39 for more information




DDR Support Select the check box to enable DDR measurements for circuits that pass through this logical port.

Clear the check box (default) to disable DDR measurements.

DDR measurements can be made only if both the near end and far end MPs for a Frame Relay OAM test have DDR enabled.

See “Data Delivery Ratio” on page 13-39 for more information.

Latching LoopBack Support

Select the check box to enable latching loopbacks for circuits that pass through this logical port.

Clear the check box (default) to disable latching loopbacks measurements.

See “Loopback Testing” on page 13-39 for more information.

Non Latching LoopBack Support

Select the check box to enable non-latching loopbacks for circuits that pass through this logical port.

Clear the check box (default) to disable latching loopbacks measurements.

See “Loopback Testing” on page 13-39 for more information.

Domain ID Scheme From the pull-down list, select one of the following schemes for the domain ID:

OUI — (Organizationally Unique Identifier) The format is a zero byte followed by a 3-octet OUI, which is administered by the IEEE.

IPV4 (default) — The format is the network portion of a public IPV4 address block owned by the service provider.

X.121 — The format is X.121 data network identification code (DNIC), as defined in X.76, padded on the left with zeros to fill 8 octets, and then BCD-encoded into 4 octets.

E.164 — The format is the E.164 Network Identification Field of the Transit Network ID, as defined in X.76, padded on the left with zeros to fill 8 octets, and then BCD-encoded into 4 octets.

Domain ID Enter a value for the domain ID. Use the format you chose in the Domain ID Scheme field. By default, the Domain ID value is the first two octets of the switch IP address. If MPs are in different networks, the default value cannot be used. See “Administrative Domains” on page 13-37 for more information.

Table 13-9. Modify Logical Port: FRF.19 Tab Fields (Continued)





3. When you are done modifying or adding the logical port, choose OK to save the changes.

Running Frame Relay OAM on a Circuit

To run Frame Relay OAM on a circuit:

Location ID Displays the default Location ID. The default Location ID for a logical port is a combination of the least significant two octets of the switch IP address and the interface number of the logical port.

The Location ID for all MPs within an administrative domain must be unique. When the administrative domain is formed by multiple Lucent networks or a Lucent and a non-Lucent network, the default values for the Location IDs might not be unique. In this case, use the Modify Logical Port dialog box to change default Location IDs.

Hello TX Timer Enter the length of time (in seconds) between the transmission of Hello messages from the MP. The minimum value is 15 and the maximum value is 3600. The default value is 900.

Hello RX Timer Enter the maximum length of time (in seconds) that may pass between the reception of consecutive Hello messages from a peer MP. If this time is exceeded, it is assumed that the peer MP is no longer advertising its presence. The Frame Relay OAM measurements with that peer are discontinued until the next Hello message is received. The minimum value is 60 and the maximum value is 14400. The default value is 3200.

SLV TX Timer Enter the length of time (in seconds) between the transmission of service verification messages from the MP to a peer MP. The minimum value is 15 and the maximum value is 36000. The default value is 900 seconds.

SLV RX Timer Enter the maximum length of time (in seconds) that may pass between the reception of a service verification message (FDR and DDR) from a MP peer and the reception of the next verification message (FDR and DDR) from the same peer. If the next service verification message is received within this time limit, the parameters are recorded, the FDR and DDR are calculated, and the timer is restarted. If the next service verification message is received after this time limit, the received parameters are recorded as initial values and the timer is restarted. The minimum value is 15 and the maximum value is 36000. The default value is 900.

Table 13-9. Modify Logical Port: FRF.19 Tab Fields (Continued)





1. Display the circuit (see “Displaying Circuits” on page 11-2 or “Viewing All Active SVCs” on page 11-13).

2. Right-click on the circuit and select FR OAM from the popup menu.

The FR OAM dialog box appears (Figure 13-19). The Enable FROAM tab is available.

Figure 13-19. FR OAM Dialog Box: Enable FROAM Tab

3. Complete the Enable FROAM tab fields as described in Table 13-10.

Table 13-10. FR OAM: Enable FROAM Tab Fields


Enable FR OAM Select the check box to enable FRF.19 on the circuit.

Location ID 1 Displays the monitoring point (MP) Location ID for endpoint 1 of the circuit.

Location ID 2 Displays the MP Location ID for endpoint 2 of the circuit.

Boundary Location 1 Select the check box to make the MP that corresponds to Location ID 1 a boundary point. This means that the MP will not forward any OAM frames intended for that administrative domain. The MP will forward OAM frames intended for a different administrative domain.

Clear the check box if you do not want Location ID 1 to be a boundary point.

Boundary Location 2 Select the check box to make the MP that corresponds to Location ID 2 a boundary point. This means that the MP will not forward any OAM frames intended for that administrative domain. The MP will forward OAM frames intended for a different administrative domain.

Clear the check box if you do not want Location ID 2 to be a boundary point.




4. Choose Enable FROAM.

The Near End tab appears (Figure 13-20). Table 13-11 describes the fields that appear in the Near End tab.

Figure 13-20. FR OAM Dialog Box: Near End Tab

5. From the Near End Loc ID fields pull-down list, select the near-end MP for the Frame Relay OAM test.

Table 13-11 describes the fields that appear.

6. Choose Send Near End Loc ID.

The near-end MP Location ID is set in the switch, and the Far End tab appears (Figure 13-21).

Table 13-11. FR OAM: Near End Tab Fields

Field Displays...

FTD Support A selected check box if FTD support is enabled on the near-end MP.

FDR Support A selected check box if FDR support is enabled on the near-end MP.

DDR Support A selected check box if DDR support is enabled on the near-end MP.

Latching LB Support A selected check box if latching loopback support is enabled on the near-end MP.

Non Latching LB Support A selected check box if non-latching loopback support is enabled on the near-end MP.




Figure 13-21. FR OAM Dialog Box: Far End Tab

7. Choose Retrieve Far End Loc ID to retrieve the peer MP Location IDs for the far end.

8. From the Far End Loc ID fields pull-down list, select the far-end MP for the Frame Relay OAM test.

Table 13-12 describes the fields that appear in the Far End tab.

9. Choose Send Far End Loc ID.

The far-end MP Location ID is set in the switch, and the Diagnostics tab appears.

10. From the Diag Test Type fields pull-down list, select one of the following test types:

• Latching Loopback (see “Loopback Testing” on page 13-39 for more details)

Table 13-12. FR OAM: Far End Tab

Field Displays...

Far End MP Count The number of peer MP Location IDs found.

FTD Support A selected check box if FTD support is enabled on the far-end MP.

FDR Support A selected check box if FDR support is enabled on the far-end MP.

DDR Support A selected check box if DDR support is enabled on the far-end MP.

Latching LB Support A selected check box if latching loopback support is enabled on the far-end MP.

Non Latching LB Support A selected check box if non-latching loopback support is enabled on the far-end MP.




• Non Latching Loopback (see “Loopback Testing” on page 13-39 for more details)

• SLV Measurement — Makes measurements of FTD/FDR/DDR. The type of measurements depend on the support at the near end and far end MPs. A particular SLV measurement can be done on a circuit only if the near-end and the far-end MPs have the same type of support enabled (for example, FTD support)

• . See “Frame Relay OAM Measurements” on page 13-39 for more details.

11. Choose Start to begin measurements for the type of test you choose in the Diag Test Type field.

Table 13-13 describes the Frame Relay OAM test results.

12. Choose Stop to end the current test that is running.

13. When you are done running Frame Relay OAM tests on the circuit, choose Close.

14. The FR OAM dialog box closes.

Table 13-13. Frame Relay OAM Test Results

Field Description

FTD (ms) Displays (in milliseconds) the frame transfer delay (FTD) measured from the near-end to the far-end MP. See “Frame Transfer Delay” on page 13-39 for more details.

FDR Displays the frame delivery ratio (FDR) measured from the near-end to the far-end MPs. See “Frame Delivery Ratio” on page 13-39 for more details.

DDR (ms) Displays the data delivery ratio (DDR) measured from the near-end to the far-end MPs. See “Data Delivery Ratio” on page 13-39 for more details.

Non Latching LB Status Displays the results of the non-latching loopback tests. The values can be:

• Failure

• Success

• Idle

Test Frames Transmitted Displays the number of test frames that were transmitted from the near-end to the far-end MP in the latching loopback test.

Test Frames Received Displays the number of looped back test frames that the near-end MP received from the far-end MP in the latching loopback test.




Disabling Frame Relay OAM Capabilities on a Logical Port

To disable Frame Relay OAM on a logical port:

1. Right-click on the logical port (see “Displaying Logical Ports” on page 6-1) and select Modify from the popup menu.


Figure 13-22. Modify Logical Port: FRF.19 Tab

2. Select the FRF.19 tab.

3. Clear the following checkboxes to disable Frame Relay OAM capabilities on the logical port:

• FTD Support

• FDR Support

• DDR Support

• Latching Loopback Support

• Non Latching Loopback Support

4. Choose OK.

The Modify Logical Port dialog box closes.





This section describes how to restart an offnet PVC.

Purpose

When Restart is selected from the popup menu for an offnet PVC, an Admin Down and Admin Up command is sent to the offnet PVC. The Restart function is only available if the offnet PVC’s administrative state is Up.

To Restart an Offnet PVC

To restart an offnet PVC:


2. Right-click on the offnet PVC and select Restart from the popup menu.

A message appears, asking if you are sure you want to restart the offnet PVC.

3. Choose Yes.

An Admin Down and then an Admin Up command are sent to the offnet PVC.



Monitoring Frame Relay CircuitsRestarting Offnet PVCs



14

Monitoring Alarms

Traps are sent from the network to inform the operator about the events occurring on switches that are configured to report information to the NMS. The traps are processed by the Trap Server and displayed in the Navis EMS-CBGX Client’s Alarm Browser Window. You can view and manage these alarms for one or many switches in Navis EMS-CBGX.

Alarms are automatically synchronized across multiple Alarm Browser Windows that are open. When you perform an action on an alarm, the Alarm Browser Window updates the database and sends a request to the Trap server that broadcasts this alarm information to all the registered, running Alarm Browser Windows. The action on the alarm is visible across all client sessions in Navis EMS-CBGX.

Appendix A, “Trap Alarm Condition Messages” describes the messages reported and displayed in the Lucent Alarms browser.


• “Displaying a List of Alarms” on page 14-2

• “Filtering the Alarms That Are Displayed” on page 14-7

• “Acknowledging/Unacknowledging Alarms” on page 14-12

• “Viewing Alarm Details” on page 14-14

• “Sorting the Alarms That Are Displayed” on page 14-16

• “Setting the Severity of Alarms” on page 14-18

• “Saving Alarms” on page 14-18

• “Deleting Alarms” on page 14-20

• “Event Configuration” on page 14-21

• “Managing the Alarm Configuration for a Switch” on page 14-22

• “Clearing the Alarm Relay” on page 14-24

• “Setting Alarm Count” on page 14-11



Monitoring AlarmsDisplaying a List of Alarms

Displaying a List of Alarms

To display a list of alarms in the Alarm Indicator Window:

1. Go to the Networks tab in the Navis EMS-CBGX Window, and from the View menu select Alarms. See Figure Figure 14-1.

Figure 14-1. Selecting Alarms from Navis EMS-CBGX

The Alarm Indicator Window appears (see Figure 14-2).

Figure 14-2. Alarm Indicator Window

A button appears for each type of switch, and the button is colored to indicate the most severe alarm that exists for that type of switch. Next to each switch type,

Beta Draft ConfidentialMonitoring Alarms



there are two numbers, “Total” and “(New)”. “Total” gives the total number of alarms that have been received from the Trap Server for that switch type. The value of “(New)” depends on the refresh rate.

• If the refresh option is “No Delay”, the “(New)” count is always zero; that is, every alarm is displayed in the alarm window as soon as it is received from the Trap Server.

• For other refresh options, “(New)” gives the total number of alarms that have been received from the Trap Server but have not yet been displayed in the alarm window. For example, in Figure 14-2, for the GX 550 switch type, the “Total (New)” values read “315 (86)”. This means that a total of 315 GX 550 alarms are present, out of which 86 alarms are “New” and have not yet been displayed in the alarm window. These 86 “New” alarms will be displayed in the alarm window only at the end of the “Refresh Interval” (See “Alarm Refresh Rate” on page 14-12).

Table 14-1 describes the colors.

2. Choose a button for the switch and alarms you want to view, as described in Table 14-2.

Table 14-1. Color Scheme in Alarm Indicator Window

Color Severity

Green Normal

Cyan Warning

Yellow Minor

Orange Major

Red Critical

Grey Unknown




3. The Alarm Browser Window opens (Figure 14-3). A separate Alarm Browser Window opens for each category you choose, but at most one Alarm Browser Window can be open at any given time.

Figure 14-3. Alarm Browser Window

Table 14-3 describes the columns that appear in the Alarm Browser Window.

Table 14-2. Alarm Indicator Window Buttons

Button Description

B-STDX Click on this button to open the Alarm Browser Window that displays all alarms received from B-STDX switches only.

CBX 500 Click on this button to open the Alarm Browser Window that displays all alarms received from CBX 500 switches only.

CBX 3500 Click on this button to open the Alarm Browser Window that displays all alarms received from CBX 3500 switches only.

GX 550 Click on this button to open the Alarm Browser Window that displays all alarms received from GX switches only.

All Click on this button to open the Alarm Browser Window that displays alarms received from all networks. This includes alarms from switches, Accounting Server and Statistics Server.




Viewing and Managing Alarms

From the Alarm Browser Window menu, you can choose several options for managing and viewing alarms. Figure 14-4 shows the Alarm Browser Window Actions menu.

Table 14-3. Alarm Browser Window Columns

Column Heading Description

Severity Displays the severity of this alarm. Possible values are:

• Normal

• Warning

• Minor

• Major

• Critical

Ack A selected checkbox indicates that a user has acknowledged this alarm. Check the box to mark an alarm as Acknowledged.

Time Received Displays the date and time when the Switch sent the alarm. The format ismm/dd/yy HH:MM:SS AM/PM, where

mm = Month (2 Digits)

dd = Date (2 Digits)

yy = Year (2 Digits)

HH = Hour (2 Digits)

MM = Minutes (2 Digits)

SS = Seconds (2 Digits)

AM/PM = Either AM (before noon) or PM (after noon)

Source The name of the switch that sent out the alarm.

Message The actual message string corresponding to the alarm.




Figure 14-4. Alarm Browser Window Actions Menu

You can perform several actions on alarms from this menu. See the following sections for details:

• “Acknowledging/Unacknowledging Alarms” on page 14-12

• “Setting the Severity of Alarms” on page 14-18

• “Deleting Alarms” on page 14-20

• “Event Configuration” on page 14-21

• “Setting Alarm Count” on page 14-11

The Alarm Browser Window View Menu provides different viewing options for the alarms in the Alarm Browser Window. Figure 14-5 shows the Alarm Browser Window View Menu.

Figure 14-5. Alarm BrowserWindow View Menu


Filtering the Alarms That Are Displayed


From this menu, you can change alarm viewing options. See the following sections for details:

• “Alarm Refresh Rate” on page 14-12


• “Sorting the Alarms That Are Displayed” on page 14-16

• “Filtering the Alarms That Are Displayed” on page 14-7




• “Overview” on page 14-7

• “Creating Filter Settings” on page 14-7

Overview

You can create filter settings so that only the types of alarms you want to see are displayed in the Alarm Browser Window. Once you create filter settings and activate them for an Alarm Browser Window session, an alarm must meet all of the filter conditions in order to be displayed in the Alarm Browser Window.

These filter settings apply to all the Alarm Browser Windows that you have open. These filter settings only apply to the current session of the Alarm Browser Window, and are not remembered for any future Alarm Browser Window sessions.

Creating Filter Settings

To create filter settings:

1. In the Alarm Browser Window (Figure 14-3), choose Set Filters from the View menu.

The Alarm Filter Configuration Window appears (Figure 14-6).



Monitoring AlarmsFiltering the Alarms That Are Displayed

Figure 14-6. Alarm Filter Configuration Window

2. Configure the filter settings as described in Table 14-4.

Table 14-4. Alarm Filter Configuration Window Settings

Field Description

Critical Check the box if you want alarms with Critical severity to be displayed.

Major Check the box if you want alarms with Major severity to be displayed.

Minor Check the box if you want alarms with Minor severity to be displayed.

Warning Check the box if you want alarms with Warning severity to be displayed.

Normal Check the box if you want alarms with Normal severity to be displayed.

Match Acknowledged

Check the box if you want acknowledged alarms to be displayed.

Match Unacknowledged

Check the box if you want unacknowledged alarms to be displayed.




Received After Check the box if you want alarms received after a specific date and time to be displayed (you will need to enter a value in the Received After: Date and Time fields).

Received After: Date

If the Received After box is checked, enter the date for filtering based on alarms received after this date. Use mm/dd/yy format.

This value should be less than or equal to the Received Before: Date value.

Received After: Time

If the Received After box is checked, enter the time for filtering based on alarms received after this time.

Use hh:mm AM/PM format.

This value should be less than or equal to the Received Before: Time value.

Received Before Check the box if you want alarms received before a specific date and time to be displayed (you will need to enter a value in the Received Before: Date and Time fields).

Received Before: Date

If the Received Before box is checked, enter the date for filtering based on alarms received before this date. Use mm/dd/yy format.

This value should be greater than or equal to the Received After: Date value.

Received Before: Time

If the Received Before box is checked, enter the time for filtering based on alarms received before this time.

Use hh:mm AM/PM format.

This value should be greater than or equal to the Received After: Time value.

Match Source Check the box if you want alarms to be filtered based on a list of switches that generate the alarms.

List below Match Source

If the Match Source box is checked, then this contains a list of switch names. Only those alarms generated from one of these switches will be displayed in the browser.

Delete If the Match Source box is checked, choose this button if you want to delete the selected Switch from the list of switches below Match Source.

Delete All If the Match Source box is checked, choose this button if you want to delete all the switches from the list of switches below Match Source

Table 14-4. Alarm Filter Configuration Window Settings (Continued)

Field Description



Monitoring AlarmsFiltering the Alarms That Are Displayed

3. When you are done entering the filter settings, choose OK.

The filter settings are saved, and the Alarm Filter Configuration Window closes.

After you click OK, the Alarm Browser Window contains only those alarms that match all the filter criteria. At the bottom of the Alarm Browser Window, next to the “Critical” and “Major” counts, there is a “Total:” count that indicates the total number of alarms currently in the Alarm Browser Window that match the filtering criteria. This “Total:” count is not the same as the “Total” count found in the Alarm Indicator Window which indicates the total number of alarms that are present for the given switch type, irrespective of whether it is shown in the Alarm Browser Window.

To activate or deactivate the filter settings that currently exist in the Alarm Filter Configuration Window, in the Alarm Browser Window (Figure 14-3), choose Deactivate Filters or Activate Filters from the View menu. The filter settings toggle between activated and deactivated. Deactivating does not clear the filter settings, it results in the filter settings not being applied. Once the filter settings are activated again, the filter settings will be applied as before.

To clear the filters settings that currently exist in the Alarm Filter Configuration Window, in the Alarm Browser Window (Figure 14-3), choose Clear Filters from the View menu. The filters settings are deleted.

Source Name If the Match Source box is checked, enter the name of a switch that you want to add to the list of switches.

Source Name: Add If the Match Source box is checked, choose this button to add the switch you entered in the Source Name field to the list of switches.

Message String Contains

Check the box if you want alarms to be filtered based on a string you enter in the Message String field.

Case Insensitive Check the box if the string comparison should be case insensitive.

Message String If the Match Message String box is checked, enter the string that the alarm message must contain in order for the alarm to be displayed.

Clear Choose Clear to clear all the fields.

Deactivate/Reactivate

This button toggles between Deactivate and Reactivate. Choosing Deactivate results in the filter settings not being applied. (This does not clear the filter settings from the Alarm Window fields.)

Choosing Reactivate applies the filter settings, so that only alarms that meet the filter settings are displayed.

Table 14-4. Alarm Filter Configuration Window Settings (Continued)

Field Description




Setting Alarm Count

You can manually set the number of alarm counts that are displayed in the Alarm Browser Window. 50 to 5,000 alarms may be displayed. This does not affect the number of alarms in the Navis EMS-CBGX data base. The data base stores a maximum of 10,000 alarms. Once this maximum number is exceeded, oldest alarms are deleted from the data base to make room for newest alarms. The default configuration is 500 alarms, when the EMS-CBGX client is opened for the first time.

To set the alarm count for the Alarm Browser Window:

1. Open the Alarm Browser Window (see “Displaying a List of Alarms” on page 14-2).

2. Under the Actions menu, select Set Alarm Count.

The Set Alarm Count Window is displayed (Figure 14-7).

Figure 14-7. Set Alarm Count Window

3. The current configuration and maximum configuration values are displayed. Enter the desired value and select OK.

4. The new selection takes effect immediately. For example, if the current alarm count is 500, and the user changes it to 1000, the latest 1000 alarms are instantly loaded from the database, and the count is set as 1000 for all the Alarm Windows of all the switch types.

5. Purging of alarms is based on the count set. If you set a count of 2000 alarms, the window loads the latest 2000 alarms from the database (if available). The alarm count goes to 2500 (set count plus 25% of the set count) before the oldest 500 alarms are purged from the Alarm Window.



Monitoring AlarmsAcknowledging/Unacknowledging Alarms

Alarm Refresh Rate

You can select the refresh rate of alarms; that is, how often alarms are updated in the Alarm Indicator and Alarm Browser windows. The default refresh rate is 30 seconds. The alarm refresh rate is applicable to the Alarm Browser Window but not to the Alarm Indicator Window. The Alarm Indicator Window updates immediately irrespective of the refresh rate set on the Alarm Browser Window.

To select the alarm refresh rate:


2. Under the View menu, right-click on Set Refresh Rate to see the refresh values available. Table 14-5 lists and describes the available values.

Acknowledging/Unacknowledging Alarms

You can mark an alarm in the Alarm Window as Acknowledged or Unacknowledged. The Acknowledged/Unacknowledged status of an alarm is stored in the database and the last status is retained, even if you exit and open the client, unless the status is modified by another client session.


• “Acknowledging or Unacknowledging an Individual Alarm” on page 14-13

• “Acknowledging Selected Alarms” on page 14-13

• “Acknowledging Filtered Alarms” on page 14-13

Table 14-5. Set Refresh Rate

Values Description

Manual New alarms are not displayed in the window until you select the switch.

No Delay Alarms are automatically updated in the window.a

a Caution: If you have a high rate of incoming alarms, you cannot perform any operations on a specific alarm with No Delay selected. You must select a refresh rate with some delay to perform operations on a specific alarm.

Every 15 Sec Alarms are automatically updated in the window every 15 seconds.

Every 30 Sec Alarms are automatically updated in the window every 30 seconds.

Every 1 Minute Alarms are automatically updated in the window every 1 minute.

Every 2 Minute Alarms are automatically updated in the window every 2 minutes.


Acknowledging/Unacknowledging Alarms


• “Acknowledging All Alarms” on page 14-13

• “Unacknowledging Selected Alarms” on page 14-14

• “Unacknowledging Filtered Alarms” on page 14-14

• “Unacknowledging All Alarms” on page 14-14

Acknowledging or Unacknowledging an Individual Alarm

To mark a single alarm as Acknowledged or Unacknowledged:


2. In the Acknowledged column for the alarm (Figure 14-3), select the checkbox to acknowledge the alarm, or clear the checkbox to unacknowledge the alarm.

Acknowledging Selected Alarms

To mark selected alarms as Acknowledged:

1. In the Alarm Browser Window (Figure 14-3), select the alarm or alarms. To select multiple alarms, hold down the Control key and select each alarm.

2. Choose Acknowledge ⇒ Selected Alarms from the Actions menu.

The selected alarms are marked as Acknowledged.

Acknowledging Filtered Alarms

To mark as Acknowledged all the alarms that are displayed in the Alarm Browser Window when the alarm filters are active:

• In the Alarm Browser Window (Figure 14-3), choose Acknowledge ⇒ Filtered Alarms from the Actions menu.

The alarms are marked as Acknowledged.

Acknowledging All Alarms

To mark as Acknowledged all the alarms for the current category, whether or not they are displayed when the alarm filters are active:

• In the Alarm Browser Window (Figure 14-3), choose Acknowledge ⇒ All Alarms in Category from the Actions menu.

The alarms are marked as Acknowledged.



Monitoring AlarmsViewing Alarm Details

Unacknowledging Selected Alarms

To mark selected alarms as Unacknowledged:


2. Choose Unacknowledge ⇒ Selected Alarms from the Actions menu.

The selected alarms are marked as Unacknowledged.

Unacknowledging Filtered Alarms

To mark as Unacknowledged all the alarms that are displayed in the Alarm Browser Window when the alarm filters are active:

• In the Alarm Browser Window (Figure 14-3), choose Unacknowledge ⇒ Filtered Alarms from the Actions menu.

The alarms are marked as Unacknowledged.

Unacknowledging All Alarms

To mark as Unacknowledged all the alarms for the current category, whether or not they are displayed when the alarm filters are active:

• In the Alarm Browser Window (Figure 14-3), choose Unacknowledge ⇒ All Alarms in Category from the Actions menu.

The alarms are marked as Unacknowledged.

Viewing Alarm Details

To view details for any alarm displayed in the Alarm Browser Window:

1. In the Alarm Browser Window (Figure 14-3), select the alarm.

2. Double-click on the row to view the alarm details.

The Alarm Details Window appears (Figure 14-8).


Viewing Alarm Details


Figure 14-8. Alarm Details Window

Table 14-6 describes the information in the Alarm Details Window.

Table 14-6. Alarm Details Window

Field Description

Alarm ID ID number for the alarm.

Alarm Name Displays the event name.

Source Name/IP Displays the name of the switch that sent out the alarm.

Severity Displays the severity of the alarm.

Enterprise ID String Displays the Object ID in dot Notation.

Enterprise ID Number Displays the Object ID in Numeric dot Notation.

GID String Displays the Generic ID in string format. This specifies one of a number of generic alarm strings.



Monitoring AlarmsSorting the Alarms That Are Displayed

3. When you are done viewing the alarm details, choose Close.

The Alarm Details Window closes.

Sorting the Alarms That Are Displayed

There are two ways to sort alarms. You can sort alarms that are already displayed in the Alarm Browser Window, or you can create an alarm sorting setting from the View menu.

Alarm sorting settings apply to all the Alarm Browser Windows that you have open. These settings only apply to the current session of the Alarm Browser Window, and are not remembered for any future Alarm Browser Window sessions.

To sort the alarms displayed in the Alarm Browser Window:

1. Click on the column heading of any column in the Alarm Browser Window. The heading now includes an up or down arrow.

2. Click the column heading again to change the direction of the arrow. Alarms are sorted according to the selection made in this column.

Note that new incoming alarms are added to the beginning or end of the sorted list when the sorting is based on the timestamp field. You may select a heading and sort again to include the most recently added alarms in the sort.

To create an alarm sorting setting:

1. In the Alarm Browser Window (Figure 14-3 on page 14-4), choose Sort Alarms from the View menu.

The Alarm Sorting Configuration Window appears (Figure 14-9)

SID String Displays the Specific ID in string format. This specifies one of a number of specific alarm strings.

Event/Alarm description Displays a brief explanation of the nature or cause of the event, as well as information on the type of the data that was associated with the event.

Table 14-6. Alarm Details Window (Continued)

Field Description


Sorting the Alarms That Are Displayed


Figure 14-9. Alarm Sorting Configuration Window

2. Configure the alarm sorting settings as described in Table 14-7.

3. When you are done entering the sorting settings, choose OK.

The sorting settings are saved, and the Alarm Sorting Configuration Window closes.

Table 14-7. Alarm Sorting Configuration Window Settings

Field Description

Sort Field 1, 2, and 3 From the pull-down list, select the parameter on which the sorting should be based. Sorting first takes place based on Sort Field 1, then on Sort Field 2, and then on Sort Field 3. The parameter choices are:

• Severity

• Acknowledged

• Time Received

• Source

• Not Selected

Ascending Button Choose this button if you want the sorting to be in ascending order for the corresponding Sort Field.

Descending Button Choose this button if you want the sorting to be in descending order for the corresponding Sort Field.

Default Choose Default to set all of the Sort Fields to Not Selected.



Monitoring AlarmsSetting the Severity of Alarms

Setting the Severity of Alarms

To set the severity of an alarm or alarms:


2. From the Actions menu, choose Set Alarm Severity. Select one of the commands described in Table 14-8.

Saving Alarms


• “Saving Selected Alarms” on page 14-18

• “Saving Acknowledged Alarms” on page 14-19

• “Saving Unacknowledged Alarms” on page 14-19

• “Saving Filtered Alarms” on page 14-19

• “Saving Unfiltered Alarms” on page 14-19

• “Saving All Alarms” on page 14-20

Saving Selected Alarms

To save information for selected alarms in the Alarm Browser Window to a file:


2. Choose Save ⇒ Selected Alarms from the File menu.

A Save Window appears.

3. Enter the file information in the Save Window, and choose OK.

Table 14-8. Set Alarm Severity Commands

Command Description

Unknown Changes the selected alarm’s severity to Unknown.

Normal Changes the selected alarm’s severity to Normal.

Warning Changes the selected alarm’s severity to Warning.

Minor Changes the selected alarm’s severity to Minor.

Major Changes the selected alarm’s severity to Major.

Critical Changes the selected alarm’s severity to Critical.


Saving Alarms


The Alarm Browser Window closes.

Saving Acknowledged Alarms

To save information for all the alarms that are acknowledged in the Alarm Browser Window:

1. In the Alarm Browser Window (Figure 14-3), choose Save ⇒ Acknowledged Alarms from the File menu.

A Save Window appears.

2. Enter the file information in the Save Window, and choose OK.


Saving Unacknowledged Alarms

To save information for all the alarms that are unacknowledged in the Alarm Browser Window:

1. In the Alarm Browser Window (Figure 14-3), choose Save ⇒ Unacknowledged Alarms from the File menu.

A Save Alarm Browser Window appears.

2. Enter the file information in the Save Alarm Browser Window, and choose OK.


Saving Filtered Alarms

To save information for all the alarms that are displayed in the Alarm Window when the alarm filters are active:

1. In the Alarm Window (Figure 14-3), choose Save ⇒ Filtered Alarms from the File menu.

A Save Alarm Window appears.

2. Enter the file information in the Save Alarm Window, and choose OK.

The Alarm Window closes.

Saving Unfiltered Alarms

To save information for all the alarms that are not displayed in the Alarm Browser Window when the alarm filters are inactive:

1. In the Alarm Browser Window (Figure 14-3), choose Save ⇒ Unfiltered Alarms from the File menu.




Monitoring AlarmsDeleting Alarms



Saving All Alarms

To save information for all the alarms for the current category, whether or not they are displayed when the alarm filters are active:

1. In the Alarm Browser Window (Figure 14-3), choose Save ⇒ All Alarms in Category from the File menu.




Deleting Alarms


• “Deleting Selected Alarms” on page 14-20

• “Deleting Filtered Alarms” on page 14-20

• “Deleting Unfiltered Alarms” on page 14-21

• “Deleting All Alarms” on page 14-21

• “Deleting Acknowledged Alarms” on page 14-21

• “Deleting Unacknowledged Alarms” on page 14-21

Deleting Selected Alarms

To delete selected alarms in the Alarm Browser Window:


2. Choose Delete Alarms ⇒ Selected Alarms from the Actions menu.

The selected alarms are deleted.

Deleting Filtered Alarms

To delete all the alarms that are displayed in the Alarm Browser Window when the alarm filters are active:

• In the Alarm Browser Window (Figure 14-3), choose Delete Alarms ⇒ Filtered Alarms from the Actions menu.

The alarms are deleted.

Beta Draft ConfidentialMonitoring AlarmsEvent Configuration


Deleting Unfiltered Alarms

To delete all the alarms that are not displayed in the Alarm Browser Window when the alarm filters are inactive:

• In the Alarm Browser Window (Figure 14-3), choose Delete Alarms ⇒ Unfiltered Alarms from the File menu.


Deleting All Alarms

To delete all the alarms that are currently displayed in the Alarm Browser Window:

• In the Alarm Browser Window (Figure 14-3), choose Delete Alarms ⇒ All Alarms from the Actions menu.


Deleting Acknowledged Alarms

To delete all the alarms that are acknowledged in the Alarm Browser Window:

• In the Alarm Browser Window (Figure 14-3), choose Delete Alarms ⇒ Acknowledged Alarms from the File menu.


Note that if alarm filters are applied, only those alarms present in the Alarm Browser Window are deleted. Unfiltered or new alarms are not deleted.

Deleting Unacknowledged Alarms

To delete all the alarms that are unacknowledged in the Alarm Browser Window:

• In the Alarm Browser Window (Figure 14-3), choose Delete Alarms ⇒ Unacknowledged Alarms from the File menu.


Event Configuration

A superuser can configure and control the severity-level of alarms through the Event Configuration window of an Alarm Browser Window.

The Event Configuration window, launched from the Alarm Browser Window Action menu, provides a User Interface (UI) to configure the severity of an alarm. See Figure 14-10.



Monitoring AlarmsManaging the Alarm Configuration for a Switch

Figure 14-10. Event Configuration Window

The UI lists all the Enterprise Identifiers and the corresponding Event Identifiers. When you select an event identifier node, the UI displays severity information about that identifier.

The Trap server and client load their caches with alarm information found in the Navis EMS-CBGX database. When a superuser changes the severity of an alarm, that change is communicated to the Trap server. The Trap server updates its cache with the new severity information and broadcasts that information to open Alarm Windows which then update their severity caches.

Managing the Alarm Configuration for a Switch

For selected switches in a Lucent network, you can configure contact alarm relay status and alarm transmit rate.

Contact Alarm Relay Status

The CBX 500 or CBX 3500 switch processor adapter (SPA) module and the GX 550 Multiservice WAN Switch node processor adapter (NPA) module contain an 8-position terminal strip that enables you to connect remote audio and visual alarms. These relay contacts alert you to critical, major, and minor alarm conditions in the switch and power supply. See the CBX 3500 Multiservice Edge Switch Hardware Installation Guide, the CBX 500 Multiservice WAN Switch Hardware Installation


Managing the Alarm Configuration for a Switch


Guide, and the GX 550 Multiservice WAN Switch Hardware Installation Guide for information about connecting these alarms. If necessary, you can disable the contact alarm relay feature through Navis EMS-CBGX (see the “Configuring the Alarm Configuration For a Switch” on page 14-23).

B-STDX switches do not support the contact alarm relay feature. They support the alarm transmit rate feature only.

Alarm Transmit Rate

The alarm transmit rate determines the maximum number of alarms per second that the switch sends to the NMS. For example, if you enter 5 (the default), the switch sends a maximum of five alarms to the NMS every second and queues any remaining alarms.

Configuring the Alarm Configuration For a Switch

To configure the alarm configuration for a switch:

1. In the switch object tree (see “Displaying a Switch Tab in the Navigation Panel” on page 2-6), right-click on the switch and select Modify from the popup menu.

The Modify Switch Alarm Window appears (Figure 14-11).

Figure 14-11. Modify Switch Alarm Window

2. Select the Trap Configuration tab.

3. Define the alarm configuration attributes as described in Table 14-9.



Monitoring AlarmsClearing the Alarm Relay

4. Choose OK.

5. The Modify Switch Alarm Window closes.

Clearing the Alarm Relay

Clearing an alarm relay turns off an audible/visual contact alarm. To clear the Alarm Relay for a switch:

1. In the switch object tree (see “Displaying a Switch Tab in the Navigation Panel” on page 2-6), right-click on the switch and select Clear Alarm Relay from the popup menu.

The Clear Alarm Relay Window appears (Figure 14-12).

Figure 14-12. Clear Alarm Relay Window

Table 14-9. Switch Trap Configuration Attributes

Field Description

Alarm Relay Status (This field is not applicable to B-STDX 9000 switches.)

Choose Active to enable the alarm relay function.

Choose Inactive to disable the alarm relay function.

Trap Transmit Rate (Traps/Sec) Enter the number of alarms that can be transmitted per second. The range is from 1 to 10.

If the switch discards traps, increase the alarm transmit rate. The switch discards alarms under peak problem conditions when the alarm transmit queues overflow.


Clearing the Alarm Relay


2. Select the alarm relay condition you want to clear.

Table 14-10 describes the alarm relay conditions.

3. Choose OK to clear the selected alarm relay condition.

The Clear Alarm Relay Window closes.

Table 14-10. Clear Alarm Relay Conditions

Field Description

All Select to clear all alarm relays.

Note: This function does not clear the alarm condition, only the audible/visual alarm contact relay.

Critical Select to clear a Critical alarm relay. This alarm indicates severe, service-affecting conditions that require immediate corrective action (for example, power supply failure).

Major Select to clear a Major alarm relay. This alarm indicates a hardware or software condition that can cause a serious disruption of service or circuit failure. An example would be an IOM or physical port down.

Minor Select to clear a Minor alarm relay. This alarm indicates non-service-affecting conditions (for example, an exceeded performance monitoring threshold).

Power Major Select to clear a major power alarm relay (for example, the second power supply is out of service).

Power Minor Select to clear a minor power alarm relay. With an N+1 chassis, this alarm is generated if one of the three power supplies fails.



Monitoring AlarmsClearing the Alarm Relay



15

Managing the Event Log

The Event Log is a diagnostic tool that enables you to selectively track application events on a CBX 500 switch, CBX 3500 switch, or GX 550 switch.

This chapter describes the following topics and tasks for configuring and using the Event Log in a Lucent switch network:

• “About the Event Log” on page 15-2

• “Event Log Structure” on page 15-3

• “Configuration Process Overview” on page 15-16

• “Configuring Remote Event Logging With Navis EMS-CBGX” on page 15-17

• “Configuring I/O Modules for Event Logging” on page 15-19

• “Configuring Applications for Event Logging” on page 15-20

• “Configuring Tracing” on page 15-21

• “Defining Filters” on page 15-23

• “Working With Event Log” on page 15-26



Managing the Event LogAbout the Event Log

About the Event Log

An event provides insight into the operation of a switch. For example, events include:

• hardware errors

• software errors

• resource shortages

• logical entity state changes

• configuration changes

• connection recoveries

• other status changes

Events may have positive, neutral, or negative impact on switch performance. When an event occurs, the application can track the event by calling the Event Log, which logs, traces, or ignores the event based on criteria established by the user.

The following sections describe several parameters that you need to understand to better manage the Event Log in a Lucent switch network. These parameters include:

• Logging — allows the user to track events on the input/output module (IOM) as well as specific applications and slots. Messages are forwarded to the event.log file.

• Tracing — is used in conjunction with Logging. Tracing is particularly useful for debugging as messages are forwarded to the console as well as the event.log file.

• Filtering — enables you to specify application-specific criteria to determine if events are to be logged or discarded. The result may or may not bypass Importance Level evaluation depending on the type of Filter that is defined.

Note – The Event Log supersedes Trace Manager, Cookie Trace, Syslog and Next Hop Resolution Protocol (NHRP) Trace functions.

See “Event Log and the Syslog Utility” on page 15-27 for detailed instructions on using the Event Log to log and view files that you previously obtained by entering the show syslog console command.

Beta Draft ConfidentialManaging the Event Log

Event Log Structure


Event Log Structure

The Event Log structure encompasses the following five components:

• Network Management System (NMS)

• Switch Console

• Event Log Server on the switch processor/node processor (SP/NP)

• Event Log Client per IOM and SP/NP

• Applications on all IOMs and the SP/NP

Figure 15-1 displays the main interactions between the above listed system components.

Figure 15-1. Event Log Structure

System Components

This section describes the system components of the Event Log:

• Network Management System (NMS)

NMS provides the user with a list of all applications that are registered on the switch for Event Logging. The NMS also allows the user to configure the log parameters for the node. An SNMP interface is available through the NMS for configuring log parameters.

The NMS can also be used to configure remote event logging (see “Configuring Remote Event Logging With Navis EMS-CBGX” on page 15-17).

• Switch Console

The Switch Console provides a command line interface (CLI) for the display of events as well as the setting of Importance Levels. Traced events may be displayed automatically as they are logged.

Applications Switch Console NMS

Event Log Client Event Log Server

MessageManager

ShellInterface

SNMPCalls

APICalls



Managing the Event LogEvent Log Structure

• Event Log Server

The Event Log server is solely responsible for the writing and reading of event data to the local file system (event.log file).

Table 15-1 outlines the Event Log server Output process for log files.

• Event Log Client

The Event Log client is responsible for buffer management and buffer transfer to the Event Log server. The Event Log client uses Message Manager for buffer transport and communication with the Event Log server.

The Event Log is an efficient system, as data is buffered on each card until the buffer is full. Events are automatically dropped if the tracking rate exceeds the buffer send rate. In addition, the Event Log provides for unsaved event data recovery from PRAM in the event of a card or system crash.

• Applications

An application is any switch software component, such as Message Manager. These applications include components that run as tasks as well as interrupt handlers. API service calls to the Event Log client allow applications to register callback functions, submit events for tracking, and modify Importance Levels.

Table 15-2 describes the application acronyms that are displayed by the system.

Table 15-1. Event Log Server Output

Setting Log files forwarded to..

Log Local event.log file

Trace Console and event.log file

Table 15-2. Application Acronyms

Acronym Application

Addrmgr Address Manager

Logs files related to the configuration and operation of the Address Manager, an application that controls and manages address registration requests.

Atmizer Atmizer

Logs files related to the configuration and operation of the Atmizer software device driver, an application that controls the transmission of ATM cells that need to be transmitted by the local application stack.


Event Log Structure


Bgp Border Gateway Protocol (BGP)

Logs files related to the configuration and operation of BGP, a protocol that exchanges routing information between autonomous systems from external BGP neighbors.

Bio Base Input/Output Module for the GX 550

Logs files related to the configuration and operation of the BIO1 Module.

BioOC12 1-Port OC12c/STM-4 Phy Module for the GX 550

Logs files related to the configuration and operation of the OC12 Phy Module.

Bootmgr Boot manager

Logs files related to the configuration and operation of warmboot and coldboot processor cards.

Bsftp Lucent SMDS Billing System File Transfer Protocol

Logs files related to the configuration and operation of the Lucent SMDS Billing System FTP, an application that measures data usage within a switching system and then transfers the measurements via FTP to other billing software programs.

Bsmgr Lucent SMDS Billing System Manager

Logs files related to the configuration and operation of the Lucent SMDS Billing System Manager, an application that controls the overall billing system.

Cac Call Admission Control (CAC)

Logs files related to the configuration and operation of CAC, a set of actions taken in order to determine whether a connection request can be accepted or not.

Cfgmgr Configuration Manager

Logs files related to the configuration and operation of the Configuration Manager, an application that controls PRAM Sync, PRAM Consistency, upgrade, and other general configuration information.

cidServer CID Server

Logs files related to the configuration and operation of the Circuit ID (CID) server and manager.

Table 15-2. Application Acronyms (Continued)

Acronym Application




Cktprim Circuit Primitives

Logs files related to the configuration and operation of Circuit Primitives, an application that provides low level routines that configure and manage circuit resources.

CrashEvmgr Crash Event Manager1

N/A

Cug Closed User Group (CUG)

Logs files related to the configuration and operation of a CUG, which is a subset of users with particular properties. Members can be addresses (individual member) or regular expressions (set of members).

Diag Diagnostics

Logs files related to the configuration and operation of Diagnostics, an application that controls system diagnostics.

Dvmrp-Cche Distance Vector Multicast Routing Protocol (DVMRP) - Cache

Logs files related to the configuration and operation of the DVMRP-Cache, an application that stores a list of routing messages.

Dvmrp-igmp DVMRP-Internet Group Multicast Protocol (IGMP)

Logs files related to the configuration and operation of DVMRP-IGMP, an application that monitors changes in group membership.

Dvmrp-Intf DVMRP-Interface

Logs files related to the configuration and operation of DVMRP-Interface, an application that controls the operation of the interface.

Dvmrp-Nbr DVMRP-Neighbor Table

Logs files related to the configuration and operation of the DVMRP-Neighbor Table, an application that controls the exchange of routing messages between DVMRP neighbors.

Dvmrp-Pkt DVMRP-Packet

Logs files related to the configuration and operation of the DVMRP-Packet, an application that controls the transfer of packets to routers using DVMRP.


Acronym Application


Event Log Structure


Dvmrp-Prob DVMRP-Probe

Logs files related to the configuration and operation of DVMRP-Probe, an application that controls DVMRP probing to and from neighbors.

Dvmrp-Prun DVMRP-Prune

Logs files related to the configuration and operation of the DVMRP-Prune, an application that enables routers with no group members return a prune packet to allow other routers to leave a multicast group.

Dvmrp-Rte DVMRP-Routing Table

Logs files related to the configuration and operation of the DVMRP-Routing Table, an application that controls the unicast routing table for DVMRP. This table is used to implement reverse path multicast forwarding.

Dvmrp-Tout DVMRP-Timeout

Logs files related to the configuration and operation of DVMRP-Timeout, an application that logs out messages relating to route aging.

Eshw Enhanced Standby Hardware Test

Logs files related to the configuration and operation of the Enhanced Standby Hardware Test, an application that tests whether the standby SP/NP module can communicate with IOM/BIO modules, and whether standby SF modules are working properly.

EventLog Event Log

Logs files related to the configuration and operation of the Event Log, an application that selectively logs application events on CBX 500/3500 and GX 550 switches.

FeEventM Piranha Frame Engine Event Manager1

N/A

FePhd Piranha FE PHD Device Driver1

N/A

Ffd Flow Filtering and Detecting Module

Logs files related to the configuration and operation of the Flow Control and Detection module, which is used as part of foreground IP processing on the ingress frame card of the CBX 500/3500.


Acronym Application




Frsvc Frame Relay Switched Virtual Circuit (FR SVC)

Logs files related to the configuration and operation of FR SVCs, which are virtual circuit connections (VCCs) established across a Frame Relay network on an as-needed basis and lasting only for the duration of the transfer.

Igmp Internet Group Multicast Protocol (IGMP)

Logs files related to the configuration and operation of IGMP, a protocol that allows hosts to register as members of a particular multicast group. Once hosts register as multicast group members, routers in the network track them dynamically.

IMA 3-Port Channelized DS3/1 Inverse Multiplexing for ATM (IMA) IOM

Logs files related to the configuration and operation of the IMA Module.

IpFilter Internet Protocol Filter

Logs files related to the configuration and operation of the IP Filter, an application that enables the system to set filters to selectively block IP packets.

Ipifarp IP Interface for Address Resolution Protocol (IPIFARP)

Logs files related to the configuration and operation of IPIFARP, an protocol that provides an IP interface for Frame Relay, Ethernet, and IP VPN cloud interface configurations when an IP address of a given destination is known, but the destination hardware address is not.

Lip Link Integrity Protocol (LIP)

Logs files related to the configuration and operation of LIP, a protocol that is used for Multilink Frame Relay (MLFR) on the 32-Port Module on the CBX 500/3500.

Lnk Link

Logs files related to the implementation of data transport between upper level applications and user ports. This also provides logical port functionality, abstracting user ports to the rest of the software.

Ltp Link Trunk Protocol (LTP)

Logs files related to the configuration and operation of LTP, a protocol that controls communication between switches by exchanging keep alive (KA) control frames.


Acronym Application


Event Log Structure


Memmgr Memory Manager

Logs files related to the configuration and operation of the Memory Manager, an application that is designed to manage pools of memory that are divided into fixed sized blocks.

Msgmgr Message Manager

Logs files related to the configuration and operation of the Message Manager, an application that provides a mechanism for the system to manage multiple non-real-time asynchronous and real-time synchronous events.

Mpt Multipoint-to-Point Tunnel (MPT)

Logs files related to the configuration and operation of MPT, a protocol that allows for multiple nodes to share the same circuit for transmission to a single destination.

Nhrp-Agent Next Hop Routing/Resolution Protocol (NHRP) Agent

Logs files related to the configuration and operation of the NHRP address resolution protocol, which provides a source station (host or router) with the NonBroadcast Multi-Access (NBMA) address of the next-hop destination station. The NHRP-Agent uses the NHRP-Container to update MIB configuration information during normal protocol processing.

Nhrp-Cont NHRP-Container

Logs files related to the configuration and operation of the NHRP-Container, an application that is responsible for adding, deleting and accessing MIB related information.

Nhrp-hold NHRP-Hold Resolution Refresh List

Logs files related to the configuration and operation of the NHRP-Hold Resolution Refresh List, an application that is responsible for maintaining refresh times for client cache entries.

Nhrp-Mgr NHRP-Manager

Logs files related to the configuration and operation of the NHRP-Manager, an application that uses the NHRP-Container to access MIB information for QoS extension functionality.

Nhrp-Pend NHRP-Pending Request List

Logs files related to the configuration and operation of the NHRP-Pending Request List, an application that maintains retries and time-outs of NHRP requests.


Acronym Application




Nhrp-Qsm NHRP-Quality of Service (QoS) Shortcut Manager

Logs files related to the configuration and operation of the NHRP-Qsm application, which is responsible for shortcut routing.

Nhrp-Test NHRP-Testing

Logs files related to the configuration and operation of the NHRP-Testing application.

Nrts NRTS Card for CBX 500/3500 Input/Output Modules

Logs files related to the configuration and operation of non-real time services (NRTS), an application that controls available bit rate (ABR) functionality for the CBX 500/3500.

Olbd Online Board Diagnostics

Logs files related to the configuration and operation of Online Board Diagnostics, an application that allows diagnostic images to be downloaded on demand to SP/NP or IOM/BIO modules on CBX 500/3500 and GX 550 switches.

PanicEvmgr Piranha PANIC Event Manager1

N/A

Pcfs-Api PCMCIA Disk File system (Pcfs)-Application

Logs files related to the configuration and operation of the Pcfs-Application, an application that provides various file system operations such as opening, reading, and writing to a file.

Pcfs-Check Pcfs-Check

Logs files related to the configuration and operation of Pcfs-Check, an application that implements file system validation routines such as Scandisk on the active and standby control processor.

Pcfs-Diag Pcfs-Diagnostics

Logs files related to the configuration and operation of Pcfs-Diagnostics, an application that provides extension of disk system validation routines.

Pcfs-FClnt Pcfs-File Client

Logs files related to the configuration and operation of the Pcfs-File Client, a generic file server that runs on the two control processor (CP)/SP/NP cards.


Acronym Application


Event Log Structure


Pcfs-FSvr Pcfs-File Server

Logs files related to the configuration and operation of the Pcfs-File Server, a class of object to read from and write into Pcfs files on behalf of other cards.

Pie Path Integrity

Logs files related to the configuration and operation of the Path Integrity feature, an application that verifies connection paths on NP1/NP2 and BIO1/BIO2 modules on the GX 550 switch.

Piranha Base Input/Output Module (BIO3) for the GX 5501

N/A

PirGenPhy Piranha GENET Phy Drive1

N/A

PirOCPhy Piranha OC-N Phy Driver1

N/A

Protcon Protcon

Logs files related to the configuration and operation of the Protcon, an application that provides multiplexing background IP compensation for transmission protocol.

Pvcmgr Permanent Virtual Circuit (PVC) Manager

Logs files related to the configuration and operation of the PVC Manager, an application that controls the setup and management of PVCs (including the PVC Establishment Feature) within the network.

Qsm QoS Shortcut Manager

Logs files related to the configuration and operation of the QoS Shortcut Manager, an application that is responsible for shortcut routing.

Rds Remote Authentication Dial-In User Service (Radius)

Logs files related to the configuration and operation of Radius, a distributed security system that uses an authentication server to solve the security problems associated with remote computing.

Resrc Resource Manager

Logs files related to the configuration and operation of components that track CPU utilization of specific tasks and provide input to the overload control features.


Acronym Application




Resrc - Ospf Resource Manager - OSPF overload control

Logs files related to the configuration and operation of overload control for OSPF, as well as transitioning cards out of card-overload states.

Resrc- RtCp Resource Manager for PVC reroute and SVC setup overload control

Logs files related to the configuration and operation of the Real Time CPU resource Manager

Resrc - Ovld Resource Manager overload control

Defines the completion of the configuration of the OSPF resource manager.

Rip Routing Information Protocol (RIP)

Logs files related to the configuration and operation of the RIP, a protocol that maintains a list of accessible networks and calculates the lowest hop count from a particular location to a specific network.

Rlmi Resilient Local Management Interface (RLMI)

Logs files related to the configuration and operation of RLMI, a protocol that enables a pair of Frame Relay logical ports to serve as primary and backup ports.

Rrmgr Redundancy Manager

Logs files related to the configuration and operation of the Redundancy Manager, an application that controls redundancy switchovers.

Rtemgr Route Manager

Logs files related to the configuration and operation of the Route Manager, an application that controls routing protocols in the network.

Rtos Real Time Operating System

Logs files related to the configuration and operation of the Real Time Operating System, an application that provides an environment for multiprocessing, integrated TCP/IP based networking as well as centralized network administration tools.

RtPolicy Routing Policy

Files related to the configuration and operation of the Routing Policy, a protocol that determines various routing paths based upon set policies.

SF High level SF2 driver information

Logs files related to the operation of high level SF2 drivers.


Acronym Application


Event Log Structure


SF - LowDrv High level Switch Fabric 2 driver information

Logs files related to the operation of low level SF2 drivers.

SF - Magellan Magellan devices on SF2 interface

Logs files related to the configuration and operation of Magellan devices on the SF2 interface.

SF - NP_CTRL Node Processor (NP) control logic.

Logs files related to the status of interrupt and control registers on the NP modules.

SF - PIONEER Pioneer Field Programmable Gate Array (FPGA) on the SF2 module.

Logs files related to the operation of the Pioneer FPGA, which is responsible for communication between port cards and the Viking device on the SF2 module.

SF - Viking Viking FPGA on the SF2 module.

Logs files related to the operation of the Viking FPGA, which is responsible for communication between port cards and the Pioneer device on the SF2 module.

Snmp Simple Network Management Protocol (SNMP)

Logs files related to the configuration and operation of SNMP, a protocol that controls MIB-based configuration within the system.

Spvc Soft Permanent Virtual Circuit

Logs files related to the configuration and operation of SPVC, a protocol that is established by signaling rather than administratively through network management.

Ssm Signal Stack Manager

Logs files related to the configuration and operation of the Signal Stack Manager, an application that initializes VPI and VCI for signaling channels.

Stats Statistics Server

Logs files related to the configuration and operation of the Statistics Server, an application that is responsible for the collection of statistics on a switch or I/O module.

Swmgr Software Manager

Logs files related to the configuration and operation of the Software Manager, an application that manages switch software from the NMS to the disk, delivering bootflash and application software to the control processor and I/O modules.


Acronym Application




Sys System

Logs files related to the configuration and operation of System, an application that handles critical PRAM Sync and upgrade events.

Syslog Syslog1

N/A

Sysmon System Monitor

Logs files related to the configuration and operation of the System Monitor, an application that provides KA checking on each slave component in the system, providing the distribution mechanism between master and slave components for data exchanging.

Ume UNI Management Entity

Logs files related to the configuration and operation of the UNI Management Entity, an application that resides in the ATM device at each end of the UNI circuit and implements the management interface to the ATM network.

Uplink GX 550 ES Uplink Phy Module

Logs files related to the configuration and operation of the GX 550 ES Uplink Phy Module, which attaches to a GX 550 Downlink Phy Module.

WarmStart Warm Boot Upgrade

Logs files related to the configuration and operation of the Warm boot component of Lucent’s Smart Upgrade capability.

Xpnlog Xpnlog application for the Event Log

Logs files related to the configuration and operation of the Xpnlog, which provides output for events collected by the Enhanced Exception Logging feature.

The following acronyms may be displayed by the Event Log, but refer to applications that are not supported in Release 09.00.00.00:


Acronym Application


Event Log Structure


Importance Levels

The Event Log allows you to prioritize informational messages by specifying Importance Levels during the Event Log configuration process. Log messages that are below the specified level are discarded.

Table 15-3 describes the types of messages that are recorded with each setting.

SF

SF-PI

SF-PIC

SF-PIX

SF-PIX_BP

SF-PX_INI

SF-PX_INT

Phnx-PiATM

Phnx-PISch

Phnx-TrATM

Phnx-TrBU

Phnx-Charm

Phnx-DevTree

Phnx-Mach

Phnx-OC12c

Phnx-OC48c

Phnx-CallProc

Phnx-Voyager

SF-PIX_QP

SF-PIX_SCH

SF-Voyager

1 This application not supported in Release 09.00.00.00.


Acronym Application

Table 15-3. Importance Level Settings

Importance Level Records ..

High (default) Errors, warnings, and high-level informational messages.

Medium Errors, warnings, and high and medium-level informational messages.

Low Errors, warnings, and informational messages.

Fatal Fatal errors.

Critical Critical and fatal errors.

Warning Warnings, critical, and fatal errors.

Disable Loggings that are disabled.



Managing the Event LogConfiguration Process Overview

Configuration Process Overview

To enable, configure, and access the Event Log using console commands, complete the following steps:

1. (Optional) Set remote logging variables. See “Configuring Remote Event Logging With Navis EMS-CBGX” on page 15-17 for instructions.

2. Set IOM logging variables. See “Configuring I/O Modules for Event Logging” on page 15-19 for instructions on setting and displaying Logroot Importance Levels.

3. Set application-specific logging variables. See “Configuring Applications for Event Logging” on page 15-20 for instructions on setting and displaying Log Importance Levels.

4. (Optional) Set tracing variables. See “Configuring Tracing” on page 15-21 for instructions on setting and displaying Trace Importance Levels.

5. (Optional) Set additional Event Log options. See “Working With Event Log” on page 15-26 for instructions on how to display and delete log files, how to use the Event Log to log files you previously viewed using the Syslog utility, how to toggle the display of trace events on and off, and how to disable the Event Log.

Note – See the Console Command User’s Reference for CBX 3500, CBX 500, GX 550, and B-STDX 9000 for descriptions of all Event Log console command arguments.


Configuring Remote Event Logging With Navis EMS-CBGX


Configuring Remote Event Logging With Navis EMS-CBGX

To configure remote logging, or the forwarding of log files to a remote location such as a UNIX Workstation, through Navis EMS-CBGX:

1. In the switch object tree (see “Displaying a Switch Tab in the Navigation Panel” on page 2-6), right-click on the switch and select Modify from the popup menu.

The Modify Switch dialog box appears (Figure 15-2).

Figure 15-2. Modify Switch Dialog Box

2. Select the Event Log tab.

3. Complete the Event Log tab fields, as described in Table 15-4.

Table 15-4. Modify Switch: Event Log Tab Fields

Field Action

Default Remote Log Collection Station Enter the IP address of the node where switch events should be logged.

Default Remote Log Directory Path Enter the directory path for where switch events should be logged on the remote log collection station. The default is /tmp/.

Default Remote Log Flush Time Enter the default flush time in seconds for the remote event log. This value may be between zero and 2 to the 31st power. The default value is 120.



Managing the Event LogConfiguring Remote Event Logging With Navis EMS-CBGX

4. When you have completed the Event Log tab fields, choose OK.

The Modify Switch dialog box closes.

Default Remote Log Flush Threshold Enter the default flush threshold for the remote event log. This value may be between zero and 2 to the 31st power. The default value is 65535.

Remote Logging Level From the pull-down menu, select the remote logging level. The default is Warning.

Log messages whose Importance Level is below the Remote Logging Level will not be sent to the remote logging collection station. See “Importance Levels” on page 15-15 for more information on Importance Levels.

Log Root Level From the pull-down menu, select the logroot importance level. The default is critical.

Logroot messages whose Importance Level is below the Log Root Level will not be sent to the remote logging collection station. See “Importance Levels” on page 15-15 for more information on Importance Levels.

Table 15-4. Modify Switch: Event Log Tab Fields (Continued)

Field Action


Configuring I/O Modules for Event Logging


Configuring I/O Modules for Event Logging

The Logroot Importance Level is a variable that controls the level of logging on an IOM.

The set logroot console command sets the Logroot Importance Level for one or more cards (slots). The show logroot console command displays the Logroot Importance Level variable(s) of one or more slots.

Setting Logroot Importance Level(s)

Enter the following command to set the Logroot Importance Level(s):

set logroot {<level> | default } [<slot_range> | all]

Help

Specified with no arguments, set logroot gives help on the command. The system prompts you to enter an Importance Level and Slot Range.

Examples

• set logroot default all

Sets the Logroot Importance Level to default (High) on all active slots.

• set logroot low allSets the Logroot Importance Level to Low on all active slots.

• set logroot critical 1Sets the Logroot Importance Level to CRITICAL on slot 1.

• set logroot fatal 1,3,6

Sets the Logroot Importance Level to FATAL on slots 1, 3, and 6.

Displaying Logroot Importance Level(s)

Enter the following command to display the Logroot Importance Level(s):

show logroot [<slot_range> | all]

Examples

• show logroot allDisplays the Logroot Importance Level of all active slots.

• show logroot 1Displays the Logroot Importance Level of slot 1.

• show logroot 1,3,6-8Displays the Logroot Importance Level of slots 1, 3, 6, 7, and 8.



Managing the Event LogConfiguring Applications for Event Logging

Configuring Applications for Event Logging

After configuring the Event Log on the IOM, you can set application-specific logging variables. Application-specific variables control event logging at a granularity of Application and Slot.

The set evlog console command sets the Log Importance Level variable(s) of one or more applications on one or more slots. The show evlog level console command displays the Log Importance Level variable(s) of all applications on the specified slot.

Setting Log Importance Level(s)

Enter the following command to set the Log Importance Level(s):

set evlog app {<app_name> | all} level {<level> | default}slot [<slot_range> | all]

Help

Specified with no arguments, set evlog gives help on the command. For example:

• If you enter set evlog, the system prompts you to set the following values:

Application:

Importance Level:

Slots:

• If you enter set evlog app {<app_name | all}, the system prompts you to set the remaining values:

Importance Level:

Slots:

• The order in which the variables are entered from the console is not important. For example, you may enter set evlog level warning. The system prompts you to set the remaining values:

Application:

Slots:


Configuring Tracing


Displaying Log Importance Level(s)

Enter the following command to display the Log Importance Level(s):

show evlog level slot [<slot>]

Examples

• show evlog level

Displays the Log Importance Level variables of all applications on slot 1 (default).

• show evlog level slot 6Displays the Log Importance Level variables of all applications on slot 6.

Configuring Tracing

Like Log Importance Levels, Trace Importance Levels are application-specific variables that control event tracing at a granularity of Application and Slot. Tracing is useful for debug purposes, as log messages are forwarded to both the console and the event.log file.

The set evtrace console command sets the Trace Importance Level variable(s) of one or more applications on one or more slots. The show evtrace level console command displays the Trace Importance Level variable(s) of all applications on the specified slot.

Setting Trace Importance Level(s)

Enter the following command to set the Trace Importance Level(s):

set evtrace app {<app_name> | all} level {<level> | default}slot [<slot_range> | all]

Note – The Logroot Importance Level(s) and Trace Importance Level(s) have an interdependent relationship. For best results, always set the Logroot Importance Level to a lower Importance Level than the Trace Importance Level. For example, if the Logroot Importance Level is set to record messages at a High setting, then the Trace Importance Level should be set to record Warning or Critical messages.



Managing the Event LogConfiguring Tracing

Help

Specified with no arguments, set evtrace gives help on the command. For example:

• If you enter set evtrace, the system prompts you to set the following values:

Application:

Importance Level:

Slots:

• If you enter set evtrace app {<app_name | all}, the system prompts you to set the remaining values:

Importance Level:

Slots:

• The order in which the variables are entered is not important. For example, you may enter set evtrace level warning. The system prompts you to set the remaining values:

Application:

Slots:

Displaying Trace Importance Level(s)

Enter the following command to display the Trace Importance Level(s):

show evtrace level slot [<slot>]

Examples

• show evtrace levelDisplays the Trace Importance Level variables of all applications on slot 1 (default).

• show evtrace level 6Displays the Trace Importance Level variables of all applications of slot 6.


Defining Filters


Defining Filters

Log and trace filters control event logging at the slot and application levels, enabling you to specify application-specific criteria to determine if events are to be logged or discarded. Event messages are saved when they meet the criteria of the filter settings. The result may or may not bypass Importance Level evaluation depending on the type of Filter that is defined.

The set evlog filter command configures the specified log filter with type, keyword, and one to three configuration arguments. The show evlog filter command displays the application log filters on the specified slot.

The set evtrace filter command configures the specified trace filter with type, keyword, and one to three configuration arguments. The show evtrace filter command displays the application trace filters on the specified slot.

Setting Log Filters

Execute the following command to set log filters:

set evlog filter {<APPNAME> | all} [<SLOT RANGE> | all} {help | clear | add | override | suggest} <KEYWORD> [<ARG1>] [<ARG2>] [<ARG3>].

Table 15-5. Log Filter Arguments

Argument Description

<APPNAME> Specifies the application for which log messages should be filtered.

all Specifies that messages generated by any application on the card or slot should be filtered.

<SLOT RANGE>

Identifies the slot or slots to which the specified filter will be applied. You can use commas to specify non-contiguous slot numbers or use slot ranges to specify contiguous slot numbers (for example, 1, 4, 7, 9-12).

all Specifies that messages from all slots on the card should be filtered.

KEYWORD Identifies a keyword from the application’s set of supported console keywords.

<APPNAME> Specifies the application for which log messages should be filtered.

all Specifies that messages generated by any application on the card or slot should be filtered.

ARG1/ARG2 /ARG3

Specifies arbitrary ord32 arguments to be passed to the application for validation and storage.



Managing the Event LogDefining Filters

Example

• set evlog filter snmp all clearClears the SNMP filter for all cards in the switch.

Displaying Log Filters

Execute the following command to display the application log filters on a specified slot:

show evlog filter [<SLOT>]

Example

• show evlog filter 1Displays the log filter value of all applications for slot 1.

Setting Trace Filters

Execute the following command to set trace filters:

set evtrace filter {<APPNAME> | all} [<SLOT RANGE> | all} {help | clear | add | override | suggest} <KEYWORD> [<ARG1>] [<ARG2>] [<ARG3>].

<SLOT> Specifies the slot number for which log filters will be displayed.

Table 15-5. Log Filter Arguments (Continued)

Argument Description

Table 15-6. Arguments for set evtrace filter Command

Arguments Description

<APPNAME> Specifies the application for which trace messages should be filtered.

all Specifies that trace messages generated by any application on the card or slot should be filtered.

<SLOT RANGE>

Identifies the slot or slots to which the specified trace filter will be applied. You can use commas to specify non-contiguous slot numbers or use slot ranges to specify contiguous slot numbers (for example, 1,4,7, 9-12).

all Specifies that messages from all slots on the card should be filtered.

KEYWORD Identifies a keyword from the application’s set of supported console keywords.


Defining Filters


Example

• set evtrace filter snmp all clear

Clears the SNMP filter for all cards in the switch.

Displaying Trace Filters

Execute the following command to display trace filters:

show evtrace filter [<SLOT>]

Examples

• show evtrace filterDisplays the trace filter value of all applications on the last slot entered.

• show evtrace filter 3Displays the trace filter value of all applications for slot 3

ARG1/ARG2 /ARG3

Specifies arbitrary ord32 arguments to be passed to the application for validation and storage.

<APPNAME> Specifies the application for which trace messages should be filtered.

all Specifies that trace messages generated by any application on the card or slot should be filtered.

<SLOT> Specifies the slot number for which trace filters will be displayed. If a <SLOT> argument is not specified, the trace filter for the last slot number entered will be displayed.

Table 15-6. Arguments for set evtrace filter Command

Arguments Description



Managing the Event LogWorking With Event Log

Working With Event Log

This section describes the various options available to you when using the Event Log, including how to:

• display and delete log files

• use the Event Log to log files previously obtained using the Syslog utility

• toggle the display trace events on and off

• disable the Event Log

Displaying Log File Contents

The show evlog and show evlog standby console commands display the contents of the log file that resides on an active or standby SP/NP.

Active SP/NP

Enter the following command to display the contents of the active log file:

show evlog app {<app_name> | all} slot {<slot>

Standby SP/NP

Enter the following command to display the contents of the standby log file:

show evlog standby

Help

To access the help menu for the show evlog console command, enter h at the show evlog prompt. Table 15-7 describes the various options in the help command output.

Table 15-7. Event Log Help Commands

Command Description

Spacebar Next Page

a Activate output filter

b Go to beginning of log

e Go to end of log

p Display previous page

n Display next page

s Set up output filters




Examples

• show evlog app pvcmgr slot 1Displays all PVCMgr logs from slot 1.

• show evlog slot 4Displays all log messages from slot 4.

Event Log and the Syslog Utility

The Event Log has replaced the Syslog utility in the current release. This section describes how to use the Event Log to view PRAM Sync, upgrade and switchover files that you previously obtained by entering the show syslog console command.

PRAM Sync and Upgrade Files

To view PRAM Sync and upgrade files:

1. Enter the following command to set the Log Importance Level for the Configuration Manager (CgfMgr) application.

set evlog cfgmgr high

u Update mode (active log only)

c Display Event Log codes

q Quit viewer

/ Forward search string

? Reverse search string

. Find again

Table 15-7. Event Log Help Commands (Continued)

Command Description

Note – If you choose to continuously log files for a particular application or slot, the system may display lengthy log files. The Event Log provides a filter mechanism for viewing large event files, enabling you to search by specific date, time, application, or slot. For more information, see “Filtering Log and Trace Files for Display” on page 15-29.

Note – The Importance Level must be set to High to log PRAM Sync, upgrade and switchover files.




2. Perform PRAM Sync or upgrade operations on the switch using the NMS. For more information about PRAM Sync, see the Getting Started User’s Guide for CBX 3500, CBX 500, GX 550, and B-STDX 9000. For more information about switch upgrade operations, see the CBX 3500 Release 09.03.00.00 Switch Software Upgrade Guide.

3. Enter the following command to view PRAM Sync and upgrade files:

show evlog app cfgmgr

Figure 15-3 displays sample output from the show evlog app cfgmgr console command.

Figure 15-3. Sample Configuration Manager Output

Switchover Files

To view switchover files:

1. Enter the following command to set the Log Importance Level for the Redundancy Manager (Rrmgr) application:

set evlog rrmgr high

2. Perform switchover operations on the switch. For more information about switchover operations, see the Switch Module Configuration Guide for CBX 3500, CBX 500, GX 550, and B-STDX 9000.

3. Enter the following command to view switchover files:

show evlog app rrmgr

Figure 15-4 displays sample output from the show evlog app rrmgr console command.




Figure 15-4. Sample Redundancy Manager Output

Help

Table 15-7 on page 15-26 describes the various help options when you enter h at the show evlog command prompt. The commands listed in Table 15-7 replace the following Syslog help commands:

Table 15-8. Syslog Help Commands

Filtering Log and Trace Files for Display

The set evlog setup and set evtrace setup console commands enable you to set filters that control the content of Log and Trace files for display. For example, you can configure a Filter to display only Log files related to the PVCMgr application.

When you enter the Log and Trace console commands, the system provides a menu of configuration steps. In addition, the system gives help on command. For example, when you enter the Filter Label, the system prompts you to configure the next value, Applications.

Setting Log Filters

To set Log Filters:

1. Enter the following Log console command at the system prompt:

set evlog setup

The following selection menu is displayed:

Command Description

n next page

p show previous page

d delete system log file

q quit syslog




2. The following prompt appears at the bottom of the selection menu:

[Filter 1] Enter selection number:>

The system then prompts you to choose a Filter number. You may specify up to 10 Filters to display Log files. After choosing the Filter number, you have a variety of configuration options:

• Enter 2 to assign the Filter a label. The system prompts you to enter the label name. Labeling the Filter enables you to save and use Filters again. You can view and choose your saved Filters by entering 1 from the Selection Menu.

• Enter 3 to specify the Application(s) you want to display. The system prompts you to choose from the following list:

You have the following options when selecting applications to display:

– Enter all to display all applications.

– Enter clear to empty the current list of applications.

Note – Saved Log and Trace Filters can be used interchangeably. For example, if you want to view Trace files using the same parameters you set for a Log Filter, simply choose that Log Filter from the list that appears in Step 2. You can then choose to customize the Filter or activate it immediately.




– To delete a name, enter the name preceded by a '-' (for example, enter -bgp to delete bgp).

– Type <Enter> to quit.

– Type ?<Enter> to show a list of Application names.

• Enter 4 to select a date and time for the system to begin displaying Log files. The system prompts you to use the following format:

MM/DD/YYYY HH:MM:SS

• Enter 5 at the system prompt to select a date and time for the system to stop displaying Log files. The system prompts you to use the following format:

MM/DD/YYYY HH:MM:SS

• Enter 6 to select Importance Level ranges for the files you want to display. The system prompts you to enter a minimum (highest importance) value and a maximum (lowest importance) value. You have the following choices:

– FATAL

– WARNING

– CRITICAL

– HIGH

– MED

– LOW

For example, to record a range of messages from Fatal to Low, enter Fatal as the minimum value and Low as the maximum value.

• Enter 7 to specify the slots from which you want to gather Log files. The system prompts you to choose a slot range from 1-16 on the CBX 500/3500 or 1-12 on the GX 550.

• Enter 8 to select the types of messages you want to display. The system prompts you to choose from the following types of messages:

– 1. Console Trace Messages

– 2. Log File Messages

– 3. All Messages

• Enter 9 to activate and save the Filter, or enter 10 to clear and discard the Filter.

Setting Trace Filters

To set Trace Filters:

1. Enter the following Trace console command at the system prompt:

set evtrace setup




2. Complete the configuration steps and options in Step 2 of the “Setting Log Filters” section on page 15-29, with one exception: when you enter 8 to select the types of messages you want to display, you have the option of displaying only Trace messages.

Filtering Options

This section describes other configuration options available when setting Log and Trace Filters.

To set other Filter options:

• Enter 11 to display all previously configured Filters.

• Enter 99 to quit the configuration process at any time. The Filter will be saved at its present stage of configuration.

• Enter 10 at the system prompt to clear and discard a Filter.

Enhanced Exception Logging

Enhanced Exception Logging uses the Event Log and its reliable logging mechanism. In addition, the Event Log’s Xpnlog application provides output for events collected by Enhanced Exception Logging.

Enhanced Exception Logging’s post-mortem ring buffer also provides an additional level of reliability to the fault logs within the Event Log.

For more information on Enhanced Exception Logging, see “Enhanced Exception Logging” on page 17-13.

Toggling Trace On and Off

Enter the Ctrl + X key sequence (Control and X keys simultaneously) to toggle console display of trace events on and off.

Deleting Log Files

The delete evlog console command deletes the Event Log files for a switch or slot on a switch.

Enter the following command to delete log files:

delete evlog

Examples

• delete evlogDeletes the Event Log files for each slot.




Disabling the Event Log

This section outlines the steps for disabling the Event Log using console commands.

To disable the Event Log:

1. Enter the following command to disable Logroot Importance Levels:

set logroot disable all

2. Enter the following command to disable Log Importance Levels:

set evlog app {<app_name> | all} level {<level> | default}slot [<slot_range> | all]

For example:

set evlog app all level disable slot all

3. Enter the following command to disable Trace Importance Levels (if configured):

set evtrace app {<APPNAME> | all} {<level> | default}level {<level> | default} slot [<slot_range> | all]

For example:

set evtrace app all level disable slot all






16

Managing the Crash Dump System

The crash dump system allows you to generate crash dumps on CBX 500, CBX 3500, GX 550, and B-STDX 9000 switch software.

Overview

Lucent switches incorporate a diagnostic facility called the crash dump system, which increases the ability to determine the cause of a crash, and to diagnose certain problems on active switches.

The following sections explain key concepts and components of the crash dump system:

• “Crash Dump System Components” on page 16-1

• “Crash Dump Files” on page 16-2

• “Live Upload” on page 16-3

• “Memory Regions” on page 16-3

• “Dump Regions” on page 16-3

Crash Dump System Components

Three major components comprise the crash dump system:

• Manager

• Targets

• Clients

The crash dump system can be configured through the console or the NMS. It collects crash dumps, but also provides live upload capabilities for cards that have not crashed.



Managing the Crash Dump System

Crash Dump Manager

The crash dump manager coordinates the activities of the other components and manages the crash dump configuration. It keeps track of all of the crash dump targets, clients, and files on the switch at any given time.

The crash dump manager runs on the active control processor (CP) on a B-STDX 9000 switch, switch processor (SP) on a CBX 500/3500 switch, or node processor (NP) on a GX 550 Multiservice WAN Switch. Each switch has only one crash dump manager instance. The manager controls the crash dump uploader, which is used to get crash dumps off the switch. The uploader is a Trivial File Transfer Protocol (TFTP) client task running on the active CP, SP, or NP.

Crash Dump Targets

The crash dump targets are disk storage areas on the CP, SP, or NP where crash dumps can be stored until they are uploaded. The targets are intended to be temporary storage locations until you can deliver the crash dump to Lucent for analysis. The size of the target depends on the size of the disk.

Crash Dump Clients

Every card in the switch has a crash dump client. The client prepares for a crash by maintaining the:

• crash configuration

• crash dump file ID

• target it will write to when a crash occurs

When a card crashes, the crash dump is sent directly to the crash dump target.

A crash dump client can also be used to upload memory from a live card in the same format as used for the crash dumps.

Crash Dump Files

The switch stores crash dumps temporarily on a crash dump target before you upload them to an NMS.

Note – For cards with Pentium CPU (NP2 and BIO2), you must reboot the crashed card to get the crash dump file on the crash target.

Beta Draft ConfidentialManaging the Crash Dump System


Live Upload

The crash dump system has a secondary purpose which is to provide a way to upload memory from a card without having to crash the card. This can be very useful for debugging certain types of issues, such as memory leaks. Live upload produces the same type of file as a crash dump.

Memory Regions

For the purposes of the crash dump system, any specific card defines a number of memory regions, which are regions of physical memory or register spaces. Each memory region has a recognizable name, such as intelligent random access memory “(IRAM)” or “IRAM-code.” The actual size and starting address of a memory region is independent of its name, so that “IRAM” on one module may be eight megabytes, while “IRAM” on another module may be 16 megabytes. Similarly, the starting address and length of “IRAM-code” could differ between two software versions.

Memory regions are not part of the crash dump system configuration; rather, they provide a logical naming structure on which the configuration is based.

Dump Regions

The crash dump system configuration consists of a set of dump regions. Each dump region defines the part of a memory region that is incorporated into the resulting crash dump file. You can configure dump regions on a card-by-card basis.

For example, you can specify “all of IRAM” or “all of IRAM-code.” You can also specify portions of a memory region, such as “the first megabyte of FMEM.” This convention allows the crash dump configuration to remain unchanged even though addresses and sizes are physically changing from card-to-card and from one switch software build to another switch software build.

Each card has two sets of dump regions:

• Crash Dump Set — Defines what gets saved in a crash dump.

• Live Upload Set — Defines what gets saved in a live upload to the NMS.

The sets are independent of each other, but will be identical unless you make a change through the console to one set or the other.



Managing the Crash Dump SystemDisk Storage Considerations

Disk Storage Considerations

Crash dump files have the potential to be very large - up to:

• 200 MB on a CBX 3500 switch running software release 9.3.x.x

• 152 MB on a CBX 500 switch running software release 3.5.x.x,

• 144 MB on a GX 550 switch running software release 1.5.x.x.

• 174 MB on a B-STDX 9000 switch running software release 6.5.x.x

You can assume that on CBX 3500 switch and GX 550 switch you already have sufficient disk space.

You should also verify that the NMS has sufficient disk space to handle large crash dump files.

Using the Crash Dump System

This section provides a tutorial on using the crash dump system.

In most cases, you do not need to modify the default configuration, except to increase the time allotted for the crash dump to occur (see “Configuring Crash System Switch Parameters” on page 16-9 for more information about increasing the time-out). The default configuration already includes all memory regions that are expected to be of the most use for crash dump analysis. For certain problems, it may be necessary to add additional regions or change the default order.

Getting a Crash Dump

You can get two kinds of crash dump files: incomplete and complete.

Incomplete crash dumps occur when the timeout is less than the time required to write the crash dump to disk. The default configuration virtually guarantees an incomplete crash dump.

To get a complete crash dump of a card (which is the most useful kind of crash dump), you must change the card configuration. Each card has a crash dump time-out parameter. If you set the time-out to zero, the card will write the crash until it is complete. The default time-out of 25 seconds provides enough time for about 2 megabytes of data. See “Configuring Crash System Card Parameters” on page 16-14 for more information about changing the time-out.

Warning – Never power off a CP, SP, or NP while a crash dump is generating — allow the crash dump to finish. Disk corruption problems may result if you power off a CP, SP, or NP while a crash dump is generating.




The following example illustrates a complete interrupt vector corruption crash. The example uses console commands.

First, using the show crash client command, you list all the crash dump clients:

atsf## show crash client

Card Target FileId Timeout State

1 1 28 25 Ready

2 2 29 25 Disabled4 2 23 25 Ready6 2 19 25 Ready7 2 20 25 Ready9 2 22 25 Ready10 2 24 25 Ready

11 2 27 25 Ready13 2 26 25 Ready15 2 25 25 Ready

Second, the card crashes. Notice in the output for the two commands below that both the crash dump client state and the card state have changed to “crashing.” This is how you can detect that a card is crashing. Note that a crashing CP, SP, or NP will not appear in the crash dump client list and will have a card state of Unknown.

atsf## show crash client

Card Target FileId Timeout State

1 1 28 25 Ready2 2 29 25 Disabled4 2 23 25 Ready

6 2 19 25 Ready7 2 20 25 Ready9 2 22 25 Ready10 2 24 25 Ready11 2 27 25 Ready13 2 26 25 Ready

15 2 25 0 Crashing

Note – When an IOP, IOM, or BIO card crashes, the red LED will blink. When a CP, SP, or NP crashes, the red switch LED remains solid.



Managing the Crash Dump SystemUsing the Crash Dump System

atsf## show card state

Card State

1 Active2 Active3 Unknown

4 Active5 Unknown6 Active7 Active8 Unknown9 Active

10 Active11 Active12 Unknown13 Active14 Unknown15 Crashing

16 Unknown

You should monitor the crash dump state to determine when the crash completes.

atsf## show crash file

FileId Targ Card Error Size Time Year/Mo/Dy State

21 1 7 20.0 2539306 16:17 1999/02/25 Uploaded18 2 2 20.0 151192831 16:30 1999/02/25 Uploaded

25 2 15 0.0 0 21:15 1999/03/01 Writing




25 2 15 0.0 0 21:15 1999/03/01 Writing




25 2 15 20.0 9721402 21:15 1999/03/01 Unprotected




Retrieving Crash Dump Files from the Switch

To retrieve a crash dump file from the switch, you must initiate a crash dump file upload. This can be accomplished with either of the following:

• The NMS. See “Viewing and Uploading a Crash Dump File” on page 16-12 for more information.

• The crash upload command. See “Uploading Crash Dump Files from the Console” on page 16-31 for more information.

The crash dump file is uploaded via TFTP. The IP address that you provide to the uploader should be the address of an NMS that runs the Lucent version of tftpserv. Do not use any other TFTP daemon.

You can also configure the crash dump system to upload crash dump files automatically through either the NMS (permanently) or a console command (temporarily). See “Configuring Crash System Switch Parameters” on page 16-9 for more information about configuring automatic upload through the NMS. See “Enabling Automatic Upload from the Console” on page 16-26 for more information about configuring automatic upload from the console.

The following example shows a crash dump file upload initiated from the console.



21 1 7 20.0 2539306 16:17 1999/02/25 Uploaded18 2 2 20.0 151192831 16:30 1999/02/25 Uploaded25 2 15 20.0 9721402 21:15 1999/03/01 Unprotected

atsf## crash file upload 25 192.168.11.5

"/tftpboot/crash/atsf.15.25"

Default upload IP address : 0.0.0.0Default filename or path : /tftpboot/crash/Uploader state : Upload in progress

Current upload IP address : 192.168.11.5Current upload filename : /tftpboot/crash/atsf.15.25

You can monitor the status of the upload by showing the uploader state or the file state.

atsf## show crash upload

Default upload IP address : 0.0.0.0Default filename or path : /tftpboot/crash/Uploader state : Upload in progress

Current upload IP address : 192.168.11.5Current upload filename : /tftpboot/crash/atsf.15.25



Managing the Crash Dump SystemUsing the Crash Dump System



21 1 7 20.0 2539306 16:17 1999/02/25 Uploaded18 2 2 20.0 151192831 16:30 1999/02/25 Uploaded25 2 15 20.0 9721402 21:15 1999/03/01 Uploading

atsf## show crash upload

Default upload IP address : 0.0.0.0Default filename or path : /tftpboot/crash/Uploader state : Ready



21 1 7 20.0 2539306 16:17 1999/02/25 Uploaded18 2 2 20.0 151192831 16:30 1999/02/25 Uploaded25 2 15 20.0 9721402 21:15 1999/03/01 Uploaded

At this point, the crash dump file is on the NMS.

Changing the Client Configuration

If you want to change the crash dump configuration or live upload configuration, you must manipulate the region configuration. There are two region configuration sets, one for the crash dump and one for the live upload. The sets are essentially independent, although changing the configuration through the NMS will update both sets. See “Configuring Crash System Card Parameters” on page 16-14 for more information.

Beta Draft ConfidentialManaging the Crash Dump SystemConfiguring the Crash Dump System


Configuring the Crash Dump System

When you configure the crash dump system, you configure the following:

Crash System Switch Parameters — Parameters that control automatic upload of files to the NMS, automatic protect mode, and display of the crash manager states and crash dump uploader.

Crash System Card Parameters — Parameters that control the configuration of crash dump clients and target.

Configuring Crash System Switch Parameters

To configure crash system switch parameters:

1. In the switch tab (see “Displaying a Switch Tab in the Navigation Panel” on page 2-6), right-click on the switch and select Crash Config from the popup menu.

The Server Details dialog box appears (Figure 16-1).

Figure 16-1. Server Details Dialog Box

2. Enter the UNIX login name and password for the machine on which the Provisioning Server is installed, and choose OK.

The Modify the Switch Crash Configuration dialog box appears (Figure 16-2).

Table 16-1 describes the display-only fields for the switch crash configuration.



Managing the Crash Dump SystemConfiguring the Crash Dump System

Figure 16-2. Modify the Switch Crash Configuration Dialog Box



3. Complete the Modify the Switch Crash Configuration dialog box fields, as described in Table 16-2.

Table 16-1. Modify the Switch Crash Configuration Dialog Box,Display-Only Fields

Field Displays...

Manager In Slot The slot number of the active CP/SP/NP.

Manager State The current crash dump manager state:

• Ready – Both crash dump targets and crash dump clients exist.

• Initializing – The crash dump manager is initializing.

• No-Clients – No crash dump clients or targets exist.

• No-Targets – No crash dump targets exist, but crash dump clients exist.

• Crashing – The card that runs the crash dump manager is crashing.

Upload State The current state of the crash dump uploader, which is responsible for uploading files to the NMS:

• Ready – The uploader is ready to upload files.

• Uploading – A file is currently uploading.

• Aborted – The last upload was aborted.

• Failed – The last upload failed.

• Init-Delay – The uploader is in a delay period after a reboot or switchover.

Uploading To The IP address of the NMS to which a crash dump file is currently uploading. This field is blank if a file is not currently uploading.

Uploading File The default filename or path used for a crash dump file upload.

Targets The current number of crash dump targets on the switch.

Clients The current number of crash dump clients on the switch.

Files The current number of crash dump files on the switch.




4. When you have completed the fields, choose OK to save the changes.

The Modify the Switch Crash Configuration dialog box closes.

Viewing and Uploading a Crash Dump File

To view information for crash dump files and load a crash dump file to the NMS:

1. In the switch tab (see “Displaying a Switch Tab in the Navigation Panel” on page 2-6), right-click on the switch, and select Crash Config from the popup menu.

The Modify the Switch Crash Configuration dialog box appears (Figure 16-2). The switch crash dump files appear at the bottom of the dialog box. Table 16-3 describes the fields that appear for each crash dump file.

Table 16-2. Modify the Switch Crash Configuration Dialog Box Fields

Field Action

Enable Auto Upload Select the check box to automatically upload crash dump files to the NMS when they are generated. Lucent recommends that you check Enable Auto Upload.

Clear the check box to disable automatic upload of crash dump files.

Enable Auto Protect Select the check box to automatically protect the file from deletion when it is generated. Once protected, you can select the file and choose File Protect to unprotect it (that is, make it available for deletion).

Clear the box to disable automatic protection. Lucent recommends that you disable automatic protection.

Upload IP Enter the IP address of the NMS to which crash dump files are uploaded. If you specify 0.0.0.0 (the default), the files are uploaded to the last NMS in the community list.

Upload Path Enter the path on the NMS where crash dump files are stored. You may specify a directory or a filename. If the path ends in a slash (/), a directory is assumed and the filename is generated automatically. If the path does not end in a slash, a filename is assumed.

Server Directory Use this file tree to browse and select the Upload Path.



2. Verify that the crash system switch parameters have been set (see “Configuring Crash System Switch Parameters” on page 16-9).

Table 16-3. Crash Dump File Fields

Field Displays...

FileId The most recent (and internally-assigned) ID of the file in this row.

Target Slot The slot number of the module where the crash dump files are stored.

Client Slot The slot number of the module associated with the crash dump client that generated the crash dump file.

Error A diagnostics error code that provides a reason for the crash. These are the same codes that are generated by background diagnostics.

Size The size, in bytes, of the crash dump file.

Time The time at which the crash dump file was generated Greenwich Mean Time (GMT).

State One of the following:

• Protected – The file cannot be deleted or overwritten by another crash dump file.

• Unprotected – The file can be deleted or overwritten by another crash dump file.

• Uploading – The file is currently uploading to the NMS. The file is protected during an upload.

• Uploaded – The file has been uploaded to the NMS. The file is unprotected once it is uploaded.

• Upload-pending – The file is waiting to be uploaded. The file is protected while it waits.

• Storing – The file is being received from a crashing card. The file is protected while it is being received.

• Delete – The crash dump file is being deleted. The file cannot be overwritten while it is being deleted.

• Upload-failed – The file failed to upload; it is protected.

• New – The file is new to the manager – the actual state is still unknown; it is protected.




3. Select the file you want to upload from the table at the bottom of the dialog box, and choose Upload.

The file field displays the name of the file that is uploading. The State field for the file displays Uploading while the file is uploading. Once the file has been successfully uploaded, the State field displays Uploaded.

4. Choose OK when you are done uploading.


Protecting and Unprotecting a Crash Dump File

The file state in the Modify the Switch Crash Configuration dialog box (Figure 16-2) determines whether or not a crash dump file can be deleted. A crash dump file can be deleted only if its state is Unprotected.

To change the state of a file:

1. In the switch tab (see “Displaying a Switch Tab in the Navigation Panel” on page 2-6), right-click on the switch and select Crash Config from the popup menu.

The Modify the Switch Crash Configuration dialog box appears (Figure 16-2). The switch crash dump files appear at the bottom of the dialog box.

2. Select the file.

3. Choose File Protect. The state of the file changes from Protect to Unprotect or from Unprotect to Protect.

4. Choose OK.


Configuring Crash System Card Parameters

You can configure crash system parameters for each card in the switch. These parameters control the configuration of crash dump clients and target.

Minimum Card Crash Dump Configuration

The following memory regions should be defined for each card as a minimum crash dump configuration:

• heap

• trace

• trace-save

• i960-data

• psos-data



• fmem

• heap-dirty

• i960-registers

• i960-control

• psos-static

Refer to the Modify the Card Crash Dump dialog box (Figure 16-3) to set and verify these regions.

Modify Crash System Card Parameters

To configure crash system card parameters:


2. Right-click on the module and select Set Crash Dump from the popup menu.

The Modify Card Crash Dump dialog box appears.

Table 16-4 describes the display-only fields for the Modify Card Crash Dump dialog box.

Figure 16-3. Modify Card Crash Dump Dialog Box




Table 16-4. Modify Card Crash Dump Dialog Box, Display-Only Fields

Field Displays...

Target State One of the following target states:

• Ready – The target is ready.

• Disabled – The target is disabled. To re-enable the target, specify Enable in the Target field.

• Initializing – The target has initialized, but is not yet fully operational.

• Rx-dump – The target is receiving a crash dump file.

• Full – The target storage capacity is full. No more crash dump files may be stored. Consider deleting old crash dump files.

• Read-only – The target is read-only.

• Crashing – The card is crashing.

• None – The target is available on this card.

Target Type One of the following target types:

• Active-disk – An active CP/SP/NP target is on the disk.

• Standby-disk – A standby CP/SP/NP target is on the disk.

• Standby-heap – A standby CP/SP/NP target is stored in heap space.

• Standby-fmem – A standby CP/SP/NP target is stored in FMEM.

• None – No target exists.

Target Files The number of crash dump files (if any) on the target for the card (if a target exists).

Target Size The total amount of storage space at the target (in bytes).

Target Free The amount of available storage space at the target (in bytes).



3. Configure the card crash attributes as described in Table 16-5.

Client State One of the following client states:

• Ready – The card is ready to generate a crash dump file in the event of a crash.

• Disabled – Crash dumps have been disabled for the card. Specify Enable in the Client field to re-enable crash dumps.

• No-Target – The client has not been assigned a target to which it can write crash dump files.

• Initializing – The client has initialized, but is not yet fully operational.

• Dumping – The card is uploading a crash dump file.

• Crashing – The card is crashing.

• None – The card does not have a crash dump client.

Client File ID The ID of the crash dump file that will be generated if the card crashes.

Target Slot The slot number of the module where the crash client file will be stored.

Table 16-5. Modify Card Crash Dump Dialog Box Field

Field Action

Target From the pull-down list, select one of the following:

• Enable – Enables the crash dump target on the CP, SP, or NP.

• Enable Medium – Increases the crash dump system’s priority, but not to the highest priority. This selection is service-affecting – switch performance slows significantly. Do not choose Enable Medium without the approval of Lucent TAC.

• Enable High – Increases the crash dump system’s priority to the highest priority. This selection is service-affecting – switch performance slows significantly. Do not choose Enable High without the approval of Lucent TAC.

• Disable – Crash dumps cannot be generated.

Table 16-4. Modify Card Crash Dump Dialog Box, Display-Only Fields (Continued)

Field Displays...




4. When you have completed the fields, choose OK to save the changes.

The Modify Card Crash Dump dialog box closes.

Displaying Dump Region Configuration as Viewed By The Switch

To display the dump region configuration for a card as viewed by the switch:


2. Expand the module (Figure 16-4).

Client From the pull-down list, select one of the following:

• Enable – Enables the crash dump client for the card.

• Force Enable – Forces the crash dump client to be enabled regardless of any hardware or software restriction (such as an SP restriction). Do not choose Force Enable without the approval of the Lucent TAC.

• Disable– Crash dumps cannot be generated.

Client Timeout Specify the amount of time, in seconds, that the card will wait before terminating a crash dump. For example, if you specify 30, the card terminates a crash dump after 30 seconds, regardless of whether the crash dump has completed.

If you set the time-out to zero, the card will never time-out. The card will continue generating the crash dump until completion. However, the card may potentially be out of service for a longer period of time.

You must allow enough time for crash dumps to complete. However, if you find that crash dumps are taking too long to complete, you can manually terminate crash dumps while in progress for modules other than CPs, SPs, and NPs by issuing the following command from the switch console:

reset card slot

where slot specifies the module’s slot number.

For CPs, SPs, and NPs, do not attempt to manually terminate a crash dump. Allow the crash dump to complete.

Table 16-5. Modify Card Crash Dump Dialog Box Field (Continued)

Field Action



Figure 16-4. Crash Regions Node

3. Right-click on the Crash Regions class node and select On Switch Crash Regions from the popup menu.

The On Switch Crash Dump Regions dialog box appears (Figure 16-5).

Figure 16-5. On Switch Crash Dump Regions Dialog Box

Table 16-6 describes the Switch Crash Dump Regions dialog box fields.

Table 16-6. On Switch Crash Dump Regions Dialog Box Fields

Field Displays...

Index An internal value that uniquely identifies the region.

Priority The priority that you assigned to the dump region. Regions are saved in priority order. The lowest-numbered priority is saved first, followed by the next lowest-numbered priority, and so on. For example, a region assigned a priority of 15 is saved before a region assigned a priority of 16.

Region ID The dump region’s memory region (for example, iram-code). Each dump region defines part of a memory region. This part is a range of memory defined by the offset and length. Minimum crash configuration for each card should include the following regions: heap, trace, trace-save, i960-data, psos-data, fmem. heap-dirty, i960-registers, i960-control, and psos-static.




4. If you want to update the dump region fields, choose Refresh.

5. When you are done viewing the fields, choose Close.

The On Switch Crash Dump Regions dialog box closes.

Configuring Dump Regions

To configure a dump region:




3. Right-click on the Crash Regions class node and select Add from the popup menu.

The Add Card Crash Dump Region dialog box appears (Figure 16-7).

Offset A hexadecimal number that specifies the start of the dump region’s memory range. Zero enumeration is used. For example, a value of 0 means that the dump region begins at the first byte of the memory region. A value of b (hexadecimal 11) means that the dump region begins at the twelfth byte of the memory region.

Length A hexadecimal number that specifies the length of the dump region from the offset. For example, if you specify an offset of b and a length of 4d2, the dump region will consist of all the memory from the twelfth byte (byte number 11) of the dump region’s memory region to the 1246th byte (byte number 1245) of the dump region’s memory region (that is, a length of 1234 bytes, starting at the twelfth byte and ending at the 1246th byte). A zero (0) indicates “until the end.”

Table 16-6. On Switch Crash Dump Regions Dialog Box Fields

Field Displays...



Figure 16-7. Add Card Crash Dump Region

4. Complete the Add Card Crash Dump Region dialog box fields as described in Table 16-7.

Table 16-7. Add Card Crash Dump Region Dialog Box Fields

Field Description

Index You cannot modify this field. The index value is assigned automatically by the system.

Type Select the memory region type from the pull-down list.

Priority Specify the dump region priority. The lowest-numbered priority is saved first, followed by the next lowest-numbered priority, and so on. For example, a region assigned a priority of 15 is saved before a region assigned a priority of 16.

Observe the following rules when specifying a priority value:

• The priority value cannot be less than five.

• The priority value cannot be divisible by 10 (for example, 10, 20, 30, and so on).

Offset After using the Available Regions on Card dialog box to check the available segments (see “Displaying Memory Regions” on page 16-24), specify the start of the dump region’s memory range in hexadecimal format. For example, a value of zero means that the dump region begins at the first byte of the memory region. A value of b means that the dump region begins at the eleventh byte of the memory region.




5. When you completed the Add Card Crash Dump Regions dialog box fields, choose OK to save the changes.

The Add Card Crash Dump Region dialog box closes.

Viewing Dump Regions

To view a dump region:



Figure 16-8. Crash Regions Node Expanded

3. Expand the Crash Regions class node.

4. Right-click on the Crash Regions class node and select View from the popup menu.

The View Card Crash Dump Region dialog box appears (Figure 16-9).

Length After using the Available Regions on Card dialog box to check the available segments (see “Displaying Memory Regions” on page 16-24), specify the length of the dump region from the offset in hexadecimal format. For example, if you specify an offset of b and a length of 4d2, the dump region will consist of all the memory from the eleventh byte of the dump region’s memory region to the 1245th byte of the dump region’s memory region (that is, a length of 1234 bytes, starting at byte 11 and ending at byte 1245).

If you specify a length of zero (0), the dump region will range from the offset to the end of the memory region.

Table 16-7. Add Card Crash Dump Region Dialog Box Fields

Field Description



Figure 16-9. View Card Crash Dump Region

Table 16-8 describes the View Card Crash Dump Region dialog box fields.

5. When you are done viewing the View Card Crash Dump Region dialog box fields, choose Close.

The View Card Crash Dump Region dialog box closes.

Table 16-8. View Card Crash Dump Region Dialog Box Fields

Field Description

Index Displays the index value assigned automatically by the system.

Type Displays the memory region type.

Priority Specify the dump region priority. The lowest-numbered priority is saved first, followed by the next lowest-numbered priority, and so on. For example, a region assigned a priority of 15 is saved before a region assigned a priority of 16.

Offset Displays the start of the dump region’s memory range in hexadecimal format. For example, a value of zero means that the dump region begins at the first byte of the memory region. A value of b means that the dump region begins at the eleventh byte of the memory region.

Length Displays the length of the dump region from the offset in hexadecimal format. For example, if the offset is b and the length is 4d2, the dump region will consist of all the memory from the eleventh byte of the dump region’s memory region to the 1245th byte of the dump region’s memory region (that is, a length of 1234 bytes, starting at byte 11 and ending at byte 1245).

If the length is zero (0), the dump region will range from the offset to the end of the memory region.




Deleting a Dump Region

To delete a dump region on a card:



Figure 16-10. Crash Regions Node Expanded

3. Expand the Crash Regions class node.

4. Right-click on the instance node for the Crash Region you want to delete, and select Delete from the popup menu.

The following message appears: “Are you sure you want to delete the selected objects?”

5. Choose Yes to delete the dump region.

Displaying Memory Regions

To display memory regions for a card:




3. Right-click on the Crash Regions class node and select Show Memory from the popup menu.

The Available Regions on Card dialog box appears (Figure 16-12).



Figure 16-12. Available Regions on Card Dialog Box

Table 16-9 describes the Available Regions on Card dialog box fields.

4. If you want to update the fields, choose Refresh.

5. When you are done viewing the dialog box fields, choose Close.

The Available Regions on Card dialog box closes.

Uploading Card Memory

To upload a card’s memory to the NMS:

1. Open the On Switch Crash Dump Regions dialog box (see “Displaying Dump Region Configuration as Viewed By The Switch” on page 16-18).

2. Choose the Live Upload button.

The Live Upload dialog box appears.

Figure 16-13. Live Upload Dialog Box

Table 16-9. Available Regions on Card Dialog Box Fields

Field Description

Name Displays the name of the memory region.

Start Displays the hexadecimal memory address where the region starts.

Stop Displays the hexadecimal memory address where the region ends.

Refresh Refreshes fields in the dialog box.



Managing the Crash Dump SystemUsing Crash Dump Console Commands

3. In the IP Address field, enter the IP address of the NMS to which you want to upload the file.

4. In the Upload Path Directory field, enter the directory path on the NMS where you want to store the file.

5. Choose the Upload button.

The uploading of the file begins.

Using Crash Dump Console Commands

This section discusses crash dump console commands. The section is organized according to the tasks the commands allow you to perform.

To display help at any time, type a question mark (?) at the end of the command line. For example,

crash ?

displays help on the crash command.

As another example,

crash autoprotect ?

displays help on the crash autoprotect command.

Enabling Automatic Crash Dump File Protection from the Console

The following commands allow you to enable and disable automatic crash dump file protection:

crash autoprotect enable

crash autoprotect disable

Enabling automatic crash dump file protection prevents new crash dumps from being overwritten before they are uploaded. Disabling automatic crash dump file protection allows crash dumps to be overwritten at any time.

Enabling Automatic Upload from the Console

The following commands allow you to enable and disable automatic crash dump file upload:

crash autoupload enable

crash autoupload disable




Enabling automatic upload causes crash dump files to be uploaded immediately after the crash dump file has been saved.

Setting Default Automatic Upload Pathname from the Console

The following command allows you to set the default pathname or filename for automatic upload:

crash autoupload filename “path”

If path ends in a slash (/), then it is assumed to be a pathname, and the filename is created automatically from the switch name, crash dump file id, and crashed card number. If path does not end in a slash, it is assumed to be the literal filename.

You must enclose path in quotation marks.

Setting Automatic Upload IP Address from the Console

The following command allows you to set the IP address of the NMS to which crash dump files are automatically uploaded:

crash autoupload ip ip_address

If you set ip_address to 0.0.0.0, the crash dump files are uploaded to the last NMS in the community list.

Enabling Crash Dump Client from the Console

The following commands allow you to enable and disable the specified crash dump client:

crash client enable slot

crash client disable slot

You specify the client by specifying the slot number of the client’s card as the value of slot.

These commands only affect the writing of a crash dump file in the event of a crash. The do not affect the ability of the client to perform a live upload.

Resetting Crash Dump Client State to the Default Valuefrom the Console

The following command allows you to reset the state of the specified crash dump client to the default value:

crash client state slot default




You specify the client by specifying the slot number of the client’s card as the value of slot.

Changing Crash Dump Client State from the Console

The following command changes the state of the specified crash dump client to the specified state value:

crash client state slot state

You specify the client by specifying the slot number of the client’s card as the value of slot. The value of state can be one of the following:

1 — The client has initialized, but is not yet fully operational.

2 — The client has not been assigned a target (CP, SP, or NP) to which it can write crash dump files.

3 — The card is ready to generate a crash dump file in the event of a crash.

4 — The card is uploading a crash dump file.

5 — The card is crashing.

6 — Crash dumps are disabled for the card.

7 — The card does not have a crash dump client.

Changing Target from the Console

The following command forces a change of the specified target for the specified client:

crash client target slot_client slot_target

You specify the client by specifying the slot number of the client’s card as the value of slot_client, and you specify the target by specifying the slot number of target’s CP, SP, or NP as the value of slot_target.

Note – The success of this command depends on the current state of the client. This command is for debugging purposes only. Changing the state may adversely affect the operation of the crash dump system.

Note – This command is for debugging purposes only. Changing the state may adversely affect the operation of the crash dump system.




If there is no target on the card specified by slot_target, then the target is reassigned automatically. This change is not permanent, and may be undone by the crash dump system in response to various events. Note: this command is for debugging purposes only.

Changing Client Time-out from the Console

The following commands allow you to change the time-out for the specified client:

crash client timeout slot default

crash client timeout slot none

crash client timeout slot timeout

You specify the client by specifying the slot number of the client’s card as the value of slot. You can change the time-out to default to restore the PRAM-configured time-out, or you can change the time-out to none to specify no time-out, in which case the entire crash dump is written until completion (that is, never times out). Otherwise, set the time-out to the number of timeout seconds (for example, 30).

Uploading Card Memory from the Console

The following commands allow you to initiate a live upload of memory from the specified client to the NMS:

crash client upload slot

crash client upload slot ip_address

crash client upload slot ip_address “filename”

You specify the client by specifying the slot number of the client’s card as the value of slot. You can specify an IP address and a filename (specify the full pathname of the file) or use the defaults for automatic upload. You must enclose the pathname in quotation marks.

Configuring Crash Dump Regions from the Console

The following commands add or modify dump regions for the specified client:

crash config slot add index priority region

crash config slot add index priority region offset

Note – Do not use the crash config command unless under the direction of Lucent TAC personnel. If you want to configure the crash dump client on your own, use the NMS. See “Configuring the Crash Dump System” on page 16-9 for details.




crash config slot add index priority region offset length

crash config set slot add index priority region

crash config set slot add index priority region offset

crash config set slot add index priority region offset length

You specify the client by specifying the slot number of the client’s card as the value of slot. If a dump region entry already exists at the specified index, then that entry is overwritten.

The value of set may be upload or crash for live upload or crash dump configuration respectively. If you do not specify a value for set, the live upload configuration is changed. The crash dump configuration should only be changed through the NMS if you want the changes to be permanent.

See Table 16-7 on page 16-21 for descriptions of index, priority, region, offset, and length.

Setting Client Configuration to the Default Region Set from the Console

The following commands allow you to change the configuration of the specified client to the default set of regions:

crash config slot defaults

crash config set slot defaults

You specify the client by specifying the slot number of the client’s card as the value of slot. The value you specify for set may be upload or crash for live upload or crash dump configuration, respectively. If you do not specify a value for set, the live upload configuration is changed. The crash dump configuration should only be changed through the NMS if the changes are to be permanent.

Deleting Regions from the Console

The following commands delete the region specified by index from the configuration of the specified client:

crash config slot delete index

crash config set slot delete index

You specify the client by specifying the slot number of the client’s card as the value of slot. The value you specify for set may be upload or crash for live upload or crash dump configuration respectively. If you do not specify a value for set, the live upload configuration is changed. The crash dump configuration should only be changed through the NMS if you want the changes to be permanent.




Restoring PRAM Client Configuration from the Console

The following commands restore the PRAM configuration of the specified client:

crash config slot pram

crash config set slot pram

You specify the client by specifying the slot number of the client’s card as the value of slot. The value of set may be upload or crash for live upload or crash dump configuration respectively. If you do not specify a value for set, the live upload configuration is changed. The crash dump configuration should only be changed through the NMS if you want the changes to be permanent.

Clearing Client Configuration from the Console

The following commands clear the configuration of the specified client:

crash config slot reset

crash config set slot reset

You specify the client by specifying the slot number of the client’s card as the value of slot. The value of set may be upload or crash for live upload or crash dump configuration respectively. If you do not specify a value for set, the live upload configuration is changed. The crash dump configuration should only be changed through the NMS if you want the changes to be permanent.

Protecting Crash Dump Files from the Console

The following commands protect and unprotect a crash dump file specified by fileid:

crash file protect fileid

crash file unprotect fileid

Removing Crash Dump Files from the Console

The following command removes a crash dump file identified by fileid:

crash file remove fileid

Files can only be removed when they are in unprotected or uploaded states.

Uploading Crash Dump Files from the Console

The following commands initiate a crash dump file upload to the NMS:

crash file upload




crash file upload fileid

crash file upload fileid ip_address

crash file upload fileid ip_address “filename”

The fileid variable specifies the ID of a crash dump file. If you do not specify a value for fileid, a file that has not been uploaded is selected.

The ip_address variable specifies the IP address of the NMS to which the file is uploaded, and the filename variable specifies the full pathname of the file on the NMS (the pathname must be enclosed in quotes). If you do not specify an IP address or filename, the automatic upload defaults are used.

Synchronizing Crash Dump Components from the Console

The following command synchronizes the crash dump manager state with the crash dump clients and the crash dump targets:

crash reset

Changing Target Size from the Console

The following commands allow you to change the size of the specified target:

crash target attributes slot

crash target attributes slot size

crash target attributes slot size files

You specify the target by specifying the slot number of the target’s CP, SP, or NP as the value of slot. Specify size in number of bytes (for example, 1 MB would be expressed as 1024000). The files value specifies the maximum number of crash dump files that can be stored on the target at any one time.

The following considerations apply when using these commands:

• The changes made by these commands are permanent for disk-based targets.

• Avoid exceeding the default size of the crash dump target, since the disk may become full.

• If you do not specify a value for size, the size of the target is restored to the default size.

• The commands will fail if there are any protected or implicitly protected files on the target.

Note – Changes you make with the other crash dump debugging commands may be undone by this command. This command is for debugging purposes only.




• A beneficial side-effect of the commands is that any space currently used by the target is returned and will not be consumed until more crash dumps are created.

Enabling Targets from the Console

The following commands enable and disable the specified target:

crash target enable slot

crash target disable slot

You specify the target by specifying the slot number of the target’s CP, SP, or NP as the value of slot. When a target is disabled, it does not accept more crash dumps. However, a disabled target can still upload a crash dump file.

Resetting Targets to the Default Value from the Console

The following commands reset the state of the specified target to either the default or the specified state value.

crash target state slot default

crash target state slot state

You specify the target by specifying the slot number of the target’s CP, SP, or NP as the value of slot.

You may specify one of the following values for state:

1 — The target has initialized, but is not yet fully operational.

2 — The target is ready.

3 — The target is receiving a crash dump file.

4 — The target storage capacity is full.

5 — The target is read-only.

6 — The target is disabled. To re-enable the target, specify Enable in the Target field.

7 — The card is crashing.

8 — The target is available on this card.

The commands may or may not succeed, depending on the current state of the target.




Aborting Crash Dump File Uploads from the Console

The following command aborts any crash dump upload currently in progress:

crash upload abort

If any files are waiting to be uploaded, one of those files will begin uploading immediately after this command.

Displaying Crash Dump System Status from the Console

The following command displays the state of the crash dump manager, uploader, clients, targets, and crash dump files:

show crash all

Displaying Crash Dump Client Status from the Console

The following command displays the state of all the crash dump clients on the switch:

show crash client

Displaying the Client Configuration from the Console

The following commands display the configuration of the specified client:

show crash config slot

show crash config slot set

You specify the client by specifying the slot number of the client’s card as the value of slot. The value of set may be upload or crash for live upload or crash dump configuration respectively. If you do not specify a set value, the live upload configuration is displayed.

Displaying Crash Dump File Status from the Console

The following command displays the state of all the crash dump files stored on the switch:

show crash file

Note – The success of this command depends on the current state of the client.

This command is for debugging purposes only. Changing the state may adversely affect the operation of the crash dump system.




Displaying Card Memory Regions from the Console

The following command displays the memory regions defined on the card specified by the card’s slot number:

show crash region slot

Displaying Crash Dump Target Status from the Console

The following command displays the state of the crash dump targets:

show crash target

Displaying Crash Dump Uploader Status from the Console

The following command displays the state of the crash dump uploader:

show crash upload

Displaying Lastcrash Information for Cards from the Console

The following command displays lastcrash information for a specified card:

show crash lastcrash card-number



Managing the Crash Dump SystemCrash Dump System Restrictions

Crash Dump System Restrictions

This section discusses crash dump system restrictions.

CBX 500 SPs

The crash dump system does not directly support crash dumps of CBX 500 SPs because they lack the necessary hardware.

Do not attempt to get crash dumps from an SP without consulting Lucent TAC personnel.

Standby Cards

The crash dump system does not directly support crash dumps for standby cards.

Do not attempt to get crash dumps from a standby card without consulting Lucent TAC personnel.



17

Monitoring Switch Reliability

This chapter describes the reliability features that are available for CBX 500, CBX 3500, and GX 550 switch software. The following sections include:

• “Emergency Action Interface (EAI)” on page 17-2

• “PVC Establishment Rate Control” on page 17-5

• “Path Integrity” on page 17-8

• “Enhanced Fault Manager” on page 17-12

• “Enhanced Exception Logging” on page 17-13

• “PRAM Consistency” on page 17-14

• “Enhanced Standby Hardware (ESHW) Tests” on page 17-18



Monitoring Switch ReliabilityEmergency Action Interface (EAI)

Emergency Action Interface (EAI)

This section describes the Emergency Action Interface (EAI) feature, and includes the following sections:

• “About the Emergency Action Interface (EAI)” on page 17-2

• “Console Commands Supported with the Emergency Action Interface (EAI)” on page 17-3

• “Using the Emergency Action Interface (EAI)” on page 17-3

About the Emergency Action Interface (EAI)

The EAI feature performs the following functions:

• automatically puts the switch into high-priority mode when the SNMP queue exceeds the high water mark to avoid an overload condition.

• allows you to set the console to high-priority mode.

Within high-priority mode, you can run a limited set of commands that will run at a higher priority between the GX 550 node processor (NP) module or CBX 500/3500 switch processor (SP) module and the Network Management System (NMS).

In addition, EAI:

• provides a high level of system access during abnormal events.

• provides a high level of system resource availability to initiate critical alarms during critical events.

• allows the use of a limited set of commands dealing with:

– initializations

– resets

– subsets of query commands (including the nodePoll command)

– specific alarm traps

• expedites specific SNMP console and telnet shell activities.

Beta Draft ConfidentialMonitoring Switch Reliability

Emergency Action Interface (EAI)


Console Commands Supported with theEmergency Action Interface (EAI)

The following console commands can be used when high-priority mode is enabled using the EAI feature:

• show node

• show card

• show software flash

• show software disk

• show software card

• show pram

• reset system

• reset tm

• reset card

• reset pram

Using the Emergency Action Interface (EAI)

You can access the EAI by opening one of the following session types:

• switch console session

• high-priority telnet session

The following sections describe how to open each type of session.

Using EAI with a Switch Console Session

When you open a switch console session, you may lose your connection if the switch becomes overloaded. To ensure that you do not lose your connection, open a high-priority telnet session, using the instructions in “Using EAI with a High-Priority Telnet Session” on page 17-4.

Open a switch console session by performing the following tasks:

1. Telnet into the direct-wired console port of the switch using local practices.

2. From the console window, enter your login name and password.

Note – There is a five-minute timeout limit for high-priority telnet sessions as well as a limit of three simultaneous telnet sessions.



Monitoring Switch ReliabilityEmergency Action Interface (EAI)

3. Using your keyboard, enter the Ctrl + R key sequence (Control and R keys simultaneously) to enter the high-priority mode.

The console prompt will be HP> when you are in high-priority mode.

4. Once you have completed issuing high-priority maintenance commands, enter lowerprio. The lowerprio command returns you to the normal priority level and the console prompt returns to its normal display.

Using EAI with a High-Priority Telnet Session

Open a high-priority telnet session by performing the following tasks:

1. Select the switch for which you want to open a telnet session.

2. Telnet into the switch using the following command:

telnet SwitchIPAddr 2770

where SwitchIPAddr is the IP address of the switch and 2770 initiates a high-priority session. For example: telnet 172.20.101.89 2770

The console prompt will be HP> when you are in high-priority mode.

3. From the telnet window, enter your login name and password.

4. Once you have completed issuing high-priority maintenance commands, enter quit. The quit command ends the high-priority telnet session.

Note – There is a five-minute timeout limit for high-priority telnet sessions as well as a limit of three simultaneous telnet sessions.


PVC Establishment Rate Control



The PVC Establishment Rate Control feature dynamically adjusts the PVC retry rate of the I/O card where the calling endpoint resides.

PVC Establishment Rate Control works with the VC Overload Control feature in the call initiating switch, and reacts to changing conditions in the network by monitoring the PVC establishment success rate and adjusting the retry rate appropriately.

VC Overload Control and PVC Establishment Rate Control

This section describes the differences in how the PVC Establishment Rate Control feature works when the VC Overload Control feature is enabled or disabled.

For information on enabling and disabling the VC Overload Control feature, see the Getting Started User’s Guide for CBX 3500, CBX 500, GX 550, and B-STDX 9000.

PVC Establishment Rate Control When VC Overload Control Is Enabled

When the VC Overload Control feature is enabled, the PVC Establishment Rate Control feature varies the rate between a minimum of 20 calls/sec and the maximum allowed by the card without going into overload. Having VC Overload Control enabled on the call initiating switch sets the upper limit for the PVC re-establishment rate.

PVC Establishment Rate Control When VC Overload Control Is Disabled

When the VC Overload Control feature is disabled, the PVC Establishment Rate Control feature reacts to changing conditions in the network by adjusting the rate from a minimum of 20 calls per second to a maximum of 120 calls per second.

Viewing the Overload Control Setting and the OverloadSeverity Level

The following sections describe how to view the overload control setting and the overload severity level using Navis EMS-CBGX.

Note – You can trace events related to the PVC Establishment Rate Control feature using the Event Log. The application that traces events related to this feature is the PvcMgr. For more information on the Event Log, see Chapter 15, “Managing the Event Log.”



Monitoring Switch ReliabilityPVC Establishment Rate Control

Viewing the Overload Control Setting

To view the overload control setting:

1. In the switch tab (see “Displaying a Switch Tab in the Navigation Panel” on page 2-6), right-click on the switch, and select View from the popup menu.

The View Switch dialog box appears (Figure 17-1).

Figure 17-1. View Switch: Switch Control Tab

2. Select the Switch Control tab.

3. View the Enable Overload Control check box.

A selected check box indicates that the VC Overload Control feature is enabled.

A cleared check box indicates that the VC Overload Control feature is disabled.

4. Choose Close.

The View Switch dialog box closes.




Viewing the Overload Severity Level

To view the overload severity of a module:


2. Right-click on the module whose overload severity you want to view and select Oper Info from the popup menu.


Figure 17-2. View Card Operational Information Dialog Box (IOM)

The Overload Severity value appears in the General tab. The range of the overload severity is 0 to 100. Any value greater than 0 indicates that the card is in overload. A severity of 100 indicates that the card is in the highest overload condition and an application must shed all new service requests.

3. If you want to update the View Card Operational Information dialog box fields, choose Refresh.

4. When you are done viewing the overload severity level, choose Close.



Monitoring Switch ReliabilityPath Integrity

Path Integrity

The Path Integrity feature is available for GX 550 switch. This section describes the Path Integrity feature, and includes the following topics:

• “About Path Integrity” on page 17-8

• “Path Integrity Console Commands” on page 17-8

• “Path Integrity Configuration Example” on page 17-9

• “Viewing Event Log Messages for Path Integrity Information” on page 17-11

About Path Integrity

With the Path Integrity feature, the switch can verify connection data paths on NP1/NP2 and BIO1/BIO2 modules using a combination of:

• Hello Messaging augmented virtual circuit (VC) cell counts, and/or

• a periodic SVC status inquiry

This feature supports ATM services and is enabled using console commands.

Path Integrity Console Commands

Use the following console commands to configure the Path Integrity feature. For more information on these commands, see the Console Command User’s Reference for CBX 3500, CBX 500, GX 550, and B-STDX 9000.

Table 17-1. Path Integrity Console Commands

Console Command Description

path_timers This command sets the various Path Integrity timers.

path_counts This command enables or disables the Path Integrity VC Cell Counts feature on the specified interface.

path_statenq This command enables or disables the Path Integrity SVC Status Enquiry Request feature on the specified interface.

show pathintegrity This command shows the status of the Path Integrity feature (enabled/disabled) and the timer parameters for the specified interface.

show evlog app pie This command shows the Path Integrity entries in the Event Log. If the slot number is omitted, then the Path Integrity entries from the logs for each card are displayed.


Path Integrity


Path Integrity Configuration Example

This section provides an example of how to configure the Path Integrity feature using console commands. For more information on the Path Integrity console commands, see the Console Command User’s Reference for CBX 3500, CBX 500, GX 550, and B-STDX 9000.

Switch Configurations

A circuit is configured between switch 1 to switch 2 with the following setup:

To activate path counts between Switch 1 and Switch 2, perform the following tasks:

1. Configure path integrity for Switch 1:

a. Set the receive timer to 3 minutes for interface number 24, using the following command: path_timers recv 3 24

b. Set the transmit timer to 3 minutes for interface number 24, using the following command: path_timers xmit 3 24

c. Enable path counts for interface number 24, using the following command: path_counts enable 24

d. Display the path counts configuration for interface number 24, using the following command: show pathinteg 24

e. Verify that path counts have been enabled for interface 24 by displaying the Event Log contents on slot 7, using the following command: show evlog app pie 7

Table 17-2. Path Integrity Switch Example

Switch Slot Port Interface Number

VPI VCI

SWITCH 1 7 9 24 10 111

SWITCH 2 5 1 7 10 111

Note – Path timers should be set before path counts, otherwise a five-minute receive timer automatically starts for the interface. This timer prevents an inaccurate “abnormal” reading for the circuit.



Monitoring Switch ReliabilityPath Integrity

2. Configure path integrity for Switch 2:

a. Set the receive timer to 3 minutes for interface number 7, using the following command: path_timers recv 3 7

b. Set the transmit timer to 3 minutes for interface number 7, using the following command: path_timers xmit 3 7

c. Enable path counts for interface number 7, using the following command: path_counts enable 7

d. Display the path counts configuration for interface number 7, using the following command: show pathinteg 7

e. Verify that path counts have been enabled for interface 7 by displaying the Event Log contents on slot 5, using the following command: show evlog app pie 5

Switch 1 Console Example

The following is an example of the console input and output for the Path Integrity configuration on Switch 1:

Switch 1 > path_timers recv 3 24

Switch 1 > path_timers xmit 3 24

Switch 1 > path_counts enable 24

Switch 1 > show pathinteg 24Path Integrity Interface Number: 24 Path Integrity (Counts) Status: enabledPath Integrity (Counts) Recv Timer: 3Path Integrity (Counts) Xmit Timer: 3Path Integrity (Status Enquiry) Status: disabledPath Integrity (Status Enquiry) Timer: 0

Switch 1 > show evlog app pie 7

Active Event Log File

I S# Seq Date Time App. Name Mes-

sage

- -- --- ---- ------------ ----------


Path Integrity


Switch 2 Console Example

The following is an example of the console input and output for the Path Integrity configuration on Switch 2:

Viewing Event Log Messages for Path Integrity Information

Table 17-3 lists some of the Event Log messages that display for the Path Integrity feature when you run the show evlog console command. These messages appear in the Message column of the Event Log output.

Switch 2 > path_timers recv 3 7

Switch 2 > path_timers xmit 3 7

Switch 2 > path_counts enable 7

Switch 2 > show pathinteg 7Path Integrity Interface Number: 7 Path Integrity (Counts) Status: enabledPath Integrity (Counts) Recv Timer: 3Path Integrity (Counts) Xmit Timer: 3Path Integrity (Status Enquiry) Status: disabledPath Integrity (Status Enquiry) Timer: 0

Switch 2> show evlog app pie 5

Active Event Log File

I S# Seq Date Time App. Name Message

- -- --- ---- ------------ ----------

---------------------------

H 05 545 02/19 14:44:51.892 Pie PIE:

Table 17-3. Path Integrity Event Logger Messages

Event Event Logger Message

Path counts enabled PIE: Enabled path_counts, interface=interface

Path counts disabled PIE: Disabled path_counts, interface=interface

Status enquiry enabled PIE: Enabled status enquiry, interface=interface

Status enquiry disabled PIE: Disabled status enquiry, interface=interface

Abnormal circuit path integrity

WARNING: Circuit Off-Normal, interface=interface, vpi=vpi#, vci=vci#



Monitoring Switch ReliabilityEnhanced Fault Manager

Enhanced Fault Manager

The Fault Manager collects and stores data about hardware/software errors that occur on the GX 550 and CBX 500/3500 switches.

The Enhanced Fault Manager feature adds the existing fault manager functionality (previously only on the GX 550 NP1 and NP2 modules) to the following modules:

• Base Input/Output (BIO) module 1

• BIO 2

• all SP modules

• IOM1 modules, including:

– 8-Port ATM DS3/E3

– 4-Port ATM OC-3c/STM-1

– 1-Port ATM OC-12c/STM-4

– 8-Port ATM T1/E1


– 32-Port Channelized T1/E1 FR/IP

– 8-Port Subrate DS3 FR/IP

– 6-Port DS3 FR/IP

– 4-Port Channelized DS3/1 and DS3/1/0 FR/IP

– 4-Port Ethernet


– 3-Port Channelized DS3/1 IMA

– 1-Port Channelized STM-1/E1 IMA

Path counts enabled before timer started

PIE: Out of Sequence Counts Activation: called recv timeout and started a 5-min-receive timer, interface=interface

Table 17-3. Path Integrity Event Logger Messages (Continued)

Event Event Logger Message




Enhanced Fault Manager and Related Reliability Features

The Enhanced Fault Manager is fully integrated to work with the following reliability features:

• Enhanced Exception Logging – The information that is collected by the Enhanced Fault Manager is managed by the Enhanced Exception Logging feature. See “Enhanced Exception Logging” on page 17-13 for more information.

• PRAM Consistency Feature – The Enhanced Fault Manager receives reports of errors detected by PRAM Consistency checks and takes appropriate recovery action to prevent an active SP or NP from switching over to a standby SP or NP that is corrupted. See “PRAM Consistency” on page 17-14 for more information.

• Enhanced Standby Hardware Test – The Enhanced Fault Manager takes appropriate recovery action when test failures occur. See “Enhanced Standby Hardware (ESHW) Tests” on page 17-18 for more information.


The Enhanced Exception Logging feature collects hardware state information on reliability events (for example, failures, crashes, lock-ups, etc.).

This feature provides a standard mechanism for coordinating log information and supports a post-mortem ring buffer. A post-mortem ring buffer is a memory region in a crash dump file that contains the latest information logged through Enhanced Exception Logging.

Enhanced Exception Logging works in conjunction with the Enhanced Fault Manager. The information managed by Enhanced Exception Logging is always related to the types of events processed by the Enhanced Fault Manager.

In addition, Enhanced Exception Logging:

• manages the number sequences for fault events to coordinate related messages and recovery information.

• provides debugging information on events (for example, back traces, parameters, stack, overload status, etc).

• sends messages to the Event Log for driver error logs and other types of driver errors.

Enhanced Exception Logging and the Event Log

Enhanced Exception Logging uses the Event Log and its reliable logging mechanism. In addition, the Event Log’s Xpnlog application provides output for events collected by Enhanced Exception Logging.



Monitoring Switch ReliabilityPRAM Consistency

Enhanced Exception Logging’s post-mortem ring buffer also provides an additional level of reliability to the fault logs within the Event Log.

PRAM Consistency

This section describes the PRAM Consistency feature, and includes the following topics:

• “About PRAM Consistency” on page 17-14

• “Running the PRAM Consistency Test” on page 17-14

• “Event Log Messages for the PRAM Consistency Feature” on page 17-16

• “PRAM Consistency Test Console Commands” on page 17-17

About PRAM Consistency

The PRAM Consistency feature verifies whether there are any differences in the PRAM data configuration files between the active and standby SP/NP modules. For more information about PRAM, see the Getting Started User’s Guide for CBX 3500, CBX 500, GX 550, and B-STDX 9000.

Running the PRAM Consistency Test

To set the PRAM Consistency test:

1. In the switch tab (see “Displaying a Switch Tab in the Navigation Panel” on page 2-6), right-click on the switch and select Test Reliability Features from the popup menu.

The Reliability Features dialog box appears (Figure 17-3).

Figure 17-3. Reliability Features Dialog Box

Note – For more information on the Event Log, see Chapter 15, “Managing the Event Log.”


PRAM Consistency


2. Choose PRAM Consistency test, and then choose OK.

The PRAM Consistency Test dialog box appears (Figure 17-4).

Figure 17-4. PRAM Consistency Test Dialog Box

3. Choose Enable Test to enable the PRAM test for all the modules.

4. Choose Execute to initialize the PRAM test.

CONFIG.1 through CONFIG.16 display the current status of the configuration files between the active and redundant SP/NP for each slot. If the PRAM data configuration files between the active and standby SP/NP modules are not consistent, a Fail condition is displayed.

An Indeterminate condition indicates either that the PRAM Consistency test has not run since the switch was started, there are no redundant SP/NP modules on the switch, the test is disabled, or the switch has been rebooted within the past hour. At least one hour must pass after a switch reboot before the PRAM Consistency test can return results.

5. Choose the Refresh button to display updated results for the consistency results.

6. When you are done running the test, choose Cancel.

The PRAM Consistency Test dialog box closes.



Monitoring Switch ReliabilityPRAM Consistency

Event Log Messages for the PRAM Consistency Feature

Messages are reported to the Event Log for the PRAM Consistency feature when the following events occur:

• The PRAM consistency check is successful in that all active and standby configuration file cyclic redundancy check (CRC) values match for a card. A single-line summary displays in the Event Log in this instance.

• The PRAM consistency check finds differences. A single-line summary displays in the Event Log for each PRAM file that does not match its redundant version.

• The status of the feature is changed (enabled/disabled and vice versa).

• A start message is sent.

• A process cannot run because of a transient problem on the switch (e.g., there are no redundant modules configured).

• Config files are inconsistent.

• A test is successful.

Table 17-4 lists some of the Event Log messages that display for the PRAM Consistency feature when you run the show evlog console command. These messages appear in the Message column of the Event Log output.

Table 17-4. PRAM Consistency Event Log Messages

Event Event Log Message

PRAM consistent between active and standby SP/NP modules

PRAM consistency check: Config files for cards X, X, ... match on the active and the standby CPs.

Inconsistent PRAM between active and standby SP/NP modules

PRAM consistency check error: file CONFIG.XX on the active and the standby CP does not match.

Consistency check aborts PRAM consistency check aborts: [the reason string]

PRAM consistency check enabled PRAM consistency check routine is enabled.

PRAM consistency check disabled PRAM consistency check routine is disabled.


PRAM Consistency


PRAM Consistency Test Console Commands

Use the following console commands to manage the PRAM Consistency test feature. For more information about these console commands, see the Console Command User’s Reference for CBX 3500, CBX 500, GX 550, and B-STDX 9000.

Note – When using console commands to enable/disable the PRAM Consistency test, always run the show cfgfile_compare command to verify that your changes have taken affect.

Table 17-5. PRAM Consistency Console Commands


execute cfgfile_compare Runs the PRAM consistency feature which verifies whether there are any differences in the PRAM data configuration files between the active and standby SP/NP modules.

This command will always cause the PRAM consistency check to run, even if the feature has been disabled.

set cfgfile_compare Either enables the PRAM Consistency feature to run periodically or disables this feature. When you enable this feature, a variable is set in the Node Table that determines when it is safe to run this test.

If you do not select either of the arguments for this command (on/off), the PRAM Consistency feature is automatically enabled.

set cfgfile_compare verbose Allows verbose (debug) output to be displayed at the SP/NP diagnostics port when you run the execute cfgfile_compare command.

show cfgfile_compare Displays the following information:

• the results of the PRAM Consistency check

• whether the PRAM Consistency check is enabled or disabled

• whether additional debug data is displayed at the SP/NP diagnostics port (verbose output)



Monitoring Switch ReliabilityEnhanced Standby Hardware (ESHW) Tests

Enhanced Standby Hardware (ESHW) Tests

About the Enhanced Standby Hardware Test

The Enhanced Standby Hardware (ESHW) test feature consists of two diagnostic tests: one test between the standby SP/NP modules and the IOM/BIO modules on a particular switch and a second test on the GX 550 switch for the standby Switch Fabric (SF) module. The purpose of these tests is to check whether the standby SP/NP module can communicate with IOM/BIO modules, and whether standby SF modules are working properly.

Having standby modules that work properly helps ensure that the standby module can take over for the active module in case a module switchover is necessary.

The ESHW test supports:

• the monitoring of IOM/BIO and redundant SF modules by diagnostics and redundant manager in the SP/NP modules.

• event reporting for the IOM/BIO modules that do not respond when polled by the standby SP/NP.

• alarm reporting based on traps for non-responding standby switch fabric (SF) modules (GX 550 only).

The two tests that make up this feature are described in the following sections:

• “Running the Enhanced Standby Hardware Test for SP/NP and IOM/BIO Modules” on page 17-19

• “Running the Enhanced Standby Hardware Test for SF Modules (GX 550)” on page 17-20

Note – To use the ESHW test for SF modules, redundant SF modules and one or two NP2 modules must be installed in the GX 550 switch.




Running the Enhanced Standby Hardware Test for SP/NP andIOM/BIO Modules

To set the ESHW test for SP/NP and IOM/BIO modules on either a CBX 500/3500 or a GX 550 switch:




2. Choose Standby CP-IO Test, and then choose OK.

The Reliability Features: Standby CPIO dialog box appears (Figure 17-6).

Figure 17-6. Reliability Features: Standby CPIO Dialog Box

3. Check the Set Standby CP-IO Execution Status field’s check boxes for each slot on which you want to enable the CP-IO test.

4. Choose OK to begin the test for the integrity of the path between the SP or NP and the slots selected in the Set Standby CP-IO Execution Status field’s check boxes.

5. View the test results in the Standby CP-IO Communications Status field. The communication status may be one of the following:

• Good — The integrity of the data path between the standby SP/NP and the IOM/BIO modules is good.

• Bad — The data path between the standby SP/NP and the IOM/BIO modules is down or bad.




• Indeterminate — The ESHW test did not run or the integrity of the data path between the standby SP/NP and the IOM/BIO modules is unknown.

6. Choose Refresh to display updated information.


The Reliability Features: Standby CPIO dialog box closes.

Running the Enhanced Standby Hardware Test for SF Modules (GX 550)

To set the ESHW test for redundant SF modules on the GX 550 switch:




2. Choose Standby SF Test, and choose OK.

The Reliability Features: Standby dialog box appears (Figure 17-8).

Note – To use the ESHW test for SF modules, redundant SF modules and two NP2 modules must be installed in the GX 550 switch.

The ESHW test for redundant switch fabric (SF) modules only supports Explorer-based SFs (part numbers 810-30163-03 or greater). The ESHW test does not support Sputnik-based SFs (part numbers less than 810-30163-03).




Figure 17-8. Reliability Features: Standby SF Dialog Box

3. Select the Standby SF <-> NP Active check boxes for the NPs you want to test.

4. Choose OK to begin the test of the communication status between the standby SF and the NP(s).

5. View the test results in the Standby SF-NP Communications Status: Standby SF-NP1 and Standby SF-NP2 fields. The communication status may be one of the following:

• Good — The integrity of the data path between the standby SF and the NP module is good.

• Bad — The data path between the standby SF and the NP module is down or bad.

• Indeterminate —The test did not run or the integrity of the data path between the standby SF and the NP module is unknown.

6. Choose Refresh to display updated information.


The Reliability Features: Standby SF dialog box closes.

Enhanced Standby Hardware Test Console Commands

Use the following console commands to configure the ESHW test feature. For more information on these commands, see the Console Command User’s Reference for CBX 3500, CBX 500, GX 550, and B-STDX 9000.




Table 17-6. ESHW Test Console Commands


set sby_cpio_tst all Use this command to enable or disable the ESHW test between the standby SP/NP and the IOM/BIO modules for all slots on the switch.

set sby_cpio_tst Use this command to enable or disable the ESHW test between the standby SP/NP and the IOM/BIO modules selected slots on the switch.

show sby_cpio_rpt all Displays the following information for all slots on the switch:

• whether the ESHW test between the standby SP/NP and the IOM/BIO modules is enabled.

• the present communication status between the standby SP/NP and the IOM/BIO modules.

show sby_cpio_rpt Displays the following information for selected slots on the switch:

• whether the ESHW test between the standby SP/NP and the IOM/BIO modules is enabled.

• the present communication status between the standby SP/NP and the IOM/BIO modules.

set sby_sf_tst Use this command to enable or disable the ESHW test for the standby SF module on a GX 550 switch.

show sby_sf_rpt Displays the following information for SF modules on a GX 550 switch:

• whether the ESHW test for SF modules is enabled.

• the present communication status between the standby SF module and NP2 module(s).



18

Monitoring MIB Values

This chapter introduces the Lucent Management Information Base (MIB) and describes how to use the Navis EMS-CBGX MIB browser to navigate through the Lucent MIB.

MIB Overview

The MIB is a collection of objects that represent network devices and their internal components. Common MIB objects include:

• Counters of packets sent

• Connections used

• Connections attempted

The Lucent MIB uses the SNMP Structure of Management Information (SMI) rules to define the MIB structure.

SNMP Structure of Management Information

The following rules specify the structure of each object in the MIB:

• Object Type — Specifies the type of MIB object.

• Syntax — Identifies the data type for the object as integer, string, counter, IP address, or pointer.

• Access — Specifies the access to the object as read-only, read-write, or non-accessible.

• Status — Uses one of the following types to specify the currency of the object:

– Mandatory – The object is required to configure a switch.

– Current – The object is not required for configuration.

– Obsolete – The object is no longer part of the MIB.

• Description — A text definition that further describes the object.



Monitoring MIB ValuesMIB Overview

• Index — Lists an index value that provides instructions for identifying object instances. For example, an index value of

::={lportEntry 68}

indicates the 68th instance of lportEntry.

MIB Information Example

The following example illustrates the MIB object for the source logical address of a circuit:

cktSrcLaddr OBJECT-TYPESYNTAX INTEGERACCESS read-writeSTATUS mandatoryDESCRIPTION

“The source logical address of the circuit.”

:: = { cktEntry 82 }

MIB Structure

The MIB structure has a tree hierarchy. This hierarchy starts at the root of the tree (which is unnamed) and splits into the following three main branches:

• ccitt(0) — Administered by the International Telecommunication Union (ITU) (formerly known as the International Telegraph and Telephone Consultative Committee).

• iso (1) — Administered by the International Organization for Standards (ISO) and the International Electrotechnical Committee (IEC).

• joint-iso-ccitt(2) — Jointly administered by ISO/IEC and ITU.

Object Identifier

Each branch of the MIB is identified by a short text string (for example, iso) and a non-negative integer (for example, 1). The integer is used as part of an object identifier for each object in the MIB.

The object identifier (OID) provides a way to identify a specific object within a MIB. It contains a sequence of non-negative integers that denote a path from the root of the path to the object. The string of integers is separated by periods.

For example, the following string specifies the path to the Lucent MIB:

Note – Each administrator of a branch is free to assign further subordinate branches (nodes).

Beta Draft ConfidentialMonitoring MIB Values

MIB Overview


iso(1).org(3).dod(6).internet(1).private(4).enterprises(1).cascade(277)

The OID for each branch of this path is indicated in parentheses. The following string specifies the OID for the path to the Lucent MIB.

1.3.6.1.4.1.277

The OID string for each variable is shown in brackets ({ }) as shown in the following example:

: : = { cktEntry 82 }

In this example, the OID string for the circuit is specified in the brackets as 82.




Lucent MIB

The Lucent MIB is identified by the group name cascade. Cascade (which has an object ID of 277) has the following groups:

Table 18-1. Lucent MIB

Group Object ID

cascade_OV_v1traps_ 0

cascfr 1

cascsmds 2

namdbinding 3

isdnaddr 4

cascsvc 5

software 6

mpt 7

protconnect 8

provserver 9

cascview 10

casccnm 11

cascdvc 14

cascadepm 15

cascatm 16

acctserver 17

cascsna 18

ipswitch 19

cascfltsrv 20

Beta Draft ConfidentialMonitoring MIB Values

MIB Overview


Figure 18-1 illustrates the SNMP MIB tree hierarchy, which shows the branches through the hierarchy that you use to access the Lucent MIB.

Figure 18-1. SNMP MIB Tree Hierarchy

iso

standard reg. authority member body organization

dod

internet

directory mgmt experimental private security snmp

enterprises

hp cascade atmforum




cascfr Group

The cascfr group contains groups that are common to all protocols (including Frame Relay, SMDS, ATM, and ISDN). The cascfr group contains the following groups:

Table 18-2. cascfr Group

Group Description

cascfr_OV_v1traps_ Lucent traps.

net Variables that are relevant to a Lucent network.

ase The OSPF Autonomous System External device and host table for NMS paths.

node Variables that configure a switch.

card Variables that configure an intelligent card.

pport Variables that configure a physical port.

lport Variables that configure a logical port.

ckt (Frame Relay only) Variables that configure permanent virtual circuits (PVCs) on a port.

cascds1 Variables that specify DS1 channel information.

chan Additional variables that relate to channel information.

fracct Variables that relate to Frame Relay accounting.

Beta Draft ConfidentialMonitoring MIB ValuesUsing the MIB Browser


Using the MIB Browser

This section includes the following:

• “Displaying All Instances and Values of a MIB Object (Walk)” on page 18-7

• “Displaying the Value of a MIB Object Instance (Get)” on page 18-8

• “Setting the Value of a MIB Object Instance (Set)” on page 18-8

Displaying All Instances and Values of a MIB Object (Walk)

To use the MIB Browser to display all the instances and values of a MIB object that are on a switch:

1. In the switch tab (see “Displaying a Switch Tab in the Navigation Panel” on page 2-6), right-click on the switch and select MIB Browser from the popup menu.

The MIB Browser window appears (Figure 18-2).

Figure 18-2. MIB Browser Window

2. In the MIB Tree, expand the nodes as needed and select the MIB object.

3. Ensure that the Read Community field value is valid.

4. Choose the Walk button.

All the instances on this switch of the selected MIB object are displayed in the SNMP Response field. The values of the instances are also displayed.

5. When you are done using the MIB Browser, choose Close.

The MIB Browser window closes.



Monitoring MIB ValuesUsing the MIB Browser

Displaying the Value of a MIB Object Instance (Get)

To use the MIB Browser to display the value of a particular object on a switch:

1. In the switch tab (see “Displaying a Switch Tab in the Navigation Panel” on page 2-6), right-click on the switch and select MIB Browser from the popup menu.

The MIB Browser window appears (Figure 18-2).

2. In the Object ID field, enter the complete MIB object instance ID, including the index value. (See “Displaying All Instances and Values of a MIB Object (Walk)” on page 18-7 if you need to find the MIB object instance ID.)

3. Ensure that the Read Community field value is valid.

4. Choose the Get button.

The MIB object instance and its value are displayed in the SNMP Response field.



Setting the Value of a MIB Object Instance (Set)

To use the MIB Browser to set the value of a particular object on a switch:

1. Right-click on the switch instance node, and select MIB Browser from the popup menu.

The MIB Browser dialog box appears (Figure 18-2).

2. In the Set Value field, enter the value you want to give the MIB object instance. You can see a description of allowable values in the lower-left portion of the MIB Browser dialog box by selecting the MIB object in the MIB tree.

3. In the Object ID field, enter the complete MIB object instance ID, including the index value. (See “Displaying All Instances and Values of a MIB Object (Walk)” on page 18-7 if you need to find the MIB object instance ID.)

4. Ensure that the Write Community field value is valid.

5. Choose the Set button.

The results of the Set operation are displayed in the SNMP Response field.



Switch Diagnostics User’s Guide for CBX 3500, CBX 500, GX 550, and B-STDX 9000 A-1


A

Trap Alarm Condition Messages

This appendix describes, in alphabetical order, each of the trap alarm condition messages that the system reports in the Events Browser. Some events are informational, while others indicate a problem or potential problem within the network configuration.

The list indicates each trap alarm condition message along with a description of the trap and, where possible, a resolution for the condition. Italicized words indicate variable values. For example, switch name specifies the name of the switch.

• A card type card has been inserted at switch name, Slot slot number

An input/output module (IOM) has been installed in the specified slot.

• A card type card has been removed from switch name, Slot slot number

An IOM has been removed from the specified slot.

• A Frame Relay usage record could not be created for Switch switch name Number of records usage records could not be created during day

A Frame Relay usage record could not be created.

• A mismatched card has been detected at switch name, Slot slot number (actual: card type, config: port type)

The IOM installed in the slot does not match the NMS configuration for this slot. Use the switch console command “show system” to verify what is actually installed in the switch slot.

• A usage record could not be created for billing service type

A Usage Data counter record could not be created for the specified node billing service type.

• A usage record could not be created for service billing service type

Note – For any message not in the list below, contact Lucent TAC at: http://www.lucent.com/support.


A-210/7/05 Switch Diagnostics User’s Guide for CBX 3500, CBX 500, GX 550, and B-STDX 9000


The system could not create a usage data record because the Aggregated Usage Data store was at full capacity. This trap does not occur when the system is in a normal state. To resolve this condition, check the Adjunct Processor (AP) to see if it is online; if it is, check to see if the AP is connected to and communicating with the switching system.

• A usage record counter-value overflow condition has occurred for billing service type

A Usage Data counter value overflow condition occurred while aggregating usage data recently collected from one or more input/output processors (IOPs). An overflow condition occurs when the system attempts to update a Usage Data counter, and the update would overflow the counter. Instead of updating the record, the system closes the filled Usage Data record and opens a new one. This can only be done if there is sufficient space in the service’s aggregated usage data store.

The system generates only one of these traps for each collection period. For example, if your collection period is set to 30 seconds, and there are more than one Usage Record Creation Failures, only one Usage Record Overflow trap is generated. If the condition still exists when the next Collection Period starts, another Usage Record Overflow trap is generated at that time.

To resolve this condition, check the AP to see if it is on-line; if it is, check to see if the AP is connected to and communicating with the switching system.

• A Warm Boot Upgrade in Slot slot number on Switch switch name has initiated a Cold Boot Upgrade on the standby card

A warm boot upgrade on the specified card has caused a cold boot upgrade on the associated standby card.

• Accounting Server accounting server IP address disk space for disk directory has been reduced to disk percentage used percent of capacity (Severity: disk severity)

The disk space percentage used on the specified disk no longer exceeds the threshold value. The severity level that the trap reports corresponds to the exceeded threshold level.

• Accounting Server accounting server IP address disk space for disk directory has exceeded threshold value percent of capacity (Severity: threshold severity). The disk percentage used on this file system is disk percentage used.

The disk space threshold of the specified file system has been exceeded.

AIS or RDI cell received on circuit ATM circuit name at switch switch name

This trap indicates the reception of alarm indication signal (AIS) or RDI Cells on this ATM circuit.

• An ATM usage record could not be created for Switch switch name. Number of records usage records could not be created during day.

An ATM usage record could not be created.

Beta Draft Confidential Trap Alarm Condition Messages

Switch Diagnostics User’s Guide for CBX 3500, CBX 500, GX 550, and B-STDX 9000 10/7/05A-3

• An authentication has failed on login login user due to authentication failure reason

This trap login fail reason indicates a user console authentication login failure.

• An authentication assignment on Logical port lport name has failed due to authentication fail reason

There is a user authentication failure on a specified logical port.

An external interface address conflicts with the locally configured IP Loopback address or OSPF router ID or the internal switch address on switch switch name

This trap is triggered when there is an external interface address conflicting with a locally configured IP Loopback address or OSPF router ID or internal switch address.

• An MP bundle modification on Logical port lport name has failed due to multilink protocol fail reason

There has been a failure to create a multilink PP (MP) bundle or to add a link to an MP Bundle.

• A PPP negotiation has failed on logical port lport name due to fail reason

A Point-to-Point Protocol (PPP) negotiation has failed on the specified switch and logical port due to the specified PPP negotiation failure reason.

• A PM Threshold Crossing has occurred in switch switch name at Slot slot number Port port number

A threshold crossing was detected on the specified physical port on the specified slot on the specified switch for the performance parameter identified by the PM threshold object. This may indicate a physical layer problem with the port or the transmission media carrying the signal.

• At pport pport number in Card card name, a mismatch has occurred between the optic admin type optic admin type and the operational type operational type

There is a mismatch between the optic admin type and operational type at the indicated pport.

• At pport pport number in Card card name, the optic state has transitioned to new optic state.

There is a state change in the pluggable optics.

• At Slot slot number Port port number in Switch switch name the protection line is now state

An Automatic Protection Switching (APS) event has just taken place on the specified port on the specified slot on the specified switch.

• At Slot slot number Port port number in Switch switch name attempting to receive traffic from working line




The specified working line physical port (APS related) on the specified slot on the specified switch has resumed carrying user traffic. This may be due to either an auto switch condition that has cleared or a problem detected on the protection line.

• At Slot slot number Port port number in Switch switch name a mode mismatch has been detected

A mode mismatch has been detected based on this PPort's APS configuration and the received K2 byte. This happens when one LTE is configured for 1+1 APS and the other for 1:n APS. The LTE configured for 1:n will fall back to 1+1 mode.

• At Slot slot number Port port number in Switch switch name the protection line is now in a failed state

The protection line is now in a failed state. APS switchover to protection is now inhibited. If the protection line was carrying user traffic, it is switched back to the working line.

• At Slot slot number Port port number in Switch switch name the protection line is now in an operational state

The protection line is now in an operational state. APS switchover to protection is now possible.

• At Slot slot number Port port number in Switch switch name the protection line has declared a protection byte failure

The protection line has declared a protection byte failure. This happens when a protection byte defect or inconsistent K1 byte is received and the condition persists for 2.5 seconds. APS switchover to protection is inhibited. If the protection line was carrying user traffic, it is switched back to the working line.

• At Slot slot number Port port number in Switch switch name a far end protection line failure has been declared

A far end protection line failure has been declared. This happens when the received K1 byte indicates SF on the protection line and the condition persists for 2.5 seconds.

• At Slot slot number Port port number in Switch switch name the far end protection line failure has cleared

The far-end protection line failure has cleared. This happens after 10 seconds without an indication of SF on the protection line in the received K1 byte.

• At Slot slot number Port port number in Switch switch name a channel mismatch has been detected

A channel mismatch has been detected. When the pportAPSconfigStatus is indicated as invalid, the user should check pportAPSadminDir, pportAPSlineType, pportAPSrevertiveMode, and pportAPSwtrPeriod for a mismatched configuration between the two physical ports.

• At Slot slot number Port port number in Switch switch name the APS configuration status has changed to new status, the paired-with APS pport at Slot slot number Port port number



The APS configuration status has changed. When the pportAPSconfigStatus is indicated as invalid, the user should check pportAPSadminDir, pportAPSlineType, pportAPSrevertiveMode, and pportAPSwtrPeriod for a mismatched configuration between the two physical ports.

• At Slot slot number Port port number in Switch switch name a direction mode mismatch has been detected

A direction mode mismatch has been detected on the indicated pport (the indicated PPort is an APS protection line PPort). This happens when one LTE is configured for Unidirectional and the other for Bidirectional mode.

• ATM Accounting Server ATM accounting server address has had a switchover

An ATM Accounting Server switchover has occurred. Either an ATM Accounting Server or a Frame Accounting Server is not configured.

• At switch switch an external interface address conflicting with locally configured IP Loopback address or OSPF router ID or the internal switch address.

An external interface address conflicts with a locally configured IP loopback address or the OSPF router ID or the internal switch address.

• Billing communications failure to adjunct processor adjunct processor address

The switch to the specified adjunct processor address has failed. For this reason, the system could not complete a Usage Data file transfer. As with the Usage Record Overflow trap, the generation rate of this message is controlled so that only one of these traps is generated for each collection period.

To resolve this condition, check the Adjunct Processor (AP) to determine whether it is online; if it is, determine whether the AP is connected to and communicating with the switching system.

• Billing has been (enabled/disabled) for service billing service type

The billing system state was enabled or disabled at the specified billing service type. The billing system state is changed when a switch boots (billing becomes enabled), or when the state is changed manually via Navis EMS-CBGX.

• Billing has been billing service type for service (enabled/disabled) on Lport port name

The billing system state was enabled or disabled at the specified billing service type and logical port name. The billing system state is changed on a logical port when a switch boots (billing becomes enabled), or when the state is changed manually via Navis EMS-CBGX.

• Billing Sys Mgr on Active CP+ failed to recover the contents of the use data store on boot for switch switch name and for service node billing service type

This is a warning that the billing system manager on the active CP+ failed to recover the contents during system boot-up.




• Billing Sys Mgr on the Active CP+ discarded the data recovered on boot because they are too old for switch switch name and for service node billing service type

The billing system manager on the active CP+ discarded the usage data recovered during system boot-up because the data was outdated. Currently, any recovered data that is older than 30 days is discarded.

• Billing usage data store on the redundant CP+ has failed for switch switch name and for service node billing service type

This is a warning that the billing system manager on the active CP+ failed to write the contents of the usage data store on the redundant CP+.

Both timing references have been lost

This trap indicates that both timing references have been lost.

• Number BTUs discarded per minute on Slot slot number due to invalid VCID exceeded the threshold

The BTUs discarded per minute on this card due to an invalid VCID exceeding the threshold.

• Number BTUs discarded per minute on Slot slot number due to lost BTUs exceeded the threshold

The Frames discarded per minute on this card due to lost BTUs exceeding the threshold.

• Number BTUs discarded per minute on Slot slot number due to bus error exceeded the threshold

The BTUs discarded per minute on this card due to bus errors exceeding the threshold.

• Number BTUs discarded per minute on Slot slot number due to no resources exceeded the threshold

The BTUs discarded per minute on this card due to no resources exceeded the threshold.

Bulk copy of records into the database has failed.

The bulk copy of records into the database by the Statistics Server has failed.

• cardDSUType0 image download failed on FPGA0 for Card Slot ID slot number

The specified image download failed on FPGA0 for the specified card slot. Card type may be one of the following: Larscom (1), Verilink (2), QuickEagle + Kentrox (3), Kentrox + QuickEagle (4).

• cardDSUType1 image download failed on FPGA1 for Card Slot ID slot number



The specified image download failed on FPGA1 for the specified card slot. Card type may be one of the following: Larscom (1), Verilink (2), QuickEagle + Kentrox (3), Kentrox + QuickEagle (4).

• CBR Lport lport name at switch switch name error states: starvation condition, receive overflow condition, loss of cell sequence, loss of structure pointer

This trap indicates the error state of the CBR logical port. Error states are as follows:

– Starvation Condition — ok (1), error (2)

– Receive Overflow Condition — ok (1), error (2)

– Loss of Cell Sequence — ok (1), error (2)

– Loss of Structure Pointer — ok (1), error (2)

• CBR pport switch name.slot number.port number runs clock mode clock mode

The CBR physical port switched its clock mode. Possible clock modes are as follows:

– 1 — Synchronous

– 2 — SRTS

– 3 — ACM

• Channel channel number at pport slot number.pport number in Switch switch name issues Threshold Crossing Alert on PM TCA ID




A threshold crossing problem was detected on the specified channel and the event identified by the PM TCA ID was issued. Each PM TCA ID is described in Table 1-1.

Note – Some of the threshold parameters listed in Table 1-1 are subject to inhibiting, so they are not accumulated during periods of unavailability, during SESs, or during seconds containing defects on the monitored entity. Inhibiting on a given monitored entity (such as a DS1 path) is not explicitly affected by conditions on any other monitored entity (such as a DS1 line). The inhibiting rules are:

• UAS, FC, PSC, and PSD parameter counts are not inhibited.

• All other performance parameter counts are inhibited during UAS, whenever the UAS parameter is implemented. Inhibiting is retroactive to the onset of unavailable time, and ends retroactively to the end of unavailable time.

• The CV and BBE parameter counts are inhibited during SESs, whenever the SES parameter is implemented.

• When an optional SES parameter is not implemented, the CV and BBE parameter counts are inhibited during seconds containing one or more of the defects that are included in the SES definition at that layer.

For entities without a defined UAS parameter, there is no inhibiting of performance parameter counts except for the CV and BBE parameters, as described in the preceding paragraphs.

Table 1-1. PM TCA IDs and Corresponding Thresholds

ID Type Threshold Description

1 15-minute CV-L (Code violations-line) – a count of both BPVs (bipolar variations) and EXZs (excessive zeros) occurring over the accumulation period. An EXZ increases the CV-L by 1, regardless of the length of the zero string (however, some existing equipment may count only BPVs).

For a B8ZS-coded signal, BPVs that are part of the zero substitution code, as defined by ANSI T1.102, are excluded from the count.

CV- L is subject to inhibiting. See note above table.

2 15-minute ES-L (Errored seconds-line) – a count of 1-second intervals with BPVs, EXZs, or LOS (loss of signal) defects. For a B8ZS-coded signal, BPVs that are part of the zero-substitution code, as defined in ANSI T1.102, are excluded.



3 15-minute SES-L (Severely errored seconds-line) – a count of 1-second intervals with 1544 or more of combined BPVs and EXZs, or any LOS defects. For a B8ZS-coded signal, BPVs that are part of the zero-substitution code, as defined in ANSI T1.102, are excluded.

4 15-minute UAS-L (Unavailable seconds) – a count of 1-second intervals for which the SONET line is unavailable (at the onset of 10 contiguous SES-Ls, which are included in the unavailable time).

The SONET line becomes available again at the onset of 10 contiguous seconds with no SES-Ls, which are excluded from unavailable time.

UAS- L is subject to inhibiting. See note above table.

5 15-minute CV-P (Code violations) – a count of frame synchronization bit errors (FE) in the SF frame format, or a count of CRC-6 errors in the ESF format occurring during the accumulation period.

There is no redundancy check in the DS1 SF frame format to verify the correctness of frame payload bits, so the FE primitive is substituted as a code violation primitive.

CV-P is subject to inhibiting. See note above table.

6 15-minute ES-P (Errored seconds) – for DS1 ESF format, a count of 1-second intervals containing CRC-6 errors, CS events, SEF defects, or AIS defects.

For DS1 SF frame format, a count of 1-second intervals containing FE errors, CS events, SEF defects, and AIS defects.

ES-P is subject to inhibiting. See note above table.

7 15-minute SES-P (Severely errored seconds) – for DS1 ESF frame format, a count of 1-second intervals with 320 or more CRC-6 errors, or any SEF or AIS defects.

For DS1 SF frame format, a count of 1-second intervals with 4 (or 8, depending on the bits measured, as described in ANSI T1.231) or more FE events, or an SEF or AIS defect.

SES-P is subject to inhibiting. See note above table.

8 15-minute SAS-P (SEF/AIS seconds) – a count of 1-second intervals containing any SEF or AIS defects.

SAS-P is subject to inhibiting. See note above table.

Table 1-1. PM TCA IDs and Corresponding Thresholds (Continued)





9 15-minute CSS-P (Controlled slip seconds) – a count of 1-second intervals containing any controlled slips. This count is accurate only in the path-terminating network element of the DS1 signal where the controlled slip occurs.

Intermediate performance monitors may only estimate potential controlled slips at downstream path terminating network elements.

CSS-P is subject to inhibiting. See note above table.

10 15-minute UAS-P (Unavailable seconds) – a count of 1-second intervals for which the DS1 path is unavailable (at the onset of 10 contiguous SESs, which are included in unavailable time).

The DS1 path become available again at the onset of 10 contiguous seconds with no SESs, which are excluded from unavailable time.

UAS-P is subject to inhibiting. See note above table.

11 15-minute CV-S (Code violations) – a count of BIP-8 (bit-interleaved parity) errors detected at the section layer of the incoming signal. Section CV counters are increased for each BIP-8 error.

Each BIP-8 can detect up to 8 errors per STS-N frame, with each error increasing the CV counter. CVs for the section layer are collected using the BIP-8 in the B1 byte located in the section overhead of STS-1 number 1.

CV-S is subject to inhibiting. See note above table.

12 15-minute ES-S (Errored seconds) – a count of 1-second intervals containing EDC errors (error detection code - B1 byte), SEF defects, or LOS defects.

13 15-minute SES-S (Severely errored seconds) – a count of 1-second intervals containing x or more EDC errors (B1 byte), SEF defects, or LOS defects; x is defined in ANSI T1.231 as 52 for OC-1, 155 for OC-3, 616 for OC-12, 1220 for OC-24, 2392 for OC-48, and 8554 for OC-192.

The value of x is configurable, but only to accommodate any future standards change to the definition of SES-S.

14 15-minute ESX (Defects in errored seconds) – A count of 1-second intervals containing one or more unclassified errors.





15 one day CV-L (Code violations-line) – a count of both BPVs (bipolar variations) and EXZs (excessive zeros) occurring over the accumulation period. An EXZ increases the CV-L by 1, regardless of the length of the zero string (however, some existing equipment may count only BPVs).

For a B8ZS-coded signal, BPVs that are part of the zero substitution code, as defined by ANSI T1.102, are excluded from the count.

CV- L is subject to inhibiting. See note above table.

16 one day ES-L (Errored seconds-line) – a count of 1-second intervals with BPVs, EXZs, or LOS (loss of signal) defects. For a B8ZS-coded signal, BPVs that are part of the zero-substitution code, as defined in ANSI T1.102, are excluded.

17 one day SES-L (Severely errored seconds-line) – a count of 1-second intervals with 1544 or more of combined BPVs and EXZs, or any LOS defects. For a B8ZS-coded signal, BPVs that are part of the zero-substitution code, as defined in ANSI T1.102, are excluded.

18 one day UAS-L (Unavailable seconds) – a count of 1-second intervals for which the SONET line is unavailable (at the onset of 10 contiguous SES-Ls, which are included in the unavailable time).

The SONET line becomes available again at the onset of 10 contiguous seconds with no SES-Ls, which are excluded from unavailable time.

UAS- L is subject to inhibiting. See note above table.

19 one day CV-P (Code violations) – a count of frame synchronization bit errors (FE) in the SF frame format, or a count of CRC-6 errors in the ESF format occurring during the accumulation period.

There is no redundancy check in the DS1 SF frame format to verify the correctness of frame payload bits, so the FE primitive is substituted as a code violation primitive.

CV-P is subject to inhibiting. See note above table.

20 one day ES-P (Errored seconds) – for DS1 ESF frame format, a count of 1-second intervals containing CRC-6 errors, CS events, SEF defects, or AIS defects.

For DS1 SF frame format, a count of 1-second intervals containing FE errors, CS events, SEF defects, and AIS defects.

ES-P is subject to inhibiting. See note above table.






21 one day SES-P (Severely errored seconds) – for DS1 ESF frame format, a count of 1-second intervals with 320 or more CRC-6 errors, or any SEF or AIS defects.

For DS1 SF frame format, a count of 1-second intervals with 4 (or 8, depending on the bits measured, as described in ANSI T1.231) or more FE events, or an SEF or AIS defect.

SES-P is subject to inhibiting. See note above table.

22 one day SAS-P (SEF/AIS seconds) – a count of 1-second intervals containing any SEF or AIS defects.

SAS-P is subject to inhibiting. See note above table.

23 one day CSS-P (Controlled slip seconds) – a count of 1-second intervals containing any controlled slips. This count is accurate only in the path-terminating network element of the DS1 signal where the controlled slip occurs.

Intermediate performance monitors may only estimate potential controlled slips at downstream path terminating network elements.

CSS-P is subject to inhibiting. See note above table.

24 one day UAS-P (Unavailable seconds) – a count of 1-second intervals for which the DS1 path is unavailable (at the onset of 10 contiguous SESs, which are included in unavailable time).

The DS1 path become available again at the onset of 10 contiguous seconds with no SESs, which are excluded from unavailable time.

UAS-P is subject to inhibiting. See note above table.

25 one day CV-S (Code violations) – a count of BIP-8 (bit-interleaved parity) errors detected at the section layer of the incoming signal. Section CV counters are increased for each BIP-8 error.

Each BIP-8 can detect up to 8 errors per STS-N frame, with each error increasing the CV counter. CVs for the section layer are collected using the BIP-8 in the B1 byte located in the section overhead of STS-1 number 1.

CV-S is subject to inhibiting. See note above table.

26 one day ES-S (Errored seconds) – a count of 1-second intervals containing EDC errors (error detection code - B1 byte), SEF defects, or LOS defects.





27 one day SES-S (Severely errored seconds) – a count of 1-second intervals containing x or more EDC errors (B1 byte), SEF defects, or LOS defects; x is defined in ANSI T1.231 as 52 for OC-1, 155 for OC-3, 616 for OC-12, 1220 for OC-24, 2392 for OC-48, and 8554 for OC-192.

The value of x is configurable, but only to accommodate any future changes to the definition of SES-S.

28 one day ESX (Defects in errored seconds) – A count of 1-second intervals containing one or more unclassified errors.

29 15-minute CVCP-P (Code violations) – a count of CP-bit parity errors occurring in the accumulation period.

CVCP-P is subject to inhibiting. See note above table.

30 15-minute ESCP-P (Errored seconds) – a count of 1-second intervals containing CP-bit parity errors, SEF defects, or AIS defects; ESCP-P is defined for the C-bit parity application.

ESCP-P is subject to inhibiting. See note above table.

31 15-minute SESCP-P (Severely errored seconds) – a count of 1-second intervals containing x (by default, 45) or more CP-bit parity errors, any SEF defects, or any AIS defects; x is defined in ANSI T1.231 as 2444 for a minimum BER (bit error ratio) of 0.000075 and 45 for a minimum BER of 0.000001; defined for the C-bit parity application.

The value of x is configurable, but only to accommodate any future changes to the definition of SES.

SESCP-P is subject to inhibiting. See note above table.

32 15-minute SASCP-P (C-bit AIS seconds) – a count of 1-second intervals containing any far-end SEF/AIS defects.

33 15-minute UASCP-P (Unavailable seconds) – a count of 1-second intervals for which the DS3 path is unavailable (at the onset of 10 contiguous SESCP-Ps, which are included in unavailable time).

The DS3 path becomes available again at the onset of 10 contiguous seconds with no SESCP-Ps, which are excluded from unavailable time.

UASCP-P is subject to inhibiting. See note above table.

34 one-day CVCP-P (Code violations) – a count of CP-bit parity errors occurring in the accumulation period.

CVCP-P is subject to inhibiting. See note above table.






35 one-day ESCP-P (Errored seconds) – a count of 1-second intervals containing CP-bit parity errors, SEF defects, or AIS defects; ESCP-P is defined for the C-bit parity application.

ESCP-P is subject to inhibiting. See note above table.

36 one-day SESCP-P (Severely errored seconds) – a count of 1-second intervals containing x (by default, 45) or more CP-bit parity errors, any SEF defects, or any AIS defects; x is defined in ANSI T1.231 as 2444 for a minimum BER (bit error ratio) of 0.000075 and 45 for a minimum BER of 0.000001; defined for the C-bit parity application.


SESCP-P is subject to inhibiting. See note above table.

37 one-day SASCP-P (C-bit AIS seconds) – a count of 1-second intervals containing any far-end SEF/AIS defects.

38 one-day UASCP-P (Unavailable seconds) – a count of 1-second intervals for which the DS3 path is unavailable (at the onset of 10 contiguous SESCP-Ps, which are included in unavailable time.

The DS3 path becomes available again at the onset of 10 contiguous seconds with no SESCP-Ps, which are excluded from unavailable time.

UASCP-P is subject to inhibiting. See note above table.

39 15-minute CVCP-PFE (Code violations) – a count of occurrences when all three FEBE bits in an M-frame are not set to 1.

CVCP-PFE is subject to inhibiting. See note above table.

40 15-minute ESCP-PFE (Errored seconds) – a count of 1-second intervals when all three FEBE bits in an M-frame are not set to 1, or any far-end SEF/AIS defects.

ESCP-PFE is subject to inhibiting. See note above table.

41 15-minute SESCP-PFE (Severely errored seconds) – a count of 1-second intervals containing x (by default, 45) or more M-frames with the three FEBE bits not all set to 1, or any far-end SEF/AIS defects; x is defined in ANSI T1.231 as 2444 for a minimum BER (bit error ratio) of 0.000075 and 45 for a minimum BER of 0.000001.


SESCP-PFE is subject to inhibiting. See note above table.





42 15-minute SASCP-PFE (SEF/AIS seconds) – a count of 1-second intervals containing any far-end SEF/AIS defects.

SASCP-PFE is subject to inhibiting. See note above table.

43 15-minute UASCP-PFE (Unavailable seconds) – a count of 1-second intervals for which the DS3 path is unavailable (at the onset of 10 contiguous SESCP-PFEs, which are included from unavailable time).

The DS3 path becomes available again at the onset of 10 contiguous seconds with no SESCP-PFEs, which are excluded from unavailable time.

UASCP-PFE is subject to inhibiting. See note above table.

44 one-day CVCP-PFE (Code violations) – a count of occurrences when all three FEBE bits in an M-frame are not set to 1.

CVCP-PFE is subject to inhibiting. See note above table.

45 one-day ESCP-PFE (Errored seconds) – a count of 1-second intervals when all three FEBE bits in an M-frame are not set to 1, or any far-end SEF/AIS defects.

ESCP-PFE is subject to inhibiting. See note above table.

46 one-day SESCP-PFE (Severely errored seconds) – a count of 1-second intervals containing x (by default, 45) or more M-frames with the three FEBE bits not all set to 1, or any far-end SEF/AIS defects; x is defined in ANSI T1.231 as 2444 for a minimum BER (bit error ratio) of 0.000075 and 45 for a minimum BER of 0.000001.


SESCP-PFE is subject to inhibiting. See note above table.

47 one-day SASCP-PFE (SEF/AIS seconds) – a count of 1-second intervals containing any far-end SEF/AIS defects.

SASCP-PFE is subject to inhibiting. See note above table.

48 one-day UASCP-PFE (Unavailable seconds) – a count of 1-second intervals for which the DS3 path is unavailable (at the onset of 10 contiguous SESCP-PFEs, which are included from unavailable time).

The DS3 path becomes available again at the onset of 10 contiguous seconds with no SESCP-PFEs, which are excluded from unavailable time.

UASCP-PFE is subject to inhibiting. See note above table.






• Circuit user-to-user PVC circuit IF Index.DLCI has changed to state to state (FailReason:reason, FailNode:node ID, FailPort:port)

The user-to-user PVC state has been changed for this virtual circuit. It has either been created or invalidated, or has toggled between the active and inactive states. Reason codes and explanations for the PVC establishment failure are listed in Table 1-2.

.

• Circuit user-to-user ATM PVC circuit IF Index.VPI.VCI has changed to state to state (FailReason:reason, FailNode:node ID, FailPort:port)

The user-to-user ATM PVC state has been changed for this virtual circuit. It has either been created or invalidated, or has toggled between the active and inactive states. Reason codes and explanations for the PVC establishment failure are listed in Table 1-2.

Table 1-2. PVC Establishment Failure Reason Variables

Reason Variable Value Condition

none 1 No failures.

admindown 2 Admin status of the PVC is down.

novcbuff 3 No virtual circuit buffer.

nobw 4 No bandwidth.

noroute 5 No circuit route.

timeout 6 A timeout has occurred.

nopdubuff 7 No protocol data buffer (PDU) buffer.

nodest 8 No destination.

trkrnr 9 Trunk route not received.

trkdown 10 Trunk down.

balancereroute 11 Balance reroute.

dead 12 Circuit is dead.

defpathreroute 13 Define a new path.

nidown 14 Network interface is down; PVC is not transmitting.

otherpvcsegdown 15 Other PVC segment is down.

otherpvcsegrnr 16 Other PVC segment route not received.

usingaltpathwarning 17 Using an alternate path.



• Circuit multipoint circuit name at circuit location is state

The specified multipoint circuit state has been changed.

• Circuit point-to-multipoint ATM PVC circuit name has changed state to state (FailNode:node ID, FailPort:lport IF index)

The specified point-to-multipoint (PMP) ATM PVC state has been changed.

• Circuit user-to-user ATM PVC circuit IF index.VPI.VCI has changed state to operational state (FailReason:reason, FailNode:node ID, FailPort:port)

The user-to-user ATM PVC state has been changed for this virtual circuit, which has rerouted to a lower-cost path. The current operational state may be one of the following values: (0) invalid, (1) inactive, (2) active. FailReason is the reason for the PVC establishment failure preferred path reroute.

• Circuit user-to-user Frame PVC circuit IF Index.DLCI has changed state to operational state (FailReason:reason, FailNode:node ID, FailPort:port)

The user-to-user Frame PVC state has been changed for this virtual circuit, which has rerouted to a lower-cost path. The current operational state may be one of the following values: (0) invalid, (1) inactive, (2) active. FailReason is the reason for the PVC establishment failure preferred path reroute.

• Circuit circuit name redirect PVC has been switched over

This indicates the last action that the node took to switch the called endpoint from primary to secondary or secondary to primary in this redirect PVC. Possible reasons for switchover may be:

– gopri-manual - manual switchover to primary as a result of cktRedirSwitchoverReq

– gosen-manual - manual switchover to secondary as a result of cktRedirSwitchoverReq

– gopri-ondemand - switchover to primary triggered by a DTE Status change in revertive mode

– gosec-ondemand - switchover to secondary triggered by a DTE Status change in non-revertive mode or revertive mode

• Circuit circuit name at switch switch name is state with fail reason (FailNode:node ID, FailPort:lport IF index)

The specified point-to-point ATM PVC or Frame Relay PVC on the specified switch has changed state. The possible states for the circuit include active (0), inactive (1), and invalid (2). When the circuit is inactive, an explanation is provided in the fail reason portion of the message. The node where the failure occurred is also indicated (the last 2 octets of the internal node ID is provided) along with the interface (IF) index of the logical port where the failure occurred. Use the Show All Logical Ports dialog box to determine the mapping between logical port names and IF indexes.

Possible fail reason variables are described in Table 1-3.




Table 1-3. PVC Fail Reason Variable Values


none 0 No failures.

admindown 1 Admin status of the PVC is down.

novcbuff 2 No virtual circuit buffer.

nobw 3 No bandwidth.

noroute 4 No circuit route.

timeout 5 A timeout has occurred.

nopdubuff 6 No PDU buffer.

nodest 7 No destination.

trkrnr 8 Trunk route not received.

trkdown 9 Trunk down.

balancereroute 10 Balance reroute.

dead 11 Circuit is dead.

defpathreroute 12 Define a new path.

nidown 13 Network interface is down; PVC is not transmitting.

otherpvcsegdown 14 Other PVC segment is down.

otherpvcsegrnr 15 Other PVC segment route not received.

usingaltpathwarning 16 Using an alternate path.

iopdown 17 An IOP used by the circuit is down.

numsgbuffer 18 The PVC manager has no user message buffer for the PDU.

noport 19 No logical port is configured for use by the PVC.

misconfig 20 Configuration error.

svcsetupfail 21 Soft PVC setup failed.

srcbackedup 22 Source is in a backup condition.

srcunknown 23 Source is unknown.

dstunknown 24 Destination is unknown.



• Circuit name at switch name has been rerouted

An ATM or Frame Relay PVC has been rerouted.

• Circuit circuit name at switch switch name is setup or cleared: calling number: calling party number, called number: called number

This trap is generated by the ingress switch whenever an SVC is setup or cleared. The value of cktStatus indicates whether the circuit is initiating a setup or a clear.

• Circuits on interfaces go switch name, string

bkpdlcicollision 25 DLCI collision occurred during backup.

oldrevinpath 26 A switch that is running an incompatible version of software is in the circuit path.

smdsmgmttrunk 27 The PVC attempted to traverse an SMDS management trunk.

nevercalled 28 The PVC endpoint was never called.

bothendptbackup 29 Both endpoints are backups.

pvcroutemgmttrunk 30 The PVC attempted to traverse a management trunk.

nomultipointparent 31 No multipoint circuit parent was found.

pvcroutefail 32 PVC route failed because it changed during setup.

novpivci 33 No VPI/VCI is available.

svcuserclear 34 User cleared the SVC. This error appears for SPVCs only.

pathregfailed 35 Circuit path registration failed.

noatmchan 36 The ATM channel selected by the PVC cannot be allocated.

norevbw 37 No bandwidth in the reverse direction is available.

internalreset 38 The PVC reset internally.

highprivcinpath 39 High priority VCI is in the PVC’s path. The PVC is disrupted due to priority routing.

nopribw 40 No negative priority bandwidth could be allocated.

Table 1-3. PVC Fail Reason Variable Values (Continued)





Circuit interfaces (such as physical ports) on the switch go up or down. The data passed in string is 4 + n*134 bytes in length where n => 1. The first and second byte make up the interface/slot ID associated with the link that goes down or comes up. The third byte is the reason why circuits go down:

1 — A user link goes down.

2 — A trunk link goes down.

3 — An IOM goes down.

4 — A user link comes up.

The fourth byte is the count of entries in a 134-byte circuit bit map array that follows. In this array, the first two bytes represent the IOM slot associated with the circuits’ DLCIs. The next two bytes represent the physical port ID associated with the DLCIs. The third pair of bytes represent the interface ID associated with the DLCIs.

The remaining 128 bytes (1024 bits) is a bit map for the DLCIs associated with the interface. The left-most bit of the first byte represents DLCI 0 and the right-most bit of the 128th byte represents DLCI 1023. If a bit is set, it means that the corresponding DLCI associated with the interface is up or down.

• Clock generation unit switch name.pport slot number.pport number synchronized on clock source clock source ID

The clock generation unit synchronized to a reference clock is specified by clock source ID.

• Clock generation unit switch name.pport slot number.pport number is in holdover mode

The clock generation unit switched to holdover mode.

• Comm Layer Failure

There is a CRITICAL FAILURE associated with problematic code on a particular object. Any operations or requests on that object will not be serviced. For this and any other CRITICAL FAILURE message, contact Lucent TAC at: http://www.lucent.com/support.

• CUG: Configuration error for prefix name on switch name

There is a run-time configuration error on the number of closed user groups (CUGs) allowed per address.

• CUG: Configuration error for address name on switch name

There is a run-time configuration error on the number of CUGs allowed per address.

• CUG: Configuration error for node prefix name on switch name

There is a run-time configuration error on the number of CUGs allowed per node prefix.

• DC 48V power supply input bus A at switch switch name is status of input bus



The DC 48V power supply input bus A has changed state (toggled between Up and Down states). Status of input bus can be one of the following values:1 (Up) or 2 (Down).

• DC 48V power supply input bus B at switch switch name is status of input bus

The DC 48V power supply input bus B has changed state (toggled between Up and Down states). Status of input bus can be one of the following values:1 (Up) or 2 (Down).

• Disk Space Threshold for the archival filesystem has been exceeded

The disk space threshold for the Statistics Server’s archival file system has been exceeded.

• DS0 channel on pport slot number.port number to DS0 far end loopback has been disabled

The DS0 requested to be set into far-end loopback has been disabled.

• DS0 Near End loopback on Lport Lport number at switch switch name is status

Notification of activating and deactivating a DS0 Near End loopback on a port.

• DS1 and Channel channel ID pport pport number, Slot slot number, Switch switch name has changed alarm state to alarm state

The circuit emulation port has detected a status change in cell loss status in upstream (towards the line) direction. The cell loss status may be one of the following values: No cell loss in the last integration period (1), cell loss occurred in the last integration period (2).

• DS1 at channel number, port number, slot number, switch name has changed loopback state to state

The current loopback state of the DS1 has changed. The loopback state can change to one of the following:

– ds1ClearLoop (1)

– ds1PayloadLoop (2)

– ds1LineLoop (3)

– ds1DiagLoop (4)

• DS1 at Channel chan ID, pport pport number, Slot slot number, Switch switch name has changed alarm state to alarm state

The alarm state of the DS1 has changed. The alarm state value can be any of the following values: none (0), red-alarm (1), yellow-alarm (2), blue-alarm (4), carrier-loss (8), looped-back (16).

• DXI heartbeat poll exceeds threshold

A non-Ack count for SMDS Data Exchange Interface (DXI) heartbeat poll exceeds the specified threshold. The non-Ack count value is reset every 15 minutes.




• Error message error has been detected on Switch switch name Slot slot number

A task running on the standby card has generated a diagnostic error message.

• Establish the backup trunk associated lport lport name on switch switch name

An attempt to establish the backup trunk associated with the specified logical port is being made.

• External power supply at switch switch name is state

The external power supply on the specified switch has toggled between Up and Down states. Possible states include: Up (1), Down (2), and Power Supply is Not Present (4).

• Fail to backup trunk with lport lport name on switch switch name due to lport backup fail reason

The primary trunk associated with the indicated logical port has not been backed up or the backup trunk associated with the indicated logical port has not been restored. The reason for the failure is either buTrkNotDef (primary trunk has not been backed up) or buTrkNotEstab (backup trunk has not been restored). The numerical values for these fail reasons are: buTrkNotDef (1) and buTrkNotEstab (2).

• Failed to receive one or more usage data files from the switch

The Statistics Server has failed to receive one or more usage data files from the switch.

• Fan number at switch name is state

The specified fan in the specified switch has changed state to either Up, Down, or Marginal.

• Fault server process failed or restarted. (Fault Server status=status, Fault Server Severity=severity, Fault Server Process=process)

Notification from the Fault Server when one of its processes fails or restarts.

• FCP on IOM slot ID has stopped responding

A flow control processor (FCP) daughter card in the specified IOM has stopped responding.

• For IMA Group IMA Group the alarm condition has changed to new condition (Reason: reason)

The IMA group alarm condition as been changed.

• For IMA Group IMA Group day thresholds have been crossed to value

The IMA group day threshold have been crossed.

• For IMA Link IMA Link the alarm condition has changed to new condition (Reason: reason)

The IMA link alarm condition as been changed.



• For IMA Link IMA link day thresholds have been crossed to value

The IMA link day threshold have been crossed.

• Frame Relay Accounting Server Frame Relay accounting server address has had a switchover

A Frame Relay Accounting Server switchover has occurred.

• Frame Relay SVC SourceIFIndex.SourceDLCI is setup or cleared: calling party number is number, called party number is number

This trap is generated by the ingress switch when the specified frame relay SVC is setup or cleared.

• Frame Relay SVC fails due to fail reason: calling party number is number, called party number is number

This trap is generated by the ingress switch when the Frame Relay Setup fails. Possible fail reason values are described in Table 1-4.

Table 1-4. Frame Relay SVC Fail Reason Variable Values

Alarm Type Value Description

unalloc-nmb 1 Unallocated number.

no-route-transnet 2 No route transnet assigned.

no-route-dest 3 No route destination assigned.

vcc-unacceptable-30 10 An unacceptable VCC was specified.

normal-call-clr-31 16 Normal Call clearing. Requested by user.

user-busy 17 Call user was busy.

no-user-response 18 No response from call user.

call-reject 21 Call was rejected by user.

nmb-changed 22 Calling number no longer assigned.

all-reject-clir 23 Caller rejected due to missing calling party information.

dest-out-of-order 27 Destination address out of order.

invalid-nmb-format 28 The number format was invalid.

response-state-enq 30 Response to Status Enquiry.

normal-unspecified 31 Normal unspecified event; reported when no other cause in normal class applies.

req-vcc-unavailable 35 The requested VCC was unavailable.

vc-fail-31 36 VPI/VCI assignment failure.




rate-unavil-31 37 User cell rate unavailable.

network-out-of-order 38 The network is out of order.

temp-fail 41 Temporary failure.

access-info-discarded 43 Access information discarded.

no-vcc-available 45 No VCC was available for the call.

resources-unavailable 47 No resources are available.

qos-unavailable 49 The QoS requested is unavailable.

rate-unavailable-30 51 The rate requested is unavailable.

b-cap-not-authorized 57 Bearer capability not authorized.

b-cap-unavailable 58 Bearer capability not available.

service-unavailable 63 Service or option unavailable; reported when no other services apply.

b-cap-not-implemented 65 Bearer capability not implemented.

combination-unsupported 73 Unsupported combination of parameters.

aal-parms-unsupp-31 78 UNI 3.1 AAL parameters cannot be supported.

invalid-call-reference 81 Invalid call reference.

no-channel 82 Identified channel does not exist.

dest-incompatible 88 Destination address is incompatible.

inavild-endpoint-ref 89 The endpoint reference is invalid.

invalid-transit-net 91 Invalid transit network selection.

too-many-add-pty-req 92 Too many add party requests.

aal-parms-unsupp-30 93 UNI 3.0 AAL parameters cannot be supported.

info-element-missing 96 Mandatory information element is missing.

msg-type-not-imp 97 Message type not implemented or non-existent.

info-element-not-imp 99 Information element not implemented/non-existent.

invalid-info-element 100 Invalid information element contents.

Table 1-4. Frame Relay SVC Fail Reason Variable Values (Continued)




• Hello Mismatch has occurred for Node ID node ID on PNNI Link

A Hello mismatch has occurred on a PNNI link. PNNI link line color on the network map will change to signify that the link is down (red).

• Holdover mode has changed to mode

The holdover mode has changed state.

• IMA Alarm Type has been cleared/declared on IMA group IMA group on Switch switch name

The IMA Group alarm type condition has been changed. Table 1-5 shows the following possible values for this alarm type condition.

message-not-compatible 101 Message type not compatible with call state.

timer-recovery 102 Recovery on time expiry.

invalid-message-len 104 Incorrect message length.

protocol-error 111 An unspecified protocol error has occured.

optional-element-error 127 Optional information element content error.

Table 1-5. IMA Alarm Type Conditions

Alarm Type Condition

(1) imaAlarmLinkLif Transmit misconnect due to loss of IMA frame

(2) imaAlarmLinkLods Transmit link out of delay synchronization

(3) imaAlarmLinkRfi IMA Alarm remote failure indication

(4) imaAlarmLinkTxMisConnect Transmit misconnect on IMA Alarm Link

(5) imaAlarmLinkRxMisConnect Receive misconnect on IMA Alarm Link

(6) imaAlarmLinkTxFault Transmit link fault on IMA Alarm Link

(7) imaAlarmLinkRxFault Receive link fault on IMA Alarm Link

(8) imaAlarmLinkTxUnusableFe Far End Transmit Unusable on IMA Alarm Link

(9) imaAlarmLinkRxUnusableFe Far End Receive Unusable on IMA Alarm Link

(10) imaAlarmGroupStartupFe Far End Startup on IMA Alarm Group

(11) imaAlarmGroupCfgAbort IMA Alarm Group cofiguration aborted

Table 1-4. Frame Relay SVC Fail Reason Variable Values (Continued)





• IMA Link alarm condition has changed on IMA Link Interface IMA interface of IMA Group IMA link group ID on Switch switch name

The IMA link alarm condition has been changed on the IMA link interface.

• IOP in Slot slot number at switch switch name is down, following PVCs is also down: circuit name list

An IOP in the specified slot number is down; as a result the specified circuits are also down.

• In switch switch name an alarm is opened or closed

The fault server generates this trap when an alarm is open or closed.

• Number inbound frames per minute were discarded due to long frame error on Lport interface port name

The long frame errors per minute on this Lport exceeded the threshold.

• Number inbound frames per minute were discarded due to CRC error on Lport interface port name

The cycle redundancy check (CRC) errors per minute on this LPort exceeded the threshold.

• Number inbound frames per minute were discarded due to overrun error on Lport interface port name

The overrun errors per minute on this LPort exceeded the threshold.

• Number inbound frames per minute were discarded due to frame octet on Lport interface port name

The octet errors per minute on this LPort exceeded the threshold.

• Number inbound frames per minute were discarded due to frame abort on Lport interface port name

The abort errors per minute on this LPort exceeded the threshold.

(12) imaAlarmGroupCfgAbortFe Far End IMA Alarm Group cofiguration aborted

(13) imaAlarmGroupInsuffLinks Insufficient Links on IMA Alarm Group

(14) imaAlarmGroupInsuffLinksFe Insufficient Links on Far End IMA Alarm Group

(15) imaAlarmGroupBlockedFe Far End IMA Alarm Group is blocked

(16) imaAlarmGroupTimingSynch Timing Synchronization on IMA Alarm Group

Table 1-5. IMA Alarm Type Conditions

Alarm Type Condition



• IP MTU of Lport port name egress link on Switch switch name is less than the packet size

The IP Max Transfer Unit (MTU) of an egress link is less than the packet size during a multicast.

• License checkout failed for the Statistics Server

The License checkout failed for the Statistics Server.

• Logical port lport name has Bandwidth Allocation Protocol (BAP) or Bandwidth Allocation Control Program (BACP) call failure with status code BAP call fail stat

There is a failure on a BAP or BACP Call on the specified logical port. The BAP call fail stat variable is the BAP Call Fail Status code (Q.931 cause code).

• Lport port name at switch switch name is link protocol status

The link protocol status for the specified logical port has changed states. Possible values for the link protocol status are up (1) or down (2). The link values can be Frame Relay, LMI, DXI heartbeat poll, PPP Link Control Protocol (LCP), etc., depending on the logical port type.

• Lport port name at switch switch name non-Ack count for SMDS DXI heartbeat poll exceeds threshold

A non-Ack count for the SMDS DXI heartbeat poll exceeds the threshold. The non-Ack count is reset every 15 minutes.

• Lport port name at switch switch name SMDS discard packets exceed the threshold

The Total Discard packet count for an SMDS packet exceeds the specified threshold.

• Lport name at switch switch name has encountered packet number frame errors (exceed threshold per minute threshold)

The frame errors per minute on this logical port exceed the threshold. The packet number variable is the number of inbound packets that contained errors, which prevented them from being delivered to a higher layer protocol. When this number exceeds the specified per-minute threshold, a link error trap is sent.

• Lport name in switch name is down, following PVCs are also down: circuit name list

The specified logical port is down; as a result, the specified circuits are also down.

• Lport name in switch name is up, following PVCs are also up: circuit name list

The specified logical port is now active; as a result, the specified circuits are now active.

• Lport name in switch name has congestion rate% (exceeded threshold threshold%)




The specified logical port is congested (threshold%). The rate% variable is the value of the congestion rate when the logical port entered a severely or absolutely congested state in the last minute interval. The threshold% variable is the alert threshold for the congestion rate. A trap is sent whenever the congestion rate exceeds this threshold value. This trap is not supported for SMDS.

• Lport port name in switch switch name the number of SMDS SIP3 Dest GA Not Found violations exceeds threshold

The number of destination group address not found violations exceeds the specified SMDS PDU threshold for the logical port.

• Lport port name in switch switch name the number of SMDS SIP3 Dest GA Screen Fail violations exceeds threshold

The number of destination group address screen failures exceeds the specified SMDS PDU threshold for the logical port.

• Lport port name in switch switch name the number of SMDS SIP3 Dest IA Not Found violations exceeds threshold

The number of destination individual address not found violations exceeds the specified SMDS PDU threshold for the logical port.

• Lport port name in switch switch name the number of SMDS SIP3 Dest IA Screen Fail violations exceeds threshold

The number of destination individual address screen failure violations exceeds the specified SMDS PDU threshold number for the logical port.

• Lport port name in switch switch name the number of SMDS SIP3 SA Not Found violations exceeds threshold

The number of source address not found violations exceeds the specified SMDS PDU threshold for the logical port.

• Lport port name in switch switch name the number of SMDS SIP3 SA DA on Same Port violations exceeds threshold

The number of SA DA on Same Port violations exceeds the specified SMDS PDU threshold for the logical port.

Note – The following nine traps are based on a counter that is set from the Add Logical Port dialog box when you add an SMDS logical port. The threshold value can be set to a value from 1 to 255 (with a default value of 10). The threshold value applies to all nine traps.

These trap violations occur during the transmission of an SMDS packet. The system maintains a counter for each type of violation and generates a trap each time the value in the counter exceeds the specified threshold value. After sending the trap, the system resets the counter to zero.



• Lport port name in switch switch name the number of SMDS SIP3 SA Not Found violations exceeds threshold

The number of source address not found violations exceeds the specified SMDS PDU threshold for the logical port.

• Lport port name in switch switch name the number of SMDS SIP3 Source IA Screen Fail violations exceeds threshold

The number of source individual address screen failures exceeds the specified SMDS PDU threshold for the logical port.

• ML Member Trunk ML member lport name at switch switch name bound to MLFR Trunk Bundle LPort lport name has changed state to state. The corresponding MLFR Trunk trunk name has total aggregate bandwidth of aggregate BW and operational bandwidth of operational BW.

The ML member trunk associated with the specified logical port has changed state. Possible values for the state variable are described below:

– ndown (0) — The switches cannot establish a communication link.

– nattempt (1) — A switch is attempting to contact another switch but has not yet received a response.

– ninit (2) — A one-way communication exists between the switches.

– n2way (3) — A bidirectional communication exists between the switches.

– nexstart (4) — The switches are about to exchange information on the network topology.

– nexchange (5) — The switches are exchanging network topology information.

– nloading (6) — The switches are requesting the most recent link state information.

– nfull (7) — The trunk is up and operational between the switches.

– btdefined (9) — A backup trunk is ready.

• MPLS LSR XCs admin/oper status has changed to admin status = admin status and oper status = oper status

The MPLS LSR cross-connect administrative or operator status has changed.

• MPLS tunnels admin/oper status has changed to admin status = admin status and oper status = oper status

The MPLS tunnels administrative or operator status has changed.

• NSI Upgrade has begun upgrading on the control card (NP/SP) for switch switch name

The NSI upgrade has begun.

• OAM cleared on circuit circuit name

The OAM cell rate on this ATM circuit has dropped to acceptable levels after having previously exceeded the threshold of 1,000 calls per second.




• OAM overload detected on circuit circuit name at switch switch name on lport lport name

The OAM speed on this circuit exceeded the threshold of 1,000 cells per second.

• On card at Slot slot number, the configuration file download from EMS to switch switch name is state

This message sends traps at various stages of the configuration file download from the EMS to the switch.

• On card at Slot slot number, the configuration state is new state after the offline PRAM download

The configuration has changed after the offline PRAM downloaded to the switch.

• On switch switch name at Slot slot number the configured card type value type does not match the actual card type value type

The input/output adapter (IOA) card type value specified through the NMS does not match the card type value of the installed card.

• One or more SVC call failures have been logged

One or more SVC call failures have been logged in the svcAtmFailedCallTable.

• ONT slot number, port number, ONT ID has declared/cleared PON Alarm State

A trap has been generated by the core ONT software.

• ONT ONT ID Slot slot number hosted on OSU pport slot number, port number has declared/cleared PON alarm state.

A trap has been generated by an ONT’s subcard.

• OSU pport at switch name, slot number, port number has a declared/cleared PON Alarm State

A trap generated by OLT on behalf of an ONT.

• PGL of peer group has changed for Node ID node ID with the new PGL election state state

The local switch has either activated as logical group node (LGN) or deactivated from LGN within a PNNI peer group. The new peer group leader (PGL) election state may be one of the following:

– starting (1)

– awaiting (2)

– awaiting full (3)

– initial delay (4)

– calculating (5)

– awaiting unanimity (6)

– oper pg 1 (7)



– oper not pg 1 (8)

– hung election (9)

– awaiting reelection (10); activated (1), deactivated (2)

• PMP ATM circuit circuit name endpoint index number at switch switch name is Ckt Leaf Oper Status Ckt leaf Connection Fail Reason, Node Port

The point-to-multipoint ATM PVC state has been changed. The possible numerical values for the Ckt Leaf Oper Status are the following: invalid (0), inactive (1), active (2). The possible values for the fail reason include the values in Table 1-3 on page A-18.

• PNNI Neighbor node ID has changed state to state for Node ID

This trap is generated when a neighboring peer state changes to Full or Down with respect to the neighbor Finite State Machine (FSM). The new state may be: (1) npdown, (2) negotiating, (3) exchanging, (4) loading, (5) full.

• PNNI link state has changed to state state for Node ID node ID

This trap is generated when there is a change in the Border node link state with respect to hello FSM states. The new state for the link may be: (1) not applicable, (2) down, (3) attempt, (4) One-way inside, (5) Two-way inside, (6) One-way outside, (7) Two-way outside, (8) common outside.

• Power supply number at switch name is state

The specified chassis power supply in the specified switch has changed state. States may be the following: (1) up, (2) down, (4) marginal.

• Pport switch name, slot number, port number is state with alarm type

The specified physical port on the specified IOM slot on the specified switch has changed state. Possible state values for the physical port are Up, Down, or Testing. Possible values for the alarm type are described in Table 1-6.

Table 1-6. Alarm Types


None 0 No alarm condition.




Red 1 A loss of signal or out-of-frame error. An out-of-frame error occurs when the receiver detects one of the following conditions:

• Two or more framing-bit errors within a 3 millisecond period

• Two or more errors within five or fewer consecutive framing bits

A loss of signal error occurs if the device detects 175+/-75 contiguous pulse positions of either positive or negative polarity.

After declaring a Red Alarm, the device sends a Yellow Alarm Signal to the far-end, which declares a Yellow Alarm.

Yellow 2 A remote channel service unit (CSU) is transmitting a Red Alarm. The remote CSU is not receiving any transmission signals from your circuit and the circuit is acting as a one-way link.

Blue 4 A keep-alive (KA) condition exists. This condition occurs when the DS1 multiplexer fails or is disconnected and the CSU sends continuous unframed 1s to the network to keep the signal alive.

Carrier loss 8 A loss of DS1 synchronization on the inbound (1x) signal has occurred.

Loopback 16 The CSU is currently in a loopback state.

BER Threshold 64 A bit error rate (BER) threshold was exceeded.

Signal Label Mismatch

128 A SONET path signal label mismatch was detected.

Loss of Signal 256 A receive loss of signal (LOS) was detected.

Loss of Frame 512 A receive loss of frame (LOF) was detected.

Loss of Cell Delineation

1024 A loss of ATM cell delineation was detected.

Line AIS 2048 A receive SONET line alarm indication signal (AIS) was detected.

Path AIS 4096 A receive SONET path AIS was detected.

Loss of Pointer 8192 A SONET loss of pointer was detected.

Table 1-6. Alarm Types (Continued)




• Pport at switch name, slot number, port number has mismatched interface type (actual: interface, configured: interface)

This trap indicates the actual physical interface is different than the configured physical interface.

• Pport slot number.pport number in switch switch name issues Threshold Crossing Alert on ATM TCA ID

This trap indicates that a threshold crossing problem was detected and the ATM TCA identified by the ATM TCA ID, slot number and physical port number was issued.

• Pport switch name.slot number.physical port number DS1 ESF Data Link (FDL) status has changed state to DS1 ESF Data Link (FDL) status

There has been a change in the status of the DS1 ESF Data Link (FDL). The DS1 ESF Data Link (FDL) status is detected on the port and can be inService (1), or outOfService (2).

• PPort switch name.slot number.port number has just gone loopback status

The loopback status of a D3/E3 or T1/E1 card has changed to one of the following status types:

– Noloop — No loopback. The card currently has a loopback status of normal, no loopback is in effect.

– Payloadloop — Payload loopback (a near-end loopback). When a payload loopback is activated, the signal transmitted beyond the loopback point (the forward signal) is the same as the received signal at the loopback point.

– Line — Line loopback (a near-end loopback). A line loopback operates upon receipt of specific framed pulse patterns. The line loopback pulse codes and functions are either Activate or Deactivate.

Line RFI 16384 A receive SONET line remote failure indication (RFI) was detected.

Path RFI 32768 A receive SONET path RFI was detected.

Signal Label Undefined

65536 A SONET path signal label unequipped was detected.

Idle 131072 The signal was idle.

Equipment Mismatch

262144 The detected physical interface daughter card type (the IOA) does not match the configured CBX 500 IOM type. All physical ports on the IOM are down.

Admin Down 524288 The admin status of the physical port was set to down.

Table 1-6. Alarm Types (Continued)





• Power supply #3 at switch switch name is state

This trap indicates power supply #3 has changed state (toggled between up and down states). Power supply status values include the following:

– up (1)

– down (2)

– marginal (4)

• PRAM Consistency Check error: file configuration file on set set number on the active and the standby CP does not match

Differences were detected between the active and standby unit copies of the specified configuration.

• PRAM Consistency Check OK: file configuration file on set set number on the active and the standby CP matches

The active and standby unit copies of the specified configuration file are now in sync again.

• PRAM File PRAM filename download to switch switch name is complete

The download of the specified file from the NMS to the specified switch is complete. This trap should follow any PRAM synchronization attempt that the user performs from the NMS. Note that the affected module still must complete the automatic post-download warmboot before returning to full operation.

• PRAM File PRAM filename download to switch switch name has failed

The download of the specified file from the NMS to the specified switch has failed. This trap may follow a PRAM synchronization attempt that the user performs from the NMS if the file download is unsuccessful for any reason. If this occurs, the PRAM synchronization should be reattempted.

• Release the backup trunk associated with lport lport name on switch switch name

The backup trunk associated with the specified logical port has been released.

• Redundant switchover failed for slot slot

The requested redundant switchover fails for the specified slot.

• Redundant state on switch switch name is changed to new state

A redundancy state change has occured on the switch.

• Revertive mode has changed to mode

The revertive mode has changed state.

• RLMI service name binding service name binding on switch switch name now has an operational state of state

The specified service name binding is in one of the following states described in Table 1-7 on the specified switch:



• Set DS0 channel on pport switch name.slot number.port number to DS0 far end loopback has failed

The request to set a DS0 into far-end loopback has failed.

• Slot slot number has been reverted back from redundant slot redundant slot number on switch switch name

The slot has reverted back to the original slot from the redundant slot.

• Slot slot number in switch switch name did not respond to the poll from the CP/SP/NP

The IOM or CP/SP/NP in the specified slot in the specified switch has stopped responding to polls from the CP/SP/NP. This may be an indication of a problem with the IOM; under normal conditions, the IOM or CP/SP/NP responds to a poll from the CP/SP/NP. This trap will occur any time a card is either warm- or cold-booted and may occur during heavy congestion in the IOM’s CPU.

• Slot slot number in switch switch name has just come up

The module in the specified slot in the specified switch has started to respond to polls from the CP, SP, or NP. This trap normally occurs after a module has completed its reboot cycle and has transitioned to an active state.

• Slot slot number in switch switch name issues Threshold Crossing Alert on ATM TCA ID

A threshold crossing problem has been detected, and the ATM TCA identified by the ATM TCA ID and slot number was issued.

• Slot slot number at switch switch name transmit clock synchronization has changed state to synchronization status

The IOM transmit clock Phase Locked Loop (PLL) synchronization status has changed.

Slot slot number at switch switch name primary clock reference has changed state to primary clock status

The IOM system primary clock reference status has changed. Status values are normal (1) and failure (2).

• Slot slot number at switch switch name secondary clock reference has changed state to secondary clock status

Table 1-7. RLMI Service Name Binding Operational States

State Description

none (1) No status at this time.

preferred (2) The preferred port is currently active.

backup (3) The backup port is currently active.




The IOM system secondary clock reference status has changed. Status values are normal (1) and failure (2).

• Slot slot number at switch switch name clock reference has changed state to sys primary clk status

The IOM system primary clock reference has changed to the specified system primary clock status as detected on the card. The sys primary clk stat variable can be either normal (1) or failure (2).

• Slot slot number at switch switch name secondary clock reference has changed state to system secondary clk status

The IOM system secondary clock reference status has changed to the specified system secondary clock status as detected on the card. The system secondary clk stat value can be either normal (1) or failure (2).

• Slot slot number in switch switch name is overload severity number

The overload severity has changed. A severity number other than zero indicates the card is in real-time overload and is shedding load. A higher severity implies a greater percentage of load is being shed.

• Slot slot number on Switch switch name has completed Warm Boot Upgrade successfully

The module in the specified slot number has successfully initialized.

• Slot slot number on Switch switch name has failed Warm Boot Upgrade due to fail reason

A Warm Boot Upgrade has failed on the module in the specified slot number on the specified switch for the specified fail reason. The fail reason variables are described in Table 1-8.

Table 1-8. Warm Boot Upgrade Fail Reason Variables

Reason Variable Condition

none (1) The card successfully completed the Warm Boot Upgrade.

not-warmstart-capable (2) You have attempted to use the Warm Boot Upgrade function with an unsupported card on the switch. For this reason, a Cold Boot was issued after download of the code to this unsupported card.

bootflash-update-failed (3) The download of the bootflash code failed.

application-load-failed (4) The download of the application code failed.

application-read-failed (5) The system was not able to read an application code file.



• Slot slot in Switch name has reported a non fatal error: Src=source, Time=time, Major=major errorcode, Minor=minor errorcode, String=ASCII string

The card in the reported slot discovered a non-fatal error condition. Possible values for the source variable are:

– power-on diagnostics (1)

– background-diagnostics (2)

– fault (3)

– frame-heap (4)

The time variable indicates the time that the last non-fatal error was reported. The major error code variable indicates the major error code of the last non-fatal error. The minor error code variable indicates the minor error code of the last non-fatal error. The ASCII string variable indicates the ASCII string that describes the last non-fatal error.

• Slot slot in Switch name, a warmboot upgrade has initiated a coldboot coldboot.

A warmboot upgrade has initiated a coldboot on this standby card.

• SONET/SDH J1 path trace message on Slot.pport Slot.Port is indicated.condition with the expected message.

The SONET SDH J1 path trace message on the specified slot and pport matches or does not match the expected message.

• State has changed to type in the DS3 Circuit Emulation port Pport ID of Subcard physical slot of card slot ID due to reason reason code.

This trap indicates a state change in the DS3 Circuit Emulation ports receiving AA11 cells from the ATM network side of the card. The state may be: (1) up, (2) down, (3) testing. Reason codes may be one of the following:

loader-load-failed (6) The system could not load the fast loader. The fast loader is the module that overwrites the old application code with the new application code.

save-state-failed (7) The save state failed.

card-timed-out (8) A card time-out occurred.

standby-card (9) Standby card which was, therefore, automatically cold booted.

downgrade-not-supported (10) Downgrade not supported.

Table 1-8. Warm Boot Upgrade Fail Reason Variables (Continued)

Reason Variable Condition




– none (0)

– red alarm (1)

– yellow alarm (2)

– blue alarm (4)

– carrier loss (8)

– looped back (16)

• SVC failure threshold has been exceeded on Lport Lport name at switch switch name

The number of ATM and Frame Relay SVC failures that occurred on the specified LPort on the specified switch has exceeded the provisioned threshold. The default value of this threshold is one failure every 15 minutes: if one failure occurs in a 15-minute period, this trap is displayed. If more than one failure occurs, another trap will not be displayed for another 15 minutes. Use the Detailed Failed SVC Attributes dialog box for specific information about the failures. See “Viewing SVC Failed-Call Attributes” on page 11-21 for information about failed SVCs.

• SW File SW filename download to switch switch name is complete

An NMS-initiated download of the specified software file to the specified switch has succeeded and is now complete.

• SW File SW filename download to switch switch name has failed

An NMS-initiated download of the specified software file to the specified switch has failed. If this occurs, the user should reattempt the download.

• Switch switch name checksum or CRC-32 error occurred in flash

A checksum or CRC-32 error occurred in flash memory.

• Switch switch name checksum error or battery problem occurred in PRAM

A checksum error or battery problem occurred in the PRAM.

• Switch switch name diagnostic log table full

The diagnostic log table was full and, for this reason, was copied to a Trivial File Transfer Protocol (TFTP) buffer that will be transferred to the NMS.

• Switch switch name: EGP neighbor down (SNMP egpNeighborLoss Trap) for neighbor ifIndex egpNeighAddr

An Exterior Gateway Protocol (EGP) neighbor is down.

• Switch switch name fatal internal error encountered and system needs to be rebooted

The system encountered a fatal internal hardware or software error. Reboot the system to correct this problem.

• Switch switch name has completed Warm Boot Upgrade

Warm Boot Upgrade has completed on the specified switch.



• Switch switch name has initiated Warm Boot Upgrade

Warm Boot Upgrade is being performed on a module in the specified switch.

• Switch switch name has reported a non fatal error: Src=source, Time=time, Major=major errorcode, Minor=minor errorcode, String=ASCII string

A component in the switch discovered a non-fatal error condition. Possible values for the source variable are:

– power-on diagnostics (1)

– background-diagnostics (2)

– fault (3)

– frame-heap (4)

The time variable indicates the time of the last non-fatal error. The major error code variable indicates the major error code of the last non-fatal error. The minor error code variable indicates the minor error code of the last non-fatal error. The ASCII string variable indicates the ASCII string that describes the last non-fatal error.

• Switch switch name: Incorrect community name (SNMP authentication failure trap)

The sending protocol entity has received a protocol message that is not properly authenticated.

• Switch switch name interface down (SNMP linkDown trap) on Lport lport name

The sending protocol entity recognizes a failure in one of the communication links in your network configuration. The following conditions cause this trap to occur:

– The Admin Status of a physical port was set to down.

– The Admin Status of a logical port was set to down.

– A physical port has lost its input modem signals.

– An IOM was removed.

– An active optimum trunk had a status change and is now inactive.

– An active virtual circuit had a status change and is now inactive.

– An active T1/T3 channel had a status change and is now inactive.

– An active Serial Line Internet Protocol (SLIP) connection had a status change and is now inactive.

– A timeout was detected on an ethernet line.

– A persistent transmit stall was detected on a physical port.

– An active trunk received no response to five consecutive Keep Alive messages.

– An active trunk received an incorrect response to a Keep Alive message.




– An active trunk received a logical down response to a Keep Alive message.

• Switch switch name interface up (SNMP linkUp trap) on Lport lport name

The sending protocol entity recognizes that one of the communication links represented in your network configuration has become active. The following conditions cause this trap to occur:

– The Admin Status of a physical port was set to up.

– The Admin Status of a logical port was set to up.

– A physical port has recovered its input modem signals.

– An IOM that was removed is now active.

– An inactive optimum trunk had a status change and is now active.

– An inactive virtual circuit had a status change and is now active.

– An inactive T1/T3 channel had a status change and is now active.

– An inactive SLIP connection had a status change and is now active.

– An inactive ethernet line is now active.

• Switch switch name IO error occurred in DRAM or SRAM

An I/O error occurred in dynamic ram (DRAM) or in static ram (SRAM).

• Switch switch name is reachable

The specified switch is now reachable by the NMS.

• Switch switch name is unreachable

The specified switch is no longer reachable by the NMS. If this occurs, verify that the connectivity between the NMS workstation and the switch is intact and functioning (you can use an NMS workstation to ping the switch).

• Switch switch name reserved for Frame Relay SVC

The specified switch is reserved for Frame Relay SVC.

• Switch switch name trace table full

The node trace table was full and, for this reason, was copied to a TFTP buffer that will be transferred to the NMS.

• Switch switch name up with no changes (SNMP warmStart trap)

A warmStart trap indicates that the sending protocol entity is reinitializing itself and neither the agent configuration nor the protocol entity implementation is altered.

• Switch switch name up with possible changes (SNMP coldStart trap)

A coldStart trap indicates that the sending protocol entity is reinitializing itself and the agent's configuration or the protocol entity implementation may be altered.



• Switch switch name VST RLE memory could not add a new route or is more than 90% utilized

The VST RLE memory could not add a new route or is more than 90% utilized on the specified switch.

• Switch switch name has reported an ICMP trap message: message

The specified switch detected a bad IP packet and generated the specified Internet Control Message Protocol (ICMP) trap message. The message includes a standard ICMP error code, a protocol identifier, and the source and destination IP address from the bad IP packet.

• Switch switch name Standby SF <-> Slot slot ID: Standby SF not responding

The standby switch fabric is not responding.

• Switch switch name Standby SF <-> Slot slot ID: Standby SF responding

The standby switch fabric was not responding but is now responding again.

• Slot card logical slot, Subcard subcard physical slot (Type=subcard actual type) in switch switch name now has an operational state of state

A GX 550 Multiservice WAN Switch subcard has changed to the specified state.

• Slot card logical slot, Subcard subcard physical slot (Type=subcard actual type) in switch switch name has had a switchover

A GX 550 Multiservice WAN Switch subcard has undergone a switchover.

• Switch switch name Reserved for Frame Relay SVC

The specified switch name is reserved for Frame Relay SVC use.

• Switch switch name has crossed the High Water Mark threshold

This trap is triggered when the SNMP High-Water Mark threshold is crossed.

• Switch switch name primary synchronization reference operational state has changed to synchronization reference

The Primary Synchronization Reference operational state has changed to the specified clock synchronization reference source. Possible values include the following:

– externala (1) — T1 Rate External Clock 1.

– externalb (2) — T1 Rate External Clock 2.

– portrefa (3) — IOM Port Reference Clock 1.

– portrefb (4) — IOM Port Reference Clock 2.

– internal (5) — Internal Free Running Clock.

– holdover (6) — Holdover.

• Switch switch name secondary synchronization reference operational state has just changed to synchronization reference

The Secondary Synchronization Reference operational state has changed to the specified clock synchronization reference source. Values include the following:




– externala (1) — T1 Rate External Clock 1.

– externalb (2) — T1 Rate External Clock 2.

– portrefa (3) — IOM Port Reference Clock 1.

– portrefb (4) — IOM Port Reference Clock 2.

– internal (5) — Internal Free Running Clock.

– holdover (6) — Holdover.

• Switch switch name external reference clock number operational state has just changed to state

The specified external reference clock (the T1 or E1 clock wired to the back of the switch SPA) on the specified switch has changed state. The following states are possible:

– Active — The clock has been restored and is operational.

– Detected Loss of Signal — The clock signal is no longer present.

– Detected AIS Alarm — An AIS alarm has been received on the external clock port.

– Detected Loss of Frame — The framing has been lost on the received signal.

• Switch switch name external Reference Clock 1 operational state has just changed to current state ext clk 1

The External Reference Clock 1 operational state has changed to the specified current state of external clock 1. Possible values for current state ext clk 1 include:

– active (1) — Valid.

– ais (2) — Detected AIS Alarm.

– los (3) — Detected Loss Of Signal.

– lof (4) — Detected Loss Of Frame.

• Switch switch name external Reference Clock 2 operational state has just changed to current state ext clk 2

The External Reference Clock 2 operational state has changed to the current state of External Clock 2. Possible values for current state ext clk 2 include the following:


– ais (2) — Detected AIS Alarm.

– los (3) — Detected Loss Of Signal.

• Switch switch name port Reference Clock 1 operational state has just changed to current state port clk A

The Port Reference Clock 1 operational state has changed to the current state of port Reference Clock A. Possible values for current state port clk A include the following:




– down (2) — Invalid.

• Switch switch name port Reference Clock 2 operational state has just changed to current state port clk B

The Port Reference Clock 2 operational state has changed to the current state of the Port Clock B reference. Possible values for current state port clk B include the following:


– down (2) — Invalid.

• Switch to Accounting Server communication for service number has failed and a usage file transfer has failed to complete

There is a communication failure between a switch and an Accounting Server, and a usage file transfer has failed to complete.

• Switch to ATM Accounting Server (AS) communication has failed for Switch switch name (Primary AS Address = Primary Accounting Server Address, Secondary AS Address = Secondary Accounting Server Address, Accounting Switch Control = Switch Level Accounting Control). A usage file transfer has failed to complete. Number of Acctg Svr Comm Failures have occurred during the day.

There is a communication failure between a switch and an ATM Accounting Server, and a usage data file transfer has failed to complete.

• Switch to ATM Bulk Statistics Server communication has failed for Switch switch name (Server Address = number). A usage file transfer has failed to complete. Switch-to-Server communication failures have occurred during the day.

There is a communication failure between a switch and an ATM Bulk Statistics Adjunct Processor, and a usage data file transfer has failed to complete.

• Switch to Frame Relay Accounting Server (AS) communication has failed for Switch switch name (Primary AS Address = Primary Accounting Server Address, Secondary AS Address = Secondary Accounting Server Address, Accounting Switch Control = Switch Level Accounting Control). A usage file transfer has failed to complete. Number of Acctg Svr Comm Failures have occurred during the day.

There is a communication failure between a switch and a Frame Relay Accounting Server, and a usage data file transfer has failed to complete.

• The Accounting Server accounting server IP address failed to transfer one or more AMA files to the BOS

The accounting server failed to transfer one or more accounting files to the Billing Operations Server (BOS).




• The Accounting Server accounting server IP address has received data from a switch that is not in the configuration. Please update the Accounting Server configuration.

The accounting server received data from a switch that is not defined in its configuration.

• The Accounting Server accounting server IP address has been shut down

The accounting server has been shut down.

• The Accounting Server accounting server IP address is operational

The accounting server is operational.

• The Accounting Server accounting server IP address took over for a failed Accounting Server

Notice that an Accounting Server took over for a failed Accounting Server.

• The ATAF Session on ATAF LPort Ifindex ifindex with VPI vpi value and VCI vci value, has been initiated on ingress Lport Ifindex ifindex with VPI vpi value and VCI vci value,

An ATM test access function (ATAF) session has been initiated on the specified LPort address.

• The ATAF Session on ATAF LPort Ifindex ifindex with VPI vpi value and VCI vci value, has been disconnected on ingress Lport Ifindex ifindex with VPI vpi value and VCI vci value.

An ATM test access function (ATAF) session has been discontinued on the specified LPort address.

• The ATM Accounting Control at the Logical Port (LP) level has been changed for Switch switch name. (LP Accounting Control = logical-port--level accounting control, LP Interface Index = Lport If Index, Slot ID = slot ID, Physical Port ID = pport ID, LP ID = lport ID).

ATM accounting has been enabled or disabled on the specified logical port. The switch does not generate this trap when it boots (that is, when the global atmacctControl object is modified). The switch generates this trap only when the value of atmacctLportControl object is modified for a specific logical port.

• The ATM Accounting Control has been changed for Switch switch name to switch-level accounting control

ATM accounting has been enabled or disabled on the switch. The switch generates this trap when it boots or when the value of atmacctControl object is modified.

• The backup clock source backup clock source is selected on port pport number, slot slot number, switch switch name

The physical port has lost the external clock source and is switching over to the selected backup clock (if the physical port’s IOM is in external clock source mode).

• The BERT status at pport switch name.slot number.port number is status



Indicates the BERT status at the indicated pport

• The card upgraded status at slot slot number is status

Indicates the status of the upgrade in the card in the indicated slot.

• The DS0 channel on pport switch name.slot number.port number has just gone into the DS0 far end loopback

The request to set a DS0 into far-end loopback has succeeded.

• The DS0s on port port number, slot slot number, switch switch name have just gone into the ds0 loopback

One or more DS0s have been put into loopback.

• The DS0s on port pport number, slot slot number, switch switch name have just gone out of loopback

One or more DS0s have returned from a status of loopback to a status of normal.

• The Emergency Action Interrupt (EAI) feature on switch switch name has been enabled/disabled.

This trap is triggered when the user enables or disables the Emergency Action Interrupt (EAI) feature.

• The external clock is recovered and the pport pport number, slot slot number, switch switch name will switch back to external clock

The external clock has recovered, and the physical port switches back to the external clock.

• The fan on the Extender Shelf associated with pport pport ID on Slot slot ID has changed state to state on switch switch name

The fan on the GX 550 Extender Shelf associated with the specified pport has changed state (toggled between up and down states).

• The FCP OBMUX has detected Slot slot ID a potential input fifo overrun in the OBMUX or that the QM has not taken its command

The FCP OBMUX has detected a potential First In First Out (FIFO) overrun in the OBMUX, or the QM has not taken its command. The card may be warm booted.

• The FCP IB or QM as detected Slot slot ID an error

This trap indicates that the FCP IB or QM has detected an error. Potential QM errors may be one of the following: real-time under flow error, non-real-time under flow error, synchronization error, or overflow error. The IB error is a synchronization error between the phy-mux and ibmux. The card must be warm or cold booted.

• The Frame Relay Accounting Control has been changed for Switch switch name to switch-level accounting control

Frame Relay accounting has been enabled or disabled on the switch. The switch generates the trap when it boots or when the value of fracctControl object is modified.




• The Frame Relay Accounting Control at the Logical Port (LP) level has been changed for Switch switch name. (LP Accounting Control = logical-port--level accounting control, LP Interface Index = Lport If Index, Slot ID = slot ID, Physical Port ID = pport ID, LP ID = lport ID).

Frame Relay accounting has been enabled or disabled on the specified logical port. The switch does not generate this trap when it boots (that is, when the global fracctControl object is modified). The switch generates this trap only when the value of fracctLportControl object is modified for a specific logical port.

• The IMA Group current thresholds threshold number on Switch switch name have been crossed on IMA group IMA group

The IMA group current thresholds have been crossed.

• The IMA Group day thresholds threshold on Switch switch name have been crossed on IMA group IMA Group

The IMA Group day thresholds have been crossed.

• The IMA Link current thresholds threshold number on Switch switch name have been crossed on IMA Link Interface interface of IMA Group IMA group

The IMA link current thresholds have been crossed.

• The IMA Link day thresholds threshold on Switch switch name have been crossed on IMA group IMA Group

The IMA Link day thresholds have been crossed.

• The LPort NTM Congestion status of interface index at switch name has changed to congestion status

There is a change of congestion status on a logical port. Possible values for the severe congestion status include the following:

– Not congested (1)

– Congested (2)

• The MPT Circuit has changed the state (MPT Domain=MPT domain, MPT PT Node=MPT PT node, MPT Operational status=MPT operational status, Trap Severity=trap severity, Trap Sequence Number=trap sequence number)

The Multipoint-to-Point Tunnel (MPT) circuit has changed the state.

• The NDC Threshold has been crossed (switch name, interface number, source connection identification number) with Incoming Discarded CLP0 Cells = number for the associated threshold value of value

This trap is a Network Data Collection (NDC) Threshold Crossing Alarm for the number of CLP0 cells discarded in a PVC on an IOM. It is not generated more than once within the 15-minute NDC measurement interval.

• The NDC Threshold has been crossed (switch name, interface number, source connection identification number) with Incoming Discarded CLP0+1 Cells = number for the associated threshold value of value



This trap indicates a Network Data Collection Threshold Crossing Alarm for the number of CLP0+1 cells discarded in a PVC on an IOM. It is not generated more than once within the 15-minute NDC measurement interval.

• The NSI Phase number Upgrade has been initiated in card slot ID for switch switch name

An NSI Phase 1, 2, 3, or 4 upgrade has been initiated on the specified slot and switch.

• The NSI Phase number Upgrade has failed on card slot ID for switch switch name

An NSI Phase 1, 2, 3, or 4 upgrade has failed on the specified slot and switch.

• The NSI Upgrade has been completed on card slot ID for switch switch name

The NSI upgrade is complete

• The number of FRF.19 frames discarded at the Boundary monitoring point have reached 200

The number of frames discarded by the Boundary monitoring point have exceeded the threshold number of 200.

• The number of SMDS DXI2 Invalid Mgmt Link ID violations exceeds the SMDS PDU violations threshold for the Lport port name in switch switch name

The number of invalid management link ID violations exceeds the specified SMDS PDU threshold for the logical port on the specified switch.

• The operational state of the ATM accounting system on switch switch name has changed to operational state of ATM accounting system. The current Switch Level Accounting Control is switch-level accounting control.

The operational state of the ATM accounting system on the switch has changed. The switch generates this trap when the ATM accounting system enters the non-operational state due to a critical failure of communications with the ATM Accounting Server. The switch also generates this trap upon recovery from this critical condition. This trap is not generated for a change of the atmacctOperState object in conjunction with an operator change of the atmacctControl object.

• The operational state of the Frame Relay accounting system on switch switch name has changed to operational state of Frame Relay accounting system. The current Switch Level Accounting Control is switch-level accounting control.

The operational state of the Frame Relay accounting system on the switch has changed. The switch generates this trap when the Frame Relay accounting system enters the non-operational state due to a critical failure of communications with the Frame Relay Accounting Server. The switch also generates this trap during recovery from this critical condition. This trap is not generated for a change of the fracctOperState object in conjunction with an operator change of the fracctControl object.

• The percentage of frame memory utilization percentage on slot slot number exceeded the threshold




This trap indicates the percentage of frame memory utilization on this card has exceeded the threshold.

• The port pport number on slot slot number, switch switch name does not support external clock

The physical port on the IOM (and the IOM itself) is unable to run the external clock.

• The power supply B on the Extender shelf associated with pport pport ID on Slot Slot ID has changed state to state on switch switch name

The DC 48V power supply B on the GX 550 Extender Shelf has toggled between up and down states.

• The PPP LCP has entered the CLOSED state on LPort lport name at switch switch name

PPP Link Control Protocol (LCP) has entered the CLOSED state on the specified logical port.

• The PPP LCP has entered the OPEN state on LPort lport name at switch switch name

PPP LCP has entered the OPEN state on the specified logical port.

• The previous file transfer request request on switch switch name is file transfer status

This trap reports the outcome of a previous file transfer request.

• The Provisioning Server process ID has terminated on host IP address. The Server received a signal signal number which prompted the shutdown.

The Provisioning Server sends this message to an SNMPv1 agent to record the Provisioning Server's shutdown. The <process ID> and <IP address> variables identify the Provisioning Server, and signal number identifies the signal that caused the shutdown. The environment variable PSRV_TRAP_VERSION in start-server.sh specifies the SNMPv1 version being used for traps. Currently, only SNMPv1 is supported.

• The Provisioning Server process ID on host IP address is operational.

The Provisioning Server sends this message to an SNMPv1 agent to record the Provisioning Server's startup. The <process ID> and <IP address> variables identify the Provisioning Server. The environment variable PSRV_SEND_TRAPS_TO in start-server.sh specifies the host name or IP address of the receiving SNMPv1 agent.

• The reference time server IP address of reference time server on the switch switch name fails to respond to an NTP time request and no other time servers are available

A time server has failed to respond, and no other time server is available.

• The stand-by card in slot number at switch name has become the active card



The card in the specified slot number is now the active partner of the pair (succeeding its partner to become the active partner).

• The state of communications to the ATM accounting system on switch switch name has changed to current state of communications to ATM accounting system. The current Switch Level Accounting Server Control is switch-level accounting server control (Primary Accounting Server = primary accounting server address, Secondary Accounting Server = secondary accounting server address).

There is a changed state of communications with the ATM accounting server.

• The state of communications to the Frame Relay accounting system on switch switch name has changed to current state of communications to ATM accounting system. The current Switch Level Accounting Server Control is switch-level accounting server control (Primary Accounting Server = primary accounting server address, Secondary Accounting Server = secondary accounting server address).

There is a changed state of communications with the Frame Relay accounting server.

• The Statistics Server Diskspace has exceeded

The disk space threshold of the Statistics Server’s file system has been surpassed.

• The Statistics Server is operational

The Statistics Server is now operational.

• The Statistics Server has been Shutdown

The Statistics Server’s operations have been manually shut down.

• The status of the ATM signaling function has changed to status on lport name at switch name

The ATM signaling function status has changed on the logical port. Status indicates the operational status of this function on the specified port.

• The status of the ATM ILMI function has changed to state on Lport Lport name at switch switch name

The ATM ILMI function has changed state for the specified logical port on the specified switch. This trap occurs only if the ILMI option on the logical port is set to enabled. The following states are possible:

– Up — the logical port is successfully exchanging ILMI poll traffic between the switch and the attached device.

– Down — the logical port is no longer successfully exchanging ILMI poll traffic between the switch and the attached device. The logical port statistics screen can help you determine the specific cause of this problem.

• The status of the ATM signalling function has change to state on LPort name at switch name




The ATM UNI or NNI signalling function has changed state for the specified logical port on the specified switch. This trap occurs only if the signalling option on the logical port is set to enabled. The following states are possible:

– Up — the logical port is successfully exchanging Q.SAAL traffic (for UNI signalling) between the switch and the attached device.

– Down — the logical port is no longer successfully exchanging Q.SAAL traffic between the switch and the attached device. The logical port statistics screen can help you determine the specific cause of this problem.

– Connecting — the logical port is transmitting Q.SAAL traffic to the attached device, but is not receiving any response from the attached device. The logical port statistics screen can help you determine the specific cause of this problem.

• The status of the Resilient LMI function now has operational state of state on LPort lport name in Slot slot name at switch switch name

The specified service name binding is in one of the states described in Table 1-9 on the specified logical port associated with the specified slot.

• The SONET/SDH Path Trace Message on pport slot ID pport ID has changed

This trap indicates that the Synchronous Optical Network (SONET)/Synchronous Digital Hierarchy (SDH) path trace message has changed.

• The time on the switch switch name has been changed by time difference milliseconds. The new time is the new time.

The time on the switch has changed, spanning a second boundary.

• The time-of-day clock on switch switch name is invalid or has not been configured.

Table 1-9. RLMI Logical Port Operational States

State Description

none (1) No status at this time.

idle (2) The working and protection links are idle.

workingInit (3) The working link is initializing.

workingDown (4) The working link is down.

workingUp (5) The working link is up.

protectInit (6) The protection link is initializing.

protectDown (7) The protection link is down.

protectUp (8) The protection link is up.



The time-of-day clock on the specified switch is invalid or has not been configured. This trap is generated only at CP/SP/NP boot-time.

• The unconfigured Accounting Server accounting server IP address tried to use the accounting system’s agent

The unconfigured Accounting Server tried to sue the accounting system’s agent.

• Threshold for the Statistics Server’s database exceeded

The threshold for the Statistics Server’s database has been exceeded.

• Transaction log threshold for the database has exceeded.

The transaction log threshold for the Statistics Server’s database has been exceeded.

• Trunk trunkname associated with Lport lport has gone into negative bandwidth state or recovered from negative bandwidth state in outgoing (reverse) direction of this Lport for one of the three QoS parameters (Qos2=qos.parameter, Qos3=qos.parameter, Qos4=qos.parameter).

The trunk associated with the indicated logical port has gone into negative bandwidth state or recovered from negative bandwidth state in outgoing (reverse) direction of this Lport for one of the three QoS parameters indicated.

• Trunk trunkname in switch name is down. Following PVCs are also down: circuit name list.

The specified trunk is down; as a result, the specified circuits are also down.

• Trunk trunk name at switch switch name is state

The specified trunk has changed states. Possible values for the state variable are:

– ndown (0) — The switches cannot establish a communication link.

– nattempt (1) — A switch is attempting to contact another switch but has not yet received a response.

– ninit (2) — A one-way communication exists between the switches.

– n2way (3) — A bidirectional communication exists between the switches.

– nexstart (4) — The switches are about to exchange information on the network topology.

– nexchange (5) — The switches are exchanging network topology information.

– nloading (6) — The switches are requesting the most recent link state information.

– nfull (7) — The trunk is up and operational between the switches.

– btdefined (9) — A backup trunk is ready.

• Upgrade status on switch switch name is new status

A switch-wide upgrade status is displayed.




• User login name has logged on to switch switch name from location

A user with the specified login name has logged into the specified switch name. The location variable identifies the user's location. This location is either an IP address (for Telnet) or a console number (for a serial port).

• User login name has logged out from switch switch name through location

A user with the specified login name has logged out of the specified switch name. The location variable identifies the user's location. This location is either an IP address (for Telnet) or a console number (for a serial port).

• Virtual Router router VPN name has been shut down on switch switch name

The designated virtual router has been shutdown.

Switch Diagnostics User’s Guide for CBX 3500, CBX 500, GX 550, and B-STDX 9000 B-1


B

Summary of Error Codes

You can interpret error codes differently, depending on the diagnostics source. For example, if the major/minor error code combination is 2.1 and the source is “Frame-heap,” then the code indicates an outbound heap low condition. However, if the major/minor error code combination is 2.1 and the source is “Background diagnostics,” then the code indicates a link stall detection condition.

Table B-1 on page B-2 summarizes the major and minor error codes when the source of the codes is background diagnostics. Table B-2 on page B-15 discusses some miscellaneous fatal error codes. See “Background Diagnostics” on page 5-1 for instructions on displaying these error codes.

For information on error codes from sources other than background diagnostics, consult the Data Networking Group (DNG) Technical Assistance Center (TAC). See the B-STDX, CBX, and GX Troubleshooting Guide for more information.

For information about system configuration requirements for the NMS, see the latest Software Release Notice (SRN) for Navis EMS-CBGX.

Note – An asterisk (*) appears in the Major Error column, after the number to indicate that additional information about the error is included in the 960 trace area. If any of these errors occur on your system, contact the TAC using the appropriate number for your region listed in “Technical Support” on page liii. Your TAC Representative can create a dump of the 960 trace area to determine the cause of the error. See the B-STDX, CBX, and GX Troubleshooting Guide for more information on contacting the TAC.

This table also specifies those error numbers that indicate fatal error conditions. For fatal error conditions, call the TAC. This manual does not describe how to resolve fatal errors.


B-210/7/05 Switch Diagnostics User’s Guide for CBX 3500, CBX 500, GX 550, and B-STDX 9000


Table B-1. Summary of Error Codes for Background Diagnostics

Major Error

Minor Error

Status Explanation

1 See Explanation

Non-Fatal Background diagnostics stalled. The minor error number is seconds in this state. This error occurs when an I/O module is not defined in the processor module or there is an internal software problem.

To resolve the error, configure the I/O slot and reinitialize the switch. See the Getting Started User’s Guide for CBX 3500, CBX 500, GX 550, and B-STDX 9000 for more information about initializing the switch. Call the TAC for assistance.

1* 0 Non-Fatal Indicates ingress Lport is not present.

2 to 16 See Explanation

Non-Fatal Link-stall detection. Transmit completions stalled. This error occurs when the switch cannot transmit because there is no clock present on the outbound interface. The major error number indicates the slot number, and the minor error number indicates the port number.

To resolve, check the physical port configuration, particularly the IOM attributes. See Chapter 2, “Viewing Network, Switch, Module, and Physical Port Details.” Specify the clock configuration if there is no clock present.

2 See Explanation

Non-Fatal, except on standby

The card crossed a threshold in the current number of message buffer allocations, where the threshold is X times 1024. These allocations are from intelligent random access memory (IRAM).

If the minor error is greater than 3, check card memory utilization from the NMS Background Diagnostics screen. See Chapter 5, “Viewing Background Diagnostics.” If remaining memory is less than 400,000 bytes, call the TAC for assistance.

2* 0 Non-Fatal Indicates VPI/VCI is not present at ingress.

3* 0 Non-Fatal Indicates circuit is inactive.

4 0 Fatal Indicates chain corruption in a memory block.

4* 0 Non-Fatal Indicates multiple taps for the same VPI/VCI has been attempted.

Beta Draft Confidential Summary of Error Codes

Switch Diagnostics User’s Guide for CBX 3500, CBX 500, GX 550, and B-STDX 9000 10/7/05B-3

5 1 Fatal If the text string includes “Parity Error”, the card has failed and then rebooted due to a parity error.

If this is a memory parity error in IRAM, CMEM, or DMEM, the string will contain a subtype of “1.” If this is a cell bus parity error, this string will contain a subtype of “2.”

5* 0 Non-Fatal Indicates connection type mismatch.

6* 0 Non-Fatal Indicates tapping of point-to-multipoint (PMP) circuits is not supported.

7 See Explanation

Fatal If text string includes “Internal Error”, the card has failed and rebooted due to low memory corruption. This minor error number is the bad value found.

Crash analysis needs to be done to determine the cause of the corruption, as it may not be hardware-related. Call the TAC.

7* 0 Non-Fatal Indicates tapping of Multipoint-to-Point Tunnel (MPT) circuits is not supported.

8* 0 Non-Fatal Indicates tapping of control circuits is not supported.

9* 0 Non-Fatal Indicates tapping of management circuits is not supported.

10* 0 Non-Fatal Indicates ATAF is not supported on ingress card.

11* 0 Non-Fatal Indicates egress card is down.

12* 0 Non-Fatal Indicates ATAF not supported on egress card.

13* 0 Non-Fatal Indicates that for BIO2 cards, egress and tap port is on the same PHY card.

14* 0 Non-Fatal Indicates egress has Automatic Protection Switching (APS).

15* 0 Non-Fatal Indicates egress has flow control processor (FCP) enabled.

16* 0 Non-Fatal Indicates resources are unavailable.

Table B-1. Summary of Error Codes for Background Diagnostics (Continued)

Major Error

Minor Error

Status Explanation




17 See Explanation


Errors found on control messages coming in from the cell bus. The minor error is the number of errored control messages received since the card last came up.

Note: This value may also be retrieved via MIB value cardInForwardBitBtus. A trap is generated if more than 15 of these errors occur in a one second interval.

If more than one of these traps occur in a minute, or if the change in the minor code is greater than 30, gather the following information:

• uptimes of the cards (MIB variable cardUpTime)

• version of code running in all the cards (MIB variable cardSwRev

• reboot counts for the cards in the switch (MIB variable cardDiagFatalReboots),

• any recent PPort, LPort, or trunk outages (in the last half hour before the trap occurred) on the switch

In addition, verify that all cards in the switch are running the same switch software revision. (Cards running mismatched software revisions in the same switch could cause this error.)

Contact the Lucent TAC with this information.

17* 0 Non-Fatal Indicates internal error.

18 See Explanation

Non-Fatal Received parity errors on bus receive. The minor error is the total number of errors.

18* 0 Non-Fatal Indicates bandwidth is unavailable on tapping port.

19 0 Fatal Direct memory access (DMA) descriptors corrupted.

19* 0 Non-Fatal Indicates access mode is unsupported.

20* 0 Fatal Interrupt vectors corrupted. Call the TAC.

20* 0 Non-Fatal Indicates tapping port is down.

21* See Explanation

Fatal 960 static RAM (SRAM) corrupted. The minor error number is the pointer to the bad SRAM location. Call the TAC.


Major Error

Minor Error

Status Explanation



21* 0 Non-Fatal Indicates tapping card is down.

22* 0 Fatal Fault table corrupted. Call the TAC.

23 0 Fatal Interrupts disabled. Call the TAC.

24 1 Fatal Processor kernel force bad parity bit is on. Call the TAC.

24 2 Fatal IOM force bad parity bit is on. Call the TAC.

25 0 Fatal Operating System (OS) counter/timer is disabled. Call the TAC.

26* See Explanation

Fatal Stack overflowed. The minor error number specifies the ID of the corrupted stack. Call the TAC.

27 1 Non-Fatal Bus transmits stalled - no transmits sent in last 90 seconds.

27 2 Non-Fatal Bus transmits full - hardware owns all bus transmit descriptors.

27 3 Non-Fatal Bus receives stalled - nothing received on bus in last 90 seconds.

28 See Explanation

Non-Fatal No fmem buffers available for user data. The minor error number is seconds in this state.


Major Error

Minor Error

Status Explanation




29 See Explanation


Bus Transfer Unit (BTU) headers obtained from the cell bus contain bad values. The error count increments if the VC identifier or the Lport interface number in the BTU header is invalid. A trap is generated if 10 or more of these errors in a one second interval.

The minor error number is the number of errored BTU headers received since the card last came up.

If more than one of these traps occur in a minute, or if the change in the minor code is greater than 30, gather the following information:

• uptimes of the cards (MIB variable cardUpTime)

• version of code running in all the cards (MIB variable cardSwRev)

• the reboot counts for the cards in the switch (MIB variable cardDiagFatalReboots)

• any recent PPort, LPort, or trunk outages (in the last half hour before the trap occurred) on the switch

In addition, verify that all cards in the switch are running the same switch software revision. (Cards running mismatched software revisions in the same switch could cause this error.)

Call the TAC with this information.

30* 1 Fatal Heap error – Invalid pointer on free. Call the TAC.

30* 2 Fatal Heap error – invalid heap header on free. Call the TAC.

30* 3 Fatal Heap error – out of memory on allocate. Call the TAC.

30* 4 Fatal Heap error – heap corrupted. Call the TAC.

30* 5 Fatal Heap error – an invalid heap block size when allocating a block memory.

30* 6 Fatal Heap error – invalid memory tag of previous block when freeing a block memory.

30* 7 Fatal Heap error – invalid memory tag of next block when freeing a block memory.


Major Error

Minor Error

Status Explanation



30* 8 Fatal Heap error – invalid memory tag of block when thread in block memory.

30* 9 Fatal Heap error – invalid memory tag of next block when thread in a block memory.

30* 10 Fatal Heap error – invalid memory tag of previous block when thread out block memory.

30* 11 Fatal Heap error – invalid memory tag of next block when thread out block memory.

30* 12 Fatal Heap error – invalid memory tag of block when allocating a block memory.

31 0 Fatal Failure to mount hard drive. This error will occur only during bootup. If a standby processor is present, the standby will take over as the active processor card.

Replace the processor card and RMA, whether a standby processor is present or not.

31 1 Non-Fatal PRAM initialized. This error is caused by resetting the PRAM.

To resolve, resynchronize the PRAM in the card. See the Getting Started User’s Guide for CBX 3500, CBX 500, GX 550, and B-STDX 9000.

31 2 Non-Fatal PRAM corrupted (header). To resolve, resynchronize the PRAM in the card. See the Getting Started User’s Guide for CBX 3500, CBX 500, GX 550, and B-STDX 9000.

31 3 Non-Fatal PRAM corrupted (bank 0). To resolve, resynchronize the PRAM in the card. See the Getting Started User’s Guide for CBX 3500, CBX 500, GX 550, and B-STDX 9000.

31 4 Non-Fatal PRAM corrupted (bank 1). To resolve, resynchronize the PRAM in the card. See the Getting Started User’s Guide for CBX 3500, CBX 500, GX 550, and B-STDX 9000.


Major Error

Minor Error

Status Explanation




31 5 Non-Fatal The PRAM version that this card is using is obsolete. The layout of the PRAM is incompatible with the software and the switch.

To resolve, resynchronize the PRAM in the card. See the Getting Started User’s Guide for CBX 3500, CBX 500, GX 550, and B-STDX 9000 for more information.

31 6 Non-Fatal Some PRAM records were discarded. To resolve, resynchronize the PRAM in the card. See the Getting Started User’s Guide for CBX 3500, CBX 500, GX 550, and B-STDX 9000 for more information.

31 7 Non-Fatal PRAM is uninitialized or empty. To resolve, resynchronize the PRAM in the card. See the Getting Started User’s Guide for CBX 3500, CBX 500, GX 550, and B-STDX 9000 for more information.

32 0 Fatal SRAM code space corrupted. Call the TAC.

33 0 Fatal IRAM code space corrupted. Call the TAC.

34* 0 Fatal 960 fault 0. Call the TAC.

34* 0 Non-Fatal Indicates requested calling party soft permanent virtual path connection (SPVPC) or soft permanent virtual channel connection (SPVCC) is not available.











Major Error

Minor Error

Status Explanation




45* 0 Fatal Bus Error (3000/6000). Call the TAC.

46 0 Fatal Parity error – IRAM (3000/6000). Call the TAC.

47 0 Fatal Parity error – FMEM (3000/6000). Call the TAC.

48 0 Fatal FMEM self test failure. Call the TAC.

49 0 Fatal Initialization error – device tables (3000/6000). Call the TAC.

50 0 Fatal Initialization error – bd out heap (3000/6000). Call the TAC.

51 0 Fatal Initialization error – bd in heap (3000/6000). Call the TAC.

52 0 Fatal Initialization error – bd initialization (3000/6000). Call the TAC.

53 0 Fatal Ethernet driver error. Call the TAC.

55 0 Fatal Ethernet driver error. Call the TAC.

56 0 Fatal Fatal internal error. This code is generic for errors not covered by any other errors in this table. Call the TAC.

57 0 Fatal Obsolete.

58 0 Fatal Circular virtual circuit list on the rate enforcement queue. Call the TAC.

59 0 Fatal Obsolete.

74* 0 Non-Fatal Indicates invalid information element contents.

75* 0 Non-Fatal Indicates requested calling party SPVPC or SPVCC is not available.

76* 0 Non-Fatal Indicates an unsupported combination of traffic parameters has been supplied.

77* 0 Non-Fatal Indicates a mandatory information element is missing.

78* 0 Non-Fatal Indicates incorrect message length.


Major Error

Minor Error

Status Explanation




79* 0 Non-Fatal Indicates requested VPI/VCI is not available.

80* 0 Non-Fatal Indicates no circuit or channel is available.

81* 0 Non-Fatal Indicates bearer capability not presently available.

82* 0 Non-Fatal Indicates bearer capability is not implemented.

83* 0 Non-Fatal Indicates incompatible destination.

84* 0 Non-Fatal Indicates resources unavailable, unspecified reason.

128 0 Fatal Cannot download bus. Call the TAC.

129 0 Fatal Warm boot. Call the TAC.

130 0 Fatal Cold boot. Call the TAC.

132 0 Fatal The standby side of a redundant pair is shooting the active side. Call the TAC.

133 0 Non-Fatal The PRAM is in conflict; PRAM is configured for another node. Each node has a unique ID. A card configured for one switch is now in use in a different switch.

To resolve, resynchronize the PRAM in the card. See the Getting Started User’s Guide for CBX 3500, CBX 500, GX 550, and B-STDX 9000.

134 0 Non-Fatal The Admin Status of a card is set to Down. A card that has its Admin Status set to Down is not an operational card.

To resolve, reactivate the card by setting the Admin Status field to Up on the Modify Logical Port dialog box. See the Getting Started User’s Guide for CBX 3500, CBX 500, GX 550, and B-STDX 9000 for more information.

135 0 Non-Fatal Unused.

136 0 Fatal The NMS caused a redundant switchover. This is a normal NMS procedure.

137 See Explanation

Fatal Illegal interrupt vector. This condition could be caused by either a software or hardware problem. The minor error number specifies the vector code. Call the TAC.


Major Error

Minor Error

Status Explanation



138 0 Fatal Proxy message from the wrong card. Call the TAC.

144 0 Non-Fatal A standby card is using a different version of the software. This error code indicates that the software revisions on the standby and active cards do not match. This is a warning condition and will not cause an interrupt in service. However, if you have to switch to the standby card, the older software revision may not support some features you are using on the active card. To resolve, update the standby card with the new software.

145 0 Fatal IOM configured for MULTI. Call the TAC.

146 0 Fatal Card service change. Call the TAC.

147 0 Fatal Some I/O to PRAM failed. Call the TAC.

148 0 Fatal One of the processor modules in a redundant pair of processor modules is incapable of the requested admin capability. Call the TAC.

149 0 Non-Fatal A standby processor module card type is incapable of a requested administrative task. This error code indicates that the standby model type does not match the active model type. This is a warning condition and will not interrupt service. However, if you have to switch to the standby model type, the older version may not support some features you are using on the active type.

To resolve, replace the standby processor module card type so that it matches the active processor module type.

149 1 Non-Fatal A standby processor module type is incapable of a requested admin capability, however, the system allowed the admin change to be made. This warning condition will not interrupt service. However, if you have to switch to the standby processor module card type, the older version may not support some features that you are using on the active card.

To resolve, replace the standby processor module so that it matches the active processor module.


Major Error

Minor Error

Status Explanation




149 2 Non-Fatal A standby processor module card type is incapable of a requested admin capability or SNMP set specified an invalid type. This condition is a warning condition and will not cause an interrupt in service. However, if you have to switch to the standby processor module card type, the older version may not support some features that you are using on the active card type.

To resolve, replace the standby processor module so that it matches the active processor module.

149 3 Non-Fatal The active IOM cannot perform a requested operation capability. For example, an SMDS request could have been made for a card that is for Frame Relay only.

To resolve, replace the IOM with the correct card type.

149 4 Non-Fatal The standby IOM cannot perform a requested operation capability.

To resolve, replace the standby card with the correct card type at your earliest convenience.

150 1 Fatal OSPF error – RTR Link State Address (LSA) is too big. Call the TAC.

150 2 Fatal OSPF error – No LSA in the age bin. Call the TAC.

150 3 Fatal OSPF error – Link State (LS) database is corrupted. Call the TAC.

150 4 Fatal OSPF error – Bad LSA in NBR queue. Call the TAC.

150 5 Fatal OSPF error – Bad LSA in NBR2 queue. Call the TAC.

150 6 Fatal OSPF error – LSA not found. Call the TAC.

150 7 Fatal OSPF error – NBR not found. Call the TAC.

150 8 Fatal OSPF error – Error in timer queue. Call the TAC.

150 9 Fatal OSPF error – Bad LSA in send Link State Uppath (LSU). Call the TAC.

150 10 Fatal OSPF error – Duplicate Autonomous System Entry (ASE). Call the TAC.


Major Error

Minor Error

Status Explanation



150 11 Fatal OSPF error – No areas. Call the TAC.

150 12 Fatal OSPF error – Bad VL. Call the TAC.

150 13 Fatal OSPF error – No BB Ifs. Call the TAC.

150 14 Fatal OSPF error – No BB. Call the TAC.

150 15 Fatal OSPF error – No memory. Call the TAC.

150 16 Fatal OSPF error – Bad receive packet. Call the TAC.

151 1 Fatal OSPF error – Console logging errors. Call the TAC.

152 0 Fatal Permanent Virtual Circuit (PVC) manager errors. Call the TAC.

153 0 Non-Fatal Virtual circuit table errors; buffer limit reached. There are too many PVCs defined between two logical ports.

To resolve, check the network configuration and reroute some PVCs. See the Frame Relay Services Configuration Guide for CBX 3500, CBX 500, and B-STDX 9000 or the ATM Services Configuration Guide for CBX 3500, CBX 500, GX 550, and B-STDX 9000 for more information about how to configure PVCs.

154 1 Fatal Fatal internal error. Call the TAC.

154 2 Fatal The card cannot read the configuration. Call the TAC.

155 See Explanation

Fatal Memory protection NMI. Either two processes tried to write to the same memory location at the same time or a process tried to read uninitialized memory. Call the TAC.

156 See Explanation

Non-Fatal Congestion thresholds that have been specified are invalid.

157 See Explanation

Fatal SAR chip HW error. These chips provide VC and VP shaping capabilities on ATM IWU and ATM CS modules. Call the TAC.


Major Error

Minor Error

Status Explanation




158 0 Non-Fatal System timing reference problem.

To resolve, check the source for the system timing reference (see “Viewing System-Timing Options” on page 2-62). Make sure the timing source is properly configured and functional.

If you cannot resolve the problem, contact the TAC for assistance.

159 See Explanation

Non-Fatal SNMP errors, such as an object identifier (OID) length of zero.

160 See Explanation

Non-Fatal Label switched path (LSP) errors.

Note: LSPs were formerly known as MPTs.

161 See Explanation

Non-Fatal PNNI errors.

162 See Explanation

Non-Fatal Signaling errors.

163 See Explanation

Non-Fatal Invalid traffic class setting.

164 See Explanation

Non-Fatal Disk error detected by scandisk.

165 See Explanation

Non-Fatal Software manager errors.

172 1 Non-Fatal The module successfully completed the Rapid Upgrade.

172 2 Non-Fatal You have attempted to use the Rapid Upgrade feature with an unsupported module on the switch. For this reason, a cold boot was issued after download of the code to this unsupported module.

172 3 Non-Fatal The bootflash code download failed.

172 4 Non-Fatal The application code download failed.

172 5 Non-Fatal The system was not able to read an application code file.

172 6 Non-Fatal The system could not load the fast loader. The fast loader is the module that overwrites the old application code with the new application code.


Major Error

Minor Error

Status Explanation



172 7 Non-Fatal The save state failed.

172 8 Non-Fatal A module time-out occurred.

172 9 Non-Fatal The standby module was automatically cold booted as part of the normal rapid upgrade process.

172 10 Non-Fatal Downgrade not supported.

254* 0 Non-Fatal Indicates no circuit or channel is available.

Table B-2. Summary of Miscellaneous Fatal Error Codes

Major Error

Minor Error

Status Explanation

3.2 See Explanation

Fatal When this error appears on a processor module, it indicates a warm boot has occurred. This is an informational error message and it requires no intervention.

4 See Explanation

Fatal Indicates chain corruption in a memory block. Call the TAC for assistance.

5 See Explanation

Fatal Indicates a fatal error that you cannot resolve without assistance. Call the TAC.


Major Error

Minor Error

Status Explanation




Switch Diagnostics User’s Guide for CBX 3500, CBX 500, GX 550, and B-STDX 9000 C-1


C

Using SVC Failure Information

This appendix describes how to use SVC failure location information displayed in the failure location and failure cause fields on the Detailed Failed SVC Attributes dialog box for failed SVCs (see “Viewing SVC Failed Calls” on page 11-19).

About SVC Cause Codes

For failed ATM SVCs, the Show Failed Call Attributes dialog box displays the reason for the SVC failure using the ATM Forum UNI 3.0/3.1/4.0 standard cause codes, and the location where the failure occurred.

For failed Frame Relay SVCs, the Show Failed Call Attributes dialog box displays the reason for the SVC failure using the Frame Relay Forum FRF.4 standard cause codes, and the location where the failure occurred.

Table C-1 describes the failure cause codes and the standards documents that you should reference for further information. The ATM Forum UNI and Frame Relay Forum FRF.4 standards use many (but not all) of the same cause codes. The ATM UNI and Frame Relay Forum FRF.4 standards documents reference ITU standards documents for many of the cause codes.


C-210/7/05 Switch Diagnostics User’s Guide for CBX 3500, CBX 500, GX 550, and B-STDX 9000

Using SVC Failure InformationAbout SVC Cause Codes

Table C-1. SVC Setup Failure Causes

Cause Description See

unalloc-nmb (1) Unallocated (unassigned) number. The called party number is not currently assigned. As a result, the called party cannot be reached.

ITU Q.850

no-route-transnet (2) No route to transit network. The equipment sending this cause received a request to route the call through an unknown transit network. The transit network is unknown to the equipment because it does not exist or does not serve the equipment.

ITU Q.850

no-route-dest (3) No route to destination. The network through which the call was routed does not serve the destination. As a result, the called party cannot be reached.

ITU Q.850

vcc-unacceptable-30 (10) VPI/VCI is unacceptable to the sending entity for use in the call.

ATM Forum UNI 3.0/3.1

normal-call-clr-31 (16) Normal call clearing. ITU Q.850

user-busy (17) User is busy. The called party is unable to accept another call because the user busy condition has been encountered.

ITU Q.850

no-user-response (18) No user response. A called party did not respond to a call establishment message with either an alerting or connect indication within a designated time period.

ITU Q.850

call-reject (21) Call has been rejected. Although the equipment sending this cause is neither busy nor incompatible, the equipment sending this cause does not want to accept the call. The cause can be generated by the network to indicate that the call may have been cleared as a result of a supplementary service constraint.

ITU Q.850

nmb-changed (22) Number has changed. The number of the called party is no longer assigned. A new number must be used to call the called party.

ITU Q.850

call-reject-clir (23) User rejects all calls with CLIR (calling line identification restriction). The called party returns this cause code when the call comes in without calling party number information and the called party requires this information.


Beta Draft Confidential Using SVC Failure InformationAbout SVC Cause Codes

Switch Diagnostics User’s Guide for CBX 3500, CBX 500, GX 550, and B-STDX 9000 10/7/05C-3

dest-out-of-order (27) Destination is out of order. The user cannot reach it because the interface to the destination is not functioning properly (that is, a signaling message could not be delivered to the destination).

ITU Q.850

invalid-nmb-format (28) Invalid number format. The called party is unreachable because the number of the called party is not in the proper format or it is incomplete.

ITU Q.850

response-stat-enq (30) Response to STATUS ENQUIRY. A STATUS message was sent in response to receipt of a STATUS ENQUIRY message.

ITU Q.850

normal-unspecified (31) Normal unspecified. A normal event occurred for which no other cause applies. As a result, the event is normal, but unspecified.

ITU Q.850

pending-add-party (32) Too many pending ADD PARTY requests. ATM Forum PNNI 1.0

req-vcc-unavailable (35) Requested virtual path connection identifier (VPCI)/VCI is unavailable. The ATM SVC attempted to use a VPCI/VCI that is unavailable.

ITU Q.2610

vcc-fail-31 (36) VPCI/VCI assignment failure. A VPCI/VCI could not be assigned to the ATM SVC.

ITU Q.2610

rate-unavail-31 (37) User cell rate is unavailable. The requested cell rate is unavailable for the ATM SVC.

ITU Q.2610

network-out-of-order (38)

Network is out of order. The problem will probably last a long period of time (that is, an immediate retry of the call is not likely to succeed).

ITU Q.850

temp-fail (41) Temporary failure. The problem will probably last a short period of time (that is, an immediate retry of the call has a good chance to succeed).

ITU Q.850

access-info-discard (43) Access information has been discarded. The network failed to deliver access information (for example, user-to-user, low-layer compatibility, high-layer compatibility, or sub-address) to the remote user.

ITU Q.850

circuit-unavailable (44) Requested circuit/channel is not available. ITU Q.850

Table C-1. SVC Setup Failure Causes (Continued)





no-vcc-available (45) No VPCI/VCI is available. A VPCI/VCI is not available for the ATM SVC.

ITU Q.2610

resources-unavailable (47)

Resources are unavailable/unspecified. A resource is unavailable, and no other cause exists to report this event.

ITU Q.850

qos-unavailable (49) Quality of Service is unavailable. The requested QoS class is unavailable for the SVC.

ITU Q.850

rate-unavailable-30 (51) User cell rate is unavailable. The requested cell rate is unavailable for the ATM SVC.


PGL-change (53) Call cleared due to change in Peer Group Leader (PGL).

ATM Forum PNNI 1.0

b-cap-not-authorized (57)

Bearer capability is not authorized. The SVC user requested a bearer capability for which the user is not authorized.

ITU Q.850

b-cap-unavailable (58) Bearer capability is not available. The SVC user requested a bearer capability that is not available at this time.

ITU Q.850

service-unavailable (63) Service or option is unavailable. A service or option is unavailable, and no other cause code exists to report this event.

ITU Q.850

b-cap-not-implemented (65)

Bearer capability is not implemented. The equipment that generates this cause does not support the requested bearer capability.

ITU Q.850

combination-unsupported (73)

Unsupported combination of traffic parameters.


aal-params-unsupp-31 (78)

ATM Adaptation Layer (AAL) parameters cannot be supported.

ITU Q.2610

invalid-call-reference (81)

Invalid call reference. The equipment that sends this cause has received a message with a call reference that is not currently in use on the user-network interface.

ITU Q.850



Beta Draft Confidential Using SVC Failure InformationAbout SVC Cause Codes


no-channel (82) Identified channel does not exist. The equipment sending this cause received a request to use a channel that was not activated on the call interface. For example, if a user subscribed to those channels on a primary rate interface numbered from 1 to 12, this cause would be generated if the user equipment or the network attempts to use channels 13 through 23.

ITU Q.850

dest-incompatible (88) Incompatible destination. The equipment sending this cause received a request to establish a call with low-layer compatibility, high-layer compatibility, or other compatibility attributes (for example, data rate) that cannot be accommodated.

ITU Q.850

invalid-endpoint-ref (89) Invalid endpoint reference. The equipment sending this cause received a message with an endpoint reference that is currently not in use on the user-network interface.


invalid-transit-net (91) Invalid transit network selection. A transit network identification was received that is formatted incorrectly. Correct formats are defined by Annex C in the Q.931 standard.

ITU Q.850

too-many-add-pty-req (92)

Too many ADD PTY requests were generated on the SVC. This condition occurs when the calling party sends an ADD PTY request, but the network cannot accept another ADD PTY message because its queues are full. This is a temporary condition.


aal-params-unsupp-30 (93)

AAL parameters cannot be supported. ITU Q.2610

invalid-message (95) Invalid message, unspecified. This cause reports an invalid message event when no other invalid message cause applies.

ITU Q.850

info-element-missing (96)

Mandatory information element is missing. The equipment sending the cause received a message that is missing a mandatory information element.

ITU Q.850






msg-type-not-imp (97) Message type is not implemented. The equipment sending the cause received a message of one of the following message types:

• Not defined

• Defined but not implemented by the equipment sending the cause

ITU Q.850

info-element-not-imp (99)

Information element is not implemented. The equipment sending the cause received a message that includes information elements or parameters that meet one of the following criteria:

• Not recognized because they are not defined

• Defined but not implemented by the equipment sending the cause

The cause indicates that the elements or parameters were discarded. However, the information element is not required to be present in the message for the equipment sending the cause to process the message.

ITU Q.850

invalid-info-element (100)

Invalid information element. The equipment sending this cause received an information element that it has implemented, but one or more fields in the information element are coded in a way that has not been implemented.

ITU Q.850

message-not-compatible (101)

Message type is not compatible with call. A message was received that is incompatible with the call state.

ITU Q.850

timer-recovery (102) Recovery on timer expiration. A procedure has been initiated by the expiration of a timer that is related to error handling procedures.

ITU Q.850

invalid-message-len (104)

Incorrect message length. ATM Forum UNI 3.0/3.1

protocol-error (111) Unspecified protocol error. A protocol error occurred for which there is no defined protocol error.

ITU Q.850



Beta Draft Confidential Using SVC Failure InformationExample


Example

This section describes the usage of cause codes. The following example uses ATM SVCs that connect CBX 500 switches and campus networks.

Using the sample network shown in Figure C-1, the CBX 500 switches are deployed in a UNI signaling environment where Links A-D are running UNI signaling. The majority of UNI signaling activity involves users (workstation and routers) at Campus ATM Network #1 using SVCs to establish ATM connectivity with users at Campus ATM Network #2. If one of these SVC attempts fail, the CBX 500 records the event.

Figure C-1. Transit ATM Network

Table C-2 describes the failure conditions that may occur and displays failed SVC information (see Figure 11-26 on page 11-21). The information in Table C-2 uses the sample network shown in Figure C-1 as an example. All SVC attempts described in this table are from Campus Network 1 to Campus Network 2.

optional-element-error (127)

Optional information element content error (non-standard). This cause indicates the occurrence of internetworking with a network that does not provide causes for actions it takes. The precise cause for any message that is sent cannot be ascertained.

ITU Q.850

no-route-next-node (128) Next node unreachable. ATM Forum PNNI 1.0

dtl-not-my-node (160) Designated transit list (DTL) Transit not my node ID.

ATM Forum PNNI 1.0



Campus ATM Network #1


CBX 500Network #1

CBX 500Network #2

Transit ATM Network

LPort

LPort LPort C

LPort D

Link A

Link B Link C

Link D



Using SVC Failure InformationExample

The following abbreviations are used in the table:

• Loc = the switch/LPort reported in the SVC Failure Location fields.

• No entry = no SVC failure reported at this LPort.

• Rel = whether the RELEASE was received (rx) on the logical port or transmitted (tx) by the logical port.

The public/private network indication is extracted from the release message that is either transmitted by the CBX 500 or received by the CBX 500. You should consider the following when you use the SVC failure location information:

• If the release message is transmitted by the CBX 500, the CBX 500 inserts “public” or “private” based on the LPort setting (for DCE LPorts).

• If the release message is received by the CBX 500, the information inserted by the other switch is used in the SVC failure location field.

Table C-2. SVC Failure Location Information for Sample Transit Network

Failure Type

Failure Location Entry At:

NotesLPort A LPort B LPort C LPort D

Link A down No entry No entry No entry No entry Link A is down – call never reaches CBX 500 #1.

Link B down Loc=ARel=tx

No entry No entry No entry Link B is down – routing never sends attempt to B. Failure is only reported at A.

Link C down Loc=BRel=tx

Loc=BRel=rx

No entry No entry Link C is down – SVC attempts sent to transit network but release is returned from transit network.

Link D down Loc=BRel=tx

Loc=BRel=rx

Loc=CRel=tx

No entry Link D is down – SVC attempt is sent to transit network but release is returned from CBX 500 #2 and passed back to CBX 500 #1 via transit network.

Called party user down at Campus 2

Loc=BRel=tx

Loc=BRel=rx

Loc=DRel=tx

Loc=DRel=rx

Release is received from Campus 2 and forwarded back to CBX 500 #2, transit, CBX 500 #1.

Beta Draft Confidential Using SVC Failure InformationExample


In general, different switches exhibit different behavior in this area. For this reason, it is difficult to use public/private as a true indication of where the failure occurs.

The configuration shown in Figure C-1 on page C-7 uses a transit network between two CBX 500 networks. In this configuration, troubleshooting is more difficult. The SVC failure location information shown in Figure C-2 is more useful because SVC information can be shared between the two networks (over the direct or OPTimum trunks). This is not the case when a UNI interface exists between the two networks.

Figure C-2. Two CBX 500 Networks (Direct or OPTimum Trunk)

Table C-3 describes the failure conditions that may occur (using the example in Figure C-2) and displays the Show All Failed SVC log information. All SVC attempts described in this table are from Campus Network 1 to Campus Network 2.

Table C-3. SVC Failure Location Information for All CBX 500 Scenarios

Failure Type


NotesLPort A LPort B LPort C

Link A down

No entry Failure info only provided on UNI ports (not trunk ports)

No entry Link A is down – call never reaches CBX 500 #1.

Link B down

Loc=ARel=tx

Failure info only provided on UNI ports (not trunk ports)

No entry Link B is down – routing never sends attempt to B. Failure is only reported at A.

Link C down

Loc=BRel=tx


No entry Link C is down – routing never sends attempt to B, so failure is only reported at A.



CBX 500Network #1

CBX 500Network #2

(Direct or OPTimum Trunk)

LPort LPorts B

Link CLink A

Link B



Using SVC Failure InformationExample

Called party user down at Campus 2

Loc=BRel=tx


Loc=DRel=tx

Release is received from Campus 2 and forwarded back to CBX #2 and CBX #1.

Table C-3. SVC Failure Location Information for All CBX 500 Scenarios (Continued)

Failure Type


NotesLPort A LPort B LPort C

Switch Diagnostics User’s Guide for CBX 3500, CBX 500, GX 550, and B-STDX 9000 D-1


D

Signalled QoS, BBC, ATC, and BEI Service Category Mappings

This appendix describes how the CBX 500 switch, CBX 3500 switch, and GX 550 switch map ATM Forum Quality of Service (QoS) classes, Broadband Bearer Classes (BBC), ATM Transfer Capability (ATC), and the Best Effort Indicator (BEI) to the CBX 500/3500 and GX 550 service categories.

QoS service classes are designed to accommodate the various types of traffic, such as video and LAN traffic, in the network. These classes include Constant Bit Rate (CBR), Variable Bit Rate Real-Time (VBR-RT), Variable Bit Rate Non-Real-Time (VBR-NRT), Available Bit Rate (ABR), and Unspecified Bit Rate (UBR). See “Definition of Specified QoS Classes” on page D-2 for more information on these classes.

When PVCs are provisioned, the CBX 500/3500 or GX 550 service class is selected by the operator as part of the provisioning process.

For SVCs that use ATM UNI 3.0/3.1 and Q.2931 signalling, the CBX 500/3500 or GX 550 selects the service class, based on the QoS, BBC, and BEI contained in the received UNI Signalling SETUP message. If the QoS class is unspecified, the BBC and BEI provide information that allow the service provider (that is, the CBX 500/3500 or GX 550) to select the appropriate QoS class.

Note – ATC applies to ATM UNI 4.0 signalling and PNNI 1.0 signalling only.

ATM UNI 4.0/PNNI 1.0 signalling is a superset of ATM UNI 3.0/3.1 signalling. Unless otherwise noted, the signalling-related information in this appendix applies to all signalling variants.


D-210/7/05 Switch Diagnostics User’s Guide for CBX 3500, CBX 500, GX 550, and B-STDX 9000

Signalled QoS, BBC, ATC, and BEI Service Category MappingsDefinition of Specified QoS Classes

For SVCs that use ATM UNI 4.0 or PNNI 1.0 signalling, the CBX 500/3500 or GX 550 selects the service category, based on the QoS, BBC (which contains the ATC), and BEI contained in the received UNI Signalling SETUP message. If the QoS class is unspecified, the BBC and the ATC/BEI combination provide information that allow the service provider (that is, the CBX 500/3500 or GX 550) to select the appropriate QoS class.

This appendix references specific sections from the ATM Forum’s UNI Appendix A specifications (3.0 and 3.1) and from the ATM Forum’s UNI Signalling Specification Version 4.0. For detailed information on the QoS, BBC, and BEI role in ATM UNI 3.0/3.1, see the ATM Forum’s UNI Appendix A specifications (3.0 and 3.1). For detailed information on the QoS, BBC, ATC and BEI role in ATM UNI 4.0, see the ATM Forum’s UNI Signalling Specification Version 4.0.

Definition of Specified QoS Classes

From ATMF UNI 3.1 Appendix A, Section A.4.1:

This section describes the ATM Forum’s definition of the specified QoS classes. It is helpful to review these definitions to understand how the CBX 500/3500 and GX 550 map ATMF QoS elements. The following text is an excerpt from ATMF UNI 3.1 Appendix A, Section A.4.1. Comments specific to the CBX 500/3500 and GX 550 are noted in italics.

A specified QoS class provides a quality of service to an ATM virtual connection (VCC or VPC) in terms of a subset of the ATM performance parameters defined in section 3 of ATMF UNI 3.1 Appendix A. For each Specified QoS class, there is one specified objective value for each performance parameter identified as defined in section 3 of ATMF UNI 3.1 Appendix A.

Initially, each network provider should define objective values for a subset of the ATM performance parameters of section 3 for at least one of the following Service Classes from ITU-T recommendation I.362 in a reference configuration that may depend on mileage and other factors:

• Service Class A — Circuit Emulation, Constant Bit Rate Video (CBX 500/CBX 3500/GX 550 CBR service category).

• Service Class B — Variable Bit Rate Audio and Video (CBX 500/CBX 3500/GX 550 VBR-RT service category).

• Service Class C — Connection-Oriented Data Transfer (CBX 500/CBX 3500/GX 550 VBR-NRT service category).

• Service Class D — Connectionless Data Transfer (CBX 500/CBX 3500/GX 550 ABR/UBR service category).

• In the future, more ‘QoS Classes’ may be defined for a given ‘Service Class’ described above. The following Specified QoS Classes are currently defined:

Beta Draft ConfidentialSignalled QoS, BBC, ATC, and BEI Service Category MappingsDefinition of Specified QoS Classes

Switch Diagnostics User’s Guide for CBX 3500, CBX 500, GX 550, and B-STDX 9000 10/7/05D-3

• Specified QoS Class 1 — Support a QoS that will meet Service Class A performance requirements.

• Specified QoS Class 2 — Support a QoS that will meet Service Class B performance requirements.

• Specified QoS Class 3 — Support a QoS that will meet Service Class C performance requirements.

• Specified QoS Class 4 — Support a QoS that will meet Service Class D performance requirements.

The specified QoS Class 1 should yield performance comparable to current digital private line performance. Specified QoS Class 2 is intended for packetized video and audio in teleconferencing and multi-media applications. Specified QoS Class 3 is intended for interoperation of connection oriented protocols, such as Frame Relay. Specified QoS Class 4 is intended for interoperation of connectionless protocols, such as IP or SMDS.

You may configure the same performance for all, or a subset of specified QoS classes, provided the requirements of the most stringent Service Class are met. (The CBX 500/CBX 3500/GX 550 provides a separate service category for each of the specified QoS classes.)

For example, assuming the SVC SETUP message contains the proper combination and structure, the following guidelines apply:

• A signalled QoS class of 1 will result in a CBX 500/CBX 3500/GX 550 service category of CBR.

• A signalled QoS class of 2 will result in a CBX 500/CBX 3500/GX 550 service category of VBR-RT.

• A signalled QoS class of 3 will result in a CBX 500/CBX 3500/GX 550 service category of VBR-NRT.

• A signalled QoS class of 4 will result in a CBX 500/CBX 3500/GX 550 service category of UBR.



Signalled QoS, BBC, ATC, and BEI Service Category MappingsDefinition of Unspecified QoS Class

Definition of Unspecified QoS Class

The unspecified QoS class requires special handling by the CBX 500/3500 and GX 550 because the ATMF Unspecified QoS does not directly map to any specific service category. This is reinforced in the following excerpts from ATMF UNI 3.1 Appendix A, Section A.4.2. Comments specific to the CBX 500/3500 and GX 550 are noted in italics.

In the unspecified QoS class, no objective is specified for the performance parameters. However, the network provider may determine a set of internal objectives for the performance parameters. In fact, these internal performance parameter objectives need not be constant during the duration of a call. Thus, for the Unspecified QoS class there is no explicitly specified QoS commitment on either the CLP=0 or the CLP=1 cell flow.

Services using the unspecified QoS class may have explicitly specified traffic parameters. This means the “network provider” (or the CBX 500/CBX 3500/GX 550) has several options for handling unspecified QoS. For ATM UNI 3.1, this involves the role of the BBC and BEI. For ATM UNI 4.0, this involves the role of the BBC, ATC, and the BEI.

An example application of the unspecified QoS class is the support of “best effort” service. For this type of service, the user selects the Best-Effort Capability, the Unspecified QoS class and only the traffic parameter for the Peak Cell Rate on CLP=0+1. As indicated in Section 3.6.2.4, this capability can be used to support users that are capable of regulating the traffic flow into the network and to adapt to time-variable available resources. (The Unspecified QoS class with a signalled Best Effort traffic descriptor is the type of service requested by the majority of ATM SVC capable CPE. This maps directly to the CBX 500/CBX 3500/GX 550 UBR service category.)

The unspecified QoS class is identified by the integer zero (0) in the ILMI MIB or a code point in a signalling message for the requested QoS class. (This is why unspecified QoS class is also called QoS class zero (0.)

Using unspecified QoS, the CBX 500/3500 and GX 550 use the BBC information element and the presence (or non presence) of the BEI to determine what service category should be used for the SVC. For a detailed description of each BBC, see the ATM Forum UNI specifications.

Beta Draft ConfidentialSignalled QoS, BBC, ATC, and BEI Service Category MappingsSupport of Class X, Class A, and Class C ATM Transport Services


Support of Class X, Class A, and Class C ATM Transport Services

For ATM UNI 3.0/3.1 signalling and Q.2931 signalling, when dealing with unspecified QoS, the CBX 500/3500 and GX 550 use the BBC information and the presence of (or lack of) the BEI as a means of determining what service category should be used for the SVC. The ATMF UNI 3.1 specification also provides information on each BBC meaning.

For ATM UNI 4.0 signalling, when dealing with unspecified QoS, the CBX 500/3500 and GX 550 use the following elements as a means of determining what service category should be used for the SVC:

• Broadband Bearer Class (BBC) in octet 5 of the Broadband bearer capability information element.

• The value of the ATC, if present, and the absence or presence of the BEI in octet 18 of the ATM Traffic Descriptor information element.

The following ATMF excerpts from ATM Forum UNI 3.1 Chapter 5, Section 5.1.2.6 describe the Broadband Bearer Class in greater detail.

Class X service is a connection-oriented ATM transport service where the ATM Adaptation Layer (AAL), traffic type (VBR or CBR) and timing requirements are user defined (that is, transparent to the network). The user chooses only the desired bandwidth and QoS with appropriate information elements in a SETUP message to establish a class X connection.

Class A service is a connection-oriented, constant bit rate ATM transport service. Class A service has end-to-end timing requirements. Class A service may require stringent cell loss, cell delay, and cell delay variation performance. The user chooses the desired bandwidth and the appropriate QoS in the SETUP message to establish a Class A connection.

Class C service is a connection-oriented, variable bit rate ATM transport service. Class C service has no end-to-end timing requirements. The user chooses the desired bandwidth and QoS with appropriate information elements in a SETUP message to establish a class C connection.

The Phase 1 Signalling specified in this document supports Class X, Class A, and Class C service. Class D service is not directly supported by signalling. It can be supported via a Class X or Class C connection to a connectionless server.

The ATMF specifications do not directly indicate how a network provider (that is, Lucent) should map BBC to service category. In switch software Release 1.1.x (and previous releases), the CBX 500/3500 and GX 550 always mapped unspecified QoS to the UBR service category, regardless of the BBC. In switch software Release 1.2.1 (and future releases), changes were made to utilize the BBC when deciding which service category to map to unspecified QoS.



Signalled QoS, BBC, ATC, and BEI Service Category MappingsSupport of Class X, Class A, and Class C ATM Transport Services

The specific mappings were made as a result of the ATMF guidelines and customer requirements. Because the BBC information element also contains traffic type and timing requirement fields, it is difficult to make general statements about which BBC maps to which CBX 500/CBX 3500/GX 550 service category. Instead, it is important to reference ATMF UNI 3.1 Appendix F or Annex 9 of the ATM Forum’s UNI Signalling Specification Version 4.0. Appendix F and Annex 9 list several guidelines and describe the valid combinations of BBC and QoS for ATM UNI 3.0/3.1 and Q.2931 signalling and ATM UNI 4.0 signalling. Excerpts of this appendix and this annex are provided in the following section.

Guidelines on Use of Bearer Class, Traffic Parameters, and QoS

From ATMF UNI 4.0 Signalling Annex 9:

The following are brief descriptions of the various BCOB classes in the Bearer capability information element (see ITU-T Recommendation F.811 for additional information).

BCOB-A (ATMF UNI 4.0 Section A9.1.1)

This class is only used for requesting a virtual channel service. When the user specifies BCOB-A, the user is requesting more than an ATM-only service. The network may look at the AAL information element to provide interworking based upon its contents. One example of such interworking would be between an ATM user calling a non-ATM user who has switched DS1 capability. In this case, the network interworking function would need to know the AAL used to be able to perform this interworking function.

BCOB-C (ATMF UNI 4.0 Section A9.1.2)

This class is only used for requesting a virtual channel service. As for BCOB-A, when the user specifies BCOB-C, the user is requesting more than an ATM only service. The network may look at the AAL information element to provide internetworking based upon its contents.

Note – Corresponding descriptions in ATM UNI 3.1 Appendix F are almost identical.



BCOB-X (ATMF UNI 4.0 Section A9.1.3)

This class is only used for requesting a virtual channel service. When the user specifies BCOB-X, the user is requesting an ATM-only service from the network. In this case, the network shall not process any higher layer protocols (for example, AAL protocols).

The difference between BCOB-X and the other classes is what service is being requested from the network. For the VBR user that wants only a ATM cell relay service (CRS), the user should specify BCOB-X and Traffic Type VBR.

A user who is placing a DS1 circuit emulation call (but does not want to allow interworking) should specify BCOB-X and Traffic Type CBR. If the user wishes to allow interworking, then the user should specify BCOB-A.

Transparent VP Service (ATMF UNI 4.0 Section A9.1.4)

When the user specifies Transparent VP Service, the user is requesting an ATM-only service from the network. This service offers BCOB-X in that with the Transparent VP Service, both the VCI field (except for VCI values 0, 3, 4, and 6 through 15) and the Payload Type field will be transported transparently by the network.

Note – Transparent VP Service applies to ATM UNI 4.0 and PNNI 1.0 only.




Allowed Combination of Bearer Capabilities, Traffic Parameters, and QoS in ATM UNI 3.0/3.1 and Q.2931

From Section F.2:

The parameters specified in the Broadband Bearer Capability IE, the Traffic Descriptor IE, and the Quality of Service Parameters information element (IE) of the SETUP message should be consistent. Table D-1 shows the allowable combinations of the Broadband Bearer Capability classes, the Traffic Descriptor parameters and the Quality of Service classes based on tables 5-7 and 5-8. If an illegal combination of parameters is specified, the call should be cleared with cause #63 “service or option not available, unspecified.”

Table D-1 (from Table F-1 in ATMF UNI 3.1) uses the following entries:

• PCR = Peak Cell Rate, SCR = Sustainable Cell Rate, MBS = Maximum Burst Size

• Y = Yes, N = No, S= Specified

• Y/N = either Yes or No is allowed.

• * = allowed QoS class values are a network option. Class zero (0) is always supported for alignment with ITU-T.

• & = parameter is coded to either “No indication” or “VBR” or octet 5a (Traffic Type/Timing Required) is absent; these three codings are treated as equivalent.

• && = parameter is coded to either “No indication” or “No” or octet 5a (Traffic Type / Timing Required) is absent; these three codings are treated as equivalent.

• A blank entry in the table indicates that the parameter is not present.



Table D-1. Allowable Combinations of Traffic Related Parameters inthe SETUP Message (ATM UNI 3.0/3.1 and Q.2931)

Broadband Bearer Capability

1 2 3 4 5 6 7 8 9 10 11 12

Broadband Bearer A,C X X C X C X A,C X X C X

Traffic Type CBR & & & CBR & &

Timing Required Y && && && Y && &&

Traffic Descriptor

PCR (CLP=0) S S S

PCR (CLP=0+1) S S S S S S S S S S S S

SCR (CLP=0) S S

SCR (CLP=0+1) S S

MBS (CLP=0) S S

MBS (CLP=0+1) S S

Best Effort S S

Tagging Y/N Y/N Y/N Y/N Y/N N N N N N N N

QoS Classes * * * * * * * * * * 0 0




Specific Service Category Mappings in ATM UNI 3.0/3.1 and Q.2931

To simplify the interpretation of the ATMF UNI 3.1 Appendix F specification and other ATMF UNI 3.1 specification excerpts in this appendix, Table D-2 simplifies the process of determining the specific CBX 500/CBX 3500/GX 550 service category mappings.

Table D-2 lists the CBX 500/CBX 3500/GX 550 service category for a number of QoS and BBC combinations. The table uses the following entries:

• BEI = NO indicates the BEI is not present.

• BEI = YES indicates the BEI is present.

• N/A indicates the parameter is either not applicable or not allowed.

• CC 63 indicates the CBX 500/3500 or GX 550 will reject the SVC with the cause code of 63 or “service or option not available, unspecified.”

The QoS information presented in this table (and in the Show All Failed SVCs dialog box) is the signalled QoS, not the actual service category. For signalled QoS classes 1 through 4, the mapping is clear. For unspecified QoS, you must look at the BBC contents and use Table D-2 to determine the actual service category. Although you can use the View QoS Parameters dialog box to determine the service category, the information on the dialog box may be difficult to interpret if many VCs exist on a logical port.



Table D-2. CBX 500/CBX 3500/GX 550 ATM UNI Service CategoryMappings Based on Signalled QoS/BBC and BEI

Table D-1 Column

QoS BBC BEI Traffic Type Timing Req. Service Category

Notes

1 0 A NO N/A N/A CBR x

1 0 C NO N/A N/A VBR-NRT x

1 1 A NO N/A N/A CBR x

1 1 C NO N/A N/A CBR x

1 2 A NO N/A N/A VBR-RT x

1 2 C NO N/A N/A VBR-RT x

1 3 A NO N/A N/A VBR-NRT x


1 4 A NO N/A N/A UBR x

1 4 C NO N/A N/A UBR x

2 0 X NO CBR e/e tmg req’d CBR x


2 2 X NO CBR e/e tmg req’d N/A CC 63



3 0 X NO No indication No indication VBR-NRT x

3 1 X NO No indication No indication N/A CC 63

3 2 X NO No indication No indication VBR-RT x


3 4 X NO No indication No indication UBR x

3 0 X NO VBR e/e tmg not req’d VBR-NRT x

3 1 X NO VBR e/e tmg not req’d N/A CC 63

3 2 X NO VBR e/e tmg not req’d VBR-RT x


3 4 X NO VBR e/e tmg not req’d UBR x
















5 2 X NO VBR e/e tmg not req’d VBR-RT xx













Table D-2. CBX 500/CBX 3500/GX 550 ATM UNI Service CategoryMappings Based on Signalled QoS/BBC and BEI (Continued)

Table D-1 Column


Notes





7 2 X NO VBR e/e tmg not req’d VBR-RT x



8 0 A NO No indication No indication CBR x

8 1 A NO No indication No indication CBR x

8 2 A NO No indication No indication VBR-RT x

8 3 A NO No indication No indication VBR-NRT x

8 4 A NO No indication No indication UBR x

8 0 C NO No indication No indication CBR x

8 1 C NO No indication No indication CBR x

8 2 C NO No indication No indication VBR-RT x

8 3 C NO No indication No indication VBR-NRT x

8 4 C NO No indication No indication UBR x

9 0 X NO CBR e/e tmg req’d CBR xx






10 1 C NO No indication No indication N/A CC 63

10 2 C NO No indication No indication VBR-RT x


10 4 C NO No indication No indication UBR x


Table D-1 Column


Notes




10 0 C NO VBR e/e tmg not req’d VBR-NRT x

10 1 C NO VBR e/e tmg not req’d N/A CC 63

10 2 C NO VBR e/e tmg not req’d VBR-RT x

10 3 C NO VBR e/e tmg not req’d VBR-NRT x

10 4 C NO VBR e/e tmg not req’d UBR x

11 0 C YES N/A N/A UBR x

11 1 C YES N/A N/A N/A CC 63




12 0 X YES No indication No indication UBR x

12 1 X YES No indication No indication N/A CC 63




12 0 X YES VBR e/e tmg not req’d UBR x

12 1 X YES VBR e/e tmg not req’d N/A CC 63





Table D-1 Column


Notes



Determination of ATM Service Category in ATM UNI 4.0/PNNI 1.0

From ATMF UNI 4.0 Signalling, Section A9.2:

The ATM service categories assigned to connections at UNI 4.0 and PNNI 1.0 are defined in the ATM Forum Traffic Management Specification, Version 4.0. An explicit way of requesting a particular ATM service category is provided in UNI 4.0 (and PNNI 1.0) signalling. Instead, the requested ATM service category must be derived from three pieces of information in a signalling message. The ATM service category is derived from:

1. The Broadband bearer class in octet 5 of the Broadband bearer capability (BBC) information element.

2. The absence or presence of the ATM transfer capability (ATC) octet (octet 5a) in the Broadband bearer capability information element.

3. The value of the ATC if present, and the absence or presence of the Best effort indicator in octet 18 of the ATM Traffic Descriptor information element.

The octet representing ATC has been changed from containing two relevant fields in UNI 3.x to a single field in UNI 4.0. The two fields in UNI 3.x were “Traffic Type” which indicated whether the traffic was CBR or VBR, and “Timing Requirements” which indicated whether end-to-end timing was required or not. In UNI 4.0, the entire octet 5a was changed to a single field and named the ATM Transfer Capability. To support backward compatibility, valid pairs of codepoint from the previous two fields were maintained and incorporated into single-field codepoints for ATC. In addition, new codepoints for the ATC have been defined.

Table D-3 summarizes the different combinations of Broadband bearer class, ATC, and BEI that define the ATM service categories. In addition, the table correlates the meaning of single-field ATC codepoints to the meanings that were interpreted previously by the two fields in octet 5a of the BBC information element in UNI 3.0/3.1.




Table D-3. Derivation of ATM Service Categories From Signalling Information (ATM UNI 4.0 and PNNI 1.0)

ASC (a)

BBC(b)

ATC(c)

BEI(d)

Equivalent UNI 3.0/3.1 Octet 5a Definitions

Comment

CBR A abs

No

Absent None

7 CBR traffic type, reserved timing requirement

New in UNI 4.0, invalid UNI 3.1 BBC octet 5a coding

X 4

No

CBR traffic type, timing not indicated None

5 CBR traffic type, end-to-end timing required

None

6 CBR traffic type, end-to-end timing not required

None



VP 5

No

CBR traffic type, end-to-end timing required

New in UNI 4.0



VBR-RT

C 9

No

VBR traffic type, end-to-end timing required

None

19 Undefined traffic type, reserved timing requirement


X 1

No

Traffic type not indicated, end-to-end timing required

None

9 VBR traffic type, end-to-end timing required

None



VP 9

No

VBR traffic type, end-to-end timing required

New in UNI 4.0





VBR-NRT

C abs

No

Absent None

11 VBR traffic type, reserved timing requirement


X abs No Absent None

0 No Traffic type not indicated, timing not indicated

None

2 No Traffic type not indicated, end-to-end timing not required

None

8 No VBR traffic type, timing not indicated None

10 No VBR traffic type, end-to-end timing not required

None

11 No VBR traffic type, reserved timing requirement


VP abs No Absent New in UNI 4.0

10 No VBR traffic type, end-to-end timing not required

New in UNI 4.0

11 No VBR traffic type, reserved timing requirement


UBR C abs Yes Absent None

X abs Yes Absent None

0 Yes None None

2 Yes None None

8 Yes None None

10 Yes None None

VP abs Yes Absent New in UNI 4.0

10 Yes VBR traffic type, end-to-end timing not required

New in UNI 4.0

Table D-3. Derivation of ATM Service Categories From Signalling Information (ATM UNI 4.0 and PNNI 1.0) (Continued)

ASC (a)

BBC(b)

ATC(c)

BEI(d)


Comment




Allowed Combination of Bearer Capabilities, Traffic Parameters, and QoS in ATM UNI 4.0 and PNNI 1.0

From ATMF UNI 4.0 Signalling, Section A9.3:

The parameters specified in the Broadband Bearer Capability information element, the ATM traffic descriptor information element, the Extended QoS parameters information element, the End-to-End transit delay information element, and the QoS parameter information element of the SETUP message should be consistent. Table D-4 shows the allowable combinations of the Broadband Bearer Class, the ATM traffic descriptor parameters, the Extended QoS parameters, the End-to-end transit delay, and the QoS classes.

If a received SETUP message contains a combination of Broadband Bearer Class, ATC, and Best Effort Indicator that does not match an entry in Table D-4, the call shall be cleared with Cause #65, “Bearer capability not implemented.” If the combination of traffic parameters, QoS parameters, and QoS class in a SETUP message is not an allowable combination for the ATM Service Category, the call shall be cleared with Cause #73, “Unsupported combination of traffic parameters.”

ABR C

12 No Undefined traffic type, timing not indicated

New in UNI 4.0, invalid in UNI 3.1 BBC octet 5a coding

X

VP

Legend:(a) ATM Service Category as defined by ATM Forum Traffic Management Specification, Version 4.0 Specification.(b) Broadband Bearer Class in octet 5 of Broadband bearer capability information element.(c) ATM Transfer Capability as defined in this Specification (octet 5a of the Broadband Bearer Capability information element).(d) Best Effort Indicator – Octet 18 of ATM Traffic descriptor information element (yes = present, no = not present).

Table D-3. Derivation of ATM Service Categories From Signalling Information (ATM UNI 4.0 and PNNI 1.0) (Continued)

ASC (a)

BBC(b)

ATC(c)

BEI(d)


Comment



Table D-4. Allowable Combinations of Traffic and QoS Parametersin the SETUP Message (ATM UNI 4.0 and PNNI 1.0)

ATM Service Category CBR

Conformance CBR.1 (Note 10) (Note 4) (Note 4)

Bearer Capability

Broadband Bearer Class A X VP A X VP(Note 5)

A X VP(Note 5)

ATM Transfer Capability(Note 1)

7 Absent 4, 5, or 6

5 Absent 4, 5, or 6

5

Traffic Descriptor for a given direction

PCR (CLP=0) S

PCR (CLP=0+1) S S S

SCR, MBS (CLP=0)

SCR, MBS (CLP=0+1)

Best Effort

Tagging N N Y/N

Frame Discard Y/N Y/N Y/N

QoS Classes * * *

Transit delay (Note 2) O O O

Peak-to-peak CDV O O O

CLR (CLP=0) (Note 11) O O

CLR (CLP=0+1) (Note 11)

O

ATM Service Category VBR Real Time

Conformance VBR.1 (Note 10) VBR.2 VBR.3

Bearer Capability

Broadband Bearer Class C X VP C X VP C X VP

ATM Transfer Capability 19 9 1 or 9 9 9 1 or 9 9




ATM Service Category VBR Real Time (continued)


PCR (CLP=0)

PCR (CLP=0+1) S S S

SCR, MBS (CLP=0) S S

SCR, MBS (CLP=0+1) S

Best Effort

Tagging N N Y


QoS Classes * * *

transit delay (Note 2) O O O

peak-to-peak CDV O O O


CLR (CLP=0+1) (Note 11) O

Conformance (Notes 4, 7) (Notes 4, 8) (Note 4)

Bearer Capability

Broadband Bearer Class X X X C or VP(Note 5)

ATM Transfer Capability 1 or 9 1 or 9 1 or 9 9


PCR (CLP=0) S

PCR (CLP=0+1) S S S

SCR, MBS (CLP=0)


Best Effort

Tagging Y/N N N

Table D-4. Allowable Combinations of Traffic and QoS Parametersin the SETUP Message (ATM UNI 4.0 and PNNI 1.0) (Continued)



ATM Service Category VBR Real Time (continued)


QoS Classes * * *

transit delay (Note 2) O O O

peak-to-peak CDV O O O

CLR (CLP=0) (Note 11) O O O


ATM Service Category VBR Non-Real Time (continues)

Conformance VBR.1 (Note 10) VBR.2 VBR.3

Bearer Capability



11 Absent Absent, 0, 2, 8 or 10

Absent, 10

Absent Absent, 0, 2, 8 or 10

Absent, 10


PCR (CLP=0)

PCR (CLP=0+1) S S S

SCR, MBS (CLP=0) S S


Best Effort

Tagging N N Y


QoS Classes * * *

transit delay (Note 2) (Note 3) (Note 3) (Note 3)

peak-to-peak CDV






ATM Service Category VBR Non-Real Time (continued)

CLR (CLP=0+1) (Note 11) O

Conformance (Notes 4, 7) (Notes 4, 8) (Note 4)

Bearer Capability

Broadband Bearer Class C X C X C X VP


Absent Absent, 0, 2, 8or 10



Absent, 10


PCR (CLP=0) S

PCR (CLP=0+1) S S S

SCR, MBS (CLP=0)


Best Effort

Tagging Y/N N N


QoS Classes * * *

transit delay (Note 2) (Note 3) (Note 3) (Note 3)

peak-to-peak CDV

CLR (CLP=0) (Note 11) O O O


ATM Service Category ABR (continues) UBR (continues)

Conformance ABR UBR.1 UBR.2

Bearer Capability





ATM Service Category ABR (continued) UBR (continued)

ATM Transfer Capability 12 Absent Absent, 0, 2, 8 or 10

Absent, 10


Absent, 10


PCR (CLP=0)

PCR (CLP=0+1) S S S

SCR, MBS (CLP=0)

SCR, MBS (CLP=0+1)

ABR MCR (Note 6)

Best Effort S (Note 9) S (Note 9)

Tagging N N Y


QoS Classes 0 0 0

Transit delay (Note 2)

Peak-to-peak CDV

CLR (CLP=0) (Note 11)






Table Notes:Note 1 – Values 0, 1, 2, 4, 6, and 8 are not used on transmission but shall be understood on reception.Note 2 – Maximum end-to-end transit delay objectives may only be specified for the forward direction.Note 3 – Maximum end-to-end transit delay objectives may be specified for the ATM Service Category of

Non-Real Time VBR for reasons of backward compatibility with ITU-T recommendations.Note 4 – Included for reasons of backward compatibility with UNI 3.1 and ITU-T recommendations. With these

conformance definitions, the CLR commitment is only for the CLP=0 traffic stream.Note 5 – Included to allow switched virtual paths to use the UNI 3.1 conformance definitions.Note 6 – Optional in the user-to-network direction. Specified in the network-to-user direction.Note 7 – This combination should be treated as if the received PCR (CLP=0) parameter were a SCR (CLP=0)

parameter and a MBS (CLP=0) parameter with a value of 1.Note 8 – This combination should be treated as if an additional SCR (CLP=0) were received with the same value as

the received PCR (CLP=0+1) parameter with a MBS (CLP=0) parameter with a value of 1.Note 9 – The Best Effort indication applies to both the forward and backward directions.Note 10 – This combination should only be used when the CLR commitment on CLP=0+1 traffic is required

versus CLR commitment on CLP=0 traffic, since these combinations are not supported by UNI 3.0/3.1 nor ITU-T Q.2931.

Note 11 – In this table, the CLR parameter is shown as two entries to indicate explicitly whether the CLR commitment is for the CLP=0 or for the CLP=0+1 cells.

Table Abbreviations:PCR = Peak Cell Rate; SCR = Sustainable Cell Rate; MBS = Maximum Burst Size; Y = Yes; N = No; Y/N = Either “Yes” or “No” is allowed; S = Specified; (Blank) = Unspecified; * = Allowed QoS class values are a network option. Class 0 is always supported for alignment with ITU-T;O = Optional. May be specified using:

- An individual QoS parameter encoded in the Extended QoS parameters information element or the end-to-end transit delay information element or,

- Objectives implied from the QoS classIf an extended QoS parameters information element is present and this parameter is not present in the message, then any value of this parameter is acceptable. If neither the parameter nor the Extended QoS parameters information element is present in the message, then the objective for this parameter is determined from the QoS class in the QoS parameter information element.


Switch Diagnostics User’s Guide for CBX 3500, CBX 500, GX 550, and B-STDX 9000 E-1


E

Using Disk Diagnostic Utilities

Lucent switches use either hard disks or flash cards that emulate hard disks, to store the following information:

• Operational software

• Configuration information

• Accounting and diagnostic information

All Lucent switches have disk diagnostic capabilities, which fall into two major areas:

• Diagnostics that run when the control processor (CP) on the B-STDX switch, switch processor (SP) on the CBX 500/35000 switch, or node processor (NP) on the GX 550 Multiservice WAN switch boots

• Diagnostics that you use at the switch console

In addition to using disk diagnostic utilities at the switch console, you can also list files and directories.


E-210/7/05 Switch Diagnostics User’s Guide for CBX 3500, CBX 500, GX 550, and B-STDX 9000

Using Disk Diagnostic UtilitiesUnderstanding Disk Boot Diagnostics

Understanding Disk Boot Diagnostics

Two disk diagnostic programs run automatically when the CP/SP/NP boots. Although you have no control over these diagnostic programs, it is helpful to understand how they work. These diagnostic programs are:

• Extended post (power-on self test) — This test, which runs during the extended post operation, verifies that the CP/SP/NP can communicate with the disk. This test is not comprehensive. If this test or any of the other extended post tests fails, the boot process stops and the red LED on the CP/SP/NP flashes repeatedly.

• Comprehensive file system test — This test examines the disk for file system errors. It is a comprehensive test that is performed after the bootflash and application code are loaded. This test is based on the scandisk utility that is found on standard desktop PCs. When this tests runs, some of the items examined include:

– Block 0 data (the file system format parameters)

– Both file allocation table (FAT) copies

– Root directory (file name, size, and storage allocation)

– Unattached clusters (storage clusters that appear to be in use but are not in any file allocation chain)

The following errors are repaired automatically when the scandisk test detects them:

• FAT errors — If the two FAT copies are not identical, the first copy is used and is copied to the second.

• Cluster chain errors — If the size of a file is larger than the disk block clusters allocated to it, the size is reduced to the allocated storage size. However, in the root directory, if file size is smaller than the storage allocated in the disk block cluster chain, the chain is truncated according to the file size.

• Unattached clusters — If unattached clusters are detected, all of them are freed.

Beta Draft Confidential Using Disk Diagnostic UtilitiesUsing Disk Diagnostics at the Switch Console

Switch Diagnostics User’s Guide for CBX 3500, CBX 500, GX 550, and B-STDX 9000 10/7/05E-3

Some disk-related errors cannot be repaired. For these errors, the CP/SP/NP cannot complete the boot cycle and halts. The red LED on the CP/SP/NP remains lighted (that is, it does not flash). You may verify this state as follows:

1. Connect a console terminal to the front of the CP/SP/NP (or the card itself on the CP).

2. Observe the displayed debug messages on the console terminal.

Depending on your switch platform, see the B-STDX 9000 Multiservice WAN Hardware Installation Guide, the CBX 3500 Multiservice Edge Switch Hardware Installation Guide, the CBX 500 Multiservice WAN Switch Hardware Installation Guide, or the GX 550 Hardware Installation Guide to connect the console terminal to the switch.

Using Disk Diagnostics at the Switch Console

While the switch is online, you can run the scandisk and testdisk disk diagnostic utilities at the switch console. To use these utilities, you must enter debug mode at the switch console as follows:

1. Access the switch console login prompt. See the Getting Started User’s Guide for CBX 3500, CBX 500, GX 550, and B-STDX 9000 for descriptions of the various ways you can access the switch console.

If the NMS is connected to the switch, select the appropriate switch object on the network map. Then, from the Misc menu, select Terminal Connect ⇒ Telnet.

2. Log in to the switch console.

3. At the switch console prompt, issue the following command:

enable debug

4. At the Debug password prompt, enter your debug password. If you do not know this password, contact the Lucent Data Networking Group Technical Assistance Center.

Note – Notify the Lucent Data Networking Group Technical Assistance Center (TAC) if you notice disk-related errors that cannot be repaired.



Using Disk Diagnostic UtilitiesUsing Disk Diagnostics at the Switch Console

Using the Scandisk Utility

You invoke the scandisk utility by issuing scandisk at the console prompt. The utility runs as either a foreground or a background program (foreground is the default mode). See the Console Command User’s Reference for CBX 3500, CBX 500, GX 550, and B-STDX 9000 for a description of the scandisk command syntax.

The scandisk utility checks the file system and storage capabilities on the disk. Unlike the scandisk test that runs when the switch boots, the online scandisk utility cannot repair errors (disk errors cannot be repaired while the file system is active).

However, the online scandisk utility is useful for detecting errors on either the active or standby CP/SP/NP disk. The online scandisk utility audits the file system and the disk storage conditions on the switch. The utility checks the disk block zero information and compares the two copies of the FAT. If the online scandisk utility finds errors, scandisk reports them as background diagnostics errors. This causes the CP/SP/NP to become yellow on the NMS. The switch also sends a trap to the NMS.

The default scandisk utility options are:

• Foreground mode — The utility runs as a foreground program, and you cannot perform other tasks at the switch console while the utility runs.

• Active disk — The utility scans the active disk.

• No surface scan — The utility does not perform a disk surface scan.

In the default mode, scandisk reports:

• The disk model

• Block zero (0) information

• FAT conditions

• Root directory entry conditions

• Cylinder/head/sector location of bad disk sectors

Note – You cannot run more than one background scandisk instance at a time.

Beta Draft Confidential Using Disk Diagnostic UtilitiesUsing Disk Diagnostics at the Switch Console

Switch Diagnostics User’s Guide for CBX 3500, CBX 500, GX 550, and B-STDX 9000 10/7/05E-5

The online scandisk utility provides you with the following options:

• Active/standby disk — Use this option to check either the active disk surface or the standby disk surface (the default is the active disk). On the active disk, this check can be performed in the foreground or background mode. On the standby disk, only the regular check can be performed in foreground mode — the surface scan of the standby disk can be performed only in the background.

• Surface scan — Use this option to check every sector of every cylinder in the available disk surface (the default is no surface scan). A surface scan takes a long time to finish. You can terminate the check by typing Ctrl-c on the console while scandisk is running in the foreground mode.

Using the Testdisk Utility

You invoke the testdisk utility by issuing testdisk at the console prompt. See the Console Command User’s Reference for CBX 3500, CBX 500, GX 550, and B-STDX 9000 for a description of the testdisk command syntax.

The testdisk utility can be run on the active disk only. It is a foreground program that provides the following disk diagnostic functions:

• Performs a fast or long scan of the disk surface and displays the location of bad disk sectors

• Dumps the contents of a particular disk sector

• Dumps the root directory and storage allocation information of a specified file, if you use the dir option

• Compares two specified files and displays the different blocks in the files, if you use the file option

Note – Notify the Lucent Data Networking Group Technical Assistance Center if you notice disk-related errors that cannot be repaired.

Note – Notify the Lucent Data Networking Group Technical Assistance Center if you notice disk-related errors that cannot be repaired.



Using Disk Diagnostic UtilitiesListing Files and Directories

Listing Files and Directories

At the switch console, you can issue dir to obtain a directory and file listing. This command is similar to the disk operating system (DOS) dir command. You do not have to be in debug mode to issue this command.

ATM Services Configuration Guide for CBX 3500, CBX 500, GX 550, and B-STDX 9000 Acronyms-1


Abbreviations and AcronymsThis section lists abbreviations for units of measure (in specifications) and terms and acronyms used in Lucent documentation.

Abbreviations

The following table lists some of the abbreviations used in Lucent documentation and product specifications.

Abbreviation Meaning

bit binary digit

bpi bits per inch

bps bits per second

CPS cells per second

GB gigabyte(s)

Gbps gigabits per second

hex hexadecimal

Hz hertz (cycles per second)

ID identification

i.e. id est (that is)

in. inch (es)

k kilo (1,000)

Kb kilobit

KB kilobyte(s)

Kbps kilobits per second


Acronyms-2 ATM Services Configuration Guide for CBX 3500, CBX 500, GX 550, and B-STDX 9000

Acronyms

kg kilogram

kHz kilohertz

Mb megabit

MB megabyte(s)

Mbps megabits per second

MHz megahertz

min minute(s)

modem modulator/demodulator

msec millisecond

usec microsecond (abbreviate with lowercase “u” for micro)

sec second

vs. versus

# number; pound

x by (multi)

Abbreviation Meaning

Beta Draft ConfidentialAcronyms


Acronyms

This guide uses the following acronyms:

Acronym Description

AAL Asynchronous Transfer Mode (ATM) Adaptation Layer

ABR available bit rate

ACR allowed cell rate

AESA ATM End System Address

AFI authority and format identifier

AIS alarm indication signal

APS Automatic Protection Switching

ARP Address Resolution Protocol

ASE Autonomous System External

ASBR autonomous system border router

ASCII American Standard Code for Information Interchange

ASR Application Specific Route

ATM Asynchronous Transfer Mode

ATMoMPLS ATM over MPLS

Bc committed burst size

BCM backward congestion message

Be excess burst size

BECN backward explicit congestion notification

BER bit error rate

BGP Border Gateway Protocol

BHLI Broadband Higher Level Information

BI backward indicator

B-ICI B-ISDN Inter-Carrier Interface

BIO Base Input/Output

CAC Call Admission Control



Acronyms

CBR Constant Bit Rate

CCRM Cascade Communications Resource Management

CDE Common Desktop Environment

CDP circuit defined path

CDV cell delay variation

CDVT cell delay variation tolerance

CE circuit emulation

CFR constant frame rate

CI congestion indication

CIC carrier identification code

CIR committed information rate

CLI command line interface

CLLM Consolidated Link Layer Management

CLP Cell Loss Priority

CLR cell loss ratio

CP control processor

CPE customer premise equipment

CRC cyclic redundancy check

CSR Customer Specific Route

CS Cell Switching or convergence sublayer

CSU channel service unit

CTD cell transfer delay

CUG closed user group

DCC data country code

DCE data communications equipment

DE discard eligible

DLCI Data Link Connection Identifier

Acronym Description



DNIC data network identification code

DSL digital subscriber line

DSP digital signal processor

DSU data service unit

DSX digital signal cross-connect

DTE data terminal equipment

DXI Data Exchange Interface

EBR excess burst rate

EBW equivalent bandwidth

EFCI explicit forward congestion indication

EPD early packet discard

ESI end system identifier

FCP Flow Control Processor

FEAC Far-End Alarm and Control

FECN forward explicit congestion notification

FR Frame Relay

FRAD Frame Relay access device

FTP File Transfer Protocol

FUNI Frame-based UNI

GFC Generic Flow Control

GUI graphical user interface

HCS header check sequence

HDLC High-level Data Link Control

HO-DSP high-order domain-specific part

H-PNNI Hierarchical PNNI

HSSI High-Speed Serial Interface

IA incoming access

Acronym Description



Acronyms

IARP Inverse Address Resolution Protocol

ICB incoming calls barred

ICD International Code Designator

ICMP Internet Control Message Protocol

ICR initial cell rate

ID identifier

IDI initial domain identifier

IDP initial domain part

IE information element

IFNUM interface number

IGMP Internet Group Multicast Protocol

IISP Interim Inter-switch Signaling Protocol

ILMI Integrated Layer Management Interface

IMA Inverse Multiplexing for ATM

I/O input/output

IOA input/output adapter

IOM input/output module

IOP input/output processor

IP Internet Protocol

ISDN Integrated Services Digital Network

ITU International Telecommunications Union

IWU Interworking Unit

IXC inter-exchange carrier

KA keep alive

LAN local area network

LAP Link Access Protocol

LATA Local Access and Transport Area

Acronym Description



LDP Label Distribution Protocol

LER Label Edge Router

LGN logical group node

LMI Link Management Interface

LOS loss of signal

LSA link state advertisement

LSP label switched path

LTP Link Trunk Protocol

MAC Media Access Control

MBS maximum burst size

MCR minimum cell rate

MIB Management Information Base

MLFR Multilink Frame Relay

MPLS Multi-protocol Label Switching

MPT Multipoint-to-Point Tunnel

MPVC management permanent virtual circuit

MSPVC management soft permanent virtual circuit

NDC Network Data Collection

Ne Network entity

NHRP Next Hop Resolution Protocol

Ne-NSC Network entity NSC

NI no increase

NIC Network Interface Card

NMS network management station; network management system

NNI Network-to-Network Interface

NP node processor

NPA node processor adapter

Acronym Description



Acronyms

NPC network parameter control

NRM Network Resource Management

NRT Non-Real Time

NRTS Non-Real Time Services

NSC Network Service Category

NTM network traffic management

OA outgoing access

OAM Operations, Administration, and Maintenance

OCB outgoing calls barred

OPTimum Open Packet Trunking

OSPF Open Shortest Path First

OUI Organizationally Unique Identifier

PAD packet assembler/disassembler

PCM Port Congestion Monitor

PCR peak cell rate

PDN public data network

PDU protocol data unit

PE provider edge

PG peer group

PGL peer group leader

PLCP Physical Layer Convergence Protocol

PM performance monitoring

PMP point-to-multipoint

PNNI Private Network-to-Network Interface

PPD partial packet discard

PPP Point-to-Point Protocol

PRAM parameter random access memory

Acronym Description



PRI Primary Rate Interface

PSA proxy siganling agent

PSC proxy signaling client

PSN public switched network; packet switched network

PTSP PNNI Topology State Packet

PTSE PNNI Topology State Element

PVC permanent virtual circuit

PVP permanent virtual path

PW pseudo wire

PWE3 pseudo wire edge to edge emulation

QoS Quality of Service

RADIUS Remote Authentication Dial-In User Service

RBOC Regional Bell Operating Company

RCC routing control channel

RDE Rate Decrease Exponent

RDF Rate Decrease Factor

RED random early discard

RFC Request For Comments

RIE Rate Increase Exponent

RIF Rate Increase Factor

RIP Routing Information Protocol

RLMI Resilient Link Management Interface

RM resource management

Rp-NSC Resource partition NSC

RSVP Resource Reservation Protocol

SCR sustainable cell rate

SD Signal Degrade

Acronym Description



Acronyms

SF Signal Fail

SLIP Serial Line Internet Protocol

SNB service name binding

SNMP Simple Network Management Protocol

SONET Synchronous Optical Network

SP switch processor

SPVC soft permanent virtual circuit

SPVCC soft permanent virtual channel connection

SPVPC soft permanent virtual path connection

STM-1 Synchronous Transport Module level 1

STS-1 Synchronous Transport Signal level 1

SVC switched virtual circuit

SVCC switched virtual channel connection

SVPC switched virtual path connection

TAC Technical Assistance Center

TCP Transmission Control Protocol

TD traffic descriptor

TDM timed division multiplexing

TE terminal equipment

TM timing module

TNS transit network selection

ToS Type of Service

UBR Unspecified Bit Rate

UDP User Datagram Protocol

UFR unspecified frame rate

UIO Universal Input/Output

UNI User-to-Network Interface

Acronym Description



UPC Usage Parameter Control

USP Universal Switch Processor

VBR Variable Bit Rate

VBR-RT/NRT variable bit rate-real time/non-real time

VC virtual circuit

VCC virtual channel connection; virtual circuit connection

VCI virtual channel identifier; virtual circuit identifier

VCL virtual circuit link; virtual channel link

VFR variable frame rate

VFR-RT/NRT variable frame rate-real time/non-real time

VNN Virtual Network Navigator

VP virtual path

VPC virtual path connection

VPCI virtual path connection identifier

VPI virtual path identifier

VPN Virtual Private Network

WAN wide area network

Acronym Description



Acronyms

Index

Switch Diagnostics User’s Guide for CBX 3500, CBX 500, GX 550, and B-STDX 9000 Index-1


Index

A

ABR. See Available Bit RateAcknowledging alarms, 14-12Admin status

changingfor a logical port, 5-11for a physical port, 5-9for an IOM, 5-9

Administrative domains, 13-36Alarm relay

clearing, 14-24Alarms

acknowledging/unacknowledging, 14-12Configuration at a switch, 14-23deleting, 14-20displaying a list, 14-2Event configuration, 14-21filtering, 14-7managing alarm configuration for a switch,

14-22messages, A-1Refresh rate, 14-12saving, 14-18saving filtered alarms, 14-19saving unfiltered alarms, 14-19Setting alarm count, 14-11sorting, 14-16viewing details, 14-14

Alarms dialog boxacknowledging/unacknowledging traps, 14-12

Alarms status indicator colors, 2-49Asynchronous Transfer Mode

circuit testing, 12-69configuring path trace information, 12-22OAM, 12-69QoS classes, 6-13, 6-16testing circuits, 12-69trunks, 10-1viewing

circuit CAC parameters, 12-68

circuit operational status, 12-2circuit summary statistics, 12-34enhanced connection trace information, 12-18NDC statistics, 12-51offnet PVC circuits, 12-75path trace information, 12-20PWE3 offnet circuits, 12-75SVC node prefixes, 11-7SVC summary statistics, 12-64, 13-26threshold crossing alarm (TCA) parameters,

2-106viewing NTM statistics, 12-51

ATAF TAP-VCconnecting, 12-85viewing statistics, 12-88

ATAF. See ATM Test Access FunctionATM

round-trip delaystatistics, 12-77

ATM round-trip delay statisticson SVCs, 12-80supported circuits, 12-77

ATM Test Access Function (ATAF), 12-81cell stream monitoring restrictions, 12-84configuration steps, 12-82overview, 12-81restrictions, 12-82supported modules, 12-81

ATM. See Asynchronous Transfer ModeAvailable Bit Rate (ABR), 11-17, 11-24

B

Background diagnosticsdescription, 5-1

Backward Explicit Congestion Notification (BECN), 13-14, 13-29

Bandwidth (BW)utilization (%), 3-9

Index-2 Switch Diagnostics User’s Guide for CBX 3500, CBX 500, GX 550, and B-STDX 9000

Index


BECN. See Backward Explicit Congestion Notification

Bit error rate test (BERT)about, 5-73for DS3 ATM/CE modules, 5-58, 5-63, 5-66for DS3-1-0 modules, 5-77, 5-82for POS Universal I/O modules, 5-66for subrate DS3 FR-IP modules, 5-58, 5-63, 5-66test pattern, 5-77test patterns, 5-74

Boundary location, 13-39Broadband Bearer Capabilities, D-6, D-8Buffers

output discarded cells, 3-9

C

CAC. See Call Admission ControlCall Admission Control (CAC), 13-24Cell transmission

measuring, 12-77Circuit summary statistics, 13-11Clearing the alarm relay, 14-24Colors

trunks, 10-8Configuring

ATAF, 12-82ATM round-trip delay statistics, 12-77

Console Commandsfor Enhanced Standby Hardware (ESHW) test,

17-21for Path Integrity, 17-8for PRAM Consistency, 17-17used with the Emergency Action Interface (EAI),

17-3Console window

description of menus and tabs, 2-53functions, 2-53

Contact alarm relay, 14-22Crash

address, 5-4trace information, 5-7

Crash dump systemcomponents, 16-1

console commands, 16-26 to 16-35description, 16-1dump regions, 16-3files, 16-2live upload, 16-2memory regions, 16-3minimum crash dump configuration, 16-14restrictions, 16-36storage considerations, 16-4using, 16-4 to 16-8

Crash systemdeleting a dump region, 16-24displaying dump regions as viewed by switch,

16-18CSU loopback tests, 5-54

D

Data Delivery Ratio, 13-39Diagnostic loopback tests, 5-41Diagnostic loopbacks

E1 near-end, 5-35, 5-39Diagnostics

errorsfatal, 5-2non-fatal, 5-2

foreground, 5-7source of information, 5-4, 5-5types of tests, 5-15, 5-20, 5-21

Discarded CLP, 12-41Disk diagnostics, E-1DS0 loopback

far-endB-STDX modules, 5-55

DS3 physical portline status, 4-22, 4-23, 4-24

DSU loopback tests, 5-54Dump regions

deleting, 16-24displaying as viewed by switch, 16-18

Index



E

E1 moderunning loopback tests, 5-37, 5-40

E1 near-end loopbacksabout, 5-35, 5-39

E1 ports, performance monitoring, 4-28Emergency Action Interface (EAI), 17-2 to 17-4

console commands supported, 17-3high-priority telnet session, 17-4switch console session, 17-3

Enhanced Exception Logging, 17-13use of Event Log, 15-32, 17-13

Enhanced Fault Manager, 17-12Enhanced PVC Loopback, 13-30Enhanced Standby Hardware (ESHW) Test, 17-18

to 17-22about, 17-18configuring for SF modules, 17-20configuring for SP/NP and IOM/BIO modules,

17-19console commands, 17-21

Error code reference, B-1Errored seconds (ES), 3-25ES. See Errored seconds (ES)ESF

FDL payload loopback test, 5-32line loopback test, 5-32

Event Log, 15-32, 17-13Path Integrity messages, 17-11

EventsEvent Log

about, 15-2configuration

disabling, 15-33

logging, 15-2, 15-19options, 15-26

overview, 15-16tracing, 15-2, 15-21

replacement of Syslog, 15-27External Power status indicator colors, 2-49

F

Failed SVCsusing failure location information, C-1 to C-10

Fan status indicator colors, 2-50Far-end loopback tests, 5-43, 5-45Fatal errors, 5-2, 5-4FEAC state, 5-24FECN. See Forward Explicit Congestion

NotificationForeground Diagnostics. See DiagnosticsForward Explicit Congestion Notification (FECN),

13-14, 13-29Frame Delivery Ratio, 13-39Frame Relay

FECN/BECN, 13-29LMI operator status, 8-9PVC loopback, 13-30QoS classes, 6-13, 6-16traffic descriptors, 13-24trunks, 10-1viewing

CAC parameters, 13-24Frame Relay OAM

about, 13-36administrative domains, 13-36boundary location, 13-39configuring monitoring points, 13-40Data Delivery Ratio, 13-39disabling on logical port, 13-48Frame Delivery Ratio, 13-39Frame Transfer Delay, 13-39loopback testing, 13-39monitoring points, 13-36, 13-39running, 13-43

Frame Relay-to-PNNI interworking, 12-75Frame Transfer Delay, 13-39Framed inband line loopback test, 5-31Front View panel

Alarms status indicator colors, 2-49fan/power status indicator colors, 2-50module status indicator colors, 2-50Stby status indicator colors, 2-50Switch Status indicator colors, 2-49


Index


H

Heap memory, 5-6

I

I/O modules (IOM)color, 2-48viewing

attributes, 2-63ILMI. See Interim Link Management InterfaceIMA links

performance, 4-38test pattern, 5-18

Interim Link Management Interface (ILMI)receiving VCC status traps, 7-3statistics, 7-15viewing addresses, 11-18

Internet Protocol (IP)BGP operational information, 9-11displaying IP objects, 9-2displaying IP VPNs, 9-32IP object attributes, 9-10IP objects operational status, 9-11OSPF operational information, 9-16summary statistics, 9-17

Invalid cells, 5-6Inverse Multiplexing Over ATM (IMA)

frame size (M), 2-97

L

Latching loopback tests, 13-40Layer 2 Tunnels

operational information, 2-35statistics, 2-36viewing, 2-35

LDP Entitiesoperational information, 2-23statistics, 2-24viewing, 2-23

Line loopback tests, 5-31, 5-41Line loopbacks

E1 near-end, 5-35, 5-39LMI

operator status, 8-8Location ID, 13-39Logical ports

changing admin status, 5-11general attributes, 6-7, 11-4viewing

attributes, 6-7, 11-4Loopback testing for Frame Relay OAM, 13-39Loopback tests

E1 near-endabout, 5-35, 5-39

LoopbacksCSU, 5-54diagnostic, 5-41DS0, 5-49, 5-54DS0 far-end loopback statistics, 5-54DS1, 5-32, 5-33, 5-36, 5-39DS3, 5-25, 5-27, 5-28, 5-42, 5-45DSU, 5-54E1, 5-47Enhanced PVC, 13-30ESF FDL payload, 5-32ESF line, 5-32external, 5-20, 5-22far-end, 5-43, 5-45, 5-52Frame Relay PVC, 13-30framed inband line, 5-31internal, 5-15, 5-20, 5-21line, 5-31, 5-41metallic, 5-30near-end, 5-40, 5-47, 5-49OAM, 12-69OC12, 5-28OC3, 5-28payload, 5-31, 5-41running, 5-22state, 5-55STM-1, 5-28STM-4, 5-28unframed inband line, 5-31

Index



M

Management DLCIs, 8-16Manufacturing information

CP, SP, NP, 2-58IOM, BIO, subcard, 2-65

Measuring cell transmission time, 12-77Memory

heap, 5-6Metallic loopback test, 5-30MIB

browser, 18-1structure, 18-2

MIB browserget, 18-8set, 18-8walk, 18-7

MID status colors, 2-51Modules

system timing options, 2-62viewing, 2-54viewing processor modules, 2-55viewing subcards, 2-54

Monitor menu, 1-1Monitoring

SNMP failures, 2-52, 2-55VP shaping, 2-101

Monitoring pointsabout, 13-36boundary location, 13-39configuring, 13-40location ID, 13-39

MPLSviewing affinities, 2-4viewing traffic profiles, 2-3viewing tunnel hoplists, 2-5

MPLS Tunnelsoperational information, 2-29statistics, 2-32viewing, 2-27

Multilink Frame Relay (MLFR)trunk, 10-1

N

Near-end loopback tests, 5-40, 5-47, 5-49Network data collection

configuring attributes, 12-59description, 12-53viewing

logical port statistics, 12-58thresholds, 12-63

Network traffic managementconfiguring attributes, 12-54congestion, 12-51, 12-52, 12-54description, 12-51surveillance measurement, 12-52types of measurements, 12-53viewing

logical port statistics, 12-57parameters, 12-56

NetworksMPLS affinities, 2-4MPLS traffic profiles, 2-3tunnel hoplists, 2-5viewing, 2-1

NNI logical portsFrame Relay, 8-7

Non-fatal errors, 5-5Non-latching loopback tests, 13-40NPC measurements, 12-54

O

OAM loopbackaccessing test functions, 12-73time interval, 12-72

OC12 physical portsloopbacks, 5-28performance monitoring, 4-4 to 4-10, 4-11

OC3 physical portsloopback, 5-28performance monitoring, 4-4 to 4-10, 4-11

on, A-47Operational information

for switch, 2-10for TAP-VC, 12-86


Index


Optical cardsviewing redundant pports, 2-107

Overload Severityviewing, 17-7

Oversubscription, 6-13

P

Path Integrity, 17-8 to 17-12configuration example, 17-9 to 17-11console commands, 17-8Event Log messages, 17-11

Payload loopback tests, 5-31, 5-41Payload loopbacks

E1 near-end, 5-35, 5-39Performance monitoring

for OC12/STM-4 ports, 4-4 to 4-10, 4-11for OC3/STM-1 ports, 4-4 to 4-10, 4-11for Sonet/SDH, 4-11, 4-18overview, 4-1viewing, 4-3

Permanent virtual circuit (PVC)round-trip delay statistics, 12-78

Permanent Virtual Circuits (PVCs)establishment rate control

VC overload control, 17-5inactive operational status codes, 12-11, 13-6loopback tests, 12-69, 13-30

Physical portchanging admin status, 5-9viewing

G.826 statistics, 3-11performance monitoring statistics, 4-32, 4-36RFC 1406 statistics, 3-11

physical portviewing, 2-74

Physical port colors, 2-48Physical Port Redundancy Pairings Dialog Box,

2-107Physical ports

viewing operational status, 2-81viewing protection ports, 2-108viewing redundant pports, 2-107viewing working ports, 2-108

Point-to-point LSPviewing operational information, 9-12, 9-23

Port addresses, 11-9Port prefixes, 11-8Port user parts, 11-10Power status indicator colors, 2-50PRAM consistency test

console commands, 17-17event log messages, 17-16running the test, 17-14viewing test configuration, 17-14

PVC Establishment Rate Control, 17-5with VC Overload Control disabled, 17-5with VC Overload Control enabled, 17-5

PVC loopbackendpoint settings, 13-30problems detected by, 13-32setting, 13-32valid endpoint combinations, 13-34when to use, 13-32

PVCsFrame Relay OAM, 13-36

PVCs. See Permanent Virtual CircuitsPWE3 circuits

offnet PVCs, 12-75PVCs, 12-2

Q

Q.2610, C-3Q.2931, 7-11, D-1Q.850, C-2Quality of Service (QoS)

ATM classes, 6-13, 6-17Frame Relay classes, 6-13, 6-17relationship to CAC, 13-24specified classes, D-2unspecified classes, D-4

R

Rear View panelExternal Power status indicator colors, 2-49

Index



fan/power status indicator colors, 2-50MID status colors, 2-51module status indicator colors, 2-50physical port colors, 2-48Stby status indicator colors, 2-50

Redundancyviewing redundant physical ports, 2-107

redundant groups, 2-20viewing, 2-20

Remote Ignore Local. See Enhanced PVC Loopback

Reportsgenerating, 1-5using scripts to generate, 1-5

Round-trip delaystatistics, 12-77

RTD. See ATM round-trip delay statistics

S

SAALstatistics, 7-14

SNMP Failures, monitoring, 2-53SONET

statistics, 4-11, 4-18Specified QoS classes, D-2Statistics

12-port E1, 3-11 to 3-18ATAF TAP-VC, 12-88ATM

PVC summary, 12-34 to 12-37, 13-11SVC summary, 12-64, 13-26

BGP peer, 9-24DS1 channel, 3-7 to 3-8ethernet logical port, 7-17, 9-28Frame Relay

PVC summary, 13-11 to 13-14G.826, 3-9 to 3-18IP logical port, 9-19IP logical port RSVP-TE, 9-21NTM and NDC, 12-51performance monitoring, 4-1, 4-32, 4-36physical port summary, 3-2 to 3-4, ?? to 3-23PPP IP logical port, 9-21

RFC 1406, 3-11 to 3-18RIP, 9-18

Statusof LMI, 8-8of management DLCIs, 8-16of switches, 2-9

Status indicator colors, 2-50Stby status indicator colors, 2-50STM-1 physical ports

loopbacks, 5-28performance monitoring, 4-4 to 4-11, 4-12, 4-24

STM-4 physical portsloopbacks, 5-28performance monitoring, 4-4 to 4-10, 4-11

subportviewing, 2-74

SVCround-trip delay statistics, 12-80

SVCs. See Switched Virtual CircuitsSwitch

viewingstatus of, 2-9

viewing operational information, 2-10viewing status colors, 2-38viewing system timing options, 2-62

Switch Status indicator colors, 2-49Switched Virtual Circuits (SVCs)

ATM, 11-7, 12-64 to 12-68, 13-26uploading record for, 11-13, 11-14using failure location information, C-1 to C-10viewing

active, 11-13, 11-14failed calls, 11-19node prefixes, 11-7port addresses, 11-9port prefixes, 11-8summary statistics, 12-64, 13-26user parts, 11-10

Syslog. See Event Log

T

T1 ports, performance monitoring, 4-28TAP-VC


Index


modifying, 12-89, 12-91viewing operational information, 12-86

Threshold crossing alert (TCA), 2-106Traffic descriptors

EIR, 13-24MBS, 13-24PFR, 13-24SFR, 13-24

Traffic load measurement, 12-53, 12-54Trunks

PVC usage, 10-12types, 10-1utilization, 10-11VNN OSPF area aggregates, 10-15VNN OSPF loopbacks, 10-15VNN OSPF virtual links, 10-15

TunnelsLayer 2 tunnels, 2-35MPLS tunnels, 2-27viewing, 2-27

U

Unacknowledging alarms, 14-12Unframed inband line loopback test, 5-31UNI logical ports

Frame Relay, 8-7Unspecified QoS classes, D-4Usage Parameter Control (UPC) measurements,

12-54User parts, 11-10

V

VC Overload ControlPVC Establishment Rate Control, 17-5viewing, 17-6

VCC status traps. See Virtual Channel Connection status traps

Viewingworking and protection ports, 2-108

Viewing redundant physical ports, 2-107

Virtual Channel Connection (VCC) status traps, ILMI, 7-3

VP shapingB-STDX 9000 switches, 2-101CBX 500 switches, 2-104description, 2-102

VPI/VCIinvalid cells, 5-6

Switch Diagnostics User’s Guide for CBX 3500, CBX 500, GX 550, and B-STDX 9000

Customer Comments

Please take time to send us your comments so that we can do our best to meet your documentation needs. Complete and mail this questionnaire or e-mail your comments to our Technical Publications Dept. Your opinions are of great value to us!

EMAIL:[email protected]

MAILING ADDRESS:Lucent Technologies

Data Networking Group1 Robbins Road

Westford, MA 01886

What tasks did you perform using this guide?

If you were having trouble performing a task, were you able to find the

Were the examples and illustrations helpful for performing tasks? If not, how

What did you like/not like about the manual?

Was there any information you needed that was not in the manual? If so, how

Do you have any other comments about the manual?

Page Description of Error

Name Company

Mailing Address

Phone E-mail address

information you needed? Was the index useful?

can we best deliver that information to you?

Did you install the hardware/software?

Fax No.

can they be improved?

Cu

t H

ere