XedgeMSPx - GDC032R401-V722 Xedge MSPx System Version 7.2.2 iii Issue 1 Configuration & Diagnostics Guide Table of Contents Chapter 6: PCL Configuration/Status

The Best Connections in the Business

TM

Xedge MSPxXedge MSPxXedge MSPx&RQILJXUDWLRQ#)#'LDJQRVWLFV

IRU#9HUVLRQ#:1515

;HGJH#,6*5#6ORW#&RQWUROOHU;HGJH#3&;#6ORW#&RQWUROOHU;HGJH#3&/#6ORW#&RQWUROOHU;HGJH#/LQH#,QWHUIDFH#0RGXOHV

365573409:55#,VVXH#4-XQH#533<

of this readable bject

the use mages.

roducts.

Copyright©2009 General DataComm, Inc. ALL RIGHTS RESERVED.This publication and the software it describes contain proprietary and confidential information. No part document may be copied, photocopied, reproduced, translated or reduced to any electronic or machine-format without prior written permission of General DataComm, Inc. The information in this document is suto change without notice. General DataComm assumes no responsibility for any damages arising fromof this document, including but not limited to, lost revenue, lost data, claims by third parties, or other daIf you have comments or suggestions concerning this manual, please contact:General DataComm, Inc. Technical Publications 6 Rubber Avenue, Naugatuck, Connecticut USA 06770 Telephone: 1 203 729 0271

TrademarksAll brand or product names are trademarks or registered trademarks of their respective companies or organizations.

Documentation

Revision History GDC P/N 032R401-V722

Related Publications

-REV is the hardware revision (-000 , -001 , etc.) -VREV is the most current software version (-V500, V600, V700, etc. ) In addition to the publications listed above, always read Release Notes for Patches supplied with your p

Issue Date Description of Change

1 June 2009 Release of Software Version 7.2.2 and associated hardware

Description Part Number

Xedge / ProSphere Quick Reference (for all Xedge 6000 systems) 032R299-000

Xedge 6000 Hardware Setup Guide (for all Xedge 6000 systems) 032R440-REV

Xedge 6000 Technical Reference Guide 032R310-REV

Xedge 6000 Version 6.2.0 Software Configuration GuideXedge 6000 Version 6.2.0 Diagnostics GuideXedge 6000 Version 6.2.x Release Notes and Cumulative Patch Notes

032R400-V620032R500-V620032R901-V62X

Xedge MSPx Version 7.2.x Configuration & Diagnostics GuideXedge MSPx Version 7.2.x Release Notes and Cumulative Patch Notes

032R401-V72X032R901-V72X

ProSphere NMS Version 5.3 User Guide 032R610-V53X

ProSphere NMS Version 5.3.X Installation and Release Notes (CORE, AEM, GFM, SPM, RTM)ProSphere NMS Version 4.4.0 Installation and Release Notes (CORE, AEM, GFM, MVS)

032R906-V53X032R906-V440

Table of Contents

i

i

8

2

1

2

-4

4

5

1

1

2

3

4

PrefaceSoftware Version History..................................................................................................vii

Hardware Installation........................................................................................................vi

Support Services and Training............................................................................................... viii

Corporate Client Services.................................................................................................viii

Factory Direct Support & Repair......................................................................................viii

Contact Information .........................................................................................................vii

Chapter 1: Xedge Switch OverviewIntroduction to Xedge Version 7.x......................................................................................... 1-1

Xedge Switch Fabric Modules.........................................................................................1-1

Xedge Slot Controllers.....................................................................................................1-1

Version 7.x Slot Controllers and LIMs............................................................................1-2

Xedge Software Overview..................................................................................................... 1-3

Software Files and Functions...........................................................................................1-3

Managing Software Files..................................................................................................1-3

Xedge Terminal Interface.................................................................................................1-4

File System Commands....................................................................................................1-5

TFTP Functions................................................................................................................1-

Special Root Menu Functions.........................................................................................1-10

SAPs and ATM Logical Ports.............................................................................................. 1-11

Routing & Interfaces......................................................................................................1-1

Chapter 2: Accessing Slot ControllersManagement Access Overview.............................................................................................. 2-1

Access Overview..............................................................................................................2-

Craft/Telnet Connections....................................................................................................... 2-

Navigating Xedge Menus and Screens.............................................................................2-3

Security Features.................................................................................................................... 2

Change Passwords............................................................................................................2-

Craft Port Security Key....................................................................................................2-4

Security Options...............................................................................................................2-

Chapter 3: Basic Slot-0 ConfigurationOverview................................................................................................................................ 3-1

Before You Begin.................................................................................................................. 3-

Current Time Format........................................................................................................3-

Slot-0 IP Addressing.........................................................................................................3-

Slot-0 Configuration............................................................................................................... 3-

SNMP Authentication............................................................................................................ 3-

032R401-V722 Xedge MSPx System Version 7.2.2 iIssue 1 Configuration & Diagnostics Guide

Table of Contents

-6

0

0

4

6

-9

11

4

6

-8

10

SNMP Authentication Table Configuration.....................................................................3-4

SNMP Traps.....................................................................................................................3

System Timing Overview...................................................................................................... 3-7

Basic Xedge Timing Principles........................................................................................3-7

System Timing without NTMs............................................................................................... 3-9

Configuration Procedure (Without NTM)......................................................................3-10

System Timing With NTM.................................................................................................. 3-12

NTM Timing Fallback Sequence...................................................................................3-13

System Timing Configuration (With NTM)...................................................................3-14

System Timing Status.......................................................................................................... 3-2

For all Nodes..................................................................................................................3-2

Redundant Slot-0 Configuration.......................................................................................... 3-25

Initial Setup for Slot-0 Redundancy...............................................................................3-25

Enable Slot-0 Redundancy.............................................................................................3-26

Disable Slot-0 Redundancy............................................................................................3-27

Re-Enable Slot-0 Redundancy........................................................................................3-28

Slot-0 Redundancy Guidelines.......................................................................................3-29

Summary.............................................................................................................................. 3-29

Chapter 4: ISG2 Configuration/StatusOverview................................................................................................................................ 4-1

Management Configuration................................................................................................... 4-2

ATM Port Configuration........................................................................................................ 4-

Connecting SAPs to ATM Ports.......................................................................................4-4

Tunnel Configuration............................................................................................................. 4-

Link Status............................................................................................................................. 4-8

Interface Status....................................................................................................................... 4

Node Status.......................................................................................................................... 4-

Chapter 5: PCX Configuration/StatusOverview................................................................................................................................ 5-1

Management Configuration................................................................................................... 5-2

ATM Port Configuration........................................................................................................ 5-

Connecting SAPs to ATM Ports.......................................................................................5-4

Tunnel Configuration............................................................................................................. 5-

Interface Status....................................................................................................................... 5

Node Status.......................................................................................................................... 5-

ii Xedge MSPx System Version 7.2.2 032R401-V722Configuration & Diagnostics Guide Issue 1

Table of Contents

-3

5

0

1

5

9

0

-

-1

1

-4

Chapter 6: PCL Configuration/StatusPCL Configuration Overview................................................................................................ 6-1

Using Stored Configurations.................................................................................................. 6-2

Quick Start Configuration Files........................................................................................6-2

Pre-Configuration Checklist.............................................................................................6-2

Quick Start Configurations - for All Sites.............................................................................. 6-3

Quick Tips........................................................................................................................6

Logging in to the PCL......................................................................................................6-3

Activating the Stored Configuration.................................................................................6-4

Define the Node................................................................................................................6-

Set Tunnel Management IP Address................................................................................6-6

Change Tunnel Management VPI/VCI............................................................................6-7

Change the Root Password...............................................................................................6-9

Configure SNMP Access..................................................................................................6-9

Fine-Tuning the PCL/IMA Configuration........................................................................... 6-10

Change D3 Parameters...................................................................................................6-10

Change T1 Settings.........................................................................................................6-1

Change E3 Parameters....................................................................................................6-11

Change E1 Settings.........................................................................................................6-1

Removing an IMA Link.................................................................................................6-12

Adding an IMA Link......................................................................................................6-1

Change T1/E1 Link Used for Timing.............................................................................6-18

Status and Diagnostics......................................................................................................... 6-1

Checking a Configuration Change.................................................................................6-19

Checking IMA Group Status..........................................................................................6-19

Warm Restarts................................................................................................................6-2

Diagnostic Loopbacks....................................................................................................6-20

Diagnosing Link Failures...............................................................................................6-21

Diagnosing Cell Layer Traffic........................................................................................6-26

Chapter 7: LIM ConfigurationIntroduction............................................................................................................................ 71

LIM Basics.......................................................................................................................7

Configuring Links.............................................................................................................7-

LIM Identification and Status...........................................................................................7-2

LIM Firmware/Software Update......................................................................................7-3

LIM Timing ......................................................................................................................7

SONET/SDH Configuration.................................................................................................. 7-5

SONET/SDH Diagnostics................................................................................................7-6

SONET/SDH Performance Monitoring............................................................................7-9

032R401-V722 Xedge MSPx System Version 7.2.2 iiiIssue 1 Configuration & Diagnostics Guide

Table of Contents

4

6

3

7

3

1

4

0

1

SONET/SDH Alarms.....................................................................................................7-12

SONET/SDH Automatic Protection Switching................................................................... 7-15

APS Group Configuration..............................................................................................7-15

APS Link Configuration.................................................................................................7-19

APS Alarms....................................................................................................................7-2

SONET/SDH Defects........................................................................................................... 7-2

DLIMs .................................................................................................................................. 7-31

DS1-2C/4C Links Configuration......................................................................................... 7-31

E1-2C/4C Links Configuration............................................................................................ 7-34

DS3 or E3 LIM Configuration............................................................................................. 7-37

Define the LIM in Slot-0................................................................................................7-37

Configure PLCP Framer.................................................................................................7-39

DS3-2C LIM Configuration................................................................................................. 7-43

Define DS3-2C Framer Mode........................................................................................7-43

Configure DS3-2C DLIM ..............................................................................................7-45

E3-2C LIM Configuration.................................................................................................... 7-47

Define the E3-2C Framer Mode.....................................................................................7-47

Configure E3-2C DLIM .................................................................................................7-49

IMA LIMs ............................................................................................................................ 7-51

IMA Configuration Overview........................................................................................7-51

IMA Group Bandwidth...................................................................................................7-52

E1 IMA Configuration......................................................................................................... 7-5

DSX-1 IMA LIM Configuration.......................................................................................... 7-55

IMA Configuration............................................................................................................... 7-5

SFP Tranceivers................................................................................................................... 7-6

Chapter 8: Alarm HandlerOverview................................................................................................................................ 8-1

Monitoring Alarms................................................................................................................. 8-

Reclassifying Alarms............................................................................................................. 8-

Configuring User Status Inputs.............................................................................................. 8-8

User Status Inputs Procedure............................................................................................8-8

Inhibiting Alarms................................................................................................................. 8-1

Alarm Classification File................................................................................................8-10

Alarm Relay Cut-Offs (ACO)........................................................................................8-10

Appendix A: OSPF CLI ReferenceOSPFv2 Protocol................................................................................................................... A-

OSPF Command Modes........................................................................................................ A-1

OSPF Guidelines and Examples........................................................................................... A-2

iv Xedge MSPx System Version 7.2.2 032R401-V722Configuration & Diagnostics Guide Issue 1

Table of Contents

2

3

0

VTY Shortcuts and Tips..................................................................................................A-2

Accessing VTY................................................................................................................A-

Sample Sessions..............................................................................................................A-

OSPF Command Reference.................................................................................................. A-4

OSPF Router Commands.................................................................................................A-4

OSPF Area Commands....................................................................................................A-5

OSPF interface Commands.............................................................................................A-7

Redistribute Routes to OSPF...........................................................................................A-8

Show OSPF Information.................................................................................................A-9

Debug OSPF..................................................................................................................A-1

032R401-V722 Xedge MSPx System Version 7.2.2 vIssue 1 Configuration & Diagnostics Guide

Table of Contents

vi Xedge MSPx System Version 7.2.2 032R401-V722Configuration & Diagnostics Guide Issue 1

PCX f

g up ith

he ly

ts eneral

efer to of

(GDC n pliance

ual,

Preface

Scope of this ManualThis manual describes how to configure Xedge MSPX Version 7.2.2 Slot Controllers (ISG2,and PCL), and their supported LIMs. All information refers to currently supported versions oswitch code, except where noted. Related Publications are listed on the inside front cover of thisdocument.

This information is intended for qualified operators and administrators experienced in settinand managing MPLS and ATM traffic and signaling in Xedge networks. Wiring must comply wthe local electrical codes in your area that govern the installation of electronic equipment. Tinformation contained in this manual has been carefully checked and is believed to be entirereliable. As General DataComm continually improves the reliability, function and design of iproducts, it is possible that some information in this document may not be current. Contact GDataComm, your sales representative or point your browser to http:\\www.gdc.com for the latest information on this and other General DataComm products.

General DataComm, Inc.6 Rubber Avenue, Naugatuck, Connecticut 06770 U.S.A.Tel: 1 203 729-0271 Toll Free: 1 800 523-1737

Software Version HistoryThis document supports the Xedge Switch Software Version 7.2.2 at Patch 3 and above. Rthe latest issue of the Xedge Version 7.2.2 Release Notes for a version-based comparisionfeatures. Refer to the Version 7.2.2 Cumulative Patch Notes as they become available.

Hardware InstallationBefore using this manual, refer to the latest issue of the Xedge Hardware Installation Guide P/N 032R440-000) for module information, specfications, hardware setup and instructions oinstalling modules in the proper slots of an Xedge chassis. Be sure to read all safety and cominformation in the Preface of that document before applying chassis power to any module.

Manual OrganizationThis manual is divided into the following chapters. When using the digital version of this manclick on any link (shown in blue text) to jump to that section.

• Chapter 1, Xedge Switch Overview

• Chapter 2, Accessing Slot Controllers

• Chapter 3, Basic Slot-0 Configuration

• Chapter 4, ISG2 Configuration/Status

• Chapter 5, PCX Configuration/Status

• Chapter 6, PCL Configuration/Status

• Chapter 7, LIM Configuration

• Chapter 8, Alarm Handler

• Appendix A, OSPF CLI Reference

032R401-V722 Xedge MSPx System Version 7.2.2 viiIssue 1 Configuration & Diagnostics Guide

Preface Support Services and Training

re-and

nt, ck,

omers f GDC DC

nd ff used port the

anges n the

Support Services and Training

General DataComm offers two comprehensive customer support organizations dedicated to ppost-sale support services and training for GDC products. Corporate Client Services and Factory-Direct Support & Repair assist customers throughout the world in the installation, managememaintenance and repair of GDC equipment. Located at GDC’s corporate facility in NaugatuConnecticut USA, these customer support organizations work to ensure that customers getmaximum return on their investment through cost-effective and timely product support.

Corporate Client Services

Corporate Client Services is a technical support and services group that is available to GDC customers throughout the world for network service and support of their GDC products. Custget the reliable support and training required for installation, management and maintenance oequipment in their global data communication networks. Training courses are available at Gcorporate headquarters in Naugatuck, Connecticut, as well as at customer sites.

Factory Direct Support & Repair

GDC provides regular and warranty repair services through Factory Direct Support & Repair at its U.S. headquarters in Naugatuck, Connecticut. This customer support organization repairs arefurbishes GDC products, backed by the same engineering, documentation and support stato build and test the original product. Every product received for repair at Factory Direct Sup& Repair is processed using the test fixtures and procedures specifically designed to confirmfunctionality of all features and configurations available in the product.

As part of GDC’s Factory Direct program, all product repairs incorporate the most recent chand enhancements from GDC Engineering departments, assuring optimal performance whecustomer puts the product back into service. Only GDC’s Factory Direct Support & Repair can provide this added value.

Contact Information

General DataComm, Inc.6 Rubber AvenueNaugatuck, Connecticut 06770 USAAttention: Corporate Client Services

Telephones: 1 800 523-1737 1 203 729-0271Fax: 1 203 729-3013Email: [email protected]

General DataComm, Inc.6 Rubber AvenueNaugatuck, Connecticut 06770 USAAttention: Factory Direct Support & Repair

Telephones: 1 800 523-1737 1 203 729-0271Fax: 1 203 729-7964Email: [email protected]

Hours of Operation: Monday - Friday 8:30 a.m. - 5:00 p.m. EST

(excluding holidays)

http://www.gdc.com

viii Xedge MSPx System Version 7.2.2 032R401-V722Configuration & Diagnostics Guide Issue 1

roller pter cribes

s cell s and /ices.

ric

. The fabric

0).

ode:

elay

ell ath ttach the

llers g

s aded

gement.

are are and uration

Chapter 1: Xedge Switch Overview

Introduction to Xedge Version 7.xThe Xedge Multi-Service Packet Exchange (MSPX) switch is comprised of Packet Slot Contmodules and Line Interface Modules (LIMs) controlled by Version 7.x switch code. This chagives a brief overview of the hardware modules, Version 7.x software organization, and desthe available file commands.

Note An Xedge switch can function with more than one type of Xedge slot controller. If your switch containcontrollers (ACP, ACS, ECC) or adaptation controllers (ETH, FRC, CHFRC, CE, VSM), those devicetheir LIMs are controlled by Version 6.2 switch code. Refer to the Xedge 6000 Ver. 6.2 ConfigurationDiagnostics Guide (032R400) listed in the front of this document to configure and manage those dev

Xedge Switch Fabric ModulesIn higher density Xedge switches (Xedge 6640, 6645, 6280 or 6160), the Xedge Switch Fabmodules plug into one or two dedicated slots at the front of the chassis, labeled SF Main and SF Standby . In these switches, the Switch Fabric is responsible for transporting cells simultaneously to 16 slot controllers in the switch, at 400 Mbit/s throughput in each directionXedge 6002 switch has no provision for the Switch Fabric modules, since the integral switch in the ISG2, PCx and PCL slot controllers are sufficient for that 1RU chassis.

Note For Xedge Switch Fabric information, refer to the Xedge6000 Hardware Installation Manual (032R44

Xedge Slot ControllersAn Xedge switch may have three types of slot controllers, under Ver 6.2 or Ver 7.x switch c

• Adaptation Controllers (Version 6.2) connect existing network technologies, e.g., Frame Rand Ethernet, to the ATM switch.

• Cell Controllers (Version 6.2) provide dedicated ATM cell interfaces and perform ATM cprocessing functions such as traffic management and Virtual Channel Identifier/Virtual PIdentifier (VCI/VPI) translation. These physical interfaces connect Xedge switches, and aLAN hubs, high performance workstations and other local devices with ATM interfaces toXedge switch.

• MultiService Packet Exchange Controllers (Version 7.x) employ ATM/MPLS transport toconverge Layer 2 and Layer 3 switching of “any-to-any” services. These “packet” controhave the multi-service capability that interconnects remote enterprise sites with emerginEthernet/IP and legacy services across an MPLS or ATM WAN.

Each slot controller has an independent SNMP agent configured with MIBs appropriate to itfunction. All operating software is held in flash EPROM, enabling operating code to be downloto accommodate new features as well as changing standards.

A management subsystem processor controls non-data path functions, such as SNMP manaEach slot controller has its own SNMP agent configured with its corresponding MIBs. The subsystem processor checks the status of hardware at boot time and loads the correct softwversion. After start-up, the subsystem processor monitors the status of the data path hardwtakes actions as required. Xedge supports upload/download of operating software and configfiles to/from the network management system via the TFTP protocol.

032R401-V722 Xedge MSPx System Version 7.2.2 1-1Issue 1 Configuration & Diagnostics Guide

Xedge Switch Overview Introduction to Xedge Version 7.x

d in

-0 in any

, the at the

le is rs. The

, the rder to

vides .

kets

Module ignals.

fer to

ersion,

Version 7.x Slot Controllers and LIMs

Xedge Version 7.x software controls the following packet slot controllers and LIMs, describethis document:

• ISG2 Slot Controller (See Chapter 4, ISG2 Configuration/Status )

• PCx Slot Controller (See Chapter 5, PCX Configuration/Status )

• PCL Slot Controller (See Chapter 6, PCL Configuration/Status )

• Line Interface Modules (See Chapter 7, LIM Configuration )

Slot-0 Controller Functions

In any Xedge MSPX switch, all packet controllers (ISG2, PCX and PCL) are capable of slotfunctionality. The ISG2 is also capable of slot-0 redundancy when installed in a chassis withprovisions for a Main and Standby slot-0. In general, a packet slot controller can be installed slot of any chassis, as long as a packet controller of any type is the slot-0 controller.

A Packet Controller in slot-0 provides the following slot-0 functions:

• Provides system-wide facilities, such as control of fault tolerance.

• Provides slot-0 redundancy (ISG2 only). When the Xedge switch has slot-0 redundancyISG2 modules are configured for redundancy and installed in two dedicated slot-0 slots Xedge switch front panel: Main and Standby.

• Runs a background task that sends health check cells to all of the other slots. If a moduactive in a slot, it responds with its state, type, software version number and serial numbeslot-0 controller is thus aware of the overall slot configuration of the switch.

• Maintains the PVC tables. PVCs are configured only on slot-0. When a PVC is activatedslot-0 controller sends appropriate messages to each link involved in the connection in oestablish the circuit.

• Runs the local management service that supports a VT100 terminal (craft) port. Also prothe IP address for remote access to slot-0 and non slot-0 controllers via Telnet interface

• Acts as a router for the virtual IP Management Overlay Network within the switch. IP pacare sent to and from slot-0 for routing.

• Allows the switch to operate with Adaptation and Cell controllers in non slot-0 positions.

Note An Xedge 6640 or 6645 switch not configured for slot-0 redundancy must have a System Termination (P/N 032P105-001) in the redundant Slot-0 position. STM monitors and conditions the system clock s

Note For compatibility and performance information on any Xedge Slot Controller and associated LIMs, reTable 0-2 in the Xedge / ProSphere Quick Reference (032R299).

Note To install Xedge modules, refer to the latest Xedge HardwareInstallation Guide (032R440-000.To load or update Xedge switch code, refer to the Xedge Software Release Notes for your software vor contact your authorized service representative.

1-2 Xedge MSPx System Version 7.2.2 032R401-V722Configuration & Diagnostics Guide Issue 1

Xedge Switch Overview Xedge Software Overview

ion to er slot

es

ation

he d for

ther nces s.

and is

a to a

d.

al

ent

f the work

Xedge Software Overview

Xedge switch software consists of operating code and configuration data. Xedge software installation consists of sending updated files to the slot-0 controller via a direct serial connectthe Xedge switch rear panel Management (craft) port. The files are then distributed to the othcontrollers in the switch. In most cases, Xedge software is pre-loaded at the factory.

Note To upgrade Xedge software or install a new Slot Controller in an Xedge switch, refer to the procedurprovided in the Xedge Release Notes for your specific software version or patch.

Software Files and Functions

Each slot controller in the Xedge switch stores all run-time operating code files and configurinformation in a solid state nonvolatile memory device (flash EPROM). The flash EPROM functions as a virtual disk drive. Thus, each controller module runs identical software in its subsystem processor. Various parts of the software are enabled or disabled depending on tmodule type and which Daughter Option Card (DOC) is fitted. Extra code files may be requirethe particular interface types in use.

Flash EPROMs retain the information written to them even after power is removed. Unlike oEPROMs, flash EPROMs can be electronically erased relatively quickly, which greatly enhatheir ability to mimic disk drive operation. A flash EPROM supports hundreds of erase cycle

The subsystem processor software is loaded from the flash EPROM virtual disk at boot timestored in a slave.cod file for all controller modules except ACP and ACS. The subsystem processor software for ACP and ACS modules is stored in the mpro1.cod file. The operating code uses a multi-tasking, message passing operating system as its kernel. Configuration information is stored in a plain ASCII text file config.cfg .

Managing Software Files

The virtual disk drive capability of flash EPROM provides a number of file management advantages, listed below. Refer to File System Commands in the next section for detailed procedures.

• Configuration files can be copied and saved to disk. You should do this before modifyingconfiguration so that the configuration can be reloaded if it becomes necessary to revertprevious configuration.

• Test configurations can be created and saved to disk for loading at a later time as neede

• Operating code can be copied and saved to disk. You should do this before loading a triversion of code for testing and then load back the regular version for normal operation.

• The switch supports TFTP (Trivial File Transfer Protocol) so that files can be transferredbetween modules, between flash EPROM virtual drives, and to/from a network managemcontroller.

• Since each slot controller has its own virtual disk drive, you can load different versions ooperating software on different slot controller modules. Thus, smaller portions of the netare effected during a software upgrade.



ch select

f

pears,

ding

elow:

the

xtra

w.

area.

Xedge Terminal InterfaceThe terminal interface provides craft or Telnet access to the switch modules and to the switsoftware files. The example screens below give a quick overview of how to navigate menus,options and execute commands at this interface.

• To access a slot controller from the root menu, type T (elnet) and then type the IP address othe desired slot controller at the prompt.

• To select an other options from the root menu, type the bold capital letter in the option description. A corresponding screen appears for that function, or the action is executed.

For example, at the Root Menu screen, select the Manage configuration option by simply type m, the underscored letter in the menu item. The MIB Display and Management screen apas shown in the lower screen, shown below.

To select a menu option from the MIB Display and Management screen, type the corresponoption number and then press the Enter key. The switch will perform that action or display acorresponding subscreen.

Common navigation and executable functions used on most Xedge subscreens are listed b

• Add entry: Brings up a new line for entering additional information.• Down (Up): Down moves to the next lower screen, e.g., from link 1 to link 2. Up moves to

next upper screen, e.g., from link 2 to link 1.

• Enter entry number to edit: Type the number associated with the row you wish to edit.

• Extra detail: Brings up a screen with all MIB items for that row.

• Goto row: Jumps to a particular row by moving that row to top of the screen. Selecting Edetail brings up the detail for that row.

• Kill entry: Prompts for a row number to be deleted. Press Enter to delete that row.

• Move entry: Prompts for a row number where you can change parameters within that ro

• ^J for extra help: Activates a help function for the selected item.• Right (Left): Shifts screen items Right or Left when more columns exist beyond viewable

• Summary: Dismisses the Extra detail and returns to previous screen.

• eXit: Returns to the top level screen.

Xedge Switch: Slot 0 Root Menu 720\700

Slot 00 : Active PCx Received datacells = 118442Slot 01 : -------- Transmitted datacells = 294679Slot 02 : Active sdhSlot 03 : Active pdhSlot 04 : Active pdhSlot 05 : --------Slot 06 : Active ceSlot 07 : --------Slot 08 : -------- User: rootSlot 09 : -------- From: telnetSlot 10 : --------Slot 11 : -------- Slot 0 Redund. available: NoSlot 12 : -------- Slot 0 Redund: Main In-servSlot 13 : -------- Sys. Ref. Loc:0: No InfoSlot 14 : -------- SVCs Connected: 0Slot 15 : -------- PVCs Connected: 1 File transfer: InactiveSelect option:Diagnostics, Events, File system, Internal status,Manage configuration, self Restarts, Telnet, sVc routing,Warm start, eXit, LinK

Hartford: Slot 0 MIB Display and Management New Event

00 system 42 Alarm Handler01 interfaces 43 CAC Configuration03 ip 69 Port, Link#, Location, ifIndex Map04 icmp 70 LIM and Link Information05 tcp 74 Ethernet Virtual Connections06 udp 82 Ethernet Statistics07 snmp 83 802.1d Bridging08 System Information 84 MPLS Label Switch Setup and Status09 Slot 0 Configuration/Status 85 PseudoWire Services12 Static Routing 94 Management IF16 Virtual Circuit Status 95 Node Status19 DSP DLIMs 97 IMA23 PVC Configuration/Status 101 QAAL224 SVC Configuration/Status27 System Timing References39 PDH Configuration/Status41 ILMI Configuration/Status

Select option:Enter group number, save As, Load, sTatus, eXit,Last save file is `/mnt/flash0/config.cfg'.

Type M



mands ile

on

e

File System Commands

The Xedge root menu provides a File Operations screen that allows you to execute file comon files stored on the virtual disk drive. The following paragraphs describe commonly used fsystem commands.

From the Root Menu select File system . The File Operations screen appears with an optimenu, as shown below.

When using the Xedge file commands, be aware that Xedge file names have the following characteristics:

• The file name maximum length is 11 alphanumeric characters.

• Periods (. ) are not a special characters, so file name suffixes can be more than threcharacters.

• Slashes (/ ) separate directory paths.From the Root Menu select File system . The File Operations screen appears with an option menu, described below.

Hartford: Slot 0 File Operations New EventCurrent directory: /mnt/flash0/

Select option:Alter file, Copy file, Directory, Erase file, Rename file,vital Product info, Scan file, TFTP menu, eXit



hown y.The

Directory CommandType D from the File System screen to displays a directory of the disk, similar to the screen sbelow. By default the directory command shows all the files in the currently selected directormask is set to * ; the default path is the root path - / .

1. To specify a different mask, select the Mask option. Note that (. ) is not a special character, sothat a mask of *.* only shows files that contain a full stop as part of their names.

2. To change the path, select the Path option.

3. To see more information about the files, select Extra detail . The Directory Extra Detail screen appears, similar to the example shown below.

The Directory Extra Detail screen shows:

• the name and size of the file

• the name of the user (owner) who created the file, the time and date it was created

• the type of read/write status (Table 1-1 lists the types of read/write access.)

• the version number of the .cod or .bin file

• whether the file is open (Yes or No )

Note If there are more files on the disk than can be displayed on the screen, the Up and Down options appear. You can also use CTRL-W and CTRL-Z keys to scroll the display one line at a time.

Table 1-1 File Access Status Types

File Access Status Description

All RW All can read and write the file.

All RO All can only read the file.Own RW The owner can read and write the file.Own RO The owner can only read the file.

Hartford: Slot 0 Directory 720v1\700Name Size Name Size------------------------------------------------------------------------------<snmp> startup_pcx.tz 5895864<zebra> config.cfg 47122one 4172 pcxmfg4.cfg 42315def.rtb 1001 alr_cls.txt 1915hosts 47 pcxmfg.cfg 47002ecc.cod 1159861dtl.bin 757dec10.cfg 47333restart.slv 1970slavepnni.cod 658987config214.cfg 47333slave.cod 639032oc12.cod 228404jan0308.cfg 47077mpro1.cod 861484mpro2.cod 1159634Select option:Extra detail, Path, eXit

Hartford: Slot 0 Directory New EventName Size Owner Created Access Ver Open-------------------------------------------------------------------------------<snmp><zebra>>one 4172 root Mon Dec 10 18:20:29 2007 644 ?>def.rtb 1001 root Tue Feb 5 15:56:51 2008 600 ?>hosts 47 root Thu Jan 24 14:36:31 2008 644 ?>ecc.cod 1159861 root Sat Nov 10 12:15:21 2007 640 620v13>dtl.bin 757 root Tue Feb 5 15:56:52 2008 600 0.208>dec10.cfg 47333 root Tue Feb 19 11:45:38 2008 644 ?>restart.slv 1970 root Tue Feb 26 10:56:12 2008 644 ?>slavepnni.cod 658987 root Sat Nov 10 12:15:44 2007 640 620v13>config214.cfg 47333 root Thu Feb 14 09:56:38 2008 644 ?>slave.cod 639032 root Sat Dec 15 11:53:20 2007 640 620v14>oc12.cod 228404 root Fri Nov 30 14:11:28 2007 644 0.09>jan0308.cfg 47077 root Thu Jan 3 13:56:02 2008 644 ?>mpro1.cod 861484 root Tue Jan 29 11:50:39 2008 640 620V15>mpro2.cod 1159634 root Tue Jan 29 10:56:09 2008 640 620v15Select option:Down, Path, Summary, eXit



he

omplete.

s the the

create

keys (or

Copy a File

The Copy File command overwrites an existing file or creates a copy with a new file name.

1. From the File Operations screen, type C to begin the Copy File process. The Select File screen appears.

2. Use the arrow keys (or CTRL-B and CTRL-N ) to move the highlight to the desired file.(As an alternative, you can type the file name at the <...> field).

3. After highlighting or typing file name, press the spacebar to select the file for copying.

4. At the prompt, type a new file name to create a separate copy, or move the highlight to tsame file name to overwrite the file.

5. Press the spacebar to proceed. A progress bar indicates the when the copy process is cAn error message appears if the copy fails.

6. Press the esc key to return to the File Operation screen.

Erase FileType E from the File System screen to erase a file from the disk. Selecting this option openstandard Select File screen. Select the file in the usual way. You will be prompted to confirmdeletion before the file is removed. Press the esc key to abort the function.

Alter a File

The Alter File command is a screen text editor that allows you to use the terminal interface to and modify the ascii configuration files, hosts files, etc.

1. From the Root Menu select File system . The File Operations screen appears.

2. From the File Operations screen, type A to access the Select File screen, shown below. The <...> field is highlighted.

Figure 1-1 Select File Screen

3. Type the file to be altered and then press the spacebar. As an alternative, use the arrow press CTRL-B or CTRL-N ) to move the highlight to the desired file, and then press the spacebar to select the file.

4. The text editor opens the ASCII file. To view editing command help, type CTRL-J .

5. When edits are done, exit the text editor by typing CTRL-K. You will be prompted to

• Save changes

• Save changes and Exit

• Quit with No Save

• Return to the Editor.

Hartford: Slot 0 Select File New Event

File to editCurrent directory: /mnt/flash0/--------------------w---------------------w-------------------------------------<..> x <snmp> x <zebra>one x def.rtb x hostsecc.cod x dtl.bin x dec10.cfgrestart.slv x slavepnni.cod x config214.cfgslave.cod x oc12.cod x jan0308.cfgmpro1.cod x mpro2.cod x startup_pcx.tzconfig.cfg x pcxmfg4.cfg x alr_cls.txtpcxmfg.cfg x

Type file name or use ^B, ^N to move,space to select file. Type * or ? to change mask, esc to abort.



P

ote

slot

nd the he file ransfer.

re it pecify

ed, ss or

the file

TFTP Functions

From the root menu, type F to access the File System screen, then type T to access to the TFTPStatus and Control screen, as shown below. This screen shows the status of any active TFTtransfers, and also allows you to Send or Get files.

Note IMPORTANT! Do not attempt to send or receive files to or from the slot controller you are using.

Sending Files

1. At the TFTP Status and Control screen, select the Send file option to send a file to a remhost.

2. At the Select File prompt, select the file to be sent.

3. At the IP prompt, enter the destination IP address for the file. If sending a file to anotheron the same switch, simply enter slot n, where n is the slot number of the target slot.

4. Once the target destination is specified, the TFTP Status and Control screen appears atransfer begins. The status line will show target destination, the state of the transfer and tname being transferred. The display automatically updates to show the progress of the t

Broadcasting Files

The Broadcast file option is used in those situations, such as software upgrades, wheis necessary to send the same file to all the slots in the switch. When you select this option, sa file name as usual. The file will then be sent to all slots in the Xedge switch.

Getting Files

Use the Get file option to fetch a file from a remote host or slot controller. When promptprovide the file name to get from the remote system. Then provide the remote host IP addrespecify the slot n, if n is the slot number where the file resides.

Note TFTP writes over the file if it has the same name as an already existing file. To prevent this, change name during the TFTP transfer.

system-1:Slot 0 SYS TFTP Status and Control# T/O:No Remote State Filename

0 20 :0 192.1.1.16:69 Sent 1024 bytes /hosts1 -1 -2 -3 -4 -5 -6 -7 -8 -9 -10-11-12-13-14-

Select option:Broadcast file, Channel number for detail, Get file, Kill, Send file, change Timeout, eXit



ile or

3

d creen ck.

Other TFTP Commands

• The Kill command will terminate a TFTP session after the TFTP has started a Send fGet file transfer.

• Change Timeout command allows you to adjust the retransmit timer. The total timeout istimes the retransmit timer. Typically, this command is used on a congested network.

Detailed Status

A detailed display of a particular TFTP channel is available for system level debugging. Thisdisplay is typically not use for day-to-day management of the switch. At the TFTP Status anControl screen, type the desired channel number. A Detailed Display of the TFTP Channel sappears as shown below, showing various system level parameters for the TFTP control blo

system-1:Slot 0 SYS Detailed Display of TFTP Channel

State: 0, last packet type: 3.In: ac 10 07 05 f6 f2 00 45 00 04 00 26

Out: ac 10 07 05 f6 f2 00 45 00 03 00 26 30 35 5d 3d 31 0a 69 6e 64 65 78 3d31 34 0a 69 6e 5b 30 30 5d 3d 31 34 0a 65 6c 5b 30 31 5d 3d 31 0a 65 6cOut length: 257, in length: 4, Ackno: 39.

Bytes sent: 19197, Bytes received: 0.Needack flag: 0, timeout: 0, timeoutcount: 2.Success flag: 0, Target: 172.16.7.5.Current state: Send OK. local port: 69

Select option:eXit



pecial of

lists arious d traps nts log

ating ating

n is

d.

Special Root Menu Functions

The Root Menu provides option commands used for special functions, listed below. Some sfunctions displayed at the Root Menu may not be available or supported under your versionXedge switch code.

Events Option

Selecting the Events option at the Root menu displays the Events log screen. This screencommon system occurrences, too many to list, ranging from the status of slot controllers to vTFTP states. Other common events displayed on this screen are the status of active links angenerated by the system. A maximum of 160 events can be stored in the events log. The evecan also be saved as a text file that can be printed for further analysis of a system event.

Warm Start Commands

• The Normal Warm start command is used to restart the processor and load new configuration parameters from memory for a specific slot controller. For A-series Cell Controllers, decompression is used.

• The Force Warm start command is used to restart the processor and reload the opersystem from flash memory. When Force Warm start is used, decompression of the opersystem is performed.

Zap Cell Interface

This function is used only with ETH, CHFRC and FRC slot controllers. Typically, this functioused at the factory to synchronize the master and slave processors. Selecting the Zap cell interface function causes the following actions:

• resets the 040 master processor

• reloads the binary software file

• reloads the 040 portion the config.cfg file

Once the function is selected, you will be prompted for the name of a configuration file to loaTypically this is the config.cfg file.

Note The Zap Cell Interface is a maintenance tool for authorized Xedge service use only. It is not asupported user feature.


Xedge Switch Overview SAPs and ATM Logical Ports

SAP

thing.)

ese, 4 to 79.

with to

16, AP

:

t.

Cx, SAPs e

SAPs and ATM Logical PortsPacket slot controllers support 96 Signaling Access Points (SAPs) as described below. Thedefaults and associated ATM port assignments are shown in Table 1-2.

• SAPs 0 to 15 are the virtual SAPs to slots 0 to 15 and are fixed.

• SAPs 16 and 17 are adaptation SAPs for the base card and are fixed.

• SAPs 18 to 79 are logical SAPs (This is a pool of SAPs that can be assigned to any

There are 70 ATM ports:

• ATM ports 0 and 1 are used for adaptation on the base card.

• ATM ports 2 to 69 are logical ATM ports (they are not connected to anything).

Physical ports consist of Physical ATM LIM ports, pseudowires and adaptation ports. All of thby their nature, are not connected to anything. Pseudowires 38 to 63 are assigned to SAPs 5Note that Pseudowires 64 to 69 do not have SAP associations in the default configuration..

ISG2 Exceptions• ISG2 does not support QAAL2 SAPs.

• For the ISG2, Logical SAPs are UNI only.

PCL Exceptions

• PCL supports four SAPs (management PVCs) per ATM port or IMA group.

PCx Exceptions• QAAL2 physical SAPs can only be used for NNI ports, with each QAAL2 SAP associated

the corresponding first 16 ATM logical SAPs configured for NNI, as follows: 80 to 16, 8117, and so forth.

• There are 16 QAAL2 physical SAPs associated with the first 16 ATM logical SAPs (80 to81 to 17, and so on). That is, the ATM logical SAP and the associated QAAL2 physical Suse the same ATM port number.

• There are only three configurable items for the QAAL2 physical SAP: Signalling VCI, ATM port number and SAP Status.

• When ProSphere Routing Manager (RTM) is used, the PCX has the following limitations

• SAP must be turned on; otherwise, the link or connection is considered nonexisten

• Only SAPs 16 to 19 can be used for RTM links 0 to 3.

• SAPs 20 to 31 are used for RTM links 4 to 15. When using SAPs 20 to 31 on the Pthe other side must be configure for SAPs 20 to 31 also. For example, if one side is20 to 31 and the other side is SAPs 0 to 3, then the connection is invalid and will bignored by RTM.

• SAPs 32 to 63 may be used for UNI links. When PNNI is in use, there is no such restriction on the SAPs.

Table 1-2 Default SAP and ATM Port Assignments

SAP Numbers Description Default ATM Ports

0 through 15 16 Fixed ATM Virtual SAPs connect to slots 0 to 15 --

16 - 63 ATM Logical SAPs (UNI) 0 - 47

64 - 79 QAAL2 Virtual SAPs --

80 - 95 16 QAAL2 Physical SAPs --


Xedge Switch Overview SAPs and ATM Logical Ports

t.

Routing & Interfaces

The routing function on packet controllers supports interface connections as depicted in Table 1-3 and the accompanying table.

When specifying a default gateway in the ISG2 Status Route Table, you must use interface IfIndex0 , and a Metric of 15 in order to direct management traffic to the management porCorrect interface and metric entries are shown in the example Static Route Table below:

Network: 0.0.0.0 Mask: 0.0.0.0Gateway: 172.16.10.10Metric: 15IfIndex: 0

Table 1-3 Interface Description

ISG2 or PCLIF Index

PCXIF Index

IF Index Description

1 1 Software loopback on this card3 (Future Use) (Future Use) Br0 Bridge

41 through 55 41 to 55 Connection to slots 1 thru 1564 through 127 64 to 127 Connection for Links on slots 1 through 15 on ports 0 through

3The value of the index is 64 + (4 x slot #) + link #For example, to slot 2 Link 1 = 64 + (4 x 2) + 1 = 73

1004 through 2515 1004 to 2515 For connection to cards with more than 4 links:Connection for Links on slots 1 thru 15 on ports 4 thru 15The value of the index is 1000 + (100 x Slot#) + link#For example, to slot 14 link 6 = 1000 + (100 x 14) + 6 = 2406

3001 through 3128 3001 to 3128 Tunnel terminations4000 4000 eth0 (MGMT)4001 4001 eth1 (USER

(Not supported) 4100 to 4115 Ports on Back LIM 1(Not supported) 4200 to 4215 Ports on Back LIM 2(Not supported) 4300 to 4301 GIG E Ports

(Not supported) 4302 to 4309 10/100 Ports

ROUTER

MGMT

USER

To Slots 1 - 15To Links 0 - 3on Slots 1 -15

To Links 4 - 15on Slots 1 -15

Tunnels 1-128

10/100 Ports GIG E PortsLIM 2 PortsLIM 1 Ports

PCX ONLY


d LIMs he IB II) tch via re that n.

n

You

n table resses

nu.

a.

C, 0 Ver. s.

e

rdware

Chapter 2: Accessing Slot Controllers

Management Access OverviewThis chapter describes accessing Xedge ISG2, PCX and PCL slot controllers and associateinstalled in your Xedge switch via a craft or Telnet management interface. Xedge supports tstandard Simple Network Management Protocol Management Information Base II (SNMP Mgroup, and a series of Enterprise MIB extensions for total management and control of the swithe SNMP interface. The Xedge switch supports common and Xedge-specific traps to ensuevents happening inside the Xedge network are reported to an external management statio

Note For more information on SNMP Authentication and Traps, refer to Chapter 3, under the paragraphs oSNMP Authentication and SNMP Traps .

Xedge uses SNMP for system configuration and monitoring over an IP network connection.can obtain SNMP access to the Xedge Switch in one of two ways:

• Internet Protocol (IP) via an Ethernet management port

• Internet Protocol (IP) via an in-band Management OverLay Network (MOLN)

Access control is provided by a number of security mechanisms, described in this chapter:

• Multi-level passwords

• Craft port security key

SNMP access can also be secured at the terminal interface by configuring the authenticatioin the slot-0 controller. This allows the supervisor to restrict access to users with valid IP addand SNMP community strings. Refer to Chapter 3, Basic Slot-0 Configuration for details.

Access OverviewThe Xedge Version 7.2.X switch is accessed with a root or admin login via Telnet or craft connection, using the default password MANAGER.

• A successful admin login will advance immediately to the Root Menu. A successful root login will activate a 3-second interval and then display the Root MeIf you press Ctrl-C during the 3-second interval, you will access the root prompt.

• Only one Telnet admin session is allowed at a time, however a second admin login is allowed at the craft serial interface. Take care when conducting a second admin login, since resources will be shared. Changes made via craft will overwrite Telnet, and visa- vers

• Multiple Telnet root sessions are allowed to superusers only.

Note If your Xedge switch contains Cell Controllers (ACP, ACS, ECC) or Adaptation Controllers (ETH, FRCHFRC, CE, VSM), those devices are controlled by Version 6.2 switch code. Refer to the Xedge 6006.2 Configuration/Diagnostics Guide (032R400) to configure and manage those devices and their LIM

Note For information on management access via the ProSphere Network Management System, refer to thdocumentation listed on the inside cover of this manual.

Note For a list of all Xedge connection cables, chassis and modules, refer to the latest issue of the Xedge HaInstallation Guide (032R440-000).


Accessing Slot Controllers Craft/Telnet Connections

t al craft On all SMM)

100 edge

your

edge

, you tion.

r 6280).

Craft/Telnet ConnectionsTelnet access to the Xedge menu-driven configuration system is supported from any IP hosconnected to the Xedge management network. VT100 terminal access is provided via a seriport on the chassis. On the Xedge 6002 chassis, use the RJ45 Craft port at the front panel.other Xedge chassis, use the serial DB9 or DB25 port on the System Management Module (at the rear panel.

To make a craft connection to slot controllers, use a VT100 emulation program that allows switching to the DOS command line. Authorized Xedge service engineers typically use a VTemulation program such as Procomm Plus (R). VT100 emulation settings are preset in the Xswitch code and cannot be changed by the user.

1. On the SUN workstation or PC, ensure your VT 100 emulation settings are as follows:

19,200 baud

8 data bits

parity=none

1 stop bit

Note IMPORTANT! For the PCL controller in a Xedge 6002 chassis, the baud rate must be set to 9600. If PCL application requires a different rate, contact your Xedge representative.

2. Connect your PC or SUN workstation serial port to the Manager (or Craft) port on the Xchassis. Table 2-1 lists serial cables required for each Xedge chassis system.

• For a SUN workstation, use the serial cable to connect the ttyb port on the workstation to the craft port on the Xedge chassis.

• For a PC, use the serial cable to connect the com1 or com2 port to the craft port on the Xedge chassis.

• For a redundant slot-0 configuration on chassis with Main and Standby slot-0 slotsmust use a Y-cable along with the correct serial cable for your PC or SUN worksta

Note Slot-0 redundancy is only supported in chassis that have Main and Standby Slot 0 slots (6640, 6645 o

Table 2-1 Serial Craft Port Cables

Management Connection Xedge Connection GDC Part No. Cable Description

SUN Workstation (DB25M) 6640 or 6645 (DB25M) 28H502 Serial, DB25M to DB25M

6160 (DB9M) 28H346 Serial, DB25M to DB9M

6002 (RJ45) TBD Serial, DB25M to RJ45

PC Workstation (DB9F) 6640 or 6645 28H303 Serial, DB9F to DB25M

6160 or 6280 27H329 Serial, DB9F to DB9M

6002 029H015-001S-078H010-XXX

Serial DB9F to RJ45Ethernet RJ45 to RJ45

Y-Cable for Redundant Slot-0 (with 6280 and serial cable) 28H350-X06 Serial Y, DB9F to dual DB9Ms

Y-Cable for Redundant Slot-0 (with 6640 or 6645 and serial cable) 28H618-X06 Serial Y, DB25F to dual DB25Ms


Accessing Slot Controllers Craft/Telnet Connections

ge Root old

s or Switch

tom of

not ing on

Navigating Xedge Menus and Screens

Selecting Root Menu Options

All configuration and status functions described in this document are executed from the Xedterminal interface root menu and the Xedge sub screens, as shown in the examples below. menu options are listed at the bottom of the screen. To select a root menu option, type the bcapital letter in the word describing the option. The terminal interface will display the corresponding Xedge menu, or execute an action immediately.

Selecting Group Options

At an Xedge subscreen, group numbers (00, 01, 02, etc.) correspond to selectable functionparameters. To select a group number, type the number, then press the Enter key. The Xedgesoftware will then execute that action. The subscreen also provides menu options at the botthe screen.

Note IMPORTANT! All Xedge terminal interface screens in this manual are provided as examples only. Docopy values from example screens. The actual appearance of menus and screens will vary, dependyour system environment and the Xedge software version controlling a particular module.

ROOT MENUOPTIONS

GROUP NUMBERSELECTIONS

MENUOPTIONS

Version ID

Event Message

Hartford: Slot 0 Root Menu 722v3

Slot 00 : Active PCx Received datacells = 103448Slot 01 : -------- Transmitted datacells = 257026Slot 02 : Active sdhSlot 03 : Active pdhSlot 04 : Active pdhSlot 05 : --------Slot 06 : Active ceSlot 07 : --------Slot 08 : -------- User: rootSlot 09 : -------- From: telnetSlot 10 : --------Slot 11 : -------- Slot 0 Redund. available: NoSlot 12 : -------- Slot 0 Redund: Main In-servSlot 13 : -------- Sys. Ref. Loc:0: No InfoSlot 14 : -------- SVCs Connected: 0Slot 15 : -------- PVCs Connected: 1 File transfer: InactiveSelect option:Diagnostics, Events, File system, Internal status,Manage configuration, self Restarts, Telnet, sVc routing,Warm start, eXit, LinK

Switch Modules

Node Name

Slot-0 Controller

StatusInformation

Hartford: Slot 0 MIB Display and Management New Event

00 system 42 Alarm Handler01 interfaces 43 CAC Configuration03 ip 69 Port, Link#, Location, ifIndex Map04 icmp 70 LIM and Link Information05 tcp 74 Ethernet Virtual Connections06 udp 82 Ethernet Statistics07 snmp 83 802.1d Bridging08 System Information 84 MPLS Label Switch Setup and Status09 Slot 0 Configuration/Status 85 PseudoWire Services12 Static Routing 94 Management IF16 Virtual Circuit Status 95 Node Status19 DSP DLIMs 97 IMA23 PVC Configuration/Status 101 QAAL224 SVC Configuration/Status27 System Timing References39 PDH Configuration/Status41 ILMI Configuration/Status

Select option:Enter group number, save As, Load, sTatus, eXit,Last save file is `/mnt/flash0/config.cfg'.

Type M

Node Name


Accessing Slot Controllers Security Features

INUX

and

he rear in slot-r

witch

lower

uide

Security Features

Change PasswordsIn a new system, it is necessary to change the default root password by editing a file via the Linterface. It is also suggested to change the Admin password from the factory default.

1. Log in as root , using the password: MANAGER

2. When the initial prompt comes up, press Control-C. This accesses the LINUX interface displays the LINUX prompt.

3. To change the Admin password:

a. Type passwd admin then press Enter.

b. At the prompt, type in the new password.

c. At the confirmation prompt, retype the password to verify your entries.

4. To change the root password:

a. Type passwd then press Enter.

b. At the prompt, type in the new password.

c. At the confirmation prompt, retype the password to verify your entries.

Craft Port Security KeyCraft port access to the switch can be controlled through the use of a physical keyswitch at tof the switch chassis. This keyswitch enables or disables craft port access to the controller 0, thereby enabling or disabling craft access to all devices in the switch. Access via Telnet oProSphere interfaces is not affected by the keyswitch position.

The location of the keyswitch panel depends on the type of Xedge chassis in use.

• For the Xedge 6160 or the Xedge 6280 chassis, the Craft Port keyswitch is on the SManagement Module (SMM).

• For the Xedge 6640 or the Xedge 6645 chassis, there is a Craft Port key is on thechassis panel for each slot-0 controller, Main and Standby.

• The Xedge 6002 chassis does not provide a craft port security keyswitch.

Note For more information about the Xedge chassis or the SMM, refer to the Xedge Chassis Installation G(032R410).



ecure

nel. switch. NMS.

ssion.oduct.

SH/xcept P.

Security OptionsThe ISG2 and PCX in slot 0 support the following security protocols: Secure Copy (SCP), SShell (SSH) and Internet Security (INET).

Secure Copy Protocol (SCP)

The PCX and ISG2 support the Secure Copy Protocol (SCP) over a secure shell (SSH) tunWith SCP, an encrypted file transfer session is conducted between ProSphere NMS and theFor example, when a configuration change is made at the switch, a trap is sent to ProSphereProSphere will then automatically initiate the SCP and get the new config.cfg file from the switch’s slot-0 controller over an encrypted file transfer session.

SCP is only used in following ProSphere NMS functions:

• When the slot-0 controller in the switch (ISG2 or PCX) is backing up the config.cfg file to the ProSphere Network Management System.

• When the ProSphere Network Management System is transferring the ISDN.bin to the VSM controller, for QSIG signaling only.

Note As an alternative, operators can use a terminal SSH client (such as PuTTY) to open the encrypted seFor more information about the SCP/SSH security, refer to the ProSphere Release Notes for your pr

INET Security Access

The ISG2 and PCX support INET, a firewall security protocol that works in conjunction with SSCP. When enabled, INET prevents unauthorized access by blocking all access attempts eSNMP port 161, SNMP port 162 Traps, ICMP, and TCP Port 22, which are used by SSH/SC

1. To configure INET Security Access, perform the following steps:

2. Log in at the craft port of a switch, and after entering the password, press the Control-C keys. The root prompt appears.

3. At the root prompt, enable INET by typing the blocking string as shown below:

./inetaccess b eth0 (where b indicates blocking)

4. The INET Firewall is now enabled and in effect at the switch’s slot-0 controller (PCX or ISG2).

Note To disable INET, type ./inetaccess u eth0 (where u indicates unblocking).




or

in this

:

nd

dge

the

C, 0 Ver. s.

. Note m time

e

r 21:08.

Chapter 3: Basic Slot-0 Configuration

OverviewXedge Version 7.x requires a properly configured Xedge packet controller (PCX, PCL, ISG2other supported packet controller) in slot 0. This chapter provides basic slot-0 configuration procedures that apply to any type of packet slot controller, except where noted. For a brief introduction to Xedge command line interface (CLI) menus and screens, refer to Chapter 2 document, under the section on Navigating Xedge Menus and Screens . Topics in this chapter include:

• Current Time Format

• Slot-0 IP Addressing

• Slot-0 Configuration

• SNMP Authentication

• System Timing Overview

• Redundant Slot-0 Configuration (ISG2 only)

Before You BeginBefore you begin basic slot-0 configuration, you must have already performed the following

• Connect a computer or terminal to the Manager (craft) port of the switch chassis aaccess the slot controllers as described in this manual. (Refer to Chapter 2, Accessing Slot Controllers for details).

• Load/update the appropriate switch code as described in the latest issue of the XeVersion 7.x Release Notes for your devices.

When you have completed the basic slot-0 procedures in this chapter, you can then performspecific configurations for each slot controller as described in later chapters of this manual.


Current Time FormatAt installation and whenever system power is interrupted, you must set the Xedge system timethat the E-Series and A-Series controllers have built-in system batteries that retain the systeif the power is interrupted. Use the following procedure to set the system time:

1. From the Root Menu of slot-0, select Manage configuration . The MIB Display and Management screen appears.

2. Select the System Information option and press Enter.

3. Select the Current time option and press Enter. At the prompt, type in the current timin the following format:

DD MMM YYYY HH:MM:SS

Note When setting the month, the three first letters are used, e.g., JAN, FEB, MAR, etc. When setting the hour and minutes, two digits must be entered for each parameter. For 9:08 PM, ente


Basic Slot-0 Configuration Before You Begin

sign

install ffic is

.

nd IP anging ss be

Slot-0 IP AddressingWhen you turn on the switch for the first time, it displays the local default address of 192.1.1.0. In order to connect this switch to any other switch in the network, you must asit a unique IP address. This address must be a valid, assigned IP address.

The Xedge switch uses multiple valid IP addresses in sequence, one for each slot. When youa controller in slot-0, this controller must also have a valid IP address. All ethernet SNMP trasent to the switch network through the controller acting as a bridge. Ask your LAN network administrator for the valid IP addresses that can be used for your switch network.

Creating the Hosts File for Slot-0

1. Log into the switch.

2. When prompted for the username, type the default user login, root and press the Enter key

3. When prompted for the password, type the default password, MANAGER and press Enter. TheRoot Menu appears, similar to the example shown below.

4. Select File system to open the File Operations screen.

5. Select Alter file .

6. At the Select File screen, enter the file name, hosts .

7. Enter the IP address of the switch containing the slot-0 controller and the alias names aaddresses of other switches or components you want to access from this switch. Not chthe default IP address can lead to problems. It is strongly advised that the default addrechanged to an assigned address; for example:

> ipaddress=192.100.100.16

> system1=192.150.100.16

> system2=192.200.100.16

8. When you have completed the entries, press CTRL K , then type X to save the configuration and return to the File Operations screen.

9. From the File Operations screen, select Directory to verify that the hosts file has been created.

10. Check that all configuration options have been changed as required.

11. To put these changes into effect, perform a Warm Start from the Root Menu, then performa Normal Start .


Basic Slot-0 Configuration Slot-0 Configuration

le 2 es not

s a ntry.

ns,

option

. To do

esses, e

the

ector.

Slot-0 Configuration

1. From the Root Menu, select Manage configuration . The MIB Display and Management screen displays.

2. Select the Slot0 Configuration/Status option and press Enter.

3. Select Standby Switch Fabric option. If you have a redundant Switch Fabric moduinstalled, select Y , otherwise select N . This option is not applicable for the 2-slot Xedge 600chassis (does not support Switch Fabric modules), or the 4-slot Xedge 6160 chassis (dosupport slot-0 redundancy).

4. Select Physical Layout option and press Enter. The Physical Layout screen displaylist of all the controllers installed in the switch. Note that you are positioned at the slot-0 e

5. Select E xtra detail to open the Detail of Physical Layout of entry 0 screen.

Note If you are configuring other non-zero slot controllers, select G oto [row number] to advance to the properslot, or you can advance one slot at a time by pressing D own.

6. Select the Dlim type option and press Enter. This displays all of the Dlim types. For acomplete listing of all of the possible slot controller and associated Dlim type combinatiorefer to the Xedge Compatibility and Performance Chart in the latest issue of the Xedge/ProSphere Quick Reference (032R299).

7. Select the option letter corresponding to the Dlim type, then press Enter. Note that theseselections are case sensitive. This returns you to the Physical Layout screen.

8. Repeat step 5. through step 7. for all other slot controllers in the switch.

9. If you intend to use signaling, you need to enter the E.164 address and a node addressthis, select eXit to return to the slot-0 Configuration/Status screen.

10. Select E.164 . Type in the address and press enter. For more information on E.164 addrrefer to the paragraphs on Addressing in Chapter 3 of the Xedge Switch Technical ReferencManual (032R310).

Note When entering an address of less than 14 digits, the switch will append zeros.

11. When all of the LIMs have been defined for all of the slot controllers in the switch, save entries by continually pressing eXit until the following prompt appears:

Save changed configuration (Y/N)

12. Press Y to save the configuration.

13. From the Root Menu, select Warm start and then select N ormal start to put configuration changes into effect.

Note The ISG2 slot controller does not accept line interface modules (LIMs) at the chassis midplane conn


Basic Slot-0 Configuration SNMP Authentication

r. The

ith the S

MP

,

able

NMP t .

SNMP Authentication

The slot-0 controller is responsible for sending traps to the user-designated SNMP manageslot controller’s SNMP Authentication Table which controls whether one or more NMS in thenetwork is allowed SNMP access, SNMP Discovery and SNMP Trap privileges associated wswitch. An entry configured in the SNMP Authentication Table will authenticate a specific NMfor all three SNMP privileges. By default, the table is empty.

When the Table is empty (no NMS entries):

• All NMS in the network will discover the switch and be allowed SNMP access.

• No Traps will be sent to any NMS.

When the Table has one or more NMS entries:

• Only an NMS with a matching IP and community address in the slot controller’s SNAuthentication Table will discover the switch and be allowed SNMP access.

• All Traps will be sent to authenticated NMS only.

• Up to 8 authentication entries can be configured in the SNMP Authentication tablenumbered from 0 to 7.

Note IMPORTANT! To restrict access to the entire switch, you must configure the SNMP Authentication Twith the parameters of at least one NMS in the network.

SNMP Authentication Table Configuration

Note IMPORTANT! Changes to the SNMP table take effect immediately. Therefore, you must configure Saccess for your manager entry first (that is, the one you are working from). If you configure a differenmanager first, Xedge will reject SNMP and TFTP packets from your own manager from that point on

Use the following procedure to configure the SNMP Authentication Table:

1. Go to the root menu of the slot controller you want to configure for SNMP security.

2. Select the System Information option. The System Information screen appears.

3. From the System Information screen, select Authentication table for SNMP access . The SYS Authentication table for SNMP access screen appears, similar to theexample below.

Switch Name: Slot 0 SYS Authentication table for SNMP access No Entry index Source IP address Community Access type Send Traps Validity

0 1 172.16.7.1 public readWrite send all valid1 2 172.16.7.3 public readWrite send none valid2 3 172.16.7.5 public readWrite send none valid3 4 172.16.1.41 public readWrite send none valid4 5 192.9.21.16 public readWrite send none valid5 6 192.9.22.16 public readWrite send none valid6 7 192.168.62.33 public readWrite send none valid7 8 172.16.1.67 public readWrite send none valid

Select option:Add entry, Enter entry number to edit, Extra detail, Goto row,Kill entry, Move entry, Press ^J for extra help on this item, eXit



you

.

n.

ct as

4. Select Extra Detail . The Detail of Authentication table for SNMP access entry “X” screen appears, similar to the example below.

5. Select the Source IP Address option. You will be prompted for the IP address of theentry’s manager.

6. Enter the manager’s Source IP Address. The Source IP Address takes effect as soon asenter it.

7. Select the Community option. You will be prompted for the entry manager’s CommunityThe default is public . The Community field takes effect as soon as you enter it.

8. Select the Access type option. You will be prompted for the entry manager’s Access Type. You can select either A - readOnly or B - readWrite . The Access Type takeseffect as soon as you enter it.

9. Select the Send Traps option. You will be prompted for the entry manager’s Trap optioYou can either select A - send all to send all traps to this manager) or select B - send none to send no traps to this manager. The Send Traps selection takes effesoon as you enter it.

10. Select the Validity option. You can either select A - valid to complete this entry, or select B - invalid to delete this entry from the SNMP Authentication Table. The Validity selection takes effect as soon as you enter it.

Switch Name: Slot 0 SYSAuthentication table for SNMP access Detail of Authentication table for SNMP access entry 0

Entry index : 10 Source IP address : 172.16.7.11 Community : public2 Access type : readWrite3 Send Traps : send all4 Validity : valid

Select option:Add entry, Down, Enter entry number to edit, Goto row, Kill entry,Move entry, Press ^J for extra help on this item, Summary, eXit



dge SNMP

own.

ystem

.

SNMP Traps

The Xedge switch generates SNMPv1 common (generic) traps and a sizable number of Xe(enterprise-specific) traps. Both types of traps are sent by the slot controller to the designatedmanager. Some common SNMP traps are:

• Cold Start trap signifies that the Xedge switch is reinitializing itself and that its configuration may have been altered.

• Warm Start trap signifies that the Xedge switch is reinitializing itself such that its configuration is unaltered.

• Link Down trap signifies that the Xedge switch has a Network Interface becoming d

• Link Up signifies that the Xedge switch has a Network Interface becoming up.

• Authentication Failure trap signifies that the Xedge switch has received a protocol message that is not properly authenticated.

• EGP Router trap

Note Not all common and Xedge SNMP traps are listed in this document.

Event Table Traps

The Xedge switch provides an Event Table that lists the most recent 160 traps sent by the s(numbered 0 through 159 ). After 160 traps, the Event Table resets the counter to 0 .

1. At the root menu, select E to access the Event Table. An example screen is shown below

Figure 3-1 Xedge Event Table

• Select U (up) or D (down) to scroll through the list of events.

• Select G (Goto row) to jump to a specific event by row number.

2. If desired, save the contents of the Event Table by selecting S (Save to Disk). At the File screen prompt, type a file name and extension, then press Enter. The File is saved to the current directory.

3. If desired, select C to clear event table.

4. Select X to return to the root menu.

Switch Name: Slot 0 Event Table New Event Date :Event-------------------------------------------------------------------------------123 03Sep08 140806:Slot 3, link 0, state Down124 03Sep08 140825:Trap: slotChanged CLEARED for125 03Sep08 140825:Slot 6 up.126 03Sep08 140825:Trap: linkChanged CLEARED for127 03Sep08 140825:Slot 6, link 0, state Stopped128 03Sep08 140825:Trap: linkChanged CLEARED for129 03Sep08 140825:Slot 6, link 1, state Stopped130 03Sep08 140825:Trap: linkChanged CLEARED for131 03Sep08 140825:Slot 6, link 2, state Stopped132 03Sep08 140825:Trap: linkChanged CLEARED for133 03Sep08 140825:Slot 6, link 3, state Stopped134 03Sep08 140826:Open VC 0/0 for slot:6 sap:6 atmp:-1 int:150 ret:0135 03Sep08 140827:Slot 6 or 0 does not support ISUP/ISDN136 03Sep08 141259:Trap: clockAlarm CLEARED for137 03Sep08 141259:Major alarm: PRIosc/SECoffline

Select option:Clear event table, Goto row, Save to disk, Up, eXit


Basic Slot-0 Configuration System Timing Overview

eable es by king d in

IMs NTM into

nce to nfigure ence,

ming. ated cuitry stem

ting

System Timing OverviewProper configuration of system timing ensures that all timing in the Xedge network can be tracto a single source. Within an Xedge switch, network timing may be distributed between nodpropagating timing information between two physical interfaces using GDC’s enhanced clocLIMs. Another timing strategy employs the Xedge Node Timing Module (NTM), which is useconjunction with the enhanced clocking LIMs to provide more flexible support for timing distribution and synchronization within the switch. With two NTMs, the switch can provide resilient system timing.

Basic Xedge Timing Principles

System Timing Hierarchy

Each type of LIM can provide a system timing reference for others of its own type, but not all Lcan provide a system timing reference for every other type. Therefore, when a node without acontains a variety of LIM types, you must be aware that configuration of that node must takeaccount the hierarchy of system timing.

• When there is no NTM in the switch, refer to Table 3-3 for system timing relationships between LIM types.

• When there is an NTM in the switch, refer to Table 3-4 for system timing relationships between LIM types.

About Enhanced Clocking LIMs

Enhanced clocking LIMs are capable of sending and receiving an 8-kHz system timing referethe system bus which can be used (received) by all modules in a Xedge switch. When you cothe node you can designate one LIM local oscillator or a link on one LIM as the primary referand one link on another LIM as the secondary reference.

The possible reference sources are receive timing from a selected link and local oscillator tiDivider circuits on the LIMs derive the 8-kHz signal required for system timing from the designreference source, which operates at a higher rate. LIMs employ phase locked loop (PLL) cirat their transmit ports to achieve the transmit clock rates they require based on the 8-kHz sytiming reference from the node.

• A DS3 link can only supply or use the system timing reference (8k clock) if it is operain PLCP mode.

• The Serial I/O LIM can only receive timing. It is not capable of generating timing.

Note For a list of all enhanced clocking LIMs supported in an Xedge system, and which slot controllers arecompatible with each type, refer to the Xedge / ProSphere System Reference (032R299-000).


Basic Slot-0 Configuration System Timing Overview

ry m ignal ource

d

from

tching

Primary / Secondary System Timing

LIMs configured to base their transmit timing on system timing will use the configured primasystem timing signal when it is available. Normally, the LIM configured as the primary systetiming reference source will supply timing based on a receive (RCV) signal. If that receive sis lost, the type of fall-back that occurs will depend on whether a secondary timing reference sis configured.

Configuration of a primary and a secondary system timing reference is advisable, but not mandatory. When implemented, the Xedge slot-0 configuration requires that the primary ansecondary references must originate on separate LIMs.

Table 3-1 illustrates the possible fallback sequences. Available timing references are shownleft to right, in order of declining desirability.

Table 3-2 describes how the options in the System Timing References screen govern the swiaction between timing references.

Table 3-1 Xedge System Reference Fall-back Sequence

MostDesirable

LeastDesirable

Condition in Effect

Primary RCV

Timing

PrimaryLocal

Oscillator

SecondaryRCV

Timing

SecondaryLocal

Oscillator

IndividualLocal

Oscillator

Normal Operation ✔

Loss of Primary RCV (no Secondary) ✔

Loss of Primary RCV (with Secondary) ✔

Loss of Primary and Secondary RCV ✔

Loss of Both RCV Signals and Secondary Oscillator

✔

Table 3-2 System Timing References Screen Options

Timing Option Action

Automatic Revert If Yes , after interruption of the primary, restores primary, when available.

If No , then no automatic switching occurs.

Revert Timer 0 to 30 seconds; imposes a delay between availability of a primary timing reference and automatic switch to that reference. Delay ensures the reference is definitely established before switchover occurs.

Activate Revert If Yes , commands an immediate switchover from fall-back to primary system timing reference. (This is the only mechanism for switchover when Automatic Revert is set to no.)The No setting is the normal state of this option; the Yes setting is not stored.

Force Secondary If Yes , commands switchover from primary to configured secondary system timing. The No setting is the normal state of this option; the Yes setting is not stored.

Primary Line Reference Refer to System Timing Reference Hierarchy for nodes without or with NTM

(Table 3-3 or Table 3-4, respectively).Secondary Line Reference

System Timing Reference In Use


Basic Slot-0 Configuration System Timing without NTMs

e may timing

pe, e

or ay not

ower

System Timing without NTMsFor a Xedge node composed entirely of enhanced clocking LIMs, the system clock referencbe derived from a single physical interface in the switch, and then propagated as the transmitsource for other interfaces in the system.

Each type of LIM in the switch can provide a system timing reference for others of its own tybut not necessarily for every other type. Table 3-3 shows the timing hierarchy in effect when theris no NTM in the switch.

Special Considerations

• The received clock may only be used to drive a transmit clock of equal or lower order. Fexample, an OC-3c/STM-1 source may be used to time a DS1 line, but a DS1 source mbe used to time an OC-3c/STM-1 line.

• Note 1: These timing configurations are supported when Transmit Line Timing is set to a lrate than the Serial I/O LIM.

• Note 2: Supported when the rate is set at the Serial I/O LIM to 1.544 Mbps or lower.

• Note 3. Supported when the rate is set at the Serial I/O LIM to 2.048 Mbps or lower.

Table 3-3 Timing Hierarchy without NTM

Transmit Line Timing

Receive Line Reference OC-3 OC-N Serial I/O DS3 DS1 E3 E1

OC-3C/STM-1 (155-Series) ✔ ✔ ✔ ✔ ✔ ✔ ✔

OC-N/STM-N ✔ ✔ ✔ ✔ ✔ ✔ ✔

Serial I/O -- -- ✔ (Note 1) -- ✔ (Note 1) -- ✔ (Note 1)

DS3 -- -- ✔ ✔ ✔ ✔ ✔

DS1 -- -- ✔ (Note 2) -- ✔ -- --

E3 -- -- ✔ -- ✔ -- --

E1 -- -- ✔ (Note 3) -- ✔ -- ✔



, and slot-0

own

rs.

the

etting

dary

before

Configuration Procedure (Without NTM)Typically, one LIM local oscillator or a link on one LIM is designated as the primary referenceone link on another LIM as the secondary reference. This configuration is performed at the controller via the System Timing References screen, as described below.

1. From the root menu, select M,27 to access the System Timing References screen, as shbelow. Note that without the NTM, only options 00-05 are available for configuration.

Figure 3-2 System Timing References Screen

2. Select 00 Automatic REVERT . When set to YES, after an interruption of the primary reference, restores the primary, when available. If NO, then no automatic switching occu

3. Select 01 REVERT Timer . This option imposes a delay between the availability of a primary timing reference and automatic switch to that reference. Setting a delay ensuresreference is definitely established before a switchover occurs. Default is 30 secs.

4. Select 02 Activate REVERT . If set to YES, commands an immediate switchover fromfallback to primary timing reference. This is the only mechanism for switchover when Automatic Revert is set to NO. The normal state is NO; the YES setting is not stored.

5. Select 03 Force Secondary LIMs. If set to YES, commands a switchover from primary to the configured secondary timing reference. The normal state is NO; the YES sis not stored.

6. The next steps configure the LIMs that will serve as the primary and secondary timing references for the node. A primary reference must be selected and configured. A seconreference should be selected and configured to allow for resilient timing operation.

Note IMPORTANT! When the node contains a variety of LIM types, be aware of the system timing hierarchyselecting the primary and secondary timing references (Table 3-3).

Switch Name: Slot 0 System Timing References New Event

00 Automatic REVERT: no 14 Primary External Config01 REVERT Timer: 30 15 Secondary External Config02 Activate REVERT: no 16 Primary External Status03 Force Secondary LIMs: no 17 Secondary External Status Line Ref Alarm Statu: major 18 Primary Derived Config Active Line Source : none 19 Secondary Derived Config04 Primary Line Reference 20 Primary Derived Status05 Secondary Line Reference 21 Secondary Derived Status Stratum 3 Clock: no Line Ref Alarm Error: pRIoscSECoff06 Primary NTM Control07 Secondary NTM Control08 Primary NTM Status09 Secondary NTM Status10 Primary Stratum 3 Config11 Secondary Stratum 3 Config12 Primary Stratum 3 Status13 Secondary Stratum 3 StatusSelect option:Enter option number or eXit



te tors.

:

is

iming.

7. To configure the primary timing reference for the node, select 04 to access the Primary LineReference screen summary.

8. Select E to access the Extra Detail screen, similar to the example below.

• Select 0 On/Off and set the option to off to take the timing reference off-line. This is required for configuration of system timing. The node will continue to operausing its fallback timing source, either the secondary system timing or local oscilla

• The switch will display a warning that timing may be interrupted. Accept the confirmation prompt to proceed.

• Select 1 Slot Number to specify the slot number of the LIM that is to supply thesystem timing reference. (Refer to Table 3-3 as needed.)

• Select 2 Reference Select to specify the timing reference course for the LIMlocal oscillator or link[n], where [n] is 0 through 15, depending on the LIM type. (Be aware that selecting a link number that is not physically available will cause thoption to default to link0.)

• Select 0 On/Off and set the option to on to put the newly configured system timingreference on-line.

9. To configure the secondary timing reference for the node, select 05 to access the SecondaryLine Reference screen summary, then repeat step 8. for the secondary timing reference.

10. From the root menu, select M,27 to check your configuration settings (Table 3-6).

11. System timing is now configured for the node without NTMs.

Note IMPORTANT! This procedure only configures the node’s system timing. You must also configure LIM tRefer to Chapter 7 in this manual, under the paragraphs on LIM Timing .

Switch Name: Slot 0 SYS Primary Line References New EventDetail of Primary Line Reference entry 0

Index : 1 Valid Reference : yes0 On/Off : on1 Slot Number : 12 Reference Select : link0 Active Reference : plcp Input Line OK : yes Reference OK : yes

Select option:Enter entry number to edit, Summary, eXit


Basic Slot-0 Configuration System Timing With NTM

g

e

ve two d

lable

ced ’s

rk.

ing

of the rce

rfaces

n:

.

/Sec).

ary own

System Timing With NTMThe Node Timing Module (NTM) is a timing controller that distributes a clean, resilient timinreference to each line interface in the node. There are two versions of the NTM:

• NTM-DS1 (for DS1 external timing)

• NTM-E1 (for E1-GPS external timing) Note that NTM-E1 utilizes the timing intefacdescribed in ITU-T G.703 Table 10 (not Table 6).

The Xedge 6280 switch has one dedicated NTM slot. Xedge 6645 and 6640 switches each hadedicated NTM slots. A node with two NTMs is capable of fully redundant system timing ansynchronization. Refer to the Xedge Hardware Guide to properly install one or two NTMs.

The NTM operates in conjunction with enhanced clocking LIMs to increase the options avaifor system timing in the node and the network. Table 3-4 shows the receive and transmit timing hierarchy for the NTM and LIM combinations.

With one or two configured NTMs, the switch’s 20 PPM oscillator is disabled and any enhanLIM can provide node timing. In the event of loss of timing at the configured source, the NTMStratum 3 Oscillator can provide the Reference Clock for the switch ot the entire ATM netwo

The NTM generates transmit timing for a variety of LIMs from a LIM local oscillator or from aLIM’s received DS1, DS3, E1, E3 and OC-3c/STM-1 line timing (Primary and Secondary timreferences designated by the user). The NTM may derive its operating frequency from any line interfaces listed above. This assumes network timing is being supplied from a clock souattached somewhere else within the ATM network. There are no restrictions on the line intethat can receive network timing.

The NTM provides a high stability Stratum 3 Oscillator which can be configured to operate i

• Internal Mode: Stratum 3 clock functions as a free-running timing reference source

• Line Mode: Phase-locked loop locks to a line reference (Pri/Sec Line Ref).

• External Mode: Phase-locked loop locks to an external reference timing source (Pri

Note When the NTM is configured for line mode or external mode, in the event of both primary and secondtiming source failures, the NTM will switch to Holdover mode. It will continue to operate at the last knfrequency until the primary clock reference is restored.

Table 3-4 Timing Hierarchy With the NTM

Transmit Line Timing

Internal, External or RCVLine Reference Source

Derived Timing OC-3c/STM-1 DS3 PLCP E3 E1 DS1

1. NTM Stratum 3 ✔ ✔ ✔ ✔ ✔ ✔

2. External DS1 ✔ ✔ ✔ ✔ ✔ ✔

3. OC-N/STM-N as OC-12 ✔ ✔ ✔ ✔ ✔ ✔

4. OC-3c/STM-1 or OC-N/STM-N as OC-3

✔ ✔ ✔ ✔ ✔ ✔

5. DS3 PLCP ✔ ✔ ✔ ✔ ✔ ✔

6. E3 ✔ ✔ ✔ ✔ ✔ ✔

7. E1 ✔ ✔ ✔ ✔ ✔ ✔

8. DS1 ✔ ✔ ✔ ✔ ✔ ✔



fall

a free-

The

ilure

.

NTM Timing Fallback SequenceWhen provisioned with the NTM, a failure of the primary timing source will cause the switch toback to the secondary timing source, with the option of reverting or not reverting to the moredesirable timing source. If both primary and secondary sources fail, the switch falls back to running 20 parts-per-million internal oscillator.

Table 3-5 describes the various timing fallback sequences for a node provisioned with NTM.fallback timing is based on the following factors:

• The number of NTMs in the node (1 or 2)

• The configured Stratum 3 mode of operation (External or Line)Note that Internal mode is not applicable, since an internal timing loss indicates a faof the NTM module itself.

Note When the Stratum 3 Mode is set to external , the NTM can not fall back to line timing. When the Stratum 3 Mode is set to line , the NTM can not fall back to external timing.

Note 1. The current status of the clock is displayed in the root menu for each Slot Controller.2. Certain restrictions apply as to which LIMs accept network timing, and which LIMs are being timed

Table 3-5 NTM Fallback Sequencing

If Stratus 3 Mode is External:

If Stratus 3 Mode is Line:

With 1 NTM in Normal Timing, timing source is... Primary External Primary Line

With 1 NTM and with Loss of Primary, timing falls back to... Primary HoldoverSec Line or

Primary Holdover

If Stratus 3 Mode is External:

If Stratus 3 Mode isLine:

If Stratus 3 Mode is PRI NTM - Ext and

SEC - Line:

With 2 NTMs in Normal Timing, timing source is... Pri NTM External

Primary NTM orPrimary Line Pri NTM External

With 2 NTMs and with Loss of Primary,timing falls back to... Sec NTM External

Primary NTM orSec Line Sec NTM-Pri Line

With 2 NTMs and with Loss of Secondary, timing falls back to... Sec NTM Holdover Primary NTM Holdover

Sec NTM-Sec LineSec NTM-Holdover



6280. the to

duct.

M.

own

rs.

the

ored.

System Timing Configuration (With NTM)NTM Slot Positions

Ensure that the NTM is installed in the dedicated Primary NTM slot at the rear of the Xedge For Xedge 6640/6645, the right outermost slot is the Primary NTM; the left outermost slot isSecondary NTM. With only one NTM, only the Primary NTM slot can be used. If necessary update NTM software, perform the following steps. Otherwise, proceed to the Basic NTM Configuration procedure below.

Updating NTM Software1. Update your switch software as described in the Release Notes accompanying your pro

2. At the slot-0 root menu, select M,9 to access the Slot-0 Configuration screen.

3. Select NTM Compatible SODOC and set the option to yes .

4. Select the NTM for updating:

• At the root menu, select M,27,6 to access the Primary NTM Control screen.• For the second NTM, select M,27,7 for the Secondary NTM Control screen.

5. Select the Download NTM Code option, then select yes to immediately download the new NTM software to the NTM. The code will not go into effect until it is activated for each NT

6. When the node has two NTMs, repeat step 1. and step 5. When finished, proceed to the Basic NTM Configuration procedure below.

Basic NTM Configuration1. From the root menu, select M,27 to access the System Timing References screen, as sh

below. Note that with the NTM, all options are available for configuration.

Figure 3-3 System Timing References Screen

2. Select 00 Automatic REVERT . When set to YES, after an interruption of the primary reference, restores the primary, when available. If NO, then no automatic switching occu

3. Select 01 REVERT Timer . This option imposes a delay between the availability of a primary timing reference and automatic switch to that reference. Setting a delay ensuresreference is definitely established before a switchover occurs. Default is 30 secs.

4. Select 02 Activate REVERT . If set to YES, commands an immediate switchover fromfallback to primary timing reference. This is the only mechanism for switchover when Automatic Revert is set to NO. The normal state is NO; the YES setting is not stored.

5. Select 03 Force Secondary LIMs. If set to YES, commands a switchover from primary to secondary timing reference. The normal state is NO; the YES setting is not st

6. Proceed to the next section to perform NTM Control Configuration .

Switch Name: Slot 0 System Timing References New Event

00 Automatic REVERT: no 14 Primary External Config01 REVERT Timer: 30 15 Secondary External Config02 Activate REVERT: no 16 Primary External Status03 Force Secondary LIMs: no 17 Secondary External Status Line Ref Alarm Statu: major 18 Primary Derived Config Active Line Source : none 19 Secondary Derived Config04 Primary Line Reference 20 Primary Derived Status05 Secondary Line Reference 21 Secondary Derived Status Stratum 3 Clock: no Line Ref Alarm Error: pRIoscSECoff06 Primary NTM Control07 Secondary NTM Control08 Primary NTM Status09 Secondary NTM Status10 Primary Stratum 3 Config11 Secondary Stratum 3 Config12 Primary Stratum 3 Status13 Secondary Stratum 3 StatusSelect option:Enter option number or eXit



w the ts.

p.

NTM Control Configuration

The following steps must be performed if the node is equipped with one or two NTMs. Revieparagraphs on NTM Slot Positions in this chapter to ensure NTMs are installed in the correct slo

7. From the root menu, select M,27,6 to access the Primary NTM Control screen, similar tothe example below.

8. Select 0 LIM Type to define the type of NTM as T1, E1 or none.

• The T1 NTM external received and derived transmit interfaces are T1-compatible.

• For the NTM-E1, the external received is E1 external BITS clock compatible.

9. Select 6 NTM on/offline to put the NTM online.

• A - offline

• B - online

10. If a second NTM is installed, select M,27,7 from the root menu to access the SecondaryNTM Control screen. Repeat step 8. for the secondary NTM. Otherwise, skip to the next ste

11. From the root menu, select M,27,8 or M,27,9 to check configuration settings of the primary or secondary NTM, respectively (Table 3-8).

12. Proceed to the next section to perform Stratum 3 Configuration .

Switch Name: Slot 0 Primary NTM Control New EventDetail of Primary NTM Control entry 0-------------------------------------------------------------------------------- index : 00 NTM LIM type : t11 Download NTM Code : no2 Activate NTM Code : no3 Download NTM Configuration : no NTM Code Bytes Transferred : 0 NTM File transfer status : idle4 Force Secondary External : no5 Force Secondary Stratum 3 : no Current Command : none Future Use : na Future Use : na6 NTM on/offline : offline

Select option:Enter entry number to edit, eXit



ary

lar

s:

M.

is

d in

e

NTM is does

Stratum 3 Configuration

The following steps must be performed if the node is equipped with one or two NTMs. A primand secondary Stratum 3 timing source should be defined to assure resilient timing.

13. From the root menu, select M,27,10 to access the Primary Stratum 3 Config screen, simito the example below.

14. Select 0 Stratum 3 Reference to define the timing source for the Stratum 3 clock a

• external - an external timing source connected to the “RC” connector of the NT

• line - line timing from a LIM installed in the switch chassis (i.e., no external clockconnected to “RC” connector of the NTM).

15. Select 1 Stratum 3 Mode to define the mode of operation of the Stratum 3 clock as:

• external or line - causes the Stratum 3 clock to use the timing source selectethe previous step to generate its timing.

• internal - causes the Stratum 3 clock to free-run using its own oscillator.

16. Select 2 Force Secondary as needed to control which Stratum 3 clock is used by thLIMs. (This item only appears on the Primary Stratum 3 Config screen.)

• yes - immediately forces the LIMs to use the secondary Stratum 3 timing source.

• no - allows the LIMs to use the Primary Stratum 3 timing source.

17. Select 3 Re-configure to put the parameters selected in this screen into effect.

• yes - reconfigures the NTM.

• no - does not reconfigure the NTM.

18. If a Secondary Stratum 3 source is desired, select M,27,11 from the root menu to access theSecondary Stratum 3 Config screen. Repeat step 8. for the secondary NTM.

19. From the root menu, select M,27,12 or M,27,13 to check configuration settings of theprimary or secondary Stratum 3 source, respectively (Table 3-9).

• If Stratum 3 Mode was set to Internal , System Timing with the NTM is complete.

• If Stratum 3 Mode was set to External , proceed to External Timing Configuration .

• If Stratum 3 Mode was set to Line , proceed to Line Timing Configuration .

Note When the NTM is set to Line (i.e., no external clock is connected to the NTM’s “IN” connector), a NO BITS LINE INPUT trap will always be sent to the Xedge system event log and to ProSphere NMS. Thnot adversely affect NTM or system functionality.

GDC: Slot 0 Primary Stratum 3 Config New EventDetail of Primary Stratum 3 Config entry 0-------------------------------------------------------------------------------- index : 00 Stratum 3 Reference : external1 Stratum 3 Mode : external or line2 Force Secondary : no3 Re-configure : no




tratum y and

to

to

e

line

d and

back

.

External Timing Configuration

The following steps must be performed when the node is to use External timing, as set at the S3 configuration screen. This procedure is only required when the NTM-T1 is in use. A primarsecondary external timing source should be defined to assure resilient timing.

1. From the root menu, select M,27,14 to access the External Configuration screen, similarthe example below.

2. Select 0 Transmit Line Length to define the length (in feet) of the line connected the RC connector of the primary/secondary NTM. Valid entries are A - H to set values at:0-110, B110-220, 220-330, 330-440, 440-550, 550-660, or greater than 655 feet.

3. Select 2 Frame Format to define the frame format of the data being transferred on thline connected to the RC connector of the primary/secondary NTM. Valid entries are:none , sf (superframe), or esf (extended superframe).

4. Select 3 Line Code to define the line code format of the data being transferred on the connected to the RC connector of the primary/secondary NTM. Valid entries are: na (not applicable), ami (alternate mark inversion), or b8zs-t1 (bit 8-zero suppression T1).

5. Select 4 Loopback define the loopback mode of the primary/secondary NTM RC interface: none, line loopback , or local loopback .

• Line loopback causes the signal received over the line connected to RC to be loopetransmitted over the same line.

• Local loopback causes the signal being transmitted by the NTM at RC to be loopedas received data.

6. Select 5 Clear Performance Counters then select yes to immediately clear items displayed in the Primary/ Secondary External Status screen. Otherwise, select no .

7. Select 6 Re-configure then select yes to put the changes made at this screen into effect. Otherwise, select no for the NTM to operate as previously.

8. If a Secondary External source is desired, select M,27,15 from the root menu to access theSecondary External Configuration screen. Repeat step 2. through step 7.for the secondary external source.

9. From the root menu, select M,27,16 or M,27,17 to check configuration settings of the primary or secondary external source, respectively (Table 3-10).

10. You have completed configuration of System Timing with the NTM using External Timing

GDC: Slot 0 Primary External Config 722v3\700Detail of Primary External Config entry 0-------------------------------------------------------------------------------- index : 00 Transmit Line Length : na1 Future Use : na2 Frame Format : none3 Line Code : na4 Loopback : none5 Clear Performance Counters : no6 Re-configure : no




tum 3 Q d be

tem

nue

m

on to

.

Line Timing Configuration

The following steps must be performed when the node is to use LIM timing, as set at the Straconfiguration screen. This procedure selects a link on a LIM and associates it with the LQ/Hbusses for the primary line timing source. A primary and secondary line timing source shouldefined to assure resilient timing.

Note IMPORTANT! When the node contains a variety of LIM types, be aware of the hierarchy rules for systiming before selecting primary and secondary timing references (Table 3-4).

1. To configure the primary timing reference for the node, select 04 to access the Primary LineReference screen summary.

2. Select E to access the Extra Detail screen, similar to the example below.

3. At the Extra Detail screen, select 0 On/Off and set the option to off to take the timing reference off-line. This is required for configuration of system timing. The node will contito operate using its fallback timing source, either the secondary system timing or local oscillators.

4. The switch will display a warning that timing may be interrupted. Accept the confirmationprompt to proceed.

5. Select 1 Slot Number to specify the slot number of the LIM that is to supply the systetiming reference. (Refer to Table 3-4 as needed.)

6. Select 2 Reference Select to specify the timing reference course for the LIM: localoscillator or link[n] , where [n] is 0 through 15, depending on the LIM type. (Be aware that selecting a link number that is not physically available will cause this optidefault to link0.)

7. Select 0 On/Off and set the option to on to put the newly configured system timing reference on-line.

8. From the root menu, select M,27,5 to access the Secondary Line Reference screen summary. Repeat step 2. through step 7. Otherwise, skip to the next step.

9. From the root menu, select M,27 to check your configuration settings (Table 3-6).

10. You have completed the configuration of System Timing with the NTM using Line Timing

Switch Name: Slot 0 SYS Primary Line References New EventDetail of Primary Line Reference entry 0

Index : 1 Valid Reference : yes0 On/Off : on1 Slot Number : 12 Reference Select : link0 Active Reference : plcp Input Line OK : yes Reference OK : yes

Select option:Enter entry number to edit, Summary, eXit



ires rce

to

to

e

line

d and

back

.

Derived Timing Configuration (Optional)

Perform the following steps if you want to output the timing source from the NTM-T1. This requan OC-3 line input defined as the clock source. A primary and secondary derived timing soushould be defined to assure resilient timing. (Derived Timing not applicable when NTM-E1 is in use.)

1. From the root menu, select M,27,18 to access the Derived Configuration screen, similarthe example below.

2. Select 0 Transmit Line Length to define the length (in feet) of the line connected the RC connector of the primary/secondary NTM. Valid entries are A - H to set values at:0-110, B110-220, 220-330, 330-440, 440-550, 550-660, or greater than 655 feet.

3. Select 2 Frame Format to define the frame format of the data being transferred on thline connected to the RC connector of the primary/secondary NTM. Valid entries are:none , sf (superframe), or esf (extended superframe).

4. Select 3 Line Code to define the line code format of the data being transferred on the connected to the RC connector of the primary/secondary NTM. Valid entries are: na (not applicable), ami (alternate mark inversion), or b8zs-t1 (bit 8-zero suppression T1).

5. Select 4 Loopback define the loopback mode of the primary/secondary NTM RC interface: none, line loopback , or local loopback .

• Line loopback causes the signal received over the line connected to RC to be loopetransmitted over the same line.

• Local loopback causes the signal being transmitted by the NTM at RC to be loopedas received data.

6. Select 5 Clear Performance Counters then select yes to immediately clear items displayed in the Primary/ Secondary External Status screen. Otherwise, select no .

7. Select 6 Re-configure then select yes to put the changes made at this screen into effect. Otherwise, select no for the NTM to operate as previously.

8. If a Secondary External source is desired, select M,27,19 from the root menu to access theSecondary Derived Configuration screen. Repeat step 2. through step 7. for the secondary derived source.

9. From the root menu, select M,27,20 or M,27,21 to check configuration settings of the primary or secondary derived source, respectively (Table 3-11).

10. You have completed configuration of System Timing with the NTM using Derived Timing

GDC: Slot 0 Primary Derived Config 722v3\700Detail of Primary Derived Config entry 0-------------------------------------------------------------------------------- index : 00 Transmit Line Length : na1 Future Use : na2 Frame Format : none3 Line Code : na4 Loopback : none5 Clear Performance Counters : no6 Re-configure : no



Basic Slot-0 Configuration System Timing Status

tion

us

System Timing StatusFor all Nodes

From the root menu, select M,27 to access the System Timing Reference screen. Status informadisplayed on this screen is described below, and applies to nodes with or without NTMs.

For Nodes with NTMs

Additional status information is displayed on subscreens accessed from the System Timingreference screen, as listed below. Refer to the associated table for descriptions of each statparameter.

• Select M,27,4 or M,27,5 to access Pri/Sec Line Status screens (Table 3-7).

• Select M,27,8 or M,27,9 to access Pri/Sec NTM Status screens (Table 3-8).

• Select M,27,12 or M,27,13 to access Pri/Sec Stratum 3 Status screens (Table 3-9).

• Select M,27,16 or M,27,17 to access Pri/Sec External Status screens (Table 3-10).

• Select M,27,20 or M,27,21 to access Pri/Sec Derived Status screens (Table 3-11).

Table 3-6 System Timing Status - All Nodes (with or without NTMs)

Status Parameter Definition

Stratum 3 Clock Displays yes when NTM is present/online.Displays no when NTM is absent/off-line.

Line Ref Alarm Status

Indicates the presence of alarms for the LIM selected as a timing reference. Possible states are:clear - No alarms in effectminor alarm - Another clock source has taken over

major alarm - Problem with primary and secondary clock sources (no valid clock source)

Active Line Source Indicates current timing source for the line reference. Possible states are:none - No line reference selectedline - The source is from the link

oscillator - The node is using its internal clock as the sourcepri-line - Primary line source is selectedsec-line - Secondary line source is selected

pri-plcp - Primary line PLCP source is selected (DS3)sec-plcp - The secondary line PLCP source is selected (DS3)pri-internal - The local oscillator is selected for the primary source

sec-internal - The local oscillator is selected for the secondary source

Line Ref Alarm Error Indicates a current alarm error. Possible states are:pRIlineSECoffline - Problem with primary and secondary clocks; sources are offlinepRIoscSECoffline - Problem with primary oscillator; secondary is offline

sEClinePRIoffline - Problem with secondary line source; primary is offlinesECoscPRIoffline - Problem with secondary oscillator; primary is offlinepRIlineSECline - Problem with primary line and a problem with secondary line

pRIosc - Problem with primary oscillator (possibly no other timing configured)sECosc - Problem with secondary oscillatorpRIoscSECosc - Problem with primary oscillator; problem with secondary oscillator

pRIoscSECline - Problem with primary oscillator; problem with secondary line sourcepRIlineSECosc - Problem with primary line source; problem with secondary oscillator.no-valid-error - This message indicates an illegal combination of inputs.



Table 3-7 Primary/Secondary Line Status Screens


Valid Reference Indicates whether the selected primary/secondary line timing source is a valid timing source. Displays yes or no .

Active Reference Indicates the selected primary/secondary line timing source. Possible states are:line , internal or plcp

Input Line OK Indicates whether the input line of the selected primary/secondary line timing source is functioning. Displays yes or no .

Reference OK Indicates whether the timing source of the selected primary/secondary timing source is functioning. Displays yes or no .

Table 3-8 Primary/Secondary NTM Status Screens


NTM LIM Type Indicates the type of NTM (T1, E1 or none).

NTM Code Revision Indicates the revision level of the primary/secondary NTM software

NTM Boot Revision Indicates the revision level of the primary/secondary NTM boot software.

NTM Flash File Status Indicates whether software exists on the flash EPROM of the primary/secondary NTM. The possible states are present, not-present, na (not available).

NTM Hardware Revision Indicates the revision level of the primary/secondary NTM hardware.

NTM Operating Mode Indicates the operating mode of the primary/secondary NTM, either no-card,boot, full-feature-offline, unknown, full-feature-in-dnld(download), boot-in-dnld (download), or full-feature-online.

NTM Error Code Indicates errors, if any, that occur during a download to the primary/secondary NTM. The possible indications are none, bad-config, no-code,no-config, download-ok, or download-fail.



rence

nce te, and

igured

Special Stratum 3 Oscillator Considerations

• Wideband-to-narrowband acquisition allows the oscillator to converge towards a new refetiming source frequency more quickly than it would in normal or narrowband state. The acquisition lasts for 255 seconds.

• If the timing source is lost, the NTM will go into holdover state where the output of the oscillator remains at the last known reference timing source frequency. When the referetiming source becomes available, the oscillator proceeds to the acquisition wideband stathen if available, to the acquisition narrowband state.

• If the oscillator never achieves a locked-in range, it cycles between the wideband and narrowband states seeking a stable received clock. This indicates a problem with the conftiming sources.

Table 3-9 Primary/Secondary Stratum 3 Status Screens


Stratum 3 Reference Status

Indicates the timing source of the primary/secondary Stratum 3 clock. States are:primary - listening to Primary timing sourcesecondary - listening to Secondary timing source

no input - nonexistent timing source

Stratum 3 Output Indicates the state of the primary/secondary Stratum 3 clock output. States are: enabled-onlinedisabled-offlinefault

Stratum 3 Oscillator Indicates the status of the phase-locked loop or the internal clock:

idle - If the Stratum 3 mode has been set to external or line, the idle state indicates that at NTM start-up or reconfiguration, neither the primary nor secondary reference timing source was available.

acquisition wideband/narrowband - If the Stratum 3 mode has been set to external or line, the wideband or narrowband acquisition state indicates that the reference timing source is available and the phase-locked loop is attempting to calculate a clock rate from the received stream at the low quality bus. In the wideband acquisition state, the NTM calculates an average “coarse” measurement from the received stream. After 255 seconds the NTM shifts to narrowband acquisition state and attempts to calculate a more precise measurement from the received stream. If a consistent rate is detected over a sufficient interval, the phase-locked loop will lock in at that rate. Otherwise, the wideband/narrowband acquisition process begins again.

locked-in-range - indicates that the received stream at the high quality bus is locked in at a rate within the narrowband range.

holdover - Indicates that both the primary and secondary reference source signals became unavailable while the oscillator was in the locked-in-range state.

reference-out-of-range - Indicates that the tracking of the reference timing source fell out of the narrowband range.

internal - If the Stratum 3 mode was set to internal, the internal state indicates that the high-quality oscillator was set to free-run at the center frequency.



Table 3-10 Primary/Secondary External Status Screens


External Reference OK

Indicates (yes or no) if any of the following four alarm conditions exist onthe line connected to the RC connector of the primary/secondary NTM:receive alarm indication signal (Rx AIS), loss of signal (LOS), out of frame(OOF), or bit error rate (BER).

Rx AIS (n/a to NTM-E1)

Indicates (yes or no) if a receive alarm indication signal condition exists onthe line connected to the RC connector of the primary/secondary NTM.

LOS Indicates (yes or no) if a loss of signal alarm condition exists on the lineconnected to the RC connector of the primary/secondary NTM.

OOF (n/a to NTM-E1)

Indicates (yes or no) if an out of frame alarm condition exists on the lineconnected to the RC connector of the primary/secondary NTM.

BER (n/a to NTM-E1)

Indicates (yes or no) if a bit error rate alarm condition exists on the lineconnected to the RC connector of the primary/secondary NTM.

OOF Count (n/a to NTM-E1)

Indicates the number of out of frame alarm conditions detected on the lineconnected to the RC connector of the primary/secondary NTM. The ClearPerformance Counters function in the Primary/Secondary ExternalConfig screen sets this item to 0.

BER Count (n/a to NTM-E1)

Indicates the number of bit error rate alarm conditions detected on the lineconnected to the RC connector of the primary/secondary NTM. The ClearPerformance Counters function in the Primary/Secondary ExternalConfig screen sets this item to 0.

LOS Count Indicates the number of loss of signal alarm conditions detected on the lineconnected to the RC connector of the primary/secondary NTM. The ClearPerformance Counters function in the Primary/Secondary ExternalConfig screen sets this item to 0.

LCV Countn/a to NTM-E1)

Indicates the number of line code violation alarm conditions detected on theline connected to the RC connector of the primary/secondary NTM. TheClear Performance Counters function in the Primary/SecondaryExternal Config screen sets this item to 0.



Table 3-11 Primary/Secondary Derived Status Screens


Line OK Indicates (yes or no) if any of the following four alarm conditions exist onthe line connected to the DR connector of the primary/secondary NTM:receive alarm indication signal (Rx AIS), loss of signal (LOS), out of frame(OOF), or bit error rate (BER).

Transmit Reference Status

Indicates whether the timing source of the primary/secondary derived clockis the primary (primary valid), secondary (secondary valid) timing source,or nonexistent (no input).

Rx AIS Indicates (yes or no) if a receive alarm indication signal condition exists onthe line connected to the DR connector of the primary/secondary NTM.

LOS Indicates (yes or no) if a loss of signal alarm condition exists on the lineconnected to the DR connector of the primary/secondary NTM.

OOF Indicates (yes or no) if an out of frame alarm condition exists on the lineconnected to the DR connector of the primary/secondary NTM

BER Indicates (yes or no) if a bit error rate alarm condition exists on the lineconnected to the DR connector of the primary/secondary NTM.

OOF Indicates the number of out of frame alarm conditions detected on the lineconnected to the DR connector of the primary/secondary NTM. The ClearPerformance Counters function in the Primary/Secondary DerivedConfig screen sets this item to 0.

BER Count Indicates the number of bit error rate alarm conditions detected on the lineconnected to the DR connector of the primary/secondary NTM. The ClearPerformance Counters function in the Primary/Secondary DerivedConfig screen sets this item to 0.

LOS Count Indicates the number of loss of signal alarm conditions detected on the lineconnected to the DR connector of the primary/secondary NTM. The ClearPerformance Counters function in the Primary/Secondary DerivedConfig screen sets this item to 0

LCV Count Indicates the number of line code violation alarm conditions detected on theline connected to the DR connector of the primary/secondary NTM. TheClear Performance Counters function in the Primary/Secondary DerivedConfig screen sets this item to 0.


Basic Slot-0 Configuration Redundant Slot-0 Configuration

and . Slot-t-0

Slot-

edge ique ervice ers are ange Out-of-d

g the

dby

Redundant Slot-0 Configuration

(For ISG2 Slot Controllers Only)

Applications that require slot-0 redundancy must have the ISG2 is installed in both the MainStandby slot-0 positions, and configured as In-Service and Out-of-Service slot-0 controllers0 Redundancy protects the Xedge switch against slot-0 component failure by passing off slocontrol from a failed In-Service ISG2 to the available Out-of-Service ISG2. Once configured,0 redundancy operation is transparent to the user.

Only ISG2 slot controllers contains the necessary logic to support slot-0 redundancy in the X6002, 6280, 6640 or 6645 chassis. Each ISG2 controller of a redundant pair has its own unMAC address that may changed by the user. One ISG2 slot-0 controller is assigned an In-SIP address and the other is assigned an Out-of-Service IP address. When the ISG2 controllfully operational in a redundant configuration, a failure at In-service ISG2 will cause an exchof the MAC addresses, IP addresses and E.164 addresses between the In-Service and the Service controller. This has the effect of putting the failed slot-0 controller Out-of-Service antransferring slot-0 functions to the redundant In-Service controller.

If so configured, the redundant ISG2 pair will exchange IP addressing at specific times durinslot-0 redundant operation. In addition, the config.cfg will be automatically copied from the In-Service to the Out-of-Service controller whenever there has been a change made to the configuration, if so enabled.

Initial Setup for Slot-0 Redundancy1. Set the rotary switch on the circuit board of each ISG2 controller.

(Refer to the Xedge Hardware Installation Guide for basic rotary switch information.)

• On the Main Slot-0 controller, set the switch to 0 .

• On the Standby Slot-0 controller, set the switch to 4 .

Note If the rotary switch is set improperly, redundant operation will not function.

2. Insert the “main” ISG2 controller into the Main slot-0 position of the chassis.

3. Configure the hosts file as described in this chapter under the paragraphs on Creating the Hosts File for Slot-0 . Be sure to perform a Warm Start from the Root Menu, then performa Normal Start at the end of that procedure to pre-initialize the slot-0 controller.

4. Insert the “standby” ISG2 controller into the Standby slot-0 position of the chassis.

5. Use the Y-cable (028H350-X06) to connect the manager ports of the Main and the StanSlot-0 controllers to the terminal.

6. Advance to the next procedures to enable slot-0 redundancy.



e IP

2.

Enable Slot-0 Redundancy7. At the “main” ISG2, access the MIB Display and Management screen, then type 94 to select

Management IF . The Management IF menu appears as shown below.

8. Type 00 to configure the In-Service IP address, if not already configured.

9. Type 04 to configure the Out-0f-Service IP address.

Note You must configure both an In-Service and an Out-of-Service IP address. Note that the Out-of-Servicaddress will use the In-Service IP Mask.

10. At the MIB Display and Management screen, select 9 (Slot-0 Configuration).

• At the Slot-0 Config screen, type 4 and then select yes .

• At the Slot-0 Config screen, type 6 and then select auto .

11. When the green Run LED on the out-of-service controller starts to flash, or when the "Slot0 Redund. available: " is "not ready ” on the root screen, the following fileswill be transferred from the In-Service ISG2 to the Out-of-Service ISG2:

• config.cfg

• hosts

• users2

• def.rtb• dtl.bin

12. Warm-start the Out-of-Service slot-0 controller to put all configurations into effect.Slot-0 configuration is now enabled at the In-Service ISG2 and at the Out-of-Service ISG

Switch Name: Slot 0 Management IF New Event

00 IP Address: 172.16.69.20 14 VxC Cross Connect Table01 IP Mask: 255.255.0.0 15 VxC Cross Connect Status02 Broadcast Addr: 172.16.255.255 16 Termination from Physical Ethernet MAC Addr: 001219010498 17 Ethernet Termination from Pseudowire03 Tunnel Management Table 18 Termination of MPLS Label04 OutOfServ IP Addr: 172.16.69.24 19 IP v4 Point-to-Point Interface Standby MAC Addr: 0012190104c8 20 IP v4 Broadcast Interface05 RIP Updates: disabled 21 Tunnel STP Group06 Bcst Rec'd RIP: enabled07 Broadcast RIP: disabled08 Proxy ARP: disabled09 VC Termination Table10 User Port IP Addr: 200.10.10.1011 User Port Mask: 255.255.255.012 User Port IP Bcst: 0.0.0.0 User Port MAC Add: 00121901049913 VCC/VPC TableSelect option:Enter option number or eXit

Middlebury: Slot 0 Slot 0 Configuration/Status 710v12\700

Switch Fabric Status: main in serv Slot0 Redund Avail: yes00 Switch Fabric to Use: not applicable01 Standby Switch Fabri: no02 Power supply statistics03 Physical Layout04 Auto xfr to out-serv: yes05 Broadcast MIB Table: none Slot0 IP Addr: 192.150.150.1606 Slot0 To Use: auto Slot0 Redund Mode: enhanced redundancy07 Slot0 Switch ID: 1608 NTM compatible SODOC: yes09 Slot 0 E.164 Address: 580010000 Slot0 Redund Status: main in service10 Slot0 IP Mask: 255.255.255.240 Max Active Slots: 15 Cur Active Slots: 15

Select option:Enter option number or eXit



is cy. d from

SG2.

save e effect

, any own.

Disable Slot-0 RedundancyIn normal operation, the “main” ISG2 is typically enabled and In-Service; the “standby” ISG2enabled and Out-of-Service. The following procedure shows how to disable slot-0 redundanSlot-0 redundancy can only be disabled via the Xedge terminal interface. It cannot be disablethe ProSphere NMS.

1. Telnet to the Out-of-Service ISG2. Be sure to use the IP address of the Out-of-Service I

2. At the MIB Display and Management screen, select 9 (Slot-0 Configuration). The Slot-0 Configuration screen appears, similar to the example below.

3. At the Slot-0 Config screen, type 6 and then select E (Disable) .

4. The MIB Display and Management screen appears. Type X to return to the root menu.

5. At the root menu, type X . At the Save prompt type N to disable slot redundancy.

Note Typing N at the Save prompt will disable slot-0 redundancy. If you type Y, slot-0 redundancy will still the disabled redundancy setting, but will also cause an error message to display. This has no adverson the system.

6. The root menu screen will now show "Slot0 Redund. available: No

7. You have effectively disabled slot-0 redundancy at the switch. Without slot-0 redundancycondition that causes the In-Service slot-0 ISG2 card to fail will cause the switch to go d

8. To re-enable slot-0 redundancy, perform the procedure provided below.

ISAF1: Slot 0 Slot 0 Configuration/Status 710v11\700

00 Switch Fabric to Use: not applicable01 Standby Switch Fabri: no02 Power supply statistics03 Physical Layout04 Auto xfr to out-serv: yes05 Broadcast MIB Table: none Slot0 IP Addr: 192.168.1.3206 Slot0 To Use: auto Slot0 Redund Mode: enhanced redundancy07 Slot0 Switch ID: 008 NTM compatible SODOC: yes09 Slot 0 E.164 Address: Slot0 Redund Status: main in service10 Slot0 IP Mask: 255.255.255.240 Max Active Slots: 4 Cur Active Slots: 4Select option:Enter option number or eXit



ble

SG2.

Out-

abled

Re-Enable Slot-0 Redundancy

When re-enabling slot-0 redundancy, typically the “main” ISG2 is In-Service and disabled; the“standby” ISG2 is Out-of-Service and disabled. The following procedure shows how to re-enaslot-0 redundancy.

1. Telnet to the Out-of-Service ISG2. Be sure to use the IP address of the Out-of-Service I

2. At the MIB Display and Management screen, select 9 (Slot-0 Configuration).

3. At the Slot-0 Config screen, type 6 and then select C (Standby) to re-enable the “standby” Out-of-Service ISG2 card for slot-0 redundancy. If the “main” ISG2 card is the of-Service disabled card, select B (Main) .

4. The MIB Display and Management screen appears. Type X to return to the root menu.

5. At the root menu, type X . At the Save prompt type N to diable slot redundancy.

Note IMPORTANT! You must type N at the prompt to re-enable slot-0 redundancy.

6. The root menu screen will now show "Slot0 Redund. available: Yes

7. The Out-of-Service card will receive a file transfer and come up as Out-of Service and enfor slot-0 redundancy. During the file transfer, the “Slot 0 Redund. Avail: ” will indicate “ Not Ready ” for one or two minutes.

8. When complete, you will have effectively re-enabled slot-0 redundancy at the switch.

Note Refer to Slot-0 Redundancy Guidelines below for additional important information.

ISAF1: Slot 0 Slot 0 Configuration/Status 710v11\700

00 Switch Fabric to Use: not applicable01 Standby Switch Fabri: no02 Power supply statistics03 Physical Layout04 Auto xfr to out-serv: yes05 Broadcast MIB Table: none Slot0 IP Addr: 192.168.1.3206 Slot0 To Use: standby Slot0 Redund Mode: enhanced redundancy07 Slot0 Switch ID: 008 NTM compatible SODOC: yes09 Slot 0 E.164 Address: Slot0 Redund Status: main in service10 Slot0 IP Mask: 255.255.255.240 Max Active Slots: 4 Cur Active Slots: 4Select option:Enter option number or eXit


Basic Slot-0 Configuration Summary

g

t-

is scribed

e swap

dancy

will

cond (if n-dant G2

C, 0 Ver. s.

Slot-0 Redundancy Guidelines

Forcing a Switch

To force the In-Service slot-0 controller into an Out-of-Service state, always use the followinmethod:

• At the MIB Display and Management screen, select 9 (Slot-0 Config)

• At the Slot-0 Config screen, type 6 (Slot to Use) and force a swap by selecting the Ouof-Service slot-0 controller (normally standby) .

Note IMPORTANT! DO NOT force a swap by extracting the In-Service Slot-0 controller from the shelf. If itnecessary to remove the In-Service Slot-0 ISG2, you must first force it to the Out-Of Service state as deabove. Once the ISG2 is Out of Service, it can be safely extracted from the shelf.

Normal Cell Loss

For a slot-0 redundant swap, it is normal to experience a few lost cells (less than 5) during thprocess as the 50mhz backplane clock source of the shelf is switched.

Slot-0 Redundancy Status

The Root Menu screen displays the status of the Slot-0 Standby Slot Controller. When redunis available, any configuration changes made and saved to the config.cfg file will update the redundant slot-0 controller. The Root Menu will display File transfer = Active and the redundant controller LEDs will indicate a TFTP in-progress. The module’s front panel LEDsflash in an alternating pattern.

Slot-0 and Switch Fabric Redundancy

The In-Service ISG2 slot-0 controller must receive a Healthcheck cell from itself within a 6 seperiod. If the health check fails, the XH switch fabric (main) will switch to the redundant XH available) and wait for the Healthcheck cell. If the Healthcheck cell is still not received, the IService ISG2 slot-0 controller will switch to the redundant ISG2 controller. If there is no redunXH switch fabric available, the In-Service ISG2 slot-0 controller will switch to the redundant ISslot-0 controller immediately.

Power Cycling

If the node is power cycled and Slot-0 controller is missing startup_isg.tz.cod , the Slot-0 controller will come up In-Service and In Boot Mode. The Slot-0 controller will not relinquishservice to the redundant Slot-0 (standby) module.

SummaryYou have completed the basic configuration procedures for the slot-0 controller. Refer to thefollowing sections of this manual to perform specific configuration procedures for each slot controller in the switch.

• Chapter 4, ISG2 Configuration/Status )

• Chapter 5, PCX Configuration/Status )

• Chapter 7, LIM Configuration )



Basic Slot-0 Configuration Summary


2) slot ment,

0 slots 0

e

the 20

s 0 ISG2.

n

Chapter 4: ISG2 Configuration/Status

Overview

This chapter describes the configuration and status of the Xedge IP Services Gateway (ISGcontroller. For a brief introduction to Xedge menu and screens refer to Chapter 2 in this docuunder the section on Navigating Xedge Menus and Screens .

Topics in this chapter include:

• Management Configuration


• ATM Port Table Configuration

• Tunnel Configuration

• Link Status

• Link Status (ATM Ports)

• Interface Status

• Node Status

Note Two ISG2 cards can be configured for slot-0 redundancy when installed in the Main and Standby slot-of the Xedge 6280, 6640 or 6645 switches. This slot-0 function is described in Chapter 3, Basic Slot-Configuration .

Accessing the ISG2 Slot Controller

• When the ISG2 is in slot-0, select M(anage Configuration) from the root menu to access thMIB Display and Management menu for the device.

• When the ISG2 is not in slot-0, select T (elnet) from the root menu and then enter the corresponding slot number (e.g., slot1 ) in the IP address to call field. When prompted, enter the password. At the root menu for the slot, select M(anage Configuration) to access the MIB Display and Management menu for the device.

• After a redundancy switch (where Standby ISG2 is now the In-Service slot-0 controller),Out-of-Service ISG2 will reboot. To avoid any transitional IP address conflict, wait aboutseconds before attempting to Telnet to the Out-of-Service ISG2.

Note A non slot-0 ISG2 has no route to the outside network; hence, Telnet access to the non slot-0 ISG2 iaccomplished via the Slot 0 controller. As an alternative, a static route can be created on the non slot-

OSPF Command Line Interface

The ISG2 supports OSPF version 2, the Interior Gateway routing protocol (IGP) described iRFC2328 - OSPF Version 2. Refer to Appendix A, OSPF CLI Reference for an overview of OSPF commands, examples, and guidelines.


ISG2 Configuration/Status Management Configuration

as tions.

In-it is

he Out dress

ards,

Management Configuration1. From the root screen, select Manage . The MIB Display and Management screen appears

shown in the figure below. This display shows the Management screen with available op

Figure 4-1 MIB Display and Management Screen

2. From the MIB Display and Management screen, type 94 to select Management IF . The Management IF menu appears as shown below. Refer to Table 4-1 for definitions of all Management IF menu options.

Figure 4-2 Management IF Screen

3. Configure the IP address, IP Mask and Broadcast Address. These entries will define theService IP address that will be used by the In-Service ISG2 controller in slot-0, whether located in the main or standby slot.

4. In a slot-0 redundant switch, a Standby IP address must also be configured for used by tof Service controller, whether it is in the main or standby slot. Note that the Standby IP admust be different In-Service IP address entered in step 3.

Note For complete information and guidelines on configuring a switch for slot-0 redundancy with the ISG2 crefer to Chapter 3, Basic Slot-0 Configuration , under Redundant Slot-0 Configuration .

5. Enable or disable the RIP Updates, Bcst Rec'd RIP, Broadcast RIP and Proxy ARPs, asrequired. Refer to Table 4-1 for option descriptions.

Middlebury: Slot 0 MIB Display and Management 710v712\700

00 system 95 Node Status01 interfaces 101 QAAL203 ip04 icmp05 tcp06 udp07 snmp08 System Information09 Slot 0 Configuration/Status12 Static Routing23 PVC Configuration/Status24 SVC Configuration/Status27 System Timing References42 Alarm Handler69 Port, Link#, Location, ifIndex Map82 Ethernet Statistics94 Management IFSelect option:Enter group number, save As, Load, sTatus, eXit,Last save file is `/mnt/flash0/config.cfg'.

Middlebury: Slot 0 Management IF 710v12\700

00 IP Address: 172.16.69.20 14 VxC Cross Connect Table01 IP Mask: 255.255.0.0 15 VxC Cross Connect Status02 Broadcast Addr: 172.16.255.255 16 Termination from Physical Ethernet MAC Addr: 0012190104c8 17 Ethernet Termination from Pseudowire03 Tunnel Management Table 18 Termination of MPLS Label04 OutOfServ IP Addr: 172.16.69.24 19 IP v4 Point-to-Point Interface Standby MAC Addr: 0012190104c8 20 IP v4 Broadcast Interface05 RIP Updates: disabled 21 Tunnel STP Group06 Bcst Rec'd RIP: enabled07 Broadcast RIP: disabled08 Proxy ARP: disabled09 VC Termination Table10 User Port IP Addr: 200.10.10.1011 User Port Mask: 255.255.255.012 User Port IP Bcst: 0.0.0.0 User Port MAC Add: 0012190104c913 VCC/VPC TableSelect option:Enter option number or eXit


ISG2 Configuration/Status Management Configuration

Table 4-1 Management IF Options Definitions

Parameter Definition Entries Take Effect

IP Address The In-Service IP address for management Immediately

IP Mask The mask for management Immediately

Broadcast Addr The management broadcast address Immediately

MAC address MAC address for management port Read only

Tunnel Management Select to set up a tunnel Immediately

OutofService IP Address: The Out-of-Service IP address for management Immediately

Standby MAC address The standby MAC address for management Read only

RIP Updates Enable/Disable Rip2 Update from Ethernet port, default disabled.

Immediately

Bcst Rec'd RIP When disabled stops RIP updates of routes received on this port

Immediately

Broadcast RIP Disabled selects noneEnablemin selects mgnt onlyEnablefull selects all routs for RIP broadcasts to port.Default disabled

Immediately

Proxy ARP Enable/Disable Proxy ARP on Ethernet portDefault disable

Immediately

VC Termination Not supported in this release --

User Port IP Address Not supported in this release --

User Port Mask Not supported in this release --

Mgnt UserPort IP Bcst Not supported in this release --

User Port MAC Address Not supported in this release --

VCC/VPC Table Not supported in this release --

VxC Cross Connect Table Not supported in this release --

VxC Cross Connect Status Not supported in this release --

Termination from Physical Ethernet Not supported in this release --

Ethernet Termination from Pseudowire Not supported in this release --

Termination of MPLS Label Not supported in this release --

IPv4 Point-to-Point Interface Not supported in this release --

IPv4 Broadcast Interface Not supported in this release --


ISG2 Configuration/Status ATM Port Configuration

.

se

ATM Port Configuration

Connecting SAPs to ATM Ports

1. From the MIB Display and Management Screen, select SVC Configuration/Status , then select SVC Resource table .

2. Select E (xtra detail), then select G (o to row) and enter 22 . A detail for SAP 22 is shown below. Note that the default configuration assigns Logical SAP 22 to Logical ATM Port 6

Figure 4-3 Typical SVC Resource Table (showing SAP 22)

3. From the MIB Display and Management Screen, select Port, Link#, Location, if Index Map , then select 0 . The ATM port table appears at the Summary level.

4. Select Extra to advance to the Extra Detail screen, then select Go to row and enter the ATM port of interest, for example, 6 . The detail for ATM port 6 appears as shown below. Uthis screen to view or change the current port parameters on the ISG2 card.

Figure 4-4 ATM Port Table (Extra Detail Screen)

Note At 99% of bandwidth, Traffic Shaping and UBR will be fully functional and free of errors.

Middlebury: Slot 0 SVC Resource Table 710v12\700Detail of SVC Resource Table entry 22------------------------------------------------------------------------------- SAP : 22 13 Max Conns : 120 28 UBR Reserv: 0 SAP Type : logical Cur Conns : 0 29 Signal Pro: uni3100 VPI/VCI Hi: low 14 ATM Port : 6 30 Route Prot: apex01 SVC VCI St: 0 15 VPCI/VPI M: off 31 Status : off02 SVC VCI En: 0 16 QoS-based : off 32 Preemption: enable03 SVC VPI St: 0 17 Restart Op: off04 SVC VPI En: 0 18 Dest E164 :05 SVP Start : 0 19 Auto Sap O: no06 SVP End : 0 20 Sap Utiliz: 9507 Max SAP Ra: 0 21 CBR Bw Lim: 100 Available : 0 22 VBR-RT Bw : 10008 Signal VCI: 5 23 VBR-NRT Bw: 10009 Signal VPI: 0 24 ABR Bw Lim: 10010 CDVT (uS) : 200 25 UBR Bw Lim: 10011 Interface : network 26 Differenti: off12 Policing : off 27 Pk Rate Li: 0

Select option:Down, Enter entry number to edit, Goto row, Index search, Summary,Up, eXit

Xedge Switch: Slot 0 ATM Port Table New EventDetail of ATM Port Table entry 6------------------------------------------------------------------------------- ATM Port : 6 Use Count : 10 Mapping Type : atmpadaptation Mapping Number : 0 Operational Sta: active Physical State : port up00 Phy Port Locati: adaptation01 Phy Port Number: 002 Bandwidth : 10000003 VC VCI Start : 104 VC VCI End : 12805 VC VPI Start : 106 VC VPI End : 107 VP Start : 508 VP End : 25509 Admin State : active10 Port Type : uniSelect option:Enter entry number to edit, Summary, eXit


ISG2 Configuration/Status ATM Port Configuration

teps:

w. P 22

5. To see the SAP to ATM Port association and status in one place perform the following s

• From the root menu select I (nternal).

• Select (Si) G(naling).

• Select S (ignal sap status).

• Select G (o to row) and then enter 22 . The Layer SAP status appears as shown beloThe Layer/SAP Status screen displays part of the table, with the top line showing SAconnected to ATM port 6 and indicating its status.

Figure 4-5 Layer/SAP Status Screen

Xedge Switch: Slot 0 Layer/SAP Status 710ER6\700SAP Type TState DLState DatInt SSCF SSCOP Comment--------------------------------------------------------------------------------22 Logical Connecting Connecting Disconnected STATE11 STATE1 Port 623 Logical Connecting Connecting Disconnected STATE11 STATE1 Port 724 Logical Connecting Connecting Disconnected STATE11 STATE1 Port 825 Logical Connecting Connecting Disconnected STATE11 STATE1 Port 926 Logical Connecting Connecting Disconnected STATE11 STATE1 Port 1027 Logical Connecting Connecting Disconnected STATE11 STATE1 Port 1128 Logical Connecting Connecting Disconnected STATE11 STATE1 Port 1229 Logical Connecting Connecting Disconnected STATE11 STATE1 Port 1330 Logical Connecting Connecting Disconnected STATE11 STATE1 Port 1431 Logical Connecting Connecting Disconnected STATE11 STATE1 Port 1532 Logical Connecting Connecting Disconnected STATE11 STATE1 Port 1633 Logical Connecting Connecting Disconnected STATE11 STATE1 Port 1734 Logical Connecting Connecting Disconnected STATE11 STATE1 Port 1835 Logical Connecting Connecting Disconnected STATE11 STATE1 Port 1936 Logical Connecting Connecting Disconnected STATE11 STATE1 Port 2037 Logical Connecting Connecting Disconnected STATE11 STATE1 Port 21Select option:Down, Goto row, Up, eXit


ISG2 Configuration/Status Tunnel Configuration

ted to G2:

l

Tunnel ConfigurationCreating a Tunnel creates an access point to the router. A VC (PVC or SPVC) must be creaattach to that access point. The following rules apply for creating a VC to a tunnel on the IS

1. From the MIB Display and Management screen, select Management IF .

2. Select Tunnel Management Table . The Tunnel Management Table summary lists alexisting tunnels by index number, from 0 to 127. An example summary is shown below.

3. Type E to display the Extra Detail view of the first entry (entry 0).

4. Use the D (own) or U (p) commands to move through the detail screens, or use the G o to command to jump to a specific entry’s detail view. An example screen is shown below.

5. To add an entry, type A. Enter an index number at the prompt, then press Enter . A series of prompts allow you to configure the tunnel parameters for the new entry. Refer to Table 4-2 as needed for definitions of all tunnel parameters.

For PVC: For SPVC

At the ISG2 end of the VC: Slot = Slot number of ISG2 card Link (ATM Port) = 0 VPI = 1 VCI = Tunnel Number

At the ISG2 end of the VC: Slot = Slot number of ISG2 card Sap = 16 VPI = 1 VCI = Tunnel Number

Xedge Switch: Slot 0 Tunnel Management Table New EventNo Index Name Type ifIndex Slot ATM Port VPI VCI--------------------------------------------------------------------------------0 32 ip 3032 1 0 1 321 33 ip 3033 2 0 1 332 34 ip 3034 3 0 1 343 35 ip 3035 4 0 1 354 36 ip 3036 5 1 1 365 37 ip 3037 6 1 1 376 38 ip 3038 7 0 1 387 39 ip 3039 8 0 1 398 40 ip 3040 0 0 0 09 41 ip 3041 0 0 0 010 42 ip 3042 11 0 1 4211 43 ip 3043 0 0 0 012 44 ip 3044 0 0 0 013 45 ip 3045 0 0 0 014 46 xx ip 3046 15 0 1 46

Select option:Add entry, Enter entry number to edit, Extra detail, Goto row,Index search, Kill entry, Right, eXit

Xedge Switch: Slot 0 Tunnel Management Table New EventDetail of Tunnel Management Table entry 0------------------------------------------------------------------------------- Index : 32 09 IP Address : 0.0.0.000 Name : 10 Netmask : 0.0.0.001 Type : ip 11 P-t-P IP Addres: 0.0.0.0 ifIndex : 3032 12 Allow RIP1x : yes Slot : 1 ATM Port : 0 VPI : 1 VCI : 3202 Broadcast RIP : disabled Operation State: running spvc03 Tunnel State : up04 Status : valid05 Max Priority : 706 Min Priority : 007 Main Intf Index: 008 Metric Offset : 0Select option:Add entry, Down, Enter entry number to edit, Goto row, Index search,Kill entry, Summary, eXit


ISG2 Configuration/Status Tunnel Configuration

to the g rate

tunnel

n an ed to

Special Tunnel Considerations

• For a VC to a tunnel on the ISG2, the flow of cells from the ISG2 to the Fabric is shaped Peak Cell Rate contract that has been set up in the PVC or SPVC. The minimum shapinallowed is 1000 cells per second.

• For tunnel type, select IP Type when the tunnel is either a Data tunnel or a Managementto a node that is not adjacent in the network topology.

• A MOLN type tunnel is a specialized IP tunnel for management traffic, with an endpoint oadjacent node (PVC) or non-adjacent node (SPVC) in the topology. You will not be allowterminate more than one MOLN tunnel on the same link.

Table 4-2 Tunnel Management Table Details


Index Tunnel Number 1-128, corresponds to the Tunnel interfaces 3001 thru 3128.

Immediately

Name Mnemonic name for tunnel Immediately

Type Ip or MOLN (Future support: Pseudowire, eth vc and eth llc) (See Special Tunnel Considerations above.)

Immediately

Interface Number

Interface assigned = Tunnel Number + 3000 Read only

Slot Target slot for tunnel Read only

ATM Port Target link for tunnel Read only

VPI Target VPI for tunnel Read only

VCI Target VCI for tunnel Read only

Broadcast RIP Disabled selects none. (Default)Enablemin selects mgnt only.Enablefull selects all routs for RIP broadcasts to port.

Immediately

Operational State

DownRunning-PVCRunning SVC

Read only

Tunnel State Up/down Immediately

Status Valid/invalid Immediately

Max Priority Received packets will be routed to a tunnel if its TOS value is within the maximum priority range.

Immediately

Min Priority Received packets will be routed to a tunnel if its TOS value is within the minimum priority range.

Immediately

Main Intf Index Index value of highest TOS value tunnel. Examples:T1: Max PRI = 7, Min PRI = 4, Main Intf Index = 0 (not used).T2 : Max PRI = 3, Min PRI = 2, Main Intf Index = 1.T3 : Max PRI = 1, Min PRI = 0, Main Intf Index = 1.

Immediately

Metric Offset (Not supported in this release) --

IP Address Address of local end of tunnel. (only used on Main Interface Index tunnels.)

--

Net Mask Net mask for tunnel address. --

P-t-P Address Address of remote end of tunnel. --

Allow RIP1x Yes or No Immediately


ISG2 Configuration/Status Link Status

sical g

f a

Link StatusThe Link Status option from the ISG2 Slot-0 root menu displays the states of the ATM Portsbelonging to a slot controller in the shelf. (This is not to be confused with slot controller PhyLink Status which is displayed at the controller’s Alarm Monitoring or Performance Monitorinscreens.)

1. From the Root Menu, type K to select LinK .

2. The Link Status screen appears, similar to the example below:

For the ISG2, LIMs are not supported. The LIM Type column will display UNKNOWN.

For ECC/IMA, an IMA group is associated with only one ATM port. The lowest link number ogroup will represent the status of the group's ATM Port. For the example below:

• Port 0 represents an IMA group that may contain links 0 through 4

• Port 5, representing an IMA group that may contain links 5,6,7

• Port 8 for status of an IMA group that may contain links 8 through 13

For IMA:

• U = Up, meaning the ATM Group is up.

• D = Down, for group in a down state.

• S = Stop , the port (IMA group) is not enabled.

For other slot controller types, the ATM Port Status reflects physical layer port states.

Middlebury: Slot 0 Link Status New Event Link No: 00 01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 LIM Type

Slot 00 : Active U O O O O O O O O O O O O O O O UNKNOWNSlot 01 : Active S U U U e1-quadSlot 02 : Active U U S S dsolimSlot 03 : Active U U S S ds3-2cSlot 04 : --------Slot 05 : Active U U S S ds3-2cSlot 06 : Active U U S S ds3-2cSlot 07 : Active U U S S e3-2cSlot 08 : Active U U S S delimSlot 09 : Active U O O O O O O O O O O O O O O O UNKNOWNSlot 10 : --------Slot 11 : Active U U S S ds1-dualSlot 12 : Active U U S S dsolimSlot 13 : Active U S S S U S S S U S S S U S S S DS1-16-portSlot 14 : Active U U S S S S S S S S S S S S S S oc3-dual-sSlot 15 : Active U U U U e1-quadEnter Option:eXit S-stop , U-up , D-down , O-off


ISG2 Configuration/Status Interface Status

w.

Interface Status

1. From the Root Menu select Manage Configuration .

2. Select Interfaces , then select Interface Table . The initial Interface Table screen appears, with the first 15 interfaces. To view the rest of the interfaces (16 - 24), select Down .

Figure 4-6 Interface Table Screens

Line numbers 0 to 19 contain the fixed interfaces:

• Lo , eth0 , eth1 , br0 and sl0 of the ISG2 card

• Virtual connections to slots 1 to 15

Line numbers 20 and beyond are added automatically when:

• An ATM port is defined as NNI. In the example screen shown above: - Line 20 shows that slot 3 link 0 has a MOLN connection. - Line 21 shows that slot 3 link 1 has a MOLN connection. - Line 22 shows that slot 5 link 0 has a MOLN connection. - Line 23 shows that slot 6 link 1 has a MOLN connection.

• An ip tunnel is created. - Line 24 shows that an ip tunnel was created on interface 3033.

3. Select Extra Detail . The detail screen for the Interface table appears as shown beloRefer to Table 4-3 for definitions of all Interface Table entries.

Xedge Switch: Slot 0 Interface Table New EventNo ifIndex Description Type M T U Link Speed Physical Address--------------------------------------------------------------------------------0 1 lo software 16436 01 2 sl0 other 1518 02 3 br0 ethernet 1500 0 0012190105693 41 slot01 other 4000 04 42 slot02 other 4000 05 43 slot03 other 4000 06 44 slot04 other 4000 07 45 slot05 other 4000 08 46 slot06 other 4000 09 47 slot07 other 4000 010 48 slot08 other 4000 011 49 slot09 other 4000 012 50 slot10 other 4000 013 51 slot11 other 4000 014 52 slot12 other 4000 015 53 slot13 other 4000 0Select option:Down, Enter entry number to edit, Extra detail, Goto row,Index search, Right, eXit

Xedge Switch: Slot 0 Interface Table New EventNo ifIndex Description Type M T U Link Speed Physical Address-------------------------------------------------------------------------------16 44 slot12 other 4000 017 45 slot13 other 4000 018 46 slot14 other 4000 019 47 slot15 other 4000 020 48 moln30 other 4000 021 49 moln31 other 4000 022 50 moln50 other 4000 023 51 moln61 other 4000 024 52 iptun33 other 4000 0

Select option:Enter entry number to edit, Extra detail, Goto row, Index search, Right, Up eXit


ISG2 Configuration/Status Interface Status

slot, fected.

Note In redundancy applications, if Out of Service ISG2 card is removed or replaced at its Standby or Mainsome of the other controllers in the switch will receive errors. Otherwise, operation is not adversely af

Table 4-3 Interface Table Detail Screen

Parameter Definition

If Index Interface Index 1-3255 Read only

Description Text string containing interface information, typically includes manufacturer name, product name and the version of the hardware interface

Read only

Type Type of interface, distinguished by the physical/link protocol(s) immediately `below' the network layer in the protocol stack.

Read only

MTU Size of largest datagram which can be sent/received on the interface (in octets) Read only

Link Speed Estimate of the interface's current or nominal bandwidth in bits per second. Read only

Physical Address Interface address at the protocol layer immediately `below' the network layer in the protocol stack.

Read only

Admin Status The desired state of the interface: Up, Down, or Testing. Read only

Oper Status Current operational state of the interface: Up, Down, or Testing. Read only

Time Last State SysUpTime at the time the interface entered its current operational state. Read only

Rcv Octet Count Total number of octets received Read only

Rcv Ucast Packets Total number of subnetwork-unicast packets delivered to a higher-layer protocol Read only

Rcv N Ucast Pack Total number of subnetwork-broadcast or subnetwork-multicast packets delivered to a higher layer protocol

Read only

Rcv Discards Total number of error free packets discarded due to other problems such as buffer availability

Read only

Rcv Errors Total number of packets discarded due to errors Read only

Rcv Unknown Pro Total number of packets discarded because of unknown protocol Read only

Xmit Octet Coun Total number of octets transmitted Read only

Xmit Ucast Pack Total number of packets requested to be transmitted including those discarded or not sent

Read only

Xmit NUCast Pac Total number of subnetwork broadcast or subnetwork-multicast packets requested to be transmitted including those that were discarded or not sent

Read only

Xmit Discards Total number of error free packets discarded due to other problems such as buffer availability

Read only

Xmit Errors Total number of packets discarded due to errors Read only

Xmit Q Length Length of the output packet queue Read only

ifSpecific Refers to MIB definitions specific to the media used to realize the interface. Read only

Xedge Switch: Slot 0 Interface Table New EventDetail of Interface Table entry 0------------------------------------------------------------------------------- ifIndex : 1 Xmit UCast Pack: 424 Description : lo Xmit NUCast Pac: 0 Type : softwareLoopback Xmit Discards : 0 M T U : 16436 Xmit Errors : 0 Link Speed : 0 Xmit Q Length : 0 Physical Addres: ifSpecific :0 Admin Status : up Oper Status : up Time Last State: 0 Rcv Octet Count: 32975 Rcv UCast Packe: 424 Rcv NUCast Pack: 0 Rcv Discards : 0 Rcv Errors : 0 Rcv Unknown Pro: 0 Xmit Octet Coun: 32975Select option:Down, Enter entry number to edit, Goto row, Index search, Summary,eXit


ISG2 Configuration/Status Node Status

en:

y one

card

s.

Node Status

1. From the Root Menu select Manage Configuration , then select Node Status . The Node Status menu appears with the following selections:

• Link State Table

• Interface Translation Table

• Interface Extension Table

2. From the Node Status menu, select Link State Table . The Link State table appears, similar to the example below.

Figure 4-7 Link State Table

The Link State Table displays an initial screen of information for Line numbers 0 to 15. Select Down to display the status of all remaining interfaces and ports. In the example scre

• Line numbers 0 to 15 show interfaces for the slot 0 ISG2 card. Since ISG2 has onlport, line 0 status shows up , and lines 1 through 15 show stop (not present).

• Line numbers 16 to 31 show the first four interfaces (0 to3) for slots 1 to 4. When theor interface does not exist, stop is displayed. Otherwise, status is up or down .

• Further down in the list describes the remaining cards and ports 4 to 15 for all card

• The last screen shows the information for any ip tunnels that have been created.

3. Select eXit to return to the Node Status menu.

Xedge Switch: Slot 0 Link State Table 710v12\700No Slot Link Interface Index State-------------------------------------------------------------------------------0 0 0 64 up1 0 1 65 off2 0 2 66 off3 0 3 67 off4 0 4 1004 off5 0 5 1005 off6 0 6 1006 off7 0 7 1007 off8 0 8 1008 off9 0 9 1009 off10 0 10 1010 off11 0 11 1011 off12 0 12 1012 off13 0 13 1013 off14 0 14 1014 off15 0 15 1015 offSelect option:Down, Enter entry number to edit, Extra detail, Goto row,Index search, eXit

Xedge Switch: Slot 0 Link State Table 710v12\700No Slot Link Interface Index State-------------------------------------------------------------------------------16 1 0 68 stop17 1 1 69 stop18 1 2 70 stop19 1 3 71 stop20 2 0 72 stop21 2 1 73 stop22 2 2 74 up23 2 3 75 stop24 2 4 1204 stop25 2 5 1205 stop26 2 6 1206 stop27 2 7 1207 stop28 2 8 1208 stop29 2 9 1209 stop30 2 10 1210 stop31 2 11 1211 stopSelect option:Down, Enter entry number to edit, Extra detail, Goto row,Index search, Up, eXit


ISG2 Configuration/Status Node Status

ink

.

le

.

4. From the Node Status menu, select Interface Translation Table . The Interface Translation Table screen appears, similar to the example below.

Figure 4-8 Interface Translation Table

The Interface Translation Table displays the translation from Interface Index to either Slot/Lnumbers or to a Tunnel number.

• An initial screen displays information for Line numbers 0 to 15, Interfaces 64 to 79

• Select Down to display the status of all remaining interfaces and ports.


6. From the Node Status menu, select Interface Extension Table to view or edit configured management connections for the slot controller. The Interface Extension Tabscreen appears, similar to the example below.

Figure 4-9 Interface Extension Table

7. In the example above, several management connections have been configured.

• Type an entry number to edit an existing connection.

• Select Down to view any additional configured connections.

• For a long list, use the Goto row or Index search to view a specific connections


Xedge Switch: Slot 0 Interface Translation Table New EventNo Interface Index Interface Type Slot Link Tunnel Number--------------------------------------------------------------------------------0 64 link 0 0 -1 65 link 0 1 -2 66 link 0 2 -3 67 link 0 3 -4 68 link 1 0 -5 69 link 1 1 -6 70 link 1 2 -7 71 link 1 3 -8 72 link 2 0 -9 73 link 2 1 -10 74 link 2 2 -11 75 link 2 3 -12 76 link 3 0 -13 77 link 3 1 -14 78 link 3 2 -15 79 link 3 3 -Select option:Down, Enter entry number to edit, Extra detail, Goto row,Index search, eXit

Xedge Switch: Slot 0 Interface Translation Table New EventNo Interface Index Interface Type Slot Link Tunnel Number-------------------------------------------------------------------------------256 3001 tunnel - - 1257 3002 tunnel - - 2258 3003 tunnel - - 3259 3004 tunnel - - 4260 3005 tunnel - - 5261 3006 tunnel - - 6262 3007 tunnel - - 7263 3008 tunnel - - 8264 3009 tunnel - - 9265 3010 tunnel - - 10266 3011 tunnel - - 11267 3012 tunnel - - 12268 3013 tunnel - - 13269 3014 tunnel - - 14270 3015 tunnel - - 15271 3016 tunnel - - 16Select option:Down, Enter entry number to edit, Extra detail, Goto row,Index search, Up, eXit

Middlebury: Slot 0 Interface Extension Table New EventNo ifIndex Slot Link VPI VCI--------------------------------------------------------------------------------0 77 3 1 0 161 80 4 0 0 162 88 6 0 0 163 89 6 1 0 164 113 12 1 0 165 116 13 0 0 1166 120 14 0 0 120

Select option:Enter entry number to edit, Extra detail, Goto row, Index search,eXit


PCX)

etting anging

IB

ted

Chapter 5: PCX Configuration/Status

Overview

This chapter describes the configuration and status of the Xedge Packet Circuit eXchange (slot controller. For a brief introduction to Xedge menu and screens refer to Chapter 2 in thisdocument, under the section on Navigating Xedge Menus and Screens .




• ATM Port Table Configuration

• Tunnel Configuration

• Interface Status

• Interface Table

• Node Status


Note Any major change in resources for the PCx will require a reboot of the PCx. Such changes include: sthe node address, setting the E.164 address, changing the internal IP address via the host file, or chthe LIM (for example from an OC3 to OCN, etc.).

Accessing the PCx Slot Controller

The PCx occupies two slots and is accessed as follows:

• When the PCx is in slot 0, select M(anage Configuration) from the root menu to access the MDisplay and Management menu for the device.

• When the PCx is not in slot 0, select T (elnet) from the root menu and then enter the corresponding slot number (e.g., slot9 ) in the IP address to call field. When prompted, enter the password. At the root menu for the slot, select M(anage Configuration) to access the MIB Display and Management menu for the device.

Supported LIMS

The PCx Controller supports the OC-N/STM-N LIM and a wide variety of additional LIMs, lisin the Xedge Hardware Installation Guide. Refer to Chapter 7, LIM Configuration for information on configuring these LIMs and the associated links.


PCX Configuration/Status Management Configuration

as tions.

Management Configuration1. From the root screen, select Manage . The MIB Display and Management screen appears

shown in the figure below. This display shows the Management screen with available op

Figure 5-1 MIB Display and Management Screen

2. From the MIB Display and Management screen, type 94 to select Management IF . The Management IF screen appears, similar to the example below.

Figure 5-2 Management IF Screen

3. Set the IP address, IP Mask and Broadcast Address.

4. Enable or disable the RIP Updates, Bcst Rec'd RIP, Broadcast RIP and Proxy ARPs, asrequired.

5. Refer to Table 5-1 for definitions of all other Management IF screen options.

Hartford: Slot 0 MIB Display and Management 710v12\700

00 system 42 Alarm Handler01 interfaces 43 CAC Configuration03 ip 69 Port, Link#, Location, ifIndex Map04 icmp 70 LIM and Link Information05 tcp 74 Ethernet Virtual Connections06 udp 82 Ethernet Statistics07 snmp 83 802.1d Bridging08 System Information 84 MPLS Label Switch Setup and Status09 Slot 0 Configuration/Status 85 PseudoWire Services12 Static Routing 94 Management IF16 Virtual Circuit Status 95 Node Status19 DSP DLIMs 97 IMA23 PVC Configuration/Status 101 QAAL224 SVC Configuration/Status27 System Timing References39 PDH Configuration/Status41 ILMI Configuration/StatusSelect option:Enter group number, save As, Load, sTatus, eXit,Last save file is `/mnt/flash0/config.cfg'.

Hartford: Slot 0 Management IF 710v12\700

00 IP Address: 172.16.69.18 14 VxC Cross Connect Table01 IP Mask: 255.255.0.0 15 VxC Cross Connect Status02 Broadcast Addr: 172.16.255.255 16 Termination from Physical Ethernet MAC Addr: 001219010468 17 Ethernet Termination from Pseudowire03 Tunnel Management Table 18 Termination of MPLS Label04 OutOfServ IP Addr: 255.255.255.255 19 IP v4 Point-to-Point Interface Standby MAC Addr: 20 IP v4 Broadcast Interface05 RIP Updates: disabled 21 Tunnel STP Group06 Bcst Rec'd RIP: enabled 22 PW and MPLS Connection Table07 Broadcast RIP: disabled08 Proxy ARP: disabled09 VC Termination Table10 User Port IP Addr: 199.168.1.8011 User Port Mask: 255.255.255.012 User Port IP Bcst: 0.0.0.0 User Port MAC Add: 00121901046913 VCC/VPC TableSelect option:Enter option number or eXit


PCX Configuration/Status Management Configuration

Table 5-1 Management IF Options Definitions


IP Address The ip address for management Immediately

IP Mask The mask for management Immediately

Broadcast Addr The management broadcast address Immediately

MAC address MAC address for management port (Read only) --

Tunnel Management Select to set up a tunnel Immediately

OutofService IP Address: Not used by the PCx --

Standby MAC address Not used by the PCx --

RIP Updates Enable/Disable Rip2 Update from Ethernet port, default disabled.

Immediately

Bcst Rec'd RIP When disabled stops RIP updates of routes received on this port

Immediately

Broadcast RIP Disabled selects noneEnablemin selects mgnt onlyEnablefull selects all routs for RIP broadcasts to port.Default disabled

Immediately

Proxy ARP Enable/Disable Proxy ARP on Ethernet port.Default disable.

Immediately

VC Termination Not supported in this release --

User Port IP Address Not supported in this release --

User Port Mask Not supported in this release --

Mgnt UserPort IP Bcst Not supported in this release --

User Port MAC Address Not supported in this release --

VCC/VPC Table Not supported in this release --

VxC Cross Connect Table Not supported in this release --

VxC Cross Connect Status

Not supported in this release --

Termination from Physical Ethernet


Ethernet Termination from Pseudowire


Termination of MPLS Label


IPv4 Point-to-Point Interface


IPv4 Broadcast Interface Not supported in this release --


PCX Configuration/Status ATM Port Configuration

.

e at the

ATM Port ConfigurationConnecting SAPs to ATM Ports

1. From the MIB Display and Management Screen, select SVC Configuration/Status , then select SVC Resource table .

2. Select E (xtra detail), then select G (o to row) and enter 22 . A detail for SAP 22 is shown below. Note that the default configuration assigns Logical SAP 22 to Logical ATM Port 6

Figure 5-3 Typical SVC Resource Table (showing SAP 22)

3. From the MIB Display and Management Screen, select Port, Link#, Location, if Index Map , then select 0 . The ATM Port Table appears at the Summary level.

4. Select Extra to advance to the Extra Detail screen, then select Go to row and enter the ATM port of interest, for example, 6 . The detail for ATM port 6 appears as shown below. ThUse this screen to view or change the current port parameters on the PCx card. Note thdefault configuration assigns ATM port 6 to LIM 1 Link 0 via the ATM port table.

Figure 5-4 ATM Port Table (Extra Detail Screen)

Note At 99% of bandwidth, Traffic Shaping and UBR will be fully functional and free of errors.

Middlebury: Slot 0 SVC Resource Table 710v12\700Detail of SVC Resource Table entry 22------------------------------------------------------------------------------- SAP : 22 13 Max Conns : 120 28 UBR Reserv: 0 SAP Type : logical Cur Conns : 0 29 Signal Pro: uni3100 VPI/VCI Hi: low 14 ATM Port : 6 30 Route Prot: apex01 SVC VCI St: 0 15 VPCI/VPI M: off 31 Status : off02 SVC VCI En: 0 16 QoS-based : off 32 Preemption: enable03 SVC VPI St: 0 17 Restart Op: off04 SVC VPI En: 0 18 Dest E164 :05 SVP Start : 0 19 Auto Sap O: no06 SVP End : 0 20 Sap Utiliz: 9507 Max SAP Ra: 0 21 CBR Bw Lim: 100 Available : 0 22 VBR-RT Bw : 10008 Signal VCI: 5 23 VBR-NRT Bw: 10009 Signal VPI: 0 24 ABR Bw Lim: 10010 CDVT (uS) : 200 25 UBR Bw Lim: 10011 Interface : network 26 Differenti: off12 Policing : off 27 Pk Rate Li: 0

Select option:Down, Enter entry number to edit, Goto row, Index search, Summary,Up, eXit

Xedge Switch: Slot 0 ATM Port Table New EventDetail of ATM Port Table entry 6-------------------------------------------------------------------------------- ATM Port : 6 Use Count : 0 Mapping Type : atmpphysicalport Mapping Number : 32 Operational Sta: inactive Physical State : disabled00 Phy Port Locati: lim 101 Phy Port Number: 002 Bandwidth : 10000003 VC VCI Start : 004 VC VCI End : 81605 VC VPI Start : 006 VC VPI End : 207 VP Start : 508 VP End : 25509 Admin State : inactive10 Port Type : uniSelect option:Down, Enter entry number to edit, Goto row, Index search, Summary,Up, eXit


PCX Configuration/Status ATM Port Configuration

teps:

w. P 22

bers

VC

VC

5. To see the SAP to ATM Port association and status in one place perform the following s

• From the root menu select I (nternal).

• Select (Si) G(naling).

• Select S (ignal sap status).

• Select G (o to row) and then enter 22 . The Layer SAP status appears as shown beloThe Layer/SAP Status screen displays part of the table, with the top line showing SAconnected to ATM port 6 and indicating its status.

Figure 5-5 Layer/SAP Status Screen

Special Considerations

• When looking at connections in the PCx card’s Virtual Circuit Status screen, the Link numare displayed as the ATM port number.

• This release does not support SVCs for connection to the LIMs on the PCx card.

• When a PVC is created in the PVC Configuration/Status table, any connection which terminates on a PCx card must use the ATM port number as the link. For example:

• if a connection is to be made to LIM 1 Link0, this would be entered as Link 6 in the Pconfiguration.

• if a connection is to be made to LIM 2 Link 1 this would be entered as Link 23 in the Pconfiguration.

Xedge Switch: Slot 0 Layer/SAP Status 710ER6\700SAP Type TState DLState DatInt SSCF SSCOP Comment--------------------------------------------------------------------------------22 Logical Connecting Connecting Disconnected STATE11 STATE1 Port 623 Logical Connecting Connecting Disconnected STATE11 STATE1 Port 724 Logical Connecting Connecting Disconnected STATE11 STATE1 Port 825 Logical Connecting Connecting Disconnected STATE11 STATE1 Port 926 Logical Connecting Connecting Disconnected STATE11 STATE1 Port 1027 Logical Connecting Connecting Disconnected STATE11 STATE1 Port 1128 Logical Connecting Connecting Disconnected STATE11 STATE1 Port 1229 Logical Connecting Connecting Disconnected STATE11 STATE1 Port 1330 Logical Connecting Connecting Disconnected STATE11 STATE1 Port 1431 Logical Connecting Connecting Disconnected STATE11 STATE1 Port 1532 Logical Connecting Connecting Disconnected STATE11 STATE1 Port 1633 Logical Connecting Connecting Disconnected STATE11 STATE1 Port 1734 Logical Connecting Connecting Disconnected STATE11 STATE1 Port 1835 Logical Connecting Connecting Disconnected STATE11 STATE1 Port 1936 Logical Connecting Connecting Disconnected STATE11 STATE1 Port 2037 Logical Connecting Connecting Disconnected STATE11 STATE1 Port 21Select option:Down, Goto row, Up, eXit


PCX Configuration/Status Tunnel Configuration

ted to x:

l

Tunnel Configuration

Creating a Tunnel creates an access point to the router. A VC (PVC or SPVC) must be creaattach to that access point. The following rules apply for creating a VC to a tunnel on the PC

Tunnel Procedure

1. From the MIB Display and Management screen, select Management IF .

2. Select Tunnel Management Table . The Tunnel Management Table summary lists alexisting tunnels by index number, from 0 to 127. An example summary is shown below.

3. Type E to display the Extra Detail view of the first entry (entry 0).

4. Use the D (own) or U (p) commands to move through the detail screens, or use the G o to command to jump to a specific entry’s detail view. An example screen is shown below.

5. To add an entry, type A. Enter an index number at the prompt, then press Enter . A series of prompts allow you to configure the tunnel parameters for the new entry. Refer to Table 5-2.

For PVC: For SPVC

At the PCx end of the VC:Slot = Slot number of PCx cardLink (ATM Port) = 0VPI = 1VCI = Tunnel Number

At the PCx end of the VC:Slot = Slot number of PCx cardSap = 16VPI = 1VCI = Tunnel Number

Xedge Switch: Slot 0 Tunnel Management Table New EventNo Index Name Type ifIndex Slot ATM Port VPI VCI--------------------------------------------------------------------------------0 32 ip 3032 1 0 1 321 33 ip 3033 2 0 1 332 34 ip 3034 3 0 1 343 35 ip 3035 4 0 1 354 36 ip 3036 5 1 1 365 37 ip 3037 6 1 1 376 38 ip 3038 7 0 1 387 39 ip 3039 8 0 1 398 40 ip 3040 0 0 0 09 41 ip 3041 0 0 0 010 42 ip 3042 11 0 1 4211 43 ip 3043 0 0 0 012 44 ip 3044 0 0 0 013 45 ip 3045 0 0 0 014 46 ip 3046 15 0 1 46

Select option:Add entry, Enter entry number to edit, Extra detail, Goto row,Index search, Kill entry, Right, eXit

Xedge Switch: Slot 0 Tunnel Management Table New EventDetail of Tunnel Management Table entry 0------------------------------------------------------------------------------- Index : 32 09 IP Address : 0.0.0.000 Name : 10 Netmask : 0.0.0.001 Type : ip 11 P-t-P IP Addres: 0.0.0.0 ifIndex : 3032 12 Allow RIP1x : yes Slot : 1 ATM Port : 0 VPI : 1 VCI : 3202 Broadcast RIP : disabled Operation State: running spvc03 Tunnel State : up04 Status : valid05 Max Priority : 706 Min Priority : 007 Main Intf Index: 008 Metric Offset : 0Select option:Add entry, Down, Enter entry number to edit, Goto row, Index search,Kill entry, Summary, eXit


PCX Configuration/Status Tunnel Configuration

o the g rate

tunnel

n an ed to

ssary CI

Special Tunnel Considerations

• For a VC to a tunnel on the PCx, the flow of cells from the PCx to the Fabric is shaped tPeak Cell Rate contract that has been set up in the PVC or SPVC. The minimum shapinallowed is 1000 cells per second.

• For tunnel type, select IP Type when the tunnel is either a Data tunnel or a Managementto a node that is not adjacent in the network topology.

• A MOLN type tunnel is a specialized IP tunnel for management traffic, with an endpoint oadjacent node (PVC) or non-adjacent node (SPVC) in the topology. You will not be allowterminate more than one MOLN tunnel on the same link.

• The LIMs on the PCx do not automatically create a 0/16 MOLN when set to NNI. It is neceto build a tunnel from slot 0 to the LIM port of a PCx. The VPI/VCI must equal the VPI/Vof the adjacent node on the LIM port (usually 0/16).

Table 5-2 Tunnel Management Table Details


Index Tunnel Number 1-128, corresponds to the Tunnel interfaces 3001 thru 3128.

Immediately

Name Mnemonic name for tunnel Immediately

Type Ip or MOLN (Future support: Pseudowire, eth vc and eth llc) (See Special Tunnel Considerations above.)

Immediately

Interface Number

Interface assigned = Tunnel Number + 3000 Read only

Slot Target slot for tunnel Read only

ATM Port Target link for tunnel Read only

VPI Target VPI for tunnel Read only

VCI Target VCI for tunnel Read only

Broadcast RIP Disabled selects none. (Default)Enablemin selects mgnt only.Enablefull selects all routs for RIP broadcasts to port.

Immediately

Operational State

Down, Running-PVC, or Running SVC Read only

Tunnel State Up or Down Immediately

Status Valid or Invalid Immediately

Max Priority Received packets will be routed to a tunnel if its TOS value is within the maximum priority range.

Immediately

Min Priority Received packets will be routed to a tunnel if its TOS value is within the minimum priority range.

Immediately

Main Intf Index Index value of highest TOS value tunnel. Examples:T1: Max PRI = 7, Min PRI = 4, Main Intf Index = 0 (not used).T2 : Max PRI = 3, Min PRI = 2, Main Intf Index = 1.T3 : Max PRI = 1, Min PRI = 0, Main Intf Index = 1.

Immediately

Metric Offset (Not supported in this release) --

IP Address Address of local end of tunnel. (only used on Main Interface Index tunnels.)

--

Net Mask Net mask for tunnel address. --

P-t-P Address Address of remote end of tunnel. --

Allow RIP1x Yes or No Immediately


PCX Configuration/Status Interface Status

w.

Interface Status

1. From the Root Menu select Manage Configuration .

2. Select Interfaces , then select Interface Table . The initial Interface Table screen appears, with the first 15 interfaces. To view the rest of the interfaces (16 - 24), select Down .

Figure 5-6 Interface Table

Line numbers 0 to 19 contain the fixed interfaces:

• Lo , eth0 , eth1 , br0 and sl0 of the PCx card

• Virtual connections to slots 1 to 15

Line numbers 20 and beyond are added automatically when:

• An ATM port is defined as NNI. In the example screen shown above: - Line 20 shows that slot 3 link 0 has a MOLN connection. - Line 21 shows that slot 3 link 1 has a MOLN connection. - Line 22 shows that slot 5 link 0 has a MOLN connection. - Line 23 shows that slot 6 link 1 has a MOLN connection.

• An ip tunnel is created. - Line 24 shows that an ip tunnel was created on interface 3033.

3. Select Extra Detail . The detail screen for the Interface table appears as shown beloRefer to Table 5-3 for definitions of all Interface Table entries.

Xedge Switch: Slot 0 Interface Table New EventNo ifIndex Description Type M T U Link Speed Physical Address--------------------------------------------------------------------------------0 1 lo software 16436 01 2 sl0 other 1518 02 3 br0 ethernet 1500 0 0012190105693 41 slot01 other 4000 04 42 slot02 other 4000 05 43 slot03 other 4000 06 44 slot04 other 4000 07 45 slot05 other 4000 08 46 slot06 other 4000 09 47 slot07 other 4000 010 48 slot08 other 4000 011 49 slot09 other 4000 012 50 slot10 other 4000 013 51 slot11 other 4000 014 52 slot12 other 4000 015 53 slot13 other 4000 0Select option:Down, Enter entry number to edit, Extra detail, Goto row,Index search, Right, eXit

Xedge Switch: Slot 0 Interface Table New EventNo ifIndex Description Type M T U Link Speed Physical Address-------------------------------------------------------------------------------16 44 slot12 other 4000 017 45 slot13 other 4000 018 46 slot14 other 4000 019 47 slot15 other 4000 020 48 moln30 other 4000 021 49 moln31 other 4000 022 50 moln50 other 4000 023 51 moln61 other 4000 024 52 iptun33 other 4000 0

Select option:Enter entry number to edit, Extra detail, Goto row, Index search, Right, Up eXit


PCX Configuration/Status Interface Status

Table 5-3 Interface Table Detail Screen

Parameter Definition

If Index Interface Index 1-3255 Read only

Description Textstring containing interface information, typically includes manufacturer name, product name and the version of the hardware interface

Read only

Type Type of interface, distinguished by the physical/link protocol(s) immediately `below' the network layer in the protocol stack.

Read only

MTU Size of largest datagram which can be sent/received on the interface (in octets) Read only

Link Speed Estimate of the interface's current or nominal bandwidth in bits per second. Read only

Physical Address Interface address at the protocol layer immediately `below' the network layer in the protocol stack.

Read only

Admin Status The desired state of the interface: Up, Down, or Testing. Read only

Oper Status Current operational state of the interface: Up, Down, or Testing. Read only

Time Last State SysUpTime at the time the interface entered its current operational state. Read only

Rcv Octet Count Total number of octets received Read only

Rcv Ucast Packets Total number of subnetwork-unicast packets delivered to a higher-layer protocol Read only

Rcv N Ucast Pack Total number of subnetwork-broadcast or subnetwork-multicast packets delivered to a higher layer protocol

Read only

Rcv Discards Total number of error free packets discarded due to other problems such as buffer availability

Read only

Rcv Errors Total number of packets discarded due to errors Read only

Rcv Unknown Pro Total number of packets discarded because of unknown protocol Read only

Xmit Octet Coun Total number of octets transmitted Read only

Xmit Ucast Pack Total number of packets requested to be transmitted including those discarded or not sent

Read only

Xmit NUCast Pac Total number of subnetwork broadcast or subnetwork-multicast packets requested to be transmitted including those that were discarded or not sent

Read only

Xmit Discards Total number of error free packets discarded due to other problems such as buffer availability

Read only

Xmit Errors Total number of packets discarded due to errors Read only

Xmit Q Length Length of the output packet queue Read only

ifSpecific Refers to MIB definitions specific to the media used to realize the interface. Read only

Xedge Switch: Slot 0 Interface Table New EventDetail of Interface Table entry 0------------------------------------------------------------------------------- ifIndex : 1 Xmit UCast Pack: 424 Description : lo Xmit NUCast Pac: 0 Type : softwareLoopback Xmit Discards : 0 M T U : 16436 Xmit Errors : 0 Link Speed : 0 Xmit Q Length : 0 Physical Addres: ifSpecific :0 Admin Status : up Oper Status : up Time Last State: 0 Rcv Octet Count: 32975 Rcv UCast Packe: 424 Rcv NUCast Pack: 0 Rcv Discards : 0 Rcv Errors : 0 Rcv Unknown Pro: 0 Xmit Octet Coun: 32975Select option:Down, Enter entry number to edit, Goto row, Index search, Summary,eXit


PCX Configuration/Status Node Status

link try

Node Status1. From the Root Menu select Manage Configuration , then select Node Status . The

Node Status menu appears, with the following status options:

• Link State Table


• Interface Extension Table

Figure 5-7 Node Status Menu

2. Select the Link State Table option. The Link State Table appears, similar to the example below. In the example screen below, entry numbers 0 through 15 correspond tonumbers 0 through 15 associated with the 16 interfaces for the slot-0 controller. Each endefines the interface and the status of the link as follows:

• Up/Down indicates the link state is up or down.• Stop indicates that the card or interface is disabled or is not present.• Off indicates that the link is not used or cannot be configured.

Table 5-4 Link State Table

Hartford: Slot 0 Node Status New Event

nodeMaxNoLinks: 00 Link State Table1 Interface Translation Table2 Interface Extension Table


Hartford: Slot 0 Link State Table New EventNo Slot Link Interface Index State--------------------------------------------------------------------------------0 0 0 64 up1 0 1 65 off2 0 2 66 off3 0 3 67 off4 0 4 1004 off5 0 5 1005 off6 0 6 1006 off7 0 7 1007 off8 0 8 1008 off9 0 9 1009 off10 0 10 1010 off11 0 11 1011 off12 0 12 1012 off13 0 13 1013 off14 0 14 1014 off15 0 15 1015 offSelect option:Down, Enter entry number to edit, Extra detail, Goto row,Index search, eXit



n the s (0

ns

own

3. Select the D own command to show the next display of interfaces and ports on the rnode. Iexample below, entry numbers 16 to 31 display interface information for the first four linkto 3) associated with slots 1 through 6.

Figure 5-8 Link State Table (Continuation)

4. Use the Down command to display the remaining link status information. The last screeshow information for any IP tunnels that have been created.

5. Type X to return to the Node Status menu.

6. From the Node Status menu, select Interface Translation Table . The status screen appears, similar to the example below. This screen displays the translation from Interface Index to either Slot and Link, or to Tunnel number. A summary of this data is shin Table 5-3.

Figure 5-9 Interface Translation Table

7. Type X to return to the Node Status menu.

Hartford: Slot 0 Link State Table New EventNo Slot Link Interface Index State-------------------------------------------------------------------------------16 2 0 72 up17 2 1 73 up18 2 2 74 stop19 2 3 75 stop20 3 0 76 up21 3 1 77 up22 3 2 78 stop23 3 3 79 stop24 4 0 80 up25 4 1 81 up26 4 2 82 stop27 4 3 83 stop28 6 0 88 up29 6 1 89 stop30 6 2 90 stop31 6 3 91 down Select option:Down, Enter entry number to edit, Extra detail, Goto row,Index search, Up, eXit

Hartford: Slot 0 Interface Translation Table New EventNo Interface Index Interface Type Slot Link Tunnel Number--------------------------------------------------------------------------------0 64 link 0 0 -1 65 link 0 1 -2 66 link 0 2 -3 67 link 0 3 -4 68 link 1 0 -5 69 link 1 1 -6 70 link 1 2 -7 71 link 1 3 -8 72 link 2 0 -9 73 link 2 1 -10 74 link 2 2 -11 75 link 2 3 -12 76 link 3 0 -13 77 link 3 1 -14 78 link 3 2 -15 79 link 3 3 -Select option:Down, Enter entry number to edit, Extra detail, Goto row,Index search, eXit



le

.

8. From the Node Status menu, select Interface Extension Table to view, add, or edit configured management connections for the slot controller. The Interface Extension Tabscreen appears, similar to the example below.

Figure 5-10 Interface Extension Table

9. In the example above, several management connections have been configured.

• Type an entry number to edit an existing connection.

• Select Down to view any additional configured connections.

• For a long list, use the Goto row or Index search to view a specific connections


Note Refer to Chapter 7, LIM Configuration for information on supported LIMs for the PCx Slot Controller.

Hartford: Slot 0 Interface Extension Table New EventNo ifIndex Slot Link VPI VCI-------------------------------------------------------------------------------0 80 4 0 0 161 81 4 1 0 162 1006 0 6 0 16



mory

unit.

e node e LIM.

edge llation ports,

the

d, enter

se the edge

Chapter 6: PCL Configuration/Status

PCL Configuration OverviewQuick Start Configuration

The Xedge PCL comes equipped with two quick-start configuration files stored in its Flash methat can be activated by the user to quickly set up the PCL for the following applications:

• Up to eight T1 IMA Links <---> One DS3 (HEC or PLCP)

• Up to eight E1 IMA Links <---> One E3 (HEC or PLCP)

Note Use the Quick Start Configuration Guide in this chapter, or the Installation Checklist provided with your

Note Any major resource change for the PCL requires a reboot of the PCL. Such changes include: setting thaddress, setting the E.164 address, changing the internal IP address via the host file, or changing th

Installation and Cable ConnectionsThe Xedge PCL slot controller and LIMs are shipped from the factory installed in the 1RU X6002 chassis. The chassis can be rack-mounted as described in the Xedge Hardware InstaGuide (Doc. No. 032R440-000). Make cable connections to the Craft port, Management/Userand LIMs for your application, as described in the table below.

Accessing the PCL Slot Controller

The PCL occupies both slots in the Xedge 6002 chassis and is accessed as follows:

• For local management, select M(anage Configuration) from the slot-0 root menu to access MIB Display and Management menu for the device.

• For remote management, Telnet to the IP address configured in the node. When promptethe username and password to access the slot-0 root menu.

Note IMPORTANT! To comply with Class A EMI-RFI Suppression requirements, TX and RX cables must uBelden Coaxial Cable, P/N 9054 or equivalent, and ferrite beads must be installed as shown in the XHardware Installation Guide, or the Xedge PCL/IMA+ Quick Reference supplied with your device.

Table 6-1 Xedge PCL/IMA+ LIM Cabling

Connector Description Part Number

Xedge 6002 Craft port RJ45 Ethernet straight-through shielded cableRJ45 to DB9 Female adapter

GDC 027H251-XXXGDC 029H015-001

Xedge PCL Mgmt/User port RJ45 Ethernet straight through shielded cable, 5, 15, 25,100 ft GDC 027H521-XXX

DSX1 or E1 IMA+ LIM T1/E1 50-pin RJ48M to 8-port RJ48C break-out cable assy GDC 025H603-006

DSX1 IMA+ LIM 100 Ohm DS1 Distribution Panel Kit with two 100 Ohm, 25-twisted pair, shielded cables.

GDC 032M131-001

E1 IMA+ LIM 120 Ohm E1 Distribution Panel Kit with two 120 Ohm, 25-twisted pair shielded cables.

GDC 032M164-001

E1 IMA+ LIM 75 Ohm E1 Distribution Panel Kit with two 120 Ohm, 25-twisted pair shielded cables, 75 Ohm adapter and 16 120 Ohm 4-twisted pair shielded cables.

GDC 032M165-001

DS3-2C or E3-2C LIM Belden Coax cable (or equivalent) Belden 9054


PCL Configuration/Status Using Stored Configurations

used s.

eeded.

ulting hat

1

MI-ge

ation

ork

MA+”

QUICK START CONFIGURATION GUIDEfor the Xedge PCL and IMA+ LIMs

Using Stored Configurations

This Quick Start Configuration Guide sets up the PCL controller for either of two commonly applications: PCL with DS3-2C and DSX1 IMA+ LIMs, or PCL with E3-2C and E1 IMA+ LIMEach procedure activates a particular configuration script stored in the PCL controller’s flashmemory.

Note Consult other chapters in this document and in related documentation listed inside the front cover as n

Quick Start Configuration Files

The table below identifies the stored configuration file names, the required LIMs, and the resapplication. Use the file and LIMs that match your network environment. In the procedures tfollow, you will be able to fine-tune the configuration as needed.

Pre-Configuration Checklist

1. Be sure to leave all jumpers on the LIMs as set at the factory.

2. For DS3/IMA or E3/IMA applications, check that the DS3-2C or E3-2C LIM is in the LIMposition (lower slot). Check that the corresponding DSX1 IMA+ LIM or E1 IMA+ LIM is inthe LIM2 position (upper slot).

3. Make appropriate cable connections as required. Refer to Table 6-1 as needed.

4. If required in your network, be sure to comply with all domestic or international Class A ERFI suppression requirements by installing ferrite beads on cables, as shown in the XedHardware Installation Guide (032R440-000).

5. To navigate quickly through a series of menus and commands, the Quick Start configurprocedures will indicate the starting screen, and then provide a series of characters thatrepresent individual selections on the displayed screens. For example, “From the root menu, select F, D to access the Directory.”

6. Perform all of the steps in the Quick Start Configuration procedure that match your netwapplication. Then perform the Quick Status & Diagnostics to verify that setup.

Note For these applications, the Xedge PCL must be installed in the Xedge 6002 chassis with the DSX1 “ILIMs or the E1 “IMA+” LIM. The PCL does not support DSX1 “IMA” LIMs or E1 “IMA” LIMs.

Quick Start File Name LIM1 LIM2 Xedge PCL Application

confT13.4hec DS3-2C LIM DSX1 IMA+ LIM Sets up 4 T1 IMA Links over one DS3 (HEC)

confE13.4hec E3-2C LIM E1 IMA+ LIM Sets up 4 E1 IMA Links over one E3 (HEC)


PCL Configuration/Status Quick Start Configurations - for All Sites

ettings

ions.

on the

Quick Start Configurations - for All Sites

Quick Tips• In this section, all procedures start from the terminal interface root menu, similar to Figure 6-1.

Note that some procedures can only be performed at the craft port.

• In a typical navigation string such as M,19,3, the alphanumeric characters represent keystroke commands. The commas indicate pressing the Enter key.

• In a navigation string such as M,97,1,G [#] ,E,1,9,0 the [#] is a screen index number.

• To return to the root menu, press x (exit command) to back out of the screens.

• To correct a keystroke error, press the Esc key. If necessary, reload the factory default sas described in the procedure on Activating the Stored Configuration and start all over with a clean baseline.

Logging in to the PCL1. Make a craft or Telnet connection to the PCL (9600 baud, N-8-1, VT100, Raw ASCII).

2. Log in with the following name/password: root / MANAGERThe Xedge PCL root menu is displayed for slot-0, similar to the example below.

Figure 6-1 Xedge PCL Root Menu

3. At the PCL root menu, select options as follows:

• Type a highlighted capital letter from the root menu, then press Enter to select opt

• Type X to exit to a previous menu.

• Press the esc key to abort a change.

Note For more information on navigating the menus, review Chapter 1 in this manual under the paragraphs Xedge Terminal Interface as needed.

PCL OXFORD: Slot 0 Root Menu New Event

Slot 00 : Active PCL Received datacells = 10892Slot 01 : -------- Transmitted datacells = 92402

User: root From: telnet

Slot 0 Redund. available: No Slot 0 Redund: Main In-serv Sys. Ref.: NONE

PVCs Connected: 2 File transfer: InactiveSelect option:Diagnostics, Events, File system, Internal status,Manage configuration, self Restarts, Telnet, sVc routing,Warm start, eXit, LinK



ow:

Activating the Stored Configuration1. At the root menu, select F,D to view Directory screen, similar to the example below. This

screen lists available config files. The currently running configuration file is config.cfg .

2. Type X to return to the root menu.

3. At the root menu, select F,C to access the Select File screen, similar to the example bel

4. Use the arrow keys to highlight the configuration file that is appropriate for your site:

• confT13.4hec for 4 T1 links (HEC)

• confE13.4hec for 4 E1 links (HEC)

5. Press Enter to select the highlighted (“Copy From”) file.

6. Now use the arrow keys to move the highlight to the config.cfg file. Press Enter to selectthe highlighted (“Copy To”) file.

7. At the confirmation prompt, type Y (es) to overwrite the current configuration file.

8. From the root menu, type W, N to perform a Warm Start on slot-0. Type Y (es) to confirm. The node will come up running the new configuration.

PCL OXFORD: Slot 0 Directory New EventName Size Name Size--------------------------------------------------------------------------------<snmp><zebra>plcDS3.cfg 38212config_e3_imae1... 38424restart.slv 1970E3E1config.cfg 38548T3T1config.cfg 38193e3wtiming.cfg 38553pclE3.cfg 39216config.cfg.e3 38697startup_pcl.tz 2457663config.cfg 27551e1ds1.cod 86416alr_cls.txt 19158E1_DS3.cfg 39488E3_E1_IMA.cfg 38554

Select option:Extra detail, Path, eXit

→→→→

PCL OXFORD: Slot 0 Select File New Event

Select file to copy FROMCurrent directory: /mnt/flash0/--------------------w---------------------w-------------------------------------<..> x <snmp> x <zebra>plcDS3.cfg x config_e3_imae1... x restart.slvE3E1config.cfg x T3T1config.cfg x e3wtiming.cfgpclE3.cfg x config.cfg.e3 x startup_pcl.tzconfig.cfg x e1ds1.cod x alr_cls.txtconfT13.4hec x confE13.4hec x


→→→→

→→→→

PCL OXFORD: Slot 0 Select File New Event

Select file to copy TOCurrent directory: /mnt/flash0/--------------------w---------------------w-------------------------------------<..> x <snmp> x <zebra>plcDS3.cfg x config_e3_imae1... x restart.slvE3E1config.cfg x T3T1config.cfg x e3wtiming.cfgpclE3.cfg x config.cfg.e3 x startup_pcl.tzconfig.cfg x e1ds1.cod x alr_cls.txtconfT13.4hec x confE13.4hec x


→→→→

→→→→



Define the Node1. At the root menu, select M,0 to view the System screen, similar to the example below.

2. Define the following identifiers for the node as required:

• Select Option 0 to specify a name or contact number.

• Select Option 1 to specify the node name.

• Select Option 2 to specify the location.

3. When complete, press X to exit back to the confirmation prompt:

Save changed configuration (Y/N):

4. Type Y to save the configuration.

PCL OXFORD: Slot 0 system New Event

Device Description: General DataComm Xedge: Slot 0 Packet Cell Link LPM-1 Software Version 720er6

System Object ID: 1.3.6.1.4.1.251.3.7.16 System Up Time: 6988520 System Contact: Please enter a name1 System Name: PCL OXFORD2 System Location: Not Specified System Services: 79


→→→→

→→→→



address .

e

Set Tunnel Management IP AddressThis procedure changes the factory default IP address to a specific tunnel management IP for the node at the customer site. This procedure must be performed from the craft interface

Note IMPORTANT! Remote management of the node will be inoperable unless the IP address is correctlyconfigured at the craft port.

1. At the root menu, select M,94,3,E to access the Tunnel Management table, similar to thexample below.

2. Select Option 09 IP Address , then enter the new IP address for the node.

3. When complete, type X to exit back to the confirmation prompt:

Save changed configuration (Y/N):

4. Type Y to save the configuration.

5. At the root menu, select M,9,6 (Slot 0 Configuration screen).

6. At the prompt, edit the IP address, then press Enter.

7. Select 11 (Slot-0 IP Mask).

8. At the prompt, type 255.255.255.255 , then press Enter.

9. Type X,X to confirmation prompt, type Y to save.

PCL OXFORD: Slot 0 Tunnel Management Table New EventDetail of Tunnel Management Table entry 0------------------------------------------------------------------------------- Index : 1 09 IP Address : 10.2.2.200 Name : Mgmnt Tunnel 10 Netmask : 255.255.255.25501 Type : ip snap 11 P-t-P IP Address: 0.0.0.0 ifIndex : 3001 12 Allow RIP1x : no Slot : 0 ATM Port : 22 VPI : 2 VCI : 4302 Broadcast RIP : disabled Operation State: running pvc03 Tunnel State : up04 Status : valid05 Max Priority : 706 Min Priority : 007 Main Intf Index: 008 Metric Offset : 0Select option:Add entry, Enter Entry number to edit, Kill entry, Summary, eXit

→→→→ →→→→



et

e new

Change Tunnel Management VPI/VCIThis procedure can only be performed from the craft port.

1. At the root menu, select M,23,1,E to access the PVC Configuration/Status Table and sthe Management VC to valid (idle), as shown in the example below.

2. Select S to view the Summary screen, shown below. Then select M to move the Management VC.

3. At the Row to Move prompt, select 0 .

4. Press the Enter key six times to get the Source VCI prompt, as shown below. Type in thVCI, then press Enter. In the example screen, the new VCI will be 43 .

PCL OXFORD: Slot 0 PVC Configuration/Status Table New eventDetail of PVC Configuration/Status Table entry 0------------------------------------------------------------------------------- Dest Slot : 0 08 Sd Fd Mode: off 18 CLP1 Disc : off VBR1 C Dest Link : 0 09 Sd Bd Rate: 0 Dest VCI : 1 10 Bd MBS(Cel: 0 Dest VPI : 1 11 Sd Bd Mode: off Src Slot : 0 12 Service Ca: cbr Src Link : 22 13 Multicast : no Src VCI : 32 14 Direction : bidirect Src VPI : 1 15 Frame Disc: disallow00 Pk Fd Rate: 15 16 Enable UBR: on01 Fd CDVT(uS: 200 17 Status : valid02 Pk Fd Mode: off Error Code: ok03 Pk Bd Rate: 15 Num Leaves: -04 Bd CDVT(uS: 200 Fwd Int VP: 005 Pk Bd Mode: off Fwd Int VC: 006 Sd Fd Rate: 0 Bwd Int VP: 007 Fd MBS(Cel: 0 Bwd Int VC: 0Select option:Add entry, Down, Enter entry number to edit, Goto row, Index search,Kill entry, Move entry, Summary, eXit

→→→→ →→→→

PCL OXFORD: Slot 0 PVC Configuration/Status Table New EventNo Dest Slot Dest Link Dest VCI Dest VPI Src Slot Src Link Src VCI Src VPI-------------------------------------------------------------------------------0 0 0 1 1 0 22 32 11 0 6 0 0 0 22 0 0

Select option:Add entry, Enter Entry number to edit, Extra detail, Go to row,Index search, Kill entry, Move entry, Right, eXit

→ →→→


Row to move: [0-1]: 0 →→→→


Src VCI: [0-65535]: 43

→→→→



PI

etail

5. When the Source VPI prompt appears, type in the new VPI. In the example screen below, the new VPI will be 2 .

6. Press Enter once to complete the row. The Summary screen now shows the new VCI/Vvalues, as shown below.

7. Exit out of the Summary page until you are back at the PVC Configuration/Status Table Dscreen, as shown below (M,23,1,E ).

• Select 17 to view the status options, then select C to start the Management VC.

• Check that the Pk Fd Rate and the Pk Bd Rate are set at 15 .

8. The Management VPI/VCI changes are complete. Select X to exit out to the root menu.


Src VPI: [0-4095]: 2

→→→→


Select option:Add entry, Enter Entry number to edit, Extra detail, Go to row,Index search, Kill entry, Move entry, Right, eXit

→→→→

PCL OXFORD: Slot 0 PVC Configuration/Status Table New eventDetail of PVC Configuration/Status Table entry 0------------------------------------------------------------------------------- Dest Slot : 0 08 Sd Fd Mode: off 18 CLP1 Disc : off VBR1 C Dest Link : 0 09 Sd Bd Rate: 0 Dest VCI : 1 10 Bd MBS(Cel: 0 Dest VPI : 1 11 Sd Bd Mode: off Src Slot : 0 12 Service Ca: cbr Src Link : 22 13 Multicast : no Src VCI : 43 14 Direction : bidirect Src VPI : 2 15 Frame Disc: disallow00 Pk Fd Rate: 15 16 Enable UBR: on01 Fd CDVT(uS: 200 17 Status : running02 Pk Fd Mode: off Error Code: ok03 Pk Bd Rate: 15 Num Leaves: -04 Bd CDVT(uS: 200 Fwd Int VP: 105 Pk Bd Mode: off Fwd Int VC: 106 Sd Fd Rate: 0 Bwd Int VP: 107 Fd MBS(Cel: 0 Bwd Int VC: 122Select option:Add entry, Down, Enter entry number to edit, Goto row, Index search,Kill entry, Move entry, Summary, eXit

→→→→→→→→

→→→→

→→→→



sword Linux

the

VCI,

n is

Change the Root Password

For security purposes, it is important to change the factory default login name to a unique pasas soon as the new device is installed in the network. This procedure is executed within theoperating system and must be performed from the craft interface.

1. Log in to the PCL using following name/password: root / ADMIN Within three seconds, press the CTRL-C keys to access the Linux operating system.

• If more than three seconds lapse, the system advances to the PCL root menu. Exit out and try again.

• If successful, the Linux prompt string appears, for example, root@PCL IMA:~#

2. At the Linux prompt, type the following command:

passwd

3. When prompted, type a new password, then press Enter. If you choose a password thatsystem considers “weak”, a Bad Password advisory may display.

4. At the Retype password: prompt, type the new password again. The following confirmation appears. Your new password is now in effect.

Password for root changed by root

5. Exit the Linux system and terminate the session by typing:

exit

Note IMPORTANT! Always terminate the session after changing the password as described.Do not attempt to execute any other commands at the Linux prompt.

Configure SNMP Access

1. At the root menu, select M,8,2,A [new entry number] to add an SNMP Management destination to the Authentication Table.

2. With the new entry displayed in the Authentication Table, select E (new entry number) and type the SNMP parameters at the prompts:

• IP address for the new SNMP management station

• Community name is public (default)

• Access set to Read/Write

• Traps set to Send All

• Validity set to valid

3. When all settings are correct, exit out of the screen. At the confirmation prompt, type Y (es) to put the changes into effect.

4. Exit back to the root menu. The node is now ready for remote management.

• To add/remove IMA links, change cell delineation, or change the management VPI/parameters, refer to the next section on Fine-Tuning the PCL/IMA Configuration .

• If the current configuration suits your site requirements, basic PCL/LIM configuratiocomplete. Refer to the Status and Diagnostics section to monitor the IMA links.


PCL Configuration/Status Fine-Tuning the PCL/IMA Configuration

r

Fine-Tuning the PCL/IMA Configuration

Change D3 Parameters

The following procedure can be performed from the craft or Telnet interface.

1. At the root menu, select M,39,0,E to view the PLCP Configuration/Status screen, similato the example below.

• Check that Phy Framer is set to DS3

• Change Cell delin as desired to HEC or PLCP

• Change Scrambler as desired to SCRAMBLED or UNSCRAMBLED This setting must match at the LIM and at the connected device.

• Check that Chip Type is set to SUNI QJET

2. When all checks and changes are complete, set Option 10 Reconfigure to YES to put the changes into effect.

3. Select X to exit out to the root menu.

Change T1 Settings

The following procedure can be performed from the craft or Telnet interface.

1. At the root menu, select M,70,3,3,G [link number],E to access DS1 Link Configuration.

• Change Option 2 as desired: Enable or Disable

• Change Option 3 Scrambler as desired: SCRAMBLED or UNSCRAMBLED This setting must match at the LIM and at the connected device.

• Change Option 4 Framing as desired: sf or esf

• Set Option 5 Line Code as desired: ami or b8zs

• Set Option 6 Line Length as desired: A through F

2. Select X to back out to the root menu.

→→→→→→→→→→→→

→→→→

PCL OXFORD: Slot 0 PLCP Configuration/Status New EventDetail of PLCP Configuration/Status entry 0------------------------------------------------------------------------------- Link # : 0 RX Clock : up FE-ES : 000 Link Enabl: enabled Txed Cells: 113 FE-SES : 001 Link Statu: ignored Rxed Cells: 0 FE-UAS : 0 Link State: down HCS Errors: 002 Phy Framer: ds3 LOCD Defec: yes03 Cell Delin: hec based Yellow Def: no04 Scrambler : enabled LOF Defect: no05 XOR w/55H : enabled LOCD Alarm: yes06 SMDS Mode : disabled Yellow Ala: no07 Idle Cell : unassigned LOF Alarm : no08 Loopback : none Frame Errs: 009 Clear Coun: no BIP8 Errs : 010 Reconfigur: no FEBE Errs : 011 Lpbk Timeo: 1 ES : 0 Chip Type : suni qjet SES : 0 TX Clock : up UAS : 0Select option:Down, Enter entry number to edit, Goto row, Index search, Summary,eXit



r

Change E3 ParametersThe following procedure can be performed from the craft or Telnet interface.

1. At the root menu, select M,39,0,E to view the PLCP Configuration/Status screen, similato the example below.

• Check that Phy Framer is set to E3

• Check that Cell delin is set to HEC

• Change Scrambler as desired to SCRAMBLED or UNSCRAMBLED This setting must match at the LIM and at the connected device.

• Check that Chip Type is set to SUNI QJET

2. When all checks and changes are complete, set Option 10 Reconfigure to YES to put the changes into effect.


Change E1 SettingsThe following procedure can be performed from the craft or Telnet interface.

1. At the root menu, select M,70,2,3,G [link number],E to access E1 Link Configuration.

• Change Option 2 as desired: Enable or Disable

• Change Option 3 Scrambler as desired: SCRAMBLED or UNSCRAMBLED This setting must match at the LIM and at the connected device.

• Change Option 4 Framing as desired: basic or crc


→→→→→→→→→→→→

→→→→

PCL OXFORD: Slot 0 PLCP Configuration/Status New EventDetail of PLCP Configuration/Status entry 0------------------------------------------------------------------------------- Link # : 0 RX Clock : up FE-ES : 000 Link Enabl: enabled Txed Cells: 186801 FE-SES : 001 Link Statu: ignored Rxed Cells: 186797 FE-UAS : 0 Link State: up HCS Errors: 002 Phy Framer: e3 LOCD Defec: no03 Cell Delin: hec based Yellow Def: no04 Scrambler : enabled LOF Defect: no05 XOR w/55H : enabled LOCD Alarm: yes06 SMDS Mode : disabled Yellow Ala: no07 Idle Cell : unassigned LOF Alarm : no08 Loopback : none Frame Errs: 009 Clear Coun: no BIP8 Errs : 010 Reconfigur: no FEBE Errs : 011 Lpbk Timeo: 1 ES : 0 Chip Type : suni qjet SES : 0 TX Clock : up UAS : 0Select option:Down, Enter entry number to edit, Goto row, Index search, Summary,eXit



Removing an IMA LinkThe following procedure must be performed from the craft interface.

1. At the root menu, select M,69,0,G,22,E,9,B to access the ATM Port Table and set ATM Port 22 to INACTIVE as shown in the example below.

2. Exit out to the root menu. Next, select M,97,0,E,0,B to access the IMA Group Table andtake IMA Group 9 out of service, as shown in the example below.

→→→→

PCL OXFORD: Slot 0 ATM Port Table New eventDetail of ATM Port Table entry 22------------------------------------------------------------------------------- ATM Port : 22 Use Count : 2 Mapping Type : atmpimagroup Mapping Number : 48 Operational Sta: connection releasing Physical State : port up00 Phy Port Locati: ima01 Phy Port Number: 902 Bandwidth : 1077603 VC VCI Start : 004 VC VCI End : 81605 VC VPI Start : 006 VC VPI End : 207 VP Start : 508 VP End : 25509 Admin State : inactive10 Port Type : nniSelect option:Down, Enter entry number to edit, Goto row, Index search, Summary,Up, eXit

→→→→

PCL OXFORD: Slot 0 IMA Group Table New EventDetail of IMA Group Table entry 0------------------------------------------------------------------------------- Group Inde: 9 Tx Frame L: m128 Rx Actual : 80 Row Status: notInServi Rx Frame L: m128 4 Test Link : 0 IF Index : 5009 Diff Delay: 25 5 Test Patte: - NE State : operationa Least Dela: 1 6 Test Proc : disabled FE State : operationa Dif Dly Ma: 0 Tx OAM Lab: 3 Failure St: noFailure Alpha : 2 Rx OAM Lab: 3 Symmetry : symmetricO Beta : 21 Min Tx Lin: 1 Gamma : 12 Min Rx Lin: 1 Running Se: 57643 NE Tx Clk : ctc Unavail Se: 2 FE Tx Clk : ctc NE Failure: 0 Tx Timing : 0 Tx Avail C: 28736 Rx Timing : 0 Rx Avail C: 28736 Last Chang: 14 Jul 200 Tx Cfg Lin: 8 Tx IMA ID : 1 Rx Cfg Lin: 8 Rx IMA ID : 1 Tx Actual : 8Select option:Down, Enter entry number to edit, Goto row, Index search, Summary,eXit



.

.

3. Exit out to the root menu. Now select M,97,1,G [link# to remove],E,0,B to access the IMA Link Table and take the desired link [n] out of service, as shown in the example below

4. Repeat step 3. for all other links to be removed.

5. Exit out to the root menu and select M,97,0,E,0,A to access the IMA Group table againNow set the IMA Group 9 to Active, as shown in the example below.

6. Exit out to the root menu and select M,69,0,G,22,E,9,A to access the ATM Port table again. Now put the ATM Port 22 back in active service, as shown in the example below.

PCL OXFORD: Slot 0 IMA Link Table New EventDetail of IMA Link Table entry 7------------------------------------------------------------------------------- Link Index : 4207 FE Unavail Secs: 00 Row Status : notInService NE Tx Unusbl Se: 11 Group Index : 9 NE Rx Unusbl Se: 1 NE Tx State : notInGroup FE Tx Unusbl Se: 2 NE Rx State : notInGroup FE Rx Unusbl Se: 1 FE Tx State : notInGroup NE Tx Failures : 0 FE Rx State : notInGroup NE Rx Failures : 0 NE Rx Fail Stat: noFailure Rx Test Pattern: 0 FE Rx Fail Stat: noFailure Test Proc Statu: disabled Tx LID : 7 Rx LID : 7 Relative Delay : 0 IMA Violations : 0 NE Sev Err Secs: 1 FE Sev Err Secs: 1 NE Unavail Secs: 0Select option:Down, Enter entry number to edit, Goto row, Index search, Summary,Up, eXit

→→→→

→→→→

PCL OXFORD: Slot 0 IMA Group Table New EventDetail of IMA Group Table entry 0------------------------------------------------------------------------------- Group Inde: 9 Tx Frame L: m128 Rx Actual : 70 Row Status: active Rx Frame L: m128 4 Test Link : 0 IF Index : 5009 Diff Delay: 25 5 Test Patte: - NE State : operationa Least Dela: 1 6 Test Proc : disabled FE State : operationa Dif Dly Ma: 0 Tx OAM Lab: 3 Failure St: noFailure Alpha : 2 Rx OAM Lab: 3 Symmetry : symmetricO Beta : 21 Min Tx Lin: 1 Gamma : 12 Min Rx Lin: 1 Running Se: 62833 NE Tx Clk : ctc Unavail Se: 2 FE Tx Clk : ctc NE Failure: 0 Tx Timing : 0 Tx Avail C: 25144 Rx Timing : 0 Rx Avail C: 25144 Last Chang: 14 Jul 200 Tx Cfg Lin: 7 Tx IMA ID : 1 Rx Cfg Lin: 7 Rx IMA ID : 1 Tx Actual : 7Select option:Down, Enter entry number to edit, Goto row, Index search, Summary,eXit

→→→→

PCL OXFORD: Slot 0 ATM Port Table New eventDetail of ATM Port Table entry 22------------------------------------------------------------------------------- ATM Port : 22 Use Count : 2 Mapping Type : atmpimagroup Mapping Number : 48 Operational Sta: active Physical State : port up00 Phy Port Locati: ima01 Phy Port Number: 902 Bandwidth : 1077603 VC VCI Start : 004 VC VCI End : 81605 VC VPI Start : 006 VC VPI End : 207 VP Start : 508 VP End : 25509 Admin State : active10 Port Type : nniSelect option:Down, Enter entry number to edit, Goto row, Index search, Summary,Up, eXit



ed,

n.

7. The selected IMA link is now removed from service. To verify that the link is not being usexit out to the root menu and access the Performance Monitoring Page for the LIM.

• For the DSX1 IMA LIM, select M,70,3,1

• For the E1 IMA LIM, select M,70,2,1

The example screen below shows no TX/RX on the out of service link.

Note The E1 Performance Monitoring Page and the DS1 Monitoring Page will display the same verificatio

PCL OXFORD: Slot 0 E1 Performance Monitoring Page New EventNo ifIndex Link Location Clr Cnts Tx Count Tx Rate Rx Count Rx Rate FERR--------------------------------------------------------------------------------0 4200 lim2/e1-1 no 16870 38 16869 37 01 4201 lim2/e1-2 no 16870 38 16870 39 02 4202 lim2/e1-3 no 16871 38 16871 39 03 4203 lim2/e1-4 no 16870 37 16870 37 04 4204 lim2/e1-5 no 16870 37 16869 37 05 4205 lim2/e1-6 no 16870 37 16870 36 06 4206 lim2/e1-7 no 16870 37 16870 36 07 4207 lim2/e1-8 no 11605 0 11604 0 08 4208 lim2/e1-9 no 0 0 0 0 09 4209 lim2/e1-10 no 0 0 0 0 010 4210 lim2/e1-11 no 0 0 0 0 011 4211 lim2/e1-12 no 0 0 0 0 012 4212 lim2/e1-13 no 0 0 0 0 013 4213 lim2/e1-14 no 0 0 0 0 014 4214 lim2/e1-15 no 0 0 0 0 015 4215 lim2/e1-16 no 0 0 0 0 0Select option:Down, Enter entry number to edit, Extra detail, Goto row,Index search, Right, eXit

→→→→ →→→→



Adding an IMA LinkThe following procedure must be performed from the craft interface.

1. At the root menu, select M,69,0,G,22,E,9,B to access the ATM Port Table and set ATM Port 22 to INACTIVE as shown in the example below.

2. Exit out to the root menu. Next, select M,97,0,E,0,B to access the IMA Group Table andtake IMA Group 9 out of service, as shown in the example below.

→→→→

PCL OXFORD: Slot 0 ATM Port Table New eventDetail of ATM Port Table entry 22------------------------------------------------------------------------------- ATM Port : 22 Use Count : 2 Mapping Type : atmpimagroup Mapping Number : 48 Operational Sta: connection releasing Physical State : port up00 Phy Port Locati: ima01 Phy Port Number: 902 Bandwidth : 1077603 VC VCI Start : 004 VC VCI End : 81605 VC VPI Start : 006 VC VPI End : 207 VP Start : 508 VP End : 25509 Admin State : inactive10 Port Type : nniSelect option:Down, Enter entry number to edit, Goto row, Index search, Summary,Up, eXit

→→→→

PCL OXFORD: Slot 0 IMA Group Table New EventDetail of IMA Group Table entry 0------------------------------------------------------------------------------- Group Inde: 9 Tx Frame L: m128 Rx Actual : 80 Row Status: notInServi Rx Frame L: m128 4 Test Link : 0 IF Index : 5009 Diff Delay: 25 5 Test Patte: - NE State : operationa Least Dela: 1 6 Test Proc : disabled FE State : operationa Dif Dly Ma: 0 Tx OAM Lab: 3 Failure St: noFailure Alpha : 2 Rx OAM Lab: 3 Symmetry : symmetricO Beta : 21 Min Tx Lin: 1 Gamma : 12 Min Rx Lin: 1 Running Se: 57643 NE Tx Clk : ctc Unavail Se: 2 FE Tx Clk : ctc NE Failure: 0 Tx Timing : 0 Tx Avail C: 28736 Rx Timing : 0 Rx Avail C: 28736 Last Chang: 14 Jul 200 Tx Cfg Lin: 8 Tx IMA ID : 1 Rx Cfg Lin: 8 Rx IMA ID : 1 Tx Actual : 8Select option:Down, Enter entry number to edit, Goto row, Index search, Summary,eXit



.

3. Exit out to root menu. Now select M,97,1,G [link# to be added],E,1,9,0,B to access the IMA Link Table, assign a new link [n] to IMA Group 9, and set it to active as shown.

4. Repeat step 3. for all other links to be added.

5. Exit out to the root menu and select M,97,0,E,0,A to access the IMA Group table againNow set the IMA Group 9 to Active, as shown in the example below.

6. Exit out to the root menu and select M,69,0,G,22,E,9,A to access the ATM Port table again. Now put the ATM Port 22 back in active service, as shown in the example below.

→→→→

PCL OXFORD: Slot 0 IMA Link Table New EventDetail of IMA Link Table entry 7------------------------------------------------------------------------------- Link Index : 4207 FE Unavail Secs: 00 Row Status : active NE Tx Unusbl Se: 21 Group Index : 9 NE Rx Unusbl Se: 2 NE Tx State : unusableInhibited FE Tx Unusbl Se: 12 NE Rx State : unusableInhibited FE Rx Unusbl Se: 11 FE Tx State : unusableInhibited NE Tx Failures : 0 FE Rx State : unusableInhibited NE Rx Failures : 0 NE Rx Fail Stat: blocked Rx Test Pattern: 0 FE Rx Fail Stat: blocked Test Proc Statu: disabled Tx LID : 7 Rx LID : 7 Relative Delay : 0 IMA Violations : 0 NE Sev Err Secs: 2 FE Sev Err Secs: 2 NE Unavail Secs: 0Select option:Down, Enter entry number to edit, Goto row, Index search, Summary,Up, eXit

→→→→

→→→→


→→→→

PCL OXFORD: Slot 0 ATM Port Table New eventDetail of ATM Port Table entry 22------------------------------------------------------------------------------- ATM Port : 22 Use Count : 2 Mapping Type : atmpimagroup Mapping Number : 48 Operational Sta: active Physical State : port up00 Phy Port Locati: ima01 Phy Port Number: 902 Bandwidth : 1077603 VC VCI Start : 004 VC VCI End : 81605 VC VPI Start : 006 VC VPI End : 207 VP Start : 508 VP End : 25509 Admin State : active10 Port Type : nniSelect option:Down, Enter entry number to edit, Goto row, Index search, Summary,Up, eXit



ot

n.

7. The new IMA link is now in service. To verify that the link is being used, exit out to the romenu and access the Performance Monitoring Page for the LIM.

• For the DSX1 IMA LIM, select M,70,3,1

• For the E1 IMA LIM, select M,70,2,1

The example screen below now shows TX/RX on the new in-service link.

Note The E1 Performance Monitoring Page and the DS1 Monitoring Page will display the same verificatio

PCL OXFORD: Slot 0 DS1 Performance Monitoring Page New EventNo ifIndex Link Location Clr Cnts Tx Count Tx Rate Rx Count Rx Rate FERR--------------------------------------------------------------------------------0 4200 lim2/ds1-1 no 15969326 1850 15969326 1850 01 4201 lim2/ds1-2 no 15965598 1761 15965597 1860 02 4202 lim2/ds1-3 no 15968510 1827 15968512 1828 03 4203 lim2/ds1-4 no 15963359 1757 15963359 1757 04 4204 lim2/ds1-5 no 15971824 1843 15971825 1843 05 4205 lim2/ds1-6 no 15966899 1857 15966899 1758 06 4206 lim2/ds1-7 no 15959165 1846 15969167 1846 07 4207 lim2/ds1-8 no 117029 1752 117034 1751 08 4208 lim2/ds1-9 no 0 0 0 0 09 4209 lim2/ds1-10 no 0 0 0 0 010 4210 lim2/ds1-11 no 0 0 0 0 011 4211 lim2/ds1-12 no 0 0 0 0 012 4212 lim2/ds1-13 no 0 0 0 0 013 4213 lim2/ds1-14 no 0 0 0 0 014 4214 lim2/ds1-15 no 0 0 0 0 015 4215 lim2/ds1-16 no 0 0 0 0 0Select option:Down, Enter entry number to edit, Extra detail, Goto row,Index search, Right, eXit

→→→→ →→→→



n

or

Change T1/E1 Link Used for Timing1. At the root menu, select M,27 to access the System Timing References screen, as show

below.

2. Select Option 4 to view the Primary Line Reference screen.

3. Select Option 2 (Reference Select) to view the Detail screen that lists the links available fsystem timing, similar to the example below.

4. Select an option letter (A - P ) to specify a link (0 - 15 ) to be used for system timing.

PCL OXFORD: Slot 0 System Timing References New Event

00 Automatic REVERT: yes 14 Primary External Config01 REVERT Timer: 30 15 Secondary External Config02 Activate REVERT: no 16 Primary External Status03 Force Secondary LIMs: no 17 Secondary External Status Line Ref Alarm Statu: major 18 Primary Derived Config Active Line Source : pri internal 19 Secondary Derived Config04 Primary Line Reference 20 Primary Derived Status05 Secondary Line Reference 21 Secondary Derived Status Stratum 3 Clock: no Line Ref Alarm Error: pRIlineSECof06 Primary NTM Control07 Secondary NTM Control08 Primary NTM Status09 Secondary NTM Status10 Primary Stratum 3 Config11 Secondary Stratum 3 Config12 Primary Stratum 3 Status13 Secondary Stratum 3 Status


→→→→

PCL OXFORD: Slot 0 Primary Line Reference New Event

A - link0B - link1C - link2D - link3E - link4F - link5G - link6H - link7I - link8J - link9K - link10L - link11M - link12N - link13O - link14P - link15Q - local oscillatorReference Select: B [link1]

→→→→


PCL Configuration/Status Status and Diagnostics

amples ed.

l

.

Status and DiagnosticsThis section runs through the most commonly used status and diagnostics screens, with exof typical failures. This information is the same for both E3 and DS3 sites, except where not

Checking a Configuration ChangeFollowing a configuration change, always use Table 6-2 as a checklist to ensure that the principaDS3 or E3 parameters are set as required for your site. In the table, bold indicates the default setting.

Checking IMA Group StatusFrom the root menu, select M,97,0,E to access the IMA Group Status screen shown below

Table 6-2 Required Settings: PCL with DS3 and DSX1 IMA+

Xedge OS Parameters

Requirements for DS3 Sites Requirements for E3 Sites

LIM Locations DSX1 IMA+ LIM is LIM2 (upper slot)DS3 LIM is LIM1 (lower slot)

E1 IMA+ LIM is LIM2 (upper slot)E3 LIM is LIM1 (lower slot)

LIM Min/Max For any site, set the Minimum number or links to 1 ; set Maximum to 8 .

IMA Type IMA 1.0 or IMA 1.1 (auto selected) IMA 1.0 or IMA 1.1 (auto selected)

IMA Group One group, ID 9 (auto selected) One group, ID 9 (auto selected)

Framing Set to esf or sf. Framing must match at both ends of the link. A mismatch will show LINK DOWN.

Set to crc multiframe or basic.Framing must match at both ends of the link. A mismatch will show LINK DOWN.

Line Code Set to b8zs only.Line code setting must match at both ends of the link. A mismatch shows LINK DOWN.

Set to Enabled or Disabled . Line code setting must match at both ends of the link. A mismatch shows LINK DOWN.

Scr Cell Payload For any site, set to (Scrambled or Not Scrambled ) Scr Cell Payload setting must match at both ends of link. A mismatch shows LINK UP but no communication is available.

Link Cable Numbers

For any site, it is recommended to configure link cables in sequential order for ease of monitoring and simplified troubleshooting.

Cell Delineation Set to HEC or PLCP.Cell Delineation must match at both ends of the link. A mismatch shows LINK DOWN.

Set to HEC or PLCP.Cell Delineation must match at both ends of the link. A mismatch shows LINK DOWN.




LIM

back.

line

Warm Restarts

Perform a warm restart of the slot controller for the following situations:

• to put a new config.cfg file into effect

• to put new controller or LIM software into effect

• to resolve general initialization problems with IMA LIMs

1. From the root menu, type W, N to perform a Warm Start, Normal on slot-0.

2. At the confirmation prompt, type Y (es) to confirm the Normal restart.

3. The node will come up running the current software and configuration. Any general IMA initialization conditions will be resolved.

Diagnostic Loopbacks

DS3/E3 and T1/E1 Loopbacks are performed as described in the procedures below. Figure 6-2 shows the data path for line, local, and diagnostic line loopbacks.

Figure 6-2 Loopback Data Paths

DS3/E3 Loopbacks

For either DS3 or E3 applications, perform the following steps to activate a line or local loop

1. From the root menu, select M,19 to access the DLIMs screen.

• For a DS3 site, select M,19,3,1

• For a E3 site, select M,19,4,1

2. At the DLIM Config/Status screen. select the desired loopback:

• Select B for a Line Loopback

• Select C for a Local Loopback

T1/E1 Loopbacks

For either T1 or E1 applications, perform the following steps to activate a line or diagnostic loopback.

1. From the root menu, select M,70 to access the LIM and Link Information screen.

• For a T1, select M,70,3,0,G [number],E,3

• For a E1, select M,70,2,0,G [number],E,3

2. At the DS1 or T1 Diagnostic page. select the desired loopback:

• Select B for a Line Loopback

• Select E for a Diagnostic Line Loopback

PCLController

LIMCIRCUIT

Line Loop Local LoopDiag Line Loop



ilures.

Diagnosing Link FailuresThis section shows how to quickly navigate the Xedge menus and screens to pinpoint link faThis information is the same for both DS3 and E3 sites, except where noted.

1. From the root menu, use the DS1 or E1 Diagnostic Page to disclose the failure of a link.The example screen shows a DS1 failure at Link 6.

• For a DS3 site, select M,70,3,0,R

• For a E3 site, select M,70,2,0,R

2. The DS1 or E1 Performance Monitoring Page also discloses the failure of a link. The example screen shows a DS1 failure at Link 6.



PCL OXFORD: Slot 0 DS1 Diagnostic Page New eventNo AIS Status Force RDI RDI Status Loopback Mode Loopback Status--------------------------------------------------------------------------------0 off no off none none1 off no off none none2 off no off none none3 off no off none none4 off no off none none5 off no conditioning none none6 off no off none none7 off no off none none8 conditioning no off none none9 conditioning no off none none10 conditioning no off none none11 conditioning no off none none12 conditioning no off none none13 conditioning no off none none14 conditioning no off none none15 conditioning no off none noneSelect option:Down, Enter entry number to edit, Extra detail, Goto row,Index search, Left, eXit

→→→→ →→→→

PCL OXFORD: Slot 0 DS1 Performance Monitoring Page New EventNo ifIndex Link Location Clr Cnts Tx Count Tx Rate Rx Count Rx Rate FERR--------------------------------------------------------------------------------0 4200 lim2/ds1-1 no 12438642 89 7010814 40 21 4201 lim2/ds1-2 no 12439058 91 6978953 66 02 4202 lim2/ds1-3 no 12439059 94 6981103 42 23 4203 lim2/ds1-4 no 12438930 95 6937490 63 24 4204 lim2/ds1-5 no 12438927 95 6959613 47 05 4205 lim2/ds1-6 no 12438846 96 6955158 0 46 4206 lim2/ds1-7 no 12438917 98 7004961 47 17 4207 lim2/ds1-8 no 12425794 99 6991926 67 233838 4208 lim2/ds1-9 no 7011319 43 12437983 97 49 4209 lim2/ds1-10 no 6978961 75 12439065 99 010 4210 lim2/ds1-11 no 6980979 43 12439156 102 211 4211 lim2/ds1-12 no 6937163 70 12438907 102 012 4212 lim2/ds1-13 no 6959104 46 12438903 102 013 4213 lim2/ds1-14 no 6954475 73 12438823 103 014 4214 lim2/ds1-15 no 7004097 46 12438895 104 015 4215 lim2/ds1-16 no 6996059 77 12420320 107 10Select option:Down, Enter entry number to edit, Extra detail, Goto row,Index search, Right, eXit

→→→→ →→→→



k.

3. The DS1 or E1 Alarms Page will display an active alarm for a failed link.The example screen shows an active alarm for an E1 failure at Link 6.



4. The DS1 or E1 Alarms Page Detail screen shows additional information on the failed linThe example screen shows two active LOS alarms for a DS1 failure at Link 6.

• For a DS3 site, select M,70,2,2,G,5,E

• For a E3 site, select M,70,3,2,G,5,E

PCL OXFORD: Slot 0 E1 Alarms Page New eventNo ifIndex Link Location LOS Defect LOS Fault OOF Defect LOF Fault-------------------------------------------------------------------------------0 4200 lim2/e1-1 inactive inactive inactive inactive1 4201 lim2/e1-2 inactive inactive inactive inactive2 4202 lim2/e1-3 inactive inactive inactive inactive3 4203 lim2/e1-4 inactive inactive inactive inactive4 4204 lim2/e1-5 inactive inactive inactive inactive5 4205 lim2/e1-6 active active inactive inactive6 4206 lim2/e1-7 inactive inactive inactive inactive7 4207 lim2/e1-8 inactive inactive inactive inactive8 4208 lim2/e1-9 inactive inactive inactive inactive9 4209 lim2/e1-10 inactive inactive inactive inactive10 4210 lim2/e1-11 inactive inactive inactive inactive11 4211 lim2/e1-12 inactive inactive inactive inactive12 4212 lim2/e1-13 inactive inactive inactive inactive13 4213 lim2/e1-14 inactive inactive inactive inactive14 4214 lim2/e1-15 inactive inactive inactive inactive15 4215 lim2/e1-16 inactive inactive inactive inactiveSelect option:Down, Enter entry number to edit, Extra detail, Goto row,Index search, Left, eXit

→→→→ →→→→

PCL OXFORD: Slot 0 DS1 Alarms Page New eventDetail of DS1 Alarms Page entry 5-------------------------------------------------------------------------------

ifIndex : 4205 Link Location : lim2/ds1-6 LOS Defect : active LOS Fault : active OOF defect : inactive LOF Fault : inactive AIS Defect : inactive AIS Fault : inactive RDI Defect : inactive RDI Fault : inactive LOCD Defect : inactive LOCD Fault : inactive

Select option:Down, Enter entry number to edit, Goto row, Index search, SummaryUp, eXit

→→→→→→→→



5. The DS1 or E1 Link Configuration screen will also disclose the failure of a link.The example screen shows a DS1 failure (port down) at Link 6.



6. The IMA Link Table will also disclose the failure of a DS1 or E1 link.The example screen shows a DS1 failure (NE RX unusable) at Link 6.

• For a DS3 or E3 site, select M,97,1

PCL OXFORD : Slot 0 DS1 Link Configuration Page New eventNo ifIndex Link Location Link Config Link Status Tx Clk Source XOR w/55H-------------------------------------------------------------------------------0 4200 lim2/ds1-1 enabled port up master timing enabled1 4201 lim2/ds1-2 enabled port up master timing enabled2 4202 lim2/ds1-3 enabled port up master timing enabled3 4203 lim2/ds1-4 enabled port up master timing enabled4 4204 lim2/ds1-5 enabled port up master timing enabled5 4205 lim2/ds1-6 enabled port down master timing enabled6 4206 lim2/ds1-7 enabled port up master timing enabled7 4207 lim2/ds1-8 enabled port up master timing enabled8 4208 lim2/ds1-9 disabled disabled master timing enabled9 4209 lim2/ds1-10 disabled disabled master timing enabled10 4210 lim2/ds1-11 disabled disabled master timing enabled11 4211 lim2/ds1-12 disabled disabled master timing enabled12 4212 lim2/ds1-13 disabled disabled master timing enabled13 4213 lim2/ds1-14 disabled disabled master timing enabled14 4214 lim2/ds1-15 disabled disabled master timing enabled15 4215 lim2/ds1-16 disabled disabled master timing enabledSelect option:Down, Enter entry number to edit, Extra detail, Goto row,Index search, Right, eXit

→→→→

PCL OXFORD : Slot 0 IMA Link Table New eventNo Link Index Row Status Group Index NE Tx State NE Rx State FE Tx State-------------------------------------------------------------------------------0 4200 active 9 active active active 1 4201 active 9 active active active 2 4202 active 9 active active active 3 4203 active 9 active active active 4 4204 active 9 active active active 5 4205 active 9 usable unusableFai usable 6 4206 active 9 active active active 7 4207 active 9 active active active 8 4208 notInServi 0 notInGroup notInGroup notInGroup9 4209 notInServi 0 notInGroup notInGroup notInGroup10 4210 notInServi 0 notInGroup notInGroup notInGroup11 4211 notInServi 0 notInGroup notInGroup notInGroup12 4212 notInServi 0 notInGroup notInGroup notInGroup13 4213 notInServi 0 notInGroup notInGroup notInGroup14 4214 notInServi 0 notInGroup notInGroup notInGroup15 4215 notInServi 0 notInGroup notInGroup notInGroupSelect option:Down, Enter entry number to edit, Extra detail, Goto row,Index search, Right, eXit

→→→→



closes

7. The IMA Link Table Detail screen shows additional information on the failed link.The example screen shows four failures for a DS1 failure at Link 6.

• For a DS3 or E3 site, select M,97,1,G,5,E

8. The DS1 or E1 Configuration/Status screen shows details on a DS3 or E3 LOS also disThe example screen shows an E3 Status LOS Defect and LOS Alarm.

• For a DS3 site, select M,39,1,E

• For a E3 site, select M,39,2,E

9. The DS3-2C or E3-2C LIM Config/Status screen shows DS3 or E3 Physical Layer LOS.The example screen below shows an E3 LOS Defect and LOS Alarm.

• For a DS3 site, select M,19,4,E

• For a E3 site, select M,19,3,E

PCL OXFORD: Slot 0 IMA Link Table New EventDetail of IMA Link Table entry 5------------------------------------------------------------------------------- Link Index : 4205 FE Unavail Secs: 12270 Row Status : active NE Tx Unusbl Se: 11 Group Index : 9 NE Rx Unusbl Se: 2 NE Tx State : usable FE Tx Unusbl Se: 2 NE Rx State : unusableFailed FE Rx Unusbl Se: 1226 FE Tx State : usable NE Tx Failures : 0 FE Rx State : unusableFailed NE Rx Failures : 0 NE Rx Fail Stat: imaLinkFailure Rx Test Pattern: 0 FE Rx Fail Stat: imaLinkFailure Test Proc Statu: disabled Tx LID : 5 Rx LID : 5 Relative Delay : 0 IMA Violations : 0 NE Sev Err Secs: 1 FE Sev Err Secs: 1 NE Unavail Secs: 1227Select option:Down, Enter entry number to edit, Goto row, Index search, Summary,Up, eXit

→→→→→→→→→→→→→→→→→→→→

PCL OXFORD: Slot 0 E3 Configuration/Status New EventDetail of E3 Configuration/Status entry 0------------------------------------------------------------------------------- Link # : 0 LOS Defect: yes Rx Trail T: 0000000000 Table Vali: yes OOF Defect: no Rx Trail T: no0 Framer Mod: g832 AIS Defect: no Rx Trail T: no1 Clear Coun: no FERF Defec: no Rx Pyld La: yes2 Reconfigur: no BER Defect: no Rx Pyld La: no3 Traceable : no LOS Alarm : yes4 Pyld Label: atm LOF Alarm : no5 Tx Trl Trc: length 16 AIS Alarm : no6 Tx Trl Trc: 2020202020 FERF Alarm: no7 Tx Trl Trc: 2020202020 BER Alarm : no8 Rx Exo Tr : 2020202020 Line ES : 09 Rx Exp Tr : 2020202020 Line SES : 0 Framing Er: 0 AISS : 0 Lcvs : 0 UAS : 32 Parity Err: 0 FEBE Errs : 0Select option:Down, Enter entry number to edit, Goto row, Index search, Summary,eXit

→→→→

→→→→→→→→

PCL OXFORD: Slot 0 E3-2C DLIM Config/Status New EventDetail of E3-2C DLIM Config/Status entry 0------------------------------------------------------------------------------- Link No : 0 Version : e3 2c LIM OK : yes 0 Rx Eq Select : auto 1 Loopback LIU : none 2 Tx AIS : no 3 Timing Reference : system LOS Defect : yes LOS Alarm : yes4 Reconfigure : no

Select option:Down, Enter entry number to edit, Goto row, Index search, Summary,eXit

→→→→→→→→



10. The PLCP Configuration/Status screen shows E3 or DS3 Link Down.The example screen below shows a DS3 Link Down condition.

• For a DS3 or E3 site, select M,39,0,E

PCL OXFORD: Slot 0 PLCP Configuration/Status New EventDetail of PLCP Configuration/Status entry 0------------------------------------------------------------------------------- Link # : 0 RX Clock : up FE-ES : 000 Link Enabl: enabled Txed Cells: 2409491 FE-SES : 001 Link Statu: ignored Rxed Cells: 2476324 FE-UAS : 0 Link State: down HCS Errors: 002 Phy Framer: ds3 LOCD Defec: no03 Cell Delin: ds3 PLCP Yellow Def: no04 Scrambler : enabled LOF Defect: no05 XOR w/55H : enabled LOCD Alarm: no06 SMDS Mode : disabled Yellow Ala: no07 Idle Cell : unassigned LOF Alarm : no08 Loopback : none Frame Errs: 009 Clear Coun: no BIP8 Errs : 010 Reconfigur: no FEBE Errs : 011 Lpbk Timeo: 1 ES : 314 Chip Type : suni qjet SES : 314 TX Clock : up UAS : 0Select option:Down, Enter entry number to edit, Goto row, Index search, Summary,eXit

→→→→



nt cells r both

n

.

and

ll

IM.

Diagnosing Cell Layer Traffic

This section shows how to set up a PVC and evaluate the cell counts captured for managemetraversing the switch fabric, or data cells received at the LIMs. This information is the same foDS3 and E3 sites.

1. From the root menu, select D,P,C to access the PCL Debug Configuration screen, showbelow.

2. Enter the VPI and VCI values to configure a filter for the desired PVC counts. This will specify which ATM cells will be captured.

3. If desired, enter values for CLP, PTI, or GFC to capture cell counts for those parameters

4. Type X to return to the PCL Debug screen, shown below.

• The FPGA SPI value at the top of the screen displays the total cell count.

• The Conf’g value shows the total cell count for the configured parameters.

• The From/To values show the cell counts of low and high priority management cells tofrom the Switch Fabric.

• The Buffer values show buffer usage at the IMA egress (current and maximum).

• The ATM Header received from links values show the header of the last ATM cereceived, sampled every two seconds.

• The Rcv’d column is a continuous capture of any cell received.

• The Cfg’d column shows the count for data coming through the SPI bus via the L

PCL OXFORD: Slot 0 PCL Debug New Event

-------------------------------------------------------------------------------

Enter GFC value:[0-15]: 0Enter VPI value:[0-255]: 1Enter VCI value:[0-65535]: 32Enter PTI value:[0-7]: 0Enter CLP value:[0-11]: 0

Select option:Cfg’d count, Reset, eXit

→→→→→→→→

PCL OXFORD: Slot 0 PCL Debug New Event

-------------------------------------------------------------------------------FPGA SPI :08775 Cfg’d :19388From Hi SF :059 Lo SF :000To Hi SF :160 Lo SF :000

Buffer Max:6656 Curr:6642

ATM Header received from links Rcv’d Cfg’dGFC : 0 0VPI : 1 1VCI : 99 99PTI : 0 0CLP : 1 0

Working...Cfg’d count, Reset, eXit

→→→→

→→→→→→→→


Note ted.

r

the

. re

hange.

tch.

ing d

ens.

Chapter 7: LIM Configuration

IntroductionThis chapter describes the configuration of LIMs associated with the PCx or PCL controller.that the same configuration screens are used to configure any type of LIM, except where no

• For a list of all LIMs currently supported by the PCx or PCL, as well as future LIMs undedevelopment, refer to the Xedge Hardware Installation Guide.

• For information on setting hard options and installing LIMs in an Xedge chassis, refer toXedge Hardware Installation Guide.

• All LIMs described in this section are supported by both the PCX and the PCL, with the exception of the IMA LIMS. The PCX uses the “IMA” LIM. The PCL uses the “IMA+” LIMsAll IMA information in this section refers to both the IMA and the IMA+ LIMs, except whenoted.

Note Some Xedge LIMs are not fully implemented at this time. The information in this chapter is subject to cContact your Xedge representative for details on availability.

LIM Basics

This chapter describes the following basic LIM procedures performed for all LIMs in the swi

• LIM Identification and Status

• LIM Firmware/Software Update

• LIM Timing

Configuring Links

Links associated with a slot controller are configured in a similar manner using a correspondMIB, as indicated by the simplified outline below. Refer to the appropriate section for detaileconfiguration procedures for each link type.

• For LIM Firmware/Software Update OC-3 LIMs (155-series) and the OC-N/STM-N LIM all comprise SONET/SDH links. From the root menu, select M,70,1 for their Configuration, Diagnostics, Performance Monitoring, Alarms, Automatic Protection Switching (APS), and Defects menus and scre

• For DLIMs DS1-2C, E1-2C, DS3-2C and E3-2C all comprise DLIM links.From the root menu, select M,19 for their Configuration and Status screens.

• For IMA LIMs DSX1 IMA, E1 IMA, DSX1 IMA+ and E1 IMA+ LIMs all comprise IMA links. From the root menu, select M,97 for link/group Configuration and Status screens.

• For SFP Tranceivers (Xedge PCx Controller Only)From the root menu, select M,70,4 for a read-only display of transceiver parametersfor each link.


LIM Configuration Introduction

LIM Identification and Status

1. From the root menu, select M,70,0 to view the LIM ID, Version and Status screen.

2. Select the desired LIM (0, 1 , 2 or 3)

3. Select E (Extra Detail) to display the LIM type, hardware version, software version and status of the selected LIM. The example screens in Figure 7-1 show information on LIM 1 of the slot-0 controller.

Figure 7-1 LIM ID, Version and Status Screens

4. At the Extra Detail screen for LIM 0, select Down to display detail information for the next installed LIM, in sequence.


MAINSCREEN

EXTRADETAILS

OXFORD: Slot 0 LIM ID, Version, Status New EventNo LIM Location LIM ID Hardware Version Boot Version Firmware Version-------------------------------------------------------------------------------0 lim 1 sonet sd 1 B- oc3_3.71 lim 2 sonet oc 0 A- oc12_1.02 mez 1 front me 3 f lim westbay

Select option:Enter entry number to edit, Extra detail, Goto row, Index search,Right, eXit

OXFORD: Slot 0 LIM ID, Version, Status New EventDetail of LIM ID, Version, Status entry 0------------------------------------------------------------------------------- LIM Location : lim 1 LIM ID : sonet sdh oc3 dual short reach Hardware Version : 1 Boot Version : B- Firmware Version : oc3_3.7 Software Version : oc3_620 Number of Ports : 2 LIM Status : operational LIM ID on Slot-0 : 28




at

LIM Firmware/Software Update

1. At the root menu, select M,70,0,2 for the LIM Firmware/Software Update screen. Figure 7-2 shows an example display and Extra Detail screen with LIM 1 selected for updating.

2. Select the desired LIM (0, 1 or 2 ). In the example, LIM 1 is selected.

3. Select Extra Detail to display the download / upgrade information and options for thLIM.

4. Select an entry number to edit the download / upgrade parameters for that LIM.

Figure 7-2 LIM Firmware/Software Update Screens

MAINSCREEN

EXTRADETAILS

OXFORD: Slot 0 LIM firmware/Software Update New EventNo LIM Location Start Download Progress (2%) Download Status Auto Upgrade-------------------------------------------------------------------------------0 lim 1 no 0 idle off1 lim 2 no 0 idle off2 f lim not applicable 0 not applicable off


OXFORD: Slot 0 LIM ID, Version, Status New EventDetail of LIM ID, Version, Status entry 0------------------------------------------------------------------------------- LIM Location : lim 10 Start Download : no Progress (2%) : 0 Download Status : idle1 Auto Upgrade : off2 Restart LIM : no




TX

select

r for

the ipped.)

LIM Timing1. At the root menu, select M,70,0,1 to access the LIM Timing screen. Figure 7-3 shows an

example display and Extra Detail screen with LIM 2 using a system clock as the Master Timing source.

2. To edit LIM timing, select the desired LIM (0, 1 or 2 ) at the LIM Timing screen. A list of Master Tx timing sources is displayed.

3. Select a letter (A - Q ) to assign a timing source for the node.

Figure 7-3 LIM Timing Screens

4. If one of the LIMs is to serve as the Primary or Secondary source of timing for the node, the desired LIM as described above, then select Extra Detail to display that LIM’s timing information. Select Option 1 (Allow Sys Timing) and set it to enable .

5. Refer to the complete description of the specific LIM’s configuration screen in this chapteadditional timing options.

Note The PCx and the PCL controllers do not provide HQ/LQ Pri/Sec Bus status information.

Note IMPORTANT! In addition to timing configuration for each LIM, you must configure System Timing fornode (including Node Timing Module configuration, if your Xedge 6628, 6640 or 6645 node is so equRefer to Chapter 3 in this manual, under the paragraphs on System Timing Overview for detailed procedures.

MAINSCREEN

EXTRADETAILS

EDITTIMINGSOURCE

Xedge Switch: Slot 0 LIM Timing 710ER6\700No LIM Location Sys Tmg Driver Source Used Sys Tmg Bus Being Driven-------------------------------------------------------------------------------0 lim 1 local oscillator none1 lim 2 local oscillator none

Select option:Enter entry number to edit, Extra detail, Right, eXit

Xedge Switch: Slot 0 LIM Timing 710ER6\700Detail of LIM Timing entry 0-------------------------------------------------------------------------------- LIM Location : lim 1 Sys Tmg Driver Source Used : local oscillator Sys Tmg Bus Being Driven : none0 Master Tx Tmg Source : system clock Master Tx Tmg Source Used : local oscillator HQ Pri Bus Status : not available HQ Sec Bus Status : not available LQ Pri Bus Status : invalid LQ Sec Bus Status : invalid1 Allow Sys Tmg : disabled

Select option:Enter entry number to edit, Summary, eXit Select option:Down, Enter entry number to edit, Goto row, Index search, Summary,Up, eXit

Xedge Switch: Slot 0 LIM Timing New Event

A - system clock R - local oscillatorB - link0C - link1D - link2E - link3F - link4G - link5H - link6I - link7J - link8K - link9L - link10M - link11N - link12O - link13P - link14Q - link15Master Tx Tmg Source: A [system clock] Up, eXit


LIM Configuration SONET/SDH Configuration

SONET/SDH Configuration1. At the root menu, select M,70,1 to access the SONET/SDH Link Configuration screen.

Figure 7-4 shows an example display and an Extra Detail screen of Entry 0 .

2. Select an entry number to edit that link as necessary.

Figure 7-4 SONET/SDH Link Configuration Screens

MAINSCREEN

EXTRADETAILS

OXFORD: Slot 0 SONET/SDH Link Configuration New EventNo ifIndex Link Location AdminState OperState Tx Clk Source Tx Tx Clk Src Used-------------------------------------------------------------------------------0 4100 lim1/link-0 enabled port down master timing master timing1 4101 lim1/link-1 enabled port down master timing master timing2 4200 lim2/link-0 enabled port up master timing master timing3 4201 lim2/link-1 enabled port up master timing master timing4 4400 flim/link-0 disenabled disabled master timing master timing5 4401 flim/link-1 disenabled disabled master timing master timing6 4402 flim/link-2 disenabled disabled master timing master timing7 4403 flim/link-3 disenabled disabled master timing master timing


OXFORD: Slot 0 SONET/SDH Link Configuration New EventDetail of SONET/SDH Link Configuration entry 0------------------------------------------------------------------------------- ifIndex : 4100 Link Location : lim1/link-0 0 AdminState : enabled OperState : port down 1 Tx Clk Source : master timing Tx Clk Src Used : master timing2 Scr Cell Payld : scrambled 3 XOR 55 w/55H : enable4 Cell Rate Dcpl : unassigned cells5 Overhead Type : sonet6 Link Type : oc3 APS Group : noSelect option:Down, Enter entry number to edit, Goto row, Index search, Summary,eXit



SONET/SDH Diagnostics

1. At the root menu, select M,70,1,0 to access the SONET/SDH Link Diagnostics screen.Figure 7-5 shows an example display and an Extra Detail screen of Entry 0 (lim1/link0).

2. Select an entry number to edit that link. Refer to Table 7-1 as needed.

Figure 7-5 SONET/SDH Diagnostics Screens

Table 7-1 SONET/SDH Diagnostics Screen Definitions

If Index If Index of the physical port on the LIM (Read only)

Link Location Read-only display of the LIM and the link location.

00 Diag Timeout Sets the amount of time allowed after any diagnostic is enabled until all the loopback or forced error generation are turned off. (Immediate effect) Enter a value from 1 to 64000 minutes.

Time Remaining Time remaining before the LIM turns off all diagnostics for this link. This parameter is reset to the Timeout value whenever the user turns on a loopback, turns on any error generation or changes the timeout value. Read-only display: 0 to 64000 minutes.

01 Force Bit Error Forces framing bit errors on the transmitter side of the link. When this option is on, a single bit error is continuously inserted in the most significant bit of the A1 Section overhead byte. (Immediate effect)Type y to generate framing errors; Type n to turn off LOF generation.

Bit Error Stat Read-only dispay of the current bit error status, indicating that Framing Errors are being inserted at the transmitter end:On - Force Bit Errors currently runningOff - Force Bit Errors currently not runningInhibited - Force LOF is enabled but inhibited due to the loopback, Conditioning (Not used)Forced (Not used)

MAINSCREEN

EXTRADETAILS

OXFORD: Slot 0 SONET/SDH Diagnostics New EventNo ifIndex Link Location Diag Timeout Timine Remaining Force Bit Error-------------------------------------------------------------------------------0 4100 lim1/link-0 5 5 no1 4101 lim1/link-1 5 5 no2 4200 lim2/link-0 5 5 no3 4201 lim2/link-1 5 5 no4 4400 flim/link-0 5 5 no5 4401 flim/link-1 5 5 no6 4402 flim/link-2 5 5 no7 4403 flim/link-3 5 5 no


OXFORD: Slot 0 SONET/SDH Diagnostics New EventDetail of SONET/SDH Diagnostics entry 0------------------------------------------------------------------------------- ifIndex : 4100 07 Force RDI-P : no Link Location : lim1/link-0 RDI-P Status : conditioning00 Diag Timeout : 5 08 Force CV-P : no Time Remaining : 5 CV-P Status : off01 Force Bit Error: no 09 Loopback Mode : none Bit Error Stat : off Loopback Status : none02 Force CV-S : no 10 Insert HCS Err : no CV-S State : off HCS State : off03 Force AIS-L : no AIS-L Status : off04 Force RDI-L : no RDI-L Status : conditioning05 Force CV-L : no CV-L Status : off06 Force AIS-P : no AIS-P Status : offSelect option:Down, Enter entry number to edit, Goto row, Index search, Summary,eXit



02 Force CV-S Forces Section Coding Violations (CV-S) on the transmitter end of the LIM. When this option is on, the section BIP-8 byte (B1) is continuously inverted. (Immediate effect)Type y to force CV-S errors; Type n to turn off CV-S errors.

CV-S Status Read-only display of the current status of Section Coding Violations (CV-S) indicating if CV-S are being inserted on the link:On - CV-S generation currently runningOff - CV-S generation currently not runningInhibited - CV-S generation is enabled but inhibited due to the loopback or Bit Error generation.Conditioning (Not used)Forced (Not used)

03 Force AIS-L Forces AIS-L to be transmitted out the link.(Immediate effect)Type y to generate an AIS-L; Type n to turn off AIS-L generation.

AIS-L Status Read-only display of the current status of Line Alarm Indication Signal (AIS-L) indicating if AIS-L is being inserted at the transmitter end of the link:On - Force AIS-L currently runningOff - Force AIS-L currently not runningInhibited - Force AIS-L is enabled but inhibited due to loopback or Bit Error generation.Conditioning (Not used)Forced (Not used)

04 Force RDI-L Forces Line Remote Defect Indication (RDI-L) on the link. (Immediate Effect)Type y to generate an RDI-L; Type n to turn off RDI-L generation.

RDI-L Status Read-only display of the current status of Line Remote Defect Indication (RDI-L) indicating if RDI-L is being inserted on the link:On - Force RDI-L currently runningOff - Force RDI-L currently not runningInhibited - Force RDI-Lis enabled but inhibited due to the loopback or Bit Error generation.Conditioning - indicates a LOS, LOF or AIS-L failure on the receive lineForced (Not used)

05 Force CV-L This parameter can force Line Coding Violations (CV-L) on the link. When this option is on, the line BIP byte(s) B2 are continuously inverted. (Immediate effect)Type y to force CV-L errors; Type n to turn off CV-L errors.

CV-L Status Read-only display of the current status of Section Coding Violations (CV-L) indicating if CV-L are being inserted on the link:On - CV-L generation currently runningOff - CV-L generation currently not runningInhibited - CV-L generation is enabled but inhibited due to the loopback or Bit Error generation.Conditioning (Not used)Forced (Not used)

06 Force AIS-p Forces AIS-P to be transmitted out of the link. (Immediate effect)Type y to generate an AIS-P; Type n to turn off AIS-P generation.

AIS-P Status Read-only display of the current status of Path Alarm Indication Signal (AIS-P) indicating if AIS-P is being inserted on the link:On - Force AIS-P currently runningOff - Force AIS-P currently not runningInhibited - Force AIS-P is enabled but inhibited due to the loopback or Bit Error generation.Conditioning (Not used)Forced (Not used)

07 Force RDI-P Forces Path Remote Defect Indication (RDI-P) on the link. (Immediate effect)Type y to generate an RDI-P; Type n to turn off RDI-P generation.



RDI-P Status Read-only display of the current status of Path Remote Defect Indication (RDI-P) indicating if RDI-P is being inserted on the link:On - Force RDI-P currently runningOff - Force RDI-P currently not runningInhibited - Force RDI-P is enabled but inhibited due to the loopback or Bit Error generation.Conditioning - indicates a LOS, LOF, LOP-P, AIS-P, UNEQ-P, PLM-P, or AIS-L failure on the receive lineForced (Not used)

08 Force CV-p Forces Path Coding Violations (CV-P) on the transmitter end of the LIM. When this option is on, the path BIP byte (B3) is continuously inverted. (Immediate effect)Type y to force CV-P errors; Type n to turn off CV-P errors.

CV-P Status Read-only status of Section Coding Violations, indicating if CV-P are being inserted on the link:On - CV-P generation currently runningOff - CV-P generation currently not runningInhibited - CV-P generation is enabled but inhibited due to the loopback or Bit Error generation.Conditioning (Not used)Forced (Not used)

09 Loopback Mode Sets the link into a specified loopback mode. (Immediate effect)Note that with line or digital loopback enabled on a link, the link status display will change accordingly as described in Loopback Status. The options are:None - loopback disabledLine Loopback - loopback any data received on the link's data port back out the transmit data port on the same link.Digital Loopback - data sent to the LIM from the Controller will be looped back to the controller.

Loopback Status Read-only display of the current loopback mode on the LIM:NoneLine LoopbackDigital Loopback

10 Insert HCS Error Inserts Header Check Sequence (HCS) errors on the transmitter end of the LIM. When this option is on, the HCS octet is inverted prior to insertion in the SPE. HCS errors generated are continuous un-correctable errors. (Immediate effect)Type y to generate HCS errors; Type n to turn off HCS error generation.

HCS Status Read-only display of the current status of Header Check Sequence (HCS) Errors, indicating if HCS Errors are being inserted on the link:On - HCS error generation currently runningOff - HCS error generation currently not runningInhibited - HCS error generation is enabled but inhibited due to loopback or Bit Error generation.Conditioning (Not used)Forced (Not used)



g

SONET/SDH Performance Monitoring

1. At the root menu, select M, 70, 1,1 to access the SONET/SDH Performance Monitorinscreen. Figure 7-6 shows an example display and an Extra Detail screen of Entry 0 (lim1/link0).


Figure 7-6 SONET/SDH Performance Monitoring

Table 7-2 SONET/SDH Performance Screen Definitions

If index If Index of the physical port on the LIM

Link Location Read-only description of the LIM and the Link Location

0 Clear Count Resets to zero all counters on the SONET/SDH Performance Monitoring Page. (Immediate effect) Type y to clear all counters; Type n to retain counter values as is.

TX Cell Count Read-only count of the number of cells transmitted, updated every second. Does not including idle or unassigned cells. Possible values are: 0 to 4,294,967,295 then restarts at 0 .

TX Cell Rate Read-only count of cells transmitted per second, not including idle or unassigned cells. Updated every second.Possible values are: 0 to 4,294,967,295 then restarts at 0 .

RX Cell Count Read-only count of cells received, updated every second. Does not including idle or unassigned cells. Possible values are: 0 to 4,294,967,295 then restarts at 0 .

RX Cell Rate Read-only count of cells received per second, not including idle or unassigned cells. Updated every second.Possible values are: 0 to 4,294,967,295 then restarts at 0 .

CV-S Read-only count of Section Coding Violations (SONET frame CV-S Errors) detected at the section layer of the ingress signal. Updated every second.Possible values are: 0 to 4,294,967,295 then restarts at 0 .

MAINSCREEN

EXTRADETAILS

OXFORD: Slot 0 SONET/SDH Performance Monitoring New EventNo ifIndex Link Location Clear Counts Tx Cell Count Tx Cell Rate Rx Cell Count-------------------------------------------------------------------------------0 4100 lim1/link-0 no 408 0 01 4101 lim1/link-1 no 0 0 02 4200 lim2/link-0 no 0 0 03 4201 lim2/link-1 no 0 0 04 4400 flim/link-0 no 0 0 05 4401 flim/link-1 no 0 0 06 4402 flim/link-2 no 0 0 07 4403 flim/link-3 no 0 0 0


OXFORD: Slot 0 SONET/SDH Performance Monitoring New EventDetail of SONET/SDH Performance Monitoring entry 0------------------------------------------------------------------------------- ifIndex : 4100 1 Cnt LFE Er: not active UAS-PFE : 0 Link Locat: lim1/link- CV-LFE : 0 HCS Corr. : 00 Clear Coun: no ES-LFE : 0 HCS Uncorr : 0 Tx Cell Co: 0 SES-LFE : 0 Tx Cell Ra: 0 FC-LFE : 0 Rx Cell Co: 0 UAS-LFE : 0 Rx Cell Ra: 0 CV-P : 0 CV-S : 0 ES-P : 0 SEFS-S : 0 SES-P : 0 ES-S : 0 FC-P : 0 SES-S : 0 UAS-P : 0 CV-L : 0 2 Cnt PFE Er: not active ES-L : 0 CV-PFE : 0 SES-L : 0 ES-PFE : 0 FC-L : 1 SES-PFE : 0 UAS-L : 2024 FC-PFE : 0Select option:Down, Enter entry number to edit, Goto row, Index search, Summary,eXit



SEFS-s Read-only count of Section Severely Errored Framing seconds on this Link, updated every second. Possible values: 0 to 4,294,967,295 then restarts at 0 .

ES-s Read-only count of number of seconds where at least one Section Coding Violations (CV-S) or Loss of Signal (LOS) defect was detected. Updated every second. Possible values are: 0 to 4,294,967,295 then restarts at 0 .

SES-s Read-only count of seconds where at least 2,500 Section Severly Errored Seconds coding violations, or as least one LOS, was detected. Updated every second. Possible values: 0 to 4,294,967,295 then restarts at 0 .

CV-L Read-only count of Line Coding Violations (BIP-24 errors) detected at the line layer of the ingress signal. Updated every second.Possible values are: 0 to 4,294,967,295 then restarts at 0 .

ES-L Read only count of Line Errored seconds, where at least one Near-End Line Coding Violations (CV-L) or at least one Line Alarm Indication Signal (AIS-L) is detected. Updated every second. Possible values: 0 to 4,294,967,295 then restarts at 0 .

SES-L Read-only count of Severely Errored seconds, where at least 2500 Line Coding Violations (CV-L) or at least one Line Alarm Indication Signal (AIS-L) is detected.Updated every second. Possible values are: 0 to 4,294,967,295 then restarts at 0 .

FC-L Read-only count of Line Failure events, when an AIS-L is received or cleared. Updated every second. Possible values are: 0 to 4,294,967,295 then restarts at 0 .

UAS-L Read-only count of Line Unavailable seconds when the line is unavailable after 10 consecutive Line Severely Errored Seconds (included in the unavailable time). The line becomes available after 10 consecutive seconds with no SES-L's (not included in the unavailable time). Updated every second.Possible values are: 0 to 4,294,967,295 then restarts at 0 .

1 Cnt LFE Err Specifies whether the far-end (next LTE in the OC-3/STM-1 network) performance monitoring should be collected (Far-End Line Errors). (Immediate effect)Type y to turn on far end line error collection.Type n to turn off far end line error violation collection.

CV-LFE Read-only count of BIP-24 Errors (Far-End Line Coding Violations) detected at the line layer of the ingress signal at the far end. This parameter does not function if the Count Far-End Line Errors (Cnt LFE Er) is set to no . Updated every second.Possible values are: 0 to 4,294,967,295 then restarts at 0 .

ES-LFE Read-only count of Far-End Line Errored seconds where at least one Far-End Line Coding Violations (CV-LFE) or at least one Line Alarm Indication Signal (AIS-LFE) is detected. This parameter does not function if the Count Far-End Line Errors (Cnt LFE Er) is set to no . Updated every second.Possible values are: 0 to 4,294,967,295 then restarts at 0 .

SES-LFE Read-only count of Far-End Line Severely Errored seconds where at least 2500 Far-End Line Coding Violations (CV-LFE) or at least one Line Alarm Indication Signal (AIS-LFE) is detected. This parameter does not function if the Count Far-End Line Errors (Cnt LFE Er) is set to no . Updated every second. Possible values are: 0 to 4,294,967,295 then restarts at 0 .

FC-LFE Read-only count of Far-End Line Failure events. A failure event is when RDI-L is received from the far-end LTE and ends when the RDI-L is cleared. This parameter does not function if the Count Far-End Line Errors (Cnt LFE Er) is set to no . Updated every second. Possible values are: 0 to 4,294,967,295 then restarts at 0 .

UAS-LFE Read-only count of Far-End Line Unavailable seconds where the line is unavailable. A line is declared unavailable after 10 consecutive Far-End Line Severely Errored Seconds (SESLFE), which are included in the unavailable time. The line becomes available after 10 consecutive seconds with no SES-LFE's, which are not included in the unavailable time. This parameter does not function if the Count Far-End Line Errors (Cnt LFE Er) is set to no . Updated every second.Possible values are: 0 to 4,294,967,295 then restarts at 0.

CV-P Read-only count of Path Coding Violations. This parameter displays the count of BIP-8 errors detected at the path layer (CV-P) of the ingress signal. Updated every second.Possible values are: 0 to 4,294,967,295 then restarts at 0 .



ES-P Read-only count of Path Errored seconds where at least one CV-P occurred, Alarm Indication Signal (AIS-P), or Synchronous Transport Signal Loss of Pointer (LOP-P) is detected. Updated every second. Possible values are: 0 to 4,294,967,295 then restarts at 0 .

SES-P Read-only count of Path Severely Errored seconds where at lest 2400 Near- End Path Coding Violations (CV-P) or at least one Alarm Indication Signal (AIS-P), or Synchronous Transport Signal Loss of Pointer (LOP-P) is detected. Updated every second.Possible values are: 0 to 4,294,967,295 then restarts at 0 .

FC-P Read-only count of Path Failure events. A failure occurs when either Alarm Indication Signal (AIS-P), or Synchronous Transport Signal Loss of Pointer (LOP-P) are declared and ends when Alarm Indication Signal (AIS-P), or Synchronous Transport Signal Loss of Pointer (LOP-P) are cleared. Updated every second.Possible values are: 0 to 4,294,967,295 then restarts at 0 .

UAS-P Read-only count of Path Unavailable seconds. A path is declared unavailable after 10 consecutive path Severely Errored Seconds (SES-P), which are included in the unavailable time. The line becomes available after 10 consecutive seconds with no SES-P's, which are not included in the unavailable time. Updated every second.Possible values are: 0 to 4,294,967,295 then restarts at 0 .

2 Cnt PFE Err Specifies whether the Path Far End Error Information should be collected or not. (Immediate effect):Not-active - indicates that the error counts will not be collected.Active - indicates that the error counts will be collected.

CV-PFE Read-only count of Path Far End Coding Violationsreceived by this link. A Path Far End Coding Violation is a BIP-8 error detected at the path layer of the ingress signal at the far end. This parameter does not function if the Count Far-End Path Errors (Cnt PFE Er) is set to no . Updated every second.Possible values are: 0 to 4,294,967,295 then restarts at 0 .

ES-PFE Read-only count of Path Far End Errored seconds where at least one Far End Path Coding Violation (CV-PFE) or at least one Far End Path Alarm Indication Signal (AIS-PFE) is detected. This parameter does not function if the Count Far-End Path Errors (Cnt PFE Er) is set to no . Updated every second.Possible values are: 0 to 4,294,967,295 then restarts at 0 .

SES-PFE Read-only count of Path Far End Severely Errored seconds received on this link. This counts the number of seconds where at least 2,500 Far End Path Section Coding Violations (CV-PFE) or at least 1 Near End Line Alarm Indication Signal (AIS-PFE) defect was detected. This parameter does not function if the Count Far-End Path Errors (Cnt PFE Er) is set to no . Updated every second. Possible values are: 0 to 4,294,967,295 then restarts at 0 .

FC-PFE Read-only Far End Path Failure count where a Far End Path Alarm Indication Signal (AIS-PFE) is declared, and ends when AIS-PFE is cleared. Updated every second.Possible values are: 0 to 4,294,967,295 then restarts at 0 .

UAS-PFE Read-only count of Far End Path Unavailable Seconds for this link. A line is declared unavailable after 10 consecutive Far End Path Severely Errored Seconds (SES-PFE), which are included in the unavailable time. The time becomes available again after 10 consecutive seconds with no SESPFE which are not included in the unavailable time. Updated every second.Possible values are: 0 to 4,294,967,295 then restarts at 0 .

HCS Corr Correctable HCS Errors. Read-only count of ATM cells with correctable Header Check Sequence (HCS) Errors. Updated every second.Possible values are: 0 to 4,294,967,295 then restarts at 0 .

HCS Uncorr Uncorrectable HCS Errors. Read-only count of ATM cells where an Header Check Sequence Error (HCS) cannot be corrected. Updated every second.Possible values are: 0 to 4,294,967,295 then restarts at 0 .



SONET/SDH Alarms

1. At the root menu, select M,70,1,2 to access the SONET/SDH Alarms screen.Figure 7-7 shows an example display and an Extra Detail screen of Entry 0 (lim1/link0).


Figure 7-7 SONET / SDH Alarm Screens

Table 7-3 SONET/SDH Alarm Definitions

If index If Index of the physical port on the Lim

Link Location Defines the Lim and the Link Location (Read only)

LOS Defect Displays of Loss of Signal Defect when all zeros are received for 20 +/- 3 microseconds or longer. Cleared when two valid framing words are detected. No defects/failures can inhibit LOS defect. Read-only values are: active or inactive

LOS Fault Display of Loss of Signal Failure when Loss of Signal Defect is detected for at least 2.5 +/- 0.5 seconds. Cleared when Loss of Signal Defect is absent for 10 +/- 0.5 seconds. No defects/failures can inhibit LOS failure. Read-only values are: active or inactive

LOF Defect Displays Loss of Frame Defect when a out-of-frame conditions persists for a period of 3 milliseconds and is not inhibited. Cleared when an in-frame condition persists for 3 milliseconds or a defect inhibitor becomes active Inhibited by: Loss of Signal (LOS) Read-only values are: active or inactive

LOF Fault Displays LOF Defect is detected for at least 2.5 +/- 0.5 seconds and is not inhibited. Cleared when Loss of Frame Defect is absent or inhibited for 10 +/- 0.5 seconds. Inhibited by: Loss of Signal (LOS) Read-only values are: active or inactive

EBER-P Thresh Excessive Bit Error Rate Defect threshold specifies the allowable path error rate, as determined by monitoring the B3 byte in the path overhead section of the SONET frame header. Possible values are: 1x10-3 or 1x10-4 or 1x10-5

MAINSCREEN

EXTRADETAILS

OXFORD: Slot 0 SONET/SDH Alarms New EventNo ifIndex Link Location LOS Defect LOS Fault LOF Defect LOF Fault-------------------------------------------------------------------------------0 4100 lim1/link-0 inactive inactive inactive inactive1 4101 lim1/link-1 active active inactive inactive2 4200 lim2/link-0 inactive inactive inactive inactive3 4201 lim2/link-1 inactive inactive inactive inactive4 4400 flim/link-0 not suppor inactive not suppor inactive5 4401 flim/link-1 not suppor inactive not suppor inactive6 4402 flim/link-2 not suppor inactive not suppor inactive7 4403 flim/link-3 not suppor inactive not suppor inactive


OXFORD: Slot 0 SONET/SDH Alarms New EventDetail of SONET/SDH Alarms entry 0------------------------------------------------------------------------------- ifIndex : 4100 RDI Fault : inactive Link Location : lim1/link-0 LOP-P Defect : inactive LOS Defect : inactive LOP-P Fault : inactive LOS Fault : inactive UNEQ-P Defect : inactive LOF Defect : inactive UNEQ-P Fault : inactive LOF Fault : inactive PLM-P Defect : inactive EBER-P Thresh. : ten to minus five PLM-P Fault : inactive EBER-P Defect : inactive LOCD Defect : inactive EBER-P Fault : inactive LOCD Fault : inactive AIS-L Defect : active AIS-L Fault : active RDI-L Defect : inactive RDI-L Fault : inactive AIS-P Defect : inactive AIS-P Fault : inactive RDI-P Defect : inactive

Select option:Down, Enter entry number to edit, Goto row, Index search, Summary,



EBER-p Defect Excessive Bit Error Rate Defect declared when then path BIP-8 error monitor detects more than 1x10-3 (default 1x10-4 1x10-5 user selectable) errors per second. Cleared when the bit error rate falls below the specified threshold, or when the EBER defect is inhibited. Inhibited by: LOS, LOF, AIS-L, AIS-P, LOP-P NA. Read-only values are: active or inactive

EBER-P Fault Excessive Bit Error Rate Failure declared when the Excessive Bit Error Rate Defect is detected for least 2.5 +/- 0.5 seconds and no inhibitor failures are active. Cleared when Excessive Bit Error Rate Defect is absent for 10 +/- 0.5 seconds with no inhibitor defects and failures set. Read-only values are: active or inactive

AIS-l Defect Line Alarm Indication Signal Defect declared when bits 6, 7 and 8 of byte K2 are 111 for 5 consecutive frames and the AIS-L defect is not inhibited. Cleared when any other pattern is detected for 5 consecutive frames or is inhibited. Inhibited by: Loss of Signal (LOS), Loss of Frame (LOF). Read-only values are: active or inactive

AIS-L Fault Line Alarm Indication Signal Failure declared when the Line Alarm Indication Signal Defect is detected for at least 2.5 +/- 0.5 seconds and no inhibitor failures are active. Cleared when Line Alarm Indication Signal Defect is absent or inhibited for 10 +/- 0.5 seconds. Inhibited by: Loss of Signal (LOS), Loss of Frame (LOF).Read-only values are: active or inactive

RDI-L Defect Line Remote Defect Indicator Defect declared when bits 6, 7, and 8 of byte K2 are 110 for 5 consecutive frames and RDI-L defect is not inhibited. Cleared when any other pattern is detected for 5 consecutive frames or becomes inhibited. Inhibited by: Loss of Signal (LOS), Loss of Frame (LOF) Read-only values are: active or inactive

RDI-l Fault Line Remote Defect Indicator Failure declared when the Line Remote Defect Indicator Defect is detected for at least 2.5 +/- 0.5 seconds and is not inhibited. Cleared when Line Remote Defect Indicator Defect is absent or inhibited for 10 +/- 0.5 seconds. Inhibited by: Loss of Signal (LOS), Loss of Frame (LOF)Read-only values are: active or inactive

AIS-P Defect STS Path Alarm Indication Signal Defect declared when all 1's pattern is detected on the H1 and H2 bytes for 3 consecutive frames and is not inhibited. Cleared when valid pointers are detected in the H1 and H2 bytes for 3 consecutive frames or when the APS-P defect is inhibited. Inhibited by: LOS, LOF, AIS-LRead-only values are: active or inactive

AIS-P Fault STS Path Alarm Indication Signal Failure declared when the STS Path Alarm Indication Signal Defect is declared for at least 2.5 +/- 0.5 seconds and is not inhibited. Cleared when STS Path Alarm Indication Signal Defect is absent or inhibited for 10 +/- 0.5 seconds. Inhibited by: LOS, LOF, AIS-LRead-only values are: active or inactive

RDI-P Defect Path Remote Defect Indicator Defect declared when bit 5 of byte G1 is '1' for 10 consecutive frames and is the RDIP defect not inhibited. Cleared when bit 5 of byte G1 is '0' for 10 consecutive frames or is inhibited. Inhibited by: LOS, LOF, RDI-L, AIS-L, LOP-P. Read-only values are: normal or defect

RDI-P Fault Path Remote Defect Indicator Failure declared when the Path Remote Defect Indicator Defect is declared for at least 2.5 +/- 0.5 seconds and is not inhibited. Cleared when Path Remote Defect Indicator Defect is absent or inhibited for 10 +/- 0.5 seconds. Inhibited by: LOS, LOF, RDI-L, AIS-P, LOP-PRead-only values are: active or inactive

LOP-P Defect STS Loss of Pointer Defect declared when eight consecutive invalid pointers are detected and is not inhibited. Cleared when valid pointers are found in 3 consecutive frames or when the LOP-P defect is inhibited. Inhibited by: LOS, LOF, AIS-L, AIS-P.Read-only values are: active or inactive

LOP-P Fault STS Loss of Pointer Failure declared when the STS Loss of Pointer Defect is declared for at least 2.5 +/- 0.5 seconds and is not inhibited. Cleared when STS Loss of Pointer Defect is absent or inhibited for 10 +/- 0.5 seconds.Inhibited by: LOS, LOF, AIS-L, AIS-P. Read-only values are: active or inactive

UNEQ-P Defect Incompatibility between the local and the far-end LTE declared when the C2 byte of the path overhead section of the SONET frame is set to a value of 0 for 3 consecutive SONET frames, a path unequipped defect (P-UNEQ) is generated, provided the defect is not inhibited. Cleared when the far-end begins sending SONET frames indicating in the C2 byte that ATM cells are embedded in them or when the path unequipped defect is inhibited. Inhibited by: LOS, LOF, AIS-L, AIS-P, LOP-PRead-only values are: active or inactive



UNEQ-P Fault Declared when the Path Unequipped Defect is declared for at least 2.5 +/- 0.5 seconds and is not inhibited. Cleared when Path Remote Defect Indicator Defect is absent or inhibited for 10 +/- 0.5 seconds. Inhibited by: LOS, LOF, AIS-L, AIS-P, LOP-P.Read-only values are: active or inactive

PLM-P Defect STS Payload Label Mismatch (mismatch between the local LTE and the far-end LTE). Declared when the payload label is not 13 (hex) for 3 consecutive frames and no inhibitor defects are active. Cleared when the payload label is 13(hex) for 3 consecutive frames or when the payload label mismatch defect is inhibited. Inhibited by: LOS, LOF, AIS-L, AIS-P, LOP-P. Read-only values are: active or inactive

PLM-P Fault STS Payload Label Mismatch Failure is declared when the STS Payload Label Mismatch Defect is declared for at least 2.5 +/- 0.5 seconds and is not inhibited. Cleared when STS Payload Label Mismatch Defect is absent or inhibited for 10 +/- 0.5 seconds. Inhibited by: LOS, LOF, AIS-L, AIS-P, LOP-PRead-only values are: active or inactive

LOCD Defect Loss of Cell Delineation Defect is declared when a Loss of Cell Delineation is detected and is not inhibited. Cleared when the LIM can successfully calculate HCS for ATM cell headers for 6 consecutive ATM cells or when the LOCD defect is inhibited Inhibited by: LOS, LOF. Read-only values are: active or inactive

LOCD Fault Loss of Cell Delineation Failure is declared when the Loss of Cell Delineation Defect is declared for at least 2.5 +/- 0.5 seconds and is not inhibited. Cleared when Loss of Cell Delineation Defect is absent or inhibited for 10 +/- 0.5 seconds. Inhibited by: LOS, LOFRead-only values are: active or inactive


LIM Configuration SONET/SDH Automatic Protection Switching

ic under

g

below.

n the

S

or

SONET/SDH Automatic Protection SwitchingThe following section configures the LIM for Automatic Protection Switching (APS). For basinformation on APS, refer to the Xedge Technical Reference Manual (032R310), Chapter 1,the paragraphs on Switch Function.

1. At the root menu, select M,70,1,4 to access the SONET Automatic Protection Switchin(APS) screen. A menu appears with the following selections:

0 APS Group Configuration

1 APS Alarms

2 APS Link Configuration

2. For each APS function, perform the configuration steps as described in the procedures Refer to Table 7-4 as needed for configuration screen definitions.

APS Group Configuration1. At the SONET Automatic Protection Switching (APS)menu, select APS Group

Configuration . A summary screen for APS Group Configuration appears.

2. Use the Extra detail command to display the Detail of a APS Group Configuration entry. Iexample below, the Extra Detail screen shows entry 0 lim 2 (APS logical link-0) settings.

Figure 7-8 APS Group Configuration Detail Screen

3. To change the APS switching mode, select Switching Mode and enter the desired APS switching mode at the prompt.

4. To change the APS directional mode, select Directional Mode and enter the desired APS switching mode at the prompt.

5. To change the Wait to Restore Period, select WTR Period and enter the desired period at the prompt. To change this setting, the Switching Mode must be set to revertive .

6. To change the APS lockout, select Lockout and then enter y to lockout APS fail-over, or enter n to allow APS fail-over.

7. For a quad LIM, use the Down command to transition to the detail screen for entry 1 (APlogical link-1). Otherwise, repeat step 3. through step 7. for entry 1 (APS logical link-1).

8. Select X to exit back to the APS screen. Proceed to APS Link Configuration procedure,configure the Timing parameters as needed (via the LIM and Link Information menu).

Xedge Switch: Slot 1 APS Group Configuration 710ER6\700Detail of APS Group Configuration entry 0-------------------------------------------------------------------- Location : lim 2 Xmt K2 Channel : nullchannel apsGroupId : Grp01 Xmt K2 Arch : oneplusone0 Group Type : Undefined Xmt K2 Mode : unknown1 AdminState : Disabled Rvd K1 Con Code: norequest Config Access : Available Rvd K1 Channel : nullchannel2 Switching Mode : nonrevertive Rvd K2 Channel : nullchannel Actual Switchin: revertive Rvd K2 Arch : oneplusone3 Directional Mod: unidirectional Rvd K2 Mode : unknown Actual Directio: bidirectional4 WTR Period : fiveminutes5 Lockout : no Actual Lockout : no APS State : disabled Time to Revert : 900 Xmt K1 Con Code: norequest Xmt K1 Channel : nullchannel




Table 7-4 APS Group Configuration Parameters

APS Group Number Indicates the displayed APS Group Number. (Read only)

Links in APS Gr Displays the links that comprise the APS protection group. Read-only values are:link0 working - APS is disabled on Link-0.link1 working - APS is disabled on Link-1.link0 working and link0 protection - APS is enabled on Link-0.link1 working and link1 protection - APS is enabled on Link-1.

2 Switching Mode Specifies whether or not the traffic running on the protection link will be reverted back to the working link once the error or user command on the working link has been cleared and the WTR period has expired. (Immediate effect) Selectable values are:Revertive - the working link automatically will revert back from the protection link when the error on the working link has cleared and the WTR period has expired, or when the user command is cleared.Nonrevertive - the working link will not revert back from the protection link once the error has cleared; WTR Period is ignored. While in nonrevertive mode, the working link will revert back from the protection link only as a result of an error on the protection link, or a user command to switch.

Actual Switching Read-only display of the switching mode that is currently running on the APS group.

3 Directional Mode Determines whether tail and head ends will cooperate during a fail over request. It is recommend that both ends of the fiber span are set to the same mode (both ends bidirectional or both ends unidirectional). (Immediate effect) Options are:Bidirectional Switching - local LTE and remote LTE negotiate whether or not the receiver switch is on the protection link.Unidirectional Switching - In one-plus-one unidirectional, the tail end switches the receiver from the working to protection link without regard to the head end. Unidirectional switching provides a minor advantage over bidirectional switching in that the protection link can handle a receiver failure from both nodes.

Actual Direction Read-only display of the directional mode currently running on the APS group. If the local side has the APS Directional Mode set to bidirectional and the remote side is set to unidirectional, the Actual APS Directional Mode will be set to unidirectional.Refer to Directional Mode parameters for a description of the possible values.

4 WTR Period Specifies the Wait to Restore Period, which is the number of minutes to wait after an error has cleared on the working link before switching back from the protection link. The WTR Period can avoid repeated fail-overs due to intermittent error conditions. (Immediate effect) Selectable values are: 0, 5, 6, 7, 8, 9, 10, 11, and 12 minutes; 0 disables WTR (reverts immediately). Note that to set WTR, Switching mode must be set to NonRevertive .

5 Lockout Lockout from Protection option prevents any of the working links from failing over to the protection link, regardless of the severity of the errors on the links. If a working link is on the protection link when lockout is issued, it is switched back to its working link. Note that you cannot issue the Lockout command if an APS error exists on the working link. (Immediate effect) Possible selections are: Yes to prevent fail-over; No to allow fail-over.

Actual Lockout Indicates whether or not the lockout from protection is in effect. Note that tlockout will not take effect when an APS error exists on the working link (protection link failure, channel mismatch, protection switching byte failure, far-end protection switching failure or APS mode mismatch failure). Read-only values are: yes or no

State Displays the state of the APS protection group. For bidirectional configurations, the states of both LTEs are shown. For unidirectional configurations, only the state of the local LTE is shown. Read-only states are:disabled - APS is disabled for this group.active - No errors or commands are currently active.requestfailover - Signal fail request, waiting for the remote to acknowledge.failover - working link that is switched over to protection.sfsdwait - wait 5 seconds after a SD/SF has cleared before reverting or entering DNR or WTR states.wtr - revertive APS that is waiting for the WTR timer to expire before restoring the linkdnr - A one-plus-one working link had a fail-over to the protection link but the cause of the failure has been fixed or the user command has been terminated. The working link does not revert back from protection because APS is configured for nonrevertive.



State (Continued) revert - local LTE has requested that the remote LTE switch back to the working link from the protection link (this is a temporary state for bidirectional configurations only)requestlockout - local LTE is waiting for the remote LTE to acknowledge a lockout request (this is a temporary state for bidirectional APS only)lockout - local LTE has locked out all working links from the protection linkrequestexercise - local LTE is waiting for the remote LTE to acknowledge an exercise request (this is a temporary state for bidirectional APS only)Exercise - Exercise command is currently in effect on the protection linkrequestswitchfromprotection - local LTE has requested that the working link be removed from the protection link (via either a manual switch or a forced switch). This is a temporary state for bidirectional one-plus-one APS.switchfromprotection - a manual or forced switch from the protection link is in effect. For one-plus-one APS only.removefailoverrequest - temporary state. Remote LTE is requesting to failover to the working link. Local LTE should acknowledge the request with a reverse request and go to the remotefailover state.remotefailover - local LTE is entertaining a failover request from the remote LTE. For bidirectional APS only.remotewtr - local LTE is entertaining a WTR command from the remote LTE. A working link is currently failed over to the protection link. For bidirectional APS only.remoterevert - local LTE is in the process of reverting a working link from the protection link as commanded by the remote LTE. For bidirectional APS only.remoteswitchfromprotection - the remote LTE has moved the working link from the protection link via either a manual or forced switch that has been issued on the protection link. For bidirectional APS only.remotelockout - the local LTE is currently entertaining a lockout request from the remote LTE. For bidirectional APS only.remoteexercise - the local LTE is currently entertaining an exercise request from the remote LTE. For bidirectional APS only. remotednr - the bidirectional local LTE is currently entertaining a DNR request from the remote LTE.protectionlinkerror - signal fail, signal degrade, AIS, LOS, LOF on the protection link.channelmismatcherror - the channel number in the transmitted K1 does not match the channel number in the received K2. Indicates that the local and remote LTE's are out of sync.protectionswitchingbyteerror - K1 and K2 are not stable possibly due to a hardware error on the protection link.farendprotectionfailure - the remote LTE is indicates that there is a failure condition on the protection link. apsmodemismatch - the configuration of the local and remote LTE's do not match. Either the mode (bidirectional or unidirectional) or the APS type (1:n or one-plus-one) do not match between the two LTEs.protectiondegrade - Signal degradation is detected on the protection link.remoteprotectiondegrade - A remote LTE detected a signal degradation on a protection link.

Time to Revert Read-only display of how much time (in seconds) is left before the revert of the protection to working link will actually occur. If non-zero, then the link is configured for revertive switching mode and is currently waiting for the WTR timer to expire. Once a fail-over has occurred and the error condition is cleared, the wait to revert timer is started prior to reverting the protection link back to the working link. The displayed value indicates the time in seconds before the revert occurs. Note that if a link has its switching mode set to non revertive , then Time to Revert is not functional. Time to revert is only non-zero on the tail end node.APS State should be WTR when Time to Revert is non-zero.

Xmt K1 Con Code Transmitted Condition Code. The current APS request, transmitted in the K1 byte, to the remote LTE. A signal failure is either an AIS-L, LOS, LOF, or exceeding the Signal Failure Bit Error Rate (see SF BER Threshold in this chapter). Read-only values are:Lockout - indicates the working link is locked out from using the protection link.Signal Fail High - This state indicates a protection link signal failure.Signal Fail Low - This state indicates a working link signal failure.Signal Deg High - This state indicates that a signal degradation is detected on the protection link (see SD BER Threshold in this chapter).



Xmt K1 Con Code (Continued)Signal Deg Low - This state indicates that a signal degradation is detected on the working link (see SD BER Threshold in this chapter).Manual Switch - This state indicates a manual switch was invoked on either the working or protection link.Wait-to-Restore - The APS waits 5-minutes after a failure condition before transmitting a No Request or do not revert condition code.Reverse Request - The APS is configured for bidirectional and acknowledges a request from the tail end.No Request - This state indicates that there are no errors or user commands.Do not revert - After a failure condition, APS maintains the receiver switch on the protection link until the user manually switches the receiver back to the working link.Exercise - This state indicates that the user is invoking an exercise command.Not Valid - not supported

Xmt K1 Channel Displays the current link number, transmitted in bits 5-8 of the K1 byte by the local LTE, that is being requested to be placed onto the protection link. Read-only values are:null-channel - remote LTE is not requesting that working link be placed on the protection link.channel1 - local LTE is requesting that working link be placed on the protection link.channel2 - local LTE is requesting a command that applies to the protection linkchannel3 through channel15 - are not currently supported

Xmt K2 Channel Dsiplays the current link number, transmitted in the K1 byte by the local LTE, that is being bridged onto the protection link. Read-only values are:null-channel - no working link is currently bridged onto the protection linkchannel1 - local LTE is requesting that working link be placed on protection link.channel2 - local LTE is requesting a command that applies to the protection linkchannel3 through channel15 - are not currently supported

Xmt K2 Arch Displays the APS architecture transmitted by the local LTE in bit 5 of K2. Read-only values are : 1+1

Xmt K2 Mode Displays the current APS mode transmitted by the local LTE in bits 6-8 of K2. Read-only values are: bidirectional, unidirectional

Rvd K1 Con Code Displays the current APS request, received in bits 1-4 of the K1 byte, from the remote LTE. A signal failure is either an AIS-L, LOS, LOF, or exceeding the Signal Failure Bit Error Rate as described in SF BER Threshold in this chapter. Read-only values are:Lockout - indicates the working link is locked out from using the protection link.Signal Fail High - indicates a high priority signal failure.Signal Fail Low - indicates a low priority signal failure.Signal Deg High - indicates that a signal degradation is detected (see SD BER Threshold in this chapter).Signal Deg Low - indicates that a signal degradation is detected (see SD BER Threshold in this chapter).Manual Switch - indicates a manual switch was invoked on the working or the protection link.Wait-to-Restore - The APS will waits 5-minutes after a failure condition before transmitting a No Request or do not revert condition code.Reverse Request - The APS is configured for bidirectional and acknowledges a request from the tail end.No Request - indicates that there are no errors or user commands.Do not revert - After a failure condition, APS maintains the receiver switch on the protection link until the user manually switches the receiver back to the working link.exercise - indicates that the user is invoking an exercise command.Not Valid - not supported

Rvd K1 Channel Displays the current link number, received in bits 5-8 in the K1 byte from the remote LTE, that is being requested to be placed onto the protection link. Read only values are:null-channel - Remote LTE is not requesting that the working link be placed on the protection link.channel1 - Remote LTE is requesting the working link be placed on protection link.channel2 - Remote LTE is requesting a command that applies to protection link.channel3 through channel15 are not currently supported



rade. e B2 t slice

the ate is

tion takes

e same

Rvd K2 Channel Displays the current link number, received in bits 5-8 in the K1 byte from the remote LTE, that is bridged on the protection link. Read-only values are:null-channel - Remote LTE is not requesting that working link be placed on the protection link.channel1 - Remote LTE is requesting that working link be placed on protection link.channel2 - Remote LTE is requesting a command that applies to protection link.channel3 through channel15 are not currently supported

Rvd K2 Arch Received K2 Type. Displays the APS architecture from the remote LTE in bit 5 of K2. Read-only values are: 1+1

Rvd K2 Mode Displays the APS mode received from the remote LTE in bits 6-8 of K2. Read-only values: bidirectional, unidirectional, ais, rdi, unknown

APS Link Configuration

SD BER Threshold

The SD BER Threshold is the bit error rate (BER) that will cause a fail-over due to signal degBit rate error is calculated by the using the bit-interleaved parity-24 (BIP-24) contained in thbytes from each STS-3C frame. The B2 bytes provide an even parity calculation for each biin the STS-3C frame. As a result, each STS-3 frame can have up to 24 parity errors.

As shown in the table below, the period of time over which BER is accumulated, as well as length of time it will take to clear the error, depends on the BER. For example, the line error r

sampled over a 1 second interval to determine an error rate of 10-6. The line error rate is sampled

over a 10 second interval to determine when the 10-6 has cleared.

If APS is configured for revertive switching and working link is recovering from an error condithen the WTR timeout is added to the clear interval when determining the amount of time it to revert a link from protection to working, once an error has been cleared.

You can set the SD BER Threshold to the values shown in Table 7-5. Although each link can havea different SD BER threshold, it is recommended that both endpoints of an OC-3 span have thvalues for SD BER.

Note The SD BER threshold must be greater than the SF BER threshold.

Table 7-5 SD BER Values and Effects

BER Threshold

BER Accumulation Interval (in seconds)

BER Clear Interval (in seconds)

10-5 .100 1.000

10-6 1.000 10.000

10-7 10.000 83.000

10-8 83.000 667.000

10-9 667.000 5000.000



. The tion of

3 byte

s. The to 24

clear mine an clear

SF BER Threshold

The SF BER Threshold is the bit error rate (BER) that will cause a fail-over due to signal failAPS SF BER measures the BER as based on the line BIP-24 bytes in the link overhead secthe SONET frame. The EBER threshold, specified in the link alarm page, is based on the B(the BIP-8 error rate associated with the path overhead section of the SONET frame).

The BIP-24 code in the line overhead section of the STS-3C frame is contained in the B2 byteB2 bytes are generated by the transmitting equipment such that they provide an even paritycalculation for each bit slice in the STS-3C payload. As a result, STS-3C frame can have upparity errors.

The period of time over which BER is accumulated, as well as the length of time it will take to the error, depends on the BER. For example, it takes 0.008 seconds of sample time to detererror rate of and 0.013-seconds to determine that the error rate has lowered below the BERthreshold.

You can set the SF BER Threshold to the values shown in Table 7-6.

Note The SD BER threshold must be less than the SF BER threshold.

Table 7-6 SF BER Values and Effects

BER Threshold

BER Accumulation Interval (in seconds)

BER Clear Interval (in seconds)

10-3 .008 .013

10-4 .013 .100

10-5 .100 1.000



and PS

o

le

n

APS Link Configuration Procedure

The APS Link Configuration Screen allows you to set the Signal Degradation Bit Error RateSignal Failure Bit Error Rate thresholds. Additionally you can manually switch between the Aworking and protection link and/or exercise the APS protocol. Use the following procedure tperform the optional APS Link Configuration procedure. Refer to Table 7-7for screen definitions.

1. At the SONET Automatic Protection Switching (APS) menu, select APS Alarms . A summary screen for APS Alarms appears.

2. Use the Extra detail command to display the Detail of a APS Alarms entry. In the exampbelow, the Extra Detail screen shows entry 0 lim 2 (APS logical link-0) settings

Figure 7-9 Detail of APS Link Configuration Screen

3. To change the SD BER threshold, select Signal Degrade bit error rate and enter the desired value at the prompt.

4. To change the SF BER threshold, select Signal Fail bit error rate and enter the desiredvalue at the prompt.

5. Select Clear APS Commands and then enter y at the prompt to clear all commands.

6. Select Forced Switch and enter y at the prompt if you want to force a switch betweethe APS working link and its corresponding protection link.

7. Select Manual Switch and enter y at the prompt if you want to manually switch between the APS working link and its corresponding protection link.

8. Select APS Exercise and enter y at the prompt if you want to exercise the APS protocol.

9. If you are configuring a quad LIM, use the D own command to transition to the detail screenfor entry 1, “link-0 (P).”

10. Repeat step 3. through step 9. for entry 1 (APS logical link-1). When complete, proceed to LIM Timing configuration (via the LIM Information and Configuration menu).

Xedge Switch: Slot 1 APS Link Configuration 710ER6\700Detail of APS Link Configuration entry 0------------------------------------------------------------------------------ ifIndex : 4200 Link Location : lim2/link-00 Clear APS Comma: no1 Forced Switch : no Actual Forced S: no2 Manual Switch : no Actual Manual S: no3 APS Exercise : no Actual APS Exer: no Link State : disabled Signal Fail Con: no Signal Fail Thr: no Signal Degrade : no4 Signal Degrade : tentominusfive5 Signal Fail bit: tentominusthree APS Group : noSelect option:Down, Enter entry number to edit, Goto row, Index search, Summary,eXit



Table 7-7 APS Link Configuration Parameters

Link Number Indicates the link number of the displayed link. (Read only)

Signal Degrade bit error rate: The bit error rate (BER) that will cause a fail over due to signal degrade. Although each link can have a different SD BER threshold, it is recommended that both endpoints of an OC-3C span have the same values for SD BER. (Immediate effect) (Note: The SF BER threshold must be smaller than the SD BER threshold. See SD BER Threshold in this chapter.)

Signal Fail bit error rate: The bit error rate (BER) that will cause a fail over due to signal fail. (Immediate effect)(Note: The SD BER threshold must be greater than the SF BER threshold. See SF BER Threshold in this chapter.)

Clear APS Commands: Clears all outstanding commands (lockout, force, manual, exercise) on the APS link. (Immediate effect) Select yes to clear all outstanding commands.Select no to exit this option without clearing all outstanding commands.

Forced Switch Switches the specified working link to the protection link (or the protection link back to the working link) unless there is one of the following conditions; a higher priority command, a higher priority force command or there is an failure outstanding on the protection link. Has higher priority than a manual switch, signal fail, and signal degrade. (Immediate effect) For revertive configurations, when the forced switch is turned off, the protection link will immediately revert back to the working link, unless there is a signal fail or signal degrade condition on the working link. There isn’t a WTR interval at the end of the forced switch. In the nonrevertive configuration, disabling the forced switch will leave the working link on the protection link unless there is an error or another forced or manual switch from protection to the working link.When a APS group lockout is in effect, this option is not functional.If the Forced Switch is preempted by a higher priority command (lockout from protection or forced switch from protection), the Forced Switch will automatically be set to no .Select yes to switch the specified working link to the protection link.Select no to revert (if revert is enabled). (Immediate effect)

Actual Forced Switch: Indicates if the Forced Switch actually took effect. Read-only values are:no - indicates a forced switch did not occur.yes - indicates a forced switch did occur.

Manual Switch Switches the working link to the protection link (or a protection link back to the working link), unless a command or error of equal or higher priority is in effect. Force switch, signal fail and signal degrade have higher priority than a manual switch.Select yes to switch the specified working link to the protection link.Select no to revert (if revert is enabled).For revertive configurations, when the manual switch is turned off, the protection link will immediately revert back to the working link unless there is a signal fail or signal degrade condition on the working link. There is not a WTR interval at the end of the manual switch.In the nonrevertive configuration, disabling the manual switch will keep the working link on the protection link unless there is an error or another forced or manual switch from protection to the working link.When a APS group lockout is in effect, this option is not functional.If a manual switch is prevented by a higher priority command (forced switch, lockout from protection, forced switch from protection or manual switch from protection) will result in the manual switch being set to no.

Actual Manual Switch: Read-only indication of whether the Manual Switch took effect:no - indicates a manual switch did not occur.yes - indicates a manual switch did occur.



APS Exercise Exercises the APS protocol and checks the responses to APS commands from the head end. If the protection link is already in use the exercise command has no effect. This is a continuous non-interfering exercise and it does not cause an APS switch. Select yes to exercise the APS protocol.Select no to exit this option without exercising the APS protocol.Note that 1+1 bidirectional - causes an exercise command to be sent to the remote LTE but has no impact on the local LTE. 1+1 unidirectional - no action required.When a APS group lockout is in effect, this option is not available.If the Exercise command is preempted by a higher priority command (lockout from protection, forced switch, manual switch, forced switch of protection link or manual switch of protection link), then Exercise will be set to no.

Actual APS Exercise: Read-only indication of whether the exercise command is in effect.no - indicates the exercise command is not in effect.yes - the exercise command is in effect.

Link State Read-only status of the APS link:disabled - APS is disabled on this link.working - Working link, no errorslockout - link has an error condition or APS user command but has not failed over to protection due to a lockout command, issued locally or remotely on the APS group.APS error - link has an error condition or APS user command but has not failed over to protection because of an APS defect or failure preventing the APS protocol from flowing from the local LTE to the remote LTE.failed over - Working link that has failed over to the protection linklockout - link is locked out from the protection linkprotection - Protection link, no working links have currently failed over.protection, in use - Protection link. One of the working links has failed over.

Signal Fail Condition: Read-only indication of a signal fail condition due to Loss of Signal, Loss of Frame, AIS or RDI is active on the link:no - signal fail condition is not present; yes -signal fail condition is present.Note that with an SF condition on a working link, the APS group state should be: pending, switched, bridged, switch+bridge or WTR. With an SF condition on a protection link, the APS group state should be Error.

Signal Fail Threshold Error: Read-only indication that the link bit error rate has passed the SF BER threshold specified the Link Configuration screen.no - indicates the link bit error rate has not passed the SF BER threshold.yes - link bit error rate has passed the SF BER threshold.Note that if there is a SF Threshold Error and this is a working link then the state of the APS group should be either switch+bridge or lockout. If there is a SF Threshold Error and this is a protection link, then the state of the APS group should be Error.

Signal Degrade Threshold Error: Read-only indication of whether the link bit error rate has passed the SD BER Threshold error rate specified in the APS Link Configuration screen. no - link bit error rate has not passed SD BER Threshold error rate.yes - link bit error rate has passed the SD BER Threshold error rate.If there is a SD Threshold Error, and this is a working link, then the link status should be Pending, Failed Over, or Lockout. SD threshold error has no effect on a protection link.



ar

le

.

APS Alarms

1. At the root menu, select M,70,1,4,1 to access the APS Alarms summary screen, similto the example below.

2. Use the Extra detail command to display the Detail of a APS Alarms entry. In the exampbelow, the Extra Detail screen shows entry 0 lim 2 (APS logical link-0) settings.

Figure 7-10 APS Alarms Detail Screen

3. Use the Down command to transition to the detail screen for entry 1 (APS logical link-1)

Table 7-8 APS Alarms Definitions

APS Group Number Indicates the APS Group Number displayed in this screen. apsGroupAlarmLinksInGroup

Lists the links that comprise the APS protection group. Read only values are: Link 0 WorkingLink 1 WorkingLink 0 WorkingLink 0 ProtectionLink 1 WorkingLink 1 Protection

Protection Link DefectIndicates if the protection link on the local LTE is in an error condition (LOS, LOF, or AIS-L), preventing fail-overs from occurring until the error has been fixed. During a Protection Link Defect, the switch will output the following K1, K2:K1 Condition Code = NO REQUESTK1 Channel Number = NULL CHANNELK2 Channel Number = NULL CHANNEL

Protection Link FailureIndicates if the protection link defect has been active for 2.5 seconds. The protection link failure is cleared when the protection link defect has been cleared for 10 seconds.

Xedge Switch: Slot 1 APS Alarms 710ER6\700Detail of APS Alarms entry 0-------------------------------------------------------------------- Location : lim 2 APS group : Grp01 Links : Protection Link Defect : inactive Protection Link Failure : inactive Protection Switching Byte Defe: inactive Protection Switching Byte Fail: inactive Far-End Protection-Line Defect: inactive Far-End Protection-Line Failur: inactive Channel Mismatch Defect : inactive Channel Mismatch Failure : inactive APS Mode Mismatch Defect : inactive APS Mode Mismatch Failure : inactive




Protection Switching Byte DefectIndicates an APS protocol error with the remote LTE, either an internal error on the LIM or a severe transmission error from the remote LTE. A protection switching byte defect results due to one of the following reasons:APS is synchronized when the LTE receives three consecutive SONET frames with the same K1 bytes in the transport overhead section of the SONET frame. If the OC-3 receives 12 successive SONET frames, where no three consecutive frames have identical K1 bytes then a protection switch defect will arise. When three consecutive SONET frames are received with the same K1 bytes then the protection switch detect will be released or the defect is not inhibited.An APS group configured for bidirectional switching and an unexpected or invalid K1 or K2 byte is received.During a Protection Switching Byte Failure, APS will output the following K1/K2:K1 Condition Code = Signal Failure HighK1 Channel Number = 2Note that this is inhibited by a Protection Link Defect.

Protection Switching Byte FailIndicates an APS protocol failure with the node at the end of this OC-3 segment. This failure indicates that the Protection Switch Defect has been in effect for over 2.5 seconds. When the Protection Switch Defect is not raised for 10 seconds then the protection switch failure will be cleared.Inhibited by: protection link defect. This either indicates an internal error on the LIM or a severe transmission error from the other side. A protection switch defect prevents fail-overs from occurring until the defect has been fixed.

Far-End Protection-Line DefectIndicates a protection link failure on the remote LTE (LOS, LOF, or AIS-L). If an OC-3 LIM is configured for any other mode other than unidirectional one-plus-one then the far-end defect failure will be assured when the adjacent node indicates the SF on the protection link. The failure will be cleared when the adjacent node indicates that the SF condition on protection link has been cleared. A far-end protection defect prevents fail-overs from occurring until the defect has been cleared. A protection switch defect prevents fail-overs from occurring until the defect has been fixed. Inhibited by a protection link defect or a PSB defect.

Far-End Protection-Line FailureIndicates a Far-End protection defect has been active for 2.5 seconds. The failure will be cleared when the adjacent node indicates that the protection link has been cleared for over 10 seconds. A far-end protection failure alarm prevents fail-overs from occurring until the failure has been cleared. Inhibited by a protection link defect or a PSB defect.

Channel Mismatch DefectIndicates an APS protocol error for 1:n or 1+1 bidirectional APS configurations only. If the channel numbers don’t match for 3 consecutive OC-3 frames, then a channel mismatch defect will result. The channel mismatch defect is cleared when the channel numbers match for 10 seconds or the channel mismatch has been inhibited. Under normal circumstances, a mismatch occurs every time the tail end changes the channel number in K1. A mismatch can also occur if the link between the two LTE’s fails and the channel number received does not equal the transmitted channel number in K1. Inhibited by a protection link defect, a protection switching byte defect, or an FEP defect.

Channel Mismatch FailureIndicates that a channel mismatch defect has been active for over 2.5 seconds. The channel mismatch failure is cleared when the channel numbers match for 10 seconds. During Channel Mismatch Failure, the switch of the receiver will be reverted back to the working link until the alarm clears. A protection switch defect prevents fail-overs from occurring until the defect has been fixed.Also during a channel mismatch failure, APS will output a K1/K2 as follows:K1 Condition Code = NO REQUESTK1 Channel Number = NULL CHANNELK2 Channel Number = NULL CHANNELInhibited by a protection link defect, a protection switching byte defect, or an FEP defect.

APS Mode Mismatch DefectIndicates that the node’s switching or directional modes do not match the LTE configuration on the other end of the OC-3 segment. If a OC-3 LIM is configured for any mode other than unidirectional 1+1, an APS mode defect will occur when the switching and directional modes do not match for over 5 or more OC-3 frames. Inhibited by protection link defect, protection switching byte defect, FEP defect, or channel mismatch failure.

APS Mode Mismatch FailureIndicates that an APS mode defect has been active for 2.5 seconds. The APS mode mismatch will be removed when the APS protocol is exchanged between the two nodes without mode mismatches for 10 seconds. Inhibited by a protection link defect, a protection switching byte defect, an FEP defect, or a channel mismatch failure.


LIM Configuration SONET/SDH Defects

wn

a

SONET/SDH Defects

1. At the root menu, select M,70,1,5 to access the SONET/SDH Defects screen. Select Doto view longer lists.

2. Select an entry, then select Extra Details. Figure 7-11 shows an example display and an ExtrDetail screen of Defects Entry 0.

Figure 7-11 SONET/SDH Defects Summary Screen

Table 7-9 Defects Definitions

LOS Defect: Loss of Signal DefectDeclared when all zero's are received for 20 +/- 3 microseconds or longer. Cleared when two valid framing words are detected. There are no defects or failures that inhibit LOS defect.

LOS Fault: Loss of Signal FailureDeclared when Loss of Signal Defect is declared for at least 2.5 +/- 0.5 seconds. Cleared when Loss of Signal Defect is absent for 10 +/- 0.5 seconds. There are no defects or failures that inhibit LOS failure.

LOF Defect: Loss of Frame DefectDeclared when a out-of-frame conditions persists for a period of 3 milliseconds and is not inhibited. Cleared when an in-frame condition persists for 3 milliseconds or a defect inhibitor becomes active. Inhibited by: Loss of Signal (LOS).

LOF Fault: Loss of Frame FailureDeclared when Loss of Frame Defect is declared for at least 2.5 +/- 0.5 seconds and is not inhibited. Cleared when Loss of Frame Defect is absent or inhibited for 10 +/- 0.5 seconds. Inhibited by: Loss of Signal (LOS).

EBER-P Thresh: User selectable threshold Excessive Bit Error Rate DefectThis parameter specifies the allowable path error rate, as determined by monitoring the B3 byte in the path overhead section of the SONET frame header.

Xedge Switch: Slot 0 SONET/SDH Defects 710ER6\700No ifIndex Link Location LOS-S LOF-S AIS-L LOP-P UNEQ-P PLM-P--------------------------------------------------------------------------------0 4200 lim2/link-0 inactive inactive inactive inactive inactive inactive1 4201 lim2/link-1 inactive inactive inactive inactive inactive inactive2 4202 lim2/link-2 inactive inactive inactive inactive inactive inactive3 4203 lim2/link-3 inactive inactive inactive inactive inactive inactive


MAINSCREEN

EXTRADETAILS

Xedge Switch: Slot 0 SONET/SDH Defects 710ER6\700Detail of SONET/SDH Defects entry 0-------------------------------------------------------------------------------- ifIndex : 4200 Link Location : lim2/link-0 LOS-S : inactive LOF-S : inactive AIS-L : inactive LOP-P : inactive UNEQ-P : inactive PLM-P : inactive




EBER-P Defect: Excessive Bit Error Rate DefectDeclared when then path BIP-8 error monitor detects more than 1x10-3 (default 1x10-4 1x10-5 user selectable) Errors per second. Cleared when the bit error rate falls below the specified threshold or when the EBER defect is inhibited. Inhibited by: LOS, LOF, AIS-L, AIS-P, LOP-P.

AIS-L Defect: Line Alarm Indication Signal DefectDeclared when bits 6, 7 and 8 of byte K2 are '111' for 5 consecutive frames and the AIS-L defect is not inhibited. Cleared when any other pattern is detected for 5 consecutive frames or is inhibited. Inhibited by: Loss of Signal (LOS), Loss of Frame (LOF).

AIS-L Fault Line: Alarm Indication Signal FailureDeclared when the Line Alarm Indication Signal Defect is declared for at least 2.5 +/- 0.5 seconds and no inhibitor failures are active. Cleared when Line Alarm Indication Signal Defect is absent or inhibited for 10 +/- 0.5 seconds. Inhibited by: Loss of Signal (LOS), Loss of Frame (LOF).

RDI-L Defect Line: Remote Defect Indicator DefectDeclared when bits 6, 7, and 8 of byte K2 are 110 for 5 consecutive frames and RDI-L defect is not inhibited. Cleared when any other pattern is detected for 5 consecutive frames or becomes inhibited. Inhibited by: Loss of Signal (LOS), Loss of Frame (LOF).

RDI-L Fault Line: Remote Defect Indicator FailureDeclared when the Line Remote Defect Indicator Defect is declared for at least 2.5 +/- 0.5 seconds and is not inhibited. Cleared when Line Remote Defect Indicator Defect is absent or inhibited for 10 +/- 0.5 seconds. Inhibited by: Loss of Signal (LOS), Loss of Frame (LOF).

AIS-P Defect STS Path: Alarm Indication Signal DefectDeclared when all 1's pattern is detected on the H1 and H2 bytes for 3 consecutive frames and is not inhibited. Cleared when valid pointers are detected in the H1 and H2 bytes for 3 consecutive frames or when the APS-P defect is inhibited. Inhibited by: LOS, LOF, AIS-L.

AIS-P Fault STS Path Alarm Indication Signal FailureDeclared when the STS Path Alarm Indication Signal Defect is declared for at least 2.5 +/- 0.5 seconds and is not inhibited. Cleared when STS Path Alarm Indication Signal Defect is absent or inhibited for 10 +/- 0.5 seconds. Inhibited by: LOS, LOF, AIS-L.

RDI-P Defect Path Remote Defect Indicator DefectDeclared when bit 5 of byte G1 is '1' for 10 consecutive frames and is the RDI-P defect not inhibited. Cleared when bit 5 of byte G1 is '0' for 10 consecutive frames or is inhibited. Inhibited by: LOS, LOF, RDI-L, AIS-L, LOP-P.

RDI-P Fault Path Remote Defect Indicator FailureDeclared when the Path Remote Defect Indicator Defect is declared for at least 2.5 +/- 0.5 seconds and is not inhibited. Cleared when Path Remote Defect Indicator Defect is absent or inhibited for 10 +/- 0.5 seconds. Inhibited by: LOS, LOF, RDI-L, AIS-P, LOP-P.

LOP-P Defect STS Loss of Pointer DefectDeclared when 8 consecutive invalid pointers are detected and is not inhibited. Cleared when valid pointers are found in 3 consecutive frames or when the LOP-P defect is inhibited. Inhibited by: LOS, LOF, AIS-L, AIS-P.

LOP-P Fault STS Loss of Pointer FailureDeclared when the STS Loss of Pointer Defect is declared for at least 2.5 +/- 0.5 seconds and is not inhibited. Cleared when STS Loss of Pointer Defect is absent or inhibited for 10 +/- 0.5 seconds. Inhibited by: LOS, LOF, AIS-L, AIS-P.

UNEQ-P Defect Incompatibility between the local and the far-end LTEDeclared when the C2 byte of the path overhead section of the SONET frame is set to a value of 0 for 3 consecutive SONET frames, a path unequipped defect (P-UNEQ) is generated, provided the defect is not inhibited. Cleared when the far-end begins sending SONET frames indicating in the C2 byte that ATM cells are embedded in them or when the path unequipped defect is inhibited. Inhibited by: LOS, LOF, AIS-L, AIS-P, LOP-P.

UNEQ-P Fault Declared when the Path Unequipped Defect is declared for at least 2.5 +/- 0.5 seconds and is not inhibited. Cleared when Path Remote Defect Indicator Defect is absent or inhibited for 10 +/- 0.5 seconds. Inhibited by: LOS, LOF, AIS-L, AIS-P, LOP-P.

PLM-P Defect STS Payload Label Mismatch (mismatch between the local LTE and the far-end LTE). Declared when the payload label is not 13 (hex) for 3 consecutive frames and no inhibitor defects are active. Cleared when the payload label is 13(hex) for 3 consecutive frames or when the payload label mismatch defect is inhibited. Inhibited by: LOS, LOF, AIS-L, AIS-P, LOP-P.



PLM-P Fault STS Payload Label Mismatch Failure. Declared when the STS Payload Label Mismatch Defect is declared for at least 2.5 +/- 0.5 seconds and is not inhibited. Cleared when STS Payload Label Mismatch Defect is absent or inhibited for 10 +/- 0.5 seconds. Inhibited by: LOS, LOF, AIS-L, AIS-P, LOP-P

LOCD Defect Loss of Cell Delineation Defect. Declared when a Loss of Cell Delineation is detected and is not inhibited. Cleared when the LIM can successfully calculate HCS for ATM cell headers for 6 consecutive ATM cells or when the LOCD defect is inhibited. Inhibited by: LOS, LOF.

LOCD Fault Loss of Cell Delineation Failure. Declared when the Loss of Cell Delineation Defect is declared for at least 2.5 +/- 0.5 seconds and is not inhibited. Cleared when Loss of Cell Delineation Defect is absent or inhibited for 10 +/- 0.5 seconds. Inhibited by: LOS, LOF.

LOF Loss OF FrameDeclared when four consecutive frames containing one or more framing pattern (Out of Frame) errors have been received for a period of 3msec. Cleared when an in-frame condition persists for 3msec.

LOP-P TS Loss Of PointerDetected when a normal pointer value is not found in 8 consecutive frames. Cleared when a normal pointer value is detected in 3 consecutive frames.

AIS-L Line Alarm Indication SignalDeclared when bits 6, 7 and 8 of the K2 byte have the '111' pattern for 5 consecutive frames. Cleared when these bits have a pattern other than '111' for 5 consecutive frames from the remote PCX or PCL Force AIS-L.

AIS-P TS Path Alarm Indication SignalDetected when an all ones pattern is received in the pointer bytes (H1 and H2) for 3 consecutive frames. AIS-P is cleared when a valid pointer is detected for 3 consecutive frames.

PLM-P TS Payload Label MismatchDetected when the received payload label is a value other than 0x13 (ATM Mapping).

RFI-L Line FERF Remote Failure Indicator-LineDetected when a '110' pattern is detected in bits 6,7 and 8 of the K2 bytes for 5 consecutive frames. Cleared when any other pattern than '110' is detected for 5 consecutive frames

RFI-P Remote Failure Indicator-PathFormerly Path Yellow. Detected when bit 5 of G1 byte is '1' for 10 consecutive frames. Cleared when bit 5 of G1 byte is '0' for 10 consecutive frames.

EBER Excessive Bit Error RateAn excessive BER corresponding to an error rate of 1 x 10-3 is detected by monitoring the number of Path BIP-8 errors accumulated in a 1 second period.



Table 7-10 Section Statistics

CV-Ss Section Coding ViolationsCount of BIP Errors detected at the Section Layer of the incoming OC-3C/STM-1 signal (BIP 8 count in the B1 byte of Section Overhead).

ES-Ss Section Errored SecondsAny second with at lest one CV-S, or where 1 or more Loss Of Signal defects were detected.

SES-Ss Section Severely Errored SecondsAny second with 2500 or more CV-Ss, or where 1 or more Loss Of Signal defects were detected.

Table 7-11 Line (Near & Far-End) Statistics

CV-L Near-End Line Coding ViolationsCount of BIP errors detected at the Line layer of the incoming OC-3C/STM-1 signal (BIP 24 count in the B2 byte of the Line Overhead).

ES-L Near-End Line Errored SecondsAny second with at least one CV-L, or where an AIS-L defect was detected.

SES-L Near-End Line Severely Errored SecondsAny second with 2500 or more CV-Ls, or where an AIS-L defect was detected.

FC-L Near-End Line Failure CountsCount of the number of occurrences of near-end line failure events. A failure event occurs when the AIS-L alarm is declared, and ends when the AIS-L alarm is cleared. A failure event that begins in one accumulation interval and ends in another is counted only in the interval in which it begins.

UAS-L Near-End Line Unavailable SecondsAny second during which the Line is considered un-available. The Line becomes unavailable at the onset of 10 consecutive SES-Ls, which are included in the unavailable time. The line becomes available at the onset of 10 consecutive seconds where no SES-Ls occur. The 10 seconds without SES-Ls are excluded from unavailable time.

CV-LFE Far-End Line Coding ViolationCount of BIP errors detected at the Line layer of the incoming signal at the far end (FEBE-L count in the Z2 byte of the Line Overhead).

ES-LFE Far-End Line Errored SecondsAny second with at least one CV-LFE, or where an RDI-L defect was detected.

SES-LFE Far End Line Severely Errored SecondsAny second with 2500 or more CV-LFEs, or where an RDI-L defect was detected.

FC-LFE Far-End Line Failure CountsCount of the number of occurrences of far-end line failure events. A failure event occurs when the RFI-L alarm is declared, and ends when the RFI-L alarm is cleared. A failure event that begins in one accumulation interval and ends in another is counted only in the interval in which it begins.

UAS-LFE Far-End Line Unavailable SecondsAny second during which the Line is considered unavailable at the far end. The Line becomes unavailable at the onset of 10 consecutive SES-LFEs, which are included in the unavailable time. The line becomes available at the onset of 10 consecutive seconds where no SES-LFEs occur. The 10 seconds without SES-LFEs are excluded from unavailable time.



Table 7-12 Sts-3c Path (Near & Far End) Statistics

CV-P STS Path near End Coding ViolationsCount of BIP Errors detected at the Path Layer of the incoming OC-3C/STM-1 signal (BIP 8 count in the B3 byte of Path Overhead).

ES-P STS Path Near End Errored SecondsAny second with at least 1 CV-P, or where an AIS-P or LOP-P defect is detected.

SES-P STS Path Near End Severely Errored SecondsAny second with 2400 or more CV-Ps, or where an AIS-P or LOP-P defect is detected.

FC-P STS Path Near-End Failure CountsCount of the number of occurrences of near-end Path failure events. A failure event begins when either an LOP-P or AIS-P alarm is declared, and ends when the LOP-P and/or AIS-P alarms are cleared. A failure event that begins in one accumulation interval and ends in another is counted only in the interval in which it begins.

UAS-P STS Path Near-End Unavailable SecondsAny second during which the Path is considered un-available. The Path becomes unavailable at the onset of 10 consecutive SES-Ps, which are included in the unavailable time. The Path becomes available at the onset of 10 consecutive seconds where no SES-Ps occur. The 10 seconds without SES-Ps are excluded from unavailable time.

CV-PFE STS Path Far-End Coding ViolationCount of BIP Errors detected at the Path Layer of the incoming OC-3/STM-1signal at the far end (FEBE-P count in the G1 byte of Path Overhead).

ES-PFE STS Path Far-End Errored SecondsAny second with at least 1 CV-PFE, or where an RDI-P defect is detected.

SES-PFE Path Far-End Severely Errored SecondsAny second with 2400 or more CV-PFEs, or where an RDI-P defect was detected.

FC-PFE STS Path Far-End Failure CountCount of the number of occurrences of far-end Path failure events. A failure event begins when the RFI-P alarm is declared, and ends when the RFI-P alarm is cleared. A failure event that begins in one accumulation interval and ends in another is counted only in the interval in which it begins.

UAS-PFE STS Path Far-End Unavailable SecondsAny second during which the Path is considered unavailable at the far end. The Path becomes unavailable at the onset of 10 consecutive SES-PFEs which are included in the unavailable time. The Path becomes available at the onset of 10 consecutive seconds where no SES-PFEs occur. The 10 seconds without SES-PFEs are excluded from unavailable time.


LIM Configuration DLIMs

and

DLIMsThis section provides procedures for configuring links for the followibng LIMs:

• DS1-2C/4C Links Configuration

• E1-2C/4C Links Configuration

• DS3 or E3 LIM Configuration

• DS3-2C LIM Configuration

• E3-2C LIM Configuration

DS1-2C/4C Links ConfigurationTo configure the Physical Framer, perform the following steps.

1. From root menu, select M,19 to access the DLIMs screen.

2. Select option 1 to access the DS1-2C/4C DLIM Config/Status screen.

3. Select E to view the Extra Detail for entry 0, similar to the example below. Table 7-13 describe the screen parameters.

Figure 7-12 DS1-2C/4C DLIM Configuration/Status Screen (M,19,1,E )

4. At the Select prompt, enter the option number for a parameter, in turn, to be configured enter the changes.

5. After making all changes for link 0, select option 8 Reconfigure and then press the Enter key.

6. At the Reconfigure (Y/N) prompt, type Y to send the changes to the LIM.

7. Select Down to transition to the Extra Detail for the next entry to be configured.

8. Repeat step 4. through step 7. as needed for the available links.

9. When complete, select eX it twice to return to the MIB Display and Management screen.

10. Select S ave . This completes the Physical Framer configuration for the DS1-2C/2S LIM.

Switch Name:Slot x SYS ds1-2C/4C DLIM Config/Status New EventDetail of ds1-2C/4C DLIM Config/Status entry 0

Link No : 0 LOS Alarm : no Version : ds1 dual LOF Alarm : no0 Txmt Line Lengt: feet 0 110 AIS Alarm : no1 Framer : none Yellow Alarm : no2 Line Coding : b8zs BER Alarm : no3 Loopback : none DS1 Framing Err: 04 Tx AIS : no DS1 Bit Errors : 05 Extract Frame B: yes DS1 OOF/COFA Er: 06 Txmt Clock Sele: system DS1 LCV Errors : 07 Clear Counters : yes Line ES : 08 Reconfigure : no Line SES : 0 LOS Defect : no ES : 0 OOF Defect : no SES : 0 AIS Defect : no AISS : 0 Yellow Defect : no UAS : 0 BER Defect : no ExBER : 0Select option:Down, Enter entry number to edit, Goto row, Index search, Summary,eXit


LIM Configuration DS1-2C/4C Links Configuration

Table 7-13 DS1-2C/4C DLIM Config/Status Parameter Definitions

Parameter Definition Takes Effect On

Link No Indicates the number of the link currently under review. Read only

Version Indicates the LIM type installed. Read only

0 Txmt Line Lengt Enables/indicates the setting of the line length. The options are:A - feet 0 110 (default) B - feet 110 220F - feet 550 660C - feet 220 330G - more than 655 feetD - feet 330 440H - squareE - feet 440 550

Reconfigure

1 Framer Enables/indicates the setting of the framer. The options are:A - none (default): transparent modeB - sf : superframeC - t1dm : DS1 data multiplexer framingD - slc96 : SLC96 framingE - esf4k : extended superframe, 4 Kbit/s data linkF - esf2K 3 : extended superframe, 2 Kbit/s data link, frames 3, 7, 11, 15, 19, 23G - esf2k 1 : extended superframe, 2 Kbit/s data link, frames 1, 5, 9, 13, 17, 21

Reconfigure

2 Line Coding Enables/indicates the setting of the line code. The options are:A - b8zs (default): bit 8-zero suppression coding.B - ami : alternate mark inversion coding.

Reconfigure

3 Loopback Enables/indicates the setting of the diagnostic loopback. Options are:A - none (default)B - line lpbkC - payload lpbkD - digital lpbk.

Immediate(Loopbacks cause data disruption.)

4 Tx AIS Enables/indicates the setting of the transmit Alarm Indication Signalling (AIS) cells. yes : Type y to enable the transmission of AIS cells.no (default): Type n to disable AIS cell transmission.

Reconfigure

5 Extract Frame B Enables/indicates the extraction of frame bits: yes : Type y to enable the extraction of frame bits.no (default): Type n to disable frame bit extraction.You should leave this option at the default setting, no .

Reconfigure

6 Txmt Clock Sele Enables/indicates the selection of the transmit clock. The options are:A - systemB - local oscillator (default)C - local link

Reconfigure

7 Clear Counters Enables the clearing of the performance monitoring counters:yes : Type y to clear the counters.no (default): Type n to exit without clearing the counters.

Immediate

LineInterface Framer Slot

Controller

Received Data

Transmitted Data

LineLoopback

PayloadLoopback

DigitalLoopback

DS1-2C/2CS LIM


LIM Configuration DS1-2C/4C Links Configuration

8 Reconfigure Resets the controller with the current parameter values:yes : Type y to reconfigure the controller.no (default): Type n to exit without reconfiguring.

Immediate

LOS Defect Indicates if there is currently a loss of signal condition. Read only

OOF Defect Indicates if there is currently an out of frame condition. Alarm towards network persists >5sec.

Read only

AIS Defect Indicates if there is currently an alarm indication signal. Read only

Yellow Defect Indicates if there is currently a yellow alarm defect state. Read only

BER Defect Indicates if there is currently a bit error rate of approx. 1x10-3. Not supported. The BER threshold is not selectable.

NA

LOS Alarm Indicates if there is currently a loss of signal alarm. Read only

LOF Alarm Indicates if there is currently a loss of frame alarm. Read only

AIS Alarm Indicates if there is currently an alarm indication signal. Read only

Yellow Alarm Indicates if there is currently a yellow alarm. Read only

BER Alarm Indicates if there is currently a bit error rate alarm. (Not supported) NA

DS1 Framing Err Reports the number of DS1 framing errors. (Not supported) NA

DS1 Bit Errors Reports the number of DS1 bit errors. Read only

DS1 OOF/COFA ER Reports the number of OOF/COFA errors. (Not supported) NA

DS1 LCV Errors Reports the number of DS1 line code violation errors. Read only

Line ES Reports the number of line errored second intervals. (Not supported) NA

Line SES Reports the number of line severely errored second intervals. Read only

ES Reports the number of errored second intervals. (Not supported) NA

SES Reports the number of severely errored second intervals. Read only

AISS Reports the number of alarm indication signal second intervals. Read only

UAS Reports the number of unavailable second intervals. Read only

ExBER Reports the number of excessive bit errors. (Not supported) NA

Table 7-13 DS1-2C/4C DLIM Config/Status Parameter Definitions (Continued)



LIM Configuration E1-2C/4C Links Configuration

and

E1-2C/4C Links ConfigurationTo configure the Physical Framer, perform the following steps.

1. From root menu, select M,19 to access the DLIMs screen.

2. Select option 0 to access the E1-2C/4C DLIM Config/Status screen.

3. Select E to view the Extra Detail for entry 0, similar to the example below. Table 7-14 describe the screen parameters.

Figure 7-13 E1-2C/4C DLIM Configuration/Status Screen (M,19,0,E )

4. At the Select prompt, enter the option number for a parameter, in turn, to be configured enter the changes.

5. After making all changes for link 0, select option 8 Reconfigure and then press the Enter key.

6. At the Reconfigure (Y/N) prompt, type Y to send the changes to the LIM.

7. Select D own to proceed to the Extra Detail for the next entry to be configured.

8. Repeat step 4. through step 7. as needed for the available links.

9. When complete, select eX it twice to return to the MIB Display and Management screen.

10. Select S ave . This completes the Physical Framer configuration for the E1-2C/2S LIM.

Switch Name:Slot x SYS E1-2C/4C DLIM Config/Status New EventDetail of E1-2C/4C DLIM Config/Status entry 0

Link No : 0 14 Sio Nat'l : on Line ES : 0 Version : dual 15 Si1 Nat'l : on Line SES : 000 Loopback : none LOS Defect: no ES : 001 Framer Mod: crc mfrm OOF Defect: no SES : 002 Tx Clk Src: system AIS Defect: no AISS : 003 TS16 PayLd: no FERF Defec: no UAS : 004 Tx AIS : no BER Defect: yes05 Extract Fr: no LOS Alarm : no06 Interface : balanc 120 LOF Alarm : no07 Clear Coun: yes AIS Alarm : no08 Reconfigur: no FERF Alarm: no09 SA4 Nat'l : on BER Alarm : yes10 SA5 Nat'l : on CRC Errors: 011 SA6 Nat'l : on Frame Erro: 012 SA7 Nat'l : on FEBE Error: 013 SA8 Nat'l : on Line Code : 0Select option:Down, Enter entry number to edit, Goto row, Index search, Summary,eXit



Table 7-14 E1-2C/4C Config/Status Parameter Definitions




0 Loopback Enables/indicates the setting of diagnostic loopback. Options are:A - none (default)B - line lpbkC - payload lpbkD - digital lpbk

Note: Loopbacks cause data disruption.

Immediate

1 Framer Mod Enables/indicates the setting of the framer. The options are:A - crc mfrm (default)B - basicC - unframedD - cas

Reconfigure

2 Tx Clk Src Enables/indicates the selection of the transmit clock. Options are:A - systemB - local oscillator (default)C - local link

Reconfigure

3 TS16 Payld Enables/indicates the setting of the TS16 payload:yes : Type y to set timeslot 16 to carry payload.no (default): Type n to be able to use timeslot 16 for CAS

(Channel Associated Signaling).

Reconfigure

4 Tx AIS Enables/indicates the setting of the transmit Alarm Indication Signalling (AIS) cells.yes : Type y to enable the transmission of AIS cells.no (default): Type n to disable AIS cell transmission.

Reconfigure

5 Extract F ram e B Enables/indicates the extraction of frame bits: yes : Type y to enable the extraction of frame bits.no (default): Type n to disable frame bit extraction.Note: You should leave this option set to the default, no .

Reconfigure

6 Interface Type Enables/indicates the choice of one of two interfaces:A - balanced 120 (default)B - unbalanced 75

Reconfigure

7 Clear Counters Enables the clearing of the performance monitoring counters:yes : Type y to clear the counters.no (default): Type n to exit without clearing the counters.

Immediate

8 Reconfigure Resets the controller with the current parameter values:yes : Type y to reconfigure the controller.no (default): Type n to exit without reconfiguring.

Immediate

LineInterface Framer Slot

Controller

Received Data

Transmitted Data

LineLoopback

PayloadLoopback

DigitalLoopback

E1-2C/2CS LIM



9 SA4 Nat’l National bit SA4, transmitted in bit position 4 of Non Frame Alignment Signal (NFAS) frames.Note: Only supported with E1-2CS/4CS LIMs. Bit is fixed to On

(1) for E1-2C/4C LIMs.

Reconfigure

10 SA5 Nat’l National bit SA5, transmitted in bit position 5 of NFAS frames. Note: Only supported with E1-2CS/4CS LIMs. Bit is fixed to On


Reconfigure



Reconfigure



Reconfigure



Reconfigure

14 Sio Nat’l International bit SI0, transmitted in bit position 1 of NFAS frames. Note 1: Only supported with E1-2CS/4CS LIMs. Bit is fixed to On

(1) for E1-2C/4C LIMs.Note 2: Not applicable when using CRC Multiframe Framing.

Reconfigure

15 Si1 Nat’l International bit SI1, transmitted in bit position 1 of Frame Alignment Signal (FAS) frames.Note 1: Only supported with E1-2CS/4CS LIMs. Bit is fixed to On

(1) for E1-2C/4C LIMs.Note 2: Not applicable when using CRC Multiframe Framing.

Reconfigure


OOF Defect Indicates if there is currently an out of frame condition. Read only

AIS Defect Indicates if there is currently an alarm indication signal. Read only

FERF Defect Indicates if there is currently a FERF defect state. Read only

BER Defect Indicates if there is currently a bit error rate of approx. 1x10-3. Read only



AIS Alarm Indicates if there is currently an alarm indication signal. Read only

FERF Alarm Indicates if there is currently a FERF alarm. Read only

BER Alarm Indicates if there is currently a bit error rate alarm. Read only

CRC Errors Reports the number of CRC errors. Read only

Frame Errors Reports the number of frame errors. Read only

FEBE Error Reports the number of far end block errors. Read only

Line Code Viola Reports the number of line code violation errors. Read only

Line ES Reports the number of line errored second intervals. Read only

Line SES Reports the number of line severely errored second intervals. Read only

ES Reports the number of errored second intervals. Read only


AISS Reports the number of alarm indication signal second intervals. Read only


Table 7-14 E1-2C/4C Config/Status Parameter Definitions (Continued)



LIM Configuration DS3 or E3 LIM Configuration

.

re.

DS3 or E3 LIM ConfigurationThe procedures in this section configure the DS3 or E3 LIMs as follows:

• Define the LIM in Slot-0

• Configure PLCP Framer

Define the LIM in Slot-0

1. From the root menu, select M, 9 to access the Slot 0 Configuration/Status screen.

2. Select option 3 to access the Physical Layout screen.

3. Select G oto row and enter the number of the slot controller with its installed LIM.

4. Select E xtra detail . Table 7-15 describes the screen parameters.

5. Select option 1 DLIM Type and press Enter.

6. From the list of DLIMs displayed, select the installed DLIM by letter (DS3-2C or E3-2C)

7. Select eX it twice to return to the MIB Display and Management screen.

8. Select S ave to save the configuration change.

9. Select eX it to return to the Root Menu.This completes the Slot-0 LIM definition procedu

10. Proceed to Configure PLCP Framer next.

OXFORD: Slot 0 Physical Layout New eventDetail of Physical Layout entry 0------------------------------------------------------------------------------- Slot No : 0 Lst Chngd Link : link 140 Name : Slot 00 Lst Previous St: none Type : pcx1 DLIM Type : unknown Version : 710v14 State : active2 Reset Slot : no3 Required State : normal Changed State : no4 Associated Slot: 15 Slot Ser # : 0808050001 Slot HW Ver : 2.0b DOC Ser # : 0808050001 DOC HW Ver : 0.0a5 Slot MAC Addres: 001219ff0030 Last State Chan: 14 Jul 2008 16:33:26Select option:Down, Enter entry number to edit, Goto row, Index search, Summary,eXit



Table 7-15 Physical Layout Screen Definitions


Slot No Displays the number of the slot currently under review. Read only

0 Name Enables you to assign a significant name to the slot being reviewed. If none is to be assigned, the default is the slot number in the format Slot XX.

Immediate

Type When the slot controller has been installed, the application code has booted and is running, and the config update has been passed to the Slot-0 Controller, the Type field identifies the type of Slot Controller installed in the slot.

Read only

1 DLIM Type Specifies the LIM type from a list of possible LIMs. Immediate

Version Indicates the version of application software running on the Slot Controller.

Read only

State Indicates the current state of the slot controller. Possible states:absent : Indicates that there is no slot controller in the slot or it has lost communications.active : The full feature software has been loaded and is running.bootmode : The full feature software has not been loaded; the software may not be present or the rotary switch may be set to bootmode.

Read only

2 Reset Slot Enables you to reset the slot. This is a warm restart of the slot, which is necessary when certain configuration changes are made to the slot such as a change in its IP address.yes : Type y to reset the slot.no : (default) Type n to exit this option without a slot reset.

Immediate

3 Required State Enables you to set the required state of the slot. Options are:A - normal : (default) Normal state required for running.B - shutdown : Stops the slot from running.C - main : not supportedD - shadow : not supported

Immediate

Changed State Reports if a state change has taken place since the last time the Slot Controller was put into operation.

Read only

4 Associated Slot Not supported. N/A

Slot Ser # Reports the slot serial number assigned at the factory. Read only

Slot HW Ver Reports the slot hardware version assigned at the factory. Read only

DOC Ser # Reports the DOC serial number assigned at the factory. Read only

DOC HW Ver Reports the DOC hardware version assigned at the factory. Read only

5 Slot MAC Addres Reports the slot MAC address assigned at the factory. Immediate



t

en.

the

Configure PLCP Framer

1. From the root menu, select M,39 to access the PDH Configuration/Status screen.

2. Select option 0 for the PLCP Configuration/Status screen.

3. Select E (xtra Detail) to view the detail screen, similar to the example below. Table 7-16 describe the screen parameters.

4. Select option 2 Physical Framer.

5. Select the appropriate framer mode type, as follows:

A- none

B - ds3 for DS3-2C LIMs

C - e3 for E3-2C LIMs

6. When the PLCP Config/Status screen appears, select option 3 Cell Delin.

7. Select the appropriate delineation type, as follows:

For DS3-2C LIMs, either:

A - hec based delineation

C - ds3 PLCP for DS3-2C LIMs. (Required to transmit the 125µs bit clock.)

For E3-2C LIMs, either:

A - hec based delineation (recommended for most applications)

E - e3 g751 PLCP

8. Select the Scrambler . The default is set to A - enabled . Note that the Scrambler setting athe LIM must match the setting at the attached device.

9. Select Reconfigure and press Enter. At the prompt, type y to save the values to the LIM.

10. Select D own to advance to the detail of PLCP Configuration/Status entry 1 (Link-1) scre

11. Select eXit twice to return to the MIB Display and Management screen. This completesPLCP Framer configuration.

OXFORD: Slot 0 PLCP Configuration/Status New EventDetail of PLCP Configuration/Status entry 0------------------------------------------------------------------------------- Link # : 0 RX Clock : up FE-ES : 000 Link Enabl: enabled Txed Cells: 0 FE-SES : 001 Link Statu: ignored Rxed Cells: 0 FE-UAS : 0 Link State: up HCS Errors: 002 Phy Framer: e3 LOCD Defec: no03 Cell Delin: e3 g751 PL Yellow Def: no04 Scrambler : enabled LOF Defect: no05 XOR w/55H : enabled LOCD Alarm: no06 SMDS Mode : disabled Yellow Ala: no07 Idle Cell : unassigned LOF Alarm : no08 Loopback : none Frame Errs: 009 Clear Coun: no BIP8 Errs : 010 Reconfigur: no FEBE Errs : 011 Lpbk Timeo: 1 ES : 0 Chip Type : unknown SES : 0 TX Clock : up UAS : 0Select option:Down, Enter entry number to edit, Goto row, Index search, Summary,eXit



Table 7-16 PLCP Configuration/Status Parameter Definitions


Link # Displays the link number associated with the extra detail shown. Read only

0 Link Enabl Sets/indicates the link as enabled or disabled. The options are:A - enabled (default)B - disabled

Immediate

1 Link Statu Sets/indicates the status of the control line, whether to be ignored or responded to. Determines whether or not the PLCP chip will use the link state as a condition for attempting to transmit or receive data. The options are:A - ignored (default)B - processed

Reconfigure

Link State Indicates the current state of the link as:up : The link is operational.down: The link is non-operational.stop : The link has been disabled.off : The link control lines are down.

Read only

2 Phy Framer Enables the selection of the physical frame mode type for the ds3 and e3 LIMs. The options are:A - none (default): When the installed LIM is not a DS3 or E3.B - ds3C - e3

Reconfigure

3 Cell Delin Enables/indicates the mode setting for the PLCP chip. This field sets the actual framing mode is set. The options are:A - ds3 PLCPB - e3 g751 PLCP

Reconfigure

4 Scrambler Sets/indicates the status of the scrambler. The scrambler is self-

synchronizing and uses a polynomial of x43+1 to scramble the ATM cell payload. If enabled, it performs scrambling for both transmission and reception. It may be used for both PLCP and non-PLCP based transmission systems. The options are:A - enable (default) or B - disabled

Reconfigure

5 XOR w/55H Enables/indicates the exclusive ORing of a fixed 0x55 pattern with the data in the header field of the ATM cell header before transmission to assist with cell delineation. Options are:A - enable (default) or B - disabled

Reconfigure

6 SMDS Mode Sets/indicates the Switched Multimegabit Data Service mode on or off. The options are:A - enable (default) or B - disabled

Reconfigure

7 Idle Cell Sets/indicates which type of cell is to be inserted when there are no cells pending for transmission. The options are:A - unassigned (default): (CLP=0, used according to ATM Forum Specification)B - idle : (CLP=1, used according to ITU Specification).

Reconfigure



8 Loopback Enables/indicates the setting of loopbacks for testing. Options are:A - none (default)B - diagnostic lpbkC - line lpbkD - payload lpbkE - cell lpbk.

Immediate(Loopbacks cause data disruption)

9 Clear Coun Enables the clearing of the performance monitoring counters:yes : Type y to clear the counters.no : (default) Type n to exit without clearing the counters.

Immediate

10 Reconfigur Resets the controller with the current parameter values:yes : Type y to reconfigure the controller.no : (default) Type n to exit without changes.

Immediate

11 Lpbk Timeo Sets the length of time a loopback will stay up before an automatic reset. Range is 1 - 604800 minutes (default = 1).

Reconfigure

Chip Type Indicates the type of framer detected on the controller. You should select the suni q

Reconfigure

TX Clock Indicates whether the transmit clock is present at the chip or absent. Displays up or down , respectively.

Read only

RX Clock Indicates whether the receive clock is present at the chip or absent. Displays up or down , respectively.

Read only

Txed Cells Reports the number of cells that have been sent to the TX FIFO buffer. Does not count idle, unassigned, or errored cells.

Read only

Rxed Cells Reports the number of cells that have been received at the RX FIFO buffer. Does not count idle, unassigned, or errored cells.

Read only

HCS Errors Reports the number of cells with bad header checksum sequences that have been received on the link.

Read only

LOCD Defec Indicates if there is currently a loss of cell delineation condition. Read only

Yellow Def Indicates if there is currently a PLCP yellow alarm defect state. This is triggered when ten or more consecutive frames are received with the yellow bit set in the PLCP framer.

Read only

LOF Defect Indicates if there is a PLCP loss of frame defect state condition. Read only

Table 7-16 PLCP Configuration/Status Parameter Definitions (Continued)


TPOS/TD

RPOS/RD

TRANSMIT FRAMER

RECEIVE FRAMER

LINE LOOPBACK

DIAGNOSTIC LOOPBACK

PAYLOAD LOOPBACK

TRANSMITCELLPROCESSOR

RECEIVECELLPROCESSOR

TRANSMITCELLFIFO

RECEIVECELLFIFO

CELL LOOPBACK

LOOPBACK TEST MODE



LOCD Alarm Indicates if there is a loss of cell delineation alarm. Read only

Yellow Ala Indicates a yellow alarm, that is, the yellow bit position in the path status octet has been detected. It is declared for either a DS3 LOF or a DS3 RX AIS. An alarm trap is sent to the manager.

Read only


Frame Errs Reports the number of PLCP framing errors detected. Read only

BIP8 Errs Reports the number of PLCP bit interleaved parity (BIP) errors that have been detected by the PLCP module.

Read only

FEBE Errs Reports the number of far-end block errors detected in each frame by the PLCP module.

Read only

ES Reports the number of errored second intervals. Read only



FE-ES Reports the number of far-end errored second intervals. Read only

FE-SES Reports the number of far-end severely errored second intervals. Read only

FE-UAS Reports the number of far-end unavailable second intervals. Read only

Table 7-16 PLCP Configuration/Status Parameter Definitions (Continued)



LIM Configuration DS3-2C LIM Configuration

DS3-2C LIM ConfigurationConfiguring the Physical Framer for the DS3-2C LIM requires the following procedures:

• Define DS3-2C Framer Mode

• Configure DS3-2C DLIM

Define DS3-2C Framer Mode

1. From the root menu, select M,39,1 to access the DS3 Configuration/Status screen.

2. Select E xtra detail . An example screen is shown below. Screen parameters are defined in Table 7-17.

3. Select the Framer Mod and press Enter.

4. Set the framer mode type to A - c bit for ATM.

5. Select Reconfigur and press Enter.

6. At the Reconfigur prompt, enter Y to send the changes to the LIM.

7. Select D own to transition to the Detail of DS3 Configuration/Status entry 1 screen.

8. Repeat step 3. through step 6. for Detail of DS3 Configuration/Status entry 1.


10. Select S ave .

11. Proceed to Configure DS3-2C DLIM on page 7-45.

Switch Name:Slot 3 SYS DS3 Configuration/Status SW VersionDetail of DS3 Configuration/Status entry 0

Table Vali: yes AIS Defect: no FE-ES : 4 Link # : 0 Yellow Def: no FE-SES : 00 Framer Mod: c bit BER Defect: no FE-UAS : 01 Tx AIS : no LOS Alarm : no2 Clear Coun: no LOF Alarm : no3 Reconfigur: no AIS Alarm : no Rcv Frame : c bit Yellow Ala: no Rcv Idle S: no BER Alarm : no Tx FEAC Co: none Line ES : 152 Lcvs : 401 Line SES : 148 Frame Errs: 450 ES(P-bit) : 5 Parity Err: 17 ES(C-bit) : 6 C-bit Pari: 9538 SES(P-bit): 0 FEBE Error: 21 SES(C-bit): 6 LOS Defect: no AISS : 0 OOF Defect: no UAS : 183Select option:Down, Enter entry number to edit, Goto row, Index search, Summary,eXit



Table 7-17 DS3 Configuration/Status Screen Parameter Definitions


Table Vali Indicates table validity. Read only

Link # Indicates the link number currently under review. Read only0 Framer Mod Enables/indicates the setting of framer mode type. Options are:

A - c bit (default): Select this option for ATM.B - m23 : This option is only used for T3 multiplexers.

Reconfigure

1 Tx AIS Enables/indicates the setting of the transmit Alarm Indication Signalling (AIS) cells.yes : Type y to enable the transmission of AIS cells.no (default):Type n to disable AIS cell transmission.

Reconfigure

2 Clear Coun Enables the clearing of the performance monitoring counters:yes : Type y to clear the counters.no (default):Type n to exit without clearing the counters.

Immediate

3 Reconfigur Resets the controller with the current parameter values:yes : Type y to reconfigure the controller

no (default): Type n to exit without reconfiguring the controller.

Immediate

Rcv Frame Indicates the type of frame being received, c bit or m23 . Read only

Rcv Idle S Indicates receiving idle cells within the last second. Read onlyTx FEAC Co Indicates a far-end alarm condition. Read onlyLcvs Reports the number of line code violations. Read only

Frame Errs Reports the number of frame errors. Read onlyParity Err Reports the number of parity errors. Read onlyC-bit Pari Reports the number of C-bit parity errors. Read only

FEBE Error Reports the number of far-end block errors. Read onlyLOS Defect Indicates if there is currently a loss of signal condition. Read onlyOOF Defect Indicates if there is currently an out of frame condition. Read only

AIS Defect Indicates if there is currently an alarm indication signal. Read onlyYellow Def Indicates if there is currently a yellow alarm defect state. Read onlyBER Defect Indicates if there is currently a bit error rate of approx. 1x10-3. Read only

LOS Alarm Indicates if there is currently a loss of signal alarm. Read onlyLOF Alarm Indicates if there is currently a loss of frame alarm. Read onlyAIS Alarm Indicates if there is currently an alarm indication signal. Read only

Yellow Ala Indicates if there is a yellow alarm. When present, indicates that the yellow bit position in the path status octet has been detected. It is declared for either a DS3 LOF or a DS3 RX AIS. An alarm trap is sent to the manager.

Read only

BER Alarm Indicates if there is currently a bit error rate alarm. Read onlyLine ES Reports the number of line errored second intervals. Read only

Line SES Reports the number of line severely errored second intervals. Read onlyES (P-bit) Reports the number of P-bit errored second intervals. Read onlyES (C-bit) Reports the number of C-bit errored second intervals. Read only

SES (P-bit) Reports the number of P-bit severely errored second intervals. Read onlySES (C-bit) Reports the number of C-bit severely errored second intervals. Read onlyAISS Reports the number of alarm indication signal second intervals. Read only

UAS Reports the number of unavailable second intervals. Read onlyFE-ES Reports the number of far-end errored second intervals. Read onlyFE-SES Reports the number of far-end severely errored second intervals. Read only

FE-UAS Reports the number of far-end unavailable second intervals. Read only



wn

enter

.

Configure DS3-2C DLIM

1. From the root menu, select M,19,3 to access the DS3-2C DLIM Config/Status screen.

2. Select E xtra detail . The Detail of DS3-2C DLIM Config/Status entry 0 appears as shobelow. The screen parameters are described in Table 7-18.

3. At the Select prompt, enter the option number of the item or items to be configured andthe configuration changes.

4. If making a change, select Reconfigure and press Enter.

5. At the Reconfigure prompt, enter Y to send the changes to the LIM.

6. Select D own to transition to the Detail of DS3-2C DLIM Config/Status entry 1 screen.

7. Repeat step 3. through step 5. for Detail of DS3-2C DLIM Config/Status entry 1.


9. Select S ave . This completes the configuration of the Physical Framer for the DS3-2C LIM

SWITCH name:Slot x SYS DS3-2C DLIM Config/Status SW VersionDetail of DS3-2C DLIM Config/Status entry 0

Link No : 00 Loopback : none Version : ds3 2c LIM OK : yes1 TX LBO : short2 Tx Clk Src : system LOS Defect : no LOS Alarm : no3 Reconfigure : no




Table 7-18 DS3-2C DLIM Config/Status Parameter Definitions



0 Loopback Enables/indicates the setting of a diagnostic loopback. Options are:A - none (default)B - line lpbkC - local lpbk

Note: Loopbacks cause data disruption.

Immediate


LIM OK Indicates the health of the LIM. Read only

1 TX LBO Enables/indicates the setting of the line build out. The options are:A - short (default): Select this option for 50-feet or less.B - long : Select this option for 50 to 450-feet.

Reconfigure

2 TX Clk Src Enables/indicates the setting of the TX clock source. Options are:A - systemB - local oscillator (default)C - link0 plcpD - link1 plcp

Reconfigure



3 Reconfigure Resets the controller with the current parameter values:yes : Type y to reconfigure the controllerno (default): Type n to exit without reconfiguring the controller.

Immediate

LineInterface

SlotController

Received Data

Transmitted Data

LocalLoopback

DS3-2C LIM

LineLoopback


LIM Configuration E3-2C LIM Configuration

, as

n)

E3-2C LIM Configuration

Configuring the Physical Framer for the E3-2C LIM requires the following procedures:

• Define the E3-2C Framer Mode

• Configure E3-2C DLIM

Define the E3-2C Framer Mode

1. From the root menu, select M,39,2 to access the E3 Configuration/Status screen.

2. Select Extra detail . The Detail of E3 Configuration/Status entry 0 screen appearsshown below. The screen parameters are described in Table 7-19.

3. Select the Framer Mod option and press Enter.

4. Set the appropriate framer mode type to one of the following:

A - g832 (when PLCP Configuration/Status, Cell Delin is hec based delineatio

B - g751 (when PLCP Configuration/Status, Cell Delin is e3 g751 PLCP)

5. Select Reconfigur and press Enter.

6. At the Reconfigur prompt, enter Y to send the changes to the LIM.

7. Select D own to transition to the Detail of E3 Configuration/Status entry 1 menu screen.

8. Repeat step 3. through step 6. for Detail of E3 Configuration/Status entry 1.


10. Select S ave .

11. Proceed to Configure E3-2C DLIM on page 7-49.

Switch Name:Slot x SYS E3 Configuration/Status SW VersionDetail of E3 Configuration/Status entry 0

Table Vali: no LOS Defect: no Rx Trail T: Link # : 0 OOF Defect: no Rx Trail I: no0 Framer Mod: g832 AIS Defect: no Rx Trail I: no1 Clear Coun: yes FERF Defec: no Rx Pyld La: no2 Reconfigur: no BER Defect: no Rx Pyld La: no3 Traceable : yes LOS Alarm : no4 Pyld Label: atm LOF Alarm : no5 Tx Trail T: length 16 AIS Alarm : no6 Tx Trl Trc: 2020202020 FERF Alarm: no7 Tx Trl Trc: 2020202020 BER Alarm : no8 Rx Exp Tr : 2020202020 Line ES : 09 Rx Exp Tr : 2020202020 Line SES : 0 Framing Er: 0 ES : 0 Lcvs : 0 SES : 0 Parity Err: 0 AISS : 0 FEBE Errs : 0 UAS : 0Select option:Down, Enter entry number to edit, Goto row, Index search, Summary,eXit



Table 7-19 E3 Configuration/Status Menu & Definitions


Table Vali Indicates table validity. Read only

Link # Indicates the link number currently under review. Read only0 Framer Mod Enables/indicates the setting of the framer mode type. Options are:

A - g832 (default)B - g751

Reconfigure

1 Clear Coun Enables the clearing of the performance monitoring counters:yes: Type y to clear the counters.no (default):Type n to exit without clearing the counters.

Immediate

2 Reconfigur Resets the controller with the current parameter values:yes: Type y to reconfigure the controller.no (default):Type n to exit without reconfiguring the controller.

Immediate

3 Traceable Enables/indicates signal is traceable to the pri ref clk (g832 only):yes: Type y to set to the primary reference clock.no (default):Type n to not set to the primary reference clock.

Reconfigure

4 Pyld Label Enables/indicates the payload label is set as:A - atm (default)

Reconfigure

5 Tx Trail T Enables/indicates the Tx Trail Trace length is set to:A - length 16 (g832 only)

Reconfigure

6 Tx Trail Trc Enables/indicates the Tx Trail Trc Upper Half (G832 only) is set. Reconfigure7 Tx Trail Trc Enables/indicates the Tx Trail Trc Lower Half (G832 only) is set. Reconfigure

8 Rx Exp Tr Enables/indicates the Rx Exp Tr Trc Upper Half (G832 only) is set. Reconfigure9 Rx Exp Tr Enables/indicates the Rx Exp Tr Trc Lower Half (G832 only) is set. ReconfigureFraming ER Reports the number of framing errors detected. Read only

Lcvs Reports the number of line code violations detected. Read onlyParity Err Reports the number of parity bit errors detected. Read onlyFEBE Errs Reports the number of far-end block errors detected. Read only

LOS Defect Indicates if there is currently a loss of signal condition. Read onlyOOF Defect Indicates if there is currently an out of frame condition. Read onlyAIS Defect Indicates if there is currently an alarm indication signal. Read only

FERF Defec Indicates if there is currently a FERF condition. Read onlyBER Defect Indicates if there is currently a bit error rate condition. Read onlyLOS Alarm Indicates if there is currently a loss of signal alarm. Read only

LOF Alarm Indicates if there is currently a loss of frame alarm. Read onlyAIS Alarm Indicates if there is currently an alarm indication signal. Read onlyFERF Alarm Indicates if there is currently a FERF alarm. Read only

BER Alarm Indicates if there is currently a bit error rate alarm. Read onlyLine ES Reports the number of line errored second intervals. Read onlyLine SES Reports the number of line severely errored second intervals. Read only

ES Reports the number of errored second intervals. Read onlySES Reports the number of severely errored second intervals. Read onlyAISS Reports the number of alarm indication signal second intervals. Read only

UAS Reports the number of unavailable second intervals. Read onlyRx Trail T Reports the last received trail trace message. Read only

Rx Trail I Indicates a received trace id mismatch. Read onlyRx Trail I Indicates an unstable received trace id. Read onlyRx Pyld La Indicates a received payload type label mismatch. Read only

Rx Pyld La Indicates an unstable received payload type label. Read only



enter

Configure E3-2C DLIM

1. From the root menu, select M,19,4 to access the E3-2C DLIM Config/Status screen.

2. Select E xtra detail to view the parameters as shown in the example below. Table 7-20 describes the screen parameters.

3. At the Select prompt, enter the option number of the item or items to be configured and the configuration changes.

4. If making a change, select Reconfigure and press Enter.

5. At the Reconfigure prompt, enter Y to send the changes to the LIM.

6. Select D own to transition to the Detail of E3-2C DLIM Config/Status entry 1 screen.

7. Repeat step 3. through step 5. for Detail of E3-2C DLIM Config/Status entry 1.


9. Select S ave . This completes configuring the Physical Framer for the E3-2C LIM.

.

Switch Name:Slot x SYS E3-2C DLIM Config/Status New EventDetail of E3-2C DLIM Config/Status entry 0

Link No : 0 Version : e3 2c LIM OK : no0 Rx EQ Select : auto1 Loopback LIU : none2 Tx AIS : no3 Timing Reference : system LOS Defect : no LOS Alarm : no4 Reconfigure : no




Table 7-20 E3-2C DLIM Config/Status Screen & Definitions




LIM OK Indicates the health of the LIM. Read only

0 Rx EQ Select Enables/indicates the selection of the receive equalization as:A - auto (default)B - set 0 to 3p5 dbC - set 2p6 to 8 dbD - set 6 to 9p9 dbE - set 8p6 to 13p2 db

Reconfigure

1 Loopback LIU Enables/indicates the setting of a diagnostic loopback. Options are:A - none (default)B - line lpbk C - local lpbk

Immediate(Loopbacks cause data disruption.)

2 TX AIS Enables/indicates the setting of the transmit Alarm Indication Signalling (AIS) cells.yes : Type y to enable the transmission of AIS cells.no (default): Type n to disable AIS cell transmission.

Reconfigure

3 Timing Reference

Enables/indicates the setting of the timing reference source. The options are:A - systemB - local oscillator (default)C - link0 plcpD - link1 plcp

Reconfigure



4 Reconfigure Resets the controller with the current parameter values:yes : Type y to reconfigure the controller.no (default): Type n to exit without reconfiguring the controller.

Immediate

LineInterface

SlotController

Received Data

Transmitted Data

LocalLoopback

E3-2C LIM

LineLoopback


LIM Configuration IMA LIMs

ion. ith

from up. on. M

arly

MA nts M ed

uits red as

y

MA its

a IMA

d for ve for

IMA LIMsTwo LIMs support ATM Inverse Multiplexing with the PCX or PCL slot controller:

• DSX1-IMA and E1 IMA (with the PCX)

• DSX1-IMA+ and E1 IMA+ (with the PCL)

The “IMA” and the “IMA+ LIMs” operate the same and are discussed as IMA LIMs in this sectEach IMA LIM provides a 16-link physical DS1 or E1 interface for its controller and complies wstandard DS1 or E1 physical-layer interface specifications. The IMA LIMs provide inverse multiplexing of an ATM cell stream over multiple physical links, and reassemble the originalstream at the far end from these links. In the transmit direction the ATM cell stream receivedthe ATM layer is uniformly distributed on a cell-by-cell basis across multiple links in IMA GroThe uniform distribution of cells to the IMA links is performed on a cyclical, "round-robin" fashiIn the receive direction, the cells are reassembled from the multiple links into the original ATlayer stream.

IMA Configuration OverviewIn configuring IMA LIMs, the difference between Physical Links and ATM Ports should be cleunderstood, as described below.

Physical Links

Each IMA LIM carries 16 physical (PHY) links which are the physical link connections to the ILIM front panel (numbers 0 through 15). All PHY links may be configured as either componeof IMA groups or as independent DS1, or E1, ATM UNI links. Assignment of PHY links to ATports is done automatically. By default, a PHY link is assigned to the corresponding numberATM port, e.g., link 0 to ATM port 0, etc.

ATM Ports

An ATM port is a source or destination logical port within the Xedge switch to which ATM circare addressed. The ATM ports reside on the PCx or PCL slot controller and may be configueither individual UNIs or as grouped UNIs.

• NNI ATM ports support PVC, SVC and SPVC (dynamically rerouted) connections.

• UNI ATM ports support PVC and SPVC connections.

IMA Groups

Referred to as “Group Index” in the IMA MIB, an IMA group is a collection of physical links bundled or grouped together and assigned to an ATM Port. The IMA Groups are identified bnumbers 1 through 8, and should be assigned as follows:

• Numbers 1 - 4 assigned to IMA Groups composed of physical links 0 - 7

• Numbers 5 - 8 assigned to IMA Groups composed of physical links 8 - 15.

Assignment of an ATM Port to an IMA group is done automatically by the switch code. The IGroup is mapped to the ATM Port that corresponds to the lowest numbered physical link in group (e.g., a group made up of links 2, 5 and 7 would be assigned to ATM Port 2).

While an IMA Group may be composed of up to 8 physical links, all physical links making upspecific IMA Group must be from either the physical-link set 0-7 or the physical-link set 8-15. Groups of more than 8 physical links are not supported.

Note Version 7.X supports both IMA and non-IMA modes. At this time, IMA LIMS are not fully implementethe PCx, hence the information in this section is subject to change. Contact your Xedge representatidetails and availability.


LIM Configuration IMA LIMs

up.

col l used Two

lls

le ot

dle ot

IMA Group BandwidthThe controller provisions IMA Bandwidth automatically when links are assigned to an IMA gro

• For T1 IMA, each T1 is assigned 3592 cps bandwidth on a per DS1 link basis.

• For E1 IMA, each E1 is assigned 4490 cps bandwidth on a per E1 link basis.

The IMA LIMs carry a bandwidth overload that is the result of two tasks: the IMA Control Proto(ICP) and the Common Transmit Clock (CTC). For every 128 cells, the IMA issues an ICP celto manage the IMA group. In addition, for every 2048 cells, the IMA sends out a Stuff Cell. (Stuff Cells equal a Stuff Cell Event).

Stuff Cells allow matching the different cell rates on links in an IMA group. ICP and Stuff Cemust be subtracted from the actual bandwidth that is available on each link.

• For a single T1, without the IMA protocol enabled, IMA ICP cells are replaced by idATM cells, so the single T1 continues to use the same bandwidth, 3592.cps, and n3622cps as you might expect when the IMA ICP cells are no longer in use.

• For a single E1, without the IMA protocol enabled, IMA ICP cells are replaced by iATM cells, so the single E1 continues to use the same bandwidth, 4490 cps, and n4528cps as you might expect when the IMA ICP cells are no longer in use.

Figure 7-14 Example IMA Groups

Example A Two 8-Link IMA Groups

Example B Four 4-Link IMA Groups

Example C Individual DS1/E1 ATM UNIs and IMA Groups (dotted lines)


LIM Configuration E1 IMA Configuration

link

o

the

5) he

E1 IMA Configuration

By default, the 16 E1-IMA physical links are disabled and inactive. To enable each link, eachmust first be assigned to an IMA Group and made active, as described below.

1. Establish a Telnet session to the slot controller for the E1-IMA LIM.

2. From the root menu, select M,70 to access the LIM and Link information screen, similar tthe example below.

3. Select 2 to access the E1 LIM screen, similar to the example below.

4. From the E1 LIM screen, select 3 to access the E1 Link Configuration screen, then select Extra detail screen. An example configuration screen for link 0 is shown below.

5. Change the parameters for link 0 as required. Repeat for all remaining links (1 through 1using the Down/Up commands. Refer to Table 7-21 as needed. When complete, advance to tIMA Configuration procedure later in this chapter.

Switch Name: Slot X SYS LIM and Link Information SW Version

LIM ID: elim e1 16 port LIM Hardware Version: 2 LIM Boot Version: A- LIM Firmware Version: elf1.3 LIM Software Version: e1_ds1_45 Number of Ports: 16 LIM Status: operational0 Common LIM1 SONET/SDH LIM2 E1 LIM3 DS1 LIM


Switch Name: Slot X SYS E1 LIM SW Version

0 E1 Diagnostic Page1 E1 Performance Monitoring Page2 E1 Alarms Page3 E1 Link Configuration Page


Switch Name: Slot X SYS E1 Link Configuration Page SW VersionDetail of E1 Link Configuration Page entry 0

Link # : 000 Link Config : enabled Link Status : port up01 Tx Clk Source : master timing02 XOR w/55H : enabled03 Scramble Cell Payload : scrambled04 Framing Mode : crc multiframe05 Sa4 Spare Bit : set06 Sa5 Spare Bit : set07 Sa6 Spare Bit : set08 Sa7 Spare Bit : set09 Sa8 Spare Bit : set10 Si0 International Bit : set11 Si1 International Bit : set



LIM Configuration E1 IMA Configuration

Table 7-21 E1 IMA LIM Configuration Parameters

Link # Read-only display of the physical link number, 0 through 15.Link Config Enables or disables the link. (Immediate effect)

The current status of the link is indicated by the Link Status parameter. Options are: Enabled or Disabled . When a LIM is used in an IMA group, Link Config will be set to enable automatically. Note that a link can not be disabled if the Row Status parameter is set to active (refer to paragraphs on IMA Configuration later in this section).

Link Status Indicates the current status of the link. (Immediate effect)disabled indicates the port is disabled at the request of the user by the Link Config parameter.port up indicates the port is enabled by the user and no alarms are detected in the receive data stream.port down indicates the user has enabled the link but one or more alarms are detected in the receive data stream.

Tx Clk Source Selects the timing source used to drive the transmit data line for this link. (Immediate effect)master-timing - use the master transmit timing source that is set in LIM Timing and the Slot 0 System Timing. (Default setting)loop-timing - use the extracted clock from the receive data stream as the transmit source.

XOR w/55H Adds the coset polynomial to the HCS octet prior to insertion in the transmit stream. (Immediate effect). Options are: Enabled or Disabled .

Scramble Cell PayloadScrambles the 48 octet info field of ATM cells. Also forces the receiver to expect the cell payload to be scrambled in the same manner. (Immediate effect) Options are Scrambled and Not Scrambled.

Framing Mode Selects the framing mode used. (Immediate effect) Options are basic and crc multiframe .

Sa4 Spare Bit Selects the Sa4 National Spare Bit used in the E1 Framing. (Immediate effect)Options are Set and Cleared.





Si0 International Bit Selects the Si0 International Bit used in the E1 Framing. (Immediate effect)Options are Set and Cleared.

Si1 International Bit Selects the Si1 International Bit used in the E1 Framing. (Immediate effect)Options are Set and Cleared.


LIM Configuration DSX-1 IMA LIM Configuration

ach

r

ct

5) he

DSX-1 IMA LIM ConfigurationBy default, the 16 DSX1-IMA physical links are disabled and inactive. To enable each link, elink must first be assigned to an IMA Group and made active, as described below.

1. Establish a Telnet session to the slot controller for the DSX1-IMA LIM.

2. From the root menu, select M,70,0,0 to view the E-Series LIM information screen, similato the example below.

3. From the root menu, select M,70,3 to access the DS1 LIM screen, as shown below.

4. From the DS1 LIM screen, select option 3 to access the DS1 Link Configuration, then selethe Extra detail screen. An example Extra Detail screen of entry 0 is shown below.

5. Change the parameters for link 0 as required. Repeat for all remaining links (1 through 1using the Down/Up commands. Refer to Table 7-22 as needed. When complete, advance to tIMA Configuration procedure later in this chapter.

Switch Name: Slot X SYS E-Series LIM Information SW Version

LIM Location: 1m1si LIM ID: dlim Hardware version: 2 Boot Version: Firmware Version: Number of Ports: 2 LIM Status: operational LIM ID on slot0 23

Select option:Enter entry number oto edit, Goto row, Index search, Summary eXit

Switch Name: Slot X SYS DS1 LIM SW Version

0 DS1 Diagnostic Page1 DS1 Performance Monitoring Page2 DS1 Alarms Page3 DS1 Link Configuration Page


Switch Name: Slot X SYS DS1 Link Configuration Page SW VersionDetail of DS1 Link Configuration Page entry 0

Link # : 00 Link Config : enabled Link Status : port up1 Tx Clk Source : master timing2 XOR w/55H : enabled3 Scr Cell Payld : scrambled4 Framing Mode : esf5 Line Code : b8zs6 Line Length : feet 0 to 110



LIM Configuration DSX-1 IMA LIM Configuration

Table 7-22 DS1 IMA Configuration Parameters

Link # Displays the physical link number, 0 through 15. (Read only)Link Config Enables or disables the link. (Immediate effect)

The current status of the link is indicated by the Link Status parameter. Options are: Enabled or Disabled . When a LIM is used in an IMA group, Link Config will be set to enable automatically. Note that a link can not be disabled if the Row Status parameter is set to active (refer to paragraphs on IMA Configuration later in this section).

Link Status Indicates the current status of the link. (Read only)disabled indicates the port is disabled at the request of the user by the Link Config parameter.port up indicates the port is enabled by the user and no alarms are detected in the receive data stream.port down indicates the user has enabled the link but one or more alarms are detected in the receive data stream.

Tx Clk Source Selects the timing source to used to drive the transmit data line for this link.master-timing will use the master transmit timing source that is set in LIM Timing and the Slot 0 System Timing (default setting).loop-timing will use the extracted clock from the receive data stream as the transmit timing source.

XOR w/55H Adds the coset polynomial to the HCS octet prior to insertion in the transmit stream. (Immediate effect) Options are Enabled or Disabled.

Scr Cell Payld Scrambles the 48 octet info field of ATM cells. Also forces the receiver to expect the cell payload to be scrambled in the same manner. (Immediate effect)Options are Scrambled and Not Scrambled.

Framing Mode Selects the framing mode used. (Immediate effect)Options are: sf (Super Frame mode) or esf Extended Super Frame mode)

Line Code Allows selection of the DS1 line coding. (Immediate effect)Options are: ami (alternate mark invert) or b8zs (binary 8 zero substitution)Note: ami line coding is not recommended for use with ATM interfaces. Idle cells and IMA ICP cells will produce excessive zeros (EXZ) indications per the ANSI T1.231-1997 specification. One or more EXZ per second causes an Errored Second. 1544 or more EXZ's per second will generate a Severely Errored Second.

Line Length Selects the length of cable that DS1 LIM will drive. (Immediate effect)Options are:feet-0-to-110feet-110-to-220feet-220-to-330feet-330-to-440feet-440-to-550feet-550-to-655


LIM Configuration IMA Configuration

to

MA

the

IMA Configuration

Once the specific DS1 IMA or E1 LIM has been configured, perform the following procedureconfigure the IMA features. This section applies to both the E1-IMA and DSX1-IMA LIM.

1. At the root menu, select M,97 to access the IMA screen, similar to the example below.

2. From the IMA screen, select option 1 to access the IMA Link Table, then select the Extra Detail screen. An example Extra Detail screen of entry 0 is shown below. Refer to Table 7-23 for a description of parameters as needed.

3. You will now assign each physical link you are using in IMA mode (0 through 15) to an IGroup (1 through 8). From the IMA Link Table, select Group Index.

4. Use the Down and Up options to sequence through each physical link. The physical linknumber (0 through 15) is displayed by the Link Index parameter.

• For links 0 - 7, the valid Group Indices are 1 - 4.

• For links 8 - 15, the valid Group indices are 5 - 8.

Note For Inverse Multiplexing and IMA Groups guidelines, refer to IMA Configuration Overview in this chapter.

5. Now select Row Status for each link assigned to an IMA Group (0 through 15) and set field to active . Use the Down and Up options to sequence through each link.

6. When complete, proceed to step 7.

Switch Name: Slot X SYS IMA SW Version

Num IMA Groups: 20 IMA Group Table1 IMA Link Table


Switch Name: Slot X SYS IMA Link Table SW VersionDetail of IMA Link Table entry 0

Link Index : 0 FE Unavail Secs: 00 Row Status : notInService NE Tx Unusbl Se: 21 Group Index : 1 NE Rx Unusbl Se: 5 NE Tx State : active FE Tx Unusbl Se: 1 NE Rx State : unusableFailed FE Rx Unusbl Se: 22 FE Tx State : active NE Tx Failures : 0 FE Rx State : active NE Rx Failures : 0 NE Rx Fail Stat: imaLinkFailure Rx Test Pattern: 0 FE Rx Fail Stat: noFailure Test Proc Statu: disabled Tx LID : 0 Rx LID : 4 Relative Delay : 117 IMA Violations : 0 NE Sev Err Secs: 5 FE Sev Err Secs: 3 NE Unavail Secs: 364877Select option:Down, Enter entry number to edit, Goto row, Index search, Summary,eXit



6.001

le or the

Table 7-23 IMA Link Table Parameters

Link Index Displays the physical link number, 0 through 15. (Read only)

Row Status Options are active and notInService (Immediate effect)No other Row Status options are supported.Row Status can only be set to active when a Group Index is selected (1-8).Row Status can only be changed when the corresponding Group Index is set to notInService .

Group Index A unique value for the IMA Group. (Immediate effect)Valid values are 1 through 8. To change the Group Index, Row Status must be set to notInService .Group Index 1-4 can only be used for physical links 0-7. Group Index 5-8 can only be used for physical links 8-15.

Note: The system will prompt with [0-4294967295]. Disregard those values and only use the valid values 1 through 8.

NE Tx State Read-only display of the current state of the near-end transmit link. (See Note 1 below)

NE Rx State Read-only display of the current state of the near-end receive link.(See Note 1 below)

FE Tx State Read-only display of the current state of the far-end transmit link as reported via ICP cells. (See Note 1 below)

FE Rx State Read-only display of the current state of the far-end receive link as reported via ICP cells. (See Note 1 below)

NE Rx Fail Stat Read-only display of the current link failure status of the near-end receive link.(See Note 2 below)

FE Rx Fail Stat Read-only display of the current link failure status of the far-end receive link as reported via ICP cells. (See Note 2 below)

Note NOTE 1: For NE Tx/Rx State and FE Tx/Rx State, the status messages are:The current state of the far-end receive link as reported via ICP cells. Status messages are: notInGroup, unusableNoGivenReason, unusableFault, unusableMisconnected, unusableInhibited, unusableFailed, usable and active. Refer to the ATM Forum IMA Specification Ver. 1.1 (AF-PHY-008for the definition of each NE and FE state and failure.

Note NOTE 2: For NE Tx/Rx Fail State and FE Tx/Rx Fail State, the status messages are:noFailure, imaLinkFailure, lifFailure, lodsFailure, misConnected, blocked, fault, farEndTxLinkUnusaband farEndRxLinkUnusable. Refer to the ATM Forum IMA Specification Ver. 1.1 (AF-PHY-0086.001 fdefinition of each NE and FE state and failure.

Tx LID Displays the outgoing LID used currently on the link by the local end. This read-only value has meaning only if the link belongs to an IMA group.

Rx LID Displays the incoming LID used currently on the link by the remote end as reported via ICP cells. This value has meaning only if the link belongs to an IMA group. The value of 31 may be used if the receive LID has not yet been detected.

Relative Delay Displays the latest measured delay on this link relative to the link in the same IMA group with the least delay.

IMA Violations Read-only count of ICP violations: count of errored, invalid or missing ICP cells, except during SES-IMA or UAS-IMA conditions.

NE Sev Err Secs Read-only count of one second intervals containing >= 30% of the ICP cells counted as IV-IMAs, or one or more link defects (e.g., LOS, OOF/LOF, AIS, or LCD), LIF defects, or LODS defects, except during UAS-IMA condition.

FE Sev Err Secs Read-only count of one second intervals containing one or more RDI-IMA defects, except during UAS-IMA-FE condition.

NE Unavail Secs Read-only 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 Unavail Secs Read-only count of unavailable seconds at far-end: unavailability begins at the onset of 10 contiguous SES-IMA-FE and ends at the onset o 10 contiguous seconds with no SES-IMA-FE.



efer

A

hich ugh

active.

NE Tx Unusbl Se Read-only count of Tx Unusable seconds at the near-end Tx LSM.

NE Rx Unusbl Se Read-only count of Rx Unusable seconds at the near-end Rx LSM.

FE Tx Unusbl Se Read-only count of seconds with Tx Unusable indications from the far-end Tx LSM.

FE Rx Unusbl Se Read-only count of seconds with Rx Unusable indications from the far-end Rx LSM.

NE Tx Failures Read-only count of times a near-end transmit failure alarm condition has been entered on this link (i.e., some form of implementation specific transmit fault)

NE Rx Failures Read-only count of times a near-end receive failure alarm condition has been entered on this link (i.e., LIF, LODS, RFI-IMA, misconnected or some form of implementation specific receive fault).

Rx Test Pattern Identifies the test pattern received in the ICP Cell (octet 17) on the link during the IMA Test Pattern Procedure. This value may be compared to the transmitted test pattern.

Test Proc Statu Indicates the current state of the Test Pattern Procedure.disabled indicates the test is not running.operating indicates the test is running and no error found on this interface.linkFail indicates an error has been detected on this link during the test. Once an error is detected, the linkFail value is latched until either this object is read or until the Group Test Proc Status is moved to disabled . Once read, if the error no longer persists, a subsequent read will report operating.

7. Select eXit until the Manage Configuration screen for the IMA slot is displayed. The MIB Display and Management screen appears.

8. Exit back to the IMA screen by typing x . The IMA screen is displayed.

9. Select IMA Group Table from the IMA screen options, then select Extra detail. The Detail of IMA Group Table entry 0 screen is displayed as shown in the example below. Rto the description of IMA Group Table screen parameters below as needed.

10. For each IMA group you are using, there are four configurable items on the Detail of IMGroup Table screen:

• Row Status

• Test Link

• Test Patte

• Test Proc

11. Use the Group Inde (Group Index) on the Detail of IMA Group Table screen to identify wIMA group number you are configuring. Use the Down and Up options to sequence throthe IMA groups.

Note At least one physical link in an IMA Group must be set to active before the IMA Group can be set to To activate the links, use the Extra Detail screen of the IMA Link Table, as described earlier.

Switch Name: Slot X SYS IMA Group Table SW VersionDetail of IMA Group Table entry 0

Group Inde: 1 Tx Frame L: m128 Rx Actual : 00 Row Status: notInServce Rx Frame L: m128 4 Test Link : 0 IF Index : 1 Diff Delay: 25 5 Test Patte: - NE State : insufficie Least Dela: 0 6 Test Proc : disabled FE State : operationa Dif Dly Ma: 0 Tx OAM Lab: 3 Failure St: insufficie Alpha : 2 Rx OAM Lab: 3 Symmetry : symmetricO Beta : 21 Min Tx Lin: 4 Gamma : 12 Min Rx Lin: 4 Running Se: 936943 NE Tx Clk : ctc Unavail Se: 364862 FE Tx Clk : ctc NE Failure: 3 Tx Timing : 0 Tx Avail C: 17962 Rx Timing : 4 Rx Avail C: 17962 Last Chang: 13 Mar 200 Tx Cfg Lin: 4 Tx IMA ID : 2 Rx Cfg Lin: 4 Rx IMA ID : 3 Tx Actual : 4Select option:Down, Enter entry number to edit, Goto row, Index search, Summary,eXit



p. ified

is

MA

p.

e, t

12. Use the Min Tx Lin and Min Rx Lin parameters to set MIN/MAX values for an IMA GrouNote that Min Tx and Min Rx values are tied together. If one is changed, the other is modby the switch software. (See IMA Group MIN/MAX Guidelines below.)

13. This completes the IMA LIM configuration procedure.

IMA Group MIN/MAX Guidelines

Relative to IMA Groups, the MIN/MAX feature refers to the capability of adjusting the Groupbandwidth when an T1 or E1 link fails, based on the remaining number of links. A failed linkdefined as a link with LOS, RDI or AIS alarm. When there is an insufficient number of links available based on the user-defined MIN/MAX threshold, the switch software will force the IGroup down and keep it down until the condition is corrected, as described below.

• If a link fails and the number of operating links in the Group is still ≥ the MIN/MAX value, the Group will go down, recalculate bandwidth for the operating links and then come back uWhen the alarm clears, the failed link is automatically added back to the IMA Group.

• If a link fails and the number of operating links in the Group falls below the MIN/MAX valuthe Group will go down and stay down. The Group will not come back up until a sufficiennumber of T1/E1 links are restored, or the operator lowers the MIN/MAX values.

Table 7-24 IMA Group Table Parameters

Group Inde A unique value for the IMA Group. (Read only) Valid values are 1 through 8.

Row Status Options are active and notInService (Immediate effect)No other Row Status options are supported.At least one link must be provisioned in the group using the IMA LInk Table before setting Row Status to active .

IF Index Identifies the logical interface number assigned to this IMA group. Note that re-initializing the management agent may cause IF Index to change.

NE State The current operational state of the near-end IMA Group State Machine. Read-only status messages are:notConfiguredstartUpstartUpAckconfigAbortUnsupportedMconfigAbortIncompatibleSymmetryconfigAbortOtherinsufficientLinksblockedoperationalconfigAbortUnsupportedImaVersion

FE State The current operational state of the far-end IMA Group State Machine. Read-only status messages are:notConfiguredstartUpstartUpAckconfigAbortUnsupportedMconfigAbortIncompatibleSymmetryconfigAbortOtherinsufficientLinksblockedoperationalconfigAbortUnsupportedImaVersion



Failure St The current failure status of the IMA group, that is, the reason why the Group Traffic State Manager (GTSM) is in the down state. Read-only status messages are:noFailurestartUpNestartUpFeinvalidMValueNeinvalidMValueFefailedAssymetricNefailedAssymetricFeinsufficientLinksNeinsufficientLinksFeblockedNeblockedFeotherFailureinvalidImaVersionNeinvalidImaVersionFe

Symmetry Symmetry of the IMA group. Note that only symmetricOperation is supported. Read-only status messages are:symmetricOperationasymmetricOperationasymmetricConfiguration

Min Tx Lin The number of transmit links provisioned in this group. (Immediate effect)Default is 1 (min number).

Min Rx Lin The number of receive links provisioned in this group.

NE Tx Clk Transmit clocking mode used by the near-end IMA group. (Immediate effect)The only valid section is ctc (common transmit clock). IMPORTANT! For NE Tx Clk, only ctc is supported. Always ensure the value is set to ctc . DO NOT select itc (independent transmit clock).

FE Tx Clk Transmit clocking mode used by the far-end IMA group. Read-only messages are:ctc indicates common transmit clockitc indicates independent transmit clock

Tx Timing The link number of the transmit timing reference link to be used by the near-end for IMA data cell clock recovery from the ATM layer. (Read only)The valid range of link numbers is 0 through 15. The value of 0 may be displayed if no link has been configured in the IMA group, or if the transmit timing reference link has not yet been selected. The T1 Timing link is selected automatically by the switch node.

Rx Timing The link number of the receive timing reference link to be used by the near-end for IMA data cell clock recovery toward the ATM layer. (Read only)The valid range of link numbers is 0 through 15. The value of 0 may be displayed if no link has been configured in the IMA group, or if the receive timing reference link has not yet been detected.

Last Chang The date the IMA group last changed operational state.

Tx IMA ID The IMA ID currently in use by the near-end IMA function. Tx IMA ID is selected automatically by the node. This value will be incorrect for more than 8 IMA groups.

Rx IMA ID The IMA ID currently in use by the far-end IMA function. The value of 255 may be used if the receive IMA ID has not yet been detected.

Tx Frame L The frame length (in cells) to be used by the IMA group in the transmit direction. This is a fixed value and is set when an IMA group is in startup. Status messages are: m32, m64, m128 , m256 (Default is m128 ).

Rx Frame L Value of IMA frame length (in cells) as received from remote IMA function. Status messages are: m32, m64 , m128 , m256 (Default is m128 ).

Diff Delay The maximum number of milliseconds of differential delay among the links that will be tolerated on this interface. This value is 25 milliseconds.

Least Dela The link number of the link configured in the IMA group which has the smallest link propagation delay. The valid range of link numbers is 0 through 15. The value of 0 may be displayed if no link has been configured in the IMA group, or if the link with the smallest link propagation delay has not yet been determined.



Dif Dly Ma The latest maximum differential delay observed (in milliseconds) between the links having the least and most link propagation delay among the receive links that are currently configured in the IMA group.

Alpha The 'alpha' value used to specify the number of consecutive invalid ICP cells to be detected before moving to the IMA Hunt state from the IMA Sync state. Range is 1 through 2. Set to default value of 2.

Beta The 'beta' value used to specify the number of consecutive errored ICP cells to be detected before moving to the IMA Hunt state from the IMA Sync state.(Read only) Range is 1 through 5. Set to default value of 2.

Gamma The 'gamma' value used to specify the number of consecutive valid ICP cells to be detected before moving to the IMA Sync state from the IMA PreSync state. Range is 1 through 5. Set to default value of 1.

Running Se The amount of time (in seconds) that this IMA group has been in the Operational state.

Unavail Se Read-only count of one second intervals where the IMA Group Traffic State Machine has been Down.

NE Failure Read-only count of times a near-end group failure (Config-Aborted, Insufficient-Links) has been reported since power-up or reboot.

Tx Avail C Read-only current cell rate (truncated value in cells per second) provided by this IMA group in the transmit direction, considering all the transmit links in the Active state.

Rx Avail C Read-only current cell rate (truncated value in cells per second) provided by this IMA group in the receive direction, considering all the receive links in the Active state.

Tx Cfg Lin Read-only count of links configured to transmit in this IMA group.

Rx Cfg Lin Read-only count of links configured to receive in this IMA group.

Tx Actual Read-only count of links configured to transmit and which are currently Active in this IMA group.

Rx Actual Read-only count of links configured to receive and which are currently Active in this IMA group.

Test Link Used to designate a link as the test link or use in the Test Pattern Procedure. (Immediate effect) The valid range is 0 through 15. Default is 0

The Test Link value is NOT the same as the Tx LID value, but instead identifies the link value of the test link to be used by the Test Pattern Procedure (i.e., the link whose LID value is inserted in the Tx LID field of the transmitted ICP cells).

Test Patte Used to specify the Tx Test Pattern in an IMA group loopback operation. A value in the range 0 to 255 designates a specific pattern. Default is - (minus) 1. The value of -1 specifies that the implementation may choose the value. In this case, the implementation may also choose the value of Test Link IF Index.

The value of 255 should not be used for testing, since by (R-137) the IMA interface is required to transmit 0xFF (i.e., 255) when the incoming test command is inactive or the test link is not detected, and thus it cannot be established for certain whether 255 was received due to an actual loopback operation or due to the normal operation of an IMA that is not performing (or cannot perform) the test pattern procedure.

When the screen displays “- ” (minus sign), the actual value is -1 .

Test Proc Used to enable or disable the Test Pattern Procedure and note whether at least one link failed the test. (Immediate effect) The test is started by setting operating status. If any link should fail the test, the IMA will set the status to linkFail. The linkFail state will persist until either the disabled state is set or until no instance of Test Proc Status has the value linkFail. Options are: disabled , operating , linkFail . Default is disabled .

For the Test Proc, only the values disabled and operating may be written. Writing the operating value will not cause clearing of the linkFail state.

Tx OAM Lab IMA OAM Label value transmitted by the NE IMA unit. (Read only)Range is 0 through 255.

Rx OAM Lab IMA OAM Label value transmitted by the FE IMA unit. (Read only)The value 0 likely means that the IMA unit has not received an OAM Label from the FE IMA unit at this time. Range is 0 through 255.


LIM Configuration SFP Tranceivers

wisted nent

shown

ters

SFP TranceiversThe Small Form-factor Pluggable (SFP) is a compact optical transceiver used in optical communications for both telecommunication and data communications applications. When installed in the PCx card, the SFP interfaces the Xedge switch to a fiber optic or unshielded tpair networking cable. It is a popular industry format supported by several fiber optic compovendors.

The Transceiver Table, shown in Figure 7-15 displays the transceiver operating parameters andmanfufacturer’s information for the SFP associated with either of the two links.

1. At the MIB Display and Management menu, select LIM and Link Information .

2. At the LIM and Link Information menu, select SFP Transceivers .

3. At the SFP Transceivers screen, select an entry number to select the Transceiver table,below. A list of links is displayed.

4. Select a link, then select Extra Detail. In the example below, entry 0 (mez1/link-1 ) is selected. The resulting screen displays the manufacturer’s read-only transceiver paramethat are associated with that link.

Figure 7-15 SFP Transceiver Information Display

Xedge Switch: Slot 0 Tansceiver Table New EventNo ifIndex sfpLocation Recognized SFP Compatibility Connector Type--------------------------------------------------------------------------------0 4300 mez1/link-0 noSFP unknown1 4301 mez1/link-1 noSFP unknown


Xedge Switch: Slot 0 Tansceiver Table New EventDetail of Tansceiver Table entry 1-------------------------------------------------------------------------------- ifIndex : 4301 Part Number : sfpLocation : mez1/link-1 Revision Number: Recognized SFP : Serial Number : Compatibility : noSFP Manufacture Dat: _delta 0 Connector Type : unknown Vendor Specific: 0 CompatibilityCo: Line Encoding : codeUnspecified Line Rate x100 : 0 9/125 fiber km : 0 9/125 fiber 100: 0 50/125 fiber 10: 0 62.5/125 fiber : 0 copper cable me: 0 Xceiver Vendor : Vendor OUI :Select option:Enter entry number to edit, Goto row, Index search, Summary, Up,eXit

TRANSCEIVERTABLE

EXTRADETAILS


LIM Configuration SFP Tranceivers


stem. s s are

e.

ify,

ns.

ies

jor

Chapter 8: Alarm Handler

OverviewAlarms occurring in the Xedge switch are detected by automatic healthcheck polling by the syThe slot-0 controller employs the Alarm Handler to process these node, slot, and link alarmaccording to default or user-defined alarm classifications and configuration. Detected alarmprocessed immediately by Alarm Handler unless inhibited by the user. Table 8-1 lists all Xedge alarms with the associated Alarm ID number and the default alarm classification for each on

This chapter identifies all alarms supported in the Xedge switch and describes how to classconfigure and monitor them via the Alarm Handler function.


• Monitoring Alarms

• Reclassifying Alarms

• Configuring User Status Inputs (Not applicable for Xedge 6002 chassis)

• Inhibiting Alarms

Note Slot controllers installed in the 1RU Xedge 6002 chassis do not support Status Inputs or ACO functio

Monitoring Alarms1. At the root menu, select M,42 to display the Alarm Handler screen. The read-only summar

indicate the status of Critical, Major, Minor alarms in the node as clear (clr ) or as active (maj , min or crit ), based on current alarm classifications. In the example below, maand minor alarms are in effect at the node.

Figure 8-1 Alarm Handler Screen

E3/IMA: Slot 0 Alarm Handler New Event

Node Summary Critical Status: clr Node Summary Major Status : maj Node Summary Minor Status: min0 Slot Alarm Status Table1 Node Alarm Cut Off: off2 Slot/Link Alarm Cut Off3 User Status Inputs4 Scan alarm class file: no



Alarm Handler Monitoring Alarms

e .

.

rms .

2. Select 0 to view the Slot Alarm Status Table to determine the slot and link location of thdetected alarm(s). Select R (Right) as needed to display additional columns of status data

Figure 8-2 Slot Alarm Status Table Summary Screen

3. In the example above, major alarm(s) are reported at slot 0 and minor alarm(s) at slot 4

• For the slot-0 alarm(s), select E to display the Extra Detail screen, as shown below.

• For non slot-0 alarms, select G (Goto row) then type the slot number you wish to investigate. Then select E to display the Extra Detail screen.

Figure 8-3 Slot Alarm Status Table Extra Detail Screen

4. The Extra Detail screen indicates the slot/link location of any major, minor and critical alaoccurring at the node. The example screen indicates that Slot-0 Link 4 has a major alarm

E3/IMA: Slot 0 Slot Alarm Status Table New EventNo Slot Number Slot Critical Status Slot Major Status Slot Minor Status-------------------------------------------------------------------------------0 0 clr maj clr1 1 clr clr clr2 2 clr clr clr3 3 clr clr clr4 4 clr min clr5 5 clr clr clr6 6 clr clr clr7 7 clr clr clr8 8 clr clr clr9 9 clr clr clr10 10 clr clr clr11 11 clr clr clr12 12 clr clr clr13 13 clr clr clr14 14 clr clr clr15 15 clr clr clrSelect option:Down, Enter entry number to edit, Extra detail, Goto row,Index search, Right, eXit

E3/IMA: Slot 0 Slot Alarm Status Table New EventDetail of Slot Alarm Status Table entry 0------------------------------------------------------------------------------- Slot Num: 0 L4 Crit: clr L9 Majo: clr L14 Mino: clr Slot Cri: clr L4 Majo: clr L9 Mino: clr L15 Crit: clr Slot Maj: clr L4 Mino: maj L10 Crit: clr L15 Majo: clr Slot Min: clr L5 Crit: clr L10 Majo: clr L15 Mino: clr L0 Crit: clr L5 Majo: clr L10 Mino: clr L0 Majo: clr L5 Mino: clr L11 Crit: clr L0 Mino: clr L6 Crit: clr L11 Majo: clr L1 Crit: clr L6 Majo: clr L11 Mino: clr L1 Majo: clr L6 Mino: clr L12 Crit: clr L1 Mino: clr L7 Crit: clr L12 Majo: clr L2 Crit: clr L7 Majo: clr L12 Mino: clr L2 Majo: clr L7 Mino: clr L13 Crit: clr L2 Mino: clr L8 Crit: clr L13 Majo: clr L3 Crit: clr L8 Majo: clr L13 Mino: clr L3 Majo: clr L8 Mino: clr L14 Crit: clr L3 Mino: clr L9 Crit: clr L14 Majo: clrSelect option:Down, Enter entry number to edit, Goto row, Index search, Summary,eXit


Alarm Handler Monitoring Alarms

5. For specific information on alarms detected at a slot/link, select X,X,X to return to the root menu. Then select E to access the Event Table, similar to the example below.

Figure 8-4 Event Table

6. Useful troubleshooting information can also be found at the Physical Layout extra detailscreen (M,9,E ) which shows Last State changes

E3/IMA: Slot 0 Event Table New Event Date :Event-------------------------------------------------------------------------------124 03Sep08 140825:Trap: slotChanged CLEARED for125 03Sep08 140825:Slot 6 up.126 03Sep08 140825:Trap: linkChanged CLEARED for127 03Sep08 140825:Slot 6, link 0, state Stopped128 03Sep08 140825:Trap: linkChanged CLEARED for129 03Sep08 140825:Slot 6, link 1, state Stopped130 03Sep08 140825:Trap: linkChanged CLEARED for131 03Sep08 140825:Slot 6, link 2, state Stopped132 03Sep08 140825:Trap: linkChanged CLEARED for133 03Sep08 140825:Slot 6, link 3, state Stopped134 03Sep08 140826:Open VC 0/0 for slot:6 sap:6 atmp:-1 int:150 ret:0135 03Sep08 140827:Slot 6 or 0 does not support ISUP/ISDN136 03Sep08 141259:Trap: clockAlarm CLEARED for137 03Sep08 141259:Major alarm: PRIosc/SECoffline138 05Sep08 141120:Error tftp_handlrsendfile(Time Out): mgtest.txt Select option:Clear event table, Goto row, Save to disk, Up, eXit

E3/IMA: Slot 0 Physical Layout New EventDetail of Physical Layout entry 0-------------------------------------------------------------------------------- Slot No : 0 Lst Chngd Link : link 140 Name : Slot 00 Lst Previous St: none Type : pcx1 DLIM Type : unknown Version : 710v14 State : active2 Reset Slot : no3 Required State : normal Changed State : no4 Associated Slot: 15 Slot Ser # : 0808050001 Slot HW Ver : 2.0b DOC Ser # : 0808050001 DOC HW Ver : 0.0a5 Slot MAC Addres: 001219ff0030 Last State Chan: 03 Sep 2008 14:08:02Select option:Down, Enter entry number to edit, Goto row, Index search, Summary,eXit


Alarm Handler Reclassifying Alarms

nal

Slot

the rms. pped lay.

the

t be

f the

ns, as

Reclassifying AlarmsAlarms generated by the switch are initially configured as Major, Minor, Critical or Informatioalarms by default and are identified by an Alarm ID number (Table 8-1). The classification determines how the switch handles an alarm throughout the system.

• When an alarm occurs in any Xedge switch, the system displays the alarm on the Alarm Status Table (M,42,0 ) according to its classification (maj , min or crit ).

• In an Xedge 6640, 6645, 6280 or 6160 switch, a red Alarm LED on the chassis illuminates in the event of a major, minor or critical alarm.

• In an Xedge 6640, 6645, 6280 or 6160 switch, the S1A/B or S2A/B connectors at Status Input panel can attach to external equipment that generates user status alaWhen a user alarm occurs, the red Alarm LED illuminates and the alarm relay is triaccording to the alarm classification and the physical configuration of the alarm re

Note For information on making proper connections to the User Input and Alarm Relay connectors, refer toXedge Chassis manual (032R410).

Editing the Alarm Class FileThe user can change an alarm’s classification or inhibit an alarm at any time by editing the alr_cls.txt file in the switch, as described below. Note that informational alarms cannoreclassified from their default class, except for the User Status Input alarms (#155 and #156 ).

1. From the root menu of the slot-0 controller, select F,A to display the Select File screen.

2. Type alr_cls.txt or use Ctrl-B or Ctrl-N keys to move the highlight to the alarm classification file. Press the spacebar to display the file in a screen editor. The first part ofile is a detailed tutorial for the alarm classification procedure.

3. Press the Ctrl-C keys to scroll to the end the file which lists the current alarm classificatioshown in the example below.

Figure 8-5 Lower Portion of alr_cls.txt File in Screen Editor

/alr_cls.txt L32 C0 Insert ^J for help. Free:

$Critical: <$Major: 4 91 109 114 126 119 120 131 139 150 110 115 127 121 132 140 111 <$Major: 116 128 122 133 141 142 113 118 130 124 135 147 143 144 138 136 <$Major: 168 169 170 171 172 202 203 205 212 207 209 204 211 188 210 308 <$Major: 309 310 311 401 405 406 407 410 417 418 419 420 421 422 423 424 <$Major: 425 426 427 428 429 430 <$Minor: 107 112 117 129 123 134 145 146 137 206 208 402 408 <$Infor: 2 3 125 155 156 177 301 302 303 304 305 306 307 403 404 1 0 440 <$Infor: 441



s:

to

rmal

ke

4. The alr_cls.txt file is modified via the Screen Editor according to the following rule

• Use Ctrl-J keys to display help for the Screen Editor control keys.

• Each line containing classifications must start with a '$', followed by the class name, a colon, space, then the Alarm ID numbers associated with that class.

• Each Alarm ID number must be separated by a space.

• Each line is limited to 80 characters, and must be terminated by a carriage return.There can be more than one line of the same classification.

Example: To change the lim-fault alarm from major to critical, remove the alarm’s ID number 91 from the $Major line and add it to the $Critical line.

Example: To inhibit the lim-fault alarm from any class list, remove the alarm’s ID number 91 . This will inhibit this alarm from being reported to the Alarm Handler.

Note Refer to Table 8-1 for a list of alarm definitions and corresponding ID numbers, as needed.

5. When all edits are complete, type X to save the file and exit the Screen Editor.

6. Select X,X to return to the root menu.

7. From the root menu, select M,42,4,Y ( Scan Alarm Class File) to activate changes madethe alarm classification file and to update the non-slot 0 controllers.

8. If User Status Input alarms (ID# 155 or ID# 156 ) were reclassified as Critical, Major or Minor, and then subsequently reclassified back to Informational, perform a Warmstart Nofrom the slot-0 root menu (W,N) to put the change into effect.

Note You must perform M,42,4,Y (Scan Alarm Class File) for the new alarm classification changes to taeffect. For changes to user input alarm classification, you must also perform W,N (Warmstart Normal).

Note Refer to Configuring User Status Inputs in this chapter for more information about these alarms.



ation

Alarm Definitions

The following table lists alarms, the corresponding Alarm ID number, and the default classificfor each alarm (Major, Minor or Informational). Note that no alarms are Critical by default.

Note Not all alarms listed below are applicable for all slot controllers types. Alarm ID 155 and 156 are not available when the slot controller is installed in the Xedge 6002 chassis (1RU).

Table 8-1 Alarm Definitions

Alarm ID Alarm Description Default Class Alarm ID Alarm Description Default Class

0 INFO Informational 142 PAIS_SONET MAJOR

1 LINK INFO Informational 143 LOP_SONET MAJOR2 SLOT_DOWN Informational 144 PLM_SONET MAJOR3 LINK_DOWN Informational 145 LYEL_SONET Minor

4 PSU_FAULT MAJOR 146 PYEL_SONET Minor91 LIM_FAULT MAJOR 147 EXBER_SONET MAJOR107 AAL1_FAULT Minor 150 LOS_HSSI MAJOR

109 LOS_DS1 MAJOR 155 USER_INPUT1 Informational110 LOF_DS1 MAJOR 156 USER_INPUT2 Informational111 AIS_DS1 MAJOR 168 LOS_J2 MAJOR

112 YEL_DS1 Minor 169 LOF_J2 MAJOR113 EXBER_DS1 MAJOR 170 AIS_J2 MAJOR114 LOS_DS1_2C MAJOR 171 RAI_J2 MAJOR

115 LOF_DS1_2C MAJOR 172 LOS_SCF MAJOR116 AIS_DS1_2C MAJOR 177 DQ7 Informational117 YEL_DS1_2C Minor 188 SEF_ESONET MAJOR

118 EXBER_DS1_2C MAJOR 202 LOS_ESONET MAJOR119 LOS_DS3 MAJOR 203 LOF_ESONET MAJOR120 LOS_DS3_2C MAJOR 204 EXBER_ESONET MAJOR

121 LOF_DS3 MAJOR 205 LAIS_ESONET MAJOR122 AIS_DS3 MAJOR 206 LRDI_ESONET Minor123 YEL_DS3 Minor 207 PAIS_ESONET MAJOR

124 EXBER_DS3 MAJOR 208 PRDI_ESONET Minor125 FRMR_DIFF_DS3 Informational 209 LOP_ESONET MAJOR126 LOS_E1 MAJOR 210 PUNEQ_ESONET MAJOR

127 LOF_E1 MAJOR 211 PLM_ESONET MAJOR128 AIS_E1 MAJOR 212 LOCD_ESONET MAJOR129 YEL_E1 Minor 301 APS_FAILOVER Informational

130 EXBER_E1 MAJOR 302 APS_SF Informational131 LOS_E3 MAJOR 303 APS_SD Informational132 LOF_E3 MAJOR 304 APS_FORCEDSW Informational

133 AIS_E3 MAJOR 305 APS_MANUALSW Informational134 YEL_E3 Minor 306 APS_EXERCISE Informational135 EXBER_E3 MAJOR 307 APS_PLF Informational

136 LOCD MAJOR 308 APS_PSBF MAJOR137 PLCP_YEL Minor 309 APS_FEPF MAJOR138 PLCP_LOF MAJOR 310 APS_CMF MAJOR

139 LOS_SONET MAJOR 311 APS_AMF MAJOR140 LOF_SONET MAJOR 401 SCE_AAL1_FAULT MAJOR141 LAIS_SONET MAJOR 402 SCE_LINK_FAULT Minor



Alarm ID Alarm Description Default Class Alarm ID Alarm Description Default Class

403 SCE_LINK_STATE Informational 422 IMA_TX_UNU_FE MAJOR

404 SCE_Q_FAULT Informational 423 IMA_RX_UNU_FE MAJOR405 LOS MAJOR 424 IMA_GRP_STARTUP_FE MAJOR406 LOF MAJOR 425 IMA_GRP_CFG_ABORT MAJOR

407 AIS MAJOR 426 IMA_GRP_CFG_ABORT_FE MAJOR408 RDI Minor 427 IMA_GRP_INSUF_LINKS MAJOR410 EBER MAJOR 428 IMA_GRP_INSUF_LINKS_FE MAJOR

417 IMA_LIF MAJOR 429 IMA_GRP_BLOCKED_FE MAJOR418 IMA_LODS MAJOR 430 IMA_GRP_TMG_MISM MAJOR419 IMA_RDI_IMA MAJOR 440 XBRIDGE_NEWROOT Informational

420 IMA_TX_MISCON MAJOR 441 XBRIDGE_TOPOLOGY_CHANGE Informational421 IMA_RX_MISCON MAJOR

Table 8-1 Alarm Definitions (Continued)


Alarm Handler Configuring User Status Inputs

s input ernal h as

switch larm ed in

oper talled

ual to

ctors.

low.

s:

Configuring User Status InputsThe high density Xedge chassis (Xedge 6160, 6280, 6640 or 6645) provides two sets of statuconnectors at the chassis rear panel (S1-A/B and S2-A/B) which can communicate with extuser equipment that generates User Input alarms. These alarms are recognized in the switc user_input1 (ID# 155) and user_input2 (ID# 156).

Once entered by the user via an external source, these input alarms can be classified in theas Major, Minor, Critical or Informational like any other alarm, and will be processed by the AHandler accordingly. User Input alarms can also be inhibited like any other alarm as describthis chapter under the paragraphs on Inhibiting Alarms .

Note Refer to the Xedge Chassis Installation Guide (GDC P/N 032R410) for detailed information on the prphysical configuration of the status input connectors S1-A/B and S2-A/B. Note that slot controllers insin the 1RU Xedge 6002 chassis do not support User Status Inputs or ACO functions.

User Status Inputs Procedure

Before configuring the Xedge switch for User Status Inputs, refer to the Xedge chassis manproperly connect the external equipment:

• One or two external devices connect to the chassis rear S1-A/B and S2-A/B conne

• External annunciator (buzzer, etc.) connects to the chassis rear alarm relay panel.

1. At the root menu, select M,42,3 to access the User Status Inputs screen.

2. Select G (Goto row) then select the user status input you wish to configure:

• Entry 0 for status input connector S1-A/B

• Entry 1 for status input connector S2-A/B

3. Select E to display the User Status Inputs extra detail screen, similar to the example be

Figure 8-6 Detail of User Status Inputs Screen

4. At the User Status Input screen, select 0 (Status Input option) and configure the function a

• enabled

• disabled

• not applicable (for Xedge 6002 chassis only)

E3/IMA: Slot 0 User Status Inputs New EventDetail of User Status Inputs entry 1------------------------------------------------------------------------------- Input Status No : 10 Status Input : enabled1 Trap : enabled2 Trap Description : x3 Active State : active closed Alarm Classification : informational Current Status : active

Select option:Enter entry number to edit, Goto row, Index search, Summary, Up,eXit


Alarm Handler Configuring User Status Inputs

ult

put

5. At the User Status Input screen, select 1 (Trap) and configure the function as:

• enabled (switch generates alarm traps in response to user input signals)

• disabled (no alarm traps generated from user input signals)

6. At the User Status Input screen, select 2 and enter a description of the alarm, if desired.

7. At the User Status Input screen, select 3 (Active State option) to define whether the alarm will be activated by a closed or open circuit.

8. The read-only “Current Status” field will display the state of the alarm as:

• clear (clr )

• active (maj , min or cri )

9. The read-only “Alarm Classification” field will display the classification of the alarm (defais Informational ). To reclassify this user status input alarm, refer to the Editing the Alarm Class File procedure as described earlier in this chapter.

10. Repeat this procedure if external equipment is also attached to the other User Status Inconnector.

11. Select X,X,X to return to the root menu.


Alarm Handler Inhibiting Alarms

y

ff d link ys, s will

oper talled

t:

Inhibiting Alarms

Alarm Classification File

For all slot controllers installed in any model of the Xedge switch chassis, inhibit any alarm bediting the alarm classification file. Refer to Editing the Alarm Class File in this chapter for instructions.

Alarm Relay Cut-Offs (ACO)

For slot controllers installed in an Xedge 6640, 6645, 6280 or 6160 chassis, the Alarm Cut-ofunction (ACO) allows you to inhibit one or both User Input Status alarms at the node, slot anlevels. When enabled, User Input Status alarms will be inhibited from tripping the alarm relahowever the system will still report alarm states to the Alarm Handler. The Alarm Status Tableshow the active alarms with ACO appended to their status.

Note Refer to the Xedge Chassis Installation Guide (GDC P/N 032R410) for detailed information on the prphysical configuration of the status input connectors S1-A/B and S2-A/B. Note that slot controllers insin the 1RU Xedge 6002 chassis do not support User Status Inputs or ACO functions.

Node Alarm Cut-Off

1. At the root menu, select M,42,1 to access the Node Alarm Cut-off screen. At the promp

• Select A (Off) to disable node alarm cut-off.

• Select B (On) to enable node alarm cut-off.

2. Select X,X to return to the root menu.

Slot / Link Alarm Cut-Off

1. At the root menu, select M,42,2 to access the Slot / Link Alarm Cut-off screen.

2. At the prompt, select the desired slot controller.

• For the slot-0, select E to display the Extra Detail screen, as shown below.

• For non slot-0 alarms, select G (Goto row) then type the slot number you wish to investigate. Then select E to display the Extra Detail screen.

Figure 8-7 Slot/Link Alarm Cut-off Extra Detail Screen

E3/IMA: Slot 0 Slot/Link Alarm Cut Off New EventDetail of Slot/Link Alarm Cut Off entry 0------------------------------------------------------------------------------- Slot Number : 0 15 Link 14 ACO : off00 Slot ACO : off 16 Link 15 ACO : off01 Link 0 ACO : off02 Link 1 ACO : off03 Link 2 ACO : off04 Link 3 ACO : off05 Link 4 ACO : off06 Link 5 ACO : off07 Link 6 ACO : off08 Link 7 ACO : off09 Link 8 ACO : off10 Link 9 ACO : off11 Link 10 ACO : off12 Link 11 ACO : off13 Link 12 ACO : off14 Link 13 ACO : offSelect option:Down, Enter entry number to edit, Goto row, Index search, Summary,eXit



ke effect.

3. If desired, select 0 for the slot controller to be configured for ACO. Otherwise, skip to step 5.

4. At the prompt, enable or disable ACO for the selected controller or link:

• Select A (Off) to disable alarm cut-off for the controller.

• Select B (On) to enable alarm cut-off for the controller.

5. If desired, select 1, 2, 3...1 for the link to be configured for ACO. Otherwise, skip to step 8.

6. At the prompt, enable or disable ACO for the link:

• Select A (Off) to disable alarm cut-off for the link.

• Select B (On) to enable alarm cut-off for the link.

7. Repeat step 5. and step 6. for all desired links.

8. when complete, select X,X to return to the root menu.

Note Xedge 6002 switch chassis does not support ACO. Therefore, entries made at ACO screens do not ta




F rgence s. The ters,

vailable

CLI. de you

that ate gure

faces, ing

Appendix A: OSPF CLI Reference

OSPFv2 ProtocolOSPF version 2 is the Interior Gateway routing protocol (IGP) described in RFC2328 - OSPVersion 2. Compared with RIP, OSPF can provide scalable network support and faster convetime. OSPF is widely used in large networks such as ISP backbone and enterprise networkfollowing paragraphs describe how to use the OSPF commands to configure OSPF parameshow OSPF information, and debug settings.

OSPF Command Modes Configuration of OSPF is done through the Virtual TeletYpe (VTY), which is a command lineinterface that consists of several modes, each of which determines the commands that are ato the user. The VTY modes are described below.

View Mode

When you first log in, you are in View Mode, which indicates read-only access to the CLI. View Mode employs the angle bracket > prompt.

Enable Mode

Enable mode is the administration mode for the router which is for read-write access to the This mode allows you to view router settings that are considered private. To enter Enable Momust use the enable command. Enable Mode employs the # prompt.

Configure Mode

Once the router is enabled, you can enter the Configure Mode to manually type commandschange router settings that are currently in memory. Common tasks from this mode are: creaccess-lists, change passwords, configure logging, and enter default routes. To enter ConfiMode type the following command: configure terminal . Configure Mode employs the (config)# prompt.

Router Mode

Router Mode allows configuration of the router. Common tasks include enabling ospf on interand setting the router id. This mode is entered from the configure mode by typing the followcommand: router ospf . Router Mode employs the ospfd(config-router)# prompt.

032R401-V722 Xedge MSPx System Version 7.2.2 A-1Issue 1 Configuration & Diagnostics Guide

OSPF CLI Reference OSPF Guidelines and Examples

terface ing

d in

ons.

Interface Mode

Interface-specific OSPF parameters are entered in this mode. To access this mode, enter in<ifname> from the Configuration Mode. Common tasks include changing OSPF timers, addauthentication, and assigning the link cost manually.

Figure 1-1 OSPF VTY Mode Hierarchy

OSPF Guidelines and Examples

VTY Shortcuts and Tips

• C-c Interrupt current input and moves to the next line.

• C-z End current configuration session and move to top node.

• C-n <DOWN> Move down to next line in the history buffer.

• C-p <UP> Move up to previous line in the history buffer.

• TAB Use command line completion by typing TAB .

• Typing help at the beginning of the line to get command line help.

• Typing ? at any point in the line will show possible completions.

• Typing list in any mode will give every combination of commands that can be enterethat mode.

Below are some sample VTY sessions to use as a guide to performing various OSPF functiNote that /8 (slash 8) is a notation for a netmask of 255.0.0.0, /16 for 255.255.0.0, /24 for 255.255.255.0, etc.

Accessing VTY

The session below demonstrates accessing the VTY:

Linux Kernel 2.4.20_mvl31-mn8270PCXem9 login: root # Login as root into the PCX/ISG MontaVista(R) Linux(R) Professional Edition 3.1

root@PCX:~# telnet localhost ospfd # Telnet to the OSPF VTYTrying 127.0.0.1...Connected to localhost.localdomain.Escape character is '^]'.

User Access Verification

Password:ospfd> enable # Entering enable modeospfd# configure terminal # Entering configure modeospfd(config)# router ospf # Entering router modeospfd(config-router)# network 172.16.12.120/24 area 0 # Enable OSPF on specified interfaces

A-2 Xedge MSPx System Version 7.2.2 032R401-V722Configuration & Diagnostics Guide Issue 1

OSPF CLI Reference OSPF Guidelines and Examples

e l static

domain

s hello

Sample Sessions

VTY Session “A”

This sample session demonstrates OSPF enabled on any interfaces with IP addresses in th172.16.0.0/16 (172.16.0.0 to 172.16.255.255) range in area 0. Also allows the sending of alroutes and connected interfaces (local interfaces).

root@PCX:~# telnet localhost ospfdTrying 127.0.0.1...Connected to localhost.localdomain.Escape character is '^]'.User Access Verification

Password:ospfd> enospfd# configure terminalospfd(config)# router ospf # Proceed to router modeospfd(config-router)# redistribute connected # Redistribute connected interfacesospfd(config-router)# redistribute static # Redistribute static routesospfd(config-router)# network 172.16.0.0/16 area 0# Enable OSPF on interfacesospfd(config-router)# write # Write changes to startup-config

Session “B”

This sample session sets the router-id of the OSPF router. Note that each OSPF router in theneeds to have a unique router-id.

root@PCX:~# telnet localhost ospfdTrying 127.0.0.1...Connected to localhost.localdomain.Escape character is '^]'.


Password:ospfd> enospfd# configure terminalospfd(config)# router ospf # Proceed to router modeospfd(config-router)# router-id 172.16.12.179# Redistribute connected interfacesospfd(config-router)# write # Write changes to startup-config

Session “C”

This sample session adds an authentication key to interface eth0 to provide security, changeand dead interval timers, and changes the cost of the interface.

root@PCX:~# telnet localhost ospfdTrying 127.0.0.1...Connected to localhost.localdomain.Escape character is '^]'.


Password:ospfd> enospfd# configure terminalospfd(config)# router ospf # Proceed to router modeospfd(config-if)# ospf authentication-key pass# Set authentication keyospfd(config-if)# ospf hello-interval 20# Set hello intervalospfd(config-if)# ospf dead-interval 80# Set dead intervalospfd(config-if)# ospf cost 40000 # Set interace costospfd(config-if)# write # Write changes to startup-config


OSPF CLI Reference OSPF Command Reference

port

es. So

raft-n of ltiple ssful c pped. ers.")

section were and

from can

OSPF Command Reference

OSPF Router Commands

To start OSPF process must specify the OSPF router. As of this writing, ospfd does not supmultiple OSPF processes.

Command: router ospf Command: no router ospf

Enable or disable the OSPF process. ospfd does not yet support multiple OSPF processyou can not specify an OSPF process number.

OSPF Command: ospf router-id a.b.c.d OSPF Command: no ospf router-id

OSPF Command: ospf abr-type type OSPF Command: no ospf abr-type type

type can be cisco|ibm|shortcut|standard More information regarding the behaviour controlled by this command can be found in dietf-ospf-abr-alt-05.txt and draft-ietf-ospf-shortcut-abr-02.txt (Quote: "Though the definitiothe Area Border Router (ABR) in the OSPF specification does not require a router with muattached areas to have a backbone connection, it is actually necessary to provide succerouting to the inter-area and external destinations. If this requirement is not met, all traffidestined for the areas not connected to such an ABR or out of the OSPF domain, is droThis document describes alternative ABR behaviors implemented in Cisco and IBM rout

OSPF Command: ospf rfc1583compatibility OSPF Command: no ospf rfc1583compatibility

This rfc2328, the successor to rfc1583, suggests according to section G.2 (changes) in 16.4 a change to the path preference algorithm that prevents possible routing loops thatpossible in the old version of OSPFv2. More specifically it demands that inter-area pathsintra-area path are now of equal preference but still both preferred to external paths.

OSPF Command: passive interface interface OSPF Command: no passive interface interface

OSPF Command: timers spf <0-4294967295> <0-4294967295> OSPF Command: no timers spf

OSPF Command: refresh group-limit <0-10000> OSPF Command: refresh per-slice <0-10000> OSPF Command: refresh age-diff <0-10000> OSPF Command: auto-cost refrence-bandwidth <1-4294967> OSPF Command: no auto-cost refrence-bandwidth

OSPF Command: network a.b.c.d/m area a.b.c.d OSPF Command: network a.b.c.d/m area <0-4294967295> OSPF Command: no network a.b.c.d/m area a.b.c.d OSPF Command: no network a.b.c.d/m area <0-4294967295>

This command specifies the OSPF enabled interface(s). If the interface has an address range 192.168.1.0/24 then the command below enables ospf on this interface so router provide network information to the other ospf routers via this interface.



in ddress

ed to d rnal-is not

ced d

re not

f area

router ospfnetwork 192.168.1.0/24 area 0.0.0.0

Prefix length in interface must be equal or bigger (ie.smaller network) than prefix length network statement. For example statement above doesn't enable ospf on interface with a192.168.1.1/23, but it does on interface with address192.168.1.129/25.

OSPF Area Commands

OSPF Command: area a.b.c.d range a.b.c.d/m OSPF Command: area <0-4294967295> range a.b.c.d/m OSPF Command: no area a.b.c.d range a.b.c.d/m OSPF Command: no area <0-4294967295> range a.b.c.d/m

Summarize intra area paths from specified area into one Type-3 summary-LSA announcother areas. This command can be used only in ABR, and only router-LSAs (Type-1) annetwork-LSAs (Type-2) (ie. LSAs with scope area) can be summarized. Type-5 AS-exteLSAs can not be summarized; their scope is AS. Summarizing Type-7 AS-external-LSAs currently supported by Quagga.

router ospfnetwork 192.168.1.0/24 area 0.0.0.0network 10.0.0.0/8 area 0.0.0.10area 0.0.0.10 range 10.0.0.0/8

With configuration above one Type-3 Summary-LSA with routinginfo 10.0.0.0/8 is announinto backbone area if area 0.0.0.10 contains at least one intra-areanetwork (ie. describewithrouter or network LSA) from this range.

OSPF Command: area a.b.c.d range IPV4_PREFIX not-advertise OSPF Command: no area a.b.c.d range IPV4_PREFIX not-advertise

Instead of summarizing intra area paths filter them - ie. intra area paths from this range aadvertised into other areas. This command makes sense in ABR only.

OSPF Command: area a.b.c.d range IPV4_PREFIX substitute IPV4_PREFIX OSPF Command: no area a.b.c.d range IPV4_PREFIX substitute IPV4_PREFIX

Substitute summarized prefix with another prefix.

router ospfnetwork 192.168.1.0/24 area 0.0.0.0network 10.0.0.0/8 area 0.0.0.10area 0.0.0.10 range 10.0.0.0/8 substitute 11.0.0.0/8

One Type-3 summary-LSA with routing info 11.0.0.0/8 isannounced into backbone area i0.0.0.10 contains at least one intra-area network (ie. described with router-LSA or networkLSA) from range

OSPF Command: area a.b.c.d virtual-link a.b.c.d OSPF Command: area <0-4294967295> virtual-link a.b.c.d OSPF Command: no area a.b.c.d virtual-link a.b.c.d OSPF Command: no area <0-4294967295> virtual-link a.b.c.d

OSPF Command: area a.b.c.d shortcut OSPF Command: area <0-4294967295> shortcut OSPF Command: no area a.b.c.d shortcut OSPF Command: no area <0-4294967295> shortcut



from

6 (for mmary-nd

se in

OSPF Command: area a.b.c.d stub 10.0.0.0/8. (This command makes sense in ABR only.)OSPF Command: area <0-4294967295> stub OSPF Command: no area a.b.c.d stub OSPF Command: no area <0-4294967295> stub

OSPF Command: area a.b.c.d stub no-summary OSPF Command: area <0-4294967295> stub no-summary OSPF Command: no area a.b.c.d stub no-summary OSPF Command: no area <0-4294967295> stub no-summary

OSPF Command: area a.b.c.d default-cost <0-16777215> OSPF Command: no area a.b.c.d default-cost <0-16777215>

OSPF Command: area a.b.c.d export-list NAME OSPF Command: area <0-4294967295> export-list NAME OSPF Command: no area a.b.c.d export-list NAME OSPF Command: no area <0-4294967295> export-list NAME

Filter Type-3 summary-LSAs announced to other areas originated from intra- area pathsspecified area.

router ospfnetwork 192.168.1.0/24 area 0.0.0.0network 10.0.0.0/8 area 0.0.0.10area 0.0.0.10 export-list foo!

access-list foo permit 10.10.0.0/16access-list foo deny any

With example above any intra-area paths from area 0.0.0.10 and from range 10.10.0.0/1example 10.10.1.0/24 and10.10.2.128/30) are announced into other areas as Type-3 suLSA's, but any others (for example 10.11.0.0/16 or10.128.30.16/30) aren't. This commamakes sense in ABR only.

OSPF Command: area a.b.c.d import-list NAME OSPF Command: area <0-4294967295> import-list NAME OSPF Command: no area a.b.c.d import-list NAME OSPF Command: no area <0-4294967295> import-list NAME

Same as export-list, but it applies to paths announced into specified area as Type-3 summary-LSAs.

OSPF Command: area a.b.c.d filter-list prefix NAME in OSPF Command: area a.b.c.d filter-list prefix NAME out OSPF Command: area <0-4294967295> filter-list prefix NAME in OSPF Command: area <0-4294967295> filter-list prefix NAME out OSPF Command: no area a.b.c.d filter-list prefix NAME in OSPF Command: no area a.b.c.d filter-list prefix NAME out OSPF Command: no area <0-4294967295> filter-list prefix NAME in OSPF Command: no area <0-4294967295> filter-list prefix NAME out

Filtering Type-3 summary-LSAs to/from area using prefix lists. This command makes senABR only.



is

is not to ld have or else ot if

and

tivity efault

be for all

OSPF Command: area a.b.c.d authentication OSPF Command: area <0-4294967295> authentication OSPF Command: no area a.b.c.d authentication OSPF Command: no area <0-4294967295> authentication OSPF Command: area a.b.c.d authentication message-digest OSPF Command: area <0-4294967295> authentication message-digest

OSPF interface Commands

Interface Command: ip ospf authentication-key AUTH_KEY Interface Command: no ip ospf authentication-key

Set OSPF authentication key to a simple password. After setting AUTH_KEY, all OSPFpackets are authenticated. AUTH_KEY has length up to 8 chars.

Interface Command: ip ospf message-digest-key KEYID md5 KEY Interface Command: no ip ospf message-digest-key

Set OSPF authentication key to a cryptographic password. The cryptographic algorithmMD5. KEYID identifies secret key used to create the message digest. KEY is the actual message digest key up to 16 chars.

Note that OSPF MD5 authentication requires that time never go backwards (correct timeimportant, only that it never goes backwards), even across resets, if ospfd is to be able promptly re-estabish adjacencies with its neighbors after restarts/reboots. The host shousystem time be set at boot from an external source (e.g., battery-backed clock, NTP, etc.)the system clock should be periodically saved to non-volative storage and restored at boMD5 authentication is to be expected to work reliably.

Interface Command: ip ospf cost <1-65535> Interface Command: no ip ospf cost

Set link cost for the specified interface. The cost value is set to router-LSA's metric fieldused for SPF calculation.

Interface Command: ip ospf dead-interval <1-65535> Interface Command: no ip ospf dead-interval

Set number of seconds for RouterDeadInterval timer value used for Wait Timer and InacTimer. This value must be the same for all routers attached to a common network. The dvalue is 40 seconds.

Interface Command: ip ospf hello-interval <1-65535> Interface Command: no ip ospf hello-interval

Set number of seconds for HelloInterval timer value. Setting this value, Hello packet willsent every timer value seconds on the specified interface. This value must be the same routers attached to a common network. The default value is 10 seconds.

Interface Command: ip ospf network (broadcast|non-broadcast|point-to-multipoint|point-to-point)

Interface Command: no ip ospf network

Set explicitly network type for specified interface.



me r. The

ting

value

Interface Command: ip ospf priority <0-255> Interface Command: no ip ospf priority

Set RouterPriority integer value. Setting higher value, router will be more eligible to becoDesignated Router. Setting the value to 0, router is no longer eligible to Designated Routedefault value is 1.

Interface Command: ip ospf retransmit-interval <1-65535> Interface Command: no ip ospf retransmit interval

Set number of seconds for RxmtInterval timer value. This value is used when retransmitDatabase Description and Link State Request packets. The default value is 5 seconds.

Interface Command: ip ospf transmit-delay Interface Command: no ip ospf transmit-delay

Set number of seconds for InfTransDelay value. LSAs' age should be incremented by thiswhen transmitting. The default value is 1 seconds.

Redistribute Routes to OSPF

OSPF Command: redistribute (kernel|connected|static|rip|bgp)

OSPF Command: redistribute (kernel|connected|static|rip|bgp) route-map

OSPF Command: redistribute (kernel|connected|static|rip|bgp) metric-type (1|2)

OSPF Command: redistribute (kernel|connected|static|rip|bgp) metric-type (1|2) route-map word

OSPF Command: redistribute (kernel|connected|static|rip|bgp) metric <0-16777214>

OSPF Command: redistribute (kernel|connected|static|rip|bgp) metric <0-16777214> route-map word

OSPF Command: redistribute (kernel|connected|static|rip|bgp) metric-type (1|2) metric <0-16777214>

OSPF Command: redistribute (kernel|connected|static|rip|bgp) metric-type (1|2) metric <0-16777214> route-map word

OSPF Command: no redistribute (kernel|connected|static|rip|bgp)

OSPF Command: default-information originate

OSPF Command: default-information originate metric <0-16777214>

OSPF Command: default-information originate metric <0-16777214> metric-type (1|2)

OSPF Command: default-information originate metric <0-16777214> metric-type (1|2) route-map word

OSPF Command: default-information originate always

OSPF Command: default-information originate always metric <0-16777214>



OSPF Command: default-information originate always metric <0-16777214> metric-type (1|2)

OSPF Command: default-information originate always metric <0-16777214> metric-type (1|2) route-map word

OSPF Command: no default-information originate

OSPF Command: distribute-list NAME out (kernel|connected|static|rip|ospf)

OSPF Command: no distribute-list NAME out (kernel|connected|static|rip|ospf)

OSPF Command: default-metric <0-16777214>

OSPF Command: no default-metric

OSPF Command: distance <1-255>

OSPF Command: no distance <1-255>

OSPF Command: distance ospf (intra-area|inter-area|external) <1-255>

OSPF Command: no distance ospf

Command: router zebra

Command: no router zebra

Show OSPF Information

Command: show ip ospf

Command: show ip ospf interface [INTERFACE]

Command: show ip ospf neighbor

Command: show ip ospf neighbor INTERFACE

Command: show ip ospf neighbor detail

Command: show ip ospf neighbor INTERFACE detail

Command: show ip ospf database

Command: show ip ospf database (asbr-summary|external|network|router|summary)

Command: show ip ospf database (asbr-summary|external|network|router|summary) link-state-id

Command: show ip ospf database (asbr-summary|external|network|router|summary) link-state-id adv-router adv-router

Command: show ip ospf database (asbr-summary|external|network|router|summary) adv-router adv-router



Command: show ip ospf database (asbr-summary|external|network|router|summary) link-state-id self-originate

Command: show ip ospf database (asbr-summary|external|network|router|summary) self-originate

Command: show ip ospf database max-age

Command: show ip ospf database self-originate

Command: show ip ospf refresher

Command: show ip ospf route

Debug OSPF

Command: debug ospf packet (hello|dd|ls-request|ls-update|ls-ack|all) (send|recv) [detail]

Command: no debug ospf packet (hello|dd|ls-request|ls-update|ls-ack|all) (send|recv) [detail]

Command: debug ospf ism

Command: debug ospf ism (status|events|timers)

Command: no debug ospf ism

Command: no debug ospf ism (status|events|timers)

Command: debug ospf nsm

Command: debug ospf nsm (status|events|timers)

Command: no debug ospf nsm

Command: no debug ospf nsm (status|events|timers)

Command: debug ospf lsa

Command: debug ospf lsa (generate|flooding|refresh)

Command: no debug ospf lsa

Command: no debug ospf lsa (generate|flooding|refresh)

Command: debug ospf zebra

Command: debug ospf zebra (interface|redistribute)

Command: no debug ospf zebra

Command: no debug ospf zebra (interface|redistribute)

Command: show debugging ospf


The Best Connections in the Business

Documents

XedgeMSPx - GDC032R401-V722 Xedge MSPx System Version 7.2.2 iii Issue 1 Configuration & Diagnostics Guide Table of Contents Chapter 6: PCL Configuration/Status