xedgemspx - gdc032r401-v710 xedge mspx system version 7.1.0 v issue 4 configuration guide preface...

The Best Connections in the Business

TM

Xedge MSPxXedge MSPxXedge MSPx6RIWZDUH#&RQILJXUDWLRQ

IRU#9HUVLRQ#:1413#

3&[#6ORW#&RQWUROOHU,6*5#6ORW#&RQWUROOHU2&01#2#67001#/LQH#,QWHUIDFH#0RGXOH

365573409:43#,VVXH#7)HEUXDU\#533;

of this readable bject

the use mages.

Copyright©2008 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-V710

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 supplied with your products.

Issue Date Description of Change

1 October 2006 Initial Release of Software Version 7.1.0 and associated hardware

2 January 2007 Updates and minor corrections/clarifications.

3 December 2007 Updated information on SAPs, Link Status, Slot-0 redundancy.

4 February 2008 Corrections/clarifications on LIMs and Slot-0 redundancy.

Description Part Number

Xedge 6000 Switch Application Guide 032R300-V620

Xedge 6000 Switch Technical Reference 032R310-V620

Xedge 6000 Switch Software Configuration Guide (for Ver 6.2 Slot Controllers/LIMs)Xedge 6000 Switch Software Ver 6.2 Release Notes and Patch Notes)

032R400-V620032R901-V62X

Xedge 6000 Switch Software Ver 7.X Configuration Guide ( for ISG2, PCx, OC-N LIM only)Xedge 6000 Switch Software Ver 7.X Release Notes and Patch Notes)

032R401-V7XX032R901-V7XX

Xedge 6000 Switch Chassis Installation Guide (all models) 032R410-000

Xedge 6000 Switch Hardware Installation Manual 032R440-V620

Xedge 6000 Switch Diagnostics Guide 032R500-V620

ProSphere Ver. 3.X Routing Manager Install & Oper Manual (RTM, INM, ADM) 032R600-V300032R605-V300032R606-V300

ProSphere NMS Version 5.X User Manual 032R610-V5XX

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

032R906-V440032R906-V5XX

Table of Contents

vi

v

ix

x

i

i

i

8

2

2

-3

PrefaceSoftware Version History....................................................................................................v

Safety Information...................................................................................................................

Compliance............................................................................................................................. ii

Before You Begin....................................................................................................................

Site Requirements............................................................................................................... i

Installation & Connectivity................................................................................................ ix

Accessing the Xedge Switch.............................................................................................. ix

Navigating Xedge Menus and Screens................................................................................x

Support Services and Training................................................................................................. x

Corporate Client Services...................................................................................................x

Factory Direct Support & Repair........................................................................................xi

Contact Information ...........................................................................................................x

Chapter 1: Xedge Switch OverviewIntroduction to Xedge Version 7.1......................................................................................... 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

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

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

Change Root Password.....................................................................................................2-3

User Read/Write Access...................................................................................................2-4

Craft Port Security Key....................................................................................................2-6

Secure Copy Protocol (SCP/SSH)....................................................................................2-6

Chapter 3: Hardware OverviewISG2 Hardware Overview...................................................................................................... 3-1

032R401-V710 Xedge MSPx System Version 7.1.0 iIssue 4 Configuration Guide

Table of Contents

1

1

-

4

4

4

-

7

1

1

2

3

4

4

6

-9

11

4

Features & Benefits..........................................................................................................3-

Traffic Management.........................................................................................................3-

Routing.............................................................................................................................31

PCx Hardware Overview....................................................................................................... 3-

Features & Benefits..........................................................................................................3-

Traffic Management........................................................................................................3-

Routing.............................................................................................................................34

PCx Assemblies................................................................................................................3-

OC-N / STM-N Line Interface Module................................................................................. 3-8

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

Before You Begin.................................................................................................................. 4-

Current Time Format........................................................................................................4-

Slot-0 IP Addressing.........................................................................................................4-

Slot-0 Configuration............................................................................................................... 4-

SNMP Authentication............................................................................................................ 4-

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

Redundant Slot-0 Configuration............................................................................................ 4-6

Initial Setup for Slot-0 Redundancy.................................................................................4-6

Enable Slot-0 Redundancy...............................................................................................4-7

Disable Slot-0 Redundancy..............................................................................................4-8

Re-Enable Slot-0 Redundancy..........................................................................................4-9

Slot-0 Redundancy Guidelines.......................................................................................4-10

Summary.............................................................................................................................. 4-10

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

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

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

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

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

Link Status............................................................................................................................. 5-8

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

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

Chapter 6: PCx Configuration/StatusOverview................................................................................................................................ 6-1

Management Configuration................................................................................................... 6-2

ATM Port Configuration........................................................................................................ 6-

ii Xedge MSPx System Version 7.1.0 032R401-V710Configuration Guide Issue 4

Table of Contents

6

-8

10

1

1

-3

5

1

4

2

6

4

1

2

3

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

Tunnel Configuration............................................................................................................. 6-

Interface Status....................................................................................................................... 6

Node Status.......................................................................................................................... 6-

Chapter 7: Line Interface ModulesATM LIMs Overview............................................................................................................ 7-

LIM Configuration................................................................................................................. 7-

LIM Information and Configuration...................................................................................... 7-2

LIM ID, Version, Status...................................................................................................7-2

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

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

SONET/SDH Links................................................................................................................ 7-

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

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

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

SONET/SDH Alarms.....................................................................................................7-15

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

APS Group Configuration..............................................................................................7-19

APS Link Configuration.................................................................................................7-25

APS Alarms....................................................................................................................7-3

SONET/SDH Defects........................................................................................................... 7-3

IMA LIMs ............................................................................................................................ 7-40

IMA Configuration Overview........................................................................................7-40

IMA Group Bandwidth...................................................................................................7-41

E1 IMA Configuration......................................................................................................... 7-4

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

IMA Configuration............................................................................................................... 7-4

SFP Tranceivers................................................................................................................... 7-5

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

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

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

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

032R401-V710 Xedge MSPx System Version 7.1.0 iiiIssue 4 Configuration Guide

Table of Contents

0

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

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

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

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

iv Xedge MSPx System Version 7.1.0 032R401-V710Configuration Guide Issue 4

7.X

ental ) and

orks. f

ntirely ts eneral

of the

ual,

Preface

Scope of this ManualThis manual describes the Xedge MultiService Packet xChange switch (MSPx) with VersionSlot Controllers (ISG2 and PCx), and supported LIMs for the PCx. All information refers to currently supported versions of switch code, except where noted. This information is supplemto the information provided in the latest issue of the Xedge 6000 Hardware Manual (032R440the Xedge 6000 Configuration and Diagnostics Guide (032R400). Related Publications are listed on the inside front cover of this document.

This information is intended for qualified network operators and administrators who are experienced in setting up and managing MPLS and ATM traffic and signaling in Xedge netwWiring must comply with the local electrical codes in your area that govern the installation oelectronic equipment.

The information contained in this manual has been carefully checked and is believed to be ereliable. 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 AvenueNaugatuck, Connecticut 06770 U.S.A.Tel: 1 203 729-0271 Toll Free: 1 800 523-1737

Software Version History

This document supports the Xedge Switch Software Version 7.1.X. Refer to the latest issueXedge Version 7.1.X Release Notes for a version-based comparision of features.

Manual Organization

This 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, Hardware Overview

• Chapter 4, Basic Slot-0 Configuration

• Chapter 5, ISG2 Configuration/Status

• Chapter 6, PCx Configuration/Status

• Chapter 7, Line Interface Modules

• Appendix A, OSPF CLI Reference

032R401-V710 Xedge MSPx System Version 7.1.0 vIssue 4 Configuration Guide

Preface Safety Information

. The

tor. for

afety

ally

ed.

tion.

tatic mputer and tic

t.

adily

s of

lt

n

Safety InformationThis manual should be read in its entirety and all procedures completely understood beforeinstalling or operating the unit, including all notes, cautions and warnings (examples below)CAUTION, WARNING, and DANGER statements that appear throughout this manual are intended to provide critical information for the safety of both the service engineer and operaThese statements also enhance equipment reliability. The following definitions and symbolsCAUTION, WARNING, and DANGER as they are used comply with ANSI Z535.2, AmericanNational Standard for Environmental and Facility Safety Signs, and ANSI Z535.4, Product SSigns and Labels, issued by the American National Standards Institute. .

Safety Guidelines

• Always use caution and common sense, especially when unsafe conditions or potentihazardous voltages are present.

• Repairs must be performed by qualified service personnel only.

• To reduce the risk of electrical shock, do not operate equipment with the cover remov

• Never install telephone jacks in a wet location unless the jack is designed for that loca

• Never touch uninsulated telephone wires or terminals unless the telephone line is disconnected at the network interface.

• Never install telephone wiring during an electrical storm.

Antistatic Precautions

This product may contain static-sensitive devices that are easily damaged by ESD (electrosdischarge). ESD occurs when a person whose body has built up static electricity touches a cocomponent. ESD can cause computer components to fail. Take proper handling, groundingprecautionary ESD measures when installing parts or cards. Keep parts and cards in antistapackaging when not in use or during transport. If possible, use antistatic pads on floor and workbench. When handling components, always use an antistatic wrist strap connected to agrounded equipment frame or chassis. If a wrist strap is not available, periodically touch an unpainted metal surface on the equipment. Never use a conductive tool, like a screwdriver or a paper clip, to set switches.

Note Indicates a note. It is something you should be particularly aware of; something not readily apparenA note is typically used as a suggestion.

Important Indicates an emphasized note. It is something you should be particularly aware of; something not reapparent. Important is typically used to prevent equipment damage.

CAUTION indicates conditions or practices that can cause damage to equipment or losdata.

WARNING indicates an imminently hazardous situation which, if not avoided, may resuin minor to moderate injury. It may also be used to alert against unsafe practices.

DANGER indicates an imminently hazardous situation which, if not avoided, will result ideath or serious injury.

vi Xedge MSPx System Version 7.1.0 032R401-V710Configuration Guide Issue 4

Preface Compliance

by ch

k, the ted to t. See

our

ephone

ected

vide

s as e

to the ing an above

upplier. y give

wer ether.

ct the

an rface. e

ceed 5.

ComplianceFCC Part 68

Connection of data communications equipment to the public telephone network is regulatedFCC Rules and Regulations. This equipment complies with Part 68 of these regulations whirequire all of the following.

For single or multi-line equipment that connects to the telephone network via a plug and jacplug and jack must comply with the FCC Part 68 rules. This device is designed to be connecthe telephone or premises wiring, using a compatible modular jack which is Part 68 complianinstallation chapter for details.

If the unit causes harm to the telephone network, the telephone company may discontinue yservice temporarily and if possible, you will be notified in advance. If advance notice is not practical, you will be notified as soon as possible and will be advised of your right to file a complaint with the FCC. The telephone company may change its communication facilities, equipment, operations and procedures where reasonably required for operation. If so, the telcompany will notify you in writing. Any other repair or modification by a user voids the FCC registration and the warranty.

The APEX DDS1 has a DSX-1 interface. To use the public telephone network, it must be connto a registered CSU.

To connect the APEX DDS1 to the public telephone network the customer is required to prothe following information:

FCC Registration Number: AG6USA-23156-XD-NTelephone Company jack type: Provided by the registered CSU. Facility Interface Codes: T1 Interface - 04DU9-BN, 04DU9-DN, 04DU9-1KN, 04DU9-1ZNService Order Code: T1 Interface - 6.0N

Industry Canada NotificationThe Industry Canada label identifies certified equipment. This certification means that the equipment meets telecommunications network protective, operation and safety requirementprescribed in the appropriate Terminal Equipment Technical Requirements document(s). ThDepartment does not guarantee the equipment will operate to the user's satisfaction.

Before installing this equipment, users should ensure that it is permissible to be connected facilities of the local telecommunications company. The equipment must also be installed usacceptable method of connection. The customer should be aware that compliance with the conditions may not prevent degradation of service in some situations.

Repairs to certified equipment should be coordinated by a representative designated by the sAny repairs or alterations made by the user to this equipment, or equipment malfunctions, mathe telecommunications company cause to request the user to disconnect the equipment.

Users should ensure for their own protection that the electrical ground connections of the poutility, telephone lines and internal metallic water pipe system, if present, are connected togThis precaution may be particularly important in rural areas.

Caution: Users should not attempt to make such connections themselves, but should contaappropriate electric inspection authority, or electrician, as appropriate.

Notice: The Ringer Equivalence Number (REN) assigned to each terminal device provides indication of the maximum number of terminals allowed to be connected to a telephone inteThe termination on an interface may consist of any combination of devices subject only to threquirement that the sum of the Ringer Equivalence Numbers of all the devices does not ex

Electromagnetic CompatibilityThis Class A digital apparatus complies with Canadian ICES-003.

032R401-V710 Xedge MSPx System Version 7.1.0 viiIssue 4 Configuration Guide

Preface Compliance

s as e

to the ing an above

upplier. y give

wer ether.

ct the

n rface. e

ceed 5.

e ues

ra à la

tallé ossible ice dans

é par le r un

de

source en a, rurales.

voir as.

e le ’une e de

Industry Canada NotificationThe Industry Canada label identifies certified equipment. This certification means that the equipment meets telecommunications network protective, operation and safety requirementprescribed in the appropriate Terminal Equipment Technical Requirements document(s). ThDepartment does not guarantee the equipment will operate to the user's satisfaction.

Before installing this equipment, users should ensure that it is permissible to be connected facilities of the local telecommunications company. The equipment must also be installed usacceptable method of connection. The customer should be aware that compliance with the conditions may not prevent degradation of service in some situations.

Repairs to certified equipment should be coordinated by a representative designated by the sAny repairs or alterations made by the user to this equipment, or equipment malfunctions, mathe telecommunications company cause to request the user to disconnect the equipment.

Users should ensure for their own protection that the electrical ground connections of the poutility, telephone lines and internal metallic water pipe system, if present, are connected togThis precaution may be particularly important in rural areas.

Caution: Users should not attempt to make such connections themselves, but should contaappropriate electric inspection authority, or electrician, as appropriate.

Notice: The Ringer Equivalence Number (REN) assigned to each terminal device provides aindication of the maximum number of terminals allowed to be connected to a telephone inteThe termination on an interface may consist of any combination of devices subject only to threquirement that the sum of the Ringer Equivalence Numbers of all the devices does not ex

Avis D’industrie Canada

L’étiquette d’Industrie Canada identifie le matériel homologué. Cette étiquette certifie que le matériel est conforme aux normes de protection, d’exploitation et de sécurité des réseaux dtélécommunications, comme le prescrivent les documents concernant les exigences techniqrelatives au matériel terminal. Le Ministère n’assure toutefois pas que le matériel fonctionnesatisfaction de l’utilisateur.

Avant d’installer ce matériel, l’utilisateur doit s’assurer qu’il est permis de le raccorder aux installations de l’entreprise locale de télécommunication. Le matériel doit également être insen suivant une méthode acceptée de raccordement. L’abonné ne doit pas oublier qu’il est pque la comformité aux conditions énoncées ci-dessus n’empêche pas la dégradation du servcertaines situations.

Les réparations de matériel homologué doivent être coordonnées par un représentant désignfournisseur. L’entreprise de télécommunications peut demander à l’utilisateur de débrancheappareil à la suite de réparations ou de modifications effectuées par l’utilisateur ou à causemauvais fonctionnement.

Pour sa propre protection, l’utilisateur doit s’assurer que tous les fils de mise à la terre de la d’énergie électrique, des lignes téléphoniques et des canalisations d’eau métalliques, s’il y sont raccordés ensemble. Cette précaution est particulièrement importante dans les régions

Avertissement: L’utilisateur ne doit pas tenter de faire ces raccordements lui-même; il doit arecours à un service d’inspection des installations électriques, ou à un électricien, selon le c

Avis: L’indice d’équivalence de la sonnerie (IES) assigné à chaque dispositif terminal indiqunombre maximal de terminaux qui peuvent être raccordés à une interface. La terminaison dinterface téléphonique peut consister en une combinaison de quelques dispositifs, à la seulcondition que la somme d’indices d’équivalence de la sonnerie de tous les dispositifs n’excèpas 5.

La Compatibilité d’ Eléctro-magnetique

Cet appareil numerique de la classe A est conforme a la norme NMB-003 du Canada.

viii Xedge MSPx System Version 7.1.0 032R401-V710Configuration Guide Issue 4

Preface Before You Begin

s. nicht, n ung

nform

ent to es.

s meet on

edge

nu.

versa.

ec-assis

DeutschlandInstallations Anweisungen: Installieren Sie die Telefonleitungen nicht während eines GewitterInstallieren Sie die Telefonleitungen nicht in einem feuchten Raum, auβer die Dose entspricht denVorschriften für Feuchträume. Berühren Sie unisolierte Telefonleitungen oder Einrichtungen auβer diese sind vom Telefonnetz getrennt. Vorsicht bei der Installierung oder Änderung voTelefonleitungen. Achtung: Es gibt keine durch den Benutzer zu wartende Teile im Gerät. Wartdarf nur durch qualifiziertes Personal erfolgen.

Before You BeginInspect all shipping cartons and their contents for visible damage. If any damage is found, iyour supplier immediately.

Site Requirements

Inspect the site, particularly the equipment room, before unloading or unpacking the equipmensure the following requirements are met. Refer to your Xedge chassis manual for guidelin

• Ensure that grounding provisions are adequate.

• Ensure that front and rear access to the equipment is adequate.

• Ensure that heating, ventilation and air conditioning systems are operating properly.

• Ensure adequate air flow and sufficient lighting.

• Check the power resources to ensure that the current ratings of the branch current feedthe requirements of the chassis to be installed. Ensure that redundant power feeds areseparate circuit breakers.

Installation & Connectivity

• Check that all switches, jumpers and connectors are set up according to your networkrequirements.

• Refer to the Xedge Chassis Installation Manual for details on installing devices in your Xchassis and making connections to the network.

Accessing the Xedge SwitchThe Xedge Version 7.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-

• Multiple Telnet root sessions are allowed to superusers only.

• For information on accessing the Xedge switch via the Prosphere NMS, refer to the corresponding documentation listed in the front of this manual.

Note IMPORTANT! An electrostatic discharge (ESD) wrist strap can be plugged into the wrist strap conntors on the front and rear of the chassis, or can be clamped to any open ground connection on the chto prevent equipment damage.

032R401-V710 Xedge MSPx System Version 7.1.0 ixIssue 4 Configuration Guide

Preface Before You Begin

ge Root old

s or Switch tom of

in ppear-re ver-

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! When accompanying configuration procedures, all Xedge terminal interface screensthis manual are provided as examples only. Do not copy values from example screens. The actual aance of menus and screens will vary, depending on your system environment and the Xedge softwasion controlling a particular module.

ROOT MENUOPTIONS

GROUP NUMBERSELECTIONS

MENUOPTIONS

Version ID

Event Message

Hartford: Slot 0 Root Menu 710v12\700

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

x Xedge MSPx System Version 7.1.0 032R401-V710Configuration Guide Issue 4

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

032R401-V710 Xedge MSPx System Version 7.1.0 xiIssue 4 Configuration Guide

Preface Support Services and Training

xii Xedge MSPx System Version 7.1.0 032R401-V710Configuration Guide Issue 4

oller pter ands.

s cell s and /ices.

ric

. The fabric

ode:

elay

ell ath ttach the

ility

across

s aded

gement.

are are and uration

Chapter 1: Xedge Switch Overview

Introduction to Xedge Version 7.1

An Xedge Multi-Service Packet Exchange (MSPx) switch is comprised of Packet Slot Contrmodules and Line Interface Modules (LIMs) controlled by Version 7.1 switch code. This chadescribes the hardware modules, Version 7.1 software organization, and available file comm

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 or PCx slot controllers are sufficient for that 1RU chassis.

Note For Xedge Switch Fabric information, refer to the Xedge Hardware Installation Manual (032R440).

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. This multi-service capabcan interconnect remote enterprise sites with emerging Ethernet/IP and legacy servicesan 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-V710 Xedge MSPx System Version 7.1.0 1-1Issue 4 Configuration Guide

Xedge Switch Overview Introduction to Xedge Version 7.1

s

he

, the at the

le is rs. The

, the rder to

y Main

kets

Module ignals.

fer to

t. ersion,

Version 7.x Slot Controllers and LIMs

Xedge Version 7.x software controls the following slot controllers and LIMs, described in thidocument:

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

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

• LIMs (See Chapter 7, Line Interface Modules )

Slot-0 Controller Functions

In an Xedge MSPx switch, ISG2 or PCx slot controllers are capable of slot-0 functionality. TISG2 is also capable of slot-0 redundancy. Slot-0 functions are listed below.

• 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 manager port service and can support a direct terminal interface. Since onlslot-0 and Standby slot-0 have a physical manager port, communication with non-slot-0 modules must be via the IP address that provides Telnet access.

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

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 1-2 in the Xedge Hardware Installation Guide (032R440).

Note To install Xedge modules, consult the hardware and shelf manuals listed in the front of this documenTo 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.1.0 032R401-V710Configuration Guide Issue 4

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.



switch 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 switchsoftware 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 712\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 710v12\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 exisiting 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

elow.

ese, 4 to 79.

with to

16, AP

for

t.

Cx, SAPs e

SAPs and ATM Logical PortsThe PCx or ISG2 slot controller supports 96 Signaling Access Points (SAPs) as described bThe SAP defaults 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 (they are not connected to anything).

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.

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 following limitations are in effect the PCx:

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

• 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

ted in

t.

Routing & Interfaces

The routing function on the ISG2 and PCx controllers support interface connections as depicTable 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

IF Index (ISG2) IF Index (PCX) 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


stalled ard up, a the ide the

You

n table lid IP

C, 0 Ver. s.

e

Chapter 2: Accessing Slot Controllers

Management Access OverviewThis chapter describes accessing Xedge ISG2 or PCx slot controllers and associated LIMs inin your Xedge switch via a craft or Telnet management interface. Xedge supports the standSimple Network Management Protocol Management Information Base II (SNMP MIB II) groand a series of Enterprise MIB extensions for total management and control of the switch viSNMP interface. A series of SNMP Traps are supported to ensure that events happening insXedge network are reported to an external management station.

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 network supervisor to restrict access to users with vaaddresses and SNMP community strings. Refer to Chapter 4, Basic Slot-0 Configuration for details.

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.


Accessing Slot Controllers Craft/Telnet Connections

gement

100

panel

erial

Craft/Telnet ConnectionsVT100 terminal access to a menu driven configuration system is supported via the serial management port. Telnet access is supported from any IP host connected to the Xedge mananetwork.

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).

