3UR6SKHUH 106Preface Support Services and Training vi ProSphere NMS 032R610-V601 Version 6.0.1 User...

9HUVLRQ#91314#8VHU#*XLGHfor Xedge MultiService Switch Systems

032R610-V601 Issue 1July 2016

3UR6SKHUH#106

of this readable bject

the use mages.

roducts.isions.

Copyright©2016 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:

http://www.gdc.com

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

Documentation

Revision History GDC P/N 032R610-V601

Related Publications

-REV is the hardware revision (-000 , -001 , etc.) -VREV is the most current software version (-V530, V620, V722, etc. ) In addition to publications listed above, always read any Patch Notes and Addenda supplied with your pBrowse to http://www.gdc.com to access the Technical Publications Library for the latest document rev

Issue Date Description of Change

1 July 2016 Release of ProSphere NMS Software Version 6.0.1

Description Part Number

Xedge / ProSphere Deployment Guide (for military systems) Contact GDC

Xedge / ProSphere Security Administration Guide (for all Xedge systems) 032R298-000

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

Xedge Hardware Installation Guide (for all Xedge systems) 032R440-000

Xedge 6000 for MSPx Applications Version 7.4.X Software Configuration GuideXedge 6000 for MSPx Applications Version 7.4.X Release Notes

032R401-V74X032R901-V74X

Xedge 6000 for ATM Applications Version 6.2.X Software Configuration & Status GuideXedge 6000 for ATM Applications Version 6.2.X Release Notes, Cumulative Patch Notes

032R400-V62X032R901-V62XXX

ProSphere NMS Version 6.0.X User Guide (for all Xedge 6000 systems)ProSphere NMS Version 6.0.X Installation & Release Notes (CORE, AEM, GFM, SPM, RTM, XPM)

032R610-V60X032R906-V60X

Table of Contents

i

i

i

1

3

4

5

-5

7

7

3

-4

4

-6

-7

-7

8

-9

0

11

PrefaceSupport Services and Training................................................................................................. v

Corporate Client Services...................................................................................................v

Factory Direct Support & Repair........................................................................................vi

Contact Information............................................................................................................v

Chapter 1: Introduction to ProSphereProSphere NMS Overview..................................................................................................... 1-1

Features & Benefits..........................................................................................................1-

ProSphere Core Functions................................................................................................1-1

ProSphere Applications....................................................................................................1-1

Navigating the ProSphere GUI.........................................................................................1-2

ProSphere Functions.............................................................................................................. 1-

User Management.................................................................................................................. 1-

User Login Procedure.......................................................................................................1-4

Default User Names..........................................................................................................1-

Access Types....................................................................................................................1

Secure Shell (SSH)................................................................................................................. 1-

Initial SSH Configuration.................................................................................................1-7

SSH at Client Side............................................................................................................1-

Chapter 2: Topology ManagementOverview................................................................................................................................ 2-1

Communications Manager..................................................................................................... 2-2

SNMP Procedures.............................................................................................................2-

Auto Discovery...................................................................................................................... 2

Before You Begin.............................................................................................................2-

Starting and Stopping Discovery......................................................................................2-5

Polling Status....................................................................................................................2

Network Views....................................................................................................................... 2

Map View.........................................................................................................................2

ProSphere Explorer...........................................................................................................2-

Object Editor.....................................................................................................................2

Shelf View......................................................................................................................2-1

Add Wizard.......................................................................................................................... 2-

Adding a New Network..................................................................................................2-11

Adding a Network Element (Node)................................................................................2-12

Adding a Card to a Node................................................................................................2-14

Adding a LIM to a Card.................................................................................................2-15

Creating Connections.....................................................................................................2-16

032R610-V601 ProSphere NMS iIssue 1 Version 6.0.1 User Guide

Table of Contents

1

2

-2

-4

-5

6

7

8

-8

1

1

1

2

4

5

1

1

2

3

3

-4

Chapter 3: Element ManagementConfiguration Overview......................................................................................................... 3-

Element Manager Tool Set...............................................................................................3-1

Node Configuration................................................................................................................ 3-

General Tab......................................................................................................................3

Physical Tab.....................................................................................................................3

Version Tab.....................................................................................................................3

Redundancy Tab...............................................................................................................3-

Static Routes Tab..............................................................................................................3-

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

General Tab......................................................................................................................3

SNMP Authentication Tab...............................................................................................3-9

SVC Configuration Tab.................................................................................................3-10

Link Configuration............................................................................................................... 3-1

General Tab....................................................................................................................3-1

Physical Tab...................................................................................................................3-1

Resources Tab.................................................................................................................3-1

Signaling Tab..................................................................................................................3-1

Management Tab............................................................................................................3-1

Selected Application Tutorials............................................................................................. 3-15

Chapter 4: Service Provisioning (SPM)Service Provisioning Overview.............................................................................................. 4-1

Creating Services..............................................................................................................4-

Using Services..................................................................................................................4-

Importing Circuits.............................................................................................................4-

Moving Circuits across Services......................................................................................4-2

Presets...............................................................................................................................4-3

Creating Circuits...............................................................................................................4-

Managing SPM Circuits...................................................................................................4-6

Chapter 5: Alarm ManagementOverview................................................................................................................................ 5-1

Alarm Configuration Screen.................................................................................................. 5-2

Configuration Parameters.................................................................................................5-3

Changing Configuration...................................................................................................5-3

Reset to Defaults...............................................................................................................5-

Active Alarms........................................................................................................................ 5

Active Alarms Screen.......................................................................................................5-5

ii ProSphere NMS 032R610-V601Version 6.0.1 User Guide Issue 1

Table of Contents

6

2

3

2

4

5

6

7

8

1

-1

2

7

7

1

Email Notification............................................................................................................5-

Alarm Polling and Masking................................................................................................. 5-12

Alarm Polling.................................................................................................................5-1

Alarm Masking...............................................................................................................5-1

Chapter 6: Routing Manager (RTM)Overview................................................................................................................................ 6-1

Manage Path Cost.................................................................................................................. 6-

Connection Cost Preferences............................................................................................6-2

Cost Setup Preferences.....................................................................................................6-3

Route Generation Panel.......................................................................................................... 6-

Configurations Panel.............................................................................................................. 6-

Routes View Panel................................................................................................................. 6-

Manage Routes Panel............................................................................................................. 6-

Route Viewer Panel................................................................................................................ 6-

Appendix A: MSPx ApplicationsIntroduction............................................................................................................................ A

Typical MSPx Applications.............................................................................................. A1

Ethernet over MPLS Example............................................................................................... A3

Basic Node Configuration................................................................................................ A4

Transport Configuration................................................................................................... A7

Configure Services (SPM).............................................................................................. A11

Appendix B: Application TutorialsIntroduction........................................................................................................................... B

IMA Configuration Guidelines............................................................................................. B-1

IMA Configuration................................................................................................................ B-

IMA Configuration Link/Group Mapping Tab...............................................................B-2

IMA Configuration Link Tab..........................................................................................B-4

IMA Configuration Group Tab........................................................................................B-5

IMA Configuration Verification......................................................................................B-6

MTS Configuration Tutorial................................................................................................. B-7

Node Configuration.........................................................................................................B-7

Slot Configuration...........................................................................................................B-

Link Configuration..........................................................................................................B-

Configure VPC Termination...........................................................................................B-8

Configure VPC Endpoints...............................................................................................B-9

Configure VP Queuing..................................................................................................B-10

QSIG Configuration............................................................................................................ B-1

032R610-V601 ProSphere NMS iiiIssue 1 Version 6.0.1 User Guide

Table of Contents

2

4

8

6

7

VSM Card for DS1 (DS1-2C/4C) or E1 LIM (E1-2C/4C)...........................................B-11

FRC Configuration.............................................................................................................. B-1

FRC Card for DS1 (DS1-2C) or E1 LIM (E1-2C).......................................................B-12

CHFRC Configuration....................................................................................................... B-1

CHFRC Card for DS1 (DS1-2C/4C) or E1 LIM (E1-2C/4C).......................................B-14

VSM Configuration............................................................................................................. B-1

VSM Card for DS1 or E1 LIM Types...........................................................................B-18

Bundle Configuration....................................................................................................B-20

Configuring Timeslots...................................................................................................B-23

LCE-16 LIM Configuration for ACP-II Card..................................................................... B-26

LCE-16 Configuration Overview..................................................................................B-26

Node Configuration.......................................................................................................B-26

Slot Configuration.........................................................................................................B-2

Link Configuration........................................................................................................B-2

iv ProSphere NMS 032R610-V601Version 6.0.1 User Guide Issue 1

ietary witch 00 for edge

ns.

ice y.

ntirely ts, it omm,

ual,

Preface

Scope of this ManualThis manual describes the ProSphere Network Management System Version 6.0.X, a proprNetwork Management System (NMS) designed to set up, control and monitor Xedge 6000 ssystems: Xedge 6000 for MultiService Packet Exchange (MSPx) applications, and Xedge 60ATM applications. ProSphere NMS can also discover components running older versions of Xswitch code, however some ProSphere applications may not fully support such older versio

This document is intended for qualified engineers who are familiar with the Xedge MultiservSwitches, Xedge network architecture, Xedge network management and related terminologRelated Publications are listed on the inside front cover of this document.

The information contained in this manual has been carefully checked and is believed to be ereliable. As General DataComm improves the reliability, function, and design of their producis possible that the information in this document may not be current. Contact General DataCyour sales representative or point your browser to http:\\www.gdc.com for the latest information on this and other General DataComm products.

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, Introduction to ProSphere

• Chapter 2, Topology Management

• Chapter 3, Element Management

• Chapter 4, Service Provisioning (SPM)

• Chapter 5, Alarm Management

• Chapter 6, Routing Manager (RTM)

• Appendix A, Application Tutorials

• Appendix B, MSPx Applications

032R610-V601 ProSphere NMS vIssue 1 Version 6.0.1 User Guide

Preface Support Services and Training

cts, to pre-

lity in tomers

omers f GDC DC

nd ff used port the

anges n the

Support Services and TrainingGeneral DataComm provides comprehensive support of GDC hardware and software produincluding open source components. Two GDC customer support organizations are dedicatedand post-sale support services and training for GDC products. Corporate Client Services and Factory-Direct Support & Repair assist customers throughout the world in the installation, management, maintenance and repair of GDC equipment. Located at GDC’s corporate faciNaugatuck, Connecticut USA, these customer support organizations work to ensure that cusget maximum 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

http://www.gdc.com

vi ProSphere NMS 032R610-V601Version 6.0.1 User Guide Issue 1

t up, ized n be tures ific l

les in

s.

n a

dened

d

Setting

Chapter 1: Introduction to ProSphere

ProSphere NMS OverviewThe ProSphere Network Management System (NMS) is proprietary software designed to secontrol and monitor switches in an Xedge 6000 network. ProSphere NMS enables a centralmanagement scheme that can scale to support very large, multi-vendor networks. It can thepartitioned into sub-network domains, each with its own management. ProSphere NMS capcritical network performance data that allows users to view statistical trends relevant to specmeasurements in the Xedge network. This automated tool set can be customized for optimaperformance monitoring suited to network multi-service configurations.

This version of ProSphere NMS supports slot controllers, LIMs, switch fabric and other moduthe following Xedge switch systems:

• Xedge 6000 for Multiservice Packet Exchange applications (Version 7.X)

• Xedge 6000 for ATM applications (Version 6.2.X)

Note ProSphere can discover components running older versions of Xedge Switch code. Some ProSphereapplications may not fully support those older versions. Refer to ProSphere Release Notes for detail

Features & Benefits• Advanced, user-friendly graphical user interface

• Distributed, Object-Oriented, scalable architecture.

• Java-based applications, i.e., platform independent

• Supports PC/Windows platforms

• Supports Client / Server installation for multiple client access to the ProSphere Server oremote PC workstation.

• Supports Server only installation on a Windows PC workstation that has been security harto conform with the security needs of your mission critical network environment.

• Application, user, and security preferences can be configured to conform with heightenesecurity policies.

Note Secure installation on a hardened PC workstation is described in the ProSphere NMS Release Notes.application, user, and security preferences are detailed in the Security Administration Guide.

ProSphere Core Functions• User Management

• Topology Management

• Alarm Management

• Configuration Management

• File Management

ProSphere Applications• Performance Monitoring (XPM)

• Service Provisioning Manager (SPM)

• Routing Manager (RTM)

032R610-V601 ProSphere NMS 1-1Issue 1 Version 6.0.1 User Guide

Introduction to ProSphere ProSphere NMS Overview

Navigating the ProSphere GUIAll configuration and monitoring functions described in this document are executed via the ProSphere GUI windows, menus and buttons shown below.

PULLDOWN MENUS(See detail)

FUNCTION TABS(See detail)

FUNCTIONWINDOW

STATUS MESSAGE

BUTTON MENU(See detail)

FUNCTIONCOMMANDBUTTONS

SYSTEMMESSAGES

PULLDOWN MENUDETAIL

BUTTON MENUDETAIL

Add/ModifyRemoveClear MapRefresh Circuit StatusExport CircuitsSetup CircuitsStart CircuitsStop CircuitsKill CircuitsCopy CircuitsPresets ...Import Circuits

Show OptionsLook & FeelLayoutFrames

TopologyTree View (ProSphere Explorer)

TopologyMap View

ADDDELETE

REFRESH

VIEWTELNET

NODE

SLOTLINK

HELP

Alarms Create/ManageCircuits

TopologyDiscovery

PerformanceMonitor (XPM)

Exit DeleteDelete AllDiscovery

Active AlarmsAlarm Config

RoutingManager (RTM)

1-2 ProSphere NMS 032R610-V601Version 6.0.1 User Guide Issue 1

Introduction to ProSphere ProSphere Functions

des, to

uter/raft ctions ement

(PVCs from ical mplates

ardware en the rough ation

s that

re tables RTM

s, for r real-

ProSphere FunctionsProSPhere Topology Management

Topology Management provides GUI-based tools for the Auto Discovery of networks and nocontrolling SNMP communication parameters, monitoring the poll status of a node or the audiscovery, and management of users.

Note Refer to Chapter 2, Topology Management for more information on Discovery, Polling and SNMP Communication. User Management is detailed later in this chapter.

ProSphere Element ManagementThe Element Manager is a set of easy-to-use GUI-based tools that run on a personal complaptop to configure the Xedge switches in the network. Although Xedge devices provide a cinterface via telnet, some specialized applications such as VSM perform certain advance funlike block copy, delete that are not possible with the craft interface. In these situations, the ElManager is a necessary alternative to Telnet.

Note Refer to Chapter 3, Element Management for more information on configuration of Xedge switches.

ProSphere Service Provisioning Management (SPM)The ProSphere Service Provisioning Manager allows the user to create end-to-end circuits or SPVCs) across a network by means of a simple point-and-click on the termination pointsthe graphical Network Map. This sophisticated tool allows the circuits to be grouped into logunits so that they can be operated on as a single unit. The user can also setup predefined teto specify bandwidth and quality of service properties to be used by the circuits.

Note Refer to Chapter 4, Service Provisioning (SPM) for more information on creating PVCs and SPVCs.

ProSphere Alarm ManagementThe ProSphere acquires alarms by means of SNMP traps generated by the Xedge network hand by polling the Xedge network elements. Since an SNMP trap is generated only once whproblem occurs, polling ensures that for any lost trap, alarm conditions are always reported ththe polling mechanism. The ProSphere Alarm Management uses the traps and polling informto report problems within the Xedge network. The user can select Alarm Configuration optionchange alarm description, alarm severity and alarm polling parameters.

Note Refer to Chapter 5, Alarm Management for more information on Alarm Configuration, Active Alarms, AlarmPolling and Alarm Masking.

ProSphere Routing Manager (RTM)The ProSphere Routing Manager (RTM) is a new integral ProSphere application in ProSpheVersion 5.3.1 and later. RTM uses a map-based GUI to generate and manage static routingwhen there are SVCs or SPVCs in the Xedge network. In ProSphere NMS V5.3.1 and later,works directly within ProSphere without the need of exporting the topology.

Note Refer to Chapter 6, Routing Manager (RTM) in this document for detailed RTM procedures.

ProSphere Xedge Performance Manager (XPM)Xedge Performance Manager (XPM) is designed for wide area networks to aid network teamadministrators, and inventory managers in the proper utilization and allocation of resources optimal network performance. XPM collects diverse statistical information and generates neatime and historical trends into graphical displays and automated reports.


Introduction to ProSphere User Management

via the on the r user).

lick the

, as