1. Connect your PC or SUN workstation serial port to the Manager (craft) port on the back of the Xedge shelf. Table 2-1 lists serial cables required for each Xedge shelf system.

• For a SUN workstation, use the serial cable to connect the ttyb port on the workstation to the craft port on the rear panel of the Xedge shelf.

• For a PC, use the serial cable to connect the com1 or com2 port to the craft port on the rear panel of the Xedge shelf.

• For redundant slot-0 configurations, you must also use a Y-cable with the correct scable for your PC or SUN workstation.

2. 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

Table 2-1 Serial Craft Port Cables

System Connection Required Xedge Shelf GDC Part No. Cable Description

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

SUN Workstation 6160 28H346 Serial, DB25M to DB9M

PC 6640 or 6645 28H303 Serial, DB9F to DB25M

PC 6160 or 6280 27H329 Serial, DB9F to DB9M

Y-Cable for Redundant Slot-0 28H350-X06 Serial Y, DB9F to dual DB9Ms

Y-Cable for Redundant Slot-0 28H618-X06 Serial Y, DB25F to dual DB25Ms


Accessing Slot Controllers Security Features

rs.

ew

Security FeaturesChange Root Password

In a new system, it is necessary to change the default root password by editing the users.cfg file in the root directory of Slot-0, as described below.

1. Log in as root , or use a local (craft) connection with an access level greater than 0.

2. From the Root Menu, type F to select File system . The File Operations screen appea

3. Type A to select Alter file . The Select File screen appears.

4. Type users.cfg to display the file. A sample screen is shown below.

Figure 2-1 users.cfg File

5. With the cursor on the first line (name=root ), press CTRL-X to move to the next line which is the password field (encrypt= ). Press CTRL-Y to delete the encrypt= entry.

6. Press the Enter key to add a new line, then press CTRL-E to move up one line.

7. Type password= [xxx] where [xxx] is your new password. The Insert screen displays the npassword, for example “SECRET” as shown in Figure 2-2.

Figure 2-2 Insert Screen

8. If the screen displays changes that are not correct, press CTRL-K followed by Q to abandon the edit session and start again.

9. If the screen displays the changes correctly, press CTRL-K followed by X to save your changes and exit. Then press X to return to the Root Menu.

/users.cfg L0 C0 Insert ^J for help. Free: 118

name=root <encrypt=6640N2 <terminal=vt100 <level=15 <' <name=GDC <encrypt=tPo0a <terminal=vt100 <level=1 <' <name=local <encrypt=9d2sd <terminal=vt100 <level=0 <' <name=telnet <encrypt=Lq02U <terminal=vt100 <level=0 <


name=root <password=SECRET <terminal=vt100 <level=15 <' <name=GDC <encrypt=tPo0a <terminal=vt100 <level=1 <' <name=local <encrypt=9d2sd <terminal=vt100 <level=0 <' <name=telnet <encrypt=Lq02U <terminal=vt100 <level=0 <



curity; bles,

m

tions dure

User Read/Write Access

User access to the Xedge terminal interface menu is password protected, with two levels of seRead-Only and Read-Write. The Read-Write option allows values to be written to MIB variachanging the operation of the switch.

When you log in as the root user, you have read and write access to all of the Xedge systefunctions. When you create another user with a login other than root , you can permit read-only or limited editing write options for that new user. The following table compares the Xedge funcavailable to via root access, a read-only access, or a limited access. A step-by-step procefor creating new read-only users follows the table.

Create Read-only Users

1. At the Root Menu, type F to select File system . The File Operation screen appears.

2. Type A to select Alter file . The Select File screen is displayed.

3. Type users.cfg to display the users.cfg file, as shown below.

Figure 2-3 Example: users.cfg file Screen

Table 2-2 User Access Options

Function Root Access Read-only Access

TCB Status All All

Diagnostics All None

Events All All except: Clear event table and Save to disk

File System All All except: Alter file, Copy file, Erase file, Format media, Link File, set Product info, Rename file and TFTP

Internal Status All All

Load File Yes None

PSI Management All All except: Abort task, Run file, Single step and Trace

self Restart Yes All except: Clear Restart Count

Telnet Yes Yes

User name Yes Yes

Warm start Yes None

sVc routing Yes All except: Save, Copy, Delete, Load, Edit and New Entry


name=root <encrypt=6640N2 <terminal=vt100 <level=15 <' <name=GDC <encrypt=tPo0a <terminal=vt100 <level=1 <' <name=local <encrypt=9d2sd <terminal=vt100 <level=0 <' <name=telnet <encrypt=Lq02U <terminal=vt100 <level=0 <



r.

ows

4. With the cursor on the first line (name= root in the example above), enter CTRL-X repeatedly until the cursor is below the last entry.

5. Press the Enter key to add a new line.

6. Press CTRL-X to move the cursor down one line.

7. Type name=OPERATOR, where “Operator” will be the login name of the new user.


9. Type password=CHECKING , where “CHECKING” will be the password for the new use


11. Type T erminal =vt100 , where “vt100” is the name of the terminal.

Note Changing the level= line is not necessary. By entering a user name other than root, the system knthat it is a read-only level user.

Figure 2-4 Adding a Read-Only User

12. If the screen displays changes that are not correct, press CTRL-K followed by Q to abandon the edit session and start again.

13. If the screen displays the changes correctly, press CTRL-K followed by X to save your changes and exit. Press X once more to return to the Root Menu.


name=root <encrypt=6640N2 <terminal=vt100 <level=15 < <name=OPERATOR <password=CHECKING <terminal=vt100 <

name=GDC <encrypt=tPo0a <terminal=vt100 <level=1 < <name=telnet <encrypt=Lq02U <terminal=vt100 <level=0 <



he rear in slot-r

witch

lower

uide

rminal that

on the

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).

Secure Copy Protocol (SCP/SSH)A future version of Xedge 7.1 is planned to support the Secure Copy Protocol (SCP) at the teinterface over a secure shell (SSH) tunnel, using PuTTY or other terminal emulation programcan act as a client for the SSH protocol. Contact your Xedge representative for information availability of this feature.


Chapter 3: Hardware Overview

ISG2 Hardware OverviewXedge Switch Version 7.10 and later supports the IP Services Gateway (ISG2) Slot Controller. The ISG2 is a single-width slot controller for Xedge Switches.

Features & Benefits• Lowers costs of branch/remote IP access-to-centralized routing resources.

• Supports OSPF, RIP2 Routing, and deterministic static routes.

• Guarantees quality of service by routing IP traffic across Xedge networks based on destination IP address & IP classification.

• Reliably extends IP connectivity and services on converged networks carrying voice, multimedia and low-speed data applications that require explicit service quality.

• Traffic shaping; IP QoS

• Establishes a resilient foundation for future application/feature development.

• Provides standard-based SNMP management interface for Xedge switches.

• Installs in a single slot 0 or non-slot 0 position in any Xedge 6000 chassis.

Traffic Management

ISG2 offers superior traffic management capabilities to assure that priority traffic (for example, real-time IP flows such as IP video packets) is not perturbed when the destination route encounters congestion from bursty traffic. Each ISG2 module acts on priorities based on destination IP addresses, and assures QoS across the wide-area network. Through intelligent tunnel management and queueing, ISG2 buffers up to 1000 frames to handle burst traffic.

Routing

ISG2 determines routes based on IP destination addresses. ISG2 builds layer-3 tunnels across the Xedge cloud to other ISG2s and selected Layer-3 devices (e.g., centralized router resources or external routers connected to the network via MPLS or ATM interfaces). Each ISG2 supports more than 128 IP tunnels which may be established using OSPF, RIP2, or deterministic MPLS/ATM routes, or by selecting a specific ISG2 tunnel as a local site’s default gateway. ISG2 can be configured with auto re-routing, along with variations on limited and restricted re-routing.

Power Up or Reboot Sequence1. All three LED indicators off.

2. LNK FLT on, FLT and RUN alternately flashing.

3. RUN on, FLT flashing, LNK FLT on.

4. RUN on, FLT off, followed by normal LED indications as described in Table 3-1.

MGMT

USER

FLTRUN

LNKFLT

ISG2


Hardware Overview ISG2 Hardware Overview

rased diately

he

ISG2 Card Layout and Installation

Figure 3-1 ISG2 Card Layout

Note IMPORTANT ! Be aware that when S1 is set to F, all user configuration files and XOS code will be efrom the card. This setting should be used with caution, and you must reset S1 back to 0, 4 or 8 immeafter reboot to prevent inadvertent erasure with subsequent reboots.

Note Additional S1 settings can be used to reboot the card to kernel for troubleshooting purposes, under tguidance of your authorized Xedge field service representative.

Table 3-1 ISG2 Controls and Indicators

Items Designation Description

Front Panel LEDs