User ManagementA valid username and password is required to access the interface. User access is defined ProSphere User Management function. The appearance of the screens will vary dependingspecific type of access authorized for a given operator (monitor, user, administrator or supe

User Login Procedure

1. Launch the StartServers by double-clicking the StartServers icon on the desktop.

2. After all Servers have started, click on the Start Client button, as shown below.

3. When the ProPShere Login screen appears, enter a valid User ID and Password, then cLogin button.

Note New users and passwords can be added by a special administrative user via the User Manager GUIdescrivbed in the next paragraphs.

2. Start Client Button

1. Servers Started

3. Login Screen



anager. ords.

tions. sers.

nager

er have P data

r Type critical

Default User NamesUsers are assigned access permissions to the Xedge system via the ProSphere Topology MThe Communications Server creates four default user names with associated default passw

• ProAdmin (Password: manager) has SuperUser access.

• nmsadmin (Password: nmsadmin) has Admin access.

• prospher (Password: prospher) has Monitor access.

• nmsoper (Password: nmsoper) has Operator access.

Note All default user names can be removed from the system except for the ProAdmin user name.

Access Types

Each access type has a well-defined set of access permissions for specific ProSphere funcTable 1-1 defines the access permissions that are associated with each of the four types of u

SuperUsers are the only users that can define access privileges for other Users. A User MaGUI in the ProSphere Client application allows for addition/removal of users and changing passwords for existing users. An example User Manager screen is shown below.

The user profiles are maintained by a ProSphere server so that all clients accessing the servaccess to the same, single set of user profiles. The Communications Server (maintaining SNMfor IP addresses and networks) will store and maintain the User Profiles (User ID, Name, Use& Password) in a separate file. There is a simple encryption mechanism that scrambles the information in this file, so that casual hacks on the password files are very difficult.

Note With ProSphere Version 5.3.1 and later, the SuperUser can define user access to ProSphere RTM.



Table 1-1 User Definitions and Privileges

Permissions

User Types(Default User ID)

Monitor(prospher)

Operator(nmsoper)

Admin(nmsadmin)

SuperUser(ProAdmin)

Add/Remove/Modify ProSphere Users

View TopologyDiscover/Add/Delete Network Elements

View ConfigurationsModify Configurations

View/Delete Active AlarmsModify Alarm Configurations & Mask Alarms

Refresh Circuit StatusSetup/Start/Stop & Kill CircuitsCreate/Modify/Remove Circuits & ServicesCopy/Move Circuits & Services

Performance Monitoring ConfigurationView Performance Monitoring Results

RTM Route GenerationRTM Route ManagementView RTM Routes

SNMP Configuration

SSH Configuration

USER MGMNT

DISCOVERY

CONFIGURATION

ALARMS

SERVICE PROVISIONING

PERFORMANCE

ROUTING

SNMP

SSH

NO

YESNO

YESNO

YESNO

YESNONONO

NOYES

NONOYES

NO

NO

NO

YESNO

YESNO

YESNO

YESYESYESYES

NOYES

NOYESYES

NO

NO

ProSphereCore Functions

NO

YESYES

YESYES

YESYES

YESYESYESYES

YESYES

YESYESYES

YES (default)

YES (default)

YES

YESYES

YESYES

YESYES

YESYESYESYES

YESYES

YESYESYES

NO

NO


Introduction to ProSphere Secure Shell (SSH)

et to n of

ust run

can be

d key

er” list,

rivate will etters

Secure Shell (SSH)

For secured installations, the SSH protocol (Secure Shell version 2) is used in place of Telnaccess the Xedge node menus. The SSH protocol is enabled as an option during installatioProSphere NMS.

Initial SSH Configuration

1. On initial startup, the seed table must be configured in order to set up SSH. The user mthe server, access the client, and add an IP address to the seed table.

2. Once the seed table is configured, select File->Setup SSH to open either of two windows shown below:

3. Select Server in the “Create key for user” list.

4. Type in the password in the “Password” field.

• For setting up the key pair for the server password is needed.

• For setting up key pair for other users, password is not necessary.

5. Select the key length and key type as necessary. (For Windows, key length and key typeset on the popup gui after the “Create” button is pressed.)

6. Click Create to generate the private/public key pair. This process also loads the createto existing ATM nodes.

7. Repeat the same procedures above for other users.

Add / Remove Access to Xedge Nodes

8. To add a new Xedge node, select Server in the “Create key for user” list, then click the Load button.

9. To remove access from an Xedge node, select the desired user in the “Create key for usthen click the Remove button.

SSH at Client Side

There is no configuration required on ProSphere Client. When ProSphere Client starts, the pkey is encrypted and sent from the server. After receiving the private key, ProSphere Clientverify SSH access to each existing ATM node. If an existing ATM node supports SSH, the l“SSH” will be shown at the bottom right corner of the window.


Introduction to ProSphere Secure Shell (SSH)


e NMS rk.

the

odes e

work lso

d es,

sions to

Chapter 2: Topology Management

OverviewNetwork topology describes the physical layout of a network, and defines all Xedge networkelements, such as nodes, cards, LIMS, ports and the connections between them. ProSpherconducts topology functions by means of SNMP requests with Xedge switches in the netwoTopology Management is comprised of the following functions:

• Auto Discovery of networks and nodes

• Shelf View, a GUI that provides a graphical representation of individual nodes andsubsequent configuration of that node.

• ProSphere Map, a network display of nodes and connections on a confihurable background image.

• ProSphere Explorer, a GUI that displays in a tree-like structure all of the networks, nand cards discovered on the network or added manually. ProSphere Explorer is thlaunching point for all configuration screens, shelf views, etc.

• Object Editor is used to view properties of elements in the ProSphere Explorer nettree, i.e., root, network, nodes, cards, slots, links and connections. Object Editor acontrols Alarm Masking and Alarm Polling.

• Add Wizard is a GUI that simplifies network modification by allowing the user to adand delete elements from the ProSphere Explorer network tree, i.e., networks, nodcards, LIMs and connections.

• User Manager allows the assignment of usernames, passwords and access permisauthorized users. (Refer to Chapter 1, Introduction to ProSphere for detailed information and procedures.)


Topology Management Communications Manager

added . For

y to has the

the

ation is

looks lobal

nd/or

Communications ManagerProSphere NMS communicates with the Xedge via SNMP requests. Authentication entries in Xedge devices will permit or deny access to various management stations in the networkXedge devices, the default read/write community name is public ; for MAC500 devices, the default name is admin .

For heightened security, the user can change the community name. It will also be necessarspecify the new community name in the management application so that the SNMP request right authentication.

The Communications Manager is accessed by selecting the SNMP Communications tab of Discovery tool. The SNMP information entered at this screen (shown below) is stored by ProSphere, along with some username and password parameters. This stored SNMP informused by the Telnet tool for a specific IP Address, or as a global default for the network.

When ProSphere applications (RTM, SMP, etc.) require details on a given IP address, the Communications Manager first looks for an exact IP address match. If it can't find one, it thenfor a match at the Network level. If no match is found, the manager returns a set of top-level Gsettings. In this way, the user can set SNMP and Telnet settings on a Global, per-Network aper-Device level.


Topology Management Communications Manager

cific IP lect

ch slot.

pe is

unity of

nity o Write

ameter n no

how een

SNMP Procedures

Add/Modify Command

Enter the IP address that you wish to change in the Address field. If you want to select a speaddress, you select Address as the Type. If you want to select a range of addresses, you seSubnet and then enter an appropriate mask.

For example: an Xedge 6640/6645 switch contains sixteen IP addresses corresponding to eaIn this case, the mask is 255.255.255.240 to allow for the 16 addresses.

Delete Command

Allows deleting entries made using the Delete command.

SNMP Control Parameters

• Type: either Address or Subnet (Global is the default).

• Address: typical IP addresses, such as 192.168.77.66

• Subnet (Mask): 255.255.255.255, available only with Subnet, or is left blank if the node tyGlobal.

• Community: The community feature lets you set the SNMP community string. The commstring allows you to control SNMP access to a device and to add a security level by waySNMP. Note that the corresponding community string would be set up in the SNMP authentication table for the devices.

• Read Community/Write Community: used to set the SNMP community string. The commustring restricts SNMP access to a device. The names assigned to Read Community and tCommunity can be any combination of alphanumeric or keyboard characters.

• Timeout: settings in intervals of seconds, where the range is 0 to 1000 seconds. This pardetermines when ProSphere will attempt to send another SNMP packet if there has beeresponse from the device.

• Retries: number of automatic retries within a timeout interval. This parameter determinesmany times ProSphere will attempt to send an SNMP packet if the timeout period has bexceeded.


Topology Management Auto Discovery

works. ere etailed

s on the ese are

nd

ices

s and

ication

e will

bles of

Auto Discovery

The Discovery tool controls the process of discovering networks and the devices in those netIt can be used to quickly build network topology in the Managed Object Manager (MOM). Thare two distinct stages of Discovery that detect a device on the network and then get more dinformation on supported devices:

• IP Discovery Stage: this stage uses seeds (IP addresses) to discover all supported devicenetwork. Each seed is asked about what other IP addressable devices it knows about. Ththen contacted and asked the same question. This process is artificially limited to MOLNnetworks.

• Node Polling Stage: this stage takes the IP addresses found in the IP Discovery stage aattempts to get more detailed information about each device, such as standard system information, device configuration (cards, power supplies, etc.). Note that only Xedge devare currently supported.

Before You Begin

Before you attempt to discover the Xedge nodes in the network, perform the following checkpreparations:

1. Ensure that PC’s IP address (where ProSphere resides) has been added to the authenttable of all packet controllers in Xedge nodes to be discovered.

Note If the authentication table of an installed packet controller does not have the PC’s IP address, that nodnot be discovered by ProSphere.

2. At the PC’s command line, add a persistent route using the following syntax:

route -p add [first network IP address] mask [network mask] [gateway IP address]

For example, given an Xedge network where the Seed IP (Xedge node) is 192.150.150.16 and the Gateway IP is 172.16.69.20 , the command would read as follows:

route -p add 192.150.150.0 mask 255.255.255.0 172.16.69.20

3. Check connectivity by pinging or telnetting to all slot controllers in each node.

4. At the ProSphere Discovery window, select the Discovery Status tab and add a Seed IPaddress.

5. At the Topology menu, select Discovery/Start (F5) to start discovery of the network.

6. To check the discovery process, select the Poll Status tab to start discovery.

Note If the network is not discovered, recheck the route added to the PC and ensure that authentication taall packet controllers have been updated.



on in

eed s the

w.

that if

Starting and Stopping Discovery1. The Discovery tool can be started from the Explorer by either clicking the Discovery butt

the toolbar or by selecting Topology->Discover->Start menu, as shown below.

2. The first time the Discovery tool is used, the user must enter one or more seeds in the stable when prompted. Simply enter a seed (IP address) into the seed field and then pres Enter key or the Add button.

3. To monitor the progress of the auto discovery, select the Poll Status tab, described belo

4. Use the Filters page as needed to exclude IP addresses from the discovery process so they are found, they will not register with the Node Polling stage.



ecking polled

rk. The twork. a card

Polling Status

The user can monitor the progress of the auto discovery or of a current poll of a node by chthe Poll Status tab at the Discovery window. This tab showns which nodes are currently beingand whether the discovery was successful for a node.

Note that the topology does not have to be an exact representation of the actual Xedge netwotopology can be a planned topology, or a combination of both the actual and the planned neSimply changing the topology does not affect the actual network. For instance, you can addto the topology, even though that card is not actually added to the node.


Topology Management Network Views

ered ards,

ws the green.

his n of

ge

h as:

Network ViewsProSphere NMS provides two views of the network: Map View or ProSphere Explorer. Discovobjects are automatically placed on the network views. Both views show networks, nodes, cLIMs, ports and connections.

Map View

The ProSphere Map View shows all nodes and connections between the nodes. It also shocolor of the highest severity of the alarms on that node. If there are no alarms, the node will be

Viewing Options

• Select View->Layout to perform an automatic layout of the nodes and connections. Toption will attempt to arrange nodes and connections in an optimal viewing representatiothe network.

• Select View->Show->Background Image to display the background image for the Map.

• To define a custom image as the background, select View->Show->Set image... Set Imamenu item.

• Menu options from the View->Show menu will display additional features and details, sucNode IP Addresses, Icons, Connection Labels or Connection Types (LIM Type of the connection.

• The View->Look and Feel menu allows the user to change the look of the GUI to Metal,Windows or Motif. You can use the one that you like. Metal is the default.



ew of

lf

t, ltip

ally

cted, ode. (object Tree ws

ment ns in

eshing

ProSphere Explorer

Click the ProSphere Explorer button (2nd Button on the toolbar) to display a top-down tree vithe network, as shown below.

The ProSphere Explorer also acts as a launch point for starting all Configuration Tools, SheViews, Object Editor, Telnet and the Add Wizard.

• The Toolbar buttons are, from left to right: Add, Delete, Refresh, View, Telnet, Node, SloLink, Help. With Help, you can move the mouse pointer over a toolbar icon to get the toofor a toolbar icon.

• Use the mouse to click on the tree handles to expand/collapse the network view.

Launching Configuration Tools

Configuration tools can be started from the ProSphere Explorer. Tools or options are generavailable through two mechanisms:

• Toolbars

• Pop-up menus (right-click on an object selected in the Explorer tree display)

Available tools depend on the currently selected object in the tree. Thus, if a Network is seleright-clicking on the object will display popup menu that is different from a popup menu for a NThe main element management tools of Node, Slot and Link are also available on the toolbar selection permitting). The tool windows will be inside the Frame where you see the Explorerby default. You can also make them pop-up by selecting the View->Frames->Popup Windomenu item.

Adding Objects

You can manually add a child object to any parent (e.g., A Network to Root or a Network Eleto Network) by the Add Menu on the pop-up menu of any object. See the subsequent sectiothis chapter on Object Editor for more information on Adding object.

Refreshing a Network / Node

The Refresh feature is enabled when a Network Element or Network object is selected. Refra Network causes Node Polling (see Discovery) to be performed on all contained Network Elements. Refreshing a Network Element causes Node Polling on that object alone.



des, ing up

ame,

Object Editor

Object Editor is used for viewing/controlling object properties. Objects are Root, Network, NoSlots, Links and Connections that you see on the ProSphere Explorer tree. The user can brthe Object Editor window with a right click on any object on the ProSphere Explorer Tree.

Figure 2-1 Object Editor Screen

The Object Editor screen provides three tabs for the following object functions:

• Object Details is a read-only display of basic object properties such as Id, Type, Netc.

• Alarm Polling on a per object basis (See Chapter 3, Element Management .)

• Alarm Masking on a per object basis (See Chapter 3, Element Management .)



g on . The

lies and view is

splay nt;

itical :

Shelf View

The Shelf displays the current configuration of a network element in the system. Right clickina node in the Explorer window allows the user to launch the shelf view for supported nodesShelf View provides a realistic front and rear view of the device and configuration.

A device can consist of a number of elements such as cards, interface modules, power suppswitching fabrics. Each of these elements can be selected and managed. An example shelfshown below.

When the GFM module is installed and the Alarm services are running, the Shelf will also dithe status of the network element and all its sub-elements by means of color on each elemeusually in the elements tabs or grab-handles.

In the example shelf view, shown below, three cards have a Red status, which denotes a cralarm condition is in effect for that element. The colors for the five different status levels are

.

Status Color Alarm Level

GREEN Normal

BLUE Minor Alarm

YELLOW Major Alarm

ORANGE Warning

RED Critical Alarm


Topology Management Add Wizard

LIMs, nt to

op-up

e.

Add WizardThe Add Wizard enables the user to add new objects (Networks, Network Elements, Cards,Connections) into the topology by means of a simple, intuitive Wizard-style tool. You may waadd the objects for simple modeling purposes or for any other reason.

Adding a New Network

1. From ProSphere Explorer Tree View, select the Root, right click on the Root to get the pmenu and select Add Object menu. A window pops up with the following selections:

<otGenericNetwork>

<otDefaultNetwork>

2. Select the otGenericNetwork and then click the Next button.

3. Enter a name for the new network. For example, type NorthEast as a new network nam

4. Click the Finish button. The new network will be displayed at the Explorer Window, asshown below.

5. The Add Wizard window will stay on and you can use the Back button to go back and createanother network or simply close the window by pressing the Cancel button.



get

.

Adding a Network Element (Node)

1. To add a new Network Element, select a Network and then right-click on the Network tothe pop-up menu.

2. Select Add Object menu.

3. Select the Network Element Type. In the example shown below, IMX is the selected type

4. Click the Next button.

5. At the resulting screen, enter information for the new node as shown below:



6. When the node information is completes, click the Finish button to add the new node. Thenew network element will be displayed at the Explorer Window.

For example, the Explorer window shows the new Network Element named Boston created under the new Network named NorthEast .

7. The Add Wizard window will stay on and you can use the Back button to go back and createanother Network Element or simply close the window by pressing the Cancel button.



get

Adding a Card to a Node

1. To add a new Card, select a Network Element and right click on the Network Element tothe pop-up menu.


3. Select the Card Type. In the example below, ACP type is selected.


5. Select the Slot Number for the Card, then click the Finish button to create the Card. In the example below, a new ACP Card added to node Boston.

6. The Add Wizard window will stay on and you can use the Back button to go back and createanother Card, or simply close the window by pressing the Cancel button.

Note After you create a card, you may want to add a LIM to it, as described in the next procedure.



ted

Adding a LIM to a Card

1. To add a new LIM, select a Card and right click on the Card to get the pop-up menu.

2. Select Add Lim menu.

3. Select the LIM Type, then click the Next button. In the example below, DS3-2C LIM is selected).

4. Select the Slot Number for the Card and then click the Finish button to create the Card.

5. Click the Cancel button to close the Window. The window below shows a new LIM creaunder ACP card in Slot 0 of node Boston.



that ate for

Creating Connections

In the example below, a connection will be created from Boston Slot0-Link1 to New York Slot0-Link1 .

1. To add a new Physical or Signalling Connection, first expand the Explorer Tree View so you can see both the source and the destination ports (under LIMs) that you want to crethe Connection..

2. Select a Network (Northeast Network in the example shown) and right click on the Network to get the pop-up menu.


4. Select the Connection Type. In the example below, Physical Connection is selected.




g

ink ID

the

6. Another window pops up with blank Source and Destination Link ID. Double click on theSource Link (Boston Slot0-Link1 ) and then set the Destination Link by double clickinon Destination Link (NewYork Slot0-Link1 ).

Note You can change the Source and Destination by clicking once on the Source Link ID button or Dest Lbutton on the Add Wizard and then double clicking on the appropriate Link at the Explore Window.)

7. Click the Validate button to verify if the Source and Destination are available.

8. Click the Finish button to create the Connection.

9. Follow the same procedure to create Signalling Connection, except that you must enterSource and Destination SAP numbers before hitting the Validate button.


, ments uire nly be

. n on tion

user

llers

Chapter 3: Element Management

Configuration OverviewProSphere Element Manager is a set of GUI-based configuration tools that configure nodesmodules and links in an Xedge switch network. ProSphere can configure all such network elethrough Telnet, through the ProSphere Element Manager, or both. Some configurations reqspecial functions (e.g., block copy and delete) which are not supported via Telnet and can operformed via the Element Manager.

This chapter describes basic Node, Slot and Link configurations for a typical controller cardAvailable configuration options will vary depending on the card type. For detailed informatioconfiguring a specific card, or for a specific feature, refer to Xedge configuration documentafor guidance. Also see Appendix A, Application Tutorials in this document for example configuration procedures for selected applications.

Note Using the Element Manager requires a thorough knowledge of the Xedge switch and configuration parameters. It is highly recommended that you review the Xedge Configuration Guide for your switch(032R400 or 032R401) before starting the ProSphere Element Manager.

Element Manager Tool SetAll Element Manager configuration tools are launched from ProSphere Explorer. When the right clicks on a node, controller or line interface module (LIM), a menu appears with the appropriate configuration screens for that particular module.

General Configuration

• Node Configuration • Slot Configuration • Link Configuration

Slot Controllers

• Xedge Adaptation Controllers: CE, CHFRC, FRC, ETH, SCE, VSM• Xedge Cell Controllers: ECC, ACP, ACS• Xedge MSPX Packet Controllers: PCX, PCE, PCL, ISG2, and other packet contro

Specific Feature Configuration

• APS Configuration • Buffer Management • Call Admission Control• ILMI Setup• ISDN• ISUP• Multi-Tiered Shaping• Numbering Plans• Resource Restrictions• Signaling


Element Management Node Configuration

. Note n.

ressing

. l of

to

et the The

single- quire an d for a etwork e node.

nual ddress.

Node ConfigurationThe Node Configuration window consists of five or more tabs, depending on the type of nodethat the ISUP or ISDN tabs appear only when the Xedge node is loaded with that applicatio

General TabUse the General tab to set the node information for administrative purposes and define addparameters for network connections and routing.

Node InformationName: An administratively assigned name for the node (up to 24 characters, e.g

Curly). This name will be used in the craft interface, AEM explorer, and alAEM configuration windows to identify the node.

Contact: Contact person for this managed node, together with information on howcontact this person. (Up to 24 characters, e.g. John, Extn: 1234)

Location: Identifies the physical location of this node. (e.g. Middlebury)System Time: Date and time set in the switch (dd mon yyyy hh:mm:ss). The user can s

system time on the switch from the Tools->Set System Time menu item. (current time on the manager node is set on the switch).

Note The user cannot set the time if the ACX or the ECC Slot controller is in Slot-0.

Address InformationEach Slot Controller in the Xedge node shall have a unique IP Address. There can be up 16width Slot Controllers in the Xedge6640 or Xedge6645 chassis. Such Slot Controllers will re16 contiguous IP addresses assigned to them. By default, Xedge nodes are configured withinternal mask of 255.255.255.240 (modulo 16). This allows enough addresses to be allocateXedge6640 or Xedge6645 chassis. An Xedge node is considered a small subnet. Assign a naddress to Slot-0 and choose subnet mask to include all of the Slot Controller addresses in th

Note For instructions on changing the default Slot-0 IP address, refer to Xedge Software Configuration Ma(032R400), Chapter 3: Configuring Components, under the paragraphs on Selecting the Switch IP A



. The , the

sign in rt of

with the ation s the

the net) for

its igned ing node

ode d in the mber ID

ending hen the

nning.

IP Address: Slot-0 IP address. This is a read-only item in the AEM Node configurationdefault Slot-0 address is 192.1.1.16. As soon as a new switch is configuredIP address should be changed.

IP Mask: Indicates the setting of the subnet mask depending on the net/subnet dewhich the node is installed. Changing this parameter requires a Warm Stathe node.

Xedge can route calls based on the destination address. This address is used in conjunction routing table to direct the call through the Xedge network. In the case of an SVC, the destinaddress is part of the incoming setup message (on the signaling channel). Xedge recognizefollowing two addressing types:

• ATM Addresses (DCC, E.164, ICD)

• Xedge Node IDs (DTLs)

E164 Address: The convention for assigning addresses in the Xedge Node is to assignE.164 address so that each Slot Controller/Link pair in the network (or subis uniquely identifiable within a shelf, but commonly identifiable as a group routing purposes. For example, assign an AREA CODE followed by an exchange number followed by the slot and link pair. No more than 15 digcan be used for this. As an example, a Slot-0 E.164 address could be assas 120375818110000. This would result in Slot-1, Link-1 of this node havan E.164 address of 120375818110101. A node in the same region as thismay have an E.164 Address assigned to its Slot-0 Controller as 120375818120000.

Node ID: For DTL (Designated Transit List) routing, it is recommended that each nin a network (or subnet) has a unique DTL Node ID. The node ID field usethe Xedge is one byte long. Hence the possible values of node IDs lies inrange between 0 and 255. However, Xedge software restricts the total nuof nodes in a routing domain to 100. The software permits up to 100 nodevalues from within the allowable range of 0-255.

Warm Starting the Node

Use the Tools->Reset Node menu item to warm start the node. This takes 1 to 5 minutes depon the slot controller type in Slot-0. The AEM Node Configuration window has no indication wthe node comes up. To determine if the switch is up and running, read the values back fromswitch. If there are no timeouts, the node is up and ready for configuration.

Note IMPORTANT! This operation takes down all traffic through the node until the node is back up and ru



e LIM ts.)

itch

IM ly e

Physical Tab

This table provides a summary of the hardware installed in the switch, lets the user define thtype for each slot controller in the switch. (This table does not show the details for empty slo

Slot Controller Type:Indicates the type of the slot controller. This is a read-only item. The swautomatically recognizes the slot controller type in a slot.

Slot Controller Status: Gives the status of the slot controller (Active or Boot Mode)

DLIM Type: The type of DLIM at the back of the slot controller. The user must define Ltype for all the slot controllers before any slot or link level configuration. Onthe LIMs that are compatible for the selected slot controller are given in thdrop-down list.

DLIM Status: Indicates if the user defined DLIM is compatible with the slot controller.



n for

s for

Version Tab

All the items in this tab are read-only to show the software and hardware version informatioeach slot controller in the switch.

Hardware Version

The following are the hardware version information assigned during the manufacture proceseach slot controller.

• Serial Number

• Doc Serial Number

• Hardware Version

• Doc Hardware Version

Software Version

The Software Version field gives the version of software used in the slot controller.



ancy

in

ric by

items

ext in Main from

Slot-0 ig.cfg, y

R400)

Redundancy Tab

Redundancy tab will be available only for devices that support switch fabric and slot-0 redundfeatures.

Switch Fabric Redundancy

This shows if a redundant switch fabric is available and indicates the switch fabric currently service (Main / Standby).

If the redundant switch fabric is available, the user can enable/disable the standby switch fabselecting the checkbox.

If the redundant switch fabric is available and enabled, the user can select one of the followingfrom the drop-down list box to change the switch fabric in operation. The options are:

• Auto: Automatically selects the standby switch fabric if main fails.

• Main: Switch to main switch fabric.

• Standby: Switch to standby switch fabric.

Slot-0 Redundancy

Slot-0 redundancy is supported only for ETH and MS/QED slot controllers. There is a status tthis panel to indicate if the Slot-0 standby is available and the slot controller currently in use (/ Standby). If the redundant Slot-0 is available, the user can select one of the following itemsthe drop-down list box to change the Slot-0 in service. The options are:

• Auto: Automatically selects standby slot-0 if main slot-0 fails.

• Main: Switch to main slot-0.

• Standby: Switch to standby slot-0.

When redundancy is available, the config files in the main are not updated in the redundant automatically unless the user selects the auto transfer option. For automatic transfer of confusers.cfg, def.rtb and dtl.bin files from Slot-0 main to Slot-0 standby, check the Automaticalltransfer config files to Standby Slot-0 option.

Note For a detailed discussion on Slot-0 redundancy refer to the Xedge Software Configuration Manual (032under the sections on MS/QED Configuration (Chapter 3) or ETH Configuration (Chapter 8).



le

Static Routes Tab

Static routes are used for setting up permanent paths from one network to another. This tabcontains entries to be added to the IP routing table when the slot controller starts up.

Index: Entry index number.

IP Address: The IP address to be routed.

Gateway: Gateway address for this route.

Metric: The metric for this route. This should be 0 if on the same device or 1 pergateway hop.

Interface Number: This indicates the interface to route matching frames, as follows:

Local Interface (1)SLIP Interface (2)ATM Interface (3)Tunnel Interface (4)


Element Management Slot Configuration

neral

Node n use

. all

to

s , read

vice

Slot ConfigurationThe Slot Configuration window consists of four tabs: General, SNMP Authentication, SVC GeConfiguration and Voice (VSM), described below.

General Tab

The purpose of this tab is to set the slot information for administrative purposes similar to theConfiguration for each slot in the switch. To use the same settings as the Node Configuratiothe Use Node Info button.

Slot Information

Name: An administratively assigned name for the node (up to 24 characters, e.gmadras). This name will be used in the craft interface, AEM explorer, andof AEM configuration windows to identify the node.

Contact: Contact person for this managed node, together with information on howcontact this person. (up to 24 characters, e.g.RR .

Location: Identifies the physical location of this node. (e.g. Middlebury)

Warm Starting the Slot

Use the Tools->Reset Slot menu item to warm start the slot. This will take about 1-5 minutedepending on the slot controller type. In order to determine if the slot is back up and runningthe values back from the switch. If there are no timeouts then the slot is up and ready for configuration.

Note IMPORTANT ! Warm starting a slot 0 device will interrupt all traffic through the node until the slot 0 deis back up and running. Do not warm start a slot 0 device without considering this result.



ication ust

e

elow, ent

s.

ty and s. Then h.

table.

SNMP Authentication Tab

Access to the MIB via SNMP can be restricted to authorized managers via the SNMP authenttable associated with a slot controller. To restrict access to the entire switch, the manager mconfigure authentication table for all slot controllers.

Index: A unique id to identify each row.

IP Address: IP Address of the manager.

Community: SNMP community string (24 characters).

Access: Access permissions (Read Only / Read & Write) for the manager.

Send Traps: If the user checks the checkbox, the switch sends all the traps to the management station. If not the manager does not receive any traps.

Configuring Authenticated Users

Since changes to the SNMP Authentication Table take immediate effect, be sure to follow thprocedures below in the exact sequence as provided.

Note IMPORTANT! The initial manager must enter his own SNMP access information first, as described bbefore adding other managers. Otherwise, Xedge will not authenticate the initial manager’s subsequaccess attempts.

1. Enter your SNMP information and select Edit->Add or click the (+) toolbar icon.

2. Check the entry for accuracy and then select File->Write or click the W or toolbar icon to write the initial manager’s entry to the switch.

3. Enter SNMP information for any additional authorized managers using the same proces

Editing Authentication Entries

Edit an existing entryas you would for any table in the AEM configuration windows., with theunderstanding that the authentication table requires that the Access permissions, CommuniSend Traps values are the same for all rows. Select all the rows and enter the desired valueselect File->Write or click the W or toolbar icon to write the initial manager’s entry to the switc

Deleting an Entry

Select the row or rows the user wants to delete and press the toolbar icon button (X) or the Edit->Delete menu item, then use File->Write to write the changes to the switch.

Note The user cannot delete the entry for the user's manager running AEM unless it is the only entry in the



ts have ast the

arties

ies ries

is

ion

lable

nes

Broadcast AuthenticationThe user can broadcast the authentication table to all the slots in the switch so that all the slothe same table. Use the Tools->Broadcast Authentication (available only in slot-0), to broadcauthentication table to all slots.

SVC Configuration Tab

When configuring for SPVC Multicast, the user must set the Max Pt-Mpt Trees and the Max Pper Tree.

Max Point-Point Connections:Maximum number of point-to-point connections. Range is 0-500 for H-serslot controllers and 0-750 for A-Series slot controllers and 0-4000 for E-Seslot controllers.

Max Point-Multipoint Trees :Maximum number of point-to-multipoint connections. The available range0-25.

Note For an emulated LAN, the user must set a minimum of 2 Pt-Mpt Trees; one for the LES (LAN EmulatServer), and one for the BUS (Broadcast Unknown Server).

Max Parties / Tree: Maximum number of parties in a point-to-multipoint connection. The avairange is 0-500. Setting this parameter requires a warm start.

Note For an H-series Cell Controller, the trees multiplied by leafs product cannot exceed 500 (parties).

Load Route Tables: Selections are: def.rtb, dtl.bin, Both or None

DTL Failure Clear Timer: Applicable only for A & E-Series slot controllers. This timer determiafter how long all previously failed routes are marked as being good to beretried.


Element Management Link Configuration

g and

ossible

nd

g is

Link ConfigurationThe Link Configuration window consists of five tabs: General, Physical, Resources, SignalinManagement, described below.

General Tab

The General tab screen indicates the current status of all the links in the slot controller. The pstates are:

• Up: The Slot Controller and LIM have been installed, the LIM has been selected arecognized, and line coding is passing.

• Down: Indicates an incomplete installation, selection of the wrong LIM, or line codinnot passing.

• Stop: Indicates that the port is disabled.

Physical Tab

The following screen shows an example of a DS3 Physical table configuration.



rt of

tart of

uires

uires

warm

warm

.

.

.

.

.

source

Resources Tab

PVC Resources

VCI Range Start: Sets the start of the VCI range. Default value is 0. Requires a warm staaffected slot controller.

VCI Range End: Sets the end of the VCI range. Default value is 816. Requires a warm saffected slot controller.

VPI Range Start: Sets the start of the VPI range for VC switching. Default value is 0. Reqa warm start of affected slot controller.

VPI Range End: Sets the start of the VPI range for VC switching. Default value is 2. Reqa warm start of affected slot controller.

VP Range Start: Sets the start of the VP switching range. Default value is 5. Requires a start of affected slot controller.

VP Range End: Sets the end of the VP switching range. Default value is 255. Requires astart of affected slot controller.

SVC Resources

VCI Range Start: Identifies the start of the range of SVC VCI values supported on this link

VCI Range End: Identifies the end of the range of SVC VCI values supported on this link

VPI Range Start: Identifies the start of the range of SVC VPI values supported on this link

VPI Range End: Identifies the end of the range of SVC VPI values supported on this link

VP Range Start: Identifies the start of the range of SVC VP values supported on this link

VP Range End: Identifies the end of the range of SVC VP values supported on this link.

Note For E-Series cards, an automatic Reconfigure is performed on the switch after any changes to PVC Retable. On A-Series, the user has to manually reconfigure using the Reconfigure button.



he /VCI (in

e

e that

this

eter

VPI/VCI Hilo: On SVC call establishment, the switch will assign a VPI/VCI value within tallowable range. This parameter enables the user to set the selected VPIvalue on SVC establishment to the high or low side of the VPI/VCI rangeorder to prevent glaring).

If High is selected, the software attempts to use the last VPI/VCI pair in thupper range for an incoming SVC connection.

If Low is selected, the software attempts to use the first VPI/VCI pair in thupper range for an incoming SVC call. The user may select either, but notethe other end of the SAP should be the opposite selection to avoid glare.

Bandwidth Parameters

Assigned Cell Rate: The backward total cell rate configured for SVCs on this link. Note that object is in cells per second (CPS). The default value is: 0

Available Cell Rate:The backward cell rate available for SVCs on this link. Note that this paramvalue is in cells per second (CPS). The default value is: 0

Max SAP Connections: Maximum SVCs this SAP. The default value is: 55

Current SAP Connections: Current SVC count this SAP The default value is: 0



user to

lues.

309

the

e, in

e SAP.

Signaling Tab

SAP Status: This parameter reports the status of the selected SAP and enables the change the SAP parameters. The options are:

On- turns on the SAP or reports that the SAP is on.Off - turns off the SAP or reports that the SAP is off.Reconfig - This option reconfigures the SAP with the current parameter vaReset - This option resets the SAP to the default parameter values.

Auto Sap Off : This option allows a Sap Status to be automatically turned off after T309expiry. Select Yes if a sap (which was on before) is to be turned off after Texpiry, else select No. The default value is: No

Interface: This enables the user to select the Interface type. The options are:

Network - select this option if the SAP is connected to the network side ofconnection. The default value is: Network.User - select this option if the SAP is connected to a user endpoint.

CDVT Size: This parameter enables the user to set the Cell Delay Variation Tolerancmicroseconds. The default value is: 200

Signaling Protocol: This parameter enables the user to set the signaling protocol used by thThe options are:UNI 3.1UNI 4.0IISP 3.1PNNI 1.0

Policing: This parameter enables the user to enable or disable policing.On - Select this option to enable policing (default).Off - Select this option to disable policing.

Signaling VCI: This is the VCI used for signaling messages. The default value is: 5

Signaling VPI: This is the VPI used for signaling messages. The default value is: 0


Element Management Selected Application Tutorials

N).

).

a

n the

ion ples

Management Tab