FLT LED FLT (red) is normally off; Lit when a problem prevents the Slot Controller from functioning.

RUN LED RUN (green) illuminates when the Slot Controller is powered on and operating.

LNK FLT LNK FLT (red) is not supported in this release.

Jumper P3 Only for use in factory tests. For normal operation, this jumper must be set to Pins 2 and 3, as shown above.

10/100 8-pin modular jacks

MGMT Connects to Prosphere Server or the network of the ProSphere Server.

USER Connects to the Ethernet network.

16-position Rotary Switch

S1(See

Figure 3-2)

Set to 0 when ISG2 is in Main Slot 0 of any Xedge 6000 chassis.Set to 4 when ISG2 is in Standby Slot 0 of Xedge 6280, 6640 or 6645 chassis.Set to 8 when ISG2 is in Non-slot 0 of any Xedge chassis (slot 0 must be PCx or ISG2).Set to F to delete all user-defined configuration files and XOS code (i.e. to factory default).

S1

P3

ISG2 Base Card

BACKPLANECONNECTORS

To SwitchFabric

ToBackplane

3

1

MG

MT

US

ER

FLT

RU

N

LNK

FLT

ISG

2

ISG2 Front Panel


Hardware Overview ISG2 Hardware Overview

.

Figure 3-2 Installing the ISG2 in an Xedge Chassis

Note Refer to Table 3-1 to properly set the S1 rotary switch on the ISG2 for the intended chassis and slot.Refer to Chapter 4, Basic Slot-0 Configuration for complete instructions on slot-0 configuration and operational guidelines. Slot-0 redundancy is not supported in an Xedge 6002 or Xedge 6160 chassis

ESDStrap

3

2

1

0

SF

SLOT 2 Slot Controller Module

Switch Fabric


6

5

4

3

2

1

0

FANTRAY

ESDSF

SF(STDBY)

0(STDBY)






Switch Fabric

Switch Fabric

Xedge 6640/6645

SLO

T 6

Slo

t Con

trolle

r M

odul

e

SLO

T 5

Slo

t Con

trolle

r M

odul

e

SLO

T 4

Slo

t Con

trolle

r M

odul

e

SLO

T 3

Slo

t Con

trolle

r M

odul

e

SLO

T 2

Slo

t Con

trolle

r M

odul

e

SLO

T 1

Slo

t Con

trolle

r M

odul

e

Sw

itch

Fabr

ic

Sw

itch

Fabr

ic

(Bla

nk)

SLO

T 9

Slo

t Con

trolle

r M

odul

e

SLO

T 1

0S

lot C

ontro

ller

Mod

ule

SLO

T 1

1S

lot C

ontro

ller

Mod

ule

SLO

T 1

2S

lot C

ontro

ller

Mod

ule

SLO

T 1

3S

lot C

ontro

ller

Mod

ule

SLO

T 1

4S

lot C

ontro

ller

Mod

ule

SLO

T 1

5S

lot C

ontro

ller

Mod

ule

(Bla

nk)

SLO

T 7

Slo

t Con

trolle

r M

odul

e

Slot 0 ISG2in Main Slot 0/Stdby Slot 0

Non Slot 0Non Slot 0

Xedge 6160

Xedge 6280

NonSlot 0

Slot 0 ISG2 inMain Slot 0 /Stdby Slot 0

Slot 0 ISG2in Slot 0

NonSlot 0

MGMT

USER

FLTRUN

LNKFLT

ISG2

SLO

T 8

Slo

t Con

trolle

r M

odul

e

MGMT

USER

FLTRUN

LNKFLT

ISG2

MG

MT

US

ER

FLT

RU

N

LNK

FLT

ISG

2


MG

MT

US

ER

FLT

RU

N

LNK

FLT

ISG

2

Slot Controller Module

MG

MT

US

ER

FLT

RU

N

LNK

FLT

ISG

2

SLOT 1

ESDStrap

1

0

Xedge 6002

Slot Controller Module

MG

MT

US

ER

FLT

RU

N

LNK

FLT

ISG

2

SLOT 1

Slot 0 ISG2in Slot 0

NonSlot 0


Hardware Overview PCx Hardware Overview

PCx Hardware OverviewXedge Switch Version 7.10 and later supports the Xedge Packet Cell Switch (PCx). PCx is a dual-width base card with two daughtercards to support all features found in the ISG2 along with the added features listed below.

Features & Benefits

• Complies with Metro Ethernet Forum (MEF) compliant Ethernet Private Line

• High speed, high capacity packet switching

• Dual control plane for MPLS or ATM transport

• Supports layer 2 or layer 3 VPNs

• Flexible Routing includes PNNI, OSPF-TE

• Reduces OPEX and CAPEX

Traffic Management

PCx offers superior traffic management capabilities to assure that priority traffic (for example, real-time IP flows such as IP video packets) is not perturbed when the destination route encounters congestion from bursty traffic. Each PCx module acts on priorities based on destination IP addresses, and assures QoS across the wide-area network. Through intelligent tunnel management and queueing, PCx buffers up to 1000 frames to handle burst traffic.

Routing

PCx determines routes based on IP destination addresses. PCx builds layer-3 tunnels across the Xedge cloud to other PCx devices and selected Layer-3 devices (e.g., centralized router resources or external routers connected to the network via MPLS or ATM interfaces). Each PCx supports more than 256 IP tunnels which may be established using OSPF, RIP2, or deterministic MPLS/ATM routes, or by selecting a specific PCx tunnel as a local site’s default gateway. PCx can be configured with auto re-routing, along with variations on limited and restricted re-routing.

Ethernet Connections

The Ethernet interface is provided by the GENPC daughter card on the PCx base card. Front panel connectivity and status LEDs are as follows:

• Gigabit Ethernet connectivity is provided by two GbE ports which require small format plugable (SFP) inserts if they are to be used. The GbE Activity LED provided for each port is described in Table 3-2.

• Fast Ethernet connectivity is provided by eight 10/100 Mbps ports. The two FE Activity LEDs provided for each port are described in Table 3-2.

Power Up or Reboot Sequence1. All three LED indicators off.

2. LNK FLT on, FLT and RUN alternately flashing.

3. RUN on, FLT flashing, LNK FLT on.

4. RUN on, FLT off, followed by normal LED indications as described in Table 3-1.

FLTRUN

LINKFLT

14

58

MGMT

USER

GbE

12

GbE

1

GbE

2

FE

PCx



rased diately

he

PCx Card Layout and Installation

Note IMPORTANT ! Be aware that when S1 is set to F, all user configuration files and XOS code will be efrom the card. This setting should be used with caution, and you must reset S1 back to 0, 4 or 8 immeafter reboot to prevent inadvertent erasure with subsequent reboots.

Note Additional S1 settings can be used to reboot the card to kernel for troubleshooting purposes, under tguidance of your authorized Xedge field service representative.

Table 3-2 PCx Controls and Indicators

Items Designation Description

Front Panel LEDs

FLT LED FLT (red) is normally off; Lit when a problem prevents the Slot Controller from functioning.

RUN LED RUN (green) illuminates when the Slot Controller is powered on and operating.

LNK FLT LNK FLT (red) is not supported in this release.

GbE 1/2 Two Gigabit Ethernet ports; LEDs indicate active connection when lit.

FE 1 - 8 Eight 10/100 Mbps Fast Ethernet ports: Left (top) LED indicates 100 Mbps operation when lit. Right (bottom) LED indicates active connection when lit.

Jumper P3 Only for use in factory tests. For normal operation, this jumper must be set to Pins 2 and 3, as shown above.

10/100 8-pin modular jacks

MGMT Connects to Prosphere Server or the network of the ProSphere Server.

USER Connects to the Ethernet network.

16-position Rotary Switch

S1(See

Figure 3-3)

Set to 0 when Slot 0 PCx is in main slot 0 and slot 1 of Xedge 6160/6280.Set to 0 when Slot 0 PCx is in standby slot 0 and slot 8 of Xedge 6640/6645.Set to 8 when PCx is in non-slot 0 of any chassis (slot 0 must be a PCx or ISG2).Set to F to delete all user-defined configuration files and XOS code (i.e. to factory default)

S1

P3

PCx Base Card

BACKPLANECONNECTORSTo Switch

FabricToBackplane

3

1

PCx Front Panel

LPM

GENPC

To LIM1

2xGbE

8xFE

FLT

RU

N

LIN

KF

LT

1 2 3 4

MG

MT

US

ER

GbE

1 2GbE1

GbE2

FE

PC

x

1 4

5 8

To LIM2



Figure 3-3 Installing the PCx in an Xedge Chassis

Note Refer to Table 3-2 to properly set the S1 rotary switch on the PCx for the intended chassis and slot.

Note The PCx card cannot be installed in Main Slot 0 of Xedge 6640 or 6645 chassis.

Note For any Xedge chassis, Slot 0 PCx redundancy cannot be provided.

ESDStrap

3

2

1

0

SF


Switch Fabric


6

5

4

3

2

1

0

FANTRAY

ESDSF

SF(STDBY)

0(STDBY)






Switch Fabric

Switch Fabric

SLOT 0 Standby Slot Controller Module

Xedge 6640/6645

SLO

T 6

Slo

t Con

trolle

r M

odul

e

SLO

T 5

Slo

t Con

trolle

r M

odul

e

SLO

T 4

Slo

t Con

trolle

r M

odul

e

SLO

T 3

Slo

t Con

trolle

r M

odul

e

SLO

T 2

Slo

t Con

trolle

r M

odul

e

SLO

T 1

Slo

t Con

trolle

r M

odul

e

SLO

T 0

Mai

nS

lot C

ontro

ller

Mod

ule

Sw

itch

Fabr

ic

Sw

itch

Fabr

ic

(Bla

nk)

SLO

T 9

Slo

t Con

trolle

r M

odul

e

SLO

T 1

0S

lot C

ontro

ller

Mod

ule

SLO

T 1

1S

lot C

ontro

ller

Mod

ule

SLO

T 1

2S

lot C

ontro

ller

Mod

ule

SLO

T 1

3S

lot C

ontro

ller

Mod

ule

SLO

T 1

4S

lot C

ontro

ller

Mod

ule

SLO

T 1

5S

lot C

ontro

ller

Mod

ule

(Bla

nk)

SLO

T 7

Slo

t Con

trolle

r M

odul

e

FLTRUN

LINKFLT

LINK

12

34

MGMT

USER

GbE

12

GbE

1

GbE

2

FE

PCx

Slot 0 PCxin Slot 0 STBY and Slot 8

Non Slot 0Non Slot 0

Xedge 6160

Xedge 6280

FLT

RU

N

LIN

KF

LT

LINK1 2 3 4

MG

MT

US

ER

GbE

1 2GbE1

GbE2

FE

PC

xNon

Slot 0

Slot 0 PCxin Slot 0

and Slot 1F

LTR

UN

LIN

KF

LT

LINK1 2 3 4

MG

MT

US

ER

GbE

1 2GbE1

GbE2

FE

PC

x

Slot 0 PCxin Slot 0

and Slot 1

NonSlot 0

ESDStrap

1

0

Xedge 6002Slot 0 PCxin Slot 0

and Slot 1

NonSlot 0

FLT

RU

N

LIN

KF

LT

LINK1 2 3 4

MG

MT

US

ER

GbE

1 2GbE1

GbE2

FE

PC

x



lity and

to the

ection Ms.

varied w.

ed 0).

PCx AssembliesThe PCx module consists of a PCx base card, a GENPC daughtercard and a LIM PersonaModule (LPM) daughtercard. This assembly can support two Line Interface Modules (LIM1 LIM2) installed at backplane connectors, as shown in the figure accompanying Table 3-2

• The PCx base card has a single connection to the main backplane, a single connection switch fabric and a single connection to LIM1.

• The LPM daughtercard provides an additional connection to the switch fabric, and a connto a second LIM (LIM2). The type of LPM in use will determine the type and location of LI

• The GENPC daughtercard provides Ethernet connectivity at the PCx front panel.

Note At the Physical Layout screen, a PCx with LIM cards installed will be displayed as Unknown . This does not affect the functionality of the PCx or its associated LIMs.

LPM/LIM Applications

The PCx is shipped with one of three types of LPM boards. Depending on the LPM in use, a combination of SERDES or Utopia LIMs can be installed as LIM1 and LIM2, as defined belo

Supported Line Interface Modules (LIMS)

Table 3-3 lists Xedge LIMs for use with PCx. The OC-N/STM-N is a SERDES-type LIM, describlater in this chapter. All Utopia LIMs are described in the Xedge Hardware Manual (032R44

PCx Assembly LPM in Use LIM1 (behind PCx) LIM2 (behind LPM)

200P001-001 LPM-1 UTOPIA LIM UTOPIA LIM

200P002-001 LPM-2 UTOPIA LIM SERDES LIM200P004-001 LPM-4 SERDES LIM SERDES LIM

Table 3-3 Xedge LIMs for PCx Module

Xedge LIMs Application Part No. Type PCx Compatibility

STM-N/OC-N 8-Port OC-N 200P003-001 SERDES Supported155M-2 2-port OC-3, short reach with single port APS 032P150-011 UTOPIA Supported155I-2 2-port OC-3, intermed. reach with single port APS 032P150-012 UTOPIA Supported

155L-2 2-port OC-3, long reach with single port APS 032P150-013 UTOPIA Supported155M-APS 2-port OC-3, short reach with dual port APS 032P150-001 UTOPIA Supported155I-APS 2-port OC-3, intermed. reach with dual port APS 032P150-002 UTOPIA Supported

155L-APS 2-port OC-3, long reach with dual port APS 032P150-003 UTOPIA SupportedDS3-2C 2-port DS3 LIM for ATM transport 032P046-001 UTOPIA (Future)DS1-2CS 2-port DS1 with voice 032P098-012 UTOPIA (Future)DS1-4CS 4-port DS1 with voice 032P098-011 UTOPIA (Future)E1-2CS 2-port E1 with voice 032P098-002 UTOPIA (Future)E1-4CS 4-port E1 with voice 032P098-001 UTOPIA (Future)E3-2C 2-port E1 LIM for ATM transport 032P108-001 UTOPIA (Future)HSSI-DCE 2-port HSSI LIM, Frame (DCE) 032P022-001 UTOPIA (Future)HSSI-DTE 2-port HSSI LIM, Cell (DTE) 032P022-002 UTOPIA (Future)SI-2C 2-port serial I/O 032P094-002 UTOPIA (Future)SI-4C 4-port serial I/O 032P094-001 UTOPIA (Future)155E-2 2-port STM-1 electrical LIM for ATM transport 032P151-001 UTOPIA (Future)LCE-16 Legacy circuit emulation 16 link LIM 032P187-001 UTOPIA (Future)DSX1-IMA 16 link Inverse Multiplexing for ATM LIM 032P153-003 UTOPIA (Future)E1-IMA 16 link Inverse Multiplexing for ATM LIM 032P153-013 UTOPIA (Future)


Hardware Overview OC-N / STM-N Line Interface Module

OC-N / STM-N Line Interface ModuleThe OC-N / STM-N is an 8-port optical LIM intended for use with PCx slot controller for high speed ATM connections and Packet over SDH/SONET. It supports a maximum cell rate of 1,412,830 cells/sec and a physical line rate of 622 Mbps.

Front Panel Features

The front panel connectors provide easy port access to the eight ports. Each port requires a Singlemode or Multimode SFPs (Small Format Plugable) insert to be operable. Available SFPs are listed below:

• Singlemode: OC-N/STM-N SR (2K) 1310nm

• Singlemode: OC-N/STM-N IR (15K) 1310nm

• Singlemode: OC-N/STM-N LR (40K) 1310nm

• Singlemode: OC-N/STM-N LR (80K) 1550nm

• Multimode: OC3/STM1-SR (2k) 1310 nm

The front panel LEDs indicate LIM communication status. All LEDs are controlled by the PCx software. There are two LED indicators associated with each port.

• When lit, IS indicates that the port is enabled.

• When lit, AL indicates an alarm condition.

Cabling

Optical connector cables compatible with the installed SFPs are user-supplied.

Jumpers

Jumpers on the OC-N/STM-N LIM are for factory use only.

LIM Installation Guidelines

Any LIM occupies a rear panel slot of the switch that is associated with its corresponding slot controller. When handling LIMs, always use an antistatic wrist strap to prevent static discharge damage to the electronic circuits. Refer to the Xedge Chassis Installation Guide (032R410) for additional information and procedures specific to your chassis.

1. Install the LIM into an empty PCx slot at the back panel of the chassis.

2. Insert the edges of the module into the tracks of the slot and slide the module inward until it stops. (LIMs are “hot-swappable”.)

3. Determine your LIM application by referring to the matrix on page 3-9 and configure the LIM accordingly.

4. Connect the appropriate I/O line(s) to the LIM’s front panel input connectors using the proper cables.

OC-NSTM-N

AL IS

LIN

K 7

AL IS

LIN

K 6

AL IS

LIN

K 5

AL IS

LIN

K 4

AL IS

LIN

K 3

AL IS

LIN

K 2

AL IS

LIN

K 1

AL IS

LIN

K 0



ard S)