MOLN VPI: Identifies the VPI that is used for the Management Overlay Network (MOLRequires a warm start of affected slot controller.

MOLN VCI: Identifies the VCI that is used for the Management Overlay Network (MOLNFor more information see MOLN in the Technical Reference Manual

Link Type: This is the type of link (UNI, APEX NNI or Non-ATM link). Currently, the biggest difference is between UNI and APEX NNI. If a link isnative ATM type and connected to another Xedge switch, it should be configured to APEX NNI. By doing so, the management overlay network protocol (MOLN) is run between the switches. If the link is connected to aend-point device, such as an ATM controller card fitted to a workstation, link type should be set to UNI. Type Non-ATM is used for Non-ATM cell based links such as on Adaptation Controllers. Requires a warm start of affected slot controller.

Selected Application Tutorials

Appendix A, Application Tutorials provides examples on how to use many different configuratscreens in a sequence for the following selected applications. Note that the tutorials are samonly; you may need to customize them to suit your network.

• IMA Configuration

• MTS Configuration

• QSIG Configuration

• FRC Configuration

• CHFRC Configuration

• VSM Configuration

• LCE-16 LIM Configuration (for ACP-II Card)


Element Management Selected Application Tutorials


VCs)

ints, or

be have

tion in y.

its in a the list

Service. have reate

Chapter 4: Service Provisioning (SPM)

Service Provisioning OverviewThe Service Provisioning Manager allows the user to create end-to-end circuits (PVCs or SPwith a simple point-and-click on the termination points from a graphical Network Map. This sophisticated tool sets up the circuits in a completely automated fashion between two end-poallows the user to specify manually various parameters for each step.

Creating ServicesA Service is a logical unit for a collection of Circuits (PVCs & SPVCs). SPM allows circuits togrouped into logical units called Services. Circuits cannot be created without a Service. It canany meaningful name that identifies the set of circuits. Type in the Service name and descripthe given fields and select the Provisioning->Add/Modify menu item or press the CTRL-D ke

Using ServicesOnly one user can access a Service at any time to prevent multiple users modifying the circuService at the same time. In order to accomplish this, the user must select the Service fromand press the Lock button to acquire lock on the Service.

When a user acquires a lock on a Service all other users are prevented from accessing that Note that there is no validation to check if the same circuit exists in another Service. You canthe same circuit in multiple Services. It is the responsibility of the administrator/manager to cservices & circuits and delegate responsibility to multiple clients.


Service Provisioning (SPM) Service Provisioning Overview

quire from r port

Importing CircuitsSPM allows the user to import circuits currently setup in all the Xedge switches. You must aca lock on a Service to import the circuits into. Then in the Create Circuit tab, select the Servicethe Drop-down list (Combo box). Then use the Provisioning->Import menu to import PVCs oSPVCs or both from the entire network. Alternatively you can right click on a single node to imcircuits just for that node.

Moving Circuits across Services

After importing the circuits, you may want to organize the circuits into multiple Services. You must acquire a lock on both Services that you want to move the circuits from and the one that you are moving the circuits to.

Select the circuits from the table (from Create Circuit or Manage Circuit tab) and select the Provisioning->Move Circuits menu item. This pops-up a window with all the Services. Select the one that you want to move the circuits to and hit the Move to button.



type of s to be rious

d/

must up ferent

Presets

Presets are the contracts or templates defined with specific parameter values for a specific circuit. The user can also setup Presets to specify bandwidth and quality of service propertieused by the circuits. You can create and store as many Presets as you need for creating vacircuits in your network.

Type in the Preset name and description in the given fields and select the Provisioning->AdModify menu item or press the CTRL-D key.

Creating Circuits

Creating circuits using SPM is very simple using a point-and-click procedure. However you have a thorough understanding of ATM circuits and have a plan of how you are going to setcircuits across an Xedge network before using the tool. You can setup the circuits in many difways and they are explained here in this section.

Creating PVCs

1. Acquire a Lock on a Service that you want to create circuits in.

2. Go to the Create Circuit tab and select that Service.

3. Select the Circuit Type as PVC.



the

Note the

ile-

M

he VCs on

resets

PCI

4. For the time being, select a Preset that you want to apply to this circuit. Leave it set as None . (You can change circuit parameters from the Manage Circuits tab later.)

5. Right click on the node(s) to get the Show Links for pop-up Menu. Then check the Card(slot controller) that you want to create the circuits for. It displays all ports for that card onMap. Repeat this step to show all termination points that you want to use for the circuits.that you may not see the termination points if either the card does not have a LIM or all ports of the card are used as NNI connections.

6. Now you can save the Node/Termination points locations for later use by selecting the F>Save Map menu item.

7. You can manually enter a text in the Description field that describes the circuit, or let SPgenerate an automatic description with source & destination details. (You can change these later from Manage Circuits tab.)

8. Enter the VPI/VCI values. (You can change these later from Manage Circuits tab.)

9. You can create end-to-end PVCs across a network by clicking two termination ports at tends. SPM automatically calculates the shortest path between the nodes and creates Pall intermediate nodes according to contract. To perform this automatic setup:

• hold the Shift-Key and Left-Click with your mouse on the Source Port;

• and hold the Shift-Key and Left-Click with your mouse on the Destination Port.

As an alternative, you can create PVCs on each node with different VPI/VCI values and Pby individually selecting the node, source & destination ports, as follows:

• hold the Shift-Key and Left-Click with your mouse on the Node.

• hold the Shift-Key and Left-Click with your mouse on the Source Port.


Otherwise, you can also manually enter the IP Addresses, Slot, Link numbers and the Vvalues and hit the Add button to add a circuit.



TM and a E164 edure

(slot Map.

ile-

ese

ts at To

Creating SPVCs

In order to create and use SPVCs, you must generate the Routing Tables using ProSphere Rdownload them to the Xedge switches. Also note that the Xedge nodes must be setup with Address. (you can set the Node ID and E164 address in the Node Info tab). Follow the procbelow to create SPVCs :

1. Acquire a Lock on a Service that you want to create circuits in.

2. Go to the Create Circuit tab and select that Service.

3. Select the Circuit Type as SPVC.

4. For the time being, select a Preset that you want to apply to this circuit. Leave it set to None .(You can change circuit parameters from the Manage Circuits tab later.)

5. Right click on the node(s) to get the Show Links for pop-up Menu. Then check the Cardcontroller) that you want to create the circuits for. It displays all ports for that card on the Repeat this step to show all termination points that you want to use for the circuits.

6. Now you can save the Node/Termination points locations for later use by selecting the F>Save Map menu item.

7. You can manually enter a text in the Description field that describes the circuit or let SPMgenerate an automatic description with source & destination details. (You can change thlater from Manage Circuits tab.)

8. Enter the VPI/VCI values.

9. You can create end-to-end SPVCs across a network by just clicking two termination porthe ends. Actual route take by the circuit is determined by the routing table parameters. perform this automatic setup:

• hold the Shift-Key and Left-Click with your mouse on the Source Port.




fore meters.

lues ly the

Managing SPM Circuits

After creating the circuits you can manage the circuits from Manage Circuits tab.

Modifying Circuit Parameters:

You cannot modify a circuit that is currently running in the Switch. You must stop the circuit bemodifying the parameters. You can select 1 or more rows in the table and change any paraAfter changing the parameters, select the Provisioning->Add/Modify to modify the Circuit. Modifying the circuit only modifies the circuit locally in ProSphere. You have to select Provisioning->Setup menu to setup the values in the switch or simply start the circuit with Provisioning->Start menu.

You can also change the VPI/VCI values for a single row by selecting the row, enter new vaand hit the Change button next to VPCI fields. (note that even if you select multiple rows, onfirst row will be modified with new VPCI values)

Applying Presets

You can apply the predefined preset values to circuits managed by SPM. Again you cannot apply presets to circuits that are currently running in the Switch. Select the circuits from the table and select the Provisioning->Presets menu item. It pops up a window showing a list of Presets. Select the Preset you want to apply to the selected circuits and hit the Apply button. You have to select Provisioning->Setup menu to setup the values in the switch.



y in

Setup / Start / Stop / Kill / Remove Circuits

When a circuit is created in SPM, it is not actually setup in the Switch. It is maintained locallthe SPM Server.

Select the circuits from the table and then select:

Provisioning -> Setup: To setup circuits in valid state in the switch.

Provisioning -> Start: To start circuits in running state in the switch.

Provisioning -> Stop: To stop running circuits in the switch.

Provisioning -> Kill: To kill & remove from the switch. (Does not remove the circuit from the SPM Server.)

Provisioning -> Remove: Removes the circuits from SPM Server. (Does not affect the circuits in the switch.)



OT ID.

st

Node Info Screen

The information presented here was obtained during the Discovery process.

• If the Node ID or the E164 Address were modified via telnet or other means after Discovery, you may not see them here.

• If you change the Node ID or the E164 Address here in the above panel you DO Nneed an Auto Discovery again. To make change enter your E164 Address or nodeSelect Provisioning from the toolbar and click Add/Modify.

• If you otherwise change them via telnet or AEM configuration Screen then you muperform Discovery after change.


s have work. clears lly

ected. alarm,

will

ion. ibes

Chapter 5: Alarm Management

OverviewProSphere’s Alarm Manager is responsible for the alarm system in the Xedge network. Alarmonly two states: Active or Clear. When an alarm is active, that alarm condition exists in the netThe alarm is cleared automatically when the problem is rectified, or when the user manually (that is, deletes) the alarm from the screen, whether the problem is rectified or not. A manuacleared alarm will become active again during the next alarm poll unless the problem is corrFor those alarm conditions that do not have defined clear criterion, such as a bad passwordthe alarm will never clear automatically. Such alarms must be cleared manually.

There are two ways to view alarms:

• the Active Alarms display in the GUI window shows all currently active alarms.

• the Historical Alarms Log lists all active and cleared alarms in a .csv file (comma separated values). This file can be imported directly into an MicroSoft Excel-like spreadsheet for further analysis.

Example: If a power supply fails, an alarm will appear in the Active Alarms window and the Historical Alarms Log. When the problem with the power supply is corrected, ProSphere automatically removes the alarm from the Active Alarms window. The Historical Alarms log continue to show the power supply alarm as well as the alarm-cleared message.

The Alarm Manager is used to control Active Alarms, Alarm Configuration and Email NotificatThe Object Editor screen has tabs for Alarm Masking and Alarm Polling. This chapter descrthese alarm functions.


Alarm Management Alarm Configuration Screen

larms ap sent Tab.

Alarm Configuration ScreenThe Alarm Configuration screen provides a list of all Alarms supported by ProSphere. These amay be generated by an SNMP Poll by a ProSphere Alarm Server or because of a SNMP Trby the network device. These are called Active Alarms and will appear in the Active Alarms The Alarm Configuration window provides certain configurable options, listed below.

Figure 5-1 ProSphere Alarm Configuration Screen


Alarm Management Alarm Configuration Screen

r of FM, a

.

se this e ou

ndow. m ever that

tain ser

, e nizes will or

ices. down your

ng the r s, and

Configuration Parameters

Alarm Id: A unique number associated with each alarm for reference purposes.

Severity: A severity associated with each alarm. The severity level affects the colothe alarm reported on the Map, Explorer and Shelf views of cards in the Gand is also shown on the Active Alarm screen for each active alarm frommanaged device.

Description: A text string that gives information about the alarm that is being reported

Mask Alarm: Each alarm can be Masked so the network manager does not report it. Ufield if you already know about a problem and don't want it reported by thNMS. The alarm will be masked for all network devices. For example, if ymask Alarm-2 Watm Start of device was detected , this alarm will never be reported if any node is warm-started in your network. (See Special Considerations below.)

Auto Clear: Each alarm can be cleared as soon as it is reported in the Active alarm wiThis function allows informational alarms to be automatically removed frothe active alarm window so only true device active alarms are shown, howthey are logged to the historical alarms log. This field can be changed somanually removing the informational alarms is required. (See Special Considerations below.)

Pollable: Read-only attribute that shows if you can poll for this particular alarm. CerAlarms may be generated only by Traps and cannot be polled such as ULogin failed or Warm Start detected.

Email Notification Read-only attribute that shows whether an email should be sent to the registered emails upon receiving the alarm event. Options are Yes , No, and Use Global . The default value is Yes .

Special Considerations

• Note the difference between the Mask Alarm and Auto Clear field. If you Mask an AlarmProSphere will ignore that Alarm even if it occurs. This assumes that you know about thproblem and want to ignore it. If the Auto Clear field is set, ProSphere Alarm Server recogit, but you will not see it in the Active Alarms Screen. It will be automatically cleared. You see two entries in the Historical Alarms log: one for Active and one for Clear condition. Fexample, if you do not want to see Alarm-7 User Login Failed in the Active Alarm screen but want the alarm logged to the historical log file, you set the Auto Clear field to Yes for that Alarm.

• From the Alarm Configuration screen, alarms can be masked globally for all network devYou can also mask an Alarm on a per object basis. For example, you can mask the link alarm on a particular Card on a Node, but may want to know about all other link downs innetwork. This is done with Object Editor GUI, described later in this chapter.

Changing Configuration

You can modify the Alarm Configuration Parameters and then select the Fault->Alarm Config->Modify Alarm Config menu item.

Reset to Defaults

After any alarm modifications are made all of the default properties can be restored by selectiFault->Alarm Config->Reset->Default menu item. This allows the network operatoto temporarily change a property of an alarm, such as the reporting of Configuration changethen change it backs when the reporting of the alarm is no longer required.


Alarm Management Active Alarms

arm

e

NMP rm essage

ctive

erity, e

en

ly

TM’s

ity.

Active AlarmsActive Alarms arrive at the NMS by two methods:

• the NMS polls each discovered device for its current active alarms

• each SNMP device in the network sends traps to the NMS

When you choose to have the NMS poll each discovered device, an SNMP get is done for the current MIB information provided by the device. Not every alarm supported by the GFM is pollable, and this information is provided in the Alarm Configuration window. Each pollable alwill report an active alarm condition to the GFM and it will be displayed in the Active Alarm window. If the polled alarm is no longer in the active state. the GFM clears the alarm from thActive Alarm window. Refer to the paragraphs on Alarm Polling later in this chapter to define thetime interval between the poll messages to each device, or to turn polling off.

You can also configure each SNMP device in the network to send traps to the NMS. Each Strap that is received by the NMS is mapped to a supported Alarm ID, and the configured alaaction is executed. Any active alarm reported to the management station in a SNMP Trap mis also displayed in the Active Alarm window. Any Alarm Clear reported to the network management station in a SNMP Trap message is cleared from the active alarm window. All Aand Clear conditions are recorded in a text file in the /var/tmp/ProAlarms directory. This file can be directly imported into a Microsoft Excel like Spread Sheet.


• To sort alarms in the Active Alarms screen, click the Column label of the table (e.g., SevEvent Id, Alarm Id etc.) to sort the data of that column. Click it again to sort the data in threverse order.

• To manually clear alarms, select one or more alarms from the Active Alarm table and thselect the Fault->Active Alarms->Clear Selected menu item. Note that by clearing the alarm, you are simply deleting it from the Active Alarms screen and not realcorrecting the problem. This alarm will appear again in the Active Alarm during the next periodic alarm polling. Refer to the next section on Alarm Masking if you want to mask an Alarm so that it never appears on the Active Alarms window.

• When the Node Timing Module is set to line (i.e., no external clock is connected to the N“IN” connector), a NO NTM BITS LINE INPUT trap will always be sent to ProSphere NMS and the Xedge system event log. This does not adversely affect system functional



table alarms.

ve a ed

Active Alarms Screen

The Active Alarms screen displays a list of currently Active Alarms in the system. When the is empty there are no alarms in the system. The example screen below shows many reportedNote that masked alarms will not appear in the Active Alarms window.

Figure 5-2 ProSphere Active Alarms Screen

Active Alarms Parameters

Event Id: A sequentially numbered identifier of the specific event in the network manager.

Severity: Severity of an Active alarm shows the network operators which alarms hahigher priority than others. Alarms typically are shown as "critical" and in rwhen they require immediate action.

Alarm Id: Maps to the Alarm Id as configured in the alarm configuration window.

Description: Alarm type defined by the user in the alarm configuration window.



d nce of a f-site

le tab:

ed

Email NotificationThe Email Notification feature allows the user to add email addresses to a notification list anassociate each email address with selected alarm events. When thus configured, the occuraparticular alarm event will cause ProSphere to send an automatic email notification to an ofuser. The configuration procedures in this section describe how to:

• configure sender email information• configure global email notification and object-based overrides• define schedule profiles• define notification profiles• select alarm objects for email notification• configure recipient email information

Configure Sender’s Email Information1. From the Alarm Manager, select the Email Configuration tab, then select the Email Profi

Figure 5-3 Email Sender Information

2. Configure the Sender’s email information:

• At the Sender Email field, enter the originating email address.

• At the Sender Username field, enter the name of the originator.

• Create and verify a password, then enter the email server address.

• At the Enable Email Notification field, click to check the box.

• At the Notify Every (minutes) field, enter the interval between email notifications. - Set 0 (default) to send emails shortly after an alarm occurs. - Set n to send emails every n minutes. The emails will contain the alarms that occurr within the n minutes that elapsed since the last set of emails were sent.



uling

s, as

Configure Global Notification

This procedure allows you to configure which alarm conditions would be enabled for email notification to all registered email recipients. Configuring email recipients and defining schedand other notification parameters will be performed in later steps.

3. From the Alarm Manager, select the Alarm Configuration tab to view all active alarm typeshown in the example below.

Figure 5-4 Configuring Global Email Notification

4. For each alarm type listed, the Email Notification column shows where global email notification (to all email addresses) is either enabled (Yes) or disabled (No). By default, global email notification is enabled for all alarm types. To change the state:

• Click to highlight an alarm, or Shift-click to highlight multiple alarms.

• With the desired alarms highlighted, use the menu bar to select: Fault->Alarm Config->Modify Alarm Config

Note You will be able to further control the alarm notification for a particular object in the Object-Based Notification Override procedure.



s, days also nt on

tab.

onth/ate.

y

t.

nt.

ofile ove,

Define Schedule Profiles

This parameter allows you to create a schedule with an ID number, and then assign the dateof the week and times during which alarm notification will be sent. The resulting profile can be configured so that particular days can be blocked out so that no email notificatons are sethose days. You can create multiple schedule profile as necessary.

5. At the Alarm Manager, select the Email Notification tab, then select the Schedule ProfileThe following screen appears:

Figure 5-5 Configuring Schedule Profiles

6. Create a new schedule profile by defining the following parameters:

• At the Schedule ID field, enter a unique identifying number. In this example, enter 5 since four profiles have been previously created.

• With the cursor in the Start Date field, use the pulldown list or calendar to select a myear and a date when email notification will begin. Do the same to select the End D

• With the cursor in the Start Time field, use the pulldown list to select the time of dawhen when email notification will begin. Do the same to select the End Time.

• In the Recur Every fields, click each day of the week email notifications will be sen

• From the Exceptions List, select those days that email notifcations are not to be se

7. When all time, date, day and exception parameters have been selected, click the Add button to add the new schedule profile to the Schedule Profile table.

8. If an existing profile needs to to changed, click to highlight the profile in the table. The prparameters will appear in the entry fields. Make the necessary changes as described abthen click the Modify button to apply the changes.



gning

ile

he

from

Define Notification Profile

If desired, you can exclude all objects in one or more nodes from notification emails by assithe nodes to a notification profile, as described below.

9. At the Alarm Manager, select the Email Notification tab, then select the Notification Proftab. The following screen appears:

Figure 5-6 Defining Notification Profiles

10. In this example, you will modify an existing notification profile, as described below:

• Click to highlight an existing profile in the Notification Profile table, then click the Add/Modify button. The current profile parameters for that profile will appear in tentry fields.

• Select the desired Schedule ID from the pulldown list.

• Click to put a checkbox in the nodes list to indicate which nodes are to be excludedemail notification.

11. When all parameters have been selected, click the Reload Table button to update the Notification Profile table.



ing

he

the

e

Object-Based Notification Override

If desired, you can override global email notification for a particular network object by includor excluding the object from notification emails.

12. From the Explorer view, right-click on a network object, then select the Object Editor.

13. In the Object Editor window, select Alarm Masking to view the subscreen shown below. Observe that the Email Notify column shows the current state of email notification for theselected object.

Figure 5-7 Overriding Notification by Object

14. Use the Email Notify pulldown list to modify email notification by including or excluding tselected object as described below:

• Select Use Global Notification (default value) to include the object in notification emails.

• Select Yes to send email notification about this object even if the global setting in Alarm Configuration menu is set to disable email notification.

• Select No to inhibit mail notification about this object even if the global setting in thAlarm Configuration menu is set to enable email notification.

15. Click the Apply button to display the new setting in the Email Notification column.

Note Be aware that the setting in Email Notification column (Yes , No or Use Global ) will override the Email Enable/Disable setting in the Alarm Config tab.



le tab:

ll

ient

Configure Recipient’s Email Information16. From the Alarm Manager, select the Email Configuration tab, then select the Email Profi

Figure 5-8 Email Recipient Information

17. Configure the Recipient’s email information:

• At the Recipient Email field, enter the destination email address.

• At the Recipient Username field, enter the name of the recipient.

• At the Notification Profile field, click to check the previously defined profiles that widirect the appropriate email notifications to this recipient at the proper times.

• Click to check the Notify this Email box.

18. When all fields are correct for this recipient, click the Add/Modify button to add this recipand the associated profile to the Receiving Email table.

19. Repeat the steps to add more recipients.


Alarm Management Alarm Polling and Masking

s. ult orks

rval he xceeds away.

l. This e the cases e the

Alarm Polling and Masking

Alarm Polling

The GFM system primarily uses SNMP traps to monitor the state of the network and deviceHowever, it is also necessary to poll the network devices periodically to make sure that a facondition on the network was not missed. This section reviews how the alarm polling in GFM wand how to control the polling of network elements.

Alarm polling is time-based. Each object has a designated poll interval time. The default inte(which is configurable) is 15 minutes. The lowest the poll interval can be set is 5 minutes. Tsystem keeps track of when a node was last polled. When the time the node was last polled ethe poll interval, the node is ready to be polled. When this happens, the node is polled right Also note that all nodes are automatically polled immediately after the auto-discovery.

Figure 5-9 Alarm Polling Screen

Use the Alarm Polling tab in the Object Editor window to change Alarm Polling parameters:

• To change the poll interval, enter the desired value, in minutes.

• To turn off polling for the node entirely, deselect the checkbox for Poll Enable.

• Poll Policy has two options: Polled by Parent and Polled by Self . By default, all objects are Polled by Parent except Root, which has Self and a 15 minute Poll Intervaoption is useful if you want to change the Poll Interval for all nodes in your network to ussame Poll Interval. You can just change the Poll Interval of the Root Object. There may bewhere you may want to change the Poll Interval of specific nodes. In those cases, changPoll Policy of those nodes to be Self and set the required Poll Interval.



dow. gnore .

ple,

Alarm Masking

Alarms are generated by polling or by SNMP traps, and are displayed in the Active Alarms winIf the user is aware of a problem on a specific object (Node/Slot/Link), it may be desirable to itraps for that alarm, or not poll for that alarm. As an alternative the user can mask that alarm

Figure 5-10 Alarm Masking Screen

Use the Alarm Masking tab in the Object Editor window to display a list of alarms that are applicable for the selected object. Note that this list is different for different objects. For examnode alarms are different from link alarms.

• Select the alarm you want to mask and check the Checkbox below to mask that Alarm.

• You also mask an alarm for all objects from the Alarm Configuration window.


ork.

tes

e

ored.

t ach

ode

Chapter 6: Routing Manager (RTM)

OverviewRTM generates and manages static routing tables when there are SVCs or SPVCs in the Xedge netwFeatures include:

• Faster route computation

• Supports cost base, hop base and bandwidth base calculationCost base calculation generates lowest path cost list, hop base calculation generalowest hop count path list, bandwidth base calculation generate highest available bandwidth path list.

• Supports node cost.n addition to the link cost, hop count and available bandwidth, user can also choospreferred pass through node by setting the node cost to lower number.

• Supports Link independent route

• Supports parallel link route generation where parallel links for each slot can be ign

• Route verification feature allow user to verify whether generated routes are correcaccording to the topology. This function will traverse from source to destination for eof the generated routes and address the incorrect routes.

• Export/Import cost setting of the topology to excel file for easy manipulation of the nand link cost.

• Allows multiple configurations to be saved.

• Exports route table to excel file

• Creates def.rtb and/or dtl.bin file and saves to local drive or sends to the switch

• Loads new route on the target switch after file transmission

• Displays the def.rtb or dtl.bin file

• Imports and creates switch structure from saved def.rtb and dtl.bin files

• Supports security features which assign access rights to user.


Routing Manager (RTM) Manage Path Cost

ode and

een. two

lt value. lue

to its route

of the

the

w a

the

Manage Path CostThe Manage Path Cost tab allows the user to set the cost and change bandwidth for each nconnection, as described below.

Figure 6-1 Cost Screen

Connection Cost Preferences

To change cost of a node of its connections, click the desired node in the RTM topology scrCurrent information of the selected node will be show in this panel. This panel is divided in tosmaller pieces, the node cost and the connection cost.

• Node Cost panel has the range between 0 to 5000, 0 means no node cost and is the defauHere user can specify higher value for non-preferred nodes. Changing the node cost vadifferent than the default will show a "C" on the node in the topology.

• Connection Cost panel shows all available links of the selected node that are connectedneighbors. The user can set link cost and/or bandwidth of the link, or exclude the link fromgeneration. Link cost range is 0-5000. There is no limit on capacity range.

When capacity is used to generate route, link bandwidth will be used to calculate the costlink using the formula: Cost = MaxRange - (LinkBW * MaxRange) / MaxCapacityWhere MaxRange is 5000, LinkBW is the value in the Capacity field and MaxCapacity ishighest link band width within the network.


End Points Indicates Slot/Link/Sap information

Link Cost Cost of each end point of the connection. Changing the link cost will sho"L" on the link in the topology.

Capacity Bandwidth of the endpoint. Changing the bandwidth value different thandefault will show a "C" on the link in the topology.


Routing Manager (RTM) Manage Path Cost

is ration

ion nds the

ink. ary

ction .

ation. ration

cost.

t to

ology

Actual The actual cost value that is used to perform route calculation. This valuecalculated based on the Route Calculation Preferences in the Route GeneTab.

Avoid going out this pathAn option to include or exclude the endpoint in route calculation. Select toexclude this endpoint will only prevent route from using the outgoing directof the endpoint. To prevent route from using the entire connection, both emust be selected. Selecting this check box will show an "X" on the link in topology.

Par This is read only field which allow user to see information about parallel lA check mark indicates that the link is detected as secondary link. The primlink of parallel links is not checked.

Change Cost This button is used to apply the changes in the node cost field and the connection parameters panel.

Reload Topology This button recreates RTM parameters for the current topology. The funof this button is the same as restarting RTM (restarting ProSphere client)

Cost Setup Preferences

The cost setup preferences show the cost equation that is currently used for link cost calculDifferent equation will be showed per the Route Calculation Preferences in the Route GeneTab.

• The bottom half of this panel shows the default cost for the node cost, hop cost, and link

• Apply button is used to apply the default node cost, default hop cost and default link cosentire topology.

• Import button allows user to import the node cost and connection cost into the current topfrom an excel file.

• Export button allows user to export the node cost and connection cost into excel file.


Routing Manager (RTM) Route Generation Panel

idth

ser can bor.

, all

are

e

Route Generation Panel


• Number of RoutesMaximum number of routes from source to each destination node.

• Route CalculationPreferencesSpecify how route calculation should be done. There are three types:

• Cost Base - perform route calculation based on node cost and link cost

• Hop Base - perform route calculation based on node cost and number of hops

• Port Capacity Base - perform route calculation based on node cost and link bandw

• Use Parallel link technologyWhen there are more than one links on the same slot connected to the same neighbor, uselect this option to generate only one route instead of multiple routes to the same neigh

• Use Link IndependentThis option allows the user to prioritize independent routes. When this option is selectedindependent routes will be found and placed first following by dependent routes. The order of the routes will be:

• Independent route via lowest cost on top

• Independent routes via higher cost go second

• Dependent routes via smaller number of common links and lower cost go third

• Dependent routes via larger number of common links and lower cost go last.

• Common links are the shared link of two or more routes.

• Avoid minor failure. This option does not affect route generation. It is used to set dtl flagwhether to avoid routes that has minor failure. Vpi/Vci unavailable, insufficient bandwidthexamples of minor failures.

• Generate Button generate all routes from one source node to the rest of the nodes in thnetworks. Select a source node then click this button.

• Generate All Button to generate all routes for entire network.


Routing Manager (RTM) Configurations Panel

hop eters ration.

Configurations PanelConfiguration allows the same network to have different configuration and cost. Node cost, cost, link cost, link capacity, parallel links of all nodes in the network, all configurable paramin the Manage Cost Tab, Route Generation Tab, Manage Route Tab are saved in the configu

ID An identifier of the configuration

Name Name of the configuration

Type

Status Saved - configuration is saved in the database or rtm.registryLoaded - configuration is currently loaded to the current networkChanged - configuration has changed.

Installed

Descriptions Detailed description of the configuration.

New Button Create a new configuration

Delete Button Delete a configuration. A configuration in the table must be selected.

Save Button Save a configuration to database or rtm.registry file. A configuration in the table must be selected.

Select Button Apply the selected configuration to the current network.


Routing Manager (RTM) Routes View Panel

ct either of nodes d node.

link f hops

ode

For raph

wn in rk

ma

Routes View Panel

In this Tab, the user can see all of the generated routes. Right-click on the node in the network and seleShow Source or Show Destination. Show Source shows all routes from the selected node to the rest in the network. Show destination shows all routes from the rest of the nodes in the network to the selecteSelect a row in the route table to see the path in the network graph.Index Table indexID Unique number identifying the routeSource Name of the source nodeTarget Name of the destination nodeFlag This field is empty for the non-link independent method.

For link independent route generation the flags are:I - independent path/routeD[x,y] - Dependent path/route where x is the number of common (shared)between the dependent path and independent path and y is the number ofrom source to the first common link.

Order The order of the path/route to be put in the dtl.bin fileCost The total cost (node costs + link costs) from source node to destination nHops The total number of hops from source node to destination nodeRoute Paths The list of segment from source node to destination node.List All Button List all routes generated for the current network.Delete Button Delete a selected row in the route tableVerify Button Start from a selected row in the table going down to the end of the table.

each row, traverse from source node to destination node in the network gaccording to the string in the Route Paths Column.

Clear Path When the user clicks a row in the table or presses Verify, the path is shothe network graph. Click Clear Path to clears those changes in the netwograph.

Export This button export whatever shown in the route table to a text file in a comseparated form which can be viewed in excel.


Routing Manager (RTM) Manage Routes Panel

o the on the ate the

ocal

.

f.rtb

Manage Routes Panel

This tab allows the user to save partial or all generated routes to a file in the local drive, or ttarget switches. The switch structure (node, slot) in the table are normally generated basedcurrent network graph. The user can also load the saved route files in local drive and generswitch structure automatically, based on the saved files. Route files are saved in the <ProSphere installation directory>\data\topology\routes

> Click this column will expand/collapse each node.

Node Name of the nodes

Slot Number identify the slot position in the node

IP Address Node Ip address or slot IP address

File Generated Identify what type of file (bin and/or ascii) was generated for the currentsession. Bin is dtl.bin and ascii is def.rtb file.

File Transferred Identify what type of file (bin and/or ascii) was sent to the target slot or ldrive

Route Initialized Identify what type of file (bin and/or ascii) was initialized (loaded) on thetarget slot controller if the "Initialize route after loading" option is selected

Ascii Explicit RoutesThis column allow user to enter explicit route string to be added to the defile. Contents in this field are not checked by the application.

File Type To DownloadOptions are:Ascii and Binary files - def.rtb and dtl.binAscii - only def.rtb fileBinary - only dtl.bin file

Send/Save To Options are:SwitchesLocal DriveBoth


Routing Manager (RTM) Route Viewer Panel

th" get

n the

ed. The d slot

tes>

oller.

Initialize route after loadingThis option only apply to the "Send/Save To Switch" or Send/Save To Booption. It instructs RTM to load the newly transferred route files on the tarslot controller.

Send Route Button This button perform the task according to the settings in "File Type To Download", "Send/Save To" and "Initialize route after loading"

Import Routes This button allow user to import and create the switch structure based osaved route files.

Route Viewer Panel

This tab allows the user to look at the contents of the route files that were generated and savfile name has the following format which identifies necessary information about the node ancontroller.

Format:

<Node Name>_<Node IP Address>_<Slot Type>_<Slot Number>_<Number of Explicit Rou

The following command buttons are provided:

• View Route:Click this button to view the contents of the selected file.

• Update List:Click this button to reload the list of files.

• Send File:Click this button to send the selected file to the corresponding slot contr


rvice

witch u may

plified lication ility

Appendix A: MSPx Applications

IntroductionProSphere NMS supports GDC’s MSPx packet controllers in the Xedge switch. The MultiSePacket Exchange platform (MSPx) can interconnect remote enterprise sites with emerging Ethernet/IP and legacy services across an MPLS, MPLS, Ethernet, IP, VLAN, MLPS or ATMWAN. This section provides examples on how to use the ProSphere NMS to configure the sfor a variety of MSPx applications. Note that the applications described are samples only; yoneed to customize them to suit your network.

For each example configuration, the hardware arrangements and configuration steps are simto represent the featured application. In an actual network, users can go beyond a typical appand employ a mix of Xedge controllers and LIMs for a vast array of features and interoperabwithin and between Xedge components, nodes or compatible devices in the network.

Typical MSPx Applications

Using Prosphere SPM for Services over Pseudowire• Ethernet over MPLS (EoMPLS)

• Ethernet over DM (EoDM: PCX2 only)

• Ethernet over ATM (EoATM)

• Ethernet over IP (EoIP)

• Ethernet Cross Connect (ExC)

• VLAN over MPLS (VLANoMPLS)

• VLAN over DM (VLANoDM: PCX2 only)

• VLAN over ATM (VLANoATM)

• VLAN over IP (VLANoIP)

• VLAN Cross Connect (VxC)

• ATM over MPLS (ATMoMPLS)

• ATM over DM (ATMoDM)

• ATM over IP (ATMoIP)

• ATM Cross Connect (ATM VC/VP)

• IP over MPLS (IP PWoMPLS)

• IP over DM (IP PWoDM: PCX2 only)

• IP over ATM (IP PWoATM)

032R610-V601 ProSphere NMS A-1Issue 1 Version 6.0.1 User Guide

MSPx Applications Introduction

• IP over IP (IP PWoIP)

• Transit Connections: MPLS to MPLS (Transit LPS)

• Transit Connections: PW to PW (PW Interconnect)

• Transit Connections: IP to IP (IP NP Assisted Routing)

• Circuit Emulation over IP-ETH-MPLS

• Circuit Emulation over IP-ETH-XConn

• Circuit Emulation over IP-VLAN-MPLS

• Circuit Emulation over IP-VLAN-XConn

• Circuit Emulation over MEF

• Circuit Emulation over TDM

• Circuit Emulation over PVC

• Circuit Emulation over SPVC

Using ProSphere Element Manager

• IP Interface on MPLS: IP Interface on MPLS (lsp)

• IP Interface on Ethernet: IP Interface on Ethernet (phe)

• IP Interface on VLAN: IP Interface on VLAN (phe)

• IP Interface on ATM: IP Interface on ATM (ip/ipsnap/moln)

• IP Interface on IP NP Assisted: IP-NP: High Performance Routing

• Bridge interface over MPLS: IP Interface on MPLS (lsp)

• Bridge interface over Ethernet: IP Interface on Ethenet (phe)

• Bridge interface over VLAN: IP Interface on VLAN (phe)

• Bridge interface over ATM: IP Interface on ATM (ethllc/wethvc)

Note For assistance with your network applications, consult your Xedge/ProSphere representative.

A-2 ProSphere NMS 032R610-V601Version 6.0.1 User Guide Issue 1

MSPx Applications Ethernet over MPLS Example

et e PCX ct. In

and ing

er

Ethernet over MPLS ExampleEoMPLS provides a QoS-based, connection oriented transport for Ethernet services. Ethernpackets originating from a PCX Fast Ethernet (FE) port can be transported end-to-end via thGigEthernet (GE) port to provide a level of service defined by the MPLS connection's contrathe example configuration below, the PCX does not employ a LIM. Perform the following configuration sequences in the order given to provision Ethernet services over MPLS.

A typical Ethernet over MPLS application is illustrated in the figure below. The IP addressessystem names shown in the figure are used in the example configuration to assist the learnprocess.

Figure A-1 Example Ethernet over MPLS Application

EoMPLS Configuration Overview

The following section details how to configure each of the following areas for an Ethernet ovMPLS application. Be sure to perform each step in the exact sequence as provided.

Basic Node Configuration

Transport Configuration

Configure Services (SPM)

EthernetService

LSPTunnel

101-200PW1

Label 20FE1GE1

10.1.1.1/30

Transport: MPLSSignaling: RSVPRouting: OSPF

10.1.1.2/30

EthernetService

LSPTunnel

200-101PW1

Label 20 FE1GE1

EthernetEthernet

System Name:Slot IP Address:Loopback IP Address:

N101192.168.101.32/271.1.1.101

System Name:Slot IP Address:Loopback IP Address:

N200192.168.102.32/271.1.1.200

FE1EthernetService

PW1Label 20

FE1EthernetService

PW1Label 20

HEAD

TAIL

TSpec: 20 MbpsCIR=EIR: 20,000Priority: High

MPLSLSP

TUNNEL

TAIL

HEAD



ork con-

n

ing

Basic Node Configuration

1. Launch the ProSphere Explorer window. from the Explorer tree directory, select the netwof interest and double-click the node to show all controllers in the node. In this example figuration, the PCX controller in Node 101 is the element of interest.

2. Select the PCX controller, right-click the highlight and then select the Node Configuratioline.

3. At the Node Configuration window (General tab), identify the node by entering the followparameters as required:

• Name: N101

• Contact: Rodrigo Diaz de Vivar

• Location: Castilla, Espana

4. When complete, click the Add/Edit (+) button to activate the entries in the node.

5. Click the Write (w) button to permanently save the configuration to the node.

6. Close the Node Configuration window.



ht

:

7. At the ProSphere Explorer tree directory, select the PCX controller, right-click the highligand then select the IP Configuration line.

8. At the IP Configuration window (General tab), set the Loopback IP address for the PCX• Loopback Address: 1.1.1.101



11. At the same window, open the IP Interface Config Table tab. Then enable OSPF for the Loopback Address of the node.





OSPF
14. At the same window, open the OSPF Config Table tab. Then configure the Loopback IP Area and Priority, as shown in the example below:
• Address: 1.1.1.101

• Area ID: 0.0.0.0

• RTR Priority: 1



17. Close the IP Configuration window.



-

Transport Configuration

1. At the ProSphere Explorer tree directory, select the PCX controller’s Front-Eth link, rightclick the highlight and then select the Link Configuration line.

2. At the Link Configuration window (Ethernet Configuration tab), set up the MPLS NNI “transport” interface as shown below:

• Admin State: Up

• Max Frame Size: 1600

• App Type: mpls

• IP Address: 10.1.1.1

• IP Masks: 255.255.255.252



5. Close the Link Configuration window.



ht

at

6. At the ProSphere Explorer tree directory, select the PCX controller, right-click the highligand then select the IP Configuration line.

7. At the IP Configuration window (IP Config Table tab), configure OSPF, RSVP and MTU the Transport interface, as shown below:

• OSPF Support: enabled

• RSVP Support: enabled

• MTU: 1500





rs for
10. At the same window, open the OSPF Config Table tab. Then configure OSPF parametethe Transport interface, as shown below:
• Type: broadcast

• Area ID: 0.0.0.0

• RTR Priority: 1



13. Close the IP Configuration window.



-
14. At the ProSphere Explorer tree directory, select the PCX controller’s Front-Eth link, rightclick the highlight and then select the Link Configuration line.
15. At the Link Configuration window (Ethernet Configuration tab), set up the Ethernet UNI “service” interface as shown below:

• Select the Ethernet Interface Index 4302 (mez1/eth1)

• Admin State: Up


• App Type: ignore tag




18. Close the Link Configuration window.



below

as

he of

Configure Services (SPM)

1. At the ProSphere Icon Menu, select the SPM icon (Groups tab).

2. Select the Service Groups icon, then enter the Group Name and Description, as shown in the left image:

• Service name: EoMPLS

• Service Description: Ethernet over MPLS Services

3. When complete, select Provisioning from the ProSphere Text Menu, then click the Add/Modify line to activate the entries in the node. The entry is added to the Services Group shown above in the right image.

4. Select the new EoMPLS Service Group and left-click to get Write Access. The color of tthe Service Group will change accordingly.



ng

5. At the same window, select the Services tab. (Expand your working area by clicking the“expand up” arrow at the upper right corner of the Services pane.)

6. At the expanded Services pane, click the Service Selection button and select the followiparameters for Ethernet over MPLS:

• Service Group: EoMPLS

• Service Set: default-set

• Service Type: Ethernet

• Transport Type: MPLS

• Source Node: N101

• Source Slot: 0

• Destination Node: 102

• Destination Slot: 0



orts.

ther-

ds in

7. When all entries have been made, the following dialog box will appear:

No Ethernet port is found for the selection service or is not imported. Clock in import button next to port box to import.

8. Click OK to proceed as follows:

• At the Source pane, click the Import button to get the available Source Ethernet pWhen the import is complete, click OK when the following dialog box appears:

Ethernet physical import complete.

• At the Destination pane, click the Import button to get the available Destination Enet ports. When the import is complete, click OK the following dialog box appears:

Ethernet physical import complete.

9. At the same window (Source pane), click the TSpec New button to open the Create TSpec screen, shown below.

10. Click Create for both source and destination (if the service is symmetrical), then enter the following TSpec values:

• TSpec: 20

• TSpec name: 20Mbps

• Committed Rate (Kbps): 20000

• Excess Rate (Kbps): 20000

• Priority: High

11. Click the Apply button to apply the Tspec values to the service. Note that the Tspec fielthe Source and Destination panes will now show the entered value (TSpec 20).



e

, as

12. At the same window (Source pane), click the PW New button to open the Create Pseudowirscreen, shown below:

13. Enter the following values to create the Pseudowire for Node 101, slot-0:

• Index: 20

• Name: FE1oMPLS

• TSpec ID: 20

• Inbound label: 20

• Outbound Label: 20

14. Click the Tunnel New button to create a new tunnel. The Create Tunnel screen appearsshown below:

15. Enter the following values:

• Name: 101-102

• Instance: 1

• Signal Protocol: rsvp

• Role: head

• Destination IP: 1.1.1.102

16. Click the Apply button to apply the values.



el bels:

17. The Create PW screen reappears with the new tunnel values now displayed in the TunnName field, as shown below. Enter the following values for Inbound and Outbound PW la

• PW Label: 20

• Destination PW Label: 2 0

18. Click the Apply button to create the Source pseudowire.



, as

19. At the same window (Destination pane), click the PW New button to open the Create Pseudowire screen, shown below:

20. Enter the following values to create the Pseudowire for Node 200, slot-0:

• Index: 20

• Name: FE1oMPLS

• TSpec ID: 20

• Inbound label: 20

• Outbound Label: 20

21. Click the Tunnel New button to create a new tunnel. The Create Tunnel screen appearsshown below:



el bels:

22. Enter the following values:

• Name: 102-101

• Instance: 1

• Signal Protocol: rsvp

• Role: head

• Destination IP: 1.1.1.101

23. Click the Apply button to apply the values.

24. The Create PW screen reappears with the new tunnel values now displayed in the TunnName field, as shown below. Enter the following values for Inbound and Outbound PW la

• PW Label: 20

• Destination PW Label: 2 0

25. Click the Apply button to create the Destination pseudowire. The Service window reappears, as shown below.

26. Click the Add button to proceed.



tus

nd

switch

27. The service is now added and two entries are displayed as “local” in the Operational Stacolumn.

28. At the same window, click the Groups tab. Select the Service Set, then right-click on it aselect the Start Services... line, as shown below:

29. The following dialog box appears:

Do you really want to start all services in this service set?

Note Be aware that the service has been created in ProSphere only and has not been added to the Xedgeyet.



will

30. Click Yes to send all of the Service elements to the switch. If all is OK, the Service Setshow the two entries in Green. It will take 5 - 10 seconds to complete the operation.

31. When the operation is complete, all Service Set element (TSpecs, tunnel configuratiion,pseudowire configuration) are sent to the switch and started, and the Service is sent andstarted.

32. This completes the Ethernet over MPLS configuration.


nce for o

ator

Appendix B: Application Tutorials

Introduction

This section provides examples on how to use many different configuration screens in sequethe following selected applications. Note that the tutorials are samples only; you may need tcustomize them to suit your network.

• IMA Configuration Guidelines

• MTS Configuration Tutorial

• QSIG Configuration

• FRC Configuration

• CHFRC Configuration

• VSM Configuration

• LCE-16 LIM Configuration for ACP-II Card

IMA Configuration Guidelines

In the IMA Configuration window, if there is an existing configuration to be modified, the operMUST configure the card in the following order:

1. Disable the Group using the Group tab.

2. Disable the Link(s) using the Link tab.

3. Associate Link(s) to Group(s) using the Link/Group Mapping tab. Change the current configuration to what is desired

4. Enable the Link(s) using the Link tab.

5. Enable the Group(s) using the Group tab.

To create a new configuration, the operator must configure the card in the following order:

1. Associate Link(s) to Group(s) using the Link/Group Mapping tab.

2. Enable the Link(s) using the Link tab.

3. Enable the Group(s) using the Group tab.

032R610-V601 ProSphere NMS B-1Issue 1 Version 6.0.1 User Guide

Application Tutorials IMA Configuration

tion, etup

NE

"Not

g

rite

IMA Configuration

This tutorial assumes that the IMA LIM is not yet configured. The procedures below will stepthrough the proper configuration of a four groups of four links setup. In this example configurathe IMA being configured is the Near End card; for simplicity, the Far End card used in this shas been configured to a four groups of four links setup. Thus, all of the Status readings for(Near End) and FE (Far End) should be accurate.

1. Click the ECC that is paired with the IMA lim and expand the card to view the LIM.

2. Highlight the LIM (E1-16), right click then select IMA Configuration . This will open the IMA Configuration window.

IMA Configuration Link/Group Mapping Tab

1. Select the Link/Group Mapping tab and verify that the AEM lists all 16 links and they are Assigned”.

2. Perform a Block Assign by highlighting link 0, pressing the shift key and then highlightinlink 3. Links 0 through 3 should now be highlighted.

3. Using the Group Index button, select Group 1, click the Edit button and then click the Wbutton.

• Verify that the Block highlight of links 0 thru 3 performs correctly.

• Verify all highlighted links change to edited .

• Verify that the Edit status returns to None .

• Verify that Links 0 through 3 are Associated with Group 1.

B-2 ProSphere NMS 032R610-V601Version 6.0.1 User Guide Issue 1


g

rite

g

rite

ng

rite





• Verify that the changes were written to the IMA (via craft port).


• Verify that Links 4 through 7 are associated with Group 2.





• Verify that the changes were written to the IMA(via craft port).


• Verify that links 8 thru 11 are associated with Group 3.

8. Perform a Block Assign by highlighting link 12, pressing the shift key and then highlightilink 15. Links 12 through 15 should now be highlighted.




• Verify that the changes were written to the IMA(via craft port).


• Verify that Links 12 thru 15 are associated with Group 4.

6. Click the Read button to check of Link/Group Mapping tab changes made so far.

• Verify that the read is performed

• Verify that all links are associated with their proper Groups.

• Via the craft port verify that all the links properly report their Groups.



IMA Configuration Link Tab

1. Select the Link tab.

• Verify links 0 thru 15 are present.

• Verify the edit status for all links is None .

• Verify that the "rowStatus" for all links is Not in Service .

2. Block select links 0 thru 3. Using the Row Status button, select Active , click the Edit button and then click the Write button.

• Verify that links 0 thru 3 become highlighted.

• Verify the Edit Status changes to Edited .

• Verify that upon the write the Edit Status changes to None .











5. Click the Read button to check the Link configuration changes made.

• Verify the Edit Status for all links is None .

• Verify the rowStatus for all links is Active .

• Verify the "neTxState" and "neRxState" report Unusable Inhibited for all links.

• Verify the "feTxState" and "feRxState" report Usable for all links.

• Verify the "neRxFailureStatus" reports Blocked .

• Verify the "feRxFailureStatus" reports No Failure for all links.

IMA Configuration Group Tab

1. At the IMA Configuration screen, select the Group tab.

2. Verify the following:

• Verify groups 1 through 4 are present.

• Verify the Edit Status reports None .

• Verify the Group Status for all of the groups reports Not in Service .

• Verify the NE State reports Not Configured .



f the

oll-

ps.

ling.

sec-

3. Highlight Group 1. Using the Group Status button, change the status of Group 1 to Active , select the Edit tab and then the Write tab.

• Verify the ability to highlight Group 1.


• Verify upon the write that the Edit Status changes to None .

• Verify that the Group Status of Group 1 changes to Active .

• Verify that after a brief period of time the "NE State" and "FE State" change to Op-erational for Group 1.

4. Block highlight Groups 2 through 4. Using the Group Status button, change the status oGroups to Active , select the Edit tab and then the Write tab.

• Verify the ability to highlight Groups.

• Verify the Edit Status changes to Edited for Groups 2 through 4.

• Verify upon the write that the Edit Status for Groups 2 through 4 changes to None .

• Verify that the Group Status of for Groups 2 through 4 changes to Active .

• Verify that after a brief period of time the "NE State" and "FE State" change to Op-erational for Groups 2 through 4.

• Via the craft port, verify that links 1 through 4 are Active .

IMA Configuration Verification

1. In the IMA Group tab press the Read button. Then select "View", "Options" and Enable Ping.

• Verify that the Edit Status for all Groups is Non e.

• Verify that the Group Status for all Groups is Active .

• Verify the "NE State" & "FE State" report Operational for all Groups.

• Verify that the "Failure Status" for all Groups is No Failure .

• Verify that the "Running Time" counters are incrementing for all Groups.

• Verify that the "Unavailable Time (secs)" counters are NOT counting for all Grou

2. In the IMA Link tab press the Read button. Then select "View", "Options" and Enable Pol

• Verify that the Edit Status for all Links is None .

• Verify that the "rowStatus" for all Links is Active .

• Verify the "neTxState", "neRxState", " feTxState" and "feRxState" report Active for all Links.

• Verify the "neRxFailureStatus" and "feRxFailureStatus" reports No Failure for all Links.

• Verify that the Error counters ( errored seconds, unavailable seconds, unusable onds) for the NE and FE are NOT incrementing.


Application Tutorials MTS Configuration Tutorial

e Node

e

ow.

up

MTS Configuration Tutorial

Node Configuration

1. Select the Xedge node that you are configuring on the ProSphere Explorer and open thConfiguration window.

2. In the Physical Tab, since E-series auto-configures the OC-3 LIM, verify that it depicts thcorrect one.

Slot Configuration

1. Select the ECC card on the explorer, right click and bring up the Slot Configuration wind

2. Set the slot name, contact, and location information.

Link Configuration

1. From the Slot configuration window, click on the Link Config Icon on the toolbar to bringthe Link Configuration Window.

2. Go to the Physical Tab and change the following:

• Enable Link : Yes (for each desired link)

• Scramble Cell Payload : Desired

• Add Coset Polynomial : Desired

• Overhead Type : Desired

• Clock Source : Desired

• Fill unused cells with : Desired

• Managed VP Service



e

Configure VPC Termination

1. From the ProSphere Explorer window, select the E-series LIM, right click and bring up thManaged VP Service. This opens the MTS Configuration window.

2. Go to the VPC Termination tab.

3. Do the following setups:

• Select Enable MTS: Yes.

• Select Add/Edit button to modify.

• Write modification to the switch.

4. Select the Slot Config icon on the toolbar to bring up the Slot Configuration window.

5. Go to the Tools pull down menu and select Reset Slot . (Note that to enable MTS, the ECC card must be warm started.)

6. Once the ECC has completed initialization, in the MTS Configuration window, VPC Termination tab, select Read from Switch .

7. Verify that MTS Enabled? changes to Yes .



Configure VPC Endpoints

1. At the MTS Configuration window, go to the VPC Endpoint tab.

2. Do the follwing setups:

• Link No : 0 (Link 0 only)

• VPI : Desired (within range)

• PCR(cps) : Desired (44cps minimum)

• CDVT (usec) : Desired

• Overbooking Factor : Desired (default = 100)

• Max UBR Connections : Desired (default = 1024)

• VPH Max Q Size : Desired

• Peak Rate Limit : Desired

• Type : VPC End Point

• UBR Bandwidth Reserved : Desired

• Disable VC Policing : Desired (default = Yes)

3. Verify Operational State goes to Active after reading back changes.



nt ble the

ment

then

Configure VP Queuing

1. At the MTS Configuration window, go to the VPC Termination tab.

2. Select Enable MTS: No

3. Verify that MTS Enabled? = "No"

4. Go to the VPC Endpoint tab and configure a VPC End Point by changing the following:

• Link No : 0 or 1








• Type : VPC End Point



5. Configure VP Queues by changing the following for each:

• Link No : 0 or 1








• Type : VP Queue (desired)



6. Verify that Operational State goes to Active after reading back changes.


When creating a VPC Endpoint for either MTS or VP Queue with VPI = 0 all the ManagemeChannels of the associated link must be disabled first, create the VPC Endpoint and then enarequired Management Channels.

By disabling the Management Channel, you can break the connection between the ManageStation and the node. So you must configure this specific case via the craft interface.

Note If Enable MTS is set to Yes already, you MUST remove all MTS endpoints before disabling MTS andfollow the above procedure to Reset the Slot Controller.


Application Tutorials QSIG Configuration

e Node

ow.

up

Off.

e the

g.)

er

he

d in

QSIG Configuration

VSM Card for DS1 (DS1-2C/4C) or E1 LIM (E1-2C/4C)

Node Configuration


2. Setup the appropriate LIM type for the VSM Card in Physical Tab

Slot Configuration

1. Select the VSM card on the explorer, right click and bring up the Slot Configuration Wind

2. Go to the SVC Config tab and change the Max Point-Point Connection to 120.

Link Configuration

1. From the Slot configuration window, click on the Link Config Icon on the toolbar to bringthe Link Configuration Window.

2. Go to the Resources Tab and change the Max SAP Connections to 120 for the SAPs

3. Go to the Signalling Tab and change the Signalling Protocol to IISP3.1 and turn Policing

4. From the Tools menu on the Signalling tab, open the Signalling Type window and changLink Type to ISDN.

5. Go to the Physical Tab and change the Tx Clock t o Link 0 (or whatever link you are usin

6. Select the E1 Framer to CRC MFRM or Basic.

7. Enable the Links on the Physical tab.

SCC Configuration

1. Open the SCC configuration from right click popup menu on the VSM card in the ExplorTree.

2. Make sure the Baud Rate is set to 64K and the Timeslot is set to TS16

Layer 3 Configuration

1. Open the ISDN Layer 3 Configuration from right click popup menu on the VSM card in tExplorer Tree.

2. Go to the Q931 SAPs tab and activate only the SAPs you are planning to use.

IWF Configuration

1. Open the ISDN IWF Configuration from right click popup menu on the VSM card in the Explorer Tree.

2. In the Route Digits tab, configure how many digits of the Called Address will be examinedetermining routing in the ATM Networks.


Application Tutorials FRC Configuration

e Node

ow.

up

FRC Configuration

FRC Card for DS1 (DS1-2C) or E1 LIM (E1-2C)

Node Configuration


2. Setup the appropriate LIM type for the CHFRC Card in Physical Tab

Slot Configuration

1. Select the FRC card on the explorer, right click and bring up the Slot Configuration Wind

2. Set the slot name, contact, location information.

Link Configuration

1. From the Slot configuration window, click on the Link Config Icon on the toolbar to bringthe Link Configuration Window. Go to the Physical Tab.

2. Change the following:

• DS1 LIM (Default Settings)Tx Line Length: DesiredExtract Frame Bits: YesLine Coding: B8ZS or AMIDS1 Framer: SF or ESF 4KTx Clock: Desired

• E1 LIM (Default settings)E1 Framer: CRC MFrm OR BasicTS16 Payload : NoInterface Type : Unbalanced 75 OR Balanced 120Tx Clock : DesiredExtract Frame Bits : Yes


Application Tutorials FRC Configuration

ow.

h.

priate

FRC Configuration (assuming Frame Relay Links)

1. Select the FRC card on the explorer, right click and bring up the FRC Configuration WindGo to Link Config tab.

2. Change appropriate fields (i.e. Service Type). DO NOT CHANGE ADMIN STATE yet.

3. Write changes to the switch.

4. Go to Frame Relay Config Tab, change appropriate fields and write changes to the switc

5. Go to Link Config tab, change appropriate Link Admin Status to Active . This activates the links and writes the change to the switch.

6. The Status windows at this point should be re-read if desired.

7. Close the FRC Configuration window.

FRC Virtual Circuits

1. In the Frame Relay VC Config tab, add appropriate rows to the table and change approfields such as:

• Link Number

• DLCI

• ATM VCI

2. DO NOT change Admin State to Active .

3. Write modified rows to the switch.

4. Change Admin State to Active and write to the switch.

5. The Status windows at this point should be re-read if desired.


Application Tutorials CHFRC Configuration

e Node

in-

up

CHFRC Configuration

CHFRC Card for DS1 (DS1-2C/4C) or E1 LIM (E1-2C/4C)

Node Configuration1. Select the Xedge node that you are configuring on the ProSphere Explorer and open th

Configuration window.

2. Setup the appropriate LIM type for the CHFRC Card in Physical Tab.

Slot Configuration1. Select the CHFRC card on the Explorer, right click and bring up the Slot Configuration W

dow.


Link Configuration

1. From the Slot configuration window, click on the Link Config icon on the toolbar to bring the Link Configuration Window. Go to the Physical tab.

2. Change the following as required:

• DS1 LIMTx Line Length : DesiredExtract Frame Bits : NoLine Coding : B8ZS or AMIDS1 Framer : SF or ESF 4KTx Clock : Desired

• E1 LIME1 Framer : CRC MFrm OR BasicTS16 Payload : Yes OR NoInterface Type : Unbalanced 75 OR Balanced 120Tx Clock : DesiredExtract Frame Bits : No



n

h.

ks

ivate

CHFRC Configuration (assuming Frame Relay Links)

1. Select the CHFRC card on the explorer, right click and bring up the CHFRC ConfiguratioWindow.

2. Go to Timeslot Assignment tab and Add desired rows and write to switch.

3. Go to Channel Config tab and do the following:

• Perform a Read.

• Change appropriate fields.

• DO NOT change ADMIN STATE yet.

• Write changes to the switch.

4. Go to Frame Relay Config Tab, change appropriate fields and write changes to the switc

5. Go to Link Enable tab, change appropriate Link Admin Status to Active to activate the linand write the change to the switch.

6. Go to Channel Config tab, change Channel Admin State to Active on all channels to actthe channels and write the change to the switch.



7. Status windows at this point should be re-read if desired.

8. Close the CHFRC Configuration window.



n

CHFRC Virtual Circuits

1. Select the CHFRC card on the explorer, right click and bring up the CHFRC ConfiguratioWindow.

2. Go to Frame Relay VC Config tab.

3. Add appropriate rows to the table and change appropriate fields such as:

• Link Number

• DLCI

• ATM VCI

4. Do NOT change Admin State to Active.

5. Write modified rows to the switch.

6. Change Admin State to Active and write to the switch.

7. Status windows at this point should be re-read if desired.


Application Tutorials VSM Configuration

e Node

ow.

the

VSM Configuration

VSM Card for DS1 or E1 LIM Types

Node Configuration


2. Setup the appropriate LIM type for the VSM card in the Physical tab.

Slot Configuration

1. Select the VSM card on the Explorer, right click and bring up the Slot Configuration wind

2. In the General tab, set the slot name, contact and location information.

3. Select the Edit/Add icon on the toolbar and then write the information to the switch usingWrite icon on the toolbar.

4. Select the Voice tab.

5. Enter desired values for the following:

• Detect End of Fax/Modem :Yes or No

• Voice Activity Detection Level (VAD) :High, Med, or Low

• Comfort Noise Generation Level (CNG) :Medium, Low, Off



up

nch

g the

Link Configuration

1. From the Slot Configuration window, click on the Link Config Icon on the toolbar to bringthe Link Configuration window.

2. Go to the Physical tab and change the following:

• DS1 LIMTx Line Length :DesiredExtract Frame Bits :NOLine Coding :B8ZS or AMIDS1 Framer :SF or ESF 4KTx Clock :DesiredEnable Link :Yes or No

• E1 LIME1 Framer :CRC MFrm or BasicTS16 Payload :Yes or NoInterface Type :Unbalanced 75 or Balanced 120Tx Clock :DesiredExtract Frame Bits :NOEnable Link :Yes or No

Signaling Configuration

From the Link Configuration window, select the Signalling tab, open the Tools menu and lauthe Signaling Type window

Select the Signalling Type tab.

3. Modify the Signalling Type for each link: None or CAS or ISDN. (ISDN requires special switch software). Note that ISUP and VPNA are not supported at this time

4. Select the Edit/Add icon on the toolbar, and then write the information to the switch usinWrite icon on the toolbar.



ura-

lbar

eters g on

Bundle Configuration

1. Select the VSM card on the Explorer, right click and bring up the Bundle/Timeslot Configtion window.

2. Although a Read from the VSM is done automatically, selecting the Read icon in the toowill upload the latest information from the VSM. Use this to verify changes, check statusinformation configured on the VSM and cancel changes made in error. An Undo functionunder the Edit menu can also be used to cancel changes made in error.

3. Modify the bundle parameters as desired, given the following guidelines:

• Bundle Number :1 to 127

• VPI :usually 1 (within specified range)

• Send Traps :Yes or No

• Max Timeslots :1 to 124 (depending on configuration requirements)

• AAL Type : AAL1 or AAL2

• Advanced items (Defaults should be used in most configurations)

• Admin Status :-- Reconfigure for activation of the bundle when written to the VSM.-- Down (writes bundle parameters, leaves bundle in "down" state)-- Up (read only status after Reconfig only, not to be written to VSM)

4. After changes are completed, choose the Edit/Add icon in the toolbar to enter the paraminto a bundle row entry. Note that parameters that do not apply are grayed-out, dependinthe choice of AAL Type.

5. When all entries are in the table, write them to the VSM via the Write icon in the toolbar.(See Advanced Methods - Bundles below for additional methods.)



ndle n

dle,

add re to sen, onfig"

e form tries

on in

n the ll of re Edit ear dit .

n

Advanced Methods - Bundles

The Bundle configuration feature of the AEM provides the ability to add, delete, and copy buconfiguration information into or out of the Bundle Configuration table on the VSM. Users capeform the following:

• Copy the information from a single bundle to form multiple new bundles

• Delete multiple bundles by block selection

• Modify the contents of multiple bundles by block selection

Copying Bundles

• After a bundle is created or read in from an existing VSM configuration, highlight the bunpull down the Edit menu and select Copy. This opens the Copy function dialog box.

• Enter how many bundles to create and the starting bundle number. The AEM will thennew bundles in sequential order from the starting bundle number. If the new bundles abe immediately started after writing them to the switch, before the copy function is chobe sure to change the selected bundle's Admin Status to "reconfig". This is so the "recstatus is written to all of the new bundle entries.

• If it is undesirable to "reconfig" the original bundle, before writing the new bundles to thVSM, change the original bundle's Admin Status back to "Up". Another method is to perthe Admin Status change after the copy function is complete by block selecting the enand changing to "reconfig" (see the Modifying Multiple Bundles sub-section below).

• Select the Write Icon in the toolbar to write the new bundles to the VSM.

Deleting Bundles:

Bundles can be deleted one at a time, multiple, or all that appear in the table.

• To delete a single bundle, highlight the bundle to be removed and select the Delete Icthe toolbar. Then select the Write Icon in the toolbar to write the change to the VSM.

• To delete multiple consecutive bundles, highlight the first bundle in the series, hold dow"shift" key and select the last bundle in the series. This will highlight the first, last and athe bundles in between. Select the Delete Icon in the toolbar. If the bundles selected weStatus "New" (meaning they were not written to or read from the VSM), they will disappfrom the table automatically. If they were bundles read from the VSM, they will go to EStatus "Deleted". Select the Write Icon in the toolbar to write the changes to the VSM

Note IMPORTANT! Be careful to only modify multiple bundles that are "like" bundles. If certain informatiodiffers between sets of bundles, one group of settings will overwrite the others. See Modifying Existing Bundles sub-section below for details.



d is will g a

New" able dles must

forming

hoose Note efore

ed in the Icon

ts tab. ows.

ialog ve

first e to

• To delete multiple non-consecutive bundles, highlight the first bundle in the series, holdown the "control" key and select each of the other bundles desired, one at a time. Thhighlight only those bundles selected, allowing you to pick out particular bundles amonlong list. Select the Delete Icon in the toolbar. If the bundles selected were Edit Status "(meaning they were not written to or read from the VSM), they will disappear from the tautomatically. This change does not need to be written to the switch. If any of the bunwere read from the VSM, they will go to Edit Status "Deleted". Deleted status changesbe written to the VSM by selecting the Write Icon in the toolbar.

Modifying Existing Bundles

On occasion, certain parameters must be changed on single or multiple bundles such as pera "reconfig". This can be accomplished using the AEM as follows:

• For a single bundle, highlight an exiting bundle, change the desired parameters, and cthe "Edit/Add" Icon on the toolbar. Use the Write Icon to write the change to the switch. that any change to take effect will require the Admin Status to be altered to "Reconfig" bthe Edit/Add command.

• For altering multiple bundles, perform the blocking function in the same way as describthe Deleting Bundles sub-section above, modify the necessary parameters (including Admin Status "reconfig" for changes to take effect immediately) and select the Edit/Addin the toolbar. Then select the Write Icon to write the changes to the VSM.

Bundle Statistics

The bundle statistics dialog box can be invoked by double-clicking on the desired bundle in iItems in the dialog box are polled so care should be taken not to open too many status windOnly items relevant to the given bundle's AAL type are displayed.

Note When a bundle has been marked to delete, if there are any associated timeslots to that bundle, a dbox will appear. The dialog box will allow you to either delete the associated timeslots as well or mothem to an existing bundle.

Note IMPORTANT! If unlike bundles are blocked together, all bundles will take on the parameters of the selected bundle in the series, thus causing undesired changes. Therefore, it is of utmost importanchighlight only those bundles with like characteristics when block modifying.



thin the d on

it pull

the

tion ar.

ar,

Configuring Timeslots

• Select the VSM card on the Explorer, right click and bring up the Bundle / Timeslot Configuration window

• Although a Read from the VSM is automatically done as with all of the other windows withe AEM, selecting the Read Icon in the toolbar will upload the latest information from VSM. You can use this to verify your changes, check the status of information configurethe VSM and cancel changes that were made in error. An Undo function under the Eddown menu was also added for the purpose of canceling changes made in error.

• Select the Timeslots tab.

• Modify the timeslot parameters as desired given the following guidelines:

Link Number :0 to 3

Timeslot No. :1 to 24 (DS1) OR 1 to 31 (E1)

Channel ID :8 to 255

Bundle No. :existing bundle or enter new number between 1 and 127

AAL Type :AAL1 or AAL2 (if existing bundle, will auto match bundle)

Detect Idle Channel :Yes or No

Echo Canceling :Enable, Disable, Auto Disable

Silence Removal :Enable, Disable, Auto Disable

Bypass Handling :Disable, Auto Disable 64K, Auto Disable 32K (for fax bypass)

Signal Type :Desired

Comp Algorithm :Desired

Companding Type :Desired (for 64K PCM - Auto for most configurations)

TLP Attenuation :0 to 9 (0 represents unity gain)

Conditioning :Desired

Fax Relay :Disable, Enable (requires particular DSP hardware)

Admin Status :Reconfig (activation of the timeslot when written to the VSM)

:Down (writes parameters, leaves timeslot in "down" state)

:Up (status after Reconfig only, not to be written to VSM)

• After the parameters are completed, choose the "Edit/Add" Icon in the toolbar to enterparameters into a timeslot row entry.

• After all entries are entered into the table (see the Advanced Methods - Timeslots secbelow), write the Edit Status "New" entries to the VSM using the Write Icon in the toolb

• Entries can also be selected and edited by highlighting an entry (see Advanced Methods - Timeslots: section below), modifying it's contents, choosing the Add/Edit Icon in the toolband writing the now Edit Status "Edited" entry to the VSM using the Write Icon.

Note Certain parameters do not apply and are "grayed" out depending on the choice of AAL Type.



eslot can

box.

nnel

ell. D

AEM ber

re the ". This

the

g the low)

on in

own and ected will will the

old is will

n

Advanced Methods - Timeslots:

The timeslot configuration feature of the AEM provides the ability to add, delete, and copy timconfiguration information into (or out of) the Timeslot Configuration table on the VSM. Usersperform the following:

• Copy the information from a single timeslot to form multiple new timeslots

• Delete multiple timeslots by block selection

• Modify the contents of multiple timeslots by block selection

Copying Timeslots

• After a timeslot is created (or read in from an existing VSM configuration) highlight thetimeslot, pull down the Edit menu and select Copy. This opens the Copy function dialog

• Enter how many timeslots to create, the starting timeslot number, and the starting ChaID. The AEM will then add new timeslots in sequential order from the starting timeslot number. For AAL2 timeslots, the channel ID number will automatically increment as wFor AAL1 timeslots, the Channel ID will be identical for each created timeslot, as the Iparameter is not used in AAL1 configurations.

Note: When copying timeslots, it is necessary to copy only up to one link worth at a time. The will not accept a number beyond 32 in the copy function. It is difficult to increment the link numdue to various configuration models.

Note: if the new timeslots are to be immediately started after writing them to the switch, befocopy function is chosen, be sure to change the selected timeslot's Admin Status to "reconfigis so the "reconfig" status is written to all of the new timeslot entries.

• If it is undesirable to "reconfig" the original timeslot, before writing the new timeslots toVSM, change the original timeslot's Admin Status back to "Up". Another method is to perform the Admin Status change after the copy function is complete by block selectinentries and changing to "reconfig" (see the Modifying Multiple Timeslots sub-section be

• Select the Write Icon in the toolbar to write the new timeslots to the VSM.

Deleting Timeslots

Timeslots can be deleted one at a time, multiple, or all that appear in the table.

• To delete a single timeslot, highlight the timeslot to be removed and select the Delete Icthe toolbar. Then select the Write Icon in the toolbar to write the change to the VSM.

• To delete multiple consecutive timeslots, highlight the first timeslot in the series, hold dthe "shift" key and select the last timeslot in the series. This will highlight the first, last all of the timeslots in between. Select the Delete Icon in the toolbar. If the timeslots selwere Edit Status "New" (meaning they were not written to or read from the VSM), theydisappear from the table automatically. If they were timeslots read from the VSM, theygo to Edit Status "Deleted". Select the Write Icon in the toolbar to write the changes toVSM.

• To delete multiple non-consecutive timeslots, highlight the first timeslot in the series, hdown the "control" key and select each of the other timeslots desired, one at a time. Th

Note IMPORTANT! Be careful to only modify multiple timeslots that are "like" bundles. If certain informatiodiffers between sets of timeslots, one group of settings will overwrite the others. See Modifying Existing Timeslots below for details.



ong tus m f the

forming the

se the any st be

n the in olbar.

ers of tmost

esired ed

in its ndows.

highlight only those timeslots selected, allowing you to pick out particular timeslots ama long list. Select the Delete Icon in the toolbar. If the timeslots selected were Edit Sta"New" (meaning they were not written to or read from the VSM), they will disappear frothe table automatically. This change does not need to be written to the switch. If any otimeslots were read from the VSM, they will go to Edit Status "Deleted". Deleted statuschanges must be written to the VSM by selecting the Write Icon in the toolbar.

Modifying Existing Timeslots

On occasion, certain parameters must be changed on single or multiple timeslots such as pera "reconfig" or changing echo cancel support, for example. This can be accomplished usingAEM as follows:

For a single timeslot, highlight an exiting timeslot, change the desired parameters, and choo"Edit/Add" Icon on the toolbar. Use the Write Icon to write the change to the VSM. Note thatchange will require the Admin Status to be altered to "Reconfig" to take effect on the VSM mudone before the Edit/Add command.

For altering multiple timeslots, perform the blocking function in the same way as described iDeleting Timeslots sub-section above, modify the necessary parameters (including the AdmStatus "reconfig" for changes to take effect immediately) and select the Edit/Add Icon in the toThen select the Write Icon to write the changes to the VSM.

Important Note: if unlike timeslots are blocked together, all timeslots will assume the parametthe first selected timeslot in the series, thus causing undesired changes. Therefore, it is of uimportance to highlight only those timeslots with like characteristics when block modifying.

Moving Timeslots

Timeslots can be moved from one bundle to another, by modifying the bundle number of the dtimeslots (and the Admin Status to "reconfig") and writing the change to the VSM as describabove.

Timeslot Statistics

The timeslot statistics dialog box can be invoked by double-clicking on the desired timeslot tab. Items in the dialog box are polled so care should be taken not to open too many status wiOnly items relevant to the given timeslot’s AAL type are displayed.


Application Tutorials LCE-16 LIM Configuration for ACP-II Card

sing

vides ries to al and

ata

.35.

CD).

ols for g and oss-

e Node

ow.

LCE-16 LIM Configuration for ACP-II CardThe LCE-16 LIM requires an ACP Version 2 (ACP2) slot controller. To determine if you are uACP2 controllers, please refer to the Xedge Configuration Manual.

LCE-16 Configuration Overview

The configuration steps and parameters in each window are briefly described below. AEM provalidation rules for each parameter and will prompt with warning messages when the user tconfigure something incorrectly. However, the user must read the Xedge Configuration Manuhave a thorough understanding of the LCE-16 LIM configuration details before using AEM.

The LCE-16 LIM provides circuit emulation for legacy EIA232, EIA530 and V.35 interfaces. Dpath configuration for each link has two steps:

• Port Configuration

• Emulation Configuration

Note that the 16 ports on the LCE-16 are not all identical.

• Ports 6, 7, 14 and 15 are Asynchronous RS232 only.

• All others ports are Synchronous/Asynchronous RS232, EIA530, X21, RS449 or V

For 01 version hardware, Ports 0, 1, 8 and 9 of the LCE-16 support four controls each (no D

For 02 and higher version hardware, Ports 0, 1, 8 and 9 support five controls each. Two contreach port are inputs, and two are outputs. The fifth signal, DCD, is bi-directional. The cablindistribution panels for the LCE-16 conform to a DCE pin definition. In this configuration, a crover cable is required to achieve DTE pin assignments.

Node Configuration


2. Setup the appropriate LIM type for the VSM Card in Physical Tab

Slot Configuration

1. Select the ACP card on the explorer, right click and bring up the Slot Configuration Wind




up

ted,

default

, link.

ible 1, C

Link Configuration

1. From the Slot Configuration window, click on the Link Config Icon on the toolbar to bringthe Link Configuration window. All LCE-16 configuration screens are available from LinkConfiguration Window.

2. Select the Physical tab to access the Port Configuration screen, shown below. Port Configuration is used to select the physical interface parameters such as: DTE/DCE, synchronous/asynchronous, data rate, character configuration, interface type, etc.

3. The Port Configuration Parameters are listed below. Once the port configuration is selecthe port is enabled.

Port No: Values 0 through 15, indicating the link number.

Enable Port: The link-status desired by the user. Possible values are Yes and No. The value is No.

Port Status: The actual status of the link, Up if the link is enabled and has no problemDown if enabled but has problem, and Disabled if user has Disabled the

Clock Mode: Whether the link is Async, or which Sync DTE/DCE clocking mode. Possvalues are Async, SYNC DCE1, SYNC DCE2, SYNC DCE3, SYNC DTESYNC DTE3. The default value is Async. Links 6, 7, 14 and 15 are ASYNonly.

Note Note that the Port Performance Screen , the Emulation Configuration Screen and the LIM Timing Screen can be launched from the same tab via the Tools menu.



s are

0,

8

rts ously rts

. The

e 5, 6,

is 1.

21, lable

r LIM

the

rt

IM

d 9.

fig-

con-

con-

rt

Invert Rx Clock: Specifies whether the received clock should be inverted. Possible valueyes and no. The default value is no.

Baud Rate: Baud rate for the serial line.

• Ports configured for ASYNC operation allow the values Async75, Async150, Async300, Async1200, Async2400, Async4800, Async720Async9600, Async19200, Async28800, Async33600, Async38400, Async57600.

• When a link is configured for SYNC, only the values Sync1200, Sync2400, Sync4800, Sync9600, Sync19200, Sync56000, and Sync64000, are allowed. SYNC is available on links 0 through 5, andthrough 13. Links 6, 7, 14 and 15 are ASYNC only.

Note that the LCE-16 LIM is divided into two halves; ports 0-7, and po8-15. Sync below 4800 and Sync64000 can not be selected simultanewithin one-half of the LIM. For example, if port 0 is set to Sync2400, po1-7 can not be set to Sync64000.

Parity: Type of parity used on the link. Possible values are none, odd, and evendefault value is none.

Bits / Byte: The number of bits per received/transmitted character. Possible values ar7, and 8. The default value is 8.

Stop Bits: The number of stop bits used. Possible values are 1 and 2. Default value

Physical Interface: The physical interface to use on this link. Possible values are EIA530, XV35, RS449, and RS232. The default value is RS232. Only RS232 is avaion links 6, 7, 14 and 15.

RTS Usage: This parameter only applies to 02 Revision Hardware (and higher) as peHardware Version on the LCE-16 LIM Info screen.

• Transport RTS - Selected for ports 0, 1, 8 or 9 to transport RTS throughATM network to the far end.

• Use RTS Input - Future use option for ports 0, 1, 8 and 9.

• Not Applicable - Selected for ports 2-7 and 10-15 which do not suppoRTS.

CTS Control For the 01 version LCE-16 (as per LIM Hardware Version on the LCE-16 LInfo screen), this item is only configurable in the Async mode. In the synchronous mode CTS is always asserted. Applicable to ports 0,1, 8 an

• Emulation - CTS output is controlled based on the CTS emulation conuration.

• Always Assert - CTS output is always asserted independent of other ditions or configurations

• Always Negate - CTS output is always negated independent of other ditions or configurations.

• Not Applicable - Selected for ports 2-7 and 10-15 which do not suppoCTS.



gh

rt

fig-

con-

con-

rt

.

con-

con-

gh

D.

. and

DTR Usage

• Transport DTR - Selected for ports 0, 1, 8 or 9 to transport DTR throuthe ATM network to the far end.

• Use DTR Input - Future use option for ports 0, 1, 8 or 9.

• Not Applicable - Selected for ports 2-7 and 10-15 which do not suppoDTR.

DSR control Applicable to ports 0,1, 8 and 9.

• Emulation - DSR output is controlled based on the DSR emulation conuration.

• Always Assert - DSR output is always asserted independent of other ditions or configurations.

• Always Negate - DSR output is always negated independent of otherditions or configurations.

• Not Applicable - Selected for ports 2-7 and 10-15 which do not suppoDSR.

DCD Control / UsageApplicable to ports 0,1, 8 and 9. This parameter only applies to LIM Hardware Version 02, as seen on the LCE-16 LIM Info screen.

• Emulation - DCD output is controlled based on DCD emulation config

• Always Assert - DCD output is always asserted independent of other ditions or configurations.

• Always Negate - DCD output is always negated independent of other ditions or configurations.

• Transport DCD - Selected for ports 0, 1, 8 or 9 to transport DCD throuthe ATM network to the far end. DCD is an input for this selection.

• Use DCD Input - Future use option for ports 0, 1, 8 and 9.

• Not Applicable - Selected for ports 2-7, 10-15 which do not support DC

Async overspeed The percentage by which the nominal clock rate should be speeded upNot all overspeed settings apply to all async baud rates. Possible values default value listed below.

Over Speed Values Clock Rate Nominal Baud Rate +1.7% +3.4% +5.3% +7.1%

+1.7% Nominal +1.7% 75 Yes Yes Yes Yes




2400 Yes Yes Yes Yes


7200 NO NO Yes NO


19200 NO Yes NO Yes

28800 NO NO Yes NO

33600 NO NO NO Yes

38400 NO NO NO Yes

57600 NO NO NO NO



only

eiver.

alue

are wn ne.

cable.

02 and

Port Performance Screen

Port Performance window can be launched from the Tools Menu of the LinkConfiguration->Physical Tab. This window displays the state and performance parameters for each port.


Total Rx Bytes: Total number of bytes received, including any errored bytes.

Error Rx Bytes: Total number of bytes with parity error received. This counter is relevant if parity is enabled.

No. of Rx Overflows:The number of times an overflow condition was encountered at the rec

Total Tx Bytes: Total number of bytes transmitted.

No. of Tx Overflows:Total number of bytes lost due to overflow of queues.

No. of Tx Underflows:Total number of times a transmit underflow condition occurred. This vis relevant only for SYNC configuration.

RTS State: This parameter is applicable to links 0, 1, 8 and 9 only. Possible values Asserted, Negated, and Not Applicable. LIM Hardware Version 01 (as shoon LCE-16 LIM Info screen) always indicates asserted state of the RTS li

CTS State: State of the CTS line. Possible values are Asserted, Negated, Not AppliThis object is applicable to links 0, 1, 8 and 9 only.

DTR State: State of the DTR line. Possible values are Asserted, Negated, and Not Applicable. This object is applicable to links 0, 1, 8 and 9 only.

DSR State: State of the DSR line. Possible values are Asserted, Negated, and Not Applicable. This object is applicable to links 0, 1, 8 and 9 only.

DCD State: State of the DCD line. This parameter is applicable to Hardware Versionand higher as seen on LCE-16 LIM Info screen. Applicable to links 0, 1, 8 9 only. Possible values are Asserted, Negated, and Not Applicable.



alues,

le

to

0.

tes by be tion

s, ount) ples n

Emulation Configuration Screen

Emulation Configuration is used to select adaptation layer parameters such as: ATM cell fill vforwarding times, control signal transport mapping, etc. After the emulation configuration is selected the emulation for that port is enabled. This window can be launched from Link Configuration->Physical Tab.


Enable Emulation: This variable is used to enable or disable the emulation function. Possibvalues are Yes / No. The default value for this object is No. To pass data, this option must be set to Yes (You must also set Port Configuration Enabled? port Enabled ).

VCC VPI: The Virtual Path Identifier of the ATM VCC. Currently has a fixed value of

VCC VCI: The Virtual Connection Identifier of the ATM VCC. Currently has a fixed value of 32+ link No.

Cell Fill Level: The number of bytes of data in each cell. Applicable to SYNC link configuration only. Possible values are 2 Bytes, 4 Bytes, 16 Bytes, 32 Byand Max Bytes (max is currently 44, 3 bytes of the AAL1 payload is takenthe Serial Line Emulation overhead), with the additional restriction that it greater than Baud Rate/(8*200). This is because of the LIM's design limitaof 200 cells per second in each direction per link. The default value is 44.

Cell Max Forwarding Time: The maximum inter-cell time, in milliseconds, when sending cellindependent of the number of bytes accumulated (must be nonzero byte cin each cell. Possible values are 10 through 10,000 milliseconds, in multiof 1 millisecond. Applies to the cell flow starting at the local LIM. Useful wheemulating ASYNC lines. The default value is 10.



nly t will

ived port

out-rans-

ved e re-

ed ion

R

ed on-

d lo-S us-

te n

ed CD rt

ich

CTS Config: CTS control in the local port configuration must be set to emulation. On version 01 hardware (as shown on the LCE-16 LIM Info screen), this is oconfigurable in the asynchronous mode. In synchronous mode CTS outpube asserted when ever the LCE-16 is not in an initialization state.

• Copy Remote RTS - Not available on 01 version hardware. RTS receat the remote end is mapped to this output. RTS usage in the remoteconfiguration must be set to transportRTS.

• Copy Remote DTR - DTR received at the remote end is mapped to thisput. DTR usage in the remote port configuration must be set to use Tport DTR.

• Copy Remote DCD - Not available on 01 version hardware. DCD receiat the remote end is mapped to this output. DCD Control / Usage in thmote port configuration must be set to use Transport DCD.

• Copy Local RTS - Not available on 01 version hardware. RTS receivlocally is mapped to this output. RTS usage in the local port configuratmust be set to transportRTS.

• Copy Local DTR - DTR received locally is mapped to this output. DTusage in the local port configuration must be set to Transport DTR.

• Copy Local DCD - Not available on 01 version hardware. DCD receivlocally is mapped to this output. DCD Control / Usage in the local port cfiguration must be set to Transport DCD.

• Copy RTS Echo - Not available on 01 version hardware. RTS receivecally and looped back by the remote end is mapped to this output. RTage in the local port configuration must be set to ignoreRTS.

• Copy DTR Echo - DTR received locally and looped back by the remoend is mapped to this output. DTR usage in the local port configuratiomust be set to Transport DCD.

• Copy DCD Echo - Not available on 01 version hardware. DCD receivlocally and looped back by the remote end is mapped to this output. DControl / Usage in the local port configuration must be set to TranspoDCD.

• Not Applicable - Selected for ports 2 through 7 and 10 through 15 whdo not support CTS.



ived port

out-port

ved e re-

ed ion

R

ed on-

d lo-S us-

end ust

lo-D

rt

ich

DSR Config: DSR control in the local port configuration must be set to emulation.


• Copy Remote DTR - DTR received at the remote end is mapped to thisput. DTR usage in the remote port configuration must be set to TransDTR.

• Copy Remote DCD - Not available on 01 version hardware. DCD receiat the remote end is mapped to this output. DCD Control / Usage in thmote port configuration must be set to Transport DCD.



• Copy Local DCD - Not available on 01 version hardware. DCD receivlocally is mapped to this output. DCD Control / Usage in the local port cfiguration must be set to Transport DCD.

• Copy RTS echo - Not available on 01 version hardware. RTS receivecally and looped back by the remote end is mapped to this output. RTage in the local port configuration must be set to transportRTS.

• Copy DTR echo - DTR received locally and looped back by the remoteis mapped to this output. DTR usage in the local port configuration mbe set to Transport DTR.

• Copy DCD echo - Not available on 01 version hardware. DCD receivedcally and looped back by the remote end is mapped to this output. DCControl / Usage in the local port configuration must be set to TranspoDCD.

• Not Applicable - Selected for ports 2 through 7 and 10 through 15 whdo not support DSR.



LIM al

ived port

out-port

ved e re-

ed ion

R

d lo-S us-

end ust

ich

before tion

f

ue of

DCD Config: This parameter only applies to 02 Revision Hardware (and higher) as perHardware Version on the LCE-16 LIM Info screen. DCD control in the locport configuration must be set to emulation.


• Copy Remote DTR - DTR received at the remote end is mapped to thisput. DTR usage in the remote port configuration must be set to TransDTR.

• Copy Remote DCD - Not available on 01 version hardware. DCD receiat the remote end is mapped to this output. DCD Control / Usage in thmote port configuration must be set to Transport DCD.



• Copy RTS echo - Not available on 01 version hardware. RTS receivecally and looped back by the remote end is mapped to this output. RTage in the local port configuration must be set to transportRTS.

• Copy DTR echo - DTR received locally and looped back by the remoteis mapped to this output. DTR usage in the local port configuration mbe set to Transport DTR.

• Not Applicable - Selected for ports 2 through 7 and 10 through 15 whdo not support DSR.

Tx Prestore Time: The number of microseconds to store data at the serial port's transmitterenabling the transmission. Only applicable when the serial port configurais SYNC. The buffering is meant to smooth the effect of the cell-delay variation of the ATM network. If this value is too small, there is a danger oserial transmitter underflow. Possible values for this object are 0 through 10000 microseconds, in increments of 100 microseconds. The default valthis object is 1000 microseconds.



ff, and

.

ther

uence

lation

Emulation Performance Screen

This window can be launched from Link Configuration->Physical Tab.


Emulation State: The status of the Serial Line Emulation. Possible values are Emulation OEmulation Up.

• Emulation Off indicates the emulation function is disabled for this link

• Emulation Up indicates the emulation function is enabled for this link.

Rx Cells: Number of cells created by the segmentation processor and sent to the oemulation end for this link.

Tx Cells: Number of cells received from the other emulation end for this link.

Out of Seq Cells: The number of cells received from the other emulation end that had a seqnumber lower than cells already received. These cells are dropped.

Bad Format Cells: Number of cells received from the other emulation end that has an undecodable/unsupported format.

Seq Number Sent: The sequence number sent in the last cell transmitted, to the other emuend.

Seq Number Received:The sequence number in the last cell received.



nsmit , in n on ork.

be

No.

id.

valid.

LIM Timing Screen

LIM Timing window can be launched from Tools menu of Link Configuration->Physical Tab.

Master Tx Timing Source:This parameter is used to set what source should be used to drive the TraClock. Possible values are System Clock, or Local Oscillator. The defaultvalue for this object is System Clock. When the System Clock is selectedtransmit timing is synchronized to the primary or secondary system clockthe Xedge node. This synchronizes the LCE-16 LIM to the network. WhelocalOscillator is selected, transmit timing is synchronized to an oscillatorthe LCE-16 LIM. In this mode, transmit timing is asynchronous to the netw

Master Tx Timing Used:The actual timing source used. Possible values for this object are Local Oscillator, Primary Bus and Secondary Bus. Depends on Tmg Source to Used: and actual availability of clocks.

Stratum3 Clock Available:Is the LIM is receiving Stratum3 timing. The possible values are Yes and

Primary Timing Bus Status:The status of the Primary timing bus. Possible values are Valid and Inval

Secondary Timing Bus Status: The status of the Secondary timing bus. Possible values are Valid and In


3UR6SKHUH 106Preface Support Services and Training vi ProSphere NMS 032R610-V601 Version 6.0.1 User...

Documents

Transcript of 3UR6SKHUH 106Preface Support Services and Training vi ProSphere NMS 032R610-V601 Version 6.0.1 User...