r to

OC-N/STM-N LIM Applications

The OC-N/STM-N LIM can be configured to support a variety of LIM applications. The LIM cis physically divided into two parts of four links each. The following matrix demonstrates thepermitted link locations for each LIM application, including Automatic Protection Switching (APapplications.

Note The limitation of the switch fabric is two OC-3s.

Note For detailed information on configuring the OC-N/STM-N LIM for use with the PCx Slot Controller, refeChapter 7, Line Interface Modules .

Permitted Link Locations

LIM Applications Link0 Link1 Link 2 Link 3 Link 4 Link 5 Link 6 Link 7

Eight OC-3s OC-3 OC-3 OC-3 OC-3 OC-3 OC-3 OC-3 OC-3

Four OC-3s with APS OC-3 APS OC-3 APS OC-3 APS OC-3 APS

Two OC-3s; One OC-12 OC-3 OC-3 -- -- OC-12 -- -- --

Two OC-3s with APS; One OC-12 with APS

OC-3 APS OC-3 APS OC-12 APS -- --

Four OC-3s; One OC-12 OC-12 -- -- -- OC-3 OC-3 OC-3 OC-3

Two OC-3s with APS; One OC-12 with APS

OC-12 APS -- -- OC-3 APS OC-3 APS

Two OC-12s with APS OC-12 APS -- -- OC-12 APS -- --


slot lers, and

ave

nd

dge

the

C, 0 Ver. s.

. Note m time

e

r 21:08.

Chapter 4: Basic Slot-0 Configuration

OverviewXedge Version 7.x requires a properly configured Xedge Packet Controller (PCX or ISG2) in0. This chapter provides basic slot-0 configuration procedures that apply to both slot controlexcept where noted. For a brief introduction to Xedge command line interface (CLI) menus screens, refer to Navigating Xedge Menus and Screens in the Preface of this document. Topics inthis chapter include:

• Current Time Format

• Slot-0 IP Addressing

• Slot-0 Configuration

• SNMP Authentication

• Slot-0 Redundancy

Before You BeginBefore you begin configuration of slot controllers and LIMs in the Xedge switch, you must halready performed the following procedures:

• 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.

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

our oller

.

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. Refer to yXedge Hardware Installation Guide (032R440) for more information on connecting the contrto your network manager.

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 oes not

s a ntry.

ns,

option

. To do

esses, e

the

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 600chasssis (does not support Switch Fabric modules), or the 4-slot Xedge 6160 chassis ( dsupport 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 no. to advance to the proper slot, 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 Hardware Installation Guide (032R440).

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 0s.

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 does not support LIMs


Basic Slot-0 Configuration SNMP Authentication

NMS iated cific

MP

,

able

NMP t .

SNMP Authentication

Each slot controller has an SNMP Authentication Table which controls whether one or more in the network is allowed SNMP access, SNMP Discovery and SNMP Trap privileges assocwith the switch. An entry configured in the SNMP Athentication Table will authenticate a speNMS for 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 SYSAuthentication table for SNMP access screen appears, similar to the example below.

Switch Name: Slot 0 SYSAuthentication 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


Basic Slot-0 Configuration SNMP Authentication

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


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 Figure 3-1 and Table 3-1.)

• 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

Xedge Switch: 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 5, ISG2 Configuration/Status )

• Chapter 6, PCx Configuration/Status )

• Chapter 7, Line Interface Modules )



0 slots 0

e

the 20

o route

Chapter 5: ISG2 Configuration/Status

Overview

This chapter describes the configuration and status of the ISG2 Slot Controller. For a brief introduction to Xedge menu and screens refer to Navigating Xedge Menus and Screens in the preface of this manual. 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 4, 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 Telnet access to the non-Slot 0 ISG2 is accomplished via the Slot 0 controller, since that ISG2 has nto the outside network. As an alternative, a static route can be created on the non-Slot 0 ISG2.

OSPF Command Line Interface

The ISG2 and the PCx support OSPF version 2, the Interior Gateway routing protocol (IGP)described in RFC2328 - 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 5-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 5-1 for definitions of all Management IF menu options.

Figure 5-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 4, 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 5-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 5-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

.

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 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. Use this screen to view or change the current port parameters on the ISG2 card.

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 : 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 5-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 alexisiting 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 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 5-2 Tunnel Managment 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 5-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 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


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 5-3 Interface Table Detail Screen

Parameter Definition

If Index Interface Index 1-3255 Read only

Description Text string containing interface information, typically includes manufacterer’s 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

the

rds.

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 5-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 card or interface does not exist, stop is displayed. Otherwise, status is up or down .

• Further down in the list describes the remainding cards and ports 4 to 15 for all ca

• 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 5-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 5-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


etting anging

IB

ted

Chapter 6: PCx Configuration/Status

Overview

This chapter describes the configuration and status of the PCx Slot Controller. For a brief introduction to Xedge menu and screens refer to Navigating Xedge Menus and Screens in the preface of this manual.

Topics in this chapter include:



• 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 from OC-3 to OC-12 (or visa-versa).

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 Table 3-3). Refer to Chapter 7, Line Interface Modules 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 6-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 6-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 6-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 6-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 fronm Pseudowire


Termination of MPLS Label


IPv4 Point-to-Point Interface


IPv4 Broadcast Interface Not supported in this release --


PCx Configuration/Status ATM Port Configuration

.

he 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 6-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. TUse 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 6-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

e

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 6-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 thPVC configuration.

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 alexisiting 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 6-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 6-2 Tunnel Managment 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 6-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 6-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 6-3 Interface Table Detail Screen

Parameter Definition

If Index Interface Index 1-3255 Read only

Description Textstring containing interface information, typically includes manufacterer’s 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 6-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 6-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 6-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 6-3.

Figure 6-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

.

oller.

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 6-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, Line Interface Modules for information on supported LIMs for the PCx Slot Contr

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



me

ntact ing 0).

Chapter 7: Line Interface Modules

ATM LIMs Overview

This chapter describes configuring the following LIMs for use with the PCx. Note that the saconfiguration screens are used to configure any type of LIM, except where noted.

• OC-N / STM-N LIM

• DS1 IMA LIM (Future implementation)

• E1 IMA LIM (Future implementation)

• For information on OC-N/STM-N front panel features, see Chapter 3, Hardware Overview .

• For a list of all LIMs currently supported by the PCx, as well as future LIMs under development, refer to Table 3-3.

Note IMA LIMS are not fully implemented at this time. The information in this chapter is subject to change. Coyour Xedge representative for details on availability. For additional information on Xedge LIMs, includinstallation and front panel features, consult the latest issue of the Xedge Hardware Manual (032R44

LIM Configuration

From the MIB Display and Management menu, select LIM and Link Information . The LIM and Link Information menu appears with the following selections:

0 LIM Information menu provides selections for:

• LIM ID, Version and Status display and an Extra Details screen (see Figure 7-1)

• LIM Timing display and Extra Details screen (see Figure 7-2)

• LIM Firmware/Software Update screens (see Figure 7-3)

1 SONET/SHD Links menu provides selections for:

• SONET/SDH Diagnostics

• SONET/SDH Performance Monitoring

• SONET/SDH Alarms

• SONET/SDH Link Configuration

• SONET/SDH Automatic Protection Switching (APS)

• SONET/SDH Defects

2 E1 Links (Future Feature)

3 DS1 Links (Future Feature)

4 SFP Tranceivers table lists transceiver parameters for each link (read only).


Line Interface Modules LIM Information and Configuration

d

LIM Information and Configuration

LIM ID, Version, Status

1. At the LIM and Link Information menu, select LIM Information , then select LIM ID, Version, Status . Figure 7-1 shows an example display and Extra Detail screen withLIM 1 as a legacy LIM, and LIM 2 as a OC-N/STM-N LIM.

2. Select the desired LIM (0, 1 , 2 or 3) . In the example, LIM 1 is selected.

3. Select Extra Detail to display the LIM type, hardware version, software version anstatus of LIM 1.

4. Select Down to display LIM 2 details.

Figure 7-1 LIM ID, Version and Status Screens

MAINSCREEN

EXTRADETAILS



ing

r the

node eded.

LIM Timing

1. At the LIM and Link Information menu, select LIM Timing . Figure 7-2 shows an example display and Extra Detail screen with LIM 2 using a a system clock as the Master TX Timsource.

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 through Q) to assign a timing source for the node.

Figure 7-2 LIM Timing Screens

4. If one of the LIMs on the PCx is to serve as the Primary or Secondary source of timing fonode, select the desired LIM as described above, then select Extra Detail to display that LIM’s timing information. Select enable under the “Allow Sys Timing” option.

Note IMPORTANT! This procedure only configures timing option for the LIM. You must also configure thefor System Timing. Refer to Xedge Version 6.2.0 Configuration Guide (032R400), Chapter 18, as ne

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 2 link0 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,

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



at

LIM Firmware/Software Update

1. At the LIM and Link Information menu, select LIM Firmware/Software Update . Figure 7-3 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-3 LIM Firmware/Software Update Screens

MAINSCREEN

EXTRADETAILS


Line Interface Modules SONET/SDH Links

SONET/SDH Links

SONET/SDH Configuration

1. At the MIB Display and Management menu, select LIM and Link Information .

2. At the LIM and Link Information menu, select SONET/SDH Links .

3. Select SONET/SDH Link Configuration . Figure 7-4 shows an example display and an Extra Detail screen of Entry 0 .

4. Select an entry number to edit that link.

Figure 7-4 SONET/SDH Link Configuration Screens

MAINSCREEN

EXTRADETAILS



ostics

SONET/SDH Diagnostics



3. Select SONET/SDH Diagnostics . Figure 7-5 shows an example display and an Extra Detail screen of Entry 0 (lim1/link0).

4. Select an entry number to edit that link. Refer to the paragraphs on SONET/SDH Diagndefinitions and parameters as needed.

Figure 7-5 SONET/SDH Diagnostics Screens

MAINSCREEN

EXTRADETAILS



abled nter

f. a is

link. ost

ing

itter

g if

ck

ing

it

SONET/SDH Diagnostics Definitions

If Index If Index of the physical port on the LIM (Read only)

Link Location Defines the LIM and the Link Location (Read only)

Diag Timeout This parameter sets the amount of time allowed after any diagnostic is enuntil all the loopback or forced error generation are turned off. You can ean Integer Value from 1 to 64000 minutes. (Immediate effect)

Time Remaining The time remaining before the LIM will turn all diagnostics for this link ofThis parameter is reset to the Timeout value whenever the user turns on loopback, turns on any error generation or changes the timeout value. Thparameter can display an Integer Value from 0 (zero) to 64000 minutes.(Read only)

Force Bit Error This parameter will force Framing Bit Errors on the transmitter side of the When this option is on, a single bit error is continuously inserted in the msignificant 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 This parameter indicates the current bit error status, indicating that FramErrors are being inserted at the transmitter end. (Read only)The possible values are: 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)

Force CV-S This parameter can force Section Coding Violations (CV-S) on the transmend 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 Displays the current status of Section Coding Violations (CV-S) indicatinCV-S are being inserted on the link. (Read only)Possible values are:On - CV-S generation currently runningOff - CV-S generation currently not runningInhibited - CV-S generation is enabled but inhibited due to the loopbaor Bit Error generation.Conditioning (Not used)Forced (Not used)

Force AIS-L This parameter can force AIS-L to be transmitted out the link.Type y to generate an AIS-L. (Immediate effect)Type n to turn off AIS-L generation.

AIS-L Status Displays the current status of Line Alarm Indication Signal (AIS-L) indicatif AIS-L is being inserted at the transmitter end of the link. Possible values are:On - Force AIS-L currently runningOff - Force AIS-L currently not runningInhibited - Force AIS-L is enabled but inhibited due to the loopback or BError generation.Conditioning (Not used)Forced (Not used)



ink.

tion

it

e

n

g if

ck

al

r

link.

Force RDI-L This parameter can force Line Remote Defect Indication (RDI-L) on the l(Immediate Effect)Type y to generate an RDI-L.Type n to turn off RDI-L generation.

RDI-L Status This parameter displays the current status of Line Remote Defect Indica(RDI-L) indicating if RDI-L is being inserted on the link. (Read only)Possible values are:On - Force RDI-L currently runningOff - Force RDI-L currently not runningInhibited - Force RDI-Lis enabled but inhibited due to the loopback or BError generation.Conditioning - indicates a LOS, LOF or AIS-L failure on the receive linForced (Not used)

Force CV-L This parameter can force Line Coding Violations (CV-L) on the link. Whethis 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 Displays the current status of Section Coding Violations (CV-L) indicatinCV-L are being inserted on the link. (Read only)Possible values are:On - CV-L generation currently runningOff - CV-L generation currently not runningInhibited - CV-L generation is enabled but inhibited due to the loopbaor Bit Error generation.Conditioning (Not used)Forced (Not used)

Force AIS-p This parameter can force 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 This parameter displays the current status of Path Alarm Indication Sign(AIS-P) indicating if AIS-P is being inserted on the link. (Read only)Possible values are:On - Force AIS-P currently runningOff - Force AIS-P currently not runningInhibited - Force AIS-P is enabled but inhibited due to the loopback oBit Error generation.Conditioning (Not used)Forced (Not used)

Force RDI-P This parameter can force Path Remote Defect Indication (RDI-P) on the(Immediate effect)Type y to generate an RDI-P.Type n to turn off RDI-P generation.



r

,

r end

g if

ck

lay :

ck

ted

ck

RDI-P Status Displays the current status of Path Remote Defect Indication (RDI-P) indicating if RDI-P is being inserted on the link. (Read only)Possible values are:On - Force RDI-P currently runningOff - Force RDI-P currently not runningInhibited - Force RDI-P is enabled but inhibited due to the loopback oBit Error generation.Conditioning - indicates a LOS, LOF, LOP-P, AIS-P, UNEQ-P, PLM-Por AIS-L failure on the receive lineForced (Not used)

Force CV-p This parameter can force Path Coding Violations (CV-P) on the transmitteof the LIM. When this option is on, the path BIP byte (B3) is continuouslyinverted. (Immediate effect)Type y to force CV-P errors.Type n to turn off CV-P errors.Immediate

CV-P Status Displays the current status of Section Coding Violations (CV-P) indicatinCV-P are being inserted on the link. (Read only) Possible values are:On - CV-P generation currently runningOff - CV-P generation currently not runningInhibited - CV-P generation is enabled but inhibited due to the loopbaor Bit Error generation.Conditioning (Not used)Forced (Not used)

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 dispwill change accordingly as described in Loopback Status. The options areNone - loopback disabledLine Loopback - loopback any data received on the link's data port baout 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 Displays the current mode of loopback on the LIM. (Read only)Possible values are:NoneLine LoopbackDigital Loopback

Insert HCS Error This parameter can insert Header Check Sequence (HCS) errors on thetransmitter end of the LIM. When this option is on, the HCS octet is inverprior 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.Immediate

HCS Status Displays the current status of Header Check Sequence (HCS) Errors, indicating if HCS Errors are being inserted on the link. (Read only)Possible values are:On - HCS error generation currently runningOff - HCS error generation currently not runningInhibited - HCS error generation is enabled but inhibited due to loopbaor Bit Error generation.Conditioning (Not used)Forced (Not used)



mace

SONET/SDH Performance Monitoring



3. Select SONET/SDH Performance Monitoring . Figure 7-6 shows an example displayand an Extra Detail screen of Entry 0 (lim1/link0).

4. Select an entry number to edit that link. Refer to the paragraphs on SONET/SDH Perfordefinitions and parameters as needed.

Figure 7-6 SONET/SDH Performance Monitoring

MAINSCREEN

EXTRADETAILS



tted

d, not

d per

ame

ng

of nal

f east

s

onds e

SONET/SDH Performance Definitions

If index If Index of the physical port on the LIM

Link Location Defines the LIM and the Link Location (Read only)

Clear Count This parameter allows you to clear (reset to zero) all the counters on theSONET/SDH Performance Monitoring Page. (Immediate effect)Type y to clear all counters.Type n to exit this option without clearing the counters.

TX Cell Count Transmitted Cell Count. This parameter displays the number of cells transmitted, not including idle or unassigned cells.(Read only, updated once per second)Possible values are: 0 to 4,294,967,295 then restarts at 0 .

TX Cell Rate Transmit Cell Rate. This parameter displays the number of cells transmiper second, not including idle or unassigned cells. (Read only, updated once per second)Possible values are: 0 to 4,294,967,295 then restarts at 0 .

RX Cell Count Received Cell Count. This parameter displays the number of cells receiveincluding idle or unassigned cells. (Read only, updated once per second)Possible values are: 0 to 4,294,967,295 then restarts at 0 .

RX Cell Rate Received Cell Rate. This parameter displays the number of cells receivesecond, not including idle or unassigned cells.(Read only, updated once per second) Possible values are: 0 to 4,294,967,295 then restarts at 0 .

CV-S Section Coding Violations. This parameter displays the count of SONET frCV-S Errors detected at the section layer of the ingress signal.(Read only, updated once per second)Possible values are: 0 to 4,294,967,295 then restarts at 0 .

SEFS-s This parameter indicates the number of Section Severely Errored FramiSeconds (SEFS-S) on this Link. (Read only, updated once per second)Possible values are: 0 to 4,294,967,295 then restarts at 0 .

ES-s Section Errored Seconds. This parameter displays the count of number seconds where at least 1 Section Coding Violations (CV-S) or Loss of Sig(LOS) defect was detected. (Read only, updated once per second)Possible values are: 0 to 4,294,967,295 then restarts at 0 .

SES-s Section Severely Errored Seconds. This parameter displays the count onumber of seconds where at least 2,500 Section coding violations or as lone LOS was detected. (Read only, updated once per second)Possible values are: 0 to 4,294,967,295 then restarts at 0 .

CV-L Line Coding Violations. This parameter displays the count of BIP-24 errordetected at the line layer of the ingress signal. (Read only, updated once per second)Possible values are: 0 to 4,294,967,295 then restarts at 0 .

ES=L Line Errored Seconds. This parameter displays the count of number of secwhere at least one Near-End Line Coding Violations (CV-L) or at least onLine Alarm Indication Signal (AIS-L) is detected. (Read only, updated once per second)Possible values are: 0 to 4,294,967,295 then restarts at 0 .



of e

e hen

of r 10 the

ds

LTE .

-24 This r) is

ber r at ter

unt of CV-his r) is

r of TE the

SES-L Severely Errored Seconds. This parameter displays the count of numberseconds where at least 2500 Line Coding Violations (CV-L) or at least onLine Alarm Indication Signal (AIS-L) is detected.(Read only, updated once per second)Possible values are: 0 to 4,294,967,295 then restarts at 0 .

FC-L Line Failure Count. This parameter displays the count of number of failurevents. A failure event occurs when an AIS-L is received and is cleared wAIS-L is cleared. (Read only, updated once per second)Possible values are: 0 to 4,294,967,295 then restarts at 0 .

UAS-l Line Unavailable Seconds. This parameter displays the count of number seconds where the line is unavailable. A line is declared unavailable afteconsecutive Line Severely Errored Seconds (SES-L), which are included inunavailable time. The line becomes available after 10 consecutive seconwith no SES-L's, which are not included in the unavailable time.(Read only, updated once per second)Possible values are: 0 to 4,294,967,295 then restarts at 0 .

Cnt LFE Err Count Far-End Line Errors. Prompt as to whether or not the far-end (nextin the OC-3/STM-1 network) performance monitoring should be collected(Immediate effect)Type y to turn on far end line error collection.Type n to turn off far end line error violation collection.Immediate

CV-LFE Far-End Line Coding Violations. This parameter displays the count of BIPErrors (CV-L) detected at the line layer of the ingress signal at the far end. parameter does not function if the Count Far-End Line Errors (Cnt LFE Eset to no . (Read only, updated once per second)Possible values are: 0 to 4,294,967,295 then restarts at 0 .

ES-LFE Far-End Line Errored Seconds. This parameter displays the count of numof seconds where at least one Far-End Line Coding Violations (CV-LFE) oleast one Line Alarm Indication Signal (AIS-LFE) is detected. This paramedoes not function if the Count Far-End Line Errors (Cnt LFE Er) is set to no .(Read only, updated once per second)Possible values are: 0 to 4,294,967,295 then restarts at 0 .

SES-LFE Far-End Line Severely Errored Seconds. This parameter displays the conumber of seconds where at least 2500 Far-End Line Coding Violations (LFE) or at least one Line Alarm Indication Signal (AIS-LFE) is detected. Tparameter does not function if the Count Far-End Line Errors (Cnt LFE Eset to no . (Read only, updated once per second)Possible values are: 0 to 4,294,967,295 then restarts at 0 .

FC-LFE Far-End Line Failure Count. This parameter displays the count of numbefailure events. A failure event is when RDI-L is received from the far-end Land ends when the RDI-L is cleared. This parameter does not function if Count Far-End Line Errors (Cnt LFE Er) is set to no . (Read only, updated once per second)Possible values are: 0 to 4,294,967,295 then restarts at 0 .



lable hich

ine

s

conds

mber r at al

ath ),

nd nal

of er 10 in the ds

th Far

Path

t the (Cnt

UAS-LFE Far-End Line Unavailable Seconds. This parameter displays the count ofnumber of seconds where the line is unavailable. A line is declared unavaiafter 10 consecutive Far-End Line Severely Errored Seconds (SESLFE), ware included in the unavailable time. The line becomes available after 10consecutive seconds with no SES-LFE's, which are not included in the unavailable time. This parameter does not function if the Count Far-End LErrors (Cnt LFE Er) is set to no . (Read only, updated once per second)Possible values are: 0 to 4,294,967,295 then restarts at 0.

CV-P Path Coding Violations. This parameter displays the count of BIP-8 errordetected at the path layer (CV-P) of the ingress signal. (Read only, updated once per second)Possible values are: 0 to 4,294,967,295 then restarts at 0 .

ES-P Path Errored Seconds. This parameter displays the count of number of sewhere at least one CV-P occurred, Alarm Indication Signal (AIS-P), or Synchronous Transport Signal Loss of Pointer (LOP-P) is detected.(Read only, updated once per second)Possible values are: 0 to 4,294,967,295 then restarts at 0 .

SES-P Path Severely Errored Seconds. This parameter displays the count of nuof seconds where at lest 2400 Near- End Path Coding Violations (CV-P) oleast one Alarm Indication Signal (AIS-P), or Synchronous Transport SignLoss of Pointer (LOP-P) is detected. (Read only, updated once per second)Possible values are: 0 to 4,294,967,295 then restarts at 0 .

FC-P Path Failure Count. This parameter displays the count of the number of pfailure events. A failure occurs when either Alarm Indication Signal (AIS-Por Synchronous Transport Signal Loss of Pointer (LOP-P) are declared aends when Alarm Indication Signal (AIS-P), or Synchronous Transport SigLoss of Pointer (LOP-P) are cleared. (Read only, updated once per second)Possible values are: 0 to 4,294,967,295 then restarts at 0 .

UAS-P Path Unavailable Seconds. This parameter displays the count of numberseconds where the path is unavailable. A path is declared unavailable aftconsecutive path Severely Errored Seconds (SES-P), which are included unavailable time. The line becomes available after 10 consecutive seconwith no SES-P's, which are not included in the unavailable time.(Read only, updated once per second)Possible values are: 0 to 4,294,967,295 then restarts at 0 .

Cnt PFE Err Count Far End Path Errors. This parameter allows you to specify if the PaEnd Error Information should be collected or not. (Immediate effect)The options are: Not-active - indicates that the error counts will not be collected.Active - indicates that the error counts will be collected.

CV-PFE Path Far End Coding Violations. This parameter indicates the number ofFar End Coding Violations received by this Link. A Path Far End Coding Violation is a BIP-8 error detected at the path layer of the ingress signal afar end. This parameter does not function if the Count Far-End Path ErrorsPFE Er) is set to no . (Read only, updated once per second)Possible values are: 0 to 4,294,967,295 then restarts at 0 .



ar End re at Path

umber nts g

ount

ailure -

f Far fter h are 10

ATM

r of cted.

ES-PFE Path Far End Errored Seconds. This parameter indicates the number of FPath Errored Seconds. An errored second is the number of seconds wheleast one Far End Path Coding Violation (CV-PFE) or at least one Far EndAlarm 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 . (Read only, updated once per second)Possible values are: 0 to 4,294,967,295 then restarts at 0 .

SES-PFE Path Far End Severely Errored Seconds. This parameter indicates the nof Far End Path Severely Errored Seconds received on this link. This couthe number of seconds where at least 2,500 Far End Path Section CodinViolations (CV-PFE) or at least 1 Near End Line Alarm Indication Signal (AIS-PFE) defect was detected. This parameter does not function if the CFar-End Path Errors (Cnt PFE Er) is set to no . (Read only, updated once per second)Possible values are: 0 to 4,294,967,295 then restarts at 0 .

FC-PFE Path Far End Failure Count. This parameter indicates the Far End Path FCount. A failure event is when Far End Path Alarm Indication Signal (AISPFE) is declared and ends when AIS-PFE is cleared. (Read only, updated once per second)Possible values are: 0 to 4,294,967,295 then restarts at 0 .

UAS-PFE Path Far End Unavailable Seconds.This parameter indicates the count oEnd Path Unavailable Seconds for this link. A line is declared unavailable a10 consecutive Far End Path Severely Errored Seconds (SES-PFE), whicincluded in the unavailable time. The time becomes available again after consecutive seconds with no SESPFE which are not included in the unavailable time. (Read only, updated once per second)Possible values are: 0 to 4,294,967,295 then restarts at 0 .

HCS Corr Correctable HCS Errors. This parameter displays the count of number of cells with correctable Header Check Sequence (HCS) Errors. (Read only, updated once per second)Possible values are: 0 to 4,294,967,295 then restarts at 0 .

HCS Uncorr Uncorrectable HCS Errors. This parameter displays the count of numbeATM cells where an Header Check Sequence Error (HCS) cannot be corre(Read only, updated once per second)Possible values are: 0 to 4,294,967,295 then restarts at 0 .



SONET/SDH Alarms



3. Select SONET/SDH Alarms . Figure 7-7 shows an example display and an Extra Detail screen of Entry 0 (lim1/link0).

4. Select an entry number to edit that link. Refer to the paragraphs on SONET/SDH Alarmdefinitions and parameters as needed.

Figure 7-7 SONET / SDH Alarm Screens

MAINSCREEN

EXTRADETAILS



ted.

or at or 10

for a

ared

s the path

nitor per d, or ,

Rate are 0.5

K2

o

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 Loss of Signal Defect. Declared when all zeros are received for 20 +/- 3 microseconds or longer. Cleared when two valid framing words are detecThere are no defects or failures that inhibit LOS defect. (Read only)Possible values are: active or inactive

LOS Fault Loss of Signal Failure. Declared when Loss of Signal Defect is declared fleast 2.5 +/- 0.5 seconds. Cleared when Loss of Signal Defect is absent f+/- 0.5 seconds. There are no defects or failures that inhibit LOS failure. (Read only) Possible values are: active or inactive

LOF Defect Loss of Frame Defect. Declared when a out-of-frame conditions persistsperiod 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) Possible values are: active or inactive

LOF Fault Defect is declared for at least 2.5 +/- 0.5 seconds and is not inhibited. Clewhen Loss of Frame Defect is absent or inhibited for 10 +/- 0.5 seconds. Inhibited by: Loss of Signal (LOS) (Read only) Possible values are: active or inactive

EBER-P Thresh Excessive Bit Error Rate Defect. This user selectable threshold specifieallowable path error rate, as determined by monitoring the B3 byte in the overhead section of the SONET frame header.Possible values you can select are: 1x10-31x10-41x10-5

EBER-p Defect Excessive Bit Error Rate Defect. Declared when then path BIP-8 error modetects more than 1x10-3 (default 1x10-4 1x10-5 user selectable) errors second. Cleared when the bit error rate falls below the specified thresholwhen the EBER defect is inhibited. Inhibited by: LOS, LOF, AIS-L, AIS-PLOP-P NA. (Read only)

EBER-P Fault Excessive Bit Error Rate Failure. Declared when the Excessive Bit ErrorDefect is declared for at least 2.5 +/- 0.5 seconds and no inhibitor failuresactive. Cleared when Excessive Bit Error Rate Defect is absent for 10 +/-seconds with no inhibitor defects and failures set). Read only

AIS-l Defect Line Alarm Indication Signal Defect. Declared when bits 6, 7 and 8 of byteare 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 isinhibited. Inhibited by: Loss of Signal (LOS), Loss of Frame (LOF)(Read only) Possible values are: active or inactive

AIS-L Fault Line Alarm Indication Signal Failure. Declared when the Line Alarm Indication Signal Defect is declared for at least 2.5 +/- 0.5 seconds and ninhibitor 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) Possible values are: active or inactive



yte

F)

fect ited. for

F)

is ited.

OS,

larm not t or

1' for n bit S,

efect ited. for

nters n 3

ect is STS

e C2 0 for

re

RDI-L Defect Line Remote Defect Indicator Defect. Declared when bits 6, 7, and 8 of bK2 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 (LO(Read only) Possible values are: active or inactive

RDI-l Fault Line Remote Defect Indicator Failure. Declared when the Line Remote DeIndicator Defect is declared for at least 2.5 +/- 0.5 seconds and is not inhibCleared when Line Remote Defect Indicator Defect is absent or inhibited10 +/- 0.5 seconds. Inhibited by: Loss of Signal (LOS), Loss of Frame (LO(Read only) Possible values are: active or inactive

AIS-P Defect STS Path Alarm Indication Signal Defect. Declared when all 1's pattern detected on the H1 and H2 bytes for 3 consecutive frames and is not inhibCleared 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: LLOF, AIS-L (Read only) Possible values are: active or inactive

AIS-P Fault STS Path Alarm Indication Signal Failure. Declared when the STS Path AIndication Signal Defect is declared for at least 2.5 +/- 0.5 seconds and isinhibited. Cleared when STS Path Alarm Indication Signal Defect is abseninhibited for 10 +/- 0.5 seconds. Inhibited by: LOS, LOF, AIS-L(Read only) Possible values are: active or inactive

RDI-P Defect Path Remote Defect Indicator Defect. Declared when bit 5 of byte G1 is '10 consecutive frames and is the RDIP defect not inhibited. Cleared whe5 of byte G1 is '0' for 10 consecutive frames or is inhibited. Inhibited by: LOLOF, RDI-L, AIS-L, LOP-P (Read only) Possible values are: normal or defect

RDI-P Fault Path Remote Defect Indicator Failure. Declared when the Path Remote DIndicator Defect is declared for at least 2.5 +/- 0.5 seconds and is not inhibCleared when Path Remote Defect Indicator Defect is absent or inhibited10 +/- 0.5 seconds. Inhibited by: LOS, LOF, RDI-L, AIS-P, LOP-P(Read only) Possible values are: active or inactive

LOP-P Defect STS Loss of Pointer Defect. Declared when eight consecutive invalid poiare detected and is not inhibited. Cleared when valid pointers are found iconsecutive frames or when the LOP-P defect is inhibited. Inhibited by: LOS, LOF, AIS-L, AIS-P (Read only) Possible values are: active or inactive

LOP-P Fault STS Loss of Pointer Failure. Declared when the STS Loss of Pointer Defdeclared for at least 2.5 +/- 0.5 seconds and is not inhibited. Cleared whenLoss of Pointer Defect is absent or inhibited for 10 +/- 0.5 seconds.Inhibited by: LOS, LOF, AIS-L, AIS-P (Read only) Possible values are: active or inactive

UNEQ-P Defect Incompatibility between the local and the far-end LTE. Declared when thbyte of the path overhead section of the SONET frame is set to a value of 3 consecutive SONET frames, a path unequipped defect (P-UNEQ) is generated, provided the defect is not inhibited. Cleared when the far-endbegins sending SONET frames indicating in the C2 byte that ATM cells aembedded in them or when the path unequipped defect is inhibited.Inhibited by: LOS, LOF, AIS-L, AIS-P, LOP-P(Read only) Possible values are: active or inactive



/- 0.5 r

far-tive el is ct is

abel ited. for

n is late

tion ared

UNEQ-P Fault Declared when the Path Unequipped Defect is declared for at least 2.5 +seconds and is not inhibited. Cleared when Path Remote Defect IndicatoDefect is absent or inhibited for 10 +/- 0.5 seconds.Inhibited by: LOS, LOF, AIS-L, AIS-P, LOP-P(Read only) Possible values are: active or inactive

PLM-P Defect STS Payload Label Mismatch (mismatch between the local LTE and theend LTE). Declared when the payload label is not 13 (hex) for 3 consecuframes and no inhibitor defects are active. Cleared when the payload lab13(hex) for 3 consecutive frames or when the payload label mismatch defeinhibited. Inhibited by: LOS, LOF, AIS-L, AIS-P, LOP-P(Read only) Possible values are: active or inactive

PLM-P Fault STS Payload Label Mismatch Failure. Declared when the STS Payload LMismatch Defect is declared for at least 2.5 +/- 0.5 seconds and is not inhibCleared when STS Payload Label Mismatch Defect is absent or inhibited10 +/- 0.5 seconds. Inhibited by: LOS, LOF, AIS-L, AIS-P, LOP-P(Read only) Possible values are: active or inactive

LOCD Defect Loss of Cell Delineation Defect. Declared when a Loss of Cell Delineatiodetected and is not inhibited. Cleared when the LIM can successfully calcuHCS for ATM cell headers for 6 consecutive ATM cells or when the LOCDdefect is inhibited Inhibited by: LOS, LOF(Read only) Possible values are: active or inactive

LOCD Fault Loss of Cell Delineation Failure. Declared when the Loss of Cell DelineaDefect is declared for at least 2.5 +/- 0.5 seconds and is not inhibited. Clewhen Loss of Cell Delineation Defect is absent or inhibited for 10 +/- 0.5 seconds. Inhibited by: LOS, LOF(Read only) Possible values are: active or inactive


Line Interface Modules SONET/SDH Automatic Protection Switching

erate nce

below.

n the

SONET/SDH Automatic Protection SwitchingThe following section describes how to configure Automatic Protection Switching (APS) to opon your LIM as required. For basic information on APS, refer to the Xedge Technical RefereManual (032R310), Chapter 1, under the paragraphs on Switch Function.



3. Select SONET Automatic Protection Switching (APS) . A menu appears with the following selections:

0 APS Group Configuration

1 APS Alarms

2 APS Link Configuration

4. For each APS function, perform the configuration steps as described in the procedures Parameter definitions and values accompany the procedures.

APS Group Configuration

1. 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 .

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

Select option:

Down, Enter entry number to edit, Goto row, Index search, Summary,eXit



S

g

R

tive ult

roup.

a fail the

to

ure

If the te

o

6. To change the APS lockout, select Lockout and then:

• enter y to lockout APS fail-over

• 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. When you are finished, use the eXit command to return to the Automatic Protection Switchinscreen. If desired, proceed to APS Link Configuration procedure, or configure the Timingparameters as needed (via the LIM and Link Information menu).

APS Group Configuration Parameters

APS Group NumberIndicates the displayed APS Group Number. (Read only)

Links in APS Gr Links in APS Protection Group. This parameter displays the links that comprise the APS protection group. (Read only)Possible 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.

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 WTperiod has expired, or when the user command is cleared.Nonrevertive - the working link will not revert back from the protectionlink once the error has cleared; WTR Period is ignored. While in nonrevermode, the working link will revert back from the protection link only as a resof an error on the protection link, or a user command to switch.

Actual Switching Reports the actual switching mode that is currently running on the APS g(Read only)

Directional Mode Determines whether or not the tail and head ends will cooperate during over request. It is recommend that both ends of the fiber span are set to 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 regardthe head end. Unidirectional switching provides a minor advantage over bidirectional switching in that the protection link can handle a receiver failfrom both nodes.

Actual Direction Reports the directional mode that is currently running on the APS group. local side has the APS Directional Mode set to bidirectional and the remoside is set to unidirectional, the Actual APS Directional Mode will be set tunidirectional. (Read only) Refer to Directional Mode parameters for a description of the possible values.



ait the ue

ode

m the

PS S

ions, s

ting

ut

e

e al

PS

al

k

WTR Period Wait to Restore Period. This option specifies the number of minutes to wafter an error has cleared on the working link before switching back fromprotection link. The WTR Period is provided to avoid repeated fail-overs dto 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 mmust be set to NonRevertive .

Lockout Lockout from Protection. This option prevents any of the working links frofailing over to the protection link, regardless of the severity of the errors onlinks. If a working link is on the protection link when lockout is issued, it isswitched back to its working link. Note that you cannot issue the Lockoutcommand 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 Actual Lockout from Protection. Indicates whether or not the lockout fromprotection is in effect. Note that the lockout will not take effect when an Aerror exists on the working link (protection link failure, channel mismatch,protection switching byte failure, far-end protection switching failure or APmode mismatch failure).(Read only) Possible values are: yes or no

State Reports the state of the APS protection group. For bidirectional configuratit shows the state of both LTE’s. For unidirectional configurations, it showjust the state of the local LTE. (Read only) Possible 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 reveror 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 bthe cause of the failure has been fixed or the user command has been terminated. The working link does not revert back from protection becausAPS is configured for nonrevertive. revert - local LTE has requested that the remote LTE switch back to thworking link from the protection link (this is a temporary state for bidirectionconfigurations only)requestlockout - local LTE is waiting for the remote LTE to acknowledge a lockout request (this is a temporary state for bidirectional Aonly)lockout - local LTE has locked out all working links from the protectionlinkrequestexercise - local LTE is waiting for the remote LTE to acknowledge an exercise request (this is a temporary state for bidirectionAPS only)Exercise - Exercise command is currently in effect on the protection lin



ch e

g t

nal

at

st

local

s

e

n

ction R

ared n nds

State (Continued) requestswitchfromprotection - local LTE has requested that the working link be removed from the protection link (via either a manual switor a forced switch). This is a temporary state for bidirectional one-plus-onAPS.switchfromprotection - a manual or forced switch from the protectionlink is in effect. For one-plus-one APS only.removefailoverrequest - temporary state. Remote LTE is requestinto failover to the working link. Local LTE should acknowledge the requeswith 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 remoteLTE. 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 bidirectioAPS only.remoteswitchfromprotection - the remote LTE has moved the working link from the protection link via either a manual or forced switch thhas been issued on the protection link. For bidirectional APS only.remotelockout - the local LTE is currently entertaining a lockout requefrom 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 onthe protection link.channelmismatcherror - the channel number in the transmitted K1 does not match the channel number in the received K2. Indicates that theand remote LTE's are out of sync.protectionswitchingbyteerror - K1 and K2 are not stable possiblydue to a hardware error on the protection link.farendprotectionfailure - the remote LTE is indicates that there ia failure condition on the protection link. apsmodemismatch - the configuration of the local and remote LTE's donot match. Either the mode (bidirectional or unidirectional) or the APS typ(1:n or one-plus-one) do not match between the two LTEs.protectiondegrade - Signal degradation is detected on the protectiolink.remoteprotectiondegrade - A remote LTE detected a signal degradation on a protection link.

Time to Revert Indicates how much time (in seconds) is left before the revert of the proteto working link will actually occur. If this value is non-zero, then the link isconfigured for revertive switching mode and is currently waiting for the WTtimer to expire. Once a fail-over has occurred and the error condition is clethen the wait to revert timer is started prior to reverting the protectiolink back to the working link. The displayed value indicates the time in secobefore 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. (Read only)



e K1

he

.

ted

nds.

ack

k ing

e

e

ion

k nto

ke

ion

itted

e

Xmt K1 Con Code Transmitted Condition Code. The current APS request, transmitted in thbyte, to the remote LTE. A signal failure is either an AIS-L, LOS, LOF, orexceeding the Signal Failure Bit Error Rate (see SF BER Threshold in this chapter). (Read only) Possible values are:Lockout - This state indicates the working link is locked out from using tprotection link.Signal Fail High - This state indicates a protection link signal failureSignal 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).Signal Deg Low - This state indicates that a signal degradation is detecon the working link (see SD BER Threshold in this chapter).Manual Switch - This state indicates a manual switch was invoked oneither 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 commaDo not revert - After a failure condition, APS maintains the receiver switch on the protection link until the user manually switches the receiver bto the working link.Exercise - This state indicates that the user is invoking an exercise command.Not Valid - not supported

Xmt K1 Channel Transmitted K1 Channel Number. This parameter reports the current linnumber, transmitted in bits 5-8 of the K1 byte by the local LTE, that is berequested to be placed onto the protection link. (Read only) Possible values are:null-channel - the remote LTE is not requesting that the working link bplaced on the protection link.channel1 - local LTE is requesting that the working link be placed on thprotection link.channel2 - local LTE is requesting a command that applies to the protectlinkchannel3 through channel15 - are not currently supported

Xmt K2 Channel Transmitted K2 Channel Number. This parameter reports the current linnumber, transmitted in the K1 byte by the local LTE, that is being bridged othe protection link. (Read only) Possible values are:null-channel - no working link is currently bridged onto the protection linchannel1 - local LTE is requesting that the working link be placed on thprotection link.channel2 - local LTE is requesting a command that applies to the protectlinkchannel3 through channel15 - are not currently supported

Xmt K2 Arch Transmitted K2 Type. This parameter reports the APS architecture transmby the local LTE in bit 5 of K2. (Read only) Possible values are: 1+1

Xmt K2 Mode Transmitted K2 Misc. Code. This parameter reports the current APS modtransmitted by the local LTE in bits 6-8 of K2. (Read only) Possible values are:bidirectional, unidirectional



est, s as

he

ted

ted

nds. on e

ing

e

on

e

e

on

e

from

Rvd K1 Con Code Received Condition Code. This parameter reports the current APS requreceived in bits 1-4 of the K1 byte, from the remote LTE. A signal failure ieither an AIS-L, LOS, LOF, or exceeding the Signal Failure Bit Error Ratedescribed in SF BER Threshold in this chapter. (Read only) Possible values are:Lockout - This state indicates the working link is locked out from using tprotection link.Signal Fail High - This state indicates a high priority signal failure.Signal Fail Low - This state indicates a low priority signal failure.Signal Deg High - This state indicates that a signal degradation is detec(see SD BER Threshold in this chapter).Signal Deg Low - This state indicates that a signal degradation is detec(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 commado not revert - After a failure condition, APS maintains the receiver switchthe protection link until the user manually switches the receiver back to thworking link.exercise - This state indicates that the user is invoking an exercise command.Not Valid - not supported

Rvd K1 Channel Received K1 Channel Number. This parameter reports the current link number, received in bits 5-8 in the K1 byte from the remote LTE, that is berequested to be placed onto the protection link. (Read only) Possible values are:null-channel - The remote LTE is not requesting that the working link bplaced on the protection link.channel1 - The remote LTE is requesting that the working link be placedthe protection link.channel2 - The remote LTE is requesting a command that applies to thprotection linkchannel3 through channel15 are not currently supported

Rvd K2 Channel Received K2 Channel Number. This parameter reports 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) Possible values are:null-channel - The remote LTE is not requesting that the working link bplaced on the protection link.channel1 - The remote LTE is requesting that the working link be placedthe protection link.channel2 - The remote LTE is requesting a command that applies to thprotection link.channel3 through channel15 are not currently supported

Rvd K2 Arch Received K2 Type. This parameter reports the APS architecture from theremote LTE in bit 5 of K2. (Read only) Possible values are: 1+1

Rvd K2 Mode Received K2 Misc. Code. This parameter reports the APS mode receivedthe remote LTE in bits 6-8 of K2. (Read only) Possible values are: bidirectional, unidirectional, ais, rdi, unknown



rade. e B2 t slice

the ate is

tion takes

e same

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 rsampled 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-1. 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-1 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 ine an lear

SF BER Threshold

The SF BER Threshold is the bit error rate (BER) that will cause a fail-over due to signal fail.APS 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 .008 seconds of sample time to determerror rate of and .013-seconds to determine that the error rate has lowered below the BER cthreshold.

You can set the SF BER Threshold to the values shown in Table 7-2.

Note The SD BER threshold must be less than the SF BER threshold.

Table 7-2 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:

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



l

es for

nual,

n s; al

re a

e d or

om

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 signadegrade. Although each link can have a different SD BER threshold, it is recommended that both endpoints of an OC-3C span have the same valuSD BER. (Immediate effect) (See SD BER Threshold in this chapter.)

Note The SF BER threshold must be smaller than the SD BER threshold.

Signal Fail bit error rate: The bit error rate (BER) that will cause a fail over due to signal fail.(Immediate effect) (See SF BER Threshold in this chapter.)

Note The SD BER threshold must be greater than the SF BER threshold

Clear APS Commands: This parameter clears all outstanding commands (lockout, force, maexercise) 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 protectiolink back to the working link) unless there is one of the following conditiona higher priority command, a higher priority force command or there is anfailure outstanding on the protection link. Has higher priority than a manuswitch, 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 theis a signal fail or signal degrade condition on the working link. There isn’tWTR interval at the end of the forced switch. In the nonrevertive configuration, disabling the forced switch will leave thworking link on the protection link unless there is an error or another forcemanual 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 frprotection or forced switch from protection) then 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)Possible values are: no - indicates a forced switch did not occur.yes - indicates a forced switch did occur.NA, read only



tion er er

ff, e is

e d or

ch, m

o APS

rcise

nt

out ink

t cally

not e

r.

Manual Switch This parameter switches the working link to the protection link (or a proteclink back to the working link), unless a command or error of equal or highpriority is in effect. Force switch, signal fail and signal degrade have highpriority than a manual switch. (Immediate effect)Select yes to switch the specified working link to the protection link.Select no to revert (if revert is enabled).Note that for revertive configurations, when the manual switch is turned othe protection link will immediately revert back to the working link, unlessthere is a signal fail or signal degrade condition on the working link. Thernot a WTR interval at the end of the manual switch.In the nonrevertive configuration, disabling the manual switch will keep thworking link on the protection link unless there is an error or another forcemanual 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 switlockout from protection, forced switch from protection or manual switch froprotection) will result in the manual switch being set to no.

Actual Manual Switch:Indicates if the Manual Switch actually took effect. (Read only)no - indicates a manual switch did not occur.yes - indicates a manual switch did occur.NA, read only

APS Exercise This parameter exercises the APS protocol and checks the responses tcommands from the head end. If the protection link is already in use the exercise command has no effect. This is a continuous non-interfering exeand it does not cause an APS switch. (Immediate effect)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 seto 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 (lockfrom protection, forced switch, manual switch, forced switch of protection lor manual switch of protection link), then Exercise will be set to no.

Actual APS Exercise:Indicates if the exercise command is in effect. (Read only)no - indicates the exercise command is not in effect.yes - the exercise command is in effect.NA, read only

Link State This parameter indicates the state of the APS link. (Read only)Possible states are:disabled - APS is disabled on this link.working - Working link, no errorslockout - link has an error condition or APS user command but has nofailed over to protection because of the lockout command issued, either loor remotely, on the APS group.APS error - link has an error condition or APS user command but has failed over to protection because of an APS defect or failure preventing thAPS 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 oveprotection, in use - Protection link. One of the working links has failed over.



ignal,

PS

oup

the SF en.

d.

e . of

ld

rror

the

Signal Fail Condition: This parameter indicates a signal fail condition because of a Loss of SLoss of Frame, AIS or RDI is active on the link. (Read only)no - indicates a signal fail condition is not present.yes - indicates a signal fail condition is present.Note that if there is a SF condition on a working link then the state of the Agroup should be one of the following: pending, switched, bridged, switch+bridge or WTR.If there is a SF condition on a protection link then the state of the APS grshould be Error.NA, read only

Signal Fail Threshold Error: This parameter indicates that the link bit error rate has passed BER threshold. The SF threshold is specified the Link Configuration scre(Read only)no - indicates the link bit error rate has not passed the SF BER thresholyes - 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 thstate of the APS group should be one either switch and bridge or lockoutIf there is a SF Threshold Error and this is a protection link, then the statethe APS group should be error.

Signal Degrade Threshold Error: Indicates that the link bit error rate has passed the SD BERThreshold error rate. The SD threshold is specified in the APS Link Configuration screen. (Read only)no - indicates the link bit error rate has not passed the SD BER Threshoerror rate.yes - indicates the link bit error rate has passed the SD BER Threshold erate.Note that if there is a SD Threshold Error, and this is a working link, then Status of the link should be one either pending, failed over, or lockout. A SD threshold error has no effect on the protection link.



le

.

n as

2:

e for

APS Alarms

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-10 APS Group Configuration Detail Screen

3. Use the Down command to transition to the detail screen for entry 1 (APS logical link-1)

APS Alarms Definitions

APS Group NumberIndicates the APS Group Number displayed in this screen.

apsGroupAlarmLinksInGroupLists the links that comprise the APS protection group. (Read only)Possible 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 conditio(LOS, LOF, or AIS-L), preventing fail-overs from occurring until the error hbeen fixed. During a Protection Link Defect, the switch will output the following K1, KK1 Condition Code = NO REQUESTK1 Channel Number = NULL CHANNELK2 Channel Number = NULL CHANNEL

Protection Link FailureThis parameter indicates if the protection link defect has been activ2.5 seconds. The protection link failure is cleared when the protection linkdefect 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

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



mote sion to

mes me. utive hen n the

r

1/

f this s not

n itch

OF,

will ction ents

been

far-ure

for he

r 10

annel ’s nnel

yte

Protection Switching Byte DefectThis parameter indicates an APS protocol error with the reLTE. This either indicates an internal error on the LIM or a severe transmiserror from the remote LTE. A protection switching byte defect results dueone of the following reasons:

APS is synchronized when the LTE receives three consecutive SONET frawith the same K1 bytes in the transport overhead section of the SONET fraIf the OC-3 receives 12 successive SONET frames, where no three consecframes have identical K1 bytes then a protection switch defect will arise. Wthree consecutive SONET frames are received with the same K1 bytes theprotection switch detect will be released or the defect is not inhibited.An APS group configured for bidirectional switching and an unexpected oinvalid K1 or K2 byte is received.

During a Protection Switching Byte Failure, APS will output the following KK2: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 oOC-3 segment. This failure indicates that the Protection Switch Defect habeen in effect for over 2.5 seconds. When the Protection Switch Defect israised for 10 seconds then the protection switch failure will be cleared.Inhibited by: protection link defect. This either indicates an internal error othe LIM or a severe transmission error from the other side. A protection swdefect 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, Lor 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 assuredwhen the adjacent node indicates the SF on the protection link. The failurebe cleared when the adjacent node indicates that the SF condition on protelink has been cleared. A far-end protection defect prevents fail-overs fromoccurring until the defect has been cleared. A protection switch defect prevfail-overs from occurring until the defect has been fixed. Inhibited by a protection link defect or a PSB defect.

Far-End Protection-Line FailureThis parameter indicates a Far-End protection defect has active for 2.5 seconds. The failure will be cleared when the adjacent nodeindicates that the protection link has been cleared for over 10 seconds. Aend protection failure alarm prevents fail-overs from occurring until the failhas been cleared. Inhibited by a protection link defect or a PSB defect.

Channel Mismatch DefectThis parameter indicates an APS protocol error for 1:n or 1+1 bidirectional APS configurations only. If the channel numbers don’t match3 consecutive OC-3 frames, then a channel mismatch defect will result. Tchannel mismatch defect is cleared when the channel numbers match foseconds or the channel mismatch has been inhibited. Under normal circumstances, a mismatch occurs every time the tail end changes the chnumber in K1. A mismatch can also occur if the link between the two LTEfails and the channel number received does not equal the transmitted chanumber in K1. Inhibited by a protection link defect, a protection switching bdefect, or an FEP defect.



een n the , the rm the

s:

an

ode end er es. EP

2.5 ol is nds. EP

Channel Mismatch FailureThis parameter indicates that a channel mismatch defect has bactive for over 2.5 seconds. The channel mismatch failure is cleared whechannel numbers match for 10 seconds. During Channel Mismatch Failureswitch of the receiver will be reverted back to the working link until the alaclears. A protection switch defect prevents fail-overs from occurring until defect has been fixed.Also during a channel mismatch failure, APS will output a K1/K2 as followK1 Condition Code = NO REQUESTK1 Channel Number = NULL CHANNELK2 Channel Number = NULL CHANNELInhibited by a protection link defect, a protection switching byte defect, orFEP defect.

APS Mode Mismatch DefectAn APS mode mismatch indicates that this node’s switching mor directional mode do not match the configuration in the LTE on the other of the OC-3 segment. If a OC-3 LIM is configured for any other mode oththan unidirectional one-plus-one, an APS mode defect will arise when theswitching and directional modes do not match for over 5 or more OC-3 framInhibited by a protection link defect, a protection switching byte defect, an Fdefect, or a channel mismatch failure.

APS Mode Mismatch FailureThis parameter that an APS mode defect has been active forseconds. The APS mode mismatch will be removed when the APS protocexchanged between the two nodes without mode mismatches for 10 secoInhibited by a protection link defect, a protection switching byte defect, an Fdefect, or a channel mismatch failure.


Line Interface Modules SONET/SDH Defects

a

r. s or

nds.

nds

nal

SONET/SDH Defects



3. Select SONET/SDH Defects . Select Down to view longer lists.

4. 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

Defects Definitions

LOS Defect: Loss of Signal DefectDeclared when all zero's are received for 20 +/- 3 microseconds or longeCleared when two valid framing words are detected. There are no defectfailures 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 secoThere 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 millisecoand is not inhibited. Cleared when an in-frame condition persists for 3 milliseconds or a defect inhibitor becomes active. Inhibited by: Loss of Sig(LOS).

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




onds ited

the

and ted ),

ast e s.

cted al

least ct oss

S-P

r at arm ited

RDI-tive

LOF Fault: Loss of Frame FailureDeclared when Loss of Frame Defect is declared for at least 2.5 +/- 0.5 secand is not inhibited. Cleared when Loss of Frame Defect is absent or inhibfor 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 frameheader.

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 whenEBER 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 framesthe AIS-L defect is not inhibited. Cleared when any other pattern is detecfor 5 consecutive frames or is inhibited. Inhibited by: Loss of Signal (LOSLoss of Frame (LOF).

AIS-L Fault Line: Alarm Indication Signal FailureDeclared when the Line Alarm Indication Signal Defect is declared for at le2.5 +/- 0.5 seconds and no inhibitor failures are active. Cleared when LinAlarm Indication Signal Defect is absent or inhibited for 10 +/- 0.5 secondInhibited 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 detefor 5 consecutive frames or becomes inhibited. Inhibited by: Loss of Sign(LOS), Loss of Frame (LOF).

RDI-L Fault Line: Remote Defect Indicator FailureDeclared when the Line Remote Defect Indicator Defect is declared for at 2.5 +/- 0.5 seconds and is not inhibited. Cleared when Line Remote DefeIndicator Defect is absent or inhibited for 10 +/- 0.5 seconds. Inhibited by: Lof 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 APdefect 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 foleast 2.5 +/- 0.5 seconds and is not inhibited. Cleared when STS Path AlIndication Signal Defect is absent or inhibited for 10 +/- 0.5 seconds. Inhibby: 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 P defect not inhibited. Cleared when bit 5 of byte G1 is '0' for 10 consecuframes or is inhibited. Inhibited by: LOS, LOF, RDI-L, AIS-L, LOP-P.



least ct :

ited. he

+/- ct is

ame d

C2 efect

/- 0.5 r F,

far-tive l is ct is

abel ited. for

n is late

tion

+/-

es. .

RDI-P Fault Path Remote Defect Indicator FailureDeclared when the Path Remote Defect Indicator Defect is declared for at 2.5 +/- 0.5 seconds and is not inhibited. Cleared when Path Remote DefeIndicator Defect is absent or inhibited for 10 +/- 0.5 seconds. Inhibited byLOS, 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 inhibCleared when valid pointers are found in 3 consecutive frames or when tLOP-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.50.5 seconds and is not inhibited. Cleared when STS Loss of Pointer Defeabsent 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 fris set to a value of 0 for 3 consecutive SONET frames, a path unequippedefect (P-UNEQ) is generated, provided the defect is not inhibited. Cleared when the far-end begins sending SONET frames indicating in thebyte that ATM cells are embedded in them or when the path unequipped dis 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 +seconds and is not inhibited. Cleared when Path Remote Defect IndicatoDefect is absent or inhibited for 10 +/- 0.5 seconds. Inhibited by: LOS, LOAIS-L, AIS-P, LOP-P.

PLM-P Defect STS Payload Label Mismatch (mismatch between the local LTE and theend LTE). Declared when the payload label is not 13 (hex) for 3 consecuframes andno inhibitor defects are active. Cleared when the payload labe13(hex) for 3 consecutive frames or when the payload label mismatch defeinhibited. Inhibited by: LOS, LOF, AIS-L, AIS-P, LOP-P.

PLM-P Fault STS Payload Label Mismatch Failure. Declared when the STS Payload LMismatch Defect is declared for at least 2.5 +/- 0.5 seconds and is not inhibCleared when STS Payload Label Mismatch Defect is absent or inhibited10 +/- 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 Delineatiodetected and is not inhibited. Cleared when the LIM can successfully calcuHCS for ATM cell headers for 6 consecutive ATM cells or when the LOCDdefect is inhibited. Inhibited by: LOS, LOF.

LOCD Fault Loss of Cell Delineation Failure. Declared when the Loss of Cell DelineaDefect 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 100.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 framCleared when a normal pointer value is detected in 3 consecutive frames



11' for

H2) d for

M

s for ed for

tive

by riod.

/

ects

l

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 '15 consecutive frames from the remote ECC Force AIS-L.

AIS-P TS Path Alarm Indication SignalDetected when an all ones pattern is received in the pointer bytes (H1 andfor 3 consecutive frames. AIS-P is cleared when a valid pointer is detecte3 consecutive frames.

PLM-P TS Payload Label MismatchDetected when the received payload label is a value other than 0x13 (ATMapping).

RFI-L Line FERF Remote Failure Indicator-LineDetected when a '110' pattern is detected in bits 6,7 and 8 of the K2 byte5 consecutive frames. Cleared when any other pattern than '110' is detect5 consecutive frames

RFI-P Remote Failure Indicator-PathFormerly Path Yellow. Detected when bit 5 of G1 byte is '1' for 10 consecuframes. 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 monitoring the number of Path BIP-8 errors accumulated in a 1 second pe

Section Statistics

CV-Ss Section Coding ViolationsCount of BIP Errors detected at the Section Layer of the incoming OC-3CSTM-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 defwere detected.

SES-Ss Section Severely Errored SecondsAny second with 2500 or more CV-Ss, or where 1 or more Loss Of Signadefects were detected.



-1

d.

ted.

lure

and

of 10 S-Ls

far

cted.

re larm ds in

d. , t the onds

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/STMsignal (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 detecte

SES-L Near-End Line Severely Errored SecondsAny second with 2500 or more CV-Ls, or where an AIS-L defect was detec

FC-L Near-End Line Failure CountsCount of the number of occurrences of near-end line failure events. A faievent occurs when the AIS-L alarm is declared, and ends when the AIS-Lalarm is cleared. A failure event that begins in one accumulation intervalends 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 consecutive seconds where no SES-Ls occur. The 10 seconds without SEare excluded from unavailable time.

CV-LFE Far-End Line Coding ViolationCount of BIP errors detected at the Line layer of the incoming signal at theend (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 dete

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 failuevent occurs when the RFI-L alarm is declared, and ends when the RFI-L ais cleared. A failure event that begins in one accumulation interval and enanother 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 enThe Line becomes unavailable at the onset of 10 consecutive SES-LFEswhich are included in the unavailable time. The line becomes available aonset of 10 consecutive seconds where no SES-LFEs occur. The 10 secwithout SES-LFEs are excluded from unavailable time.



TM-

t is

ilure when one n

et of ut

-

.

ure alarm ds in

The h are

et of thout

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/S1 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 defecdetected.

FC-P STS Path Near-End Failure CountsCount of the number of occurrences of near-end Path failure events. A faevent begins when either an LOP-P or AIS-P alarm is declared, and ends the LOP-P and/or AIS-P alarms are cleared. A failure event that begins inaccumulation interval and ends in another is counted only in the interval iwhich 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 ons10 con-secutive seconds where no SES-Ps occur. The 10 seconds withoSES-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/STM1signal 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 failevent begins when the RFI-P alarm is declared, and ends when the RFI-P is cleared. A failure event that begins in one accumulation interval and enanother 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.Path becomes unavailable at the onset of 10 consecutive SES-PFEs whicincluded in the unavailable time. The Path becomes available at the ons10 consecutive seconds where no SES-PFEs occur. The 10 seconds wiSES-PFEs are excluded from unavailable time.


Line Interface Modules IMA LIMs

A vide

nks

nks

arly

MA nts M ed

uits ither

.

y

IMA its

a IMA

d for ve for

IMA LIMs

Two LIMs support ATM Inverse Multiplexing with the PCx slot controller:

• DSX1-IMA (Future implementation)

• E1-IMA (Future implementation)

Each LIM provides a 16-link physical DS1 or E1 interface for the ECC controller. Individual IMLIMs comply with standard DS1 and E1 physical-layer interface specifications. The LIMs proinverse multiplexing of an ATM cell stream over multiple physical links, and reassemble theoriginal stream at the far end from these links. In the transmit direction the ATM cell stream received from the ATM layer is uniformly distributed on a cell-by-cell basis across multiple liin IMA Group. The uniform distribution of cells to the IMA links is performed on a cyclical, "round-robin" fashion. In the receive direction, the cells are reassembled from the multiple liinto the original ATM layer 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 slot controller and may be configured as eindividual 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 Group 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.


Line Interface Modules IMA LIMs

col l used wo

lls

le ot

dle ot

IMA Group BandwidthThe PCx provisions IMA Bandwidth automatically when links are assigned to an IMA group.

• 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 2-48 cells, the IMA sends out a Stuff Cell. (TStuff 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-12 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)


Line Interface Modules E1 IMA Configuration

h link

5) hen

E1 IMA Configuration

By default, the 16 E1-IMA physical links are disabled and inactive. To enable each link, eacmust first be assigned to an IMA Group and made active, as described below.

1. Establish a Telnet session to the PCx slot controller for the E1-IMA LIM.

2. From the PCx root menu, select Manage Configuration .

3. At the MIB Management and Display screen, select E-Series LIM information . The E-Series Lim Informatiopn screen appears, similar to the example below.

4. From the E-Series LIM Information screen, select E1 LIM . The E1 LIM screen appears, asshown below.

5. From the E1 LIM screen, select E1 Link Configuration , then select the Extra detail screen to configure link 0. An example Extra Detail screen of entry 0 is shown below.

6. Change the parameters for link 0 as required. Repeat for all remaining links (1 through 1using the Down/Up commands. Refer to the parameter descriptions below as needed. Wcomplete, advance to the IMA Configuration procedure later in this chapter.

Switch Name: Slot X SYS E-Series LIM 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



Line Interface Modules E1 IMA Configuration

tions

ink

cted

ms

ink.

M

the

mit

er to

E1 IMA LIM 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. Opare: 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 toactive (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 LConfig parameter.port up indicates the port is enabled by the user and no alarms are detein the receive data stream.port down indicates the user has enabled the link but one or more alarare detected in the receive data stream.

Tx Clk Source Selects the timing source to used to drive the transmit data line for this l(Immediate effect)master-timing - use the master transmit timing source that is set in LITiming and the Slot 0 System Timing. (Defalt setting)loop-timing - use the extracted clock from the receive data stream astransmit source.

XOR w/55H Adds the coset polynomial to the HCS octet prior to insertion in the transstream. (Immediate effect). Options are: Enabled or Disabled .

Scramble Cell PayloadScrambles the 48 octet info field of ATM cells. Also forces the receivexpect 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 BitSelects the Si0 International Bit used in the E1 Framing. (Immediate effect)Options are Set and Cleared.

Si1 International BitSelects the Si1 International Bit used in the E1 Framing. (Immediate effect)Options are Set and Cleared.


Line Interface Modules DSX-1 IMA LIM Configuration

ach

w.

5) hen

DSX-1 IMA LIM Configuration

By 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 PCx slot controller for the DSX1-IMA LIM.

2. From the PCx root menu, select Manage Configuration .

3. At the MIB Management and Display screen, select E-Series LIM information . The E-Series Lim Informatiopn screen appears, similar to the example below.

4. From the E-Series LIM Information screen, select DS1 LIM . The DS1 LIM screen appears,as shown below.

5. From the DS1 LIM screen, select DS1 Link Configuration , then select the Extra detail screen to configure link 0. An example Extra Detail screen of entry 0 is shown belo

6. Change the parameters for link 0 as required. Repeat for all remaining links (1 through 1using the Down/Up commands. Refer to the parameter descriptions below as needed. Wcomplete, advance to the IMA Configuration procedure later in this chapter.

Switch Name: Slot X SYS E-Series LIM 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 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



Line Interface Modules DSX-1 IMA LIM Configuration

tions

ink

cted

ms

ink.

as

mit

o

le the

y

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. Opare: 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 toactive (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 LConfig parameter.port up indicates the port is enabled by the user and no alarms are detein the receive data stream.port down indicates the user has enabled the link but one or more alarare detected in the receive data stream.

Tx Clk Source Selects the timing source to used to drive the transmit data line for this lmaster-timing will use the master transmit timing source that is set inLIM Timing and the Slot 0 System Timing (default setting).loop-timing will use the extracted clock from the receive data streamthe transmit timing source.

XOR w/55H Adds the coset polynomial to the HCS octet prior to insertion in the transstream. (Immediate effect) Options are Enabled or Disabled.

Scr Cell Payld Scrambles the 48 octet info field of ATM cells. Also forces the receiver texpect 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. Idcells and IMA ICP cells will produce excessive zeros (EXZ) indications perANSI T1.231-1997 specification. One or more EXZ per second causes anErrored Second. 1544 or more EXZ's per second will generate a SeverelErrored 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


Line Interface Modules IMA Configuration

to

gure to

MA ions

the

IMA ConfigurationOnce 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. Select eXit until the MIB Display and Management screen appears.

2. From the MIB Management and Display screen, select IMA . The IMA screen is displayed asshown below.

3. From the IMA screen, select IMA Link Table, then select the Extra Detail screen to confiIMA features for link 0. An example Extra Detail screen of entry 0 is shown below. Referthe description of parameters following the procedure as needed.

4. 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. The Group Index optare 1 throug.

5. 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.

6. 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.

7. When complete, proceed to step 8.

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



).et to

ICP

as

via p. ected.

A

6.001

le or the

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-8Row Status can only be changed when the corresponding Group Index is s 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 For a Group Index range, the system will prompt with [0-4294967295]. Disregard those values and only use the valid values 1 through 8.

NE Tx State The current state of the near-end transmit link. (Read only)(See Note 1 below)

NE Rx State The current state of the near-end receive link. (Read only)(See Note 1 below)

FE Tx State The current state of the far-end transmit link as reported via ICP cells. (Read only) (See Note 1 below)

FE Rx State The current state of the far-end receive link as reported via ICP cells. (Read only) (See Note 1 below)

NE Rx Fail Stat The current link failure status of the near-end receive link. (Read only) (See Note 2 below)

FE Rx Fail Stat The current link failure status of the far-end receive link as reported via cells. (Read only) (See Note 2 below)

Tx LID The outgoing LID used currently on the link by the local end. This value hmeaning only if the link belongs to an IMA group. (Read only)

Rx LID The incoming LID used currently on the link by the remote end as reportedICP cells. This value has meaning only if the link belongs to an IMA grouThe distinguished value of 31 may be used if the receive LID has not yet been det(Read only)

Relative Delay The latest measured delay on this link relative to the link in the same IMgroup with the least delay. (Read only)

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.



g

ted as

,

set of with

set of ds

x LSM.

x LSM.

n ult)

n of

uring

ce.st.

ct is

IMA Violations ICP violations: count of errored, invalid or missing ICP cells, except durinSES-IMA or UAS-IMA conditions. (Read only)

NE Sev Err Secs Count of one second intervals containing >= 30% of the ICP cells counIV-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. (Read only)

FE Sev Err Secs Count of one second intervals containing one or more RDI-IMA defectsexcept during UAS-IMA-FE condition. (Read only)

NE Unavail Secs Count of unavailable seconds at near-end: unavailability begins at the on10 contiguous SES-IMA and ends at the onset of 10 contiguous secondsno SES-IMA. (Read only)

FE Unavail Secs Count of unavailable seconds at far-end: unavailability begins at the on10 contiguous SES-IMA-FE and ends at the onset o 10 contiguous seconwith no SES-IMA-FE. (Read only)

NE Tx Unusbl Se Tx Unusable seconds: count of Tx Unusable seconds at the near-end T(Read only)

NE Rx Unusbl Se Rx Unusable seconds: count of Rx Unusable seconds at the near-end R(Read only)

FE Tx Unusbl Se Tx Unusable seconds at far-end: count of seconds with Tx Unusable indications from the far-end Tx LSM. (Read only)

FE Rx Unusbl Se Rx Unusable seconds at far-end: count of seconds with Rx Unusable indications from the far-end Rx LSM. (Read only)

NE Tx Failures The number of times a near-end transmit failure alarm condition has beeentered on this link (i.e., some form of implementation specific transmit fa(Read only)

NE Rx Failures The number of times a near-end receive failure alarm condition has beeentered on this link (i.e., LIF, LODS, RFI-IMA, misconnected or some formimplementation specific receive fault). (Read only)

Rx Test Pattern Identifies the test pattern received in the ICP Cell (octet 17) on the link dthe IMA Test Pattern Procedure. This value may then be compared to thetransmitted test pattern. (Read only)

Test Proc Statu This value indicates the current state of the Test Pattern Procedure. (Read only) disabled indicates the test is not running.operating indicates the test is running and no error found on this interfalinkFail indicates an error has been detected on this link during the teOnce an error is detected, the linkFail value is latched until either this objeread 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.

8. Select eXit until the Manage Configuration screen for PCx/IMA slot is displayed. The MIBDisplay and Management screen appears.

9. Exit back to the IMA screen by typing x . The IMA screen is displayed.



efer

A

hich ugh

active.

p. ified

is

MA

p.

e, nt

10. 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.

11. 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

12. 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.

13. 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.)

14. 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 sufficienumber of T1/E1 links are restored, or the operator lowers the MIN/MAX values.

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



.

le

nge.

.

roup

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 Tabbefore setting Row Status to active .

IF Index Identifies the logical interface number assigned to this IMA group. (Read only)Note that re-initializing the management agent may cause IF Index to cha

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 GTraffic State Manager (GTSM) is in the down state. (Read only)Status messages are:

noFailurestartUpNestartUpFeinvalidMValueNeinvalidMValueFefailedAssymetricNefailedAssymetricFeinsufficientLinksNeinsufficientLinksFeblockedNeblockedFeotherFailureinvalidImaVersionNeinvalidImaVersionFe



ted.

ar-

of 0 e

-end

of 0 e

yet

in

n.

s

Symmetry Symmetry of the IMA group. Note that only symmetricOperation is suppor(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).

Note 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)Status 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 neend for IMA data cell clock recovery from the ATM layer. (Read only)The valid range of link numbers is 0 through 15. The distinguished value may be displayed if no link has been configured in the IMA group, or if thtransmit timing reference link has not yet been selected.

Note 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 nearfor IMA data cell clock recovery toward the ATM layer. (Read only)The valid range of link numbers is 0 through 15. The distinguished value may be displayed if no link has been configured in the IMA group, or if threceive 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.

Note The Tx IMA ID is selected automatically by the switch node.

Rx IMA ID The IMA ID currently in use by the far-end IMA function. (Read only)The distinguished value of 255 may be used if the receive IMA id has notbeen detected.

Tx Frame L The frame length (in cells) to be used by the IMA group in the transmit direction. (Read only) This is a fixed value and is set when an IMA group is 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 functio(Read only) Status messages are: m32, m64 , m128 , m256 (Default is m128).

Diff Delay The maximum number of milliseconds of differential delay among the linkthat will be tolerated on this interface. (Read only)This value is 25 milliseconds.



of 0 ink

the links

ells te.

ells to .

cells c

has

nt-

IMA ive

IMA e

in

in

ure.

est link of the

Least Dela The link number of the link configured in the IMA group which has the smallest link propagation delay. (Read only) The valid range of link numbers is 0 through 15. The distinguished value may be displayed if no link has been configured in the IMA group, or if the lwith the smallest link propagation delay has not yet been determined.

Dif Dly Ma The latest maximum differential delay observed (in milliseconds) betweenlinks having the least and most link propagation delay among the receive that are currently configured in the IMA group. (Read only)

Alpha The 'alpha' value used to specify the number of consecutive invalid ICP cto be detected before moving to the IMA Hunt state from the IMA Sync sta(Read only) Range is 1 through 2. Set to default value of 2.

Beta The 'beta' value used to specify the number of consecutive errored ICP cbe 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 ICPto be detected before moving to the IMA Sync state from the IMA PreSynstate. (Read only) 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. (Read only)

Unavail Se Count of one second intervals where the IMA Group Traffic State Machinebeen Down. (Read only)

NE Failure The number of times a near-end group failure (Config-Aborted, InsufficieLinks) has been reported since power-up or reboot. (Read only)

Tx Avail C The current cell rate (truncated value in cells per second) provided by this group in the transmit direction, considering all the transmit links in the Actstate. (Read only)

Rx Avail C The current cell rate (truncated value in cells per second) provided by this group in the receive direction, considering all the receive links in the Activstate. (Read only)

Tx Cfg Lin The number of links configured to transmit in this IMA group. (Read only)

Rx Cfg Lin The number of links configured to receive in this IMA group. (Read only)

Tx Actual The number of links configured to transmit and which are currently Activethis IMA group. (Read only)

Rx Actual The number of links configured to receive and which are currently Activethis IMA group. (Read only)

Test Link Used to designate a link as the test link or use in the Test Pattern Proced(Immediate effect) The valid range is 0 through 15. Default is 0

Note The Test Link value is NOT the same as the Tx LID value, but instead identifies the link value of the tto be used by the Test Pattern Procedure (i.e., the link whose LID value is inserted in the Tx LID fieldtransmitted ICP cells).



.

nus) ose

Test

ace is t pback ttern

at least

to or

will

el

Test Patte Used to specify the Tx Test Pattern in an IMA group loopback operation(Immediate effect) A value in the range 0 to 255 designates a specific pattern. Default is - (mi1. The distinguished value of -1 specifies that the implementation may chothe value. In this case, the implementation may also choose the value of Link IF Index.

Note It is recommended that the specific value 255 not be used for testing, since by (R-137) the IMA interfrequired to transmit 0xFF (i.e., 255) when the incoming test command is inactive or the test link is nodetected, and thus it cannot be established for certain whether 255 was received due to an actual loooperation or due to the normal operation of an IMA that is not performing (or cannot perform) the test paprocedure.

Note 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 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 statuslinkFail. The linkFail state will persist until either the disabled state is set until no instance of Test Proc Status has the value linkFail. Options are: disabled , operating , linkFail . Default is disabled .

Note For the Test Proc, only the values disabled and operating may be written. Writing the operating valuenot 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 Labfrom the FE IMA unit at this time. Range is 0 through 255.


Line Interface Modules 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-13 displays the transceiver operating parameters andmanfufacturer’s information for the SFP associated with either of the two links.


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-13 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

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

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


F

prise OSPF

vailable

CLI. de you

that ate

gure

g the

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 convergence time. OSPF is widely used in large networks such as ISP backbone and enternetworks. The following paragraphs describe how to use the OSPF commands to configureparameters, show 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 interfaces, and setting the router id. This mode is entered from the configure mode by typinfollowing command: router ospf . Router Mode emplys the ospfd(config-router)# prompt.

032R401-V710 Xedge MSPx System Version 7.1.0 A-1Issue 4 Configuration Guide

OSPF CLI Reference OSPF Guidelines and Examples

nterface ing

d in

ons.

Interface Mode

Interface-specific OSPF parameters are entered in this mode. To access this mode, enter i<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.1.0 032R401-V710Configuration Guide Issue 4

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 reestabish adjacencies with its neighbours after restarts/reboots. The host shousystem time be set at boot from an external source (eg 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 specifed 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


The Best Connections in the Business

xedgemspx - gdc032r401-v710 xedge mspx system version 7.1.0 v issue 4 configuration guide preface...

Documents