Navis EMS-PSAX User Guide for the Client/Server Application

Doc. No.: 255-700-762R11.1

Navis® EMS-PSAX User Guide for the Client/Server ApplicationIssue 1, July 2006

Navis® EMS-PSAX Software Release 11.1.0 for PacketStar® PSAX Multiservice Media Gateways

Copyright © 2006 by Lucent Technologies. All rights reserved.

For trademark, regulatory compliance, and related legal information, see the "Copyright and Legal Notices" section.

Copyright and Legal Notices

CopyrightCopyright © 2006 by Lucent Technologies. All rights reserved.

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

Information is subject to change. Lucent Technologies assumes no responsi-bility or liability for errors or inaccuracies that may appear in this guide.

TrademarksLucent, Lucent Technologies, PacketStar, Navis, and the Lucent Technologies logo are registered trademarks of Lucent Technologies in the USA.

NavisCore and NavisXtend are trademarks of Lucent Technologies in the USA.

Adobe is a registered trademark of Adobe Systems, Inc.

UNIX is a registered trademark of The Open Group.

Windows, Windows NT and Windows XP are registered trademarks of Microsoft Corporation in the United States and/or other countries.

Other product and brand names mentioned in this guide are trademarks or registered trademarks of their respective owners.

Software Limited WarrantyLucent Technologies provides a 90-day limited software warranty. Refer to the Software License envelope that accompanied your package for more infor-mation.

Navis® EMS-PSAX User Guide for the Client/Server Application, Issue 1 Release 11.1.0

255-700-762R11.1 iii

Copyright and Legal NoticesSoftware Limited Warranty

iv 255-700-762R11.1


Contents

Copyright and Legal Notices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . iiiCopyright . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . iii

Trademarks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . iii

Software Limited Warranty . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . iii

List of Figures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xvii

List of Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxvii

1 Getting Started . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1Purpose of This Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-1

Audience For This Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-1

What You Should Know . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-1

Lucent Technologies Information Products. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-2

Product Information Library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-2

Printed Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-2

Other Publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-2

About Lucent Technologies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-2

History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-2

For More Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-3

Text Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-3

Text Types Used in This Document. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-3

Icons and Symbols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-3

Use of Button Description Tables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-4

Use of Field Description Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-4

Selecting Menu Options and Fields in the EMS-PSAX GUI . . . . . . . . . . . . . . . . . . . . . .1-5

Technical Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-6

Before You Begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-6

Planning the PSAX Management Network. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-7

Comments on This Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-8

2 EMS-PSAX Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1Managing PSAX Devices with the EMS-PSAX. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-1

Managing the PSAX Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-1

Monitoring System Faults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-1

Monitoring Real-Time Statistics and System Performance . . . . . . . . . . . . . . . . . . . . . .2-2.2-2

.2-1

.2-1

.2-1

2-1

.1-8

.1-7

.1-6

.1-6

.1-5

.1-4

.1-4

.1-3

.1-3

.1-3

.1-3

.1-2

.1-2

.1-2

.1-2

.1-2

.1-2

.1-1

.1-1

.1-1

1-1

xxvii

xvii

iii

iii

iii

iii

255-700-762R11.1 v


Contents

Managing Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2

Operating the EMS-PSAX. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2

Front Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3

LED/Port Indicators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3

Client/Server Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4

CORBA Client/Server Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4

Client/Server Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-5

Simple Network Management Protocol (SNMP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-5

SNMP MIB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-6

SNMP Traps. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-6

Designating SNMP Trap Recipients . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-6

Network Management Access Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-8

I/O and Server Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-8

List of I/O Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-8

Configuring Ports, Channels, and Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-9

Creating Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-9

3 Navigating Windows in the EMS-PSAX . . . . . . . . . . . . . . . . . . . . . . . .3-1Overview of This Chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1

The Device List and User List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1

Using the Device List Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2

Adding Device List Information in SNMPv2c Mode . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2

Virtual Client Feature . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-6

Updating Device Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-7

Deleting Device Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-8

Accessing a Device From the Open Device Window in SNMPv2c Mode . . . . . . . . . . . 3-8

Accessing a Device From the Device List Window . . . . . . . . . . . . . . . . . . . . . . . 3-10

Opening Multiple Devices Simultaneously . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-10

Device Verification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-10

Using the User List. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-11

Adding a Username to the User List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-11

Updating User Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-16

Viewing User Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-17

Deleting User Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-17

Changing the User Password. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-18

Managing PSAX Devices in SNMPv3 Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-19

Configuring SNMPv3 Access in the EMS-PSAX . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-19

Adding Device List Information in SNMPv3 Mode . . . . . . . . . . . . . . . . . . . . . . . . . . 3-20

Accessing a Device From the Open Device Window in SNMPv3 Mode . . . . . . . . . . . 3-213-21

3-20

3-19

3-19

3-18

3-17

3-17

3-16

3-11

3-11

3-10

3-10

3-10

3-8

3-8

3-7

3-6

3-2

3-2

3-1

3-1

.3-1

2-9

2-9

2-8

2-8

2-8

2-6

2-6

2-6

2-5

2-5

2-4

2-4

2-3

2-3

2-2

2-2

vi 255-700-762R11.1


Contents

Determining the EMS-PSAX Engine ID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-26

Configuring SNMPv3 Devices Monitored by PollClient. . . . . . . . . . . . . . . . . . . . . . . .3-26

Managing Network Partitioning for Users and PSAX Devices . . . . . . . . . . . . . . . . . . . . . .3-27

Prerequisites for Managing Network Partitioning . . . . . . . . . . . . . . . . . . . . . . . . . . .3-28

Managing Network Partitioning From the User List . . . . . . . . . . . . . . . . . . . . . . . . . .3-28

Adding Users to the Device Access List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-29

Removing Users From the Device Access List . . . . . . . . . . . . . . . . . . . . . . . . . . .3-30

Managing Network Partitioning From the Device List . . . . . . . . . . . . . . . . . . . . . . . .3-32

Adding Users to the User Access List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-32

Removing Users From the User Access List . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-33

Using the Main EMS-PSAX Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-34

Title Bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-34

Menu Bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-35

File Menu. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-35

View Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-36

Help Menu. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-38

Message Bar. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-38

Device Tree . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-39

Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-39

Expanding and Collapsing the Device Tree . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-40

Running Scripts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-42

Device Window Menu Bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-43

Device Window Layers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-44

Front Panel Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-47

Connections Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-50

Site-Specific Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-51

Diagnostics Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-51

System Maintenance Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-52

IISP Routing Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-52

PNNI Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-53

Log Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-53

Active Alarm Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-54

4 Site-Specific Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1Site-Specific Documentation for the EMS-PSAX. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-1

Overview of PSAX Site-Specific Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-1

Configuring the Stratum 3–4 Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-4

Configuring CPU Module Parameters for System Identification . . . . . . . . . . . . . . . . . . . .4-17

Rules for Configuring IP Addresses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-18.4-18

.4-17

.4-4

.4-1

.4-1

4-1

.3-54

.3-53

.3-53

.3-52

.3-52

.3-51

.3-51

.3-50

.3-47

.3-44

.3-43

.3-42

.3-40

.3-39

.3-39

.3-38

.3-38

.3-36

.3-35

.3-35

.3-34

.3-34

.3-33

.3-32

.3-32

.3-30

.3-29

.3-28

.3-28

.3-27

.3-26

.3-26

255-700-762R11.1 vii


Contents

Rules for Configuring IP Address Masks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-19

Configuring the Date and Time for the PSAX Device . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-19

Configuring the TCP Client/Server for a Connection Gateway . . . . . . . . . . . . . . . . . . . . 4-21

Configuring System-Related Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-24

ATM Addresses and OAM Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-26

Configuring SNMP Trap Destinations and Source Types . . . . . . . . . . . . . . . . . . . . . . . . . 4-27

Enabling System-Wide Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-31

Configuring Call Control Resource Allocation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-34

Interface Protection Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-42

Creating a Protection Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-42

Viewing a Protection Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-44

Deleting a Protection Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-45

Creating Interface Protection Entries Within a Group. . . . . . . . . . . . . . . . . . . . . . . . 4-46

Viewing an Interface Protection Entry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-49

Deleting an Interface Protection Entry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-50

IP Throttling. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-52

IP Throttling Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-52

Viewing Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-56

Configuring N:1 Protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-56

Configuring N:1 Protection Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-56

Viewing N:1 Protection Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-60

Updating N:1 Protection Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-61

Deleting N:1 Protection Groups. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-62

Viewing N:1 Protection Slot Configurations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-64

Performing N:1 Protection Slot Switchovers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-67

Saving Configuration Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-69

5 Configuring ATM Trunking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-1Overview of This Chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1

Switched Trunking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1

Non-Switched Trunking. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1

Configuring the Local Node. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2

Configuring the Remote IWF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-4

Configuring the Signaling VCC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-8

Configuring Bearer VCC Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-12

Configuring the Bearer VCC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-12

Provisioning Bearer VCCs in Bulk. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-21

Configuring Bearer VCC Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-23

Configuring the DSP Parameters for the Bearer VCC . . . . . . . . . . . . . . . . . . . . . . . . 5-255-25

5-23

5-21

5-12

5-12

5-8

5-4

5-2

5-1

5-1

5-1

.5-1

4-69

4-67

4-64

4-62

4-61

4-60

4-56

4-56

4-56

4-52

4-52

4-50

4-49

4-46

4-45

4-44

4-42

4-42

4-34

4-31

4-27

4-26

4-24

4-21

4-19

4-19

viii 255-700-762R11.1


Contents

Deleting Bearer VCCs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-29

Creating a Broadband Routing Entry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-30

Creating a Narrowband Routing Entry. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-32

Viewing the Data Channel Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-34

6 Configuring System Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1Configuring User Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-1

Configuring EMS-PSAX Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-1

Specifying the Adobe Acrobat Reader Path. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-4

EMS-PSAX Logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-5

EMS-PSAX System Log Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-5

Security Log Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-5

Config Log Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-6

Location of Log Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-7

Log Message Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-7

EMS-PSAX System Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-8

Adding a PSAX Icon to an HP OpenView NNM Map . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-14

Viewing the EMS-PSAX Poll Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-15

RADIUS Server Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-19

Configuring the RADIUS Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-19

Configuring RADIUS Properties in the EMS-PSAX . . . . . . . . . . . . . . . . . . . . . . . . . . .6-20

Setting Up the Aqv.properties File for the RADIUS Server . . . . . . . . . . . . . . . . . .6-20

Setting Up the Radius.properties for the RADIUS Server . . . . . . . . . . . . . . . . . . .6-20

7 Fault Monitoring. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1Overview of Fault Monitoring in the EMS-PSAX. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-1

Event, Alarm, and Trap Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-1

EMS-PSAX Log Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-3

Overview of the EMS-PSAX Log Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-3

Log Page Menu Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-4

Trap Descriptions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-5

Overview of Enhanced Trap Descriptions Feature . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-5

Finding a Trap Message Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-5

Saving the Trap Log. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-8

Finding Text in a Trap Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-8

Copying Trap Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-11

Cutting and Pasting Trap Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-11

Deleting Trap Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-11

SNMP Trap Log Capacity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-12.7-12

.7-11

.7-11

.7-11

.7-8

.7-8

.7-5

.7-5

.7-5

.7-4

.7-3

.7-3

.7-1

.7-1

7-1

.6-20

.6-20

.6-20

.6-19

.6-19

.6-15

.6-14

.6-8

.6-7

.6-7

.6-6

.6-5

.6-5

.6-5

.6-4

.6-1

.6-1

6-1

.5-34

.5-32

.5-30

.5-29

255-700-762R11.1 ix


Contents

MIB Objects Used for Traps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-12

Trap Activation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-12

Disconnecting EMS-PSAX Clients On-Demand . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-15

Forcing the Unloading of EMS-PSAX Clients . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-16

Obtaining Module Hardware Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-17

Obtaining Hardware Operating Status Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-17

Obtaining LED Status Indicator Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-17

Obtaining Port Configuration Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-19

Ghosted Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-20

PSAX Symbols on the HP OpenView NNM Submap . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-21

Operational Status and Colors of Symbols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-21

CPU Status Symbol Colors. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-22

EMS-PSAX Active Alarm Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-22

Overview of the EMS-PSAX Active Alarm Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-22

Active Alarm Table Menu Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-26

Setting filters for the Active Alarm Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-26

8 Configuring ATM Routing Data Using PNNI. . . . . . . . . . . . . . . . . . . . .8-1Overview of This Chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-1

Configuring PNNI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-1

Adding PNNI Routing Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-4

Viewing PNNI Node PGL Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-8

Viewing PNNI Node Timer Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-11

Viewing PNNI Node SVCC Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-14

Viewing PNNI Scope Mapping Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-16

Configuring Route Addresses and Metrics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-19

Configuring Route Addresses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-19

Configuring Metrics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-25

Configuring Route TNS Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-29

Configuring PNNI Summary Addresses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-35

Viewing PNNI Map Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-37

Viewing PNNI Map Node Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-41

Viewing PNNI Map Address Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-44

Viewing PNNI Map TNS Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-46

Viewing PNNI Link Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-48

Viewing PNNI SVCC RCC Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-54

Viewing PNNI Neighbor Peer Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-54

Viewing PNNI Neighbor Peer Port Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-57

Viewing PNNI PTSE Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-598-59

8-57

8-54

8-54

8-48

8-46

8-44

8-41

8-37

8-35

8-29

8-25

8-19

8-19

8-16

8-14

8-11

8-8

8-4

8-1

8-1

.8-1

7-26

7-26

7-22

7-22

7-22

7-21

7-21

7-20

7-19

7-17

7-17

7-17

7-16

7-15

7-12

7-12

x 255-700-762R11.1


Contents

Viewing PNNI Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-62

Saving Configuration Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-65

9 Configuring ATM Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-1Overview of This Chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-1

Overview of the ATM Security Feature. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-1

Configuring PNNI SVCC RCC Security Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-1

Setting the Values for PNNI SVCC RCC Security Information . . . . . . . . . . . . . . . . . . . .9-1

Viewing PNNI SVCC RCC Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-6

Viewing PNNI SVCC RCC Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-8

Enabling ATM Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-12

Configuring ATM Security on the ATM UNI Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-13

Configuring a Signaling PVC. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-13

Viewing Signaling PVC Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-18

Configuring ATM Security on the ATM PNNI Interface . . . . . . . . . . . . . . . . . . . . . . . . . . .9-22

Configuring a Signaling PVC. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-22

Viewing Signaling PVC Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-27

Configuring a Routing PVC. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-31

Viewing Routing PVC Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-36

10 Using Diagnostics and Upgrading PSAX Components. . . . . . . . . . . 10-1Overview of This Chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10-1

Running System Diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10-1

Viewing System Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10-3

Disk and Memory Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10-5

Backplanes and Cell Bus Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10-6

Cell Buffers and Message Pool Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10-7

Operations Administration and Maintenance (OAM) . . . . . . . . . . . . . . . . . . . . . . . . . . . .10-7

Performing OAM Loopback Tests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10-8

OAM Activation and Deactivation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10-10

Running Cell Test Diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10-18

Configuring RTD / CLM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10-21

Performing RTD / CLM Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10-21

Copying RTD / CLM Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10-25

Diagnostics for Module Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10-28

Diagnostics for PSAX Hardware Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10-30

Restarting PSAX Device Hardware Components . . . . . . . . . . . . . . . . . . . . . . . . . . .10-30

Switching to the Standby CPUn Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10-32

Removing Configuration Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10-33.10-33

.10-32

.10-30

.10-30

.10-28

.10-25

.10-21

.10-21

.10-18

.10-10

.10-8

.10-7

.10-7

.10-6

.10-5

.10-3

.10-1

.10-1

10-1

.9-36

.9-31

.9-27

.9-22

.9-22

.9-18

.9-13

.9-13

.9-12

.9-8

.9-6

.9-1

.9-1

.9-1

.9-1

9-1

.8-65

.8-62

255-700-762R11.1 xi


Contents

Saving Configuration Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-34

PSAX System Software Upgrades and Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-34

Before You Begin Upgrading PSAX System Software . . . . . . . . . . . . . . . . . . . . . . . 10-34

System Maintenance Tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-35

Upgrading the System Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-36

Reverting to a Previous CPU Software Version . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-41

Upgrading Firmware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-42

Firmware Drivers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-42

Selecting Firmware Drivers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-43

Upgrading Firmware on I/O and Server Modules . . . . . . . . . . . . . . . . . . . . . . . 10-43

Scheduling PSAX Configuration Backups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-47

Creating an FTP-Only Account . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-48

Setting Up a PSAX Backup Schedule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-49

Viewing Configured Backup Schedules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-53

Checking the Status of a Backup Process. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-53

Deleting a PSAX Backup Schedule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-53

Remote Database Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-54

Profiling Tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-57

Configuring Bulk Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-59

Enabling Bulk Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-59

Viewing Bulk Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-61

Copying Thousands of Connections When the Bulk Statistics Feature is Enabled . . 10-64

11 Configuring the GR-303 Voice Gateway. . . . . . . . . . . . . . . . . . . . . . .11-1GR-303 Feature Availability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-1

Enabling the GR-303 Feature. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-1

Configuring I/O and Server Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-4

Configuring the DSP2 Voice Server Module Values . . . . . . . . . . . . . . . . . . . . . . . . . 11-4

Configuring ATM I/O Module Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-5

Applying the GR-303 Interface to DS1s . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-5

Configuring the GR-303 Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-6

Configuring the GR-303 Gateway . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-9

Updating GR-303 Interface Group Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-17

Adding DS1s to a GR-303 Interface Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-19

Viewing GR-303 Interface Group Statistics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-21

Performing Bulk Operations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-22

Creating GR-303 AAL2 PVC Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-24

Adding an AAL2 Trunk Entry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-24

Provisioning a GR-303 AAL2 PVC Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-3411-34

11-24

11-24

11-22

11-21

11-19

11-17

11-9

11-6

11-5

11-5

11-4

11-4

11-1

11-1

.11-1

10-64

10-61

10-59

10-59

10-57

10-54

10-53

10-53

10-53

10-49

10-48

10-47

10-43

10-43

10-42

10-42

10-41

10-36

10-35

10-34

10-34

10-34

xii 255-700-762R11.1


Contents

Viewing a GR-303 AAL2 PVC Connection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11-39

Saving Your Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11-41

12 Configuring the H.248 Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-1Overview of This Chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12-1

Enabling the H.248 Protocol Feature . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12-1

Turning On the H.248 Protocol Feature. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12-1

Configuring Call Control Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12-3

Rebooting the PSAX System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12-5

Configuring the H.248 Protocol Feature Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . .12-5

Accessing the H.248 Protocol Feature Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . .12-6

Establishing the PSAX System to MGC Communication Links . . . . . . . . . . . . . . . . . .12-8

Configuring the Congestion Handling between the PSAX System to MGC . . . . . . .12-10

Configuring the Tone Generation and Detection Parameter . . . . . . . . . . . . . . . . . .12-12

Configuring the H.248 TIDs on the TDM-interface Modules . . . . . . . . . . . . . . . . . . . . .12-13

Prerequisites for Configuring the H.248 TIDs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12-13

Configuring the Pseudo TID at the Slot Level . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12-14

Configuring the Pseudo TID at the Port Level . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12-17

Configuring the Logical TID at the Channel Level . . . . . . . . . . . . . . . . . . . . . . . . . .12-19

Saving the System Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12-21

13 Tracing a Call . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-1Purpose of This Chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13-1

Tracing a Call with the Context ID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13-1

Tracing a Call with the TID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13-2

14 Configuring V5.2 European IDLC . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-1Configuring the V5.2 Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14-1

Overview of V5.2 Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14-1

Enabling V5.2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14-1

Setting Call Control Resources for V5.2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14-3

Configuring V5.2 Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14-11

Configuring V5.2 DSP Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14-15

Accessing the DSP Over Subscription Window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14-16

Configuring V5.2 Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14-19

Viewing a V5.2 Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14-21

Updating a V5.2 Interface. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14-21

Deleting a V5.2 Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14-22

Configuring V5.2 Variants . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14-24

Viewing a V5.2 Variant . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14-28.14-28

.14-24

.14-22

.14-21

.14-21

.14-19

.14-16

.14-15

.14-11

.14-3

.14-1

.14-1

.14-1

14-1

.13-2

.13-1

.13-1

13-1

.12-21

.12-19

.12-17

.12-14

.12-13

.12-13

.12-12

.12-10

.12-8

.12-6

.12-5

.12-5

.12-3

.12-1

.12-1

.12-1

12-1

.11-41

.11-39

255-700-762R11.1 xiii


Contents

Updating a V5.2 Variant . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-28

Deleting a V5.2 Variant . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-29

Configuring V5.2 Physical C Channels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-31

Viewing a V5.2 Physical C Channel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-34

Updating a V5.2 Physical C Channel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-35

Deleting a V5.2 Physical C Channel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-36

Configuring V5.2 E1 Links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-38

Using the Timeslot Channel Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-40

Viewing a V5.2 E1 Link . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-42

Updating a V5.2 E1 Link . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-43

Deleting a V5.2 E1 Link. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-44

Configuring V5.2 Data Links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-46

Viewing a V5.2 Data Link . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-49

Deleting a V5.2 Data Link . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-49

Configuring ATM Trunking for the V5.2 Application . . . . . . . . . . . . . . . . . . . . . . . . . . 14-51

Configuring V5.2 User Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-52

Viewing a V5.2 User Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-58

Updating a V5.2 User Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-59

Deleting a V5.2 User Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-60

Accessing the V5 B Channels CID Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-62

Appendix A Troubleshooting the EMS-PSAX . . . . . . . . . . . . . . . . . . . . . . . . A-1Troubleshooting Topics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-1

Launching and Logging in to the EMS-PSAX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-1

Cannot Log Into the EMS-PSAX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-1

Setting Up a Client on the Same Subnet as the EMS-PSAX Server Causes the Client to Malfunction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-2

The EMS-PSAX Client Does Not Connect to the Server . . . . . . . . . . . . . . . . . . . . A-2

Using the Main Menu Bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-3

Cannot Open a Device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-3

Cannot Add Users to the User List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-5

Cannot Add Devices to the Device List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-6

Cannot View User Documentation From the Help Option in the Menu Bar . . . . . A-6

Cannot Change User Properties for Your EMS-PSAX . . . . . . . . . . . . . . . . . . . . . . A-6

IP Addresses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-7

Cannot Determine IP Address or Community Name of a Device . . . . . . . . . . . . . A-7

Cannot Set the Switch IP Address Using the EMS-PSAX . . . . . . . . . . . . . . . . . . . A-7

Cannot Open a Device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-8

Cannot Open a Device Using Windows XP/2000. . . . . . . . . . . . . . . . . . . . . . . . . A-8A-8

A-8

A-7

A-7

A-7

A-6

A-6

A-6

A-5

A-3

A-3

A-2

A-2

A-1

A-1

A-1

A-1

14-62

14-60

14-59

14-58

14-52

14-51

14-49

14-49

14-46

14-44

14-43

14-42

14-40

14-38

14-36

14-35

14-34

14-31

14-29

14-28

xiv 255-700-762R11.1


Contents

Cannot Open a Device from theOpen Device Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-8

Cannot Update the EMS-PSAX GUI Display; Do Not Receive SNMP Trap Messages A-9

Diagnosing Errors Using the EMS-PSAX Installation Log File . . . . . . . . . . . . . . . . A-9

Cannot Access the EMS-PSAX CD-ROM Using File Manager on Solaris Workstation . A-10

Cannot Install the EMS-PSAX on Solaris . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-10

Checking Which Version of the EMS-PSAX Is Installed on Your Workstation . . . A-11

I/O and Server Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-12

Cannot Change Values on a Port and Channel Configuration Window . . . . . . A-12

Cannot Remove Ghosted Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-12

Cannot Overwrite the Existing Interface Configuration on the Copy Interface Configuration Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-13

Cannot Create a Backup PVC Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-13

Cannot Restore a Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-13

Cannot View Slot 25 in the Front Panel for a PSAX 2300 Device. . . . . . . . . . . . A-13

NSAP Database. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-14

Cannot View the Remote NSAP Address in the NSAP Database . . . . . . . . . . . . A-14

Cannot View a Remote Device in the Remote Switch IP Menu . . . . . . . . . . . . . A-14

Cannot Delete an NSAP Address Entry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-14

General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-15

Cannot Modify an IISP VBR/CBR Route Entry . . . . . . . . . . . . . . . . . . . . . . . . . . A-15

Cannot Update or Delete a PNNI Node. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-15

Cannot View a Current List of SVCs (or Other Data) . . . . . . . . . . . . . . . . . . . . . A-15

Need to Monitor Disk and Memory Usage on CPU . . . . . . . . . . . . . . . . . . . . . . A-15

Checking the Crontab File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-16

Errors Displaying In-band Addresses in HP OpenView NNM . . . . . . . . . . . . . . . . . . . . . . A-16

Operational Conditions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-16

Workaround to HP OpenView NNM Problems with Addresses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-17

Errors in Applying Interfaces to Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-17

Errors in Creating Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-17

Displaying Graphics Properly on Solaris . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-18

Appendix B Setting Up Firewall Support . . . . . . . . . . . . . . . . . . . . . . . . . . . B-1Overview of This Appendix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .B-1

Firewall Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .B-1

Firewall Between the EMS-PSAX Client and Server . . . . . . . . . . . . . . . . . . . . . . . . . . .B-1

Setting Up the Client Workstation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .B-2B-2

B-1

B-1

B-1

B-1

A-18

A-17

A-17

A-17

A-16

A-16

A-16

A-15

A-15

A-15

A-15

A-15

A-14

A-14

A-14

A-14

A-13

A-13

A-13

A-13

A-12

A-12

A-12

A-11

A-10

A-9

A-8

A-10

255-700-762R11.1 xv


Contents

Setting Up the Gatekeeper . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-2

Setting Up the Firewall . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-3

Launching Network Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-3

Firewall Between the EMS-PSAX Server and a PSAX Device . . . . . . . . . . . . . . . . . . . . B-3

EMS-PSAX Client/Server Configuration in NAT Environments . . . . . . . . . . . . . . . . . . . B-4

Configuring the Server Workstation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-4

Configuring the Client Workstation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-5

Receiving Traps From the NAT EMS-PSAX Server . . . . . . . . . . . . . . . . . . . . . . . . . B-5

Appendix C EMS-PSAX Configuration Options with HP OpenView NNM . C-1Overview of This Chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-1

Generating Reports Using HP OpenView NNM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-1

Data Collection and Thresholding. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-1

Setting Up Data Collection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-2

Viewing Collected Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-10

Using the HP OpenView NNM Events Log and Browser. . . . . . . . . . . . . . . . . . . . . . . . . . C-12

Event Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-13

Events Browser. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-13

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-13

Event Browser List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-13

Tips for Using the Event Browser . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-13

Actions on Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-14

Assigning Categories and Severity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-14

Acknowledging and Deleting Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-14

Saving and Restoring Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-14

Highlighting Event Sources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-15

Additional Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-15

Filtering Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-15

Event Filter Elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-15C-15

C-15

C-15

C-15

C-14

C-14

C-14

C-14

C-13

C-13

C-13

C-13

C-13

C-12

C-10

C-2

C-1

C-1

C-1

C-1

B-5

B-5

B-4

B-4

B-3

B-3

B-3

B-2

xvi 255-700-762R11.1


List of Figures

1-1 Field Description Table Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-5

2-1 Device Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-3

2-2 Sample EMS-PSAX Client/Server Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-5

2-3 Add to Trap List Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-7

2-4 SNMP Manager List is Full Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-7

3-1 The Main EMS-PSAX Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-2

3-2 Device List Window (in SNMPv2c Mode) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-3

3-3 Device List Window (Displaying Menu) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-4

3-4 Add Device Dialog Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-4

3-5 Device Cannot Be Unloaded Error Message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-6

3-6 Device Was Not Preloaded in Server Error Message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-7

3-7 Device Unload Confirmation Message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-7

3-8 Update Device Dialog Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-7

3-9 Confirmation Window (Deleting Device List Entry) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-8

3-10 Open Device Window (SNMPv2c Mode) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-9

3-11 Error Message Window (Cannot Open Device) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-11

3-12 View Menu (As Displayed on the EMS-PSAX Menu Bar) . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-12

3-13 User List Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-12

3-14 User List Window (Displaying Menu) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-12

3-15 Create New User Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-13

3-16 Password Expiration Warning Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-16

3-17 Update User Information Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-16

3-18 User Information Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-17

3-19 Confirmation Window (Deleting User List Entry) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-18

3-20 Reset User Password Window (Administrator Privileges) . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-19

3-21 SNMPv3 Device List Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-20

3-22 SNMPv3 Device List Window (Displaying User Names) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-21

3-23 Add SNMPv3 Device Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-22

3-24 Open SNMPv3 Device Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-22

3-25 HP OV V3 Device List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-27

3-26 Unauthorized User Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-28

3-27 Device Selection Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-29

3-28 Enable User Access Confirmation Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-30

3-29 User Access List Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-32

3-30 EMS-PSAX Valid User List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-33

3-31 Deleting User Access List Entry Confirmation Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-33.3-33

.3-33

.3-32

.3-30

.3-29

.3-28

.3-27

.3-22

.3-22

.3-21

.3-20

.3-19

.3-18

.3-17

.3-16

.3-16

.3-13

.3-12

.3-12

.3-12

.3-11

.3-9

.3-8

.3-7

.3-7

.3-7

.3-6

.3-4

.3-4

.3-3

.3-2

.2-7

.2-7

.2-5

.2-3

.1-5

255-700-762R11.1 xvii


List of Figures

3-32 Device Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-34

3-33 Title Bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-34

3-34 Menu Bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-35

3-35 File Menu (As Displayed on the EMS-PSAX Menu Bar) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-35

3-36 View Menu (As Displayed on the EMS-PSAX Menu Bar) . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-36

3-37 Help Menu (As Displayed on the EMS-PSAX Menu Bar) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-38

3-38 About Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-38

3-39 Message Bar (Bottom of Window) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-39

3-40 Message Bar (Top of Window) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-39

3-41 Device Tree (Displaying Empty Slots) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-39

3-42 Device Tree Status Indicators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-40

3-43 Device Tree (Displaying Right-Click Menu) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-40

3-44 Expanded Device Tree . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-41

3-45 Collapsed Device Tree . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-41

3-46 Run Script Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-42

3-47 Sample Port and Channel Configuration Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-45

3-48 Sample Channel Configuration Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-46

3-49 Sample Port Statistics Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-47

3-50 Front Panel Tab (Displaying a PSAX 4500 Chassis) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-48





3-55 Device Tree (Displaying an Alarm Module in Slot 25) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-50

3-56 Site-Specific Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-51

3-57 Diagnostics Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-51

3-58 CPU Upgrade Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-52

3-59 IISP Routing Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-52

3-60 PNNI Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-53

3-61 Log Tab (Displaying Menu) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-53

3-62 Active Alarm Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-54

4-1 Site-Specific Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2

4-2 Front Panel View of the Stratum 3–4 Module (Used in the PSAX 1250 Chassis) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-5

4-3 Front Panel View of the Stratum 3–4 Module (Used in the PSAX 1000 and PSAX 2300 Chassis) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-6

4-4 Front Panel View of the Stratum 3–4 Module (Used in the PSAX 4500 Chassis) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-7

4-5 Primary Stratum Configuration Window (PSAX 1000) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-8

4-6 Primary Stratum Configuration Window (PSAX 1250) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-8

4-7 Primary Stratum Configuration Window (PSAX 2300) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-94-9

4-8

4-8

4-7

4-6

4-5

4-2

3-54

3-53

3-53

3-52

3-52

3-51

3-51

3-50

3-50

3-49

3-49

3-48

3-48

3-47

3-46

3-45

3-42

3-41

3-41

3-40

3-40

3-39

3-39

3-39

3-38

3-38

3-36

3-35

3-35

3-34

3-34

xviii 255-700-762R11.1


List of Figures

4-8 Primary Stratum Configuration Window (PSAX 4500) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-9

4-9 System Identification Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-17

4-10 System Date and Time Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-20

4-11 PacketStar® PSAX System as a TCP Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-21

4-12 PacketStar® PSAX System as a TCP Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-22

4-13 TCP Server Configuration Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-22

4-14 System Related Data Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-24

4-15 Master ATM Address Type and OAM Related Data Panel . . . . . . . . . . . . . . . . . . . . . . . . . . .4-26

4-16 Notify and Target Address Table Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-28

4-17 UPDATE Notify and Target Address Table Entry Window . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-28

4-18 Feature Turn On/Off Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-32

4-19 Feature Turn On/Off Page Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-32

4-20 Feature Turn On/Off Confirmation Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-32

4-21 Call Control Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-35

4-22 Call Control Confirmation Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-36

4-23 Protection Group Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-42

4-24 Protection Group Table Right-Click Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-43

4-25 ADD Protection Group Entry Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-43

4-26 UPDATE Protection Group Entry Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-44

4-27 Protection Group Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-45

4-28 VIEW Protection Group Entry Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-45

4-29 Delete Protection Group Entry Confirmation Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-46

4-30 ADD Interface Protection Entry Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-47

4-31 VIEW Interface Protection Entry Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-50

4-32 UPDATE Interface Protection Entry Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-51

4-33 IP Throttling Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-53

4-34 N to M Protection Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-57

4-35 N to M Protection Group Table Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-57

4-36 N to M Protection Group Table Entry Window (ADD) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-58

4-37 N to M Protection Group Table Entry Window (VIEW) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-61

4-38 N to M Protection Group Table Entry Window (VIEW) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-62

4-39 N to M Protection Table (Displaying Menu) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-64

4-40 N to M Protection Table Entry Window(Working and Protection Slots Displayed Respectively) . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-65

4-41 UPDATE N To M Protection Table Entry Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-68

4-42 Confirmation Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-68

5-1 ATM Trunking Page (Displaying Menu) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-3

5-2 View ATM Trunking Remote IWF Table Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-5

5-3 View ATM Trunking Remote IWF Table Window (Displaying Menu) . . . . . . . . . . . . . . . . . . . .5-6

5-4 ADD ATM Trunking Remote Entry Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-6

5-5 View ATM Trunking Sig Vcc Table Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-9.5-9

.5-6

.5-6

.5-5

.5-3

.4-68

.4-68

.4-65

.4-64

.4-62

.4-61

.4-58

.4-57

.4-57

.4-53

.4-51

.4-50

.4-47

.4-46

.4-45

.4-45

.4-44

.4-43

.4-43

.4-42

.4-36

.4-35

.4-32

.4-32

.4-32

.4-28

.4-28

.4-26

.4-24

.4-22

.4-22

.4-21

.4-20

.4-17

.4-9

255-700-762R11.1 xix


List of Figures

5-6 ADD ATM Trunking Sig VCC Entry Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-10

5-7 View ATM Trunking Br Vcc Table Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-13

5-8 ADD ATM Trunking Br VCC Entry Window (Bearer VCC Config Page) . . . . . . . . . . . . . . . . . 5-14

5-9 UPDATE ATM Trunking Br VCC Entry Window (Bearer VCC Config Page) . . . . . . . . . . . . . . 5-22

5-10 Copy Bearer VCC Configuration Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-23

5-11 View ATM Trunking Bearer VCC Profile Config Table Window . . . . . . . . . . . . . . . . . . . . . . 5-24

5-12 View ATM Trunking Bearer VCC Profile Entry Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-24

5-13 ADD ATM Trunking Br VCC Entry Window (DSP Parameters Page) . . . . . . . . . . . . . . . . . . . 5-26

5-14 View Broadband Table Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-30

5-15 ADD ATM Trunking Broadband Routing Entry Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-31

5-16 View Narrowband Table Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-32

5-17 ADD ATM Trunking Narrowband Routing Entry Window . . . . . . . . . . . . . . . . . . . . . . . . . . 5-33

5-18 View ATM Trunking Data Channel Table Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-34

6-1 User Properties Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-2

6-2 Browse for Acrobat Reader Path Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-4

6-3 security.log.0 Log File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-6

6-4 config.log.0 Log File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-7

6-5 aqv Log File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-8

6-6 Root Window (Displaying Internet) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-16

6-7 Internet Window (Displaying PSAX Map) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-17

6-8 PSAX Symbol 172.26.41.83 (Displaying CPU Status Symbol) . . . . . . . . . . . . . . . . . . . . . . . . 6-18

6-9 The radius.properties File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-20

7-1 Sample Event Display Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-3

7-2 Log Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-4

7-3 Enhanced Trap Description Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-6

7-4 Enhanced Trap Description Window (Displaying Description) . . . . . . . . . . . . . . . . . . . . . . . . . 7-7

7-5 Trap Message Not Found Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-7

7-6 Save Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-8

7-7 Save Dialog Box (Displaying Menu) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-8

7-8 Find in Log Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-9

7-9 Find in Log Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-10

7-10 End of Log Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-10

7-11 Beginning of Log Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-10

7-12 Cut Confirmation Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-11

7-13 Delete Selection Confirmation Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-12

7-14 Trap Activation Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-13

7-15 Show Traps From Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-14

7-16 Trap Activation Page Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-15

7-17 Users Logged On Server Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-15

7-18 Client Shutdown Confirmation Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-167-16

7-15

7-15

7-14

7-13

7-12

7-11

7-10

7-10

7-10

7-9

7-8

7-8

7-7

7-7

7-6

7-4

7-3

6-20

6-18

6-17

6-16

6-8

6-7

6-6

6-4

6-2

5-34

5-33

5-32

5-31

5-30

5-26

5-24

5-24

5-23

5-22

5-14

5-13

5-10

xx 255-700-762R11.1


List of Figures

7-19 Error - Cannot Terminate Client Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-16

7-20 Force Unload Confirmation Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-17

7-21 Force Unload Complete Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-17

7-22 Example of Module with LED Status Indicators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-18

7-23 Port Status Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-19

7-24 Device Tree Status Indicators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-20

7-25 Active Alarm Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-23

7-26 Set Filters Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-27

8-1 PNNI Node Configuration Table Page (Displaying Menu) . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-2

8-2 PNNI Node Entry Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-5

8-3 PNNI Node PGL Configuration Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-9

8-4 PNNI Node Timer Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-12

8-5 PNNI Node SVCC Configuration Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-15

8-6 PNNI Scope Mapping Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-17

8-7 PNNI Route Address Table Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-19

8-8 ADD PNNI Route Address Entry Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-20

8-9 VIEW PNNI Route Address Entry Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-24

8-10 UPDATE PNNI Route Address Entry Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-24

8-11 PNNI Metrics Table Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-25

8-12 ADD PNNI Metrics Entry Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-26

8-13 VIEW PNNI Metrics Entry Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-29

8-14 PNNI Route TNS Table Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-30

8-15 ADD PNNI Route TNS Entry Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-31

8-16 PNNI Summary Address Table Window (Displaying an Entry) . . . . . . . . . . . . . . . . . . . . . . . . .8-35

8-17 ADD PNNI Summary Address Entry Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-36

8-18 PNNI Map Table Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-38

8-19 VIEW PNNI Map Link Entry Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-39

8-20 View PNNI Map Node Table Window (Displaying an Entry) . . . . . . . . . . . . . . . . . . . . . . . . . .8-41

8-21 VIEW PNNI Map Node Entry Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-42

8-22 View PNNI Map Address Table Window (Displaying Multiple Entries) . . . . . . . . . . . . . . . . . .8-45

8-23 PNNI Map Address Entry Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-45

8-24 View PNNI Map TNS Table Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-47

8-25 View PNNI Link Table Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-49

8-26 VIEW PNNI Link Entry Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-50

8-27 View PNNI Neighbor Peer Table Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-54

8-28 VIEW PNNI Neighbor Peer Entry Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-55

8-29 View PNNI Neighbor Peer Port Table Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-58

8-30 VIEW PNNI Neighbor Peer Port Entry Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-58

8-31 View PNNI PTSE Table Window (Displaying Multiple Entries) . . . . . . . . . . . . . . . . . . . . . . . . .8-60

8-32 VIEW PNNI PTSE Entry Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-60.8-60

.8-60

.8-58

.8-58

.8-55

.8-54

.8-50

.8-49

.8-47

.8-45

.8-45

.8-42

.8-41

.8-39

.8-38

.8-36

.8-35

.8-31

.8-30

.8-29

.8-26

.8-25

.8-24

.8-24

.8-20

.8-19

.8-17

.8-15

.8-12

.8-9

.8-5

.8-2

.7-27

.7-23

.7-20

.7-19

.7-18

.7-17

.7-17

.7-16

255-700-762R11.1 xxi


List of Figures

8-33 PNNI Statistics Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-63

9-1 PNNI SVCC RCC Security Configuration Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-2

9-2 View PNNI SvccRcc Table Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-6

9-3 PNNI SvccRcc Information Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-7

9-4 ATM Security Statistics - Routing SVC Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-9

9-5 Feature Turn On/Off Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-12

9-6 Feature Turn On/Off Page Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-12

9-7 Feature Turn On/Off Confirmation Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-13

9-8 Signaling PVC Page Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-14

9-9 Signaling PVC Stats Page Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-19

9-10 Signaling PVC Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-23

9-11 Signaling PVC Stats Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-28

9-12 Routing PVC Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-32

9-13 Routing PVC Stats Page Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-37

10-1 Diagnostics Tab (Displaying Diagnostics Page) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-2

10-2 CPU Status Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-3

10-3 Disk and Memory Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-5

10-4 Backplanes and Cell Bus Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-6

10-5 Cell Buffers and Message Pool Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-7

10-6 OAM Loopback Test Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-8

10-7 ADD OAM Loopback Table Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-8

10-8 OAM Activation - Deactivation Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-11

10-9 ADD OAM Activate & Deactivate Table Entry Window . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-11

10-10 Cell Test Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-18

10-11 RTD / CLM Table Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-21

10-12 ADD RTD / CLM Table Entry Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-22

10-13 ADD RTD / CLM Table Entry Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-26

10-14 Copy RTD / CLM Configuration Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-26

10-15 Module Connection Count Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-29

10-16 Restart Button . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-31

10-17 Restart Hardware Component Confirmation Window (Primary CPU Module) . . . . . . . . . . . 10-32

10-18 Restart Hardware Component Confirmation Window (An I/O Module) . . . . . . . . . . . . . . . 10-32

10-19 Switchover to Backup CPU Button . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-33

10-20 Switchover to Backup CPU Confirmation (Redundant PSAX Device) . . . . . . . . . . . . . . . . . 10-33

10-21 Switchover to Backup CPU Message Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-33

10-22 Remove Configuration Files Button . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-34

10-23 Remove Configuration Files Confirmation Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-34

10-24 System Maintenance Tab (Displaying the CPU Upgrade Page) . . . . . . . . . . . . . . . . . . . . . . 10-35

10-25 FTP System Files Panel (System Upgrade 100% Completed) . . . . . . . . . . . . . . . . . . . . . . . 10-39

10-26 Upgrade Done Successfully . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-3910-39

10-39

10-35

10-34

10-34

10-33

10-33

10-33

10-32

10-32

10-31

10-29

10-26

10-26

10-22

10-21

10-18

10-11

10-11

10-8

10-8

10-7

10-6

10-5

10-3

10-2

9-37

9-32

9-28

9-23

9-19

9-14

9-13

9-12

9-12

9-9

9-7

9-6

9-2

8-63

xxii 255-700-762R11.1


List of Figures

10-27 Upgrade System Software Panel (Displaying Upgrade Device Confirmation Window) . . . . .10-40

10-28 Save Configuration Files Confirmation Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10-40

10-29 Device Reboot Status Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10-41

10-30 Upgrade Status—Standby . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10-41

10-31 Upgrade Successfully Completed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10-41

10-32 Sample Fallback Confirmation Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10-42

10-33 Firmware Upgrade Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10-44

10-34 Firmware Upgrade Panel (Selecting Next Firmware Version) . . . . . . . . . . . . . . . . . . . . . . . .10-47

10-35 Firmware Upgrade Confirmation Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10-47

10-36 Backup Configuration Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10-49

10-37 Show Existing Configurations Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10-53

10-38 Remote Database Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10-55

10-39 Example of Profile File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10-58

10-40 Profiler Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10-59

10-41 Feature Turn On/Off Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10-60

10-42 Feature Turn On/Off Page Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10-60

10-43 Feature Turn On/Off Confirmation Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10-60

10-44 Special Features Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10-61

10-45 Bulk Statistics Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10-62



11-3 Feature Turn On/Off Confirmation Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11-2

11-4 GR-303 Interface Configuration Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11-7

11-5 GR303 System-Wide Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11-10

11-6 ADD GR303 IG Configuration Entry Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11-11

11-7 VIEW GR303 IG Configuration Entry Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11-17

11-8 UPDATE GR303 IG Configuration Entry Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11-18

11-9 ADD DS1 GR303IG Interface Configuration Entry Window . . . . . . . . . . . . . . . . . . . . . . . . .11-19

11-10 IG Statistics Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11-21

11-11 AAL2 Trunk Page (Displaying Menu) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11-24

11-12 ADD AAL2 Trunk Config Entry Window (Top) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11-25

11-13 ADD AAL2 Trunk Config Entry Window (Bottom) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11-25

11-14 Create Connection Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11-34

11-15 Create GR303 AAL2 PVC VCC Connection Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11-35

11-16 Listing Page with GR-303 AAL2 Entry Selected (Displaying Menu) . . . . . . . . . . . . . . . . . . . .11-40

11-17 Display Connection: GR303_AAL2_PVC_VCC Window . . . . . . . . . . . . . . . . . . . . . . . . . . . .11-40

12-1 Site-Specific Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12-2



12-4 Feature Turn On/Off Confirmation Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12-3.12-3

.12-3

.12-2

.12-2

.11-40

.11-40

.11-35

.11-34

.11-25

.11-25

.11-24

.11-21

.11-19

.11-18

.11-17

.11-11

.11-10

.11-7

.11-2

.11-2

.11-1

.10-62

.10-61

.10-60

.10-60

.10-60

.10-59

.10-58

.10-55

.10-53

.10-49

.10-47

.10-47

.10-44

.10-42

.10-41

.10-41

.10-41

.10-40

.10-40

255-700-762R11.1 xxiii


List of Figures

12-5 Call Control Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-4

12-6 Call Control Confirmation Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-4

12-7 Restart Button . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-5

12-8 Restart Hardware Component Confirmation Window (Primary CPUn Module) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-5

12-9 H.248 Configuration Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-6

12-10 H.248 Configuration Page (Displaying Menu) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-7

12-11 H.248 Transport and Resource Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-8

12-12 H.248 Congestion Handling Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-11

12-13 H.248 Tone Generation Detection Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-12

12-14 High-Density E1 Port and Channel Configuration Window . . . . . . . . . . . . . . . . . . . . . . . . 12-13

12-15 Slot Menu (Displaying H.248 Option) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-14

12-16 Terminal ID Configuration Window (Slot) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-15

12-17 Terminal ID Configuration Window (Port) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-17

12-18 Channel Configuration Menu (Displaying H.248 Option) . . . . . . . . . . . . . . . . . . . . . . . . . . 12-19

12-19 Terminal ID Configuration Window (Channel) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-20

13-1 H.248 Context Access Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-1

13-2 H.248 Termination Access Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-3

14-1 Site-Specific Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-2

14-2 Feature Turn On/Off Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-3

14-3 Feature Turn On/Off Page Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-3

14-4 Call Control Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-5

14-5 Special Features Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-12

14-6 Resources Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-13

14-7 V5 Dsp Over Subscription Table Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-16

14-8 V5 DSP Over Subscription Table Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-17

14-9 UPDATE V5 DSP Over Subscription Configuration Window . . . . . . . . . . . . . . . . . . . . . . . . 14-17

14-10 Interfaces Page (Displaying V5 Interface Configuration Table) . . . . . . . . . . . . . . . . . . . . . . 14-19

14-11 Interfaces Page (Displaying V5 Interface Configuration Table Menu) . . . . . . . . . . . . . . . . . 14-20

14-12 ADD V5 Interface Table Entry Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-20

14-13 VIEW V5 Interface Table Entry Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-21

14-14 UPDATE V5 Interface Table Entry Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-22

14-15 Variant Page (Displaying V5 Variant Configuration Table) . . . . . . . . . . . . . . . . . . . . . . . . . 14-24

14-16 Variant Page (Displaying V5 Variant Configuration Table Menu) . . . . . . . . . . . . . . . . . . . . 14-25

14-17 ADD V5 Variant Table Entry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-25

14-18 VIEW V5 Variant Table Entry Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-28

14-19 UPDATE V5 Variant Table Entry Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-29

14-20 View V5 Physical C Channel Table Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-32

14-21 V5 Physical C Channel Table Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-32

14-22 ADD V5 Physical C Channel Table Entry Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-33

14-23 VIEW V5 Interface Table Entry Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-3514-35

14-33

14-32

14-32

14-29

14-28

14-25

14-25

14-24

14-22

14-21

14-20

14-20

14-19

14-17

14-17

14-16

14-13

14-12

14-5

14-3

14-3

14-2

13-3

13-1

12-20

12-19

12-17

12-15

12-14

12-13

12-12

12-11

12-8

12-7

12-6

12-5

12-5

12-4

12-4

xxiv 255-700-762R11.1


List of Figures

14-24 UPDATE V5 Interface Table Entry Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14-36

14-25 View V5 E1 Link Table Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14-38

14-26 V5 E1 Link Table Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14-39

14-27 ADD V5 E1 Link Table Entry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14-39

14-28 View V5 Timeslot Channel Table Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14-42

14-29 V5 Timeslot Channel Table Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14-42

14-30 VIEW V5 E1 Link Table Entry Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14-43

14-31 UPDATE V5 E1 Link Table Entry Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14-44

14-32 View V5 Data Link Table Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14-47

14-33 V5 Data Link Table Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14-47

14-34 ADD V5 Data Link Table Entry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14-47

14-35 VIEW V5 Data Link Table Entry Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14-49

14-36 View V5 User Port Table Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14-53

14-37 V5 User Port Table Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14-53

14-38 ADD V5 User Port Entry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14-54

14-39 VIEW V5 User Port Entry Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14-59

14-40 UPDATE V5 User Port Entry Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14-60

14-41 V5 B Channels CID Table Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14-62

A-1 Unauthorized User Error Message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-3

A-2 Users Logged On Server Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-4

A-3 Client Shutdown Confirmation Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-4

A-4 Error - Cannot Terminate Client Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-5

A-5 Force Unload Confirmation Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-5

A-6 Force Unload Complete Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-5

A-7 Terminal Window (Displaying EMS-PSAX Software Version) . . . . . . . . . . . . . . . . . . . . . . . . A-11

A-8 Terminal Window (When EMS-PSAX Software Does Not Exist on This Workstation) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-11

A-9 Programs Menu (Displaying EMS-PSAX Menu Items) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-12

B-1 Sample Network Configuration With Firewall and Gatekeeper . . . . . . . . . . . . . . . . . . . . . . . .B-2

B-2 EMS-PSAX/NAT Environment Scenario . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .B-4

C-1 Data Collection & Thresholds: SNMP for phobos Window . . . . . . . . . . . . . . . . . . . . . . . . . . . C-2

C-2 Data Collection & Thresholds: SNMP for phobos Window (Displaying the Edit Menu) . . . . . . C-3

C-3 Data Collection & Thresholds / MIB Object Selection Window . . . . . . . . . . . . . . . . . . . . . . . . C-4

C-4 Data Collection & Thresholds / MIB Object Selection Window (Displaying Selection) . . . . . . . C-5

C-5 Add e1PortStatsCurrentESs Collection for phobos Window (Before Configuration) . . . . . . . . C-6

C-6 Add e1PortStatsCurrentESs Collection for phobos Window (After Configuration) . . . . . . . . . C-7

C-7 Data Collection & Thresholds: SNMP for phobos Window (Displaying the Edit Menu and Selection) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-8

C-8 Data Collection & Thresholds /MIB Object Selection Window (Displaying Selection) . . . . . . . . C-9

C-9 Data Collection & Thresholds: SNMP for phobos Window (Displaying File Menu) . . . . . . . . C-10

C-10 Data Collection & Thresholds / Show Data Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-11C-11

C-10

C-9

C-8

C-7

C-6

C-5

C-4

C-3

C-2

B-4

B-2

A-12

A-11

A-11

A-5

A-5

A-5

A-4

A-4

A-3

.14-62

.14-60

.14-59

.14-54

.14-53

.14-53

.14-49

.14-47

.14-47

.14-47

.14-44

.14-43

.14-42

.14-42

.14-39

.14-39

.14-38

.14-36

255-700-762R11.1 xxv


List of Figures

C-11 Openview Grapher Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-12C-12

xxvi 255-700-762R11.1


List of Tables

1-1 Text Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-3

1-2 Button Description Table Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-4

1-3 Selecting Multiple Menu Options or Buttons in Succession . . . . . . . . . . . . . . . . . . . . . . . . . . .1-5

1-4 How Fields Are Displayed in the EMS-PSAX GUI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-6

1-5 Shortcut Keys for Navigating the EMS-PSAX GUI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-6

2-1 LED/Port Indicators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-4

2-2 Adding Server IP Addresses to SNMP Manager List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-7

3-1 Field Descriptions for the Add/Update Device Dialog Window . . . . . . . . . . . . . . . . . . . . . . . . .3-5

3-2 EMS-PSAX System Operation When Opening a Device . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-11

3-3 Field Descriptions for the Create New User and Update User Information Windows . . . . . . .3-13

3-4 Field Descriptions for the Open SNMPv3 Device Window . . . . . . . . . . . . . . . . . . . . . . . . . . .3-23

3-5 Modifying User Access Privileges for Network Partitioning . . . . . . . . . . . . . . . . . . . . . . . . . .3-28

3-6 Selecting Users and Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-29

3-7 User Access on the Update Device Dialog Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-30

3-8 User Access List Confirmation Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-31

3-9 File Menu Option Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-35

3-10 View Menu Option Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-37

3-11 Help Menu Option Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-38

3-12 Descriptions for the Device Window Menu Bar Options . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-43

3-13 EMS-PSAX Windows and Subwindows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-45

4-1 Site-Specific Tab Options Not Documented in This Chapter . . . . . . . . . . . . . . . . . . . . . . . . . . .4-1

4-2 Panel Descriptions for the Site-Specific Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-3

4-3 Stratum Configuration Window Field Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-10

4-4 System Identification Panel on the Site-Specific Configuration Window Field Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-18

4-5 System Date and Time Panel on the Site-Specific Configuration Window Field Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-20

4-6 TCP Server Configuration Window Field Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-23

4-7 System Related Data Panel on the Site-Specific Configuration Window Field Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-24

4-8 Master ATM Address and OAM Related Data Panel on the Site-Specific Configuration Window Field Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-27

4-9 Notify and Target Address Table Entry Window Field Descriptions . . . . . . . . . . . . . . . . . . . . .4-29

4-10 Feature Turn On/Off Page Field Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-33

4-11 Call Control Page Field Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-36

4-12 PSAX System Performance Capabilities Per Node for Release 11.1.0 . . . . . . . . . . . . . . . . . . .4-41

4-13 ADD Interface Protection Group Window Field Descriptions . . . . . . . . . . . . . . . . . . . . . . . . .4-44.4-44

.4-41

.4-36

.4-33

.4-29

.4-27

.4-24

.4-23

.4-20

.4-18

.4-10

.4-3

.4-1

.3-45

.3-43

.3-38

.3-37

.3-35

.3-31

.3-30

.3-29

.3-28

.3-23

.3-13

.3-11

.3-5

.2-7

.2-4

.1-6

.1-6

.1-5

.1-4

.1-3

255-700-762R11.1 xxvii


List of Tables

4-14 ADD Interface Protection Entry Window Field Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . 4-48

4-15 Deleting an Interface Protection Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-52

4-16 IP Throttling Configuration Page Field Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-54

4-17 ADD N to M Protection Group Table Entry Window Field Descriptions . . . . . . . . . . . . . . . . . 4-60

4-18 Deleting an N to M Protection Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-63

4-19 N to M Protection Table Window Field Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-64

4-20 N to M Protection Configuration Window Field DescriptionsN to M Protection Table Panel Field Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-66

5-1 ATM Trunking Page Field Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-4

5-2 ADD ATM Trunking Remote Entry Window Field Descriptions . . . . . . . . . . . . . . . . . . . . . . . . 5-7

5-3 ADD ATM Trunking Sig VCC Entry Window Field Descriptions . . . . . . . . . . . . . . . . . . . . . . 5-10

5-4 ATM Trunking Bearer VCC Entry Window Field Descriptions . . . . . . . . . . . . . . . . . . . . . . . . 5-14

5-5 ATM Trunking Bearer VCC Profile Configuration Window Field Descriptions . . . . . . . . . . . . 5-25

5-6 ATM Trunking Bearer VCC Parameters Window Field Descriptions . . . . . . . . . . . . . . . . . . . 5-27

5-7 ADD ATM Trunking Broadband Routing Entry Window Field Descriptions . . . . . . . . . . . . . . 5-31

5-8 ADD ATM Trunking Narrowband Routing Entry Window Field Descriptions . . . . . . . . . . . . . 5-33

6-1 Panel Descriptions for the User Properties Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3

6-2 Configurable EMS-PSAX Attributes in the aqv File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-9

6-3 PSAX Symbol Color Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-19

6-4 Field Descriptions for the RADIUS Properties File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-21

7-1 Menu Options for the Log Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-4

7-2 Field Descriptions for the Find in Log Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-10

7-3 Trap Activation Table Window Field Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-14

7-4 LED Status Indicator Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-18

7-5 Port Status Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-20

7-6 Removing Ghosted Modules from the Front Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-21

7-7 CPU Status Symbol Characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-22

7-8 Active Alarm Status Table Window Field Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-23

7-9 Active Alarm Status Table Window Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-24

7-10 Menu Options for the Active Alarm Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-26

7-11 Set Filters Window Field Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-27

8-1 PNNI Page Menu Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-2

8-2 PNNI Node Entry Window Field Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-6

8-3 PNNI Node PGL Configuration Window Field Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . 8-9

8-4 PNNI Node Timer Configuration Window Field Descriptions . . . . . . . . . . . . . . . . . . . . . . . . 8-13

8-5 PNNI Node SVCC Configuration Window Field Descriptions . . . . . . . . . . . . . . . . . . . . . . . . 8-15

8-6 PNNI Scope Mapping Configuration Window Field Descriptions . . . . . . . . . . . . . . . . . . . . . 8-18

8-7 PNNI Route Address Entry Window Field Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-21

8-8 PNNI Metrics Entry Screen Field Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-27

8-9 ADD PNNI Route TNS Entry Window Field Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-31

8-10 PNNI Summary Address Entry Window Field Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . 8-378-37

8-31

8-27

8-21

8-18

8-15

8-13

8-9

8-6

8-2

7-27

7-26

7-24

7-23

7-22

7-21

7-20

7-18

7-14

7-10

7-4

6-21

6-19

6-9

6-3

5-33

5-31

5-27

5-25

5-14

5-10

5-7

5-4

4-66

4-64

4-63

4-60

4-54

4-52

4-48

xxviii 255-700-762R11.1


List of Tables

8-11 PNNI Map Link Entry Window Field Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-39

8-12 PNNI Map Node Information Window Field Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-42

8-13 PNNI Map Address Information Window Field Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . .8-46

8-14 PNNI Map TNS Table Window Field Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-47

8-15 PNNI Map TNS Configuration Window Field Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . .8-48

8-16 PNNI Link Entry Window Field Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-50

8-17 PNNI Neighbor Peer Entry Window Field Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-55

8-18 PNNI Neighbor Peer Port Entry Window Field Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . .8-59

8-19 PNNI PTSE Entry Window Field Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-61

8-20 PNNI Statistics Window Field Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-64

9-1 ATM PNNI SVCC RCC Security Configuration Window Field Descriptions . . . . . . . . . . . . . . . .9-3

9-2 PNNI SVCC RCC Information Window Field Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-7

9-3 ATM PNNI SVCC RCC Security Statistics Window Field Descriptions . . . . . . . . . . . . . . . . . . .9-10

9-4 ATM UNI Interface ATM Security Signaling PVC Configuration Page Field Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-15

9-5 ATM UNI Interface ATM Security Statistics - Signaling PVC Window Field Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-20

9-6 ATM PNNI Interface ATM Security Configuration - Signaling PVC Page Field Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-24

9-7 ATM PNNI Interface ATM Security Statistics - Signaling PVC Window Field Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-29

9-8 ATM PNNI Interface ATM Security Configuration - Routing PVC Page Field Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-33

9-9 ATM PNNI Interface ATM Security Statistics - Routing PVC Page Field Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-38

10-1 Page/Panel Descriptions for the Diagnostics Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10-1

10-2 CPU Status Panel Field Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10-4

10-3 Field Descriptions for the Disk and Memory Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10-6

10-4 Field Descriptions for the Backplanes and Cell Bus Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . .10-7

10-5 Field Descriptions for the Cell Buffers and Message Pool Panel . . . . . . . . . . . . . . . . . . . . . . .10-7

10-6 OAM Loopback Window Field Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10-9

10-7 OAM Activation-Deactivation Window Field Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . .10-12

10-8 Connection Interface Panel Field Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10-20

10-9 Cell Test Statistics Panel Field Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10-20

10-10 RTD / CLM Table Entry Window Field Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10-23

10-11 Copy RTD / CLM Configuration Window Field Descriptions . . . . . . . . . . . . . . . . . . . . . . . .10-27

10-12 Module Connection Count Table Window Field Descriptions . . . . . . . . . . . . . . . . . . . . . . .10-30

10-13 Field Descriptions for the Restart Hardware Components Panel . . . . . . . . . . . . . . . . . . . . . .10-31

10-14 CPU Upgrade Page Panel Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10-36

10-15 Field Descriptions for the FTP System Files Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10-37

10-16 Field Descriptions for the Upgrade System Software Panel . . . . . . . . . . . . . . . . . . . . . . . . .10-37

10-17 Firmware Upgrade Panel Field Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10-45.10-45

.10-37

.10-37

.10-36

.10-31

.10-30

.10-27

.10-23

.10-20

.10-20

.10-12

.10-9

.10-7

.10-7

.10-6

.10-4

.10-1

.9-38

.9-33

.9-29

.9-24

.9-20

.9-15

.9-10

.9-7

.9-3

.8-64

.8-61

.8-59

.8-55

.8-50

.8-48

.8-47

.8-46

.8-42

.8-39

255-700-762R11.1 xxix


List of Tables

10-18 Field Descriptions for the Backup Configuration Window . . . . . . . . . . . . . . . . . . . . . . . . . 10-50

10-19 Scheduled Backup Configuration Confirmation Window . . . . . . . . . . . . . . . . . . . . . . . . . . 10-52

10-20 Remote Database Page Field Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-55

10-21 Bulk Statistics Window Field Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-62

11-1 Feature Turn On/Off Page Field Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-3

11-2 Values to Choose for the DSP2x Voice Server Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-4

11-3 DS1 Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-6

11-4 GR303 Interface And DS0 Configuration Window Field Descriptions . . . . . . . . . . . . . . . . . . 11-8

11-5 GR- 303 Interface Group Configuration Window Field Descriptions . . . . . . . . . . . . . . . . . . 11-12

11-6 DS1 GR303 Interface Configuration Entry Window Field Descriptions . . . . . . . . . . . . . . . . 11-20

11-7 GR303IG Statistics Window Field Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-21

11-8 Performing an Action on an Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-22

11-9 Enabling or Disabling Traps Decision Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-23

11-10 AAL2 Trunk Config Entry Window Field Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-26

11-11 Display Connection: GR303_AAL2_VCC_PVC Window Field Descriptions . . . . . . . . . . . . . 11-35

12-1 Buttons for the H.248 Configuration Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-7

12-2 H.248 Management and Configuration Window Commands . . . . . . . . . . . . . . . . . . . . . . . 12-7

12-3 H.248 Transport and Resource Window Field Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . 12-9

12-4 H.248 Congestion Handling Window Field Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . 12-11

12-5 H.248 Tone Generation and Detection Window Field Descriptions . . . . . . . . . . . . . . . . . . 12-13

12-6 Buttons for the Terminal ID Configuration (Slot) Window . . . . . . . . . . . . . . . . . . . . . . . . . 12-15

12-7 Termination ID Configuration (Slot) Window Field Descriptions . . . . . . . . . . . . . . . . . . . . . 12-16

12-8 Buttons for the Terminal ID Configuration (Port) Window . . . . . . . . . . . . . . . . . . . . . . . . . 12-18

12-9 Termination ID Configuration (Port) Window Field Descriptions . . . . . . . . . . . . . . . . . . . . . 12-18

12-10 Termination ID Configuration (Channel) Window Field Descriptions . . . . . . . . . . . . . . . . . 12-21

13-1 Buttons for the H.248 Context Access Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-1

13-2 H.248 Context Access Window Field Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-2

13-3 H.248 Termination Access Window Field Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-3

14-1 Call Control Page Field Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-6

14-2 Resources Page Field Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-14

14-3 V5 DSP Over Subscription Table Window Field Descriptions . . . . . . . . . . . . . . . . . . . . . . . . 14-18

14-4 ADD V5 Interface Table Entry Window Field Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . 14-21

14-5 Deleting a V5.2 Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-23

14-6 ADD V5 Variant Entry Window Field Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-26

14-7 Deleting a V5.2 Variant . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-30

14-8 V5 Physical C Channel Configuration Window Field Descriptions . . . . . . . . . . . . . . . . . . . 14-34

14-9 Deleting a V5.2 Physical C Channel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-37

14-10 V5 E1 Link Configuration Window Field Panel Field Descriptions . . . . . . . . . . . . . . . . . . . . 14-40

14-11 V5 E1 Interface Configuration Panel Field Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-40

14-12 Performing Actions on Timeslot Channels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-4114-41

14-40

14-40

14-37

14-34

14-30

14-26

14-23

14-21

14-18

14-14

14-6

13-3

13-2

13-1

12-21

12-18

12-18

12-16

12-15

12-13

12-11

12-9

12-7

12-7

11-35

11-26

11-23

11-22

11-21

11-20

11-12

11-8

11-6

11-4

11-3

10-62

10-55

10-52

10-50

xxx 255-700-762R11.1


List of Tables

14-13 Deleting a V5.2 E1 Link . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14-45

14-14 V5 Data Link Configuration Window Field Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . .14-48

14-15 Deleting a V5.2 Data Link . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14-50

14-16 V5 User Port Table Entry Window Field Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14-55

14-17 Deleting a V5.2 User Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14-61

14-18 V5 B Channel CID Table Window Field Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14-62

A-1 Enabling Client and Server Connectivity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-2

B-1 Setting Up Network Components for Firewall Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .B-2

B-2 Firewall Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .B-3B-3

B-2

A-2

.14-62

.14-61

.14-55

.14-50

.14-48

.14-45

255-700-762R11.1 xxxi


List of Tables

xxxii 255-700-762R11.1


1 Getting Started

Purpose of This GuideThe Navis® EMS-PSAX User Guide for the Client/Server Application provides a description of the EMS-PSAX element management system (EMS). It also provides information about using the EMS-PSAX to:

• Configure basic system parameters and manage the EMS-PSAX system

• Configure PNNI, ATM trunking, V5.2, and other system-wide functions

• Run system diagnostics

• Upgrade system software

• Access system trap definitions

• Configure and manage PacketStar PSAX Multiservice Media Gateway sys-tems (PSAX devices) using the EMS-PSAX

• Understand the EMS-PSAX functions and features

• Troubleshoot the EMS-PSAX

You must install and launch the EMS-PSAX before using it to configure and manage PSAX devices. For information about installing the client/server application, see the Navis® EMS-PSAX Quick-Start Guide for the Client/Server Application.

Audience For This Guide

The information in this guide is intended for people who will use the EMS-PSAX Release 11.1.0 system software to configure and manage Packet-Star Multiservice Media Gateways (PSAX devices).

What You Should KnowBefore you use this document or operate a PSAX system, you should already understand and have experience with the following:

• Configuration of the PSAX device

• The Solaris operating system

• The Windows XP/2000 operating system

• HP OpenView Network Node Manager (NNM)

• How to navigate the EMS-PSAX Device window

• How to use the Device Tree

• General network management practices


255-700-762R11.1 1-1

Chapter 1 Getting StartedLucent Technologies Information Products

Lucent Technologies Information Products

Product Information Library

To install and configure the PSAX system, you need to read the publications provided on your Lucent Technologies Navis® EMS-PSAX Software/Product Information Library CD-ROM.

Printed Documents

For your convenience, many of the documents included on the PacketStar® PSAX Multiservice Media Gateways Product Information Library CD-ROM are also available in printed form. You can order these documents through the Lucent Technologies Customer Information Center Web site at: http://www.lucentdocs.com.

Other Publications

Numerous books are currently available on the subject of basic telecommuni-cations technology and specific protocols. In addition to such general reading, you should also be familiar with appropriate industry standards and specifications.

About Lucent Technologies

History

Lucent Technologies is the communications systems and technology com-pany formed through the restructuring of AT&T. We bring with us a tradition of more than 125 years of experience and a dedication to superior customer service.

Lucent Technologies manufactures, sells, and services a complete line of cus-tomer premises communications units, and commercial and multimedia communications and messaging systems designed and supported by our research and development unit, Bell Laboratories.

Our legacy and our spirit of innovation allow Lucent to provide our custom-ers with the tools needed to communicate effectively, any time and any-where, and to integrate the latest technologies into real-life solutions that help make business work.

1-2 255-700-762R11.1


Chapter 1 Getting StartedText Conventions

For More Information

To learn more about the PacketStar PSAX family of Multiservice Media Gate-ways and the complete line of Lucent Technologies products, visit our Web site at http://www.lucent.com.

Text Conventions

Text Types Used in This Document

This guide uses a different typeface to denote text displayed on console inter-face windows and equipment, as well as data you enter. Table 1-1 shows how each typographical convention is used.

Icons and Symbols

Standard icons and symbols to alert you to dangers, warnings, cautions, and notes are described as follows:

! DANGER:Warnings for a personal injury hazard are identified by this format.

WARNING:!Warnings relating to risk of equipment damage or failure are identified by this format.

Table 1-1. Text Conventions

Appearance How it is used

SANS SERIF BOLD, ALL CAPS Labels on module panels, chassis face-plates, or other hardware

Fixed-width normal Message text displayed on the user inter-face window

Serif bold • Button name (GUI interface) or com-mand name (console interface) on the user interface window

• Literal text for values that the user types in fields or selects from predefined sets of values for fields

• Commands or literal argument values

Fixed-width bold System prompt displayed on the user interface window

Serif italics • A variable name or string for which you will substitute your own information

• An argument or parameter on a com-mand line for which you will substitute your own information

255-700-762R11.1 1-3


http://www.lucent.com


! CAUTION:Warnings relating to risk of data loss or other general precautionary notes are identified by this format.

Note: Identifies additional information pertinent to the text preceding this note.

Use of Button Description Tables

All illustrations for configuration windows in this guide for the EMS-PSAX interface are followed by a command or button description table describing the button functions displayed on the window. You should read all the infor-mation in the button description table, especially when first using a window, because these descriptions may have special instructions or configuration constraints provided in the Function column by use of the Note: text conven-tion (see Table 1-2).

Use of Field Description Tables

For all illustrations for configuration windows in this guide for the EMS-PSAX, the field description tables normally follow the command description tables. Field description tables define the editable and the display-only fields, their functions, valid values, and constraints, if applicable. As in the command description tables, the Note: text convention is also used, where appropriate, in the field description tables to alert the user to special instructions or configuration constraints (see Figure 1-1).

Table 1-2. Button Description Table Example

Button Function

Bring All Interfaces Into Service

Brings the out-of-service configured interfaces to in-service status.

Note: In GR-303 configuration, it is critical to bring into service only those channels actively configured with DS1 ports.

1-4 255-700-762R11.1



Selecting Menu Options and Fields in the EMS-PSAX GUI

Follow these guidelines to select a menu option or field in the EMS-PSAX GUI windows and to navigate through the windows:

• For EMS-PSAX procedures, instructions using the term “click” mean to press the left mouse button, and instructions using the term “right-click” mean to press the right mouse button. (If you have a mouse with three buttons, you will not need to use the middle mouse button to do any func-tions with the EMS-PSAX GUI.)

• When multiple menu options are displayed in a procedural step, select the menu options or click the appropriate buttons in succession as described in Table 1-3.

Figure 1-1. Field Description Table Example

Field Name Field Values Description

Interface Type Default: 0Range: 0-22Format: Numeric

Specifies the type of end-to-end connection protocol that governs the transmission parametersfor this configured port and channel interface.Note: When certain types of interfaces are select-ed in this field, other configuration fields are dis-played on this window.

Identifies editable fieldsor display-only fields onscreens

Identifies initial fieldvalue default

Describes the function of the fieldand special instructions forconfiguring modules

Identifies availablerange for field valuewhen applicable

Identifies field value format asNumeric, Predefined Alphanumeric, Hexadecimal, or Valid Dotted Quad.

Decribes special instructions orconfiguration constraints

Table 1-3. Selecting Multiple Menu Options or Buttons in Succession

If you encounter a step in a procedure to select multiple...

then do this..

menu options in succession, such as the step “Select Start > Programs.”

Using the left mouse button:

a Click the Start menu option

b Click the Programs menu option

buttons in succession, such as the step, “Click Apply > Close.”

Using the left mouse button:

a Click the Apply button.

b Click the Close button.

255-700-762R11.1 1-5


Chapter 1 Getting StartedTechnical Support

• Field values are displayed in three ways. To select a field, do one of the fol-lowing methods to enter the desired values into the fields on a window in the EMS-PSAX GUI as described in Table 1-4.

• To quickly select menu options from the EMS-PSAX Menu Bar, you can also simultaneously press keyboard combinations as described in Table 1-5.

Technical Support

If you experience a problem with the EMS-PSAX, refer to the troubleshoot-ing appendix, Appendix A. If the problem remains unresolved thereafter, refer to the Limited Software Warranty, which accompanied the EMS-PSAX product shipment, for instructions on obtaining support in your area.

Before You BeginBefore you install and use the EMS-PSAX to manage PSAX devices, be sure you:

• Plan the PSAX management network

Table 1-4. How Fields Are Displayed in the EMS-PSAX GUI

For a field displayed as... do this...

a combo box (it displays with a small triangle pointing downward)

select the displayed value and a drop-down list will appear with additional values.

a blank box enter a valid value in the field by typing it.

grey view the information, which is read-only. You cannot edit values that display as grey in the EMS-PSAX GUI.

Table 1-5. Shortcut Keys for Navigating the EMS-PSAX GUI

If you want to... press...

display the File menu on the EMS-PSAX Menu Bar Alt+F

display the View menu on the EMS-PSAX Menu Bar Alt+V

display the Help menu on the EMS-PSAX Menu Bar Alt+H

display the Open Device window Ctrl+O

display the Run Script window Ctrl+C

display the User List window Ctrl+U

display the Device List window Ctrl+D

display the Users Logged On Server window Alt+L

display the User Properties window Ctrl+P

terminate the EMS-PSAX session Alt+X and Alt+F4

1-6 255-700-762R11.1


Chapter 1 Getting StartedPlanning the PSAX Management Network

• Install the PSAX system according to the appropriate PacketStar PSAX Mul-tiservice Media Gateway user guide

• Check that you have met the system requirements for the EMS-PSAX (see Chapter 3)

• Back up your HP OpenView NNM databases

• Unload the PSAX MIB (ac120.my or v1Ac120) from HP OpenView NNM

• Remove the PSAX Event Categories and trap definitions from HP OpenView NNM

Take note of the following points before using the EMS-PSAX to manage the PSAX device:

• The PSAX device must be accessible either through in-band or out-of-band management connections, to access the device using the EMS-PSAX.

• The PSAX device must be assigned an IP address and IP mask, through the serial console port.

• PSAX devices must be configured to direct traps to the EMS-PSAX server so that the EMS-PSAX will function properly.

• Ensure that the management workstation receives traps.

Planning the PSAX Management NetworkBefore you install and use the EMS-PSAX, you should plan the PSAX man-agement network. You can use in-band or out-of-band management to pro-vide IP connectivity between the PSAX and the NMS, as described below.

Out-of-band management—This method may be used to connect the PSAX via the CPU Ethernet port to an existing IP network that connects your site to the NMS. The network configuration will depend on your site’s data commu-nication network topology. PSAX devices may be in the same IP subnet as your NMS, or in a remote subnet. Refer to the appropriate PacketStar® PSAX Multiservice Media Gateway user guide for instructions on how to configure the switch IP address, CPU IP address, and default gateway address.

In-band management—This method may be used to connect the PSAX via an IP-over-ATM PVC or SVC using the same facilities as your ATM traffic. Refer to the PacketStar® PSAX Connections Provisioning Guide for instructions on how to configure in-band management IP interfaces and routing on the PSAX device.

PSAX devices that have other devices attached to them through in-band management must have at least a T1 connection (or equivalent) along the entire length between themselves and the router from their network to the routing network. PSAX devices that have no other devices connected to them through in-band management must have at least 256 Kbps dedicated throughput to the routing network, since network congestion and latency could affect EMS-PSAX client response times.

The local management network includes the EMS-PSAX server and all EMS-PSAX clients on the same network as the server. This network is con-nected through a router to the remote management network. The remote management network contains management stations running the

255-700-762R11.1 1-7


Chapter 1 Getting StartedComments on This Guide

EMS-PSAX client. The osagent process must be running on the local manage-ment network; it is recommended that osagent runs on the EMS-PSAX server.

Comments on This GuideTo comment on the Navis® EMS-PSAX User Guide for the Client/Server Applica-tion, please complete the comment card at the following web address: http://www.lucent-info.com/comments/

You can also email your comments to [email protected].

Include the following information:

Title: Navis® EMS-PSAX User Guide for the Client/Server ApplicationRelease number: Release 11.1.0Document number: 255-700-762R11.1Issue number: Issue 1Publication date: July 2006

1-8 255-700-762R11.1


http://www.lucent-info.com/comments/

mailto: [email protected]

2 EMS-PSAX Overview

The Navis® EMS-PSAX (formerly known as the Navis® AQueView® Element Management System) is a GUI-based element management tool that is used to provision the Navis PSAX 1000, PSAX 1250, PSAX 2300, and PSAX 4500 systems. The EMS-PSAX application enables a network of PSAX devices to be managed and provisioned from a single location, using easy-to-use windows. The EMS-PSAX application also provides centralized configuration, diagnos-tic, performance, and security management of PSAX systems.

Navis® EMS-PSAX adds support for all of the features added in PSAX Release 11.1.0. In addition, GUI enhancements were made to align Navis® EMS-PSAX with other management tools offered by Lucent. Please refer to the Navis® EMS-PSAX Release 11.1.0 Release Note for additional details.

Managing PSAX Devices with the EMS-PSAXThe EMS-PSAX works on the element management level to enable you to:

• Configure individual PSAX devices and the individual modules in the sys-tems

• View and manage faults that occur in the PSAX devices by:

~ Viewing the LED indicators

~ Viewing Device Tree indicators and Front Panel view port indicators

~ Viewing traps in the Log tab

• Monitor real-time statistics and system performance

• Manage access to the devices through user IDs and passwords

Managing the PSAX Configuration

With its GUI, the EMS-PSAX enables you to easily configure and provision your PSAX network elements from a central management station or multiple management workstations.

Monitoring System Faults

The EMS-PSAX enables fault management for PSAX devices that are man-aged by the EMS-PSAX by:

• Changing the color of the status indicators on the Front Panel and Device Tree (For more information, see "Obtaining Port and Interface Data" in Chapter 6.)

• Displaying trap messages for individual PSAX network elements on the top message bar and viewing later in the Log tab. Traps are shown only for the PSAX devices that the EMS-PSAX is currently managing. For more infor-mation, see "Fault Monitoring" in Chapter 6.


255-700-762R11.1 2-1

Chapter 2 EMS-PSAX OverviewOperating the EMS-PSAX

Monitoring Real-Time Statistics and System Performance

The EMS-PSAX enables you obtain usage performance statistics. You can use these statistics to evaluate PSAX diagnostic information.

The EMS-PSAX also features a Diagnostics tab that provides system perfor-mance data, such as the amount of currently available memory and CPUn utilization.

For more information on performance data, see Chapter 6.

Managing Security

The EMS-PSAX provides security that restricts the accessibility of EMS-PSAX features, based on your user identification and password. The EMS-PSAX has three security levels, which consist of different access privileges:

• Administrator—read-write and user and device registration privileges

• Configurator—read-write access to the PSAX device and Device List; no access to User List

• Monitor—read-only privileges to the PSAX device and read-only access to the Device List; no access to User List

Access to particular PSAX devices also depends upon matching read-write community names that are configured on the target PSAX devices. EMS-PSAX Administrator users specify the community name of a PSAX device when adding the devices to the EMS-PSAX Device List. You must identify the community name of the device only when opening a PSAX device from the Open Device window. The community name of a PSAX device can be changed only by accessing the PSAX device through the serial port on the primary CPUn module (labeled CONSOLE).

For more information on managing security, see the appropriate Navis® EMS-PSAX Management System Quick-Start Guide.

Operating the EMS-PSAXAfter launching the EMS-PSAX, a logon window appears, prompting you to enter your username and password. After logging into the EMS-PSAX sys-tem, the Main EMS-PSAX window opens and displays the Device List win-dow (see Figure 3-1). For instructions on opening a device, see Chapter 3.

2-2 255-700-762R11.1


Chapter 2 EMS-PSAX OverviewOperating the EMS-PSAX

After opening a device, the device is displayed in the Device window of the Main EMS-PSAX window (see Figure 2-1). The Device window appears, dis-playing the Front Panel tab.

Front Panel

The Front Panel page displays all slots, including I/O, server, and common equipment modules that are seated in the open PSAX device, and empty slots where modules are absent. By clicking one of the tabs displayed across the top of the Device window, different pages appear to enable you to configure the modules, monitor hardware and software performance statistics, and change parameters for the displayed PSAX device.

LED/Port Indicators

Each module in the Front Panel window displays the ports and LED indica-tors, which indicate the current status of the hardware. The various status levels are indicated by the different colors of the ports and LEDs. These indi-cators show whether a port is configured, is in service, or has an alarm condi-tion. Table 2-1 describes the various status levels of the EMS-PSAX ports and LEDs.

Figure 2-1. Device Window

255-700-762R11.1 2-3


Chapter 2 EMS-PSAX OverviewClient/Server Architecture

For more information on LEDs and fault management, see Chapter 6.

Client/Server ArchitectureIn a client/server architecture, the server functions as the high-end com-puter, which processes data and applications that are shared by all users of the network. The client is the user’s personal computer that is used to access the network and run other applications.

CORBA Client/Server Model

The EMS-PSAX client/server application is based on the CORBA interface, allowing communication with network-level management systems and other OSSs. The Visibroker 5.2 component of EMS-PSAX Release 11.1.0 is CORBA 2.4-compliant.

Table 2-1. LED/Port Indicators

LEDs and Ports Colors

Alarm Status

Blue The port is normal and none of the interfaces are config-ured.

Sky Blue The port is normal. One or more interfaces are configured but both their Admin Status and Oper Status are out-of-service.

Green The port is normal. The Admin Status and the Oper Status of all the configured interfaces are in-service.

Yellow The port has some minor alarm condition.

Orange The port has some major alarm conditions like Loss Of Signal or Loss Of Frame. Also, when this happens for one or more interfaces, the Admin Status is in-service but the Oper Status is out-of-service.

Red The port is down and critical.

2-4 255-700-762R11.1


Chapter 2 EMS-PSAX OverviewSimple Network Management Protocol (SNMP)

The CORBA client/server model provides flexible approach to developing dis-tributed applications. The EMS-PSAX client and server communicate with each other using CORBA, while the EMS-PSAX server communicates with the PSAX devices using SNMP (see Figure 2-2). For more information about how SNMP is used in the EMS-PSAX, see Chapter 6.

Within this CORBA model, the client and server communicate through the CORBA IDL. Because of this separation, developers can change the way a server accomplishes a task without affecting how the client application asks the server application to accomplish the task.

Client/Server Applications

The CORBA model allows client applications to make requests to server applications, and to receive responses from them without direct knowledge of the information source or its location.

The CORBA IDL can serve as a northbound interface from the EMS-PSAX server, enabling integration of EMS-PSAX with higher-level management systems for functions such as flow-through provisioning.

Simple Network Management Protocol (SNMP)The PSAX system software features a SNMP-compliant MIB, which gives external management systems, such as HP OpenView NNM, SunNet Man-ager, or the customized EMS-PSAX, access to the system software that is loaded on the CPUn module of each PSAX device. The Internet Activities Board defined SNMP to provide a simple low-bandwidth protocol to carry management and provisioning information.

The management station monitors network nodes by reading management variables. The management station can also control the network elements by writing to management variables.

Previous versions of EMS-PSAX software support community-based SNMPv2c to monitor and manage PSAX devices. Beginning with Release 11.1.0, the EMS-PSAX also supports User Security Model (USM) SNMPv3, the secure version of SNMP, as described in Chapter 3.

Figure 2-2. Sample EMS-PSAX Client/Server Configuration

EMS-PSAXClient

EMS-PSAXServer

PSAX 1250

PSAX 1250

SNMP

SNMP

CORBA

255-700-762R11.1 2-5



SNMPv3 support enables users to have authenticated and encrypted commu-nication between SNMPv3-enabled PSAX devices and the EMS-PSAX server. The EMS-PSAX server can be configured to maintain the list of authenticated users, and allows creation of USM users for multiple PSAX devices per EMS-PSAX user (e.g., MONITOR1, CONFIG1). This feature restricts the access of authenticated devices to only those USM users, which have been created for a specific EMS-PSAX user, thus improving network partitioning and user access control.

Managing SNMPv3 devices is not supported when the EMS-PSAX is inte-grated with the NavisCore system.

Note: Trap and Inform users are created differently in the EMS-PSAX Cli-ent/Server and Standalone applications:

• EMS-PSAX server with NNM: Trap and Inform users are created in /etc/srconf/mgr/mgr.cnf, not within the EMS-PSAX.

• EMS-PSAX Standalone application: Trap and Inform users are created in the EMS-PSAX SNMPv3 Device List.

SNMP MIB

The SNMP MIB describes objects that are anticipated to be implemented by managed nodes running the Internet suite of protocols. The SNMP MIB pro-vides an extensive series of configuration management and provisioning fea-tures that allow the user to prepare the various components for supporting services.

SNMP Traps

Once the EMS-PSAX is launched, it polls the PSAX device to obtain its cur-rent configuration. Every time a change occurs in the device, a message about the event, which is called an SNMP trap, is sent from the PSAX device to the EMS-PSAX server, which relays it to registered management stations specified on the Site-Specific page. A trap message about the event is dis-played on the Log page.

An SNMP agent is the interface that enables a device to communicate with other SNMP devices. On the Site-Specific page, the agent for a PSAX device can be configured to send SNMP messages to your management station with-out a specific request.

Note: To retrieve and modify MIB information through an SNMP agent, you must directly access the software loaded on the CPUn module of the PSAX device itself, either through the console user interface or an SNMP-based manager, such as the EMS-PSAX.

Designating SNMP Trap Recipients

The IP address for your management station must be designated as an SNMP trap recipient in the PSAX device that you are managing with the EMS-PSAX. Otherwise, no trap messages will be received and the EMS-PSAX will not function properly.

2-6 255-700-762R11.1



If the PSAX device does not have the IP address of the EMS-PSAX server in its trap destination list, then the EMS-PSAX will prompt you to add it auto-matically (see Figure 2-3 and Table 2-2).

If the SNMP manager list is full, the following message appears (see Figure 2-4). You must manually add the IP address of the EMS-PSAX server on the SNMP Trap Destinations panel of the Site-Specific page or on the Notify and Target Address Table page.

Figure 2-3. Add to Trap List Window

Table 2-2. Adding Server IP Addresses to SNMP Manager List

If You Click ... Then the EMS-PSAX...

Yes adds the IP address to the site-specific information for the device if an open slot exists. If an open slot does not exist, you must manually add the IP address to the site-specific information for the device.

No does nothing. You must manually add the IP address to the site-specific information for the device (you can do this only if you are logged in with the proper security access privileges in SNMPv3 mode). Click the Notify and Target Address Table tab, right-click and select Update, and enter the appropriate information. Then click Update > Close.

Figure 2-4. SNMP Manager List is Full Window

255-700-762R11.1 2-7


Chapter 2 EMS-PSAX OverviewNetwork Management Access Options

! CAUTION:If you decline to enter the IP address at this time, no traps will be received and the EMS-PSAX will not display the latest PSAX device con-figuration.

Note: You can only add addresses to the SNMP manager list if you have Administrator or Configurator access privileges.

Network Management Access OptionsThe PSAX system software supports the following options for network man-agement:

• Serial port interface with a direct connection to a standard VT100 terminal emulator.

The console interface provides access to the configuration, fault, network data-collection, and security-management features of the system software.

This port is typically used for local management (using a direct serial con-nection), but it can also be used for remote management. Remote manage-ment may be performed over a PSTN with the use of an external modem, or over an ATM network with the use of a terminal emulation connection from a 6-Port Multiserial module. The serial port is also used for the config-uration of IP parameters, which are necessary for IP-based management.

• Ethernet interface connection on a LAN.

A 10BASE-T Ethernet interface (RJ-45 connector labeled ETHERNET) on the CPUn module allows access to the MIB, either using the EMS-PSAX application over a LAN or by telneting to the PSAX system. If a telnet ses-sion is used to manage a PSAX system, then the console interface is dis-played (similar to that which is used for the serial interface, as explained above). Only one person can have access to the console interface at a time; therefore, direct access using the serial port precludes telnet access using the Ethernet port.

• In-band management by using a PVC connection over an ATM WAN.

This allows for IP-based functions (that is, telnet) and SNMP functions (that is, element and network management software) to be performed remotely using ATM virtual circuits, which terminate within the managed node. The PVC/SVC connection is set up using an I/O module with an ATM cell bearing port (for example, the OC-12, OC-3c, STM-1, DS1, DS3, E1, and E3 modules). Three basic types of configuration are possible:

I/O and Server Modules

List of I/O Modules

Each PSAX system has one or two CPUn, Stratum 3–4, and Power Supply modules. I/O and server modules can be installed in any of its universal slots. Using the EMS-PSAX, you can configure ports and channels with interfaces with the I/O modules and provision (create) connections between them.

2-8 255-700-762R11.1


Chapter 2 EMS-PSAX OverviewI/O and Server Modules

Note: For more information on configuring ports, channels, interfaces, and connections, see the Navis® EMS-PSAX Modules Configuration Guide and Navis® EMS-PSAX Interfaces and Connection Provisioning Guide.

Configuring Ports, Channels, and Interfaces

Using the EMS-PSAX, you can perform all the port, channel, and interface configuration functions supported by the PSAX systems. Clicking on a port symbol in the Front Panel page or a port identifier in the Device Tree panel opens a corresponding port and channel configuration window. You must configure ports, channels, and interfaces before you can establish connec-tions between the modules.

For more information on configuring ports and channels, see the Navis® EMS-PSAX Module Configuration Guide.

Creating Connections

Once the interfaces are created, the Connections window, which is opened by clicking the Connections tab in the Device window, can be used to create unique connections between various interfaces established on the PSAX sys-tem.

For an explanation of the ATM in-band management feature on the PSAX systems, see the PacketStar® PSAX Multiservice Media Gateways User Guide.

For more information on provisioning connections using the PacketStar I/O and server modules, see the Navis® EMS-PSAX Interface and Connection Provi-sioning Guide.

255-700-762R11.1 2-9


Chapter 2 EMS-PSAX OverviewI/O and Server Modules

2-10 255-700-762R11.1


3 Navigating Windows in theEMS-PSAX

Overview of This ChapterThis chapter describes the following tasks:

• Using the Device List

~ Adding Device List Information

~ Updating Device Information

~ Deleting Device Information

~ Opening and accessing devices

• Using the User List

~ Adding a username to the User List

~ Updating, viewing, and deleting user information

• Navigating the main windows in the EMS-PSAX GUI

~ Viewing and using menu options

~ Viewing and using the Device Tree

~ Accessing and viewing the tabs within the Device window

• Managing Network Partitioning for Users and PSAX Devices

~ Preparing to use the Network Partitioning feature

~ Managing network partitioning from the User List

~ Managing network partitioning from the Device List

~ Adding Users

~ Removing Users

• Using the Main EMS-PSAX window

• Running scripts

The Device List and User ListThis section describes how to open and add devices in the EMS-PSAX system, and how to add users to the EMS-PSAX system in SNMPv2c and SNMPv3 mode. You cannot open devices in SNMPv2c and SNMPv3 modes simulta-neously within the same EMS-PSAX client.

In the EMS-PSAX system, you can open a device in two ways: from the Open Device window or from the Device List window.

Note: You can only add devices to the Device List window if you have Administrator or Configurator access privileges. You can only add users to the User List if you have Administrator access privileges. For detailed description on the differences between each security access level, see the Navis® EMS-PSAX Quick-Start Guide for the Cli-ent/Server Application.


255-700-762R11.1 3-1

Chapter 3 Navigating Windows in the EMS-PSAXUsing the Device List Windows

Once you launch the EMS-PSAX client and log in, the Main EMS-PSAX win-dow appears with the Device List window displayed (see Figure 3-1). The Device List uses CORBA North Bound Interface to populate or refresh the list of Devices. The Device List is updated based on Device added,deleted and modified events and these events are displayed in the status bar.

Using the Device List WindowsThe Device List windows contain a list of all PSAX devices that have been added to the list by administrators of the EMS-PSAX system. You can open devices using SNMPv2c (by default), or choose to open devices in SNMPv3 mode. For instructions on opening devices in SNMPv3 mode, see the section, “Managing Devices in SNMPv3 Mode,” in this chapter.

Adding Device List Information in SNMPv2c Mode

Perform the steps in the following procedures to add PSAX device informa-tion to the Device List window.

Figure 3-1. The Main EMS-PSAX Window

3-2 255-700-762R11.1



Begin

1 To open a device in SNMPv2c mode, in the EMS-PSAX Menu Bar, select View > Device List > SNMPv2c Device List.

The Device List window appears (see Figure 3-2).

Note: Upon initial installation in SNMPv2c mode, only an entry named Sample will appear in the Device List window.

The buttons on these windows have the following functions:

2 Use one of the following options to add a device to the Device List win-dow as described below (a or b):

a Right-click within the Device List window and a menu appears (see Figure 3-3). Select Create. The Add Device Dialog window appears (see Figure 3-4). Proceed to step 3.

b Click Open New Device or press Ctrl+O. The Open Device window appears (see Figure 3-10).

Proceed to the section, “Accessing a Device From the Open Device Window in SNMPv2c Mode” on page 3-8.

Figure 3-2. Device List Window (in SNMPv2c Mode)

Button Function

Open Displays the selected device in the Device window.

Close Closes this window.

Open New Device Displays the Open Device window so that you can open a device that is not listed in the Device List window.

255-700-762R11.1 3-3




3 In the Add Device Dialog window, enter data in each field as described in Table 3-1.

4 Click Add > Close.

End

Figure 3-3. Device List Window (Displaying Menu)

Figure 3-4. Add Device Dialog Window

Button Function

Add Adds the device information to the Device List window.


3-4 255-700-762R11.1



Table 3-1. Field Descriptions for the Add/Update Device Dialog Window

Field Name Values Description

IP Address Default: 0.0.0.0

Range: N/A

Format: Valid-dotted quad

Specifies the IP address of the PSAX device. To determine the IP address of a device, log on to the device through the console port on a CPU mod-ule in the device, with read-write privileges. On the Console Interface Main Menu, select the Site-Specific Configuration menu option and view the value in the CPU IP Address field.

Community Name Default: N/A

Range: N/A

Format: Text

Specifies the read/write community name for the PSAX device. To determine the community name of a device, log on to the device through the con-sole port on a CPU module in the PSAX device. On the Console Interface Main Menu, select the User Options menu option and view the value in the [Current SNMP readwrite community string] field. To change this value, enter up to 53 charac-ters in the Next SNMP readwrite community string field.

Retype Community Name

Default: N/A

Range: N/A

Format: Text

Confirms the read/write community name for the PSAX device.

SNMP Timeout Default: N/A

Range: N/A

Format: Numeric (seconds)

Indicates the number of seconds that elapse before the SNMP timeout for this device. For example, if you set this field to 10, then when-ever this device is opened or you use the GUI to retrieve information from this device, if the action cannot be done within 10 seconds, the EMS-PSAX system will show an SNMP timeout message and you will have to re-attempt the action.

SNMP is the protocol used between the EMS-PSAX server and the PSAX device. This value overrides the value specified in the snmp.timeout field in the aqv.properties file (see "EMS-PSAX System Properties" in Chapter 5.)

SNMP Retries Count Default: N/A

Range: N/A

Format: Numeric

Specifies the number of times you wish the SNMP manager to retry opening the device if the first try fails. This value overrides the value speci-fied in the snmp.retries field in the aqv.properties file (see "EMS-PSAX System Properties" in Chapter 5.)

255-700-762R11.1 3-5



Virtual Client Feature

Using the Virtual Client feature introduced in EMS-PSAX Release 5.1.1, you can preload devices individually using the Client/Server application to decrease the amount of time it takes to load devices.

By default, when you add a new device to the Device List window from the Open Device Dialog window, the device is added with preloading turned off. You can enable preloading of the device in the Device List window by select-ing the checkbox next to the Preload Device field. The next time the EMS-PSAX server is started or an EMS-PSAX client opens the updated device, the device is automatically loaded in the EMS-PSAX server. Thereaf-ter, when any EMS-PSAX client opens this device, the device is quickly dis-played in the Device window because the device was preloaded in the server.

You can also unload devices that were preloaded while the device continues to run. To unload a preloaded device, select View > Device List. Right-click the device you want to remove from the preloaded devices list, and select Unload In Server. The device will be unloaded if the device is preloaded in the server and is not open in any clients. Otherwise, an error message is dis-played (see Figure 3-5, Figure 3-6, and Figure 3-7).

Use Access List Default: (Unse-lected Checkbox)

Range: N/A

Format: Checkbox

Indicates whether or not to this device is autho-rized for access by EMS-PSAX users. Only a user with Administrator access privileges can config-ure this setting.

(Unselected Check-box)

Disables you from viewing the authorized users for this device.

(Selected Check-box)

Enables you to view the authorized users for this device. Checking this box also enables the User Access List button on the Update Device Dialog window.

Table 3-1. Field Descriptions for the Add/Update Device Dialog Window


Figure 3-5. Device Cannot Be Unloaded Error Message

3-6 255-700-762R11.1



Updating Device Information

Perform the steps in the following procedures to update PSAX device infor-mation in the Device List window.

Begin

1 To update the information about a device, open the Device List window by selecting View > Device List > SNMPv2c Device List or by pressing Ctrl+D.

2 Select the entry for the device that you want to update.

3 Right-click the entry a menu appears. Select Update (see Figure 3-3).

The Update Device Dialog window appears, displaying the information about the device that was previously entered (see Figure 3-8).

Figure 3-6. Device Was Not Preloaded in Server Error Message

Figure 3-7. Device Unload Confirmation Message

Figure 3-8. Update Device Dialog Window

255-700-762R11.1 3-7



The buttons on this window have the following functions:

4 Change information in any of the fields as appropriate, and click Update.

5 Click Close.

End

Deleting Device Information

Perform the steps in the following procedures to delete PSAX device informa-tion from the Device List window.

Begin

1 To delete a device from the Device List window, open the Device List window by pressing Ctrl+D.

2 Select the entry you want to remove from the Device List window.

3 Click the right mouse button and select Delete (see Figure 3-3).

A window appears, displaying a confirmation message (see Figure 3-9).

4 Click Yes.

The entry is removed from the Device List window.

5 On the Device List window, click Close.

End

Accessing a Device From the Open Device Window in SNMPv2c Mode

You can open devices using SNMPv2c (by default), or choose to open devices in SNMPv3 mode. You cannot open devices in SNMPv2c and SNMPv3 modes simultaneously.

Button Function

Update Updates the device information in the Device List window.


User Access List

Displays the User Access List window for the selected device.

Figure 3-9. Confirmation Window (Deleting Device List Entry)

3-8 255-700-762R11.1



The IP address will automatically display in this Open Device window if the Selection Name field for that PSAX object in HP OpenView NNM is set to the IP address.

To access the Open Device window in SNMPv2c mode, perform the steps in the following procedure.

Begin

1 In the EMS-PSAX Menu Bar, select File > Open Device > Open SNMPv2c Device or press Ctrl+O.

The Open Device window appears (see Figure 3-10).


2 Enter the appropriate values in the fields on the window as described in Table 3-1.

3 Click the checkbox next to Add to Device List if you want this device to be stored in the Device List window.

4 To open the device, click OK. To close the Open Device window without opening a device or adding to the Device List window, click Cancel.

The device appears in the Device window.

Note: If you get an error that says “EMS-PSAX encountered an error; device open failed,” then check your IP address and community name (as described in step 2 above) to make sure you entered them correctly, and repeat this procedure (steps 1–4).

End

Figure 3-10. Open Device Window (SNMPv2c Mode)

Button Function

OK Prompts the EMS-PSAX to open the device.

Cancel Closes this window without opening a device or adding to the Device List window.

255-700-762R11.1 3-9



Accessing a Device From the Device List Window

If the PSAX device for which you are launching the EMS-PSAX system from HP OpenView NNM is not included in the Device List window, the EMS-PSAX system will prompt you for the SNMP community name for that device. This PSAX device will then be added to the Device List window.

Perform the steps in the following procedure to open a device from the Device List window.

Begin

1 Do one of the following to open the Device List window:

• In the EMS-PSAX Menu Bar, click View > Device List > SNMPv2c Device List

• Press Ctrl+D

The Device List window appears (see Figure 3-2).

2 If the device you want to open appears in the Device List, right-click on the device entry and a menu appears (see Figure 3-3). Select Open.

The device opens in the Device window.

3 If the device you want to open does not appear in the Device List win-dow, click Open New Device or press Ctrl+N.

The Open Device window appears. Follow the instructions in “Accessing a Device From the Open Device Window in SNMPv2c Mode” on page 3-8.

End

Opening Multiple Devices Simultaneously

To select and open multiple devices simultaneously, perform the following two steps:

Begin

1 To select more than one, but not all the devices in the Device List win-dow, simultaneously press the Ctrl key and select the devices you want to open. To select all devices in the Device List window, select the first and last entries in the Device List window while pressing the Shift key.

2 Do either of the following:

~ Click Open.

~ Right-click the mouse and a menu appears (see Figure 3-3). Select Open.

Each device opens in separate Device windows.

End

Device Verification The EMS-PSAX system automatically verifies that the information entered in the IP Address and Community fields in the Open Device window is valid. Then the EMS-PSAX system will operate as described in Table 3-2.

When opening a device from HP OpenView NNM, the community name is not required if the device was previously added to the Device List window.

3-10 255-700-762R11.1


Chapter 3 Navigating Windows in the EMS-PSAXUsing the User List

Using the User ListPerform the steps in the following procedure to add, update or delete infor-mation about a user in the User List.

Adding a Username to the User List

Begin

Note: Only a user with Administrator access privileges can add users to the User List. See For detailed description on the differences between each security access level, see the Navis® EMS-PSAX Quick-Start Guide for the Client/Server Application.

1 Do one of the following to add a username to the User List:

~ In the EMS-PSAX Menu Bar, click View > User List (see Figure 3-36)

~ Press Ctrl+U

Table 3-2. EMS-PSAX System Operation When Opening a Device

When the EMS-PSAX... Then the EMS-PSAX...

cannot communicate with the device displays an error message (see Figure 3-11)Note: For troubleshooting tips, see the PacketStar® PSAX Simple Network Management Protocol (SNMP) Trap Ref-erence Guide.

locates the IP address of the device and verifies that the community name is correct

opens a new Device window for the device

has the Add to Device List field checked on the Open Device win-dow

adds the IP address, device type, and site name of the device to the Device List window Note: This option is only available if you have Administrator or Configu-rator access privileges.

Figure 3-11. Error Message Window (Cannot Open Device)

255-700-762R11.1 3-11



The User List window appears (see Figure 3-13).

Note: Upon initial installation, only three entries will appear in the User List window: ADMIN1, CONFIG1, and MONITOR1.

2 Right-click on an entry and a menu appears (see Figure 3-14).

3 Click Create.

Figure 3-12. View Menu (As Displayed on the EMS-PSAX Menu Bar)

Figure 3-13. User List Window

Figure 3-14. User List Window (Displaying Menu)

3-12 255-700-762R11.1



The Create New User window appears (see Figure 3-15).


The EMS-PSAX will use the selected user to display the default values.

4 Enter the values for the fields on this window according to the informa-tion provided in Table 3-3.

5 Click Add.

Figure 3-15. Create New User Window

Button Function

Add Adds the user information to the User List.

Update Updates the user information to the User List.

Delete Removes the user information from the User List.


Table 3-3. Field Descriptions for the Create New User and Update User Information Windows


Note: Many default values on the Create New User and Update User Information windows vary depending on the credentials you used to log into the EMS-PSAX and your security access level.

255-700-762R11.1 3-13



User Name Default: ADMIN1, CONFIG1, or MONITOR1

Range: N/A

Format: Predefined

Indicates the security access level for user.

ADMIN1 Indicates that the user has (Administrator) read/write access privileges.

CONFIG1 Indicates that the user has (Configurator) read/write access privileges.

MONITOR1 Indicates that the user has (Monitor) read-only access privileges.

Password Default: N/A

Range: > 5

Format: ASCII alpha-characters

Indicates the password for the person using the EMS-PSAX. It must be a minimum of six charac-ters.

Retype Password Default: N/A

Range: N/A


Indicates the password for the person using the EMS-PSAX. This field is used to confirm the pass-word. If the value in this field does not match the value in the Password field, the EMS-PSAX will not accept the user information on this window, and you will be prompted to reenter the values for both of these fields.

First Name Default: admin, con-fig, or monitor

Range: N/A


Indicates the first name of the user whose cre-dentials are being created or updated.

It is optional whether you enter a value in this field; that is, the EMS-PSAX will accept it if this field is blank.

Last Name Default: admin, con-fig, or monitor

Range: N/A


Indicates the last name of the user whose creden-tials are being created or updated.

It is optional whether you enter a value in this field; that is, the EMS-PSAX will accept it if this field is blank.

Role Default: Adminis-trator, Configura-tor, or Monitor

Range: N/A

Format: Predefined

Indicates the security access level for this user. For detailed description on the differences between each security access level, see the Navis® EMS-PSAX Quick-Start Guide for the Client/Server Application.

Administrator Indicates that this user has Administrator security access privileges.

Configurator Indicates that this user has Configurator security access privileges.

Monitor Indicates that this user has Monitor security access privileges.



3-14 255-700-762R11.1



For the last 10 days before the date selected in the Expiration Date field on the Create New User and Update User Information windows, a warning mes-sage appears upon launching the EMS-PSAX (see Figure 3-16).

Expiration Date Default: Never Expires

Range: N/A

Format: Predefined

Indicates the date when the user’s password expires.

Never Expires Indicates that the user’s password does not expire.

Note: When you select this value, the Year, Month, and Day fields are ghosted.

Default (30 days) Indicates that the user’s password expires 30 days from today’s date.

Note: When you select this value, the Year, Month, and Day fields are ghosted.

Configure Indicates that the user’s password expires on the date specified by the Year, Month, and Day fields.

Year Default: N/A

Range: 2003-2010

Format: Predefined

Indicates the year in which the user’s password expires.

Month Default: N/A

Range: N/A

Format: Predefined

Indicates the month in which the user’s password expires.

Day Default: N/A

Range: 1–31 (depend-ing on the value selected in the Month field)

Format: Predefined

Indicates the day of the month on which the user’s password expires. The days available reflect the number of days available in that month (28, 30, or 31).

Login Attempts Default: 10

Range: 3–10

Format: Numeric

Indicates the threshold value for the number of times a user tries to log into the EMS-PSAX before their account is disabled. This field is only applicable to users without Administrator access privileges.

User Access Default: Enable

Range: N/A

Format: Predefined

Indicates whether the user has access to the EMS-PSAX server.

Enable Indicates that the user has access to the EMS-PSAX server.

Disable Indicates that the user is denied access to the EMS-PSAX server.



255-700-762R11.1 3-15



For the last 10 days before the date selected in the Expiration Date field (except when Never Expires is selected), a warning message appears after launching the EMS-PSAX (see Figure 3-16).

Prior to or after the password expires, any user can reset the password, but only an Administrator user can reset a user’s expiration date.

Updating User Information

If you have Administrator access privileges, you can update the information about a user.

Begin

1 Select an entry on the User List, and select Update from the right-click menu in the User List (see Figure 3-14).

The Update User Information window will appear, displaying the infor-mation about the user that was previously entered (see Figure 3-17).

2 Change information in any of the fields (see Table 3-3), then click Update.

Figure 3-16. Password Expiration Warning Window

Figure 3-17. Update User Information Window

3-16 255-700-762R11.1




3 Click Close.

End

Viewing User Information

If you have Administrator access privileges, you can view the information about a user.

Begin

1 Do one of the following to view user information:

a Select an entry on the User List, and select View from the right-click menu in the User List (see Figure 3-14).

b On the EMS-PSAX Main Menu, select User Info > User Properties.

The User Information window will appear, displaying the information about the user that was previously entered (see Figure 3-18).

2 Click Close.

End

Deleting User Information

If you have Administrator access privileges, you can delete an entry from the User List. Perform the steps in the following procedure.

Button Function

Delete Removes the user information from the User List.

Update Updates the user information to the User List.


Figure 3-18. User Information Window

255-700-762R11.1 3-17



Begin

1 Select the entry you want to remove in the User List.

2 Click the right mouse menu and select Delete (see Figure 3-14).

A window appears, displaying a confirmation message (see Figure 3-19).

3 Click Yes.

The entry is removed from the User List.

4 On the User List window, click Close.

Note: You can also delete an entry in the User List from the Update User Information window (see Figure 3-17).

End

Changing the User Password

Perform the steps in the following procedure to change a user’s password.

Note: If you have Administrator access privileges, you can change the password for any user. If you do not have Administrator access privileges, you can change only your password.

Begin

1 Do one of the following:

a Select an entry on the User List, and select Reset Password from the right-click menu in the User List (see Figure 3-14).

b Type Alt+R.

The Reset User Password window appears (see Figure 3-20).

Figure 3-19. Confirmation Window (Deleting User List Entry)

3-18 255-700-762R11.1


Chapter 3 Navigating Windows in the EMS-PSAXManaging PSAX Devices in SNMPv3 Mode

2 In the Old Password field, type the current password.

3 In the New Password and Retype Password fields, enter the same new password. The password must be at least six characters in length.

4 Click OK.

End

Managing PSAX Devices in SNMPv3 Mode

Managing SNMPv3 devices is not supported when the EMS-PSAX is inte-grated with the NavisCore system.

Note: Trap and Inform users are created differently in the EMS-PSAX Cli-ent/Server and Standalone applications:

• EMS-PSAX server with NNM: Trap and Inform users are created in /etc/srconf/mgr/mgr.cnf, not within the EMS-PSAX.

• EMS-PSAX Standalone application: Trap and Inform users are created in the EMS-PSAX SNMPv3 Device List.

Configuring SNMPv3 Access in the EMS-PSAX

This section provides an overview of steps to configure devices in SNMPv3 mode. For detailed procedures on the steps in this section, see the SNMP Research SNMP Security Pack User Documentation, Version 15.4.

Begin

1 Install the SNMP Security Pack.

2 For managing SNMPv3 devices in HP OpenView NNM, configure USM users in the SNMP configuration window.

3 To enable ovtrapd to recognize traps and informs, and so that traps and informs will be forwarded to the EMS-PSAX server, configure SNMPv3 trap users and inform users in the /etc/srconf/mgr/mgr.cnf file.

Figure 3-20. Reset User Password Window (Administrator Privileges)

255-700-762R11.1 3-19



4 To enable PollClient to monitor SNMPv3 PSAX devices on the HP Open-View NNM map, use the V3Device_Menulist script to set up the list of SNMPv3 PSAX devices.

End

Adding Device List Information in SNMPv3 Mode

Perform the steps in the following procedures to add PSAX device informa-tion to the Device List window.

Begin

1 To open a device in SNMPv3 mode, in the EMS-PSAX Menu Bar, select View > Device List > SNMPv3 Device List.

The SNMPv3 Device List window appears (see Figure 3-21).


Figure 3-21. SNMPv3 Device List Window

Button Function

Open Displays the selected device in the Device window.


Open New Device Displays the Open Device window so that you can open a device that is not listed in the Device List window.

3-20 255-700-762R11.1



2 You can filter the SNMPv3 Device List window to display SNMPv3 devices by user type. To do this, select the appropriate user name in the Showing List for EMS-PSAX User field (see Figure 3-22).

3 Use one of the following options to add a device to the Device List win-dow as described below:

a Right-click within the SNMPv3 Device List window and a menu appears. Select Create.

b Click Open New Device.

The Open SNMPv3 Device window appears (see Figure 3-23). Proceed to the section, “Accessing a Device From the Device List Window” on page 3-10.

End

Accessing a Device From the Open Device Window in SNMPv3 Mode

You can open devices using SNMPv2c (by default), or choose to open devices in SNMPv3 mode. You cannot open devices in SNMPv2c and SNMPv3 modes simultaneously.

The IP address will automatically display in this Open Device window if the Selection Name field for that PSAX object in HP OpenView NNM is set to the IP address.

To access the Open Device window in SNMPv3 mode, perform the steps in the following procedure.

Begin

1 In the EMS-PSAX Menu Bar, select File > Open Device > Open SNMPv3 Device.

The SNMPv3 Device window appears (see Figure 3-21).

2 Do one of the following to open an SNMPv3 device (a or b):

Figure 3-22. SNMPv3 Device List Window (Displaying User Names)

255-700-762R11.1 3-21



a Right-click within the window and select Create. The Add SNMPv3 Device window appears (see Figure 3-23).

b Click the Open New Device button. The Open SNMPv3 Device win-dow appears (see Figure 3-24).


3 Enter the appropriate values in the fields on the window as described in Table 3-4.

4 Do one of the following (a or b):

a Click the checkbox next to Add to SNMPv3 Device List in the Open SNMPv3 Device window if you want this device to be stored in the SNMPv3 Device List.

Figure 3-23. Add SNMPv3 Device Window

Figure 3-24. Open SNMPv3 Device Window

Button Function

Add/Open Prompts the EMS-PSAX to open the device.

Close Closes this window without opening a device or adding to the Device List window.

3-22 255-700-762R11.1



b Click the checkbox next to Preload Device in the Add SNMPv3 Device window if you want this device to be preloaded.

5 To open the device, click Add. To close the Open Device window with-out opening a device or adding to the Device List window, click Close.

The device appears in the Device window.

End

Table 3-4. Field Descriptions for the Open SNMPv3 Device Window


EMS-PSAX User Default: Internal User

Range: N/A

Format: Predefined

Indicates the type of SNMPv3 user on the EMS-PSAX. This field must be configured in order for the EMS-PSAX to work properly in SNMPv3 mode.

Note: This field does not appear if you access this window from the File menu, by clicking Open New Device on the SNMPv3 Device List window, or from the V3Device_Menulist script. It also does not appear unless the user accessing the window is has administrator access privileges (ADMIN1).

Internal User Indicates that the server initiates an SNMP request to the PSAX device in order to get the user’s information. After entering the values for this field, the PSAX device will authenticate this type of user.

Note: Only an Internal User can preload devices in the device list.

SNMPv3TrapAuthUser

Indicates that the EMS-PSAX server will autheti-cate traps initated by the PSAX device. After entering the values for this field, the PSAX device will authenticate this type of user.

Note: If this value is not configured, traps will not be authenticated or viewable in the Log page.

SNMPv3InformUser

Indicates that EMS-PSAX server will autheticate informs initated by the PSAX device. (Informs are similar to traps except that when the PSAX device sends an inform to the EMS-PSAX server, the server is expected to respond with an acknowledgement.) After entering the values for this field, the v server will authenticate this type of user.

Note: If this value is not configured, informs will not be authenticated or viewable in the Log page.

See also the section, “Determining the EMS-PSAX Engine ID” on page 3-26.

255-700-762R11.1 3-23



IP Address Default: 0.0.0.0

Range: N/A


Specifies the IP address of the PSAX device using SNMPv3. To determine the IP address of a device, log on to the device through the console port on a CPU module in the device, with read-write privileges. On the Console Interface Main Menu, select the Site-Specific Configuration menu option and view the value in the CPU IP Address field.

Note: The specified IP address can only have one type of user. See the EMS-PSAX User field description.

SNMPv3 User Default: N/A

Range: N/A

Format: Alphanu-meric characters

Specifies the user name for the PSAX device using SNMPv3. You must know your user name in advance.

Note: This field is not associated with the com-munity string for the device. The user name is only configurable in the PSAX console through the serial port.

Security Level Default: Authenti-cation, No-Privacy

Range: N/A

Format: Predefined

Indicates whether authentication and privacy passwords are required in order to for the user specified in the SNMPv3 User field to access the PSAX device.

Authentication, No-Privacy

Indicates that only an authentication password is required in order to access the PSAX device.

Authentication, Privacy

Indicates that both authentication and privacy passwords are required in order to access the PSAX device.

No-Authentica-tion, No-Privacy

Indicates that neither authentication nor privacy passwords are required in order to access the PSAX device.

Authentication Proto-col

Default: MD5

Range: N/A

Format: Predefined

Indicates the type of authentication protocol to be used between the EMS-PSAX server and the PSAX device.

Note: This field is display-only when No-Authentication, No-Privacy is selected in the Security Level field.

MD5 Indicates that the authentication protocol is Mes-sage-Digest 5 (MD5).

SHA-1 Indicates that the authentication protocol is Secure Hash Algorithm (SHA).



3-24 255-700-762R11.1



Authentication Pass-word

Default: N/A

Range: 1–32

Format: Alphanu-meric

Specifies the authentication password. You can specify alphanumeric characters including A-Z, a-z, 0-9, / (forward slash), - (hyphen), and _ (underscore). The text string is case-sensitive. The use of the space character is not supported.

Note: This field is display-only when No-Authentication, No-Privacy is selected in the Security Level field.

Privacy Password Default: N/A

Range: 1–32


Specifies the privacy password. You can specify alphanumeric characters including A-Z, a-z, 0-9, / (forward slash), - (hyphen), and _ (underscore). The text string is case-sensitive. The use of the space character is not supported.

Note: This field is display-only when Authenti-cation, No-Privacy or No-Authentication, No-Privacy is selected in the Security Level field.

Site Name Default: N/A

Range: 1–19

Format: Alphanu-meric Character

Specifies the site name that you define for the selected device. Enter a site name having no more than 19 characters of the following types: alphanumeric, - (hyphen), and _ (underscore). Do not use spaces or periods.

Note: This field displays only when accessing this window from the V3Device_Menulist script, and is optional.

SNMP Timeout (sec) Default: 5

Range: N/A

Format: Seconds

Indicates the number of seconds that elapse before the SNMP timeout for this device. For example, if you set this field to 10, then whenver this device is opened or you use the GUI to retrieve information from this device, if the action cannot be done within 10 seconds, the EMS-PSAX will show an SNMP timeout message and you will have to reattempt the action.

SNMP is the protocol used between the EMS-PSAX server and the PSAX device. This value overrides the value specified in the snmp.timeout field in the aqv.properties file (see "EMS-PSAX System Properties" in Chapter 6.)

SNMP Retries Default: 1

Range: N/A

Format: Numeric

Specifies the number of times you wish the SNMP manager to retry opening the device if the first try fails. This value overrides the value speci-fied in the snmp.retries field in the aqv.properties file (see "EMS-PSAX System Properties" in Chapter 6.)



255-700-762R11.1 3-25



Determining the EMS-PSAX Engine ID

The EMS-PSAX engine ID is specified while configuring USM users in the PSAX device in the SnmpEngineID field under Site-Specific Configuration > SNMP Agent > USM User Config to add USM user entries for authentication of SNMPv3 informs. This menu is available through the console when con-nected to the PSAX device through a serial port and logged in as root user.

The engine ID of any SNMP agent is a 12-byte value which identifies that SNMP entity. When the PSAX device is configured to send SNMPv3 informs to the EMS-PSAX, the PSAX device should create a USM user entry by using the EMS-PSAX engine ID. This USM user should match the SNMPv3 user created under SNMPv3InformUser in the SNMv3 Open Device window in the EMS-PSAX GUI.

To determine the engine ID of the EMS-PSAX EMS, the algorithm is as fol-lows:

• The first 8 bytes of the engine ID are the hexadecimal equivalents of the letters that spell EMS-PSAX, which are 41,51,75,65,56,69,65,77 respec-tively.

• The remaining 4 bytes of the engine ID are the hexadecimal equivalent of IP address where the EMS-PSAX server or Standalone system is running.

For example, an EMS-PSAX server or Standalone system is running on a machine having the IP address 180.48.207.161 has an EMS-PSAX engine ID of 4151756556696577B430CFA1.

Configuring SNMPv3 Devices Monitored by PollClient

To configure the SNMPv3 Device List script in the EMS-PSAX server, go to the directory /opt/NEP/bin and run the script named V3Device_Menulist. You must be root or bin to access the SNMPv3 Device List.

The HP OV V3 Device List window appears (see Figure 3-25), displaying the complete list of SNMPv3 devices managed by the Poll Client.

3-26 255-700-762R11.1


Chapter 3 Navigating Windows in the EMS-PSAXManaging Network Partitioning for Users and PSAX Devices

The buttons in this window have the following functions:

For information on using the fields on the Open SNMPv3 Device window, see Chapter 3.

Managing Network Partitioning for Users and PSAX DevicesWith the Network Partitioning feature introduced in Release 6.1.0, a user with Administrator access privileges can control the Configurator and Moni-tor user access to devices in the Device List.

Once the access control is defined, users without the proper access cannot open devices from the EMS-PSAX GUI (see Figure 3-26). Thus, user access is controlled to specific devices in the managed network.

Figure 3-25. HP OV V3 Device List

Button Function

Add Device Displays the Open SNMPv3 Device window.

Delete Removes the device from the list.


255-700-762R11.1 3-27



Prerequisites for Managing Network Partitioning

Before you can use the Network Partitioning feature, you must do the fol-lowing:

• Log in to the EMS as an Administrator

• Add the devices that you want to manage in the Device List

• Add the users that will access these devices in the User List

The user access to devices can be modified from the User List or the Device List (see Table 3-5).

The Network Partitioning feature must be enabled on each PSAX device before you can add or remove entries from the device access list. You can enable this feature by opening the Device List, choosing the device on which the feature is to be enabled, right-click the mouse and select Update, select the Use Access List checkbox, and click Update. Another way to enable the feature is described in Table 3-7.

Managing Network Partitioning From the User List

To manage network partitioning from the User List, perform the steps in the following procedures, “Adding Users to the Device Access List” and “Remov-ing Users From the Device Access List”.

Note: Only users with Administrator access privileges can manage net-work partitioning.

Figure 3-26. Unauthorized User Window

Table 3-5. Modifying User Access Privileges for Network Partitioning

To manage network partitioning from the...

see the section...

User ListNote: If you want to modify the user access parameters for multiple users on multiple devices, it is recom-mended that you modify user access from the User List.

“Managing Network Partitioning From the User List”

Device List “Managing Network Partitioning From the Device List”

3-28 255-700-762R11.1



Adding Users to the Device Access List

Begin

1 Open the User List window.

2 Select one or more users, see Table 3-6.

3 Select Add to an access list from the menu.

The Device Selection window appears (see Figure 3-27).

4 Select the PSAX devices within the Device Selection window that you want to add authorization for the selected user(s). Press the Ctrl key to select multiple devices.

5 Right-click within the window and a menu appears. Select Add to device access list.

Table 3-6. Selecting Users and Devices

If you want to select... then...

one user or device click on the entry whose information you want to update. Then right-click and a menu appears.

more than one user or device right-click on the entry containing the information you want to update. Press the Ctrl key and click each entry. When finished, continue holding the Ctrl key, and right-click the mouse. A menu appears.

Figure 3-27. Device Selection Window

255-700-762R11.1 3-29



6 Click OK.

7 On the Device Selection and User List windows, click Close.

End

Removing Users From the Device Access List

Begin

1 Open the User List window.

Table 3-7. User Access on the Update Device Dialog Window

If the User Access List field on the Update Device Dialog window for this device is...

then...

selected (meaning that the Network Partitioning feature is enabled)

the corresponding confirmation window appears (see Figure 3-28).

deselected (meaning that the Network Partitioning feature is disabled)

the corresponding prompt window appears for each selected device, prompting you to decide whether to acti-vate the Network Partitioning feature.

If you click No, the window closes without adding the device(s). If you click Yes, the Network Partitioning fea-ture is enabled, and the corresponding confirmation win-dow appears (see Figure 3-28).

Figure 3-28. Enable User Access Confirmation Window

3-30 255-700-762R11.1



2 To select one or more users whose information you want to remove from the device access list, see Table 3-6.

3 A menu appears. Select Remove from an access list from the menu.

The Device Selection window appears (see Figure 3-27).

4 Select the PSAX devices within the Device Selection window that you want to remove authorization for this user. Press the Ctrl key to select multiple devices.

5 Right-click within the window and a menu appears. Select Remove from access list. See Table 3-8.

6 Click OK.

Table 3-8. User Access List Confirmation Windows

If the user... then...

was previously given access on the device

the corresponding confirmation window appears

Proceed to step 6.

was not previously given access on the device

the corresponding confirmation window appears

a Click Yes to proceed or No to Cancel.

If you press No, the window closes without removing the device(s). If you press Yes, the corresponding confirmation window appears.

b Proceed to step 6.

255-700-762R11.1 3-31



7 On the Device Selection and User List windows, click Close.

End

Managing Network Partitioning From the Device List

You can manage the user access list for a specific PSAX device from the Device List. To manage network partitioning between users from the Device List, perform the steps in the following procedures, “Adding Users to the User Access List” and “Removing Users From the User Access List”.

Note: Only users with Administrator access privileges can manage net-work partitioning between users.

Adding Users to the User Access List

Begin

1 Open the Device List window.

2 Select the entry for each device that you want to update.

3 Right-click on the entry, and a menu appears. Select Update.

The Update Device Dialog window appears.

4 Select the Use Access List checkbox (if it is unchecked).

5 Click User Access List.

The User Access List window appears (see Figure 3-29).

6 Right-click within the window and a menu appears (see Figure 3-29).

7 Select Add a User.

Figure 3-29. User Access List Window

3-32 255-700-762R11.1



The EMS-PSAX Valid User List window appears (see Figure 3-30).

8 In the User Name field, select the user name for the user that you want to add to the User Access List.

9 Click Add.

The user name is added to the User Access List window. Repeat steps 8 and 9 to add more users.

10 On the User Access List and Device List windows, click Close.

End

Removing Users From the User Access List

Begin

1 Follow steps 1–5 in the procedure, “Adding Users to the User Access List”; then proceed to step 2 of this procedure.

2 Right-click the entry for the user that you want to remove from the User Access List and a menu appears (see Figure 3-29).

3 Select Delete.

A confirmation window appears (see Figure 3-31).

4 Click Yes to proceed or No to Cancel.

If you press No, the window closes without removing the user(s) from the User Access List window. If you press Yes, the user name is removed from the User Access List window.

5 On the User Access List, Update Device Dialog, and Device List windows, click Close.

Figure 3-30. EMS-PSAX Valid User List

Figure 3-31. Deleting User Access List Entry Confirmation Window

255-700-762R11.1 3-33


Chapter 3 Navigating Windows in the EMS-PSAXUsing the Main EMS-PSAX Window

Note: Users can also be removed from access lists by clicking Delete in the EMS-PSAX Valid User List window (see Figure 3-30).

End

Using the Main EMS-PSAX WindowThe Main EMS-PSAX window contains a Title Bar, Menu Bar, and Device Tree, which are described in the following sections.

After you select and open a PSAX device, the Device window appears within the Main EMS-PSAX window, and the Device Tree and Front Panel displays the configuration of the PSAX device (see Figure 3-32).

Title Bar

The EMS-PSAX Title Bar displays the name of the application, the user’s name, and the user’s security access level (see Figure 3-33).

Figure 3-32. Device Window

Figure 3-33. Title Bar

3-34 255-700-762R11.1



Menu Bar

The EMS-PSAX Menu Bar (see Figure 3-34), located directly under the Title Bar, contains the File, View, and Help menu options.

File Menu The Open Device window can be opened from the File menu (see Figure 3-35) in the EMS-PSAX Menu Bar.

The File menu options are described in Table 3-9.

Figure 3-34. Menu Bar

Figure 3-35. File Menu (As Displayed on the EMS-PSAX Menu Bar)

Table 3-9. File Menu Option Descriptions

Options Description

Open Device • Open SNMPv2c Device

• Open SNMPv3 Device

Displays the Open Device or Open SNMPv3 Device window, in which you can enter an IP address and community name to open a specific PSAX device in SNMPv2c or SNMPv3 mode. The keyboard shortcut to display the Open Device window is Ctrl+O.

Run Script Allows you to execute a system command. The keyboard shortcut to display the Run Script win-dow is Ctrl+C. For more information on running scripts, see the section “Running Scripts” in this chapter.

Config Backup Opens the Backup Configuration window. For more information on scheduling PSAX configura-tion backups, see Chapter 9.

Connections File Displays the Connections File window. For details on this window, see the Navis® EMS-PSAX Inter-face and Connection Provisioning Guide.

255-700-762R11.1 3-35



View Menu The following windows can be opened from the View menu (see Figure 3-36) in the EMS-PSAX Menu Bar:

• User List window (described in this chapter)

• Device List window (described in this chapter)

• NSAP Database window (see the Navis® EMS-PSAX Interface and Connection Provisioning Guide)

• Users Logged On Server window (see the appropriate Navis® EMS-PSAX Quick-Start Guide).

• User Properties window (see “Configuring User Properties” in Chapter 6)

Interfaces File Displays the Interfaces File window. For details on this window, see the Navis® EMS-PSAX Inter-face and Connection Provisioning Guide.

Generate Device Report

Allows you to generate report for all the PSAX devices. The keyboard shortcut to generate device report is Shit+G.

Exit Closes the EMS-PSAX client. The keyboard short-cuts to leave the EMS-PSAX are Alt+F4 and Alt+X.

Table 3-9. File Menu Option Descriptions

Options Description

Figure 3-36. View Menu (As Displayed on the EMS-PSAX Menu Bar)

3-36 255-700-762R11.1



The View menu options are described in Table 3-10.

Table 3-10. View Menu Option Descriptions

Options Description

User ListNote: Only accessible by Administrators and Configurators.

Displays all users who are registered to use the EMS-PSAX. The keyboard shortcut to display the User List window is Ctrl+U.

For more information about the EMS-PSAX secu-rity access levels, see the appropriate Navis® EMS-PSAX Quick-Start Guide.

Device List • SNMPv2c Device List

• SNMPv3 Device List

Each of these windows display all PSAX devices accessible by the EMS-PSAX in either SNMPv2c mode (default) or SNMPv3 mode, and contains a button to access the Open Device window.

The keyboard shortcut to display the Device List window is Ctrl+D.

User Info • User Properties

Displays the User Information window. The key-board shortcut to display this window is Alt+U.

• Reset User Passwd

Displays the Reset User Password window. The keyboard shortcut to display this window is Alt+R.

NSAP Database Allows you to edit, load, or save a configured net-work service access point (NSAP) flat-file data-base.

For more information about the NSAP database, see the Navis® EMS-PSAX Connection Provisioning Guide.

Show Logged In Users Displays the Users Logged On Server window. The keyboard shortcut to display the Users Logged On Server window is Alt+L. For more information about the Users Logged On Server window, see the appropriate Navis® EMS-PSAX Quick-Start Guide.

Properties Displays the User Properties window, which lists the user properties for the EMS-PSAX client, including the server name, location of Acrobat Reader file for viewing documentation, debug level, and NSAP format. The keyboard shortcut to display the User Properties window is Ctrl+P.

255-700-762R11.1 3-37



Help Menu The About window (see Figure 3-38) can be opened from the Help menu (see Figure 3-37) in the EMS-PSAX Menu Bar.

The Help menu options are described in Table 3-11.

Message Bar

The Message Bar displays messages about actions in the Main EMS-PSAX window and the EMS-PSAX. The Main EMS-PSAX window contains a Mes-sage Bar on the bottom of the window (see Figure 3-39). Once a device is

Figure 3-37. Help Menu (As Displayed on the EMS-PSAX Menu Bar)

Figure 3-38. About Window

Table 3-11. Help Menu Option Descriptions

Options Description

Quick Start Guide Launches the Adobe Acrobat PDF file of the EMS-PSAX Quick-Start Guide (installation instructions) for the version of the EMS-PSAX that you are running.

User Guide Launches the Adobe Acrobat PDF file of the EMS-PSAX User Guide (configuration instruc-tions) for the version of the EMS-PSAX that you are running.

Module Guide Launches the Adobe Acrobat PDF file of the Navis EMS-PSAX Modules Configuration Guide.

Interface and Con-nection Guide

Launches the Adobe Acrobat PDF file of the Navis EMS-PSAX Interface and Connection Provision-ing Guide.

About Opens the About window, displaying the soft-ware version of the EMS-PSAX and the year of copyright.

3-38 255-700-762R11.1



opened, a second Message Bar displays at the top of the Device window (see Figure 3-40). This top Message Bar displays the latest SNMP trap message or EMS-PSAX event regarding a particular PSAX device.

Device Tree

Once a PSAX device is opened, the Device Tree displays in the left panel of the Device window, (see Figure 3-32). The Device Tree provides a snapshot of the PSAX device configuration and can be expanded to view the device, slot, port, channel, and connection levels.

Functions The Device Tree creates a tree for each open PSAX device. The Device Tree panel and the Device window of the Main EMS-PSAX window can be resized by dragging the bar between the panels to the left or to the right. The Device Tree or the Device window can be expanded to cover the entire window by clicking on the left and right arrows located on the top of the bar between them. Once in the expanded position, they can be returned to their original positions by clicking the opposite arrow.

The Device Tree does the following:

• Displays the device, slot, port, channel, and connection level of each open device. If a slot is empty, the Device Tree displays Empty for that slot instead of the module name (see Figure 3-41).

• Indicates the current status of each object through color-coded icons, using the same color-coding as the ports in the Front Panel window.

Figure 3-39. Message Bar (Bottom of Window)

Figure 3-40. Message Bar (Top of Window)

Figure 3-41. Device Tree (Displaying Empty Slots)

255-700-762R11.1 3-39



The color of the highest severity level propagates from child to parent symbol (see Figure 3-42). This enables users to quickly recognize alarm conditions even when the tree has not been fully expanded. For more information about LED status and color indicators, see Chapter 6.

• Enables you to quickly open configuration windows for the desired object.

Expanding and Collapsing the Device Tree

The Device Tree can be expanded to display each module and its port, chan-nel, and connection levels. When a device is opened in the Device window, the Device Tree displays the slot level by default. To expand the tree, click the toggle switch icon for a given module, port, or channel, or select Expand Node in the right-click menu for a given module, port, or channel. If you choose Expand Node in the right-click menu on the toggle switch icon for a PSAX device, the entire tree is expanded for all modules.

Figure 3-42. Device Tree Status Indicators

Module Indicatorand Module Name

Port Indicators

Name of PSAX Device

Operational Status

Figure 3-43. Device Tree (Displaying Right-Click Menu)

3-40 255-700-762R11.1



When the icon is vertical, the tree is expanded, and all child (underlying) objects are displayed (see Figure 3-44, which displays the child objects of each configured port).

When the icon is horizontal, the tree is collapsed and only the higher-level objects are displayed (see Figure 3-45). To collapse the tree, click the toggle switch icon in the Device Tree or select Collapse Node in the right-click menu (see Figure 3-43).

Objects in the tree are automatically highlight as the mouse cursor is placed on it. Objects in the tree must be double-clicked to display a dialog window.

Figure 3-44. Expanded Device Tree

Figure 3-45. Collapsed Device Tree

255-700-762R11.1 3-41


Chapter 3 Navigating Windows in the EMS-PSAXRunning Scripts

If you right-click a module icon in the Device Tree (or bar-code graphic in the Front Panel tab), a menu will appear that will allow you to perform opera-tions on all interfaces, and expand or collapse the tree. (For more informa-tion, see Chapter 6.)

Multiple devices can be in the foreground of the Device window simulta-neously (if the device windows are resized). If multiple PSAX devices are open, the PSAX device selected in the Device Tree is displayed in the fore-ground of the Device window. If only one device is displayed, you can do either of the following to bring a different opened device to the foreground of the Device window:

• In the Device Tree, double-click on the icon for the device

• From the View option in the EMS-PSAX Menu Bar, select the device from the list of opened devices at the bottom

Running ScriptsYou can run scripts for any type of executable file or application, for example, launching one of the programs under the Start/Programs/Accessories menu on a Windows OS. This feature was introduced in Release 5.1.

Perform the steps in the following procedure to run scripts or system com-mands.

Begin

1 Select File > Run Script from the EMS-PSAX Menu Bar.

The Run Script window appears (see Figure 3-46).

The buttons at the bottom of the window have the following functions:

The Run Script window functions like the Start > Run command menu on Windows workstations.

2 Enter any pathname or system command, for example, "telnet," and click Run.

The command in the Run Script field is performed.

End

Using the Device Window

Figure 3-46. Run Script Window

Button Function

Run Performs the command in the Run Script field.

Cancel Closes this window.

3-42 255-700-762R11.1



Device Window Menu Bar

When the Device window opens, the Menu Bar displays the options described in Table 3-12.

Table 3-12. Descriptions for the Device Window Menu Bar Options

Menu Options Description

Device Refresh Device Updates the device completely within the EMS-PSAX.

Save PSAX Configuration

Saves all configuration changes on the PSAX net-work element to the PSAX device.

View Stratum Configuration

Displays the Primary Stratum Configuration win-dow.

Stop All Polling Terminates polling of statistics on the PSAX device.

Start Profiling Enables profiling on all open PSAX devices.

Stop Profiling Disables profiling on all open PSAX devices.

Search Interfaces by Name

Displays the Interface Search By Name window.

Exit Removes the PSAX device that is selected in the Device window.

Dialog [List of open windows on the PSAX device]

Lists the configuration windows that are opened on the PSAX device displayed in the Device win-dow. Click on one of these windows to make it active.

Close All Dialogs Closes all the dialog windows that are open.

255-700-762R11.1 3-43



Device Window Layers

The Device window contains several tabs. From these main tabs, you can access a number of other windows and panels for configuring and maintain-ing of the PSAX systems. This guide refers to the various window layers as described in Table 3-13.

Connection Create New Opens the Create New Connection window. This option does not become active until the Load option is used (see below).

For more information about creating connec-tions, see the appropriate Navis® EMS-PSAX Mod-ules Configuration Guide.

Load This option displays after a new device is opened. Selecting this option loads the current connection table from the PSAX device. After the table is loaded, this option changes to Create New.

This option does not display if you have already clicked the Connections tab in the Device win-dow for the device.

Refresh Updates the connection.

Restore Adds the previously deleted connection to the Listing page. For more information, see the appropriate Navis® EMS-PSAX Modules Configura-tion Guide.

This option is available only after you have deleted and recreated an interface that was involved in a connection in the current session.

For more information on restoring connections, see the section, “Restoring Connections,” in the Navis® EMS-PSAX Interface and Connection Provi-sioning Guide.

Clear Restore Deletes any connection that was previously restored during the current session of the EMS-PSAX.

This option is available only after you have deleted and recreated an interface that was involved in a connection in the current session.

Zoom 30% Enlarges the view of the current PSAX device to 30% of the original size.

The Zoom option only enlarges the front panel view. All other windows appear as full size.

50% Changes the view of the current PSAX device to 50% of the original size.



Table 3-12. Descriptions for the Device Window Menu Bar Options (Continued)

3-44 255-700-762R11.1



Table 3-13. EMS-PSAX Windows and Subwindows

Level Title

First Window (for an example of a window, see Figure 3-47)

Second Tab (the tab that you click to view a page

Third Page(for an example of a page, see Figure 3-48)

Fourth Panel(for an example of a panel, see Figure 3-49)

Figure 3-47. Sample Port and Channel Configuration Window

255-700-762R11.1 3-45



Figure 3-48. Sample Channel Configuration Page

3-46 255-700-762R11.1



Additional areas that are not viewed from the Device window, but are viewed by clicking a button are called windows. For example, when files are being transferred using the CPU Upgrade page, a confirmation window auto-matically appears (for more information, see Chapter 9). The tabs in the Device window are described in the following sections.

Front Panel Tab Clicking the Front Panel tab in the Device window displays a graphical repre-sentation of the PSAX device’s front panel (see Figure 3-50 through Figure 3-54). From the Front Panel tab, you can easily open windows that let you do the following:

• Obtain current port and interface data

• Open port and channel configuration windows so that a port can be provi-sioned

• Access the PSAX console user interface

Figure 3-49. Sample Port Statistics Panel

255-700-762R11.1 3-47



Note: If a configured I/O or server module has failed, or is removed from the PSAX chassis, a "ghosted," or light gray, version of the module appears in the Front Panel tab (see Figure 3-54).

The Back Panel is also displayed for a PSAX 1000 device. The Back Panel dis-plays the Power Supply/Stratum modules.

Figure 3-50. Front Panel Tab (Displaying a PSAX 4500 Chassis)


3-48 255-700-762R11.1





255-700-762R11.1 3-49



Note: For the EMS-PSAX to display a 23-inch chassis, a module must be installed in slot 13, 14, 15, or 16 (these slots are present only in the PSAX 1250 23-inch chassis).

Note: The Front Panel will not display slot 25 in the Device Tree for the PSAX 2300 system unless an Alarm module is present (see Figure 3-55).

Connections Tab The Connections tab in the Device window enables you to create connections and display all connections currently established on the PSAX device. For more information about using the pages located under the Connections tab, see the appropriate PacketStar® PSAX Connection Provisioning User Guide.


Figure 3-55. Device Tree (Displaying an Alarm Module in Slot 25)

3-50 255-700-762R11.1



Site-Specific Tab The Site-Specific tab is used to set properties for a PSAX device (see Figure 3-56). For more information about the Site-Specific tab and its under-lying pages, see Chapter 4.

Diagnostics Tab The Diagnostics tab (see Figure 3-57) displays information related to the CPUn in the PSAX device. For more information about the Diagnostics tab, see Chapter 9.

Figure 3-56. Site-Specific Page

Figure 3-57. Diagnostics Page

255-700-762R11.1 3-51



System Maintenance Tab

The System Maintenance tab is used to perform software and firmware upgrades to PSAX hardware components. For more information about the System Maintenance tab, see Chapter 9.

IISP Routing Page The IISP Routing page (see Figure 3-59) is used to display and configure the IISP VBR and IISP CBR routing tables. The IISP Routing page lists all existing routing entries in the VBR and CBR routing tables. For more information about the IISP Routing page, see Chapter 7.

Figure 3-58. CPU Upgrade Page

Figure 3-59. IISP Routing Page

3-52 255-700-762R11.1



PNNI Page The PNNI page (see Figure 3-60) is used to display and configure PNNI sys-tem-wide configuration. For more information about the IISP Routing page, see the Navis® EMS-PSAX Interface and Connection Provisioning Guide.

For more information about the PNNI page, see Chapter 7.

Log Tab The Log tab (see Figure 3-61) displays all SNMP traps that enter the EMS-PSAX for a specific PSAX device on the in the Log page.

To view trap messages in the Log page, they must be stamped with the same originating IP address that the device was opened within the EMS-PSAX. The EMS-PSAX server address must be specified as a trap recipient in the Notify and Target Address Table page.

Note: The EMS-PSAX log will only collect traps for a particular PSAX device while that device is open in the EMS-PSAX. Closing and reopening the device will clear this log. To view a trap log history, use the HP OpenView NNM Events Browser or the PSAX console user interface trap log.

Figure 3-60. PNNI Page

Figure 3-61. Log Tab (Displaying Menu)

255-700-762R11.1 3-53



For more information about the Log tab, see Chapter 6. For more informa-tion on PSAX-specific trap messages, see the document, PacketStar® PSAX Simple Network Management Protocol Reference Guide for PSAX Multiservice Gate-ways.

Active Alarm Tab The Active Alarm Tab displays the list of alarms that are generated in the PSAX system (see Figure 3-62).

To view the list of alarms that are generated in the PSAX system, you should enable the Active Alarm Table field in the site specific window (see Figure 3-56).

To refresh the Active Alarm Table, right-click and select Refresh. For more information about the Active Alarm tab, see Chapter 7 (see Figure 7-25).

Figure 3-62. Active Alarm Table

3-54 255-700-762R11.1


4 Site-Specific Configuration

Site-Specific Documentation for the EMS-PSAXSome of the functions that are accessible from the Site-Specific tab in the EMS-PSAX are described in other documents on the Navis EMS-PSAX Prod-uct Information Software Library, as shown in Table 4-1. All other functions that are accessible from the Site-Specific tab are described in this chapter.

Overview of PSAX Site-Specific Configuration

The properties of a PSAX system and its primary CPUn module display in the Site-Specific page of the Site-Specific tab (see Figure 4-1). You can also use this page to set many of these properties. Some values, such as the switch IP address, must be set by a direct connection to the serial console port on the PSAX system.

Note: You cannot access or manage a PSAX device until its site-specific, CPUn module(s), and Stratum 3–4 module(s) values have been configured.

This chapter describes how to do the following tasks:

• Configure Stratum 3–4 module parameters

Table 4-1. Site-Specific Tab Options Not Documented in This Chapter

To use this page... see...

ATM Trunking Chapter 5 of this guide

Bulk Stats Configuration Navis® EMS-PSAX Interface and Connection Provisioning Guide

DSP Resource Configuration Navis® EMS-PSAX Module Configuration Guide

GR303 System-Wide Chapter 11 of this guide

H.248 Configuration Chapters 12 and 13 of this guide

In-Band Mmgt Navis® EMS-PSAX Interface and Connection Provisioning Guide

TASM Navis® EMS-PSAX Module Configuration Guide

Trap Activation Chapter 7 of this guide

V5 Configuration Chapter 14 of this guide


255-700-762R11.1 4-1

Chapter 4 Site-Specific ConfigurationOverview of PSAX Site-Specific Configuration

• Configure CPUn module parameters

• Configure date, time, and ID parameters for the PSAX device

• Configure the TCP Client/Server for a Connection Gateway

• Configure SNMP trap destinations and source types

• Configure ATM addresses and OAM properties

• Enable system-wide features

• Configure call control resource allocation

• Configure and view ATM trunking components

• Create, view, and delete a protection group

• Create, view, and delete entries within a protection group

• Configure IP throttling

• Configure, view, update, and delete N:1 protection groups

• View N:1 protection slot configurations

• Perform N:1 protection slot switchovers

• Save configuration values


4-2 255-700-762R11.1


Chapter 4 Site-Specific ConfigurationOverview of PSAX Site-Specific Configuration


The Site-Specific page contains the following panels as described in Table 4-2.

You can set the properties of the PSAX system by entering data on the vari-ous panels of the Site-Specific page, as described in the following procedures.

Note: The Reset button on the Site-Specific page restores all modified values to the last applied settings, regardless of whether or not you select Device > Save PSAX Configuration in the Device Menu Bar before terminating the EMS-PSAX session. If you click Reset after you click Apply, the EMS-PSAX will poll the MIB for the current settings.

Button Function

Apply Executes configuration changes on the PSAX device made in the Site-Specific page in the EMS-PSAX. To save changes to the PSAX system, click Device > Save PSAX Configuration in the Device Menu Bar.

(See the section, “Saving Configuration Values.”)

Reset Restores all of the fields in the Site-Specific page to the lat-est values that were applied to the device.

Table 4-2. Panel Descriptions for the Site-Specific Page

Panel Name Description

System Identification Displays data that identifies the CPUn module.Note: The switch IP address and IP mask must be set locally over the serial console port on the CPUn module.

System Date and Time Displays the calendar and time of day set-tings for a PSAX system.

SNMP Trap Destina-tions and Source Type

Displays the IP addresses to which you want the PSAX system to send SNMP traps. These traps indicate significant events that occur on the switches. Note: The EMS-PSAX GUI is updated based on the SNMP traps. In order for EMS-PSAX to run properly, the IP address for the management station on which the EMS-PSAX server resides must be desig-nated as one of the five SNMP trap desti-nations for the managed PSAX system.

TCP Server Configura-tion

Defines the parameters of a TCP/IP session between a PSAX device and an external call controller. The PSAX device communi-cates with call controllers using connection gateway application programming inter-face (API) configuration.

Master ATM Address and OAM Related Data

Displays the Master ATM address, the loopback, and debouncing period.

255-700-762R11.1 4-3


Chapter 4 Site-Specific ConfigurationConfiguring the Stratum 3–4 Module

Before proceeding with the site configuration, you must first determine the actual values you use for the following configuration identifiers:

• Site name

• Site identifier

• Switch master IP address

• Ethernet mask address

• Gateway address

• IP addresses of remote network managers configured to receive SNMP traps

Configuring the Stratum 3–4 Module

WARNING:!You must configure the Stratum 3–4 module before configuring any I/O modules. Once the Stratum 3–4 module is configured, it provides the ref-erence clock to all module ports configured for local timing. The proce-dure in this section describes how to establish the source of the system synchronization.

Perform the steps in the following procedure to configure the Stratum 3–4 module.

Begin

1 In the Front Panel, on a PSAX 1250, PSAX 2300, or PSAX 4500 device, double-click the Stratum 3–4 module’s external timing port (see Figure 4-2, Figure 4-3, or Figure 4-4). For a PSAX 1000 device, click Device > View Stratum Configuration in the Provisioning Menu Bar.

The Primary Stratum Configuration window is displayed (see Figure 4-5 through Figure 4-8).

When you select LineTiming in the Synchronization Source field, the Primary Line Source and the Secondary Line Source fields become active. When you select LineTiming in the Synchronization Source field and click Apply, the Switch Line Timing Source button become active.

2 Enter values for the fields on this window according to the information provided in Table 4-3.

3 Click Apply > Close.

End

For more information on the hardware and functionality of the Stratum 3–4 modules, see any of the following documents:

• PacketStar® PSAX Multiservice Media Gateways PSAX Timing Options Technical Note

• PacketStar® PSAX Multiservice Media Gateways PSAX 1000 Stratum 3–4/-48 V dc Power Supply Module Description and Specifications

• PacketStar® PSAX Multiservice Media Gateways PSAX 1000 Stratum 3–4/24 V dc Power Supply Module Description and Specifications

4-4 255-700-762R11.1



• PacketStar® PSAX Multiservice Media Gateways PSAX 1000 Stratum 3–4/110/220 V dc Power Supply Module Description and Specifications

• PacketStar® PSAX Multiservice Media Gateways PSAX 1250/2300/4500 Stratum 3–4 Module Description and Technical Specification

• PacketStar® PSAX 1000/1250/2300/4500 Multiservice Media Gateway User Guide

Figure 4-2. Front Panel View of the Stratum 3–4 Module (Used in the PSAX 1250 Chassis)

Port Timing External

255-700-762R11.1 4-5



Figure 4-3. Front Panel View of the Stratum 3–4 Module (Used in the PSAX 1000 and PSAX 2300 Chassis)

External Timing Port

4-6 255-700-762R11.1



Figure 4-4. Front Panel View of the Stratum 3–4 Module (Used in the PSAX 4500 Chassis)

External Timing Port

255-700-762R11.1 4-7



Figure 4-5. Primary Stratum Configuration Window (PSAX 1000)


4-8 255-700-762R11.1





255-700-762R11.1 4-9



The buttons in these windows have the following functions:

Button Function

Switch Line Tim-ing Source

Switches between the primary and secondary line timing sources specified in the Primary Line Source and Secondary Line Source fields. This button appears only when LineTiming is selected in the Synchronization Source field.

Apply Applies the configuration.

Reset Clears the values to the last applied configuration settings.


Table 4-3. Stratum Configuration Window Field Descriptions

Field Name Mode of Operation Description

Primary Stratum Mode(display only)

Default: Holdover

Range: N/A

Format: Predefined

Indicates the current mode of operation for the pri-mary Stratum 3–4 module.

Holdover Indicates that the primary module has lost its syn-chronization source because of excessive frequency offset and that the Holdover timing mode is main-taining chassis timing.

Freerun Indicates that the primary module is operating from the internal clock source either by design or because the Holdover timing mode has excessive frequency offset.

Synchronized3 Indicates the module clock circuitry is locked to a Stratum3 level of precision.


CardRemoved Indicates that the primary Stratum 3–4 module is not present.

4-10 255-700-762R11.1



Backup Stratum Mode(display only)

Default: Holdover

Range: N/A

Format: Predefined

Indicates the current mode of operation for the backup Stratum 3–4 module.

Holdover Indicates that the backup module has lost its syn-chronization source because of excessive frequency offset and that the Holdover timing mode is main-taining chassis timing.

Freerun Indicates that the backup module is operating from the internal clock source either by design or because the Holdover timing mode has reached excessive frequency offset.



CardRemoved Indicates that the backup Stratum 3–4 module is not present.

Line Timing Status(display only)

Default: None

Range: N/A

Format: Predefined

Indicates the current line timing status for the module.

None Indicates that the system timing is not being pro-vided by the line timing source.

PrimaryLine Indicates that the system timing is provided by the slot and port of the module specified as the Primary Line Source when LineTiming is selected as the synchronization source.

SecondaryLine Indicates that the system timing is provided by the slot and port of the module specified as the Second-ary Line Source when LineTiming is selected as the synchronization source and the primary line source has been removed or failed.

Table 4-3. Stratum Configuration Window Field Descriptions (Continued)


255-700-762R11.1 4-11



Primary Stratum Input Port Status(display only)

Default: Unconfig-ured

Range: N/A

Format: Predefined

Indicates the status of the input T1BITS or E1ETSI clock source connected to the external clock con-nector on the primary Stratum 3–4 module.

Unconfigured Indicates the T1BITS or E1ETSI clock source is not connected to the external clock connector.

noalarm Indicates the connected T1BITS or E1ETSI clock source is functioning properly.

portAIS Indicates the connected T1BITS or E1ETSI clock source is reporting an alarm indication signal.

portLOF Indicates the connected T1BITS or E1ETSI clock source is reporting a loss of frame.

portLOS Indicates the connected T1BITS or E1ETSI clock source is reporting a loss of signal.

portFOS Indicates the connected T1BITS or E1ETSI clock source is reporting a frequency offset.

Backup Stratum Input Port Status(display only)


Range: N/A

Format: Predefined

Indicates the status of the input T1BITS or E1ETSI clock source connected to the external clock con-nector on the baclup Stratum 3–4 module.

Unconfigured Indicates T1BITS or E1ETSI clock source is not con-nected to the external clock connector.

noalarm Indicates the connected T1BITS or E1ETSI clock source is functioning properly.

portAIS Indicates the connected T1BITS or E1ETSI clock source is reporting an alarm indication signal.

portLOF Indicates the connected T1BITS or E1ETSI clock source is reporting a loss of frame.

portLOS Indicates the connected T1BITS or E1ETSI clock source is reporting a loss of signal.

portFOS Indicates the connected T1BITS or E1ETSI clock source is reporting a frequency offset.

Accuracy Default: Stratum3

Range: N/A

Format: Predefined

Indicates the precision of the clock circuitry when it locks to the selected external synchronization source (CompositeClock, CompositeClock-DS0A, T1BITS, and E1ETSI, selected in the Syn-chronization Source field).

Stratum3 Indicates the timing source has a Stratum3 level of precision for a PSAX 1250/2300/4500 chassis. Indi-cates the timing source has a Stratum3+ level of precision for a PSAX 1000 chassis.

Stratum4 Indicates the timing source has a Stratum4 level of precision.



4-12 255-700-762R11.1



On Reference Clock Failure Go To

Default: Freerun

Range: N/A

Format: Predefined

Indicates what timing source is used when the selected synchronization source fails, except LineTiming. If LineTiming is selected, both the Primary Line Source and Secondary Line Source clocks must fail before reverting to this clock.

Freerun Indicates that the module switches to freerun if the selected synchronization source fails.

Holdover Indicates that the module switches to holdover mode if the selected synchronization source fails.

Synchronization Source

Default: LineTiming

Range: N/A

Format: Predefined

Indicates the synchronization source to be used by the chassis and specified I/O modules. The I/O modules use this source when LocalTiming is selected in the Transmit Clock field that appears on most channel and port configuration windows.

LineTiming Indicates that the synchronization source is to be provided through the slot and port specified in the Primary Line Source or upon failure of the Primary Line Source in the Secondary Line Source fields. Any data rate can be selected on either line source; the module does not care what rate is chosen. If LineTiming is selected, the Primary Line Source and the Secondary Line Source fields and the Switch Line Timing Source button become selectable.

Freerun Indicates that the synchronization source is to be provided through the internal clock of the Stratum 3–4 module.

CompositeClock Indicates that the synchronization source is to be provided through the external composite clock (64 Kbps) connected to the external clock connec-tor on the primary Stratum 3–4 module.

CompositeClock-DS0A

Indicates that the synchronization source is to be provided through the external composite clock (64 Kbps) connected to the external clock connec-tor on the primary Stratum 3–4 module. This option is only used by the 12-Port Medium-Density DS1/E1/DS0A CES module when operating in the DS0A mode.

T1BITS Indicates that the synchronization source is to be provided through the external T1BITS clock (1.544 Mbps) connected to the external clock con-nector on the primary Stratum 3–4 module.

E1ETSI Indicates that the synchronization source is to be provided through the external E1ETSI clock (2.048 Mbps) connected to the external clock con-nector on the primary Stratum 3–4 module.



255-700-762R11.1 4-13



Revertive Line Tim-ing Usage

Default: Disabled

Range: N/A

Format: Predefined

Controls the stratum revertive line timing feature between the primary and secondary line timing sources when LineTiming is selected through the Synchronization Source field. This feature only affects the line timing sources and does not affect the external timing sources.

Disabled Select to disable the revertive line timing feature in the PSAX system. This selection also returns the switching between secondary and primary line tim-ing sources to a non-revertive mode (user interven-tion required).

Wait to Restore Timer

Default: 0300

Range: 10–7200

Format: Numeric (sec)

This timer starts after the primary line timing source is restored, and is reset by any failure of the Stratum 3–4 module. Once the timer expires, a switch over to the primary line timing source is ini-tiated. This field is reset to 300 seconds each time the Revertive Line Timing Usage field transitions from Enabled to Disabled.

Ssm Byte Usage Default: Disabled

Range: N/A

Format: Predefined

Controls the usage of the synchronization status messages (SSMs) on OCn/STMn modules in the PSAX system.

Disabled Select to disable the SSMs on the OCn/STMn mod-ules in the PSAX system.

Enabled Select to enable the SSMs on the OCn/STMn mod-ules in the PSAX system.



4-14 255-700-762R11.1



Ssm RX Byte Default: QL_DNU

Range: N/A

Format: Predefined

Displays the contents of the incoming SSM bits on the port the Stratum 3–4 module is using for line timing. The field values represent the clock source quality level (QL) of the SSMs.

QL-DNU Indicates the signal carrying this SSM shall not be used for synchronization because a timing loop sit-uation could result if it is used.

GL-INVn Indicates an unallocated SSM value is received where n=0, 1, 3, 5, 6, 7, 9, 12, 13, or 14.

GL-PRC Indicates the source of the trail is a PRC clock as defined in Recommendation ITU-T G.811.

GL-SEC Indicates the source of the trail is a SEC clock as defined in Recommendation ITU-T G.813, Option I.

GL-SSUL Indicates the source of the trail is a Type VI SSU clock as defined in Recommendation ITU-T G.812.

GL-SSUT Indicates the source of the trail is a Type I or V SSU clock as defined in Recommendation ITU-T G.812.



255-700-762R11.1 4-15



Ssm Tx Byte Default: QL_DNU

Range: N/A

Format: Predefined

Displays the contents of the SSM bits transmitted by all the OCn/STMn module ports. The port which is active for the purpose of stratum line timing transmits QL-DNU. All of the other OCn/STMn modules transmit the SSM bits shown in this field.

QL-DNU Indicates the signal carrying this SSM shall not be used for synchronization because a timing loop sit-uation could result if it is used.

GL-INVn Indicates an unallocated SSM value is received where n=0, 1, 3, 5, 6, 7, 9, 12, 13, or 14.

GL-PRC Indicates the source of the trail is a PRC clock as defined in Recommendation ITU-T G.811.

GL-SEC Indicates the source of the trail is a SEC clock as defined in Recommendation ITU-T G.813, Option I.

GL-SSUL Indicates the source of the trail is a Type VI SSU clock as defined in Recommendation ITU-T G.812.

GL-SSUT Indicates the source of the trail is a Type I or V SSU clock as defined in Recommendation ITU-T G.812.

Primary Line Source

Default: Slot: 00 Port: 00

Range: Chassis/mod-ule dependent

Format: Numeric

Specifies the primary line source when LineTim-ing is selected in the Synchronization Source field. Enter the values for the slot and the port of the desired I/O module port that is providing line timing.



4-16 255-700-762R11.1


Chapter 4 Site-Specific ConfigurationConfiguring CPU Module Parameters for System Identification

Configuring CPU Module Parameters for System Identification

To configure a CPUn module by setting the identification values for your PSAX device, perform the steps in the following procedure.

Begin

1 In the Device window, click the Site-Specific tab.

The Site-Specific page appears.

2 Select the values for the fields in the System Identification panel (see Figure 4-9) as described in Table 4-4.

Secondary Line Source

Default: Slot: 00 Port: 00

Range: Chassis/mod-ule dependent

Format: Numeric

Specifies the secondary line source when LineTim-ing is selected in the Synchronization Source field. Enter the values for the slot and the port of the desired I/O module port that is providing line tim-ing. Leave the default value if you do not want to specify a secondary line source. If both line sources fail, timing reverts to the timing source selected in the On Reference Clock Failure Go To field.

Slot Default: 00

Range: Depends on chassis.

Format: Numeric

Displayed as part of the Primary Line Source and Secondary Line Source fields. Select the slot in the PSAX system that contains the desired I/O module you want to use as the primary or secondary line source.

Port/VPN ID Default: 00

Range: Primary Line Source, depends on the number of ports on the module selected in the Slot field; Secondary Line Source, 00–30, or All

Range: Numeric

Displayed as part of the Primary Line Source and Secondary Line Source fields. Select the port of the I/O module you selected in the Slot field that is pro-viding line timing as the primary or secondary line source. For the number of ports on a module, refer to the appropriate PSAX module user guide.



Figure 4-9. System Identification Panel

255-700-762R11.1 4-17


Chapter 4 Site-Specific ConfigurationConfiguring CPU Module Parameters for System Identification

If the fields already contain data, you can type directly over the high-lighted data to change the values. Use the left mouse button to move between the fields.

3 Click Apply.

4 In the Device Menu Bar, select Device > Save PSAX Configuration. (See the section, “Saving Configuration Values.”)

End

Rules for Configuring IP Addresses

Use the following rules when configuring the CPU IP address (CPU IP Addr field), the switch IP address (Switch IP Addr field), and the in-band IP address (IP Mask field) on the Site-Specific Configuration window:

1. The CPU IP address is always necessary, and you must not leave it as zero. However, you can enter the switch IP address in a redundant sys-tem.

2. The CPU IP and switch IP addresses cannot be the same.

Table 4-4. System Identification Panel on the Site-Specific Configuration Window Field Descriptions


Site Name Default: N/A

Range: 1–19

Format: Alphanumeric

Specifies the site name that you define for this PSAX system. Enter a site name having no more than 19 characters of the following types: alpha-numeric, - (hyphen), and _ (underscore). Do not use spaces or periods.

Switch IP Address(display only)

Default: 0.0.0.0

Range: N/A

Format: Valid dotted quad

Specifies the IP address that identifies the PSAX system. This field is only required to be set if you have a redundant PSAX system. Determine from your network configuration plan the IP address you want to use.

IP Mask (display only)

Default: 0.0.0.0

Range: N/A


Specifies the IP mask for Ethernet access to your PSAX system. This field determines which part of the IP address is the network identifier, and shows the subnet mask of the network.

Gateway Address Default: 0.0.0.0

Range: N/A


Specifies the Ethernet address of the router, which will act as a gateway that the PSAX system will use to access other networks. Leave this field blank if you are not using a router.

CPU IP Address(display only)

Default: 0.0.0.0

Range: N/A


Specifies the IP address of the active CPU module for the PSAX system. Determine from your net-work configuration plan the IP address you want to use.

Note: Do not leave this field value as 0.

4-18 255-700-762R11.1


Chapter 4 Site-Specific ConfigurationConfiguring the Date and Time for the PSAX Device

3. The CPU IP and switch IP addresses cannot be on the same subnet as the in-band IP addresses.

4. The switch IP and in-band IP management addresses may each be zero.

Note: If the CPU IP address is zero and the ssid file on the CPUn mod-ule is corrupted, the system cannot access the Ethernet.

5. If the CPU IP, switch IP, and in-band IP addresses are not zero, then they must be valid IP addresses.

6. If the switch IP address is not zero, then the system will respond to the switch IP address; otherwise, the system will respond to the the CPU IP address on the Ethernet port.

7. The gateway IP address cannot be the same as the CPU IP and switch IP addresses.

8. In a redundant system, both CPUn modules must have a unique CPU IP address. They will have the same switch IP address and in-band IP address if either address is defined. After initial setup, the IP settings can be modified only on the active CPUn module.

Rules for Configuring IP Address Masks

Use the following rules when configuring the CPU IP address and switch IP address on the Site-Specific Configuration window:

1. The CPU IP address and switch IP address share the same IP mask.

2. The CPU IP address (or switch IP address) and in-band IP address masks are independent of each other, as long as the CPU IP address (or switch IP address) and in-band IP address are in different networks.

3. If the CPU IP address (or switch IP address) and in-band IP address are in the same class, then their masks must be the same.

4. The CPU IP address and switch IP address must always be on a different subnet from the in-band IP address; CPU IP and switch IP addresses can-not be on the same subnet as the in-band IP address.

Configuring the Date and Time for the PSAX Device

The System Date and Time panel on the Site-Specific page lets you view and enter information about the date and time when managing a PSAX device.

To set the date and time for a PSAX device, perform the steps in the following procedure.

Begin



255-700-762R11.1 4-19


Chapter 4 Site-Specific ConfigurationConfiguring the Date and Time for the PSAX Device

2 Select the values for the fields on the System Date and Time panel (see Figure 4-10) as described in Table 4-5.

If a field already contains a value, you can type directly over the high-lighted data to change its value. Use the left mouse button to move between the fields.

3 Click Apply Date and Time.


End

Figure 4-10. System Date and Time Panel

Table 4-5. System Date and Time Panel on the Site-Specific Configuration Window Field Descriptions


Month/Day/Year Default: today’s date

Range: N/A

Format: Numeric (mm/dd/yyyy)

Specifies the current date in month (mm), day (dd), and year (yyyy). Enter the current date in the format: mm/dd/yyyy (2-digit values for the month and the day, and a 4-digit value for the year).

Hours: Mins: Secs (UTC)

Default: current time

Range: N/A

Format: Numeric (24-hour format [HH:MM:SS])

Specifies the current time for your location in Universal Time Coordinated (UTC) format (24-hour format) (also known as Greenwich Mean Time [GMT]).

Local Time(display only)

Default: current time

Range: N/A

Format: Numeric (12-hour format [HH:MM:SS] am or pm)

Displays the local time of the PSAX system in 12-hour format with the am or pm indicator.

Note: The date and time stamp in the EMS-PSAX system trap log is derived from the EMS-PSAX management workstation clock, not the clock settings internal to the managed PSAX device.

Temperature (C)(display only)

Default: N/A

Range: N/A

Format: Numeric (degrees Celsius)

Displays the ambient temperature where the PSAX system is located.

4-20 255-700-762R11.1


Chapter 4 Site-Specific ConfigurationConfiguring the TCP Client/Server for a Connection Gateway

Configuring the TCP Client/Server for a Connection Gateway

If you are using the Connection Gateway API with the PSAX device, you need to configure the system as either a TCP client or as a TCP server. If you set up the CG device as a TCP server, you can connect multiple PSAX devices as TCP clients (see Figure 4-11).

You can also set up the PSAX device as a TCP server with the CG device as the client. As an option, you can connect two CG devices (clients), set up as primary and backup CG devices, to the PSAX device (server) (see Figure 4-12).

Figure 4-11. PacketStar® PSAX System as a TCP Client

In-bandManagement

PVC Connection

Local Access Concentrator(Primary TCP Client)

Call Controller Device (Computer)

(TCP Server)

ATM I/OModule

EthernetModule

Ethernet Hub

ATM I/OModule

Remote Access Concentrator(TCP Client)

ATM I/OModule

Local Access Concentrator(Backup TCP Client)

In-bandManagement

PVC Connection

EthernetModule

ATMWAN

ATMWAN

255-700-762R11.1 4-21



The TCP Server Configuration panel on the Site-Specific page lets you con-nect a PSAX system to an external call controller using the Connection Gate-way API configuration (also known as a Signaling Gateway API).

To configure the PSAX device as a TCP client or server, perform the steps in the following procedure.

Begin



2 Select the values for the fields in the TCP Server Configuration panel of the Site-Specific page (see Figure 4-13) as described in Table 4-6.

If a field already contains a value, you can type directory over the high-lighted data to change its value. Use the left mouse button to move between the fields.

3 Click Apply.

Figure 4-12. PacketStar® PSAX System as a TCP Server

Figure 4-13. TCP Server Configuration Panel

Call Controller Device-Primary (Computer)

(TCP Client)

Call Controller Device-Backup (Computer)

(TCP Client)

EthernetConnection

EthernetHub

EthernetConnection

EthernetModule

ATM I/OModule

Local Access Concentrator(TCP Server)

ATM I/OModule

Remote Access Concentrator(TCP Server)

ATMWAN

In-bandManagement

Connection

Route ServerModule

4-22 255-700-762R11.1




End

Table 4-6. TCP Server Configuration Window Field Descriptions


Mux TCP Type Default: Client

Range: N/A

Format: Predefined

Specifies how the PSAX system is defined for the TCP connection between the PSAX system and the connection gateway for messages transmitted through the Connection Gateway API. If the PSAX system is designated as the client device, the PSAX system establishes the connection to the connection gateway. If the PSAX system is designated as the server device, the connection gateway establishes the connection to the PSAX system.

Client Indicates that the PSAX system is serving as the client device.

Server Indicates that the PSAX system is serving as the server device.

Server IP Address Default: 0.0.0.0

Range: N/A


Note: Specifies the IP address of the server, such as the call controller. This field is displayed only if you selected Client in the Mux TCP Type field on the Site-Specific page.

Server Port Number Default: 1025

Range: 1025–65535 (excluding 5000, 5009, and 6000)

Format: Numeric

Specifies the TCP server port number. This num-ber must be a valid number based on the agree-ment between the connection gateway and the call controller.

Keep-alive Timer (secs)

Default: 0

Range: 1–100


Specifies the interval of time that elapses before the TCP server sends a query message to deter-mine whether the connection is still active.

Inactive Timer (secs)

Default: 0

Range: 1–100


Specifies the amount of time that the server is inactive before the TCP/IP session is automati-cally terminated.

Client IP Address Default: 0.0.0.0

Range: N/A


Specifies the IP address of the client. This field is displayed only if you selected Client in the Mux TCP Type field on the Site-Specific page.

255-700-762R11.1 4-23


Chapter 4 Site-Specific ConfigurationConfiguring System-Related Data

Configuring System-Related Data

Perform the following procedure to configure the System Related Data panel.

Begin

Entering Your System Master ATM Address



2 Select a value for the field in the System Related Data panel (see Figure 4-14) as described in Table 4-7.

End

Figure 4-14. System Related Data Panel

Table 4-7. System Related Data Panel on the Site-Specific Configuration Window Field Descriptions

Field Name Field Value Description

I/O Module Audit Feature

Default: Enabled

Range: N/A

Format: Predefined

Indicates whether the I/O modules are synchronized with the CPU module if they get out of synchronized due to CPU switchovers or backplane errors.

Enabled Select to enable I/O modules to synchronize with the CPU module after CPU switchovers or backplane errors occur.

Disabled Select to disable I/O modules from synchronizing with the CPU module after CPU switchovers or backplane errors occur.

4-24 255-700-762R11.1


Chapter 4 Site-Specific ConfigurationConfiguring System-Related Data

Active Alarm Table

Default: Disabled

Range: N/A

Format: Predefined

Indicates whether the Alarm Status Table feature allows events that are generated in the PSAX chassis to be saved in the CPU module and displayed in the Active Alarm Table window. The Active Alarm Table can display a max-imum of 200 events. When the number exceeds 200 then the less priority events in the table are replaced with the current high priority events.

Enabled Select to enable the Alarm Status Table feature. Indicates the events that are raised, updated, or modified are recorded and displayed in the Active Alarm Table in the EMS-PSAX.

Note: In order for EMS-PSAX to display the events, the Active Alarm Table field must be enabled in the Site-Spe-cific window.

Disabled Indicates the events that are raised, updated, or modified are not displayed in the Active Alarm Table in the EMS-PSAX.

Connection Name On Traps Feature

Default: Disabled

Range: N/A

Format: Predefined

Indicates whether the Connection/Interface Name on Trap feature appends assigned connection names or inter-face names to SNMP trap messages generated from mod-ule-configured interfaces or connections. The feature extends the ability to better identify trap messages as opposed to using slot, port, and channel information.

Enabled Select to enable the Connection/Interface Name on Trap feature. Trap messages are viewed from the Trap Log Dis-play window and transmitted to an appropriate NMS. Additional trap message information can be found in the PacketStar® PSAX Simple Network Management Protocol (SNMP) Trap Reference Guide. Additional connection name and interface name information can be found in the Pack-etStar® PSAX Connections Provisioning Guide.

Disabled Select to disable the Connection/Interface Name on Trap feature.

Auto Restart All Calls

Default: Disabled

Range: N/A

Predefined

Indicates whether the Auto Restart All Calls restarts all the SPVCs on the transit switch when the link becomes active.

Enabled Indicates that the Auto Restart All Calls feature is enabled. This will restart all the SPVCs on the transit switch.

Disabled Indicates that the Auto Restart All Calls feature is dis-abled. This will restart only the SPVCs that are enabled for auto restart feature on the transit switch.

Table 4-7. System Related Data Panel on the Site-Specific Configuration Window Field Descriptions (Continued)


255-700-762R11.1 4-25


Chapter 4 Site-Specific ConfigurationATM Addresses and OAM Properties

ATM Addresses and OAM Properties The Master ATM Address and OAM Related Data panel allows you to enter and display information about the master ATM address, loopback location, and OAM debouncing period. The loopback feature is an aid for trouble-shooting and testing. Some modules contain several types of loopback config-urations, which transmit a received signal back to the source to verify the integrity of a port.

Perform the steps in the following procedure to configure the loopback parameters on modules that support loopback configuration.

Begin



2 Select the values for the fields in the Master ATM Address and OAM Related Data panel (see Figure 4-15) as described in Table 4-8.

If a field already contains a value, you can type directly over the high-lighted data to change its value. Use the left mouse button to move between the fields.

3 Click Apply.

4 Clicking Reset before performing the next step reverts the Site-Specific page to its the previous configuration.


End

Figure 4-15. Master ATM Address Type and OAM Related Data Panel

4-26 255-700-762R11.1


Chapter 4 Site-Specific ConfigurationConfiguring SNMP Trap Destinations and Source Types

Configuring SNMP Trap Destinations and Source Types You can configure the EMS-PSAX to send SNMP traps to a remote NMS, to alert the NMS that a configuration problem exists for a PSAX device.

To set the destinations for SNMP trap messages from a PSAX device, and the source types for the destinations using the Notify And Target Address Table page, you must be logged into the EMS-PSAX as a valid user in SNMPv3 mode (see Chapter 3 for SNMPv3 instructions).

Begin

1 In the Device window, click the Notify And Target Address Table tab.

Table 4-8. Master ATM Address and OAM Related Data Panel on the Site-Specific Configuration Window Field Descriptions


Master ATM Address (Hex)

Default: 0000.0000. 0000.0000.0000. 0000.0000.0000. 0000.0000

Range: N/A

Format: Hexadecimal

Indicates the master node address where the SNMP traps will be sent (20 octets). The address must start with 39, 45, or 47, depending on your world region.

Master ATM Address Type

Default: Nsap

Range: N/A

Format: Predefined

Nsap, E164, E164nsap

Indicates the type of address used for the master node ATM address. Select an address type from the pull-down menu: Nsap, E164, or E164nsap.

Loopback Location ID (Hex)

Default: FFFF.FFFF. FFFF.FFFF.FFFF. FFFF.FFFF.FFFF

Range: N/A

Format: Hexadecimal

Indicates the unique identifier of the ATM node where the loopback is to occur (8 octets).

Loopback Location ID is the location identifier of the local switch. It is used as the “Source Location Id” in all the outgoing OAM loopback cells and will be compared with the “Destination Location Id” of a received OAM loopback cell to decide if the received OAM loopback cell should be looped back by this switch or not. You must enter a unique value in the Loopback Location ID field to perform OAM loopback tests.

For more information about OAM loopback tests, see Chapter 5, “Using System Diagnostics.”For more information about performing OAM loop-back tests, see Chapter 8.

Debouncing Period (msecs)

Default: 3000

Range: 1000–300000

Format: Numeric (msec)

Indicates the maximum time for clearing OAM AIS and RDI alarms.

255-700-762R11.1 4-27



The Notify And Target Address Table page appears (see Figure 4-16).

All stations running the EMS-PSAX server must be displayed in the Name column. Each transport address defines a network manager (up to five total).

The management workstation on which the EMS-PSAX is running must be designated to receive traps from each target PSAX device. If the EMS-PSAX detects that the management station IP address is not one of the SNMP trap destinations for the PSAX device, the EMS-PSAX displays a message, offering to automatically enter the address. Click OK to have the EMS-PSAX modify the configuration for you, or click Cancel and enter the address manually on the Notify And Target Address Table page.

2 Right-click within the table and select Update.

The UPDATE Notify And Target Address Table Entry window appears (see Figure 4-17).

3 In the UPDATE Notify And Target Address Table Entry window, select from the following values as described in Table 4-9:

4 Repeat Step 3 for up to five different sources.

5 Click Update > Close.

Note: Clicking Reset before performing Step 6 reverts this window to its the previous configuration.

Figure 4-16. Notify and Target Address Table Page

Figure 4-17. UPDATE Notify and Target Address Table Entry Window

4-28 255-700-762R11.1




End

Table 4-9. Notify and Target Address Table Entry Window Field Descriptions


Notify/Target Address Name

Default: N/A

Range: NMS 1–NMS 5

Format: Predefined

Identifies the first through fifth network manage-ment systems to which you want SNMP trap messages to be sent.

Notification Type Default: SNMPv1Trap

Range: N/A

Format: Predefined

Indicates the type of notification. An inform is an acknowledged notification. A trap is an un-acknowledged notification.

Note: If you are managing PSAX devices using in-band management SVC connections, it is rec-ommended that you configure the notification type as SNMPv2cInform or SNMPv3Inform.

SNMPv1Trap Send SNMP traps with v1Readonly community string in SNMPv1 trap format. This option does not support authentication or privacy.

SNMPv2cTrap Send SNMP traps with v1Readonly community string in SNMPv2 trap format. This option does not support authentication or privacy.

SNMPv3Trap Send SNMP traps with a user-specified USM user name in v3 trap format. The user may also select a security level.

SNMPv2cInform Send SNMP informs with v1Readonly commu-nity string in v2 inform format. This option does not support authentication or privacy.

SNMPv3Inform Send SNMP informs with a user-specified USM user name in v3 inform format. The user may also select a security level.

Destination/Target Address

Default: 000.000.000.000

Range: 000–255


Specifies the IP address of the network manage-ment system to which you want SNMP trap mes-sages to be sent.

255-700-762R11.1 4-29



Source Interface Default: Interface

Range: N/A

Format: Predefined

Indicates the IP address of the source system that will send the SNMP traps to the network man-agement system.

Note: This value is only used when the Notify Type is set to SNMPv1Trap, otherwise the value is ignored.

Interface Specifies that the source of PSAX trap messages is the IP address of the interface you use to connect the PSAX system to the IP network.

If you have a complicated network configuration, as described in the description for the value Ethernet, Lucent recommends that you select Ethernet.

Ethernet Specifies that the source of PSAX trap messages is the IP address you entered in the Switch IP Addr. field. This IP address for your PSAX system is associated with your Ethernet network.

Use this value if you want to manage the PSAX system using the switch (PSAX system) IP address, but can only access the PSAX system through the in-band management (IBM) inter-face; for example, you have a router entry for the switch IP address pointing to the IBM IP address as the next hop. Even though you are not access-ing the PSAX system through the Ethernet port on the CPU module, the PSAX system associates the IP address in the Switch IP Addr. field with the Ethernet port.

Ibm Specifies that the source of PSAX trap messages is the primary IP address for in-band management. You set this address in the Primary IP Address field on the In-Band Management IP Configura-tion window.

Timeout Interval Default: 100

Range: 0–2147483647

Format: Numeric

Indicates the maximum round trip time, in hun-dredths of seconds, for communicating with the transport address. When a message is sent to this address, and a response (if one is expected) is not received within this time period, it is assumed that the response will not be delivered.

Note: This field appears only when the value SNMPv2cInform or SNMPv3Inform is selected in the Notification Type field.

Table 4-9. Notify and Target Address Table Entry Window Field Descriptions (Continued)


4-30 255-700-762R11.1


Chapter 4 Site-Specific ConfigurationEnabling System-Wide Features

Enabling System-Wide Features

To enable or disable system-wide features for your EMS-PSAX, perform the steps in the following procedure.

Begin



Retry Times Default: 3

Range: 0–255

Format: Numeric

Specifies the number of retries to be attempted when a response is not received for a generated message. An application may provide its own retry count, in which case the value of this object is ignored.

Note: This field appears only when the value SNMPv2cInform or SNMPv3Inform is selected in the Notification Type field.

USM User Name Default: N/A

Range: 1–32


Specifies the name assigned to this particular USM user. You can specify alphanumeric charac-ters including A-Z, a-z, 0-9, / (forward slash), - (hyphen), and _ (underscore). The text string is case-sensitive. The use of the space character is not supported.

Note: This field appears only when the value SNMPv3Trap or SNMPv3Inform is selected in the Notification Type field.

Security Level Default: NoAuthNoPriv

Range: N/A

Format: Predefined

Indicates the level of security at which SNMP messages can be sent or with which operations are being processed.

Note: This field appears only when the value SNMPv3Trap or SNMPv3Inform is selected in the Notification Type field.

Note: This field value must match the Security Level field value configured on the Open SNMPv3 Device window. Otherwise, you will not be able to access the PSAX device from an exter-nal SNMP manager using SNMPv3 protocol.

NoAuthNoPriv Indicates a security level without authentication and privacy.

AuthNoPriv Indicates a security level with authentication but without privacy.

AuthPriv Indicates a security level with authentication and privacy.

Table 4-9. Notify and Target Address Table Entry Window Field Descriptions (Continued)


255-700-762R11.1 4-31



2 Click the Feature Turn On/Off tab.

The Feature Turn On/Off Configuration page appears (see Figure 4-18).

3 In the Feature On/Off Configuration panel, select an entry that you wish to enable (turn on) or disable (turn off).

4 Click the right mouse button and a menu appears (see Figure 4-19).

5 To enable the feature, select Turn On Selected Feature. To disable the fea-ture, select Turn Off Selected Feature. When you select either of these options, the following window appears (see Figure 4-20).

6 The values for the fields on this window are described in Table 4-10.

7 In the Device Menu Bar, click Device > Save PSAX Configuration. (See the section, “Saving Configuration Values.”)

Figure 4-18. Feature Turn On/Off Page

Figure 4-19. Feature Turn On/Off Page Menu

Figure 4-20. Feature Turn On/Off Confirmation Window

4-32 255-700-762R11.1



8 Reboot the PSAX device so that the values you selected will take effect. See Chapter 9 for instructions.

End

Table 4-10. Feature Turn On/Off Page Field Descriptions


Feature Default: N/A

Range: N/A

Format: Pre-defined

Displays the PSAX system features that you can enable or dis-able.

Pnni Private network-to-network interface feature.

Note: Currently, this feature cannot be disabled.

Gr303 ITU-T GR-303 local loop emulation services feature. For exam-ples of applications using the GR-303 interface, see the Packet-Star® PSAX Configuring the GR-303 Voice Gateway User Guide.

Vipr Virtual Internet Protocol Router feature.

Note: This feature is not currently supported.

H248 Select this value to enable the H.248 protocol feature.

V5 European V5.2 local loop emulation services feature.

Iua ISDN Q.921 User Adaptation Layer Protocol feature. Enables OSI Layer 2 ISDN D-channel signalling between an Media Gateway Controller (for example, a Softswitch) and a Media Gateway (for example, a PSAX system) in PRI offload applications.

AtmSec Select this value to enable the ATM security feature.

BulkStats Select this value to enable the Bulk statistics feature.

CpuBridge Select this value to enable the CPU bridge feature only on the CPU3 module. See the procedure “Configuring the CPU3 Mod-ule Ethernet Bridge” on page 5-33 to configure the connection.

Minimum Memory Required (Bytes)

Default: PNNI: 0Gr303: 25165824Vipr: 262144H248: 3145728V5: 25165824Iua: 1507328AtmSec: 655360BulkStats: 262144CpuBridge: 262144

Range: N/A

Format: Numeric (bytes)

Displays the amount of system memory in bytes required by the feature.

255-700-762R11.1 4-33


Chapter 4 Site-Specific ConfigurationConfiguring Call Control Resource Allocation

Configuring Call Control Resource Allocation

Perform the steps in the following procedure to allocate call resources for a PSAX device.

Begin

1 In the Site-Specific tab, click the Call Control tab.

The Call Control page appears (see Figure 4-21).

2 Enter the values in the fields on this window according to the informa-tion provided in the following two tables.

Note: The field values shown in the following two tables are for PSAX devices running PSAX system software Release 11.1.0. To obtain the maximum number of calls supported for a different version of PSAX system software, consult the appropriate PacketStar® PSAX Multiservice Media Gateway release note.

3 To apply the values you have entered, click Apply.

An informational window appears.

4 Click OK.

Desired Status Default: Enable or Disable (depends on the feature)

Range: N/A

Format: Pre-defined

Specifies whether the feature is to be made operational or not.

Note:

Disable Indicates that the selected enabled feature is to be made non-operational. After selecting this value, you must reboot the PSAX system to make this change take effect. After the system reboots, Disabled is displayed in the current status field.

Enable Indicates that the selected disabled feature is to be made opera-tional. After selecting this value, you must reboot the PSAX sys-tem to make this change take effect. After the system reboots, Enabled is displayed in the current status field.

Current Status Default: N/A

Range: N/A

Format: Pre-defined

Displays the current operational status of the feature.

Disabled Indicates that the selected feature is currently not operational.

Enabled Indicates that the selected feature is currently operational.

Table 4-10. Feature Turn On/Off Page Field Descriptions (Continued)


4-34 255-700-762R11.1




6 Follow the instructions in “Rebooting the Device,” in this chapter, to restart hardware components so that the call control configuration val-ues will take effect on your PSAX device.

End

You can back up the data on the Call Control Resource Allocation window by backing up the file ssid.def, which resides on the CPU module system disk. Lucent highly recommends that you back up the ssid.def file, which contains your configuration data. See Chapter 9 for procedures on backing up your system software data.

The buttons on this window (not shown above) have the following func-tions:

Figure 4-21. Call Control Page

Button Function

Apply Applies the configuration field values you set.

Reset Resets the fields to the last set of applied values.

255-700-762R11.1 4-35



Figure 4-22. Call Control Confirmation Window

Table 4-11. Call Control Page Field Descriptions


Important: The ranges of values for numeric fields are software imposed. When changing the val-ues in these fields, keep in mind that the PSAX system calculates the percentage of the memory allocation usage from the combination of values you have entered in the fields. This calculation is displayed in the Call Control Resource Allocation Usage field. When all the values of SVC calls and parties, SPVC calls, CG API endpoints, and CG API calls and parties are calculated as a percentage of memory allocation, this percentage value cannot exceed 100 percent of the memory allocation. If you enter a combination of values that exceeds 100 percent when calculated by the system, the fol-lowing error message is displayed: T-CallControlResAllocFail. If you receive this error message, adjust the values in the fields and click Apply to recalculate the allocation usage percentage value. Read the configuration guidelines and the PSAX System Performance Capabilities per Node table in the preceding section before you enter values in the fields on this window.

SVC Point To Point Calls

Default: 2000

Range: 0–15000

Format: Numeric

Specifies the maximum number of SVC point-to-point calls to be supported by the PSAX system.

H.248 Applications: For AAL2, this field must be greater than or equal to the sum of the values in the atmTrunkNarrowBandCalls and atmTrunkVccs fields.

Set this field to the same value as the sgApiPtToPtSvc-Calls field. Example: If the Maximum Number of Con-texts field on the H.248 Configuration window is set to 4000 and the Maximum Number of Terminations field on that window is set to 8000, then recommended val-ues for this field are:

• AAL1: 4000

• AAL2: 4100

• AAL1/AAL2: 4100

SVC Point To Multi Point Calls

Default: 2000

Range: 0–4000

Format: Numeric

Specifies the maximum number of SVC point-to-mul-tipoint calls to be supported by the PSAX system.

H.248 Applications: Set the value in this field to 0.

SVC Point To Multi Point Parties

Default: 2000

Range: 0–4000

Format: Numeric

Specifies the maximum number of parties on SVC point-to-multipoint calls to be supported by the PSAX system.


4-36 255-700-762R11.1



SPVC Ce Point To Point Calls

Default: 1000

Range: 0–10000

Format: Numeric

Specifies the maximum number of SPVC circuit emu-lation point-to-point calls to be supported by the PSAX system.

Note: The total of all call fields and atmTrunkVccs can-not exceed 32 when the spvcGlobalPriorityScheme field is Enabled.


SPVC Te Point To Point Calls

Default: 100

Range: 0–10000

Format: Numeric

Specifies the maximum number of SPVC terminal emulation point-to-point calls to be supported by the PSAX system.



SPVC ATM Point To Point Calls

Default: 2000

Range: 0–10000

Format: Numeric

Specifies the maximum number of SPVC ATM point-to-point calls to be supported by the PSAX system.



SPVC Fr Point To Point Calls

Default: 900

Range: 0–10000

Format: Numeric

Specifies the maximum number of SPVC frame relay point-to-point calls to be supported by the PSAX sys-tem.


SPVC Point To Multi Point Calls

Default: 500

Range: 0–500

Format: Numeric

Specifies the maximum number of SPVC point-to-mul-tipoint calls to be supported by the PSAX system.


SPVC Point To Multi Point Parties

Default: 1000

Range: 0–4000

Format: Numeric

Specifies the maximum number of parties on SPVC point-to-multipoint calls to be supported by the PSAX system.


Aal2 Cir-ATM SPVC Calls

Default: 1000

Range: 0–4000

Format: Numeric

Specifies the maximum number of circuit emulation-to-ATM standard AAL2 SPVC calls to be supported by the PSAX system.


Aal2 Vbr-Atm SPVC Calls

Default: 100

Range: 0–4000

Format: Numeric

Specifies the maximum number of VBR-to-ATM stan-dard AAL2 SPVC calls to be supported by the PSAX system.


SPVC ERM Point-To-Point Calls

Default: 100

Range: 1–1000

Format: Numeric

Specifies the maximum number of Enhanced Router-to-ATM SPVC calls supported on this PSAX system.

Table 4-11. Call Control Page Field Descriptions (Continued)


255-700-762R11.1 4-37



SPVC Global Prior-ity Scheme

Default: Disabled

Range: N/A

Format: Predefined

Specifies whether the PSAX systemwide priority scheme must be supported for all SPVCs and SPVC trunks.

Disabled Indicates that the priority scheme is not in force (dis-abled).

Enabled Indicates that the priority scheme is in force (enabled). If you select the value Enabled in this field, the total number of calls specified in all of the SPVC call fields and the number of ATM trunk VCCs cannot exceed 32 calls.

Note: For SPVC reconnections in priority scheme-enabled trunks in an IMA link, the limit is 32 SPVCs.

SPVC Priority Scheme

Default: Disabled

Range: N/A

Format: Predefined

An indication that the priority scheme should be sup-ported in SPVCs.

Disabled The priority scheme is disabled for SPVCs.

Enabled The priority scheme is enabled for SPVCs.

SPVC Trunking Pri-ority Scheme

Default: Disabled

Range: N/A

Format: Predefined

An indication that the priority scheme should be sup-ported in SPVC trunks.

Disabled The priority scheme is disabled for SPVC trunks.

Enabled The priority scheme is enabled for SPVC trunks.

SPVC Global Auto Reversion Scheme

Default: Disabled

Range: N/A

Format: Predefined

Indicates that the auto reversion scheme is supported across SPVCs and SPVC trunks.

Disabled The auto reversion scheme is disabled for SPVCs and SPVC trunks.

Enabled The auto reversion scheme is enabled for SPVCs and SPVC trunks.

SPVC Global Auto Restart Feature

Default: Disabled

Range: N/A

Predefined

Indicates that the auto restart feature is supported across SPVCs on a PNNI link.

Disabled The auto restart scheme is disabled for SPVCs.

Enabled The auto restart scheme is enabled for SPVCs.



4-38 255-700-762R11.1



SPVC Auto Rever-sion Scheme

Default: Disabled

Range: N/A

Format: Predefined

An indication that the auto reversion scheme should be supported in SPVCs.

Note: The SPVC Global Auto Reversion Scheme field has to be enabled along with either the SPVC Autore-version Scheme field or SPVC Trunking Auto Rever-sion Scheme field, or both for auto reversion scheme to be enabled on a particular chassis.

Disabled The auto reversion scheme is disabled for SPVCs.

Enabled The auto reversion scheme is enabled for SPVCs.

SPVC Trunking Auto Reversion Scheme

Default: Disabled

Range: N/A

Format: Predefined

An indication that the auto reversion scheme shoul be supported in SPVC trunks.

Note: The SPVC Global Auto Reversion Scheme field has to be enabled along with either the SPVC Autoev-ersion Scheme field or SPVC Trunking Auto Reversion Scheme field, or both for auto reversion scheme to be enabled on a particular chassis.

Disabled The auto reversion scheme is disabled for SPVC trunks.

Enabled The auto reversion scheme is enabled for SPVC trunks.

Signalling Gateway Panel

SG API CirEm End Points

Default: 1000

Range:

Format: Numeric

Specifies the maximum number of circuit emulation endpoints for the Connection Gateway API to be sup-ported by the PSAX system.


SG API ATM Svc End Points

Default: 0

Range:

Format: Numeric

Specifies the maximum number of ATM SVC end-points for the Connection Gateway API to be sup-ported by the PSAX system.


Connection Gateway Panel

SCG API Point To Point Svc Calls

Default: 0

Range:

Format: Numeric

Specifies the maximum number of SVC point-to-point calls for the Connection Gateway API to be supported by the PSAX system.

H.248 Applications: Specifies the maximum number of point-to-point calls through H.248. Set this field to the same value as the svcPtToPtCalls field. Example: If the Maximum Number of Contexts field on the H.248 Configuration window is set to 4000 and the Maxi-mum Number of Terminations field on that window is set to 8000, then recommended values for this field are:

• AAL1: 4000

• AAL2: 4100

• AAL1/AAL2: 4100



255-700-762R11.1 4-39



SCG API Point To Multi Point Svc Calls

Default: 0

Range:

Format: Numeric

Specifies the maximum number of SVC point-to-mul-tipoint calls for the Connection Gateway API to be sup-ported by the PSAX system.


SCG API Point To Multi Point Parties

Default: 0

Range:

Format: Numeric

Specifies the maximum number of parties on SVC point-to-multipoint calls for the Connection Gateway API to be supported by the PSAX system.


ATM Trunking Panel

ATM Trunk VCCs Default: 100

Range: 1–1024; 1–4096 for V5 appli-cations

Format: Numeric

Specifies the maximum number of VCCs supported by ATM trunking.

H.248 Applications: Specifies the maximum number of AAL2 trunks. For AAL1 call setups, this field does not apply and should be set to 0. Example: If the Maxi-mum Number of Contexts field on the H.248 Configu-ration window is set to 4000 and the Maximum Num-ber of Terminations field on that window is set to 8000, then recommended values for this field are:

• AAL1: 0

• AAL2: 100

• AAL1/AAL2: 100

SPVC Priority Configurations: The total of all call fields and atmTrunkVccs cannot exceed 32 when the spvc-GlobalPriorityScheme field is Enabled.

V5.2 Applications: You can enter up to the value 4096. If you enter 4096, be sure that you have first freed enough resources in other fields in order to enter a high value in the atmTrunkVccs field.

ATM Trunk Nar-rowband Calls

Default: 1000

Range: 1–4000

Format: Numeric

Specifies the maximum number of switched narrow-band calls supported by ATM trunking.

H.248 Applications: Specifies the maximum number of simultaneous calls through AAL2. For AAL1 call set-ups, this field does not apply and should be set to 0. Example: If the Maximum Number of Contexts field on the H.248 Configuration window is set to 4000 and the Maximum Number of Terminations field on that window is set to 8000, then recommended values for this field are:

• AAL1: 0

• AAL2: 4000

• AAL1/AAL2: 2000



4-40 255-700-762R11.1



The maximum numbers for PVC, SPVC, and SVC duplex calls per connection type available on the PSAX system, as well as the call setup rate for all types of CPUn modules, are shown in Table 4-12.

Call Control Resource Allocation Usage

Default: N/A

Range: 0–100

Format: Numeric

Displays the percentage of memory allocated to call control. A portion of the total system memory is allo-cated for call control. The value in this field represents the amount of this allocation that is currently in use. This percentage value is calculated by the system from the values you enter in the other fields.

SVC Cut Through Option

Default: CgSvcAcI-mplicitCutThrough

Range: N/A

Format: Predefined

Specifies whether the PSAX system or the connection gateway device (connection manager) sends a cut-through message to initiate an SVC connection.

Note: The value in this field is relevant only if you have enabled a media gateway control feature (the Connection Gateway API feature or the H.248 fea-ture).

CgSvcAcImplicit-CutThrough

Indicates that the PSAX system sends a cut-through message to the connection gateway device to initiate an SVC connection.

CgSvcAcExplicit-Cuthrough

Indicates that the connection gateway device deter-mines when to send a cut-through message to the con-nection manager to initiate an SVC connection.

H.248 Applications: You must use the value cgSv-cAcExplicitCutThrough if you are using the H.248 Media Gateway Control protocol feature.

Number Of Calls Supported

Default: 60000

Range: 30000-60000

Format: Numeric

The total number of calls that a CPU module can sup-port including PVC, SVC, SPVC and others. Reducing this number can increase system memory to be used for other applications such as GR-303 or V5.2. Since the call ID range is also reduced, the calls with call IDs greater than the new ID range will be dropped in the next boot up and need to be re-established. It is recom-mended that this be changed only during a mainte-nance window. The minimum is set to 30,000 calls to ensure system functionality.



Table 4-12. PSAX System Performance Capabilities Per Node for Release 11.1.0

Connection TypeMaximum Number of Duplex Calls per Node

Call Set-up Rate for CPU2 and CPU3L Modules*

Call Set-up Rate for CPU3 and CPU4 Modules*

PVC 60,000 N/A N/A

SPVC 10,000† 60 calls per second 120 calls per second

SVC 15,000† 60 calls per second 120 calls per second

All connections combined

60,000‡

255-700-762R11.1 4-41


Chapter 4 Site-Specific ConfigurationInterface Protection Groups

End

Interface Protection Groups

The SPVC Support on Interface Protection Groups feature now provides M:N protection for interface protection groups for which SPVCs are configured. Previously, only PVC connections were supported for interface protection groups. This feature provides a many-to-many (M:N) protection scheme for a situation in which a failure condition is detected on a primary interface. Upon failure of a primary interface, the system moves all affected connec-tions from the primary interface to one of its standby interfaces based on cri-teria provided by the user.

Creating a Protection Group

To configure interface protection groups using the EMS-PSAX, perform the steps in the following procedure.

Begin



2 Click the Interface Protection tab.

The Protection Group page appears (see Figure 4-23).

* A CPU3 or CPU4 module paired in the same chassis with a CPU2 or CPU3L module will operate at the lower CPU2/CPU3L module call rate.

† When using both SPVC and SVC connection types, you can set up any combination of calls as long as you do not exceed 100% of the call control resource memory allocation (callContrlResAllocUsage field on the Call Control Resource Allocation Configuration window).Refer to the configuration guidelines in the field description table for this window.

‡ For all three types of connections, you cannot configure more than the maximum number of duplex calls indicated. For OAM monitoring the maximum number of calls that can be monitored in one direction is 2,000, and the maximum number of calls that can be monitored in both directions is 1,000.

Figure 4-23. Protection Group Page

4-42 255-700-762R11.1



3 Within the Interface Protection table panel, click the right mouse button and a menu appears (see Figure 4-24). Select Create.

The ADD Protection Group Entry window appears (see Figure 4-25).



Figure 4-24. Protection Group Table Right-Click Menu

Figure 4-25. ADD Protection Group Entry Window

Button Function

Add Adds this entry to the Interface Protection Table.

Delete Removes this entry from the Interface Protection Table. This button is displayed on the VIEW and UPDATE Protection Group Entry windows.

Reset Changes user-configurable fields to the last saved values. This button is displayed on the UPDATE Protection Group Entry window.


255-700-762R11.1 4-43



5 Click Add.

If this entry is valid, it is added to the Protection Group Table and dis-played as the UPDATE Protection Group Entry window. The Add button changes to Delete, and a Reset button appears (see Figure 4-26).

6 In the Provisioning Menu Bar, click Device > Save PSAX Configuration. (See the section, “Saving Configuration Values.”)

End

Viewing a Protection Group

To view existing interface protection groups, perform the steps in the follow-ing procedure.

Begin




Table 4-13. ADD Interface Protection Group Window Field Descriptions


Group ID Default: 0

Range: 1–9999

Format: Numeric

Specifies the group ID that represents a unique protection group within the PSAX system. You must first set up this group ID on the Protection Group Configuration window.

Figure 4-26. UPDATE Protection Group Entry Window

4-44 255-700-762R11.1



The Protection Group page appears (see Figure 4-23).

3 Within the Interface Protection table panel, click the right mouse button and a menu appears (see Figure 4-24). Select Display.

4 Click Close.

End

Deleting a Protection Group

Perform the steps in the following procedure to delete an interface protection group.

Begin



2 Click the Protection Group tab.

The Protection Group page appears (see Figure 4-23 on page 4-42).

3 Do one of the following to delete an interface protection group (Step 3 or Step 4):

Figure 4-27. Protection Group Page

Figure 4-28. VIEW Protection Group Entry Window

255-700-762R11.1 4-45



a Within the Protection Group Table panel, select the entry you want to delete.

b With the entry selected, click the right mouse button and a menu appears (see Figure 4-24). Select Delete.


c Click Yes.

The entry is removed from the Protection Group Table. You may skip step 4.

4 To delete a protection group from the UPDATE or VIEW Protection Group Entry window, do one of the following (a or b):

a Within the Protection Group Table panel, select the entry you want to delete, and select Display from the right mouse menu.

b Within the Protection Group Table panel, double-click the entry you want to delete.

The VIEW Protection Group Entry window appears.

c Click Delete.


d Click Yes.

The entry is removed from the Protection Group Table.

End

Creating Interface Protection Entries Within a Group

Continuing from the procedure ”Creating a Protection Group” on page 4-42, perform the steps in the following procedure to configure interface protec-tion entries within existing interface protection groups.

Begin

1 From the ADD/UPDATE/VIEW Protection Group Entry window, click the right mouse button within the Interface Protection Table panel and a menu appears. Select Create.

The ADD Interface Protection Entry window appears (see Figure 4-30).

Figure 4-29. Delete Protection Group Entry Confirmation Window

4-46 255-700-762R11.1



2 Select the values for the fields on this window as described in Table 4-14.

3 Click Add.

If this entry is valid, it is added to the Protection Group Table.

4 To initiate a switchover of the selected interface, click Interface Switchover.

5 To initiate a switchback of the selected interface, click Interface Switch-back.


End


Figure 4-30. ADD Interface Protection Entry Window

Button Function

Add Adds this entry to the Protection Group Table (see Figure 4-23).

Delete Removes this entry from the Interface Protection group. This button is displayed on the VIEW and UPDATE Interface Pro-tection Entry windows.

Reset Changes user-configurable fields to the last saved values. This button is displayed on the UPDATE Interface Protection Entry window.


Interface Switchover Initiates the interface switchover.

Interface Switchback Initiates the interface switchback.

255-700-762R11.1 4-47



Table 4-14. ADD Interface Protection Entry Window Field Descriptions

Field Names Values Description

Group ID(display only)

Default: N/A

Range: 1–9999

Format: Numeric

A user-selected number used to uniquely identify a protection group within a PSAX system.

Logical ID Default: 0

Range: 1–9999

Format: Numeric

A user-selected logical number which represents a unique protection interface entry within a PSAX system.

Interface Type Default: Primary

Range: N/A

Format: Predefined

Indicates whether this interface is the primary or secondary interface.

Primary Primary interface.

Secondary Secondary (backup) interface.

Selected Standby # Default: 0

Range: 0

Format: Numeric

Standby interface logical number on which to switch traffic. Used only when the protection group configuration window has Manual selected in the Switchover Method field and Explicit selected in the Standby Selection field. You must set the value in this field after perform-ing a switchover.

Operational State(display only)

Default: Inactive

Range: N/A

Format: Predefined

Indicates whether the interface is operational or not.

Inactive Indicates that the interface is not operationally active.

Active Indicates that the interface is operationally active.

Operational Interface(display only)

Default: 0

Range: 0

Format: Numeric

Protection operational state of the interface. Indi-cates which logical interface is carrying traffic originally configured for this interface.

Slot Default: 0

Range: Varies depending on chassis type

Format: Numeric

The slot number containing the module you want to include in this interface protection entry.

Port Default: 0

Range: Varies depending on module type

Format: Numeric

The port number containing the module you want to include in this interface protection entry.

Channel Default: 0

Range: Varies depending on module type

Format: Numeric

The channel number of the port on the module you want to include in this inteface protection entry.

4-48 255-700-762R11.1



Viewing an Interface Protection Entry

Perform the steps in the following procedure to view an interface protection entry.

Begin




The Interface Protection page appears (see Figure 4-23 on page 4-42).

3 Right-click an existing interface protection group, and a menu appears. Select View.

The VIEW Interface Protection Entry window appears (see Figure 4-31). The values for the fields on this window are described in Table 4-14.

Interface Default: N/A

Range: N/A

Format: Predefined

The interface type configured on the slot, port, and channel selected of the I/O module.

OperStatus(display only)

Default: InService

Range: N/A

Format: Predefined

Indicates whether the interface is operational or not.

InService Indicates that the interface is operational.

OutOfService Indicates that the interface is not operational.

AdminStatus (display only)

Default: InService

Range: N/A

Format: Predefined

Indicates whether any conditions exist that pre-vent the port from being fully operational.

InService Indicates that no conditions are preventing the port from being fully operational.

OutOfService Indicates that some condition is preventing the port from being configured with an interface.

Table 4-14. ADD Interface Protection Entry Window Field Descriptions


255-700-762R11.1 4-49



4 Click Close.

End

Deleting an Interface Protection Entry

Perform the steps in the following procedure to delete an interface protection entry.

Begin




The Interface Protection page appears (see Figure 4-23 on page 4-42).

3 Right-click an existing interface protection group, and a menu appears. Select Update.

The UPDATE Interface Protection Entry window appears (see Figure 4-32). The values for the fields on this window are described in Table 4-14.

Figure 4-31. VIEW Interface Protection Entry Window

4-50 255-700-762R11.1



4 Do one of the following as shown in Table 4-18:

Figure 4-32. UPDATE Interface Protection Entry Window

255-700-762R11.1 4-51


Chapter 4 Site-Specific ConfigurationIP Throttling

5 On the UPDATE or VIEW Interface Protection Entry window, click Close.

End

IP Throttling

IP Throttling ConfigurationPerform the steps in the following procedure to configure IP throttling.

Table 4-15. Deleting an Interface Protection Group

To delete an interface protection group...

do this...

when unsure which entry you want to delete

a View the attributes of the entry first.

b On the VIEW or UPDATE Protection Entry window, click Delete.

A confirmation window appears.

c Click Yes to delete the entry, or click No to cancel the request.

when sure which entry you want to delete

a Select the entry you want to delete.

b Right-click the mouse within the Pro-tection Group Table and a menu appears. Select Delete.



4-52 255-700-762R11.1



Begin



2 Click the IP Throttling tab.

The IP Throttling page appears (see Figure 4-33).

3 To view all the fields on this window, select Enabled in the IP Throttling field.

4 Click Apply.


6 Click Apply.

End


Figure 4-33. IP Throttling Page

255-700-762R11.1 4-53



Buttons Function

Apply Sets the values you enter on this page.

Refresh Updates the fields on the IP Throttling panel.

Update Refreshes the statistics.

Clear Resets the resetable statistics to zero.

Poll Poll + continuously update the statistics and changes the but-ton label to Poll-.

Poll- terminates polling and changes the button label to Poll +.

Table 4-16. IP Throttling Configuration Page Field Descriptions


IP Throttling Default: Disabled

Range: N/A

Format: Predefined

Indicates whether traffic will go through the ETHERNET port and in-band management virtual port (in the backplane) by its maximum designated throughput in the Allowed Rate field.

Note: This feature will not be applied to the backup CPU module.

Disabled The IP Throttling feature is turned off. If you select this value, the following fields in this table will disappear, and the fea-ture will not affect the IP data path.

Note: Before you disable the IP throttling feature, be sure to stop polling on the IP throttling statistics by clicking Poll- (doing so will terminate polling and change the button label to Poll+).

Enabled The IP Throttling feature is turned on. (If you select this value and click Apply, the following fields in this table will appear.)

4-54 255-700-762R11.1



Allowed Rate Default: 2000 fps

Range: 100–2000 fps

Format: Predefined

Specifies the maximum bandwidth allowed to pass through the ETHERNET or in-band management virtual port into the PSAX system in the unit of frames per second (fps). Select one of the values listed below.

Note: If you do not assign any value, then 2,000 fps will be used. This value will correspond to 2000 x 64 x 8 bits/second = 1.024 Mbps for 64-byte frames, 2,000 x (576+18) x 8 = 9.504 Mbps for default frame size of 594 bytes, or 2,000 x 1,518 x 8 = 24.288 Mbps for 1,518-byte frames. The latter rate is larger than the maximum rate supported by the 10BASE-T ETHERNET port of the CPU module. For current MIPS CPU/CPU2 modules, FTP sessions will rarely be affected under the value of 1,500 and above. Lower values of the Allowed Rate field will subsequently cause greater loss of ingress packets.

100–2000 fps Select a value of 100, 200, 300, 500, 1000, or 2000 frames per second of input to the CPU module.

Other fps Select this value to allow a number of frames per second of input to the CPU module that is not selectable from the other values in this field, and then enter the rate you want to use in the Rate field that appears.

Rate Default: N/A

Range: 1–20000 fps

Format: Numeric

This field appears when Other is selected in the Allowed Rate field. Enter the rate you want to use. See the Note in the pre-vious field description for more information. This field is dis-play only unless Other fps is selected in the Allowed Rate field.

Leaky Bucket Size

Default: 32

Range: 1–20000

Format: Numeric

The virtual buffer that serves as a counter that monitors the rate of ingress traffic to the CPU module. It counts the num-ber of packets and drops packets that exceed the value you select for this field.

In general, the smaller the value that is used, the more likely the ingress traffic will be dropped. The greater value that is used, the more unlikely the ingress packets will be dropped, and the more bursty the ingress traffic may become.

In Packets(display only)

Default: N/A

Range: N/A

Format: Numeric

The total number of input packets that are received from both the ETHERNET port of the CPU module and the in-band man-agement virtual port of the CPU module.

Passed Ether Port(display only)

Default: N/A

Range: N/A

Format: Numeric

The number of input packets passed through the ETHERNET port of the CPU module.

Dropped Ether Port(display only)

Default: N/A

Range: N/A

Format: Numeric

The number of input packets dropped through the ETHERNET port of the CPU module.

Table 4-16. IP Throttling Configuration Page Field Descriptions (Continued)


255-700-762R11.1 4-55


Chapter 4 Site-Specific ConfigurationConfiguring N:1 Protection

Viewing Statistics

You can view the statistics for IP throttling on the Statistics panel. The fields on this panel are described in Table 4-16.

Configuring N:1 Protection

Configuring N:1 Protection Groups

Perform the steps in the following procedure to create an N to M protection group.

Begin



2 Click the Special Features tab.

The Special Features page appears.

3 Click the N to M Protection tab.

Passed IBM(display only)

Default: N/A

Range: N/A

Format: Numeric

The number of input packets passed through the in-band management virtual port of the CPU module.

Dropped IBM(display only)

Default: N/A

Range: N/A

Format: Numeric

The number of input packets dropped through the in-band management virtual port of the CPU module.

Time Elapsed(display only)

Default: N/A

Range: N/A

Format: hh:mm:ss

Number of seconds since the Clear button was clicked.

Table 4-16. IP Throttling Configuration Page Field Descriptions (Continued)


4-56 255-700-762R11.1



The N to M Protection page appears, displaying the N to M Protection Group Table and the N to M Protection Table (see Figure 4-34).

4 Right-click the mouse within the N to M Protection Group Table and a menu appears (see Figure 4-35). Select Create.

Figure 4-34. N to M Protection Page

Figure 4-35. N to M Protection Group Table Window

255-700-762R11.1 4-57



The ADD N to M Protection Group Table Entry window is displayed (see Figure 4-36).

This window allows you to create an N:1 protection group by selecting work-ing and protection slots, a group ID, and the type of protection group you want to configure.

5 Enter values in the fields on this window according to the information provided in Table 4-17.

6 Click Add.

The protection group is created and added to the N to M Protection Group Table. If the N to M Protection Table does not update automati-cally, right-click anywhere within the N to M Protection Table and select Refresh.

7 Click Close.

8 View the Device Tree and verify that the module status for modules being configured for 1:1 protection indicates Primary for the working module and Standby for the protection module.

9 In the Device Menu Bar, select Device > Save PSAX Configuration.

End

The buttons on the N to M Group Protection Entry windows have the follow-ing functions:

Figure 4-36. N to M Protection Group Table Entry Window (ADD)

4-58 255-700-762R11.1



Button Function

Add Displayed on the ADD N to M Protection Group Table Entry window when creating an N to M protection group. Adds the entry to the N to M Protection Group Table.

Update Displayed on the UPDATE N to M Protection Group Table Entry window when updating an N to M pro-tection group. Updates the entry in the N to M Pro-tection Group Table with the values you select.

Delete Displayed on the VIEW N to M Protection Group Table Entry and UPDATE N to M Protection Group Table Entry windows. Removes the entry from the N to M Protection Group Table.

Reset Displayed on the UPDATE N to M Protection Group Table Entry window when updating an N to M pro-tection group. Refreshes the configurable values for this the entry.

Reset Statistics Selectable on the UPDATE N to M Protection Group Table Entry window when updating an N to M pro-tection group. Refreshes the display-only values for this the entry.

Poll Selectable on the VIEW N to M Protection Group Table Entry and UPDATE N to M Protection Group Table Entry windows. Poll+ initiates the continuous update of statistics. Poll- suspends polling.

Close Closes the window.

255-700-762R11.1 4-59



Viewing N:1 Protection Groups

Begin







4 Select the protection group that you want to view.

5 Right-click the mouse within the N to M Protection Group Table, and a menu appears (see Figure 4-35). Select Display.

Table 4-17. ADD N to M Protection Group Table Entry Window Field Descriptions


Working Slots Default: N/A

Range: 1–16

Format: Numeric

Displays the selected working slots within a protec-tion group. Select the slots containing the modules that you want to designate as the working modules.

High-Density DS1 Multiservice module: Select one odd-numbered checkbox that corresponds to the slot number where the working module is installed.

LIM modules: Slots 3–8 and 9–12 are dedicated for each protection group.

Protection Slots Default: N/A

Range: 1–16

Format: Numeric

Displays the selected protection slots within a pro-tection group. Select the slots containing the mod-ules that you want to designate as the protection modules.

High-Density DS1 Multiservice module: Select one even-numbered checkbox that corresponds to the slot number where the protection module is installed.

LIM modules: Slot 15 must be used for working slots 3–8; slot 13 must be used for working slots 9–12.

4-60 255-700-762R11.1



The VIEW N to M Protection Group Table Entry window is displayed (see Figure 4-37).

6 Refer to Table 4-17 for field descriptions.

7 When finished viewing the entry, click Close.

End

Updating N:1 Protection Groups

Begin

1 In the Device window, click the Site-Specific tab, and the Site-Specific page appears.

2 From the Site-Specific page, click the N to M Protection tab. The N to M Protection page appears, displaying the N to M Protection Group Table and the N to M Protection Table (see Figure 4-34).

3 Select the protection group that you want to update.

4 Right-click the mouse within the N to M Protection Group Table and a menu appears (see Figure 4-35). Select Update.

Figure 4-37. N to M Protection Group Table Entry Window (VIEW)

255-700-762R11.1 4-61



The UPDATE N to M Protection Group Table Entry window is displayed (see Figure 4-38).

5 Change the desired values according to the information provided in Table 4-17.

6 Click Update.

7 Click Close.

If the N to M Protection Table does not update automatically, right-click anywhere within the N to M Protection Table and select Refresh.

End

Deleting N:1 Protection Groups

Begin

1 In the Device window, click the Site-Specific tab, and the Site-Specific page appears.

2 From the Site-Specific page, click the N to M Protection tab. The N to M Protection page appears, displaying the N to M Protection Group Table and the N to M Protection Table (see Figure 4-34).

Figure 4-38. N to M Protection Group Table Entry Window (VIEW)

4-62 255-700-762R11.1





End

Table 4-18. Deleting an N to M Protection Group

To delete an N to M protection group... do this...


a View the attributes of the entry first. Follow steps 1 and 2 in the section, “Viewing N:1 Protection Groups”

b Click Delete.



when sure which entry you want to delete


b Right-click the mouse within the N to M Protection Group Table and a menu appears (see Figure 4-35). Select Delete.



255-700-762R11.1 4-63



Viewing N:1 Protection Slot Configurations

Begin







The N to M Protection Table allows you to view the protection status of all modules and to select a slot to view or to change the protection con-figuration of a module. The fields for unconfigured slots (displaying None) are read-only.

The fields on this window are described in Table 4-19.

Select a row for a slot in this table, right-click the mouse within the N to M Protection Table and a menu appears (see Figure 4-39). Select Display.

The VIEW N to M Protection Table Entry window is displayed (see Figure 4-40).

Figure 4-39. N to M Protection Table (Displaying Menu)

4-64 255-700-762R11.1



4 View the field values.

End

The buttons on the N to M Protection Entry windows have the following functions:

Figure 4-40. N to M Protection Table Entry Window(Working and Protection Slots Displayed Respectively)

button Function

Update Displayed on the UPDATE N to M Protec-tion Table Entry window when updating an N to M Protection Group Entry. Updates the entry in the N to M Protec-tion Group Table with the values you select.

Reset Displayed on the UPDATE N to M Protec-tion Table Entry window when updating an N to M Protection Group Entry. Refreshes the values for this the entry.


255-700-762R11.1 4-65



Table 4-20. N to M Protection Configuration Window Field DescriptionsN to M Protection Table Panel Field Descriptions


Slot IdSlot ID(display only)

Default: N/A

Range: 1–15

Format: Numeric

Selects module slot in the chassis that is to be viewed or changed. To make another selection, type the slot number in this field and select the Refresh Display command.

Command Default: N/A

Range: N/A

Format: Predefined

Indicates the selectable commands used to con-trol the protection feature on the selected slot.

None Indicates that no command is enabled for the selected slot.

Clear Forces traffic back to the working module slot.

ForcedSwitchOver-ToProtection

Forces traffic to the assigned protection module slot.

[Switchover Slot Id]Switchover Slot ID(display only)

Default: 18

Range: 1–15

Format: Numeric

Displays the slot number of the module that traf-fic is transferred to during a protection switchover. The value 18 indicates that no valid switchover slot exists at this time.

[Config Mode]Config Mode(display only)

Default: None

Range: N/A

Format: Predefined

Displays the protection configuration status of the selected slot.

None Indicates that the selected slot is not configured.

Working Indicates that the selected slot is configured as a working module.

Protection Indicates that the selected slot is configured as a protection module.

[Group Id]Group ID(display only)

Default: N/A

Range: 0–15

Format: Numeric

Displays the number assigned to the protection group associated with the selected slot.

[Oper State]Oper State(display only)

Default: None

Range: N/A

Format: Predefined

Displays the operational state of the selected module.

None Indicates that the selected module is not opera-tional.

Active Indicates that the selected module is actively sending traffic.

Standby Indicates that the selected module is standing by to send traffic should a switchover take place.

4-66 255-700-762R11.1



Performing N:1 Protection Slot Switchovers

Begin







Select a row for a slot in this table, right-click the mouse within the N to M Protection Table and a menu appears (see Figure 4-39). Select Update. The UPDATE N to M Protection Table Entry window is displayed (see Figure 4-41).

[Slot Active Counter]Slot Active Counter(display only)

Default: 0

Range: 0–2147483647

Format: Numeric

Displays the number of times that this slot has gone from the Standby to the Active state since the protection group was created.

[Timer]Timer(display only)

Default: 0

Range: 0–2147483647

Format: Numeric (sec-onds)

Displays the number of seconds for which the statistics for this protection group has been collected.

[Card Status]Card Status

Default: NoAlarm

Range: N/A

Format: Predefined

Indicates the status of the line: one of several alarms. This field is displayed on the UPDATE N to M Protection Table window only.

Table 4-20. N to M Protection Configuration Window Field DescriptionsN to M Protection Table Panel Field Descriptions (Continued)


255-700-762R11.1 4-67



This window allows you to apply a switchover for a module within a pro-tection group.

4 Select a value in the Command field on this window according to the information provided in Table 4-20.

5 Click Update.


6 Click Yes to perform the switchover, or No to cancel the operation.

If you clicked Yes, your configuration value are applied to the entry, and the Working module changes status to Protection (or vice versa, depend-ing on the configuration values you updated).


End

Figure 4-41. UPDATE N To M Protection Table Entry Window

Figure 4-42. Confirmation Window

4-68 255-700-762R11.1


Chapter 4 Site-Specific ConfigurationSaving Configuration Values

Saving Configuration Values

! CAUTION:Select Device > Save PSAX Configuration to permanently save the con-figuration.

Applied, but unsaved, configuration data will be lost if the PSAX system is restarted, or if power to the PSAX system is lost. Terminating the EMS-PSAX will not cause the applied values to be lost because the configuration data is stored in the PSAX device, not in the EMS-PSAX.

255-700-762R11.1 4-69


Chapter 4 Site-Specific ConfigurationSaving Configuration Values

4-70 255-700-762R11.1


5 Configuring ATM Trunking

Overview of This Chapter

An ATM Trunk is an ATM SVC connection which serves as the ATM side of an CE-to-ATM Standard AAL2 SPVC or a VBR-to-ATM Standard AAL2 SPVC connection. An ATM trunk may be configured using an UNI 4.0 or a PNNI interface.

ATM Trunks are configured before any standard AAL2 SPVCs may be config-ured. The ATM Trunk configuration assigns the QoS and bandwidth to the ATM interface, which will be used by the individual AAL2 SPVCs. The ATM interface slot/port/channel and VPI/VCI are assigned dynamically by the sys-tem when the SVC is successfully set up across the network.

ATM trunking configuration supports switched and nonswitched IWF trunks.

Switched Trunking

Switched trunking involves analysis of the signalling that accompanies an incoming narrowband call and routing of its bearer information to an AAL2 channel within a VCC between IWFs. Similar analysis and routing is required for incoming calls from the ATM network as well. After the narrowband call has ended, subsequent calls occupying the same narrowband channel (TDM timeslot) may be switched to different AAL2 channels and VCCs. There is no permanent relationship between a narrowband channel and an AAL2 chan-nel.

For configuring IWF trunks in switched mode, the following list describes the tasks you need to perform:

1. Configuring the local IWF node

2. Configuring the remote IWF nodes

3. Configuring one or more signaling VCC identifiers and their parameters

4. Configuring one or more bearer VCC identifiers and their parameters

5. Configuring the addresses for the narrowband routing and the broad-band routing tables

Non-Switched Trunking

In non-switched trunking, the information stream of a narrowband channel is always carried on the same AAL2 channel within the same VCC and vice-versa. Non-switched trunking involves no termination of signalling and no routing of narrowband calls in the IWFs.

For configuring IWF trunks in nonswitched mode, the following list describes the tasks you need to perform:


255-700-762R11.1 5-1

Chapter 5 Configuring ATM TrunkingConfiguring the Local Node

1. Configuring the local IWF node

2. Configuring the remote IWF nodes

3. Configuring one or more bearer VCC identifiers and their parameters

In addition, you can view all ATM trunking configuration information for both switched and nonswitched IWF trunks

To configure the system for ATM trunking, perform the following procedures.

Configuring the Local NodeTo configure the ATM trunking local node, perform the steps in the following procedure.

Begin





3 Click the ATM Trunking tab.

The ATM Trunking page appears (see Figure 5-1).

4 Select the values for the fields on this page as described in Table 5-1.

5 Do one of the following to apply the values for the local node:

~ Under the ATM Trunking Local Node Configuration panel, click the right mouse button and a menu appears. Select Apply.

~ Click Apply.


End

5-2 255-700-762R11.1


Chapter 5 Configuring ATM TrunkingConfiguring the Local Node


Figure 5-1. ATM Trunking Page (Displaying Menu)

Button Function

Apply Applies the values set for the local node.

Refresh Updates the information for the local node configuration.

255-700-762R11.1 5-3


Chapter 5 Configuring ATM TrunkingConfiguring the Remote IWF

Configuring the Remote IWFTo configure the ATM trunking remote interworking function, perform the steps in the following procedure.

Begin







Table 5-1. ATM Trunking Page Field Descriptions


Local IWF ID Default: 0

Range: 1–255

Format: Numeric

Specifies the local interworking function (IWF) identifier for the local endpoint.

Wireless Applications: The Cell Site and the MSC must have different IDs. The Cell site is the local IWF; the MSC is the remote.

ATM Address Default: 0

Range: N/A


Specifies the IWF ATM address for the local end-point. Type an address in hexadecimal format up to 20 bytes (160 bits) long (10 groups of 4 charac-ters each). The address must start with 39, 45, or 47, depending on the ATM address format used.

Wireless Applications: The Cell Site and MSC must have different addresses.

Max Remote IWF Default: 100

Range: 1–1024

Format: Numeric

Specifies the maximum value of the remote IWF ID that can be connected to the local endpoint in the PSAX system. If you enter a value higher than the default value in this field, you must also increase the value of the ATM Trunk VCCs field on the Call Control Resource Allocation window accordingly.

Wireless Applications: For the Cell Site to MSC applications, the MSC is the remote IWF. You are limited to 32 ATM VCC IWFs, as configured on the Call Control Resource Allocation window.

Admin Status Default: Down

Range: N/A

Format: Predefined

Specifies the status of the local IWF.

Up Indicates that the local IWF is active.

Down Indicates that the local IWF is inactive.

5-4 255-700-762R11.1



4 Under the ATM Trunking Local Node Configuration panel, click the right mouse button and a menu appears. Select Remote IWF Table.

The View ATM Trunking Remote IWF Table window appears (see Figure 5-2).

5 In the View ATM Trunking Remote IWF Table window, click the right mouse button and a menu appears (see Figure 5-3).

6 Select Create.

The ADD ATM Trunking Remote Entry window appears (see Figure 5-4).


8 Click Add.

If this entry is valid, it is added to the ATM Trunking Remote IWF Table.


10 Click Close.

End


Figure 5-2. View ATM Trunking Remote IWF Table Window

Button Function

Find Searches the table and displays a matching text string entered in the Show table entry containing: field.

Reset Removes text entered in the Show table entry containing: field and deselects any selected entries.


255-700-762R11.1 5-5



The buttons on this window has the following functions:

Figure 5-3. View ATM Trunking Remote IWF Table Window (Displaying Menu)

Figure 5-4. ADD ATM Trunking Remote Entry Window

Button Function

Add Adds this entry to the table.


5-6 255-700-762R11.1



Table 5-2. ADD ATM Trunking Remote Entry Window Field Descriptions


Remote IWF ID Default: 0

Range: 1–4096

Format: Numeric

Specifies the remote interworking function (IWF) identifier for the remote endpoint. The value in this field must be less than or equal to the value for the Max Remote IWF on the ATM Trunking Local Node Configuration window.

Wireless Applications: You are limited in the number of remote IWFs by the values configured on the Call Control Resource Configuration window.

Remote IWF ATM Address (Hex)

Default: 0

Range: N/A

Format: Hexadeci-mal

Specifies the IWF ATM address for the remote endpoint. Type an address in hexadecimal format up to 20 bytes (160) bits long (10 groups of 4 characters each). The address must start with 39, 45, or 47, depending on the ATM address for-mat used.

Wireless Applications: If configuring a cell site with an MSC, the MSC is the remote IWF.

Remote IWF Trunk Mode(display only)

Default: Switched

Range: N/A

Format: Predefined

Specifies whether the remote IWF trunk is in switched mode or non-switched mode.

Switched Indicates that the specified signaling VCC is used for the connection trunk.

Non-switched Indicates that no signaling is used for the connection trunk.

Wireless Applications: If configuring a cell site with an MSC, select this value.

Remote IWF Max Call Rate

Default: 60

Range: 1–4096

Format: Numeric (Calls per second)

Indicates the maximum number of new calls per second within this remote IWF. This field value is used to estimate the bandwidth resource requirement for an unconfigured SVC signaling VCC.

Remote IWF PCM Encoding

Default: A-law

Range: N/A

Format: Predefined

Indicates the type of PCM encoding performed on the bearer VCC.

A-law Indicates that the traffic on the bearer VCC is encoded as A-law traffic.

U-law Indicates that the traffic on the bearer VCC is encoded as U-law traffic.

None Indicates that PCM encoding is not performed on the bearer VCC.

Remote IWF Admin Status(display only)

Default: Down

Range: N/A

Format: Predefined

Specifies whether the remote IWF is active.

Down Indicates that the remote IWF is inactive.

Up Indicates that the remote IWF is active.

255-700-762R11.1 5-7


Chapter 5 Configuring ATM TrunkingConfiguring the Signaling VCC

Configuring the Signaling VCCTo configure the ATM trunking signaling VCC, perform the steps in the fol-lowing procedure.

Begin









5 In the View ATM Trunking Remote IWF Table window, click the right mouse button and a menu appears (see Figure 5-3). Select SigVcc Table.

The View ATM Trunking Sig Vcc Table window appears (see Figure 5-5).

In the View ATM Trunking Sig Vcc Table window, click the right mouse but-ton and a menu appears. Select Create.

The ADD ATM Trunking Sig VCC Entry window appears (see Figure 5-6).


7 Click Add.

If this entry is valid, it is added to the ATM Trunking Sig Vcc Table.


9 Click Close.

End

5-8 255-700-762R11.1




Figure 5-5. View ATM Trunking Sig Vcc Table Window

Button Function




255-700-762R11.1 5-9




Figure 5-6. ADD ATM Trunking Sig VCC Entry Window

Button Function



Table 5-3. ADD ATM Trunking Sig VCC Entry Window Field Descriptions


[Remote IWF ID] Default: User-assigned

Range: N/A

Format: Numeric

Displays the remote IWF identifier for the remote end-point.

Sig VCC ID Default: 0

Range: 0–16383

Format: Numeric

Specifies the virtual channel connection identifier, which is assigned by the owner of the signaling VCC.

[Out Interface ID] Default: 0

Range: N/A

Format: SS/PP/CCC

Displays the interface identifier of the outgoing inter-face. This field is editable only for the PVC connection type. This field is display only for VCC Conn Type field values of SVC and SPVC.

5-10 255-700-762R11.1



Inactive Time Period

Default: 3600

Range: N/A

Format: Numeric

Specifies the inactive time period allowed to clear the call.

Signaling Default: Other

Range: N/A

Format: Predefined

Specifies the type of signaling protocol used between the local and remote IWFs. At the present time, both ends of the connection must be on a PSAX system.

Other Indicates that ATM 4.0 signaling is used.

Pss1 This value is not currently supported.

Dss1 This value is not currently supported.

Dpnss This value is not currently supported.

Max AAL2 VCC Default: 255

Range: N/A

Format: Numeric

Maximum number of bearer VCCs controlled by the sig-naling VCC.

Active AAL2 VCC(display only)

Default: 1

Range: N/A

Format: Numeric

Number of active bearer VCCs controlled by the signal-ing VCC.

Egress VIB Default: 0

Range: N/A

Format: Numeric

Virtual identifier to associate with the egress side of the A to B connection.

Egress VUNIB Default: 0

Range: N/A

Format: Numeric

Virtual UNI identifier to associate with the egress side of the A to B connection.

[Sig VCC Owner] Default: Local

Range: N/A

Format: Predefined

Specifies the owner of the signaling VCC. This field is editable only when the VCC Conn Type field is set to Pvc or Spvc.

Local The signaling VCC owner is the local IWF.

Remote The signaling VCC owner is the remote IWF.

[Retry Timer] Default: 30

Range: N/A


Indicates the time in seconds that the PSAX system will wait before attempting to establish the ATM Trunking Signalling VCC SPVC connection after a previous failed call attempt. A value of 0 indicates that retries will be attempted immediately. This field is editable only when the VCC Conn Type field is set to Spvc.

[Retry Limit] Default: 0

Range: N/A

Format: Numeric

Indicates the number of times that the PSAX system attempting to establish the ATM Trunking Signalling VCC SPVC connection. A value of 0 indicates an unlim-ited number of attempts. This field is editable only when the VCC Conn Type field is set to Spvc.

Table 5-3. ADD ATM Trunking Sig VCC Entry Window Field Descriptions (Continued)


255-700-762R11.1 5-11


Chapter 5 Configuring ATM TrunkingConfiguring Bearer VCC Components

Configuring Bearer VCC Components

Configuring the Bearer VCC

To configure ATM trunking bearer VCC, you must first have configured a remote IWF. Perform the steps in the following procedure.

Begin









5 In the View ATM Trunking Remote IWF Table window, select an entry.

6 Right-click the mouse button and a menu appears (see Figure 5-3). Select Bearer Table.

The View ATM Trunking Br Vcc Table window appears (see Figure 5-7).

7 In the View ATM Trunking Br Vcc Table window, click the right mouse button and a menu appears. Select Create.

The ADD ATM Trunking Br VCC Entry window appears (see Figure 5-8).

[Oper Status] Default: Idle

Range: N/A

Format: Predefined

Displays the operational status of the local IWF.

Idle Indicates that the connection is not operational.

OutOfService Indicates that the PVC connection is not operational.

Init Indicates that the connection is being initiated.

Connecting Indicates that the connection is being connected but layer 2 is not yet operational.

Active Indicates that the connection is operational and is trans-mitting traffic.

Release Indicates that the connection is being released.

Table 5-3. ADD ATM Trunking Sig VCC Entry Window Field Descriptions (Continued)


5-12 255-700-762R11.1




9 Click Add.

If this entry is valid, it is added to the ATM Trunking Br Vcc Table.


11 Click Close.

End


Figure 5-7. View ATM Trunking Br Vcc Table Window

Button Function




255-700-762R11.1 5-13




Figure 5-8. ADD ATM Trunking Br VCC Entry Window (Bearer VCC Config Page)

Button Function

Add Adds this entry to the table. This button is dis-played on the ADD ATM Trunking Bearer VCC Config Page.


Table 5-4. ATM Trunking Bearer VCC Entry Window Field Descriptions*


Remote IWF ID Default: 0

Range: 0–255

Format: Numeric

Displays the remote interworking function (IWF) identifier for the remote endpoint.

ATM Trnk Br VCC ID

Default: 0

Range: 0–4096

Format: Numeric

Specifies the ATM Trunk bearer VCC ID.

Sig VCC ID(display only)

Default: 0

Range: N/A

Format: Numeric

Displays the identifier of the signaling VCC.

5-14 255-700-762R11.1



Service Type Default: Cbr-1

Range: N/A

Format: Predefined

Specifies the service type for the connection.

For any CBR type selected, the CAC only allows 1 DS0 per connection. For any CBR type selected, the total available bandwidth for all DS0 connec-tions is checked before DSPs are allocated, as VBR has no restrictions on the number of DS0s allowed per connection.

Cbr-1 Indicates constant bit rate, priority 1.




Ubr Indicates unspecified bit rate.

Vbr-nrt2 Indicates variable bit rate, nonreal time, queue 2

Vbr-nrt1 Indicates variable bit rate, nonreal time, queue 1

Vbr-rt2 Indicates variable bit rate, real time, queue 2

Vbr-rt1 Indicates variable bit rate, real time, queue 1

Vbr-express Indicates variable bit rate, express.

SAR Type Default: Aal2

Range: N/A

Format: Predefined

Specifies the segmentation and reassembly type for the connection.

Aal2 Indicates that compressed, connection-oriented, delay-sensitive VBR traffic will be transmitted on this connection.

Wireless Applications: Select this service type for the ATM Trunking local and remote nodes (caller and called sides).

Aal1 Indicates that uncompressed, connection-ori-ented, time-sensitive CBR traffic will be transmit-ted on this connection.

Fwd/Bwd PCR (cps)

Default: 172

Range:

Format: Numeric (cells per second)

Specifies the forward and backward peak cell rate for the connection, respectively.

OAM Status Default: Unsupp

Range: N/A

Format: Predefined

Specifies the OAM support used.

Unsupp Indicates that OAM is not in use.

End-Pt The PSAX system is used as a termination point for ATM traffic.

The OAM loopback test is supported for end-to-end connections only.

Table 5-4. ATM Trunking Bearer VCC Entry Window Field Descriptions* (Continued)


255-700-762R11.1 5-15



VCC Conn Type Default: Svc

Range: N/A

Format: Predefined

Specifies the VCC connection type.

Svc Switched virtual circuit.

Spvc Software-switched permanent virtual circuit.

Pvc Permanent virtual circuit.

VCC Interface ID(display only)

Default: 00/00/00

Range: N/A

Format: Numeric

VCC interface ID for the outgoing interface.

This field is valid only when Pvc is selected in the VCC Conn Type field.

VCC VPI/VCI Default: 0 / 0

Range: VPI 0-255 (user-to-user inter-face, output side), 0-4095 (network-to-network interface, output side)

Range: VCI 32-65535 (signaling enabled, (5-32 are reserved), VCI 5-65535 (signal-ing disabled).

Format: Numeric

Identifies the VPI and VCI for the outgoing inter-face. The trunk bearer VCC does not become active until both the local and remote trunk ter-minations are configured and brought into ser-vice. After this is done, the values assigned to the trunk are displayed in this field and the VCC Interface ID field above. This field is editable only when Pvc is selected in the VCC Conn Type field.

VCC VIB/VUNIB Default: 0

Range:

Format: Numeric

Specifies the egress side of the A to B side of the VCC VI and VUNIB, respectively. This field is valid only when Pvc is selected in the VCC Conn Type field.

VCC Owner(display only)

Default: Local

Range: N/A

Format: Predefined

Indicates whether the VCC owner is local or remote. This field is valid only when Spvc or Pvc is selected in the VCC Conn Type field.

Local The VCC owner is local.

Remote The VCC owner is remote.



5-16 255-700-762R11.1



Retry Timer/Limit Default: 30

Range:

Format: Seconds (Timer); Numeric (Limit)

Timer: Specifies the amount of seconds to wait before attempting to establish the signaling side of the connection after a previously failed call attempt. The value 0 indicates that the call attempt is to be retried immediately.

Limit: Specifies the maximum limit on how many retried calls are to be attempted. The value 0 indi-cates no limit on how many call attempts can be made.

This field is valid only when Spvc is selected in the VCC Conn Type field.

Inactive Timer Default: 3600

Range: 0–999999999


Specifies the time period during which no activity is taking place before the signaling side of the connection clears the call.

This field is valid only when Spvc is selected in the VCC Conn Type field.

Admin Status(display only)

Default: OutofService

Range: N/A

Format: Predefined

Indicates whether the connection is attempting to make calls or receive calls.

OutOfService Indicates that the connection is not available to attempt making or receiving calls.

InService Indicates that the connection is available to attempt making calls or receiving calls.

Priority Default: 3

Range: 1–6

Format: Numeric

User-defined reconnection order for dropped connections in case of IMA link failure. Priority 1 reconnects emergency 911 calls first if the need arises. Select 1 if you are using only one IMA link. The user assigns all other types of traffic (non-emergency) to priorities 2–6.



255-700-762R11.1 5-17



App Type Default: Narrowband

Range: N/A

Format: Predefined

Specifies the PSAX application that will use this trunk connection.

Narrowband Indicates the trunk will be used for narrowband connections.

V5 Indicates the trunk will be used for V5 connec-tions.

Gr303 Indicates the trunk will be used for GR-303 con-nections.

H248 Indicates the trunk will be used for H.248 con-nections.

Spvc Indicates the trunk will be used for SPVC connec-tions.

Wireless Backhaul Applications: If the spvcGlo-balPriorityScheme field is enabled on the Call Control Resource Allocation Configuration win-dow, you must select Spvc as the VCC Conn Type.

Dsp Iwf Type Default: None

Range: N/A

Format: Predefined

Specifies the Interworking function type on assigning AAL2 connections to compatible DSP chips on the DSP2C through DSP2F Voice Server modules.

None Allows the assignment of standard AAL2 connec-tions to DSP chips on the DSP2C Voice Server module that are configured as AlgoSet1 through AlgoSet3, and on the DSP2E/F as AlgoSet1 and AlgoSet6. This parameter allows the mixture of pure voice (CE-to-ATM) with data (VBR-to-ATM) in the same AAL2 trunk group, such as is used in the European LES trunking standard V.5.2. This parameter supports applica-ble connection types of previous PSAX system software releases.

Packet-pipe Allows the assignment of standard AAL2 connec-tions to DSP chips on the DSP2E/F modules that are configured as AlgoSet7. This parameter will not allow the mixture of pure voice (CE-to-ATM) with data (VBR-to-ATM) in the same AAL2 trunk group. This parameter supports applicable connection types for pure data (VBR-to-ATM) in wireless applications.

How bandwidth is assigned for this type depends on what type of CBR or VBR you select in the Service Type field.

Note: The value Packet-pipe cannot be used with the DSP2C Voice Server module.



5-18 255-700-762R11.1



Dsp Select Type Default: Automatic

Range: N/A

Format: Predefined

Specifies whether the DSP resources are allo-cated. The setting you select in this field must match the setting in the Selection Type column on the Dsp Resource Management Table (after the site-specific DSP Resource Configuration option), or your connections will not be made.

Note: Its is critical that the value configured in this field match the Selection Type field on the Dsp Resource Management Table at the Site-Spe-cific configuration level. If the values do not match, the connections using DSP parameters will not be assigned or activate.

Automatic Indicates that the DSP resource manager selects DSPs from a chassiswide pool automatically.

Manual Indicates that the DSP resource manager selects DSPs from a particular module specified in the Dsp Card Slot Id field.

Dsp Card Slot Id Default: 0

Range: Chassis dependent

Format: Numeric

Specifies the slot number of the DSP2x Voice Server module from which the DSP Resource Manager selects DSPs. If you selected Manual in the Dsp Select Type field, you must specify the DSP2x Voice Server module slot number in the Dsp Card Slot Id field from which you want the DSP Resource Manager to select DSPs. If no DSP resource is available on the DSP2x module in the specified slot, the connection is rejected. If you selected Automatic in the Dsp Select Type field, the Dsp Card Slot Id field is not displayed.

Num of DSP Chnl Default: 0

Range: 0–384

Format: Numeric

Specifies the number of DS0s that can be reserved as DSP channels. If the IWF Type is Packet-pipe, the bandwidth configured by you for the trunk calculates how many DS0s fit into the trunk. For example, the DS0 line rate is approximately 171 cps. If you want 200 cps, the bandwidth actually allocated is 200/171, or 1.16 DS0s.

The CAC reserves the DS0 resource when the first connection is made on the trunk. If the value is left at the default 0, the number of reserved DS0s is best-effort.

Note: If you have selected Packet-pipe in the Dsp Iwf Type field, how bandwidth is assigned to the DSP channels also depends on what type of CBR or VBR you select in the Service Type field (see the Dsp Iwf Type and Service Type fields for more details).



255-700-762R11.1 5-19



Traffic Shaping Default: Disabled

Range: N/A

Format: Predefined

Specifies whether traffic shaping is enabled or disabled on this connection. The traffic shaping feature uses an input cell selection algorithm (leaky bucket) that smooths bursts of input traf-fic. For the Traffic Shaping feature to work on this connection, you must have already selected the value Enabled on the ATM UNI Interface Con-figuration, the ATM IISP Interface Configuration, or the ATM PNNI Interface Configuration win-dow, as appropriate.See the Peak Rate field in this field description table for range of values con-straints on these modules.

Disabled Disables the Traffic Shaping feature on this con-nection.

Enabled Enables the Traffic Shaping feature on this con-nection.

DSP Resource Pool Type

Default: None

Range: N/A

Format: Predefined

Specifies the DSP resource pool type. This field is used for the DSP2G Voice Server module only. For all other DSP2x modules this value must be set to None.

Release Cause(display only)

Default: N/A

Range: N/A

Format: Numeric

Displays the last release cause code. The cause code indicates a reason why the last attempted call was released.

Release Diagnostics(display only)

Default: 00000000

Range: N/A

Format: Numeric

Displays the last release diagnosis. The value in this field explains how the connection was released and reported by the far end of the con-nection.

Retry Counter(display only)

Default: N/A

Range: N/A

Format: Numeric

Displays how many attempts to establish the con-nection have failed. The counter is reset when-ever a connection is successfully established or the signaling side of the connection is restarted.



5-20 255-700-762R11.1



Provisioning Bearer VCCs in Bulk

Beginning in Release 9.1.0, EMS-PSAX has the capability of provisioning for bearer VCCs in bulk (that is, configuring several VCCs simultaneously). To perform bulk provisioning for bearer VCCs, perform the steps in the follow-ing procedure.

Begin

1 From the View ATM Trunking Br Vcc Table window (see Figure 5-7), right-click the desired entry and a menu appears.

2 Select Display.

The UPDATE ATM Trunking Br VCC Entry window appears (see Figure 5-9).

Oper Status(display only)

Default: Idle

Range: N/A

Format: Predefined

Indicates the operational status of the bearer VCC.

Idle The bearer VCC is not transmitting.

OutOfService The bearer VCC is not operational.

Init The bearer VCC is initializing.

Active The bearer VCC is transmitting.

Default: 0

Range:

Format: Numeric

Number of currently active channels for the bearer VCC

Active Chnl Count(display only)

Default: 0

Range: N/A

Format: Numeric

Displays the number of currently active channels for the bearer VCC.

Avail Bandwidth(display only)

Default: 0

Range:

Format: Numeric

Available bandwidth remaining for the bearer VCC.

Wireless Backhaul Applications: This value is static and does not change when bandwidth is used; you must manually keep a record.

* If you are configuring wireless backhaul applications, all parameters selected for the local and remote VCC must have the same value (symmetric), or the bearer VCC will not become active.



255-700-762R11.1 5-21




3 Click Copy.

The Copy Bearer VCC Configuration window appears (see Figure 5-10).

Figure 5-9. UPDATE ATM Trunking Br VCC Entry Window (Bearer VCC Config Page)

Button Function

Bring Into Service Brings this bearer VCC into service.

Take Out of Service Takes this bearer VCC out of service.

Delete Removes this bearer VCC configuration.

Reset Retrieves the current (last saved) configuration.


Copy Copies a range of bearer VCC configurations for bulk provisioning.

Restart Connection Restarts connection establishment procedure for the connections that were not previously set up.

5-22 255-700-762R11.1




4 In the Start At: panel, add a VCC ID number (it must be different from the value displayed in the VCC ID field on the UPDATE ATM Trunking Br VCC Entry window).

5 When finished, click close.

End

Configuring Bearer VCC Profiles

To configure bearer VCC profiles, perform the steps in the following proce-dure.

Begin







4 Under the ATM Trunking Local Node Configuration panel, click the right mouse button and a menu appears. Select Bearer VCC Profile Config Table.

Figure 5-10. Copy Bearer VCC Configuration Window

Button Function

Start Copy Copies a range of bearer VCC configurations for bulk provisioning.


255-700-762R11.1 5-23



The View ATM Trunking Bearer VCC Profile Config Table window appears (see Figure 5-11).

5 In the View ATM Trunking Bearer VCC Profile Config Table window, click the right mouse button and a menu appears.

6 Select Create.

The ADD ATM Trunking Bearer VCC Profile Entry window appears (see Figure 5-12).



8 Click Add.

If this entry is valid, it is added to the View ATM Trunking Bearer VCC Profile Config Table.


10 Click Close.

End

Figure 5-11. View ATM Trunking Bearer VCC Profile Config Table Window

Figure 5-12. View ATM Trunking Bearer VCC Profile Entry Window

Button Function



5-24 255-700-762R11.1



Configuring the DSP Parameters for the Bearer VCC

To configure DSP parameters for the ATM trunking bearer VCC, perform the steps in the following procedure.

Begin









5 In the View ATM Trunking Remote IWF Table window, click the right mouse button and a menu appears (see Figure 5-3). Select Bearer Table.

The View ATM Trunking Br Vcc Table window appears (see Figure 5-7).

Table 5-5. ATM Trunking Bearer VCC Profile Configuration Window Field Descriptions


Profile ID Default: 1

Range: 1-255

Format: Numeric

Indicates the unique identifier of VCC profile within the local IWF.

Number of NB Channel

Default: 24

Range: 1-247

Format: Numeric

Indicates the number of AAL2 channels contained in each bearer VCC created based on this profile. Together with the default algorithm, this is used to calculate the ATM bandwidth requirements.

Profile Source Default: Itu-t

Range: N/A

Format: Predefined

Indicates the organization that defines the audio profile.

Itu-t Indicates that the audio profile is from ITU-T stan-dard.

Other Indicates that the audio profile is not from ITU-T standard.

Profile Audio ID Default: 1

Range: 1-255

Format: Numeric

Indicates the audio profile ID associated with the Profile source field.

If the Profile Source is ITU-T, the valid IDs are 1, 3, or 7.

255-700-762R11.1 5-25



In the View ATM Trunking Br Vcc Table window, click the right mouse but-ton and a menu appears. Select Create.

The ADD ATM Trunking Br VCC Entry window appears (see ).


7 Click Add.

If this entry is valid, it is added to the ATM Trunking Br Vcc Table.


9 Click Close.

End

Figure 5-13. ADD ATM Trunking Br VCC Entry Window (DSP Parameters Page)

5-26 255-700-762R11.1



Table 5-6. ATM Trunking Bearer VCC Parameters Window Field Descriptions


PCM Encoding Default: A-law

Range: N/A

Format: Predefined

Specifies the type of pulse code modulation encoding used.

A-law European companding standard is used.

U-law Mu-law is the North American and Japanese companding standard.

None No companding is done on the connection.

Compression Type Default: None

Range: N/A

Format: Predefined

Specifies the type of voice compression used in this connection.

None No compression is used on the connection.

G726-16K Voice compression ITU-T G.726 standard at 16-Kbps.




G729a-8K Voice compression ITU-T G.729a standard at 8-Kbps.

Audio Profile Src Default: Itu-t

Range: N/A

Format: Predefined

Select the type of audio profile source.

Itu-t ITU-T predefined profile.

Other ATM Forum predefined or user-defined profile.

Audio Profile Id Default: 1

Range: 1–255

Format: Numeric

Audio profile identifier.

Max AAL2 Channel ID

Default: 255

Range: 9–255

Format: Numeric

Specifies the maximum number of channel IDs within this bearer VCC.

Max Frame Length Default: 4095

Range: 1–65535

Format: Numeric

Maximum length of frame mode data.

255-700-762R11.1 5-27



Combined Use Timer

Default: 4

Range: 0–99

Format: Numeric

Specifies the amount of time the host processor will wait for a cell to fill. The combined use timer (CuTimer) is set to zero, so that every ATM cell transmitted contains only one AAL2 packet. The first octet of the AAL2 packet header follows immediately after the Start Field in the ATM cell payload. If the AAL2 packet payload is less than 44 octets, the remainder of the ATM cell payload following the end of the AAL2 packet is filled with zeros as padding. Each increment of the CuTimer is 5 msec waiting time. The default value 4 indicates a wait of 20 msec (4 x 5 msec) before an ATM cell is sent out.

If using the DSP2E/F Voice/Data Server modules, set this value to 1 (5 msec.).

GR-303 Applications: In a GR-303 configuration, set the value to 0 if using non-Lucent IADs.

V5.2 Applications: Set the value to 0 if fax or modem calls are supported. Any value greater than 0 causes jitter to drop fax/modem calls.

Circuit Data Supp Default: Enable

Range: N/A

Format: Predefined

Indicates whether support for circuit data is dis-abled or enabled.

Disable Support for circuit data is disabled.

Enable Support for circuit data is enabled.

Frame Mode Supp Default: Disable

Range: N/A

Format: Predefined

Indicates whether support for frame mode is dis-abled or enabled.

Disable Support for frame mode is disabled.

Enable Support for frame mode is enabled.

Fax Mode Supp Default: Enable

Range: N/A

Format: Predefined

Indicates whether support for fax mode is dis-abled or enabled.

Enable Support for fax mode is enabled.

Disable Support for fax mode is disabled.

CAS Pkt Xport Supp

Default: Disable

Range: N/A

Format: Predefined

Indicates whether support for CAS packet export is disabled or enabled.

Disable Support for CAS packet export is disabled.

Enable Support for CAS packet export is enabled.

Table 5-6. ATM Trunking Bearer VCC Parameters Window Field Descriptions (Continued)


5-28 255-700-762R11.1


Chapter 5 Configuring ATM TrunkingDeleting Bearer VCCs

Deleting Bearer VCCsTo delete a bearer VCC configuration, perform the steps in the following pro-cedure.

Begin

1 From the UPDATE ATM Trunking Br VCC Entry window appears (see Figure 5-9), click Take Out of Service (this button selectable only if the bearer VCC is configured and in service).

2 Click Delete.

DTMF Pkt Xport Supp

Default: Enable

Range: N/A

Format: Predefined

Indicates whether support for DTMF packet export is disabled or enabled.

Enable Support for DTMF packet export is enabled.

Disable Support for DTMF packet export is disabled.

MF-R1 Pkt Xport Supp

Default: Disable

Range: N/A

Format: Predefined

Indicates whether support for multi-frame R1 (NAR protocol) packet export is disabled or enabled.

Disable Support for MF-R1 packet export is disabled.

Enable Support for MF-R1 packet export is enabled.

MF-R2 Pkt Xport Supp

Default: Disable

Range: N/A

Format: Predefined

Indicates whether support for multi-frame R2 (NAR protocol) packet export is disabled or enabled.

Disable Support for MF-R2 packet export is disabled.

Enable Support for MF-R2 packet export is enabled.

Idle Chan Supr Supp

Default: Enable

Range: N/A

Format: Predefined

Indicates whether support for idle channel sup-pression is disabled or enabled.

Enable Support for idle channel suppression is enabled.

Disable Support for idle channel suppression is disabled.

Silence Detect Supp Default: Enable

Range: N/A

Format: Predefined

Indicates whether support for silence detection and suppression is disabled or enabled.

Enable Support for silence detection and suppression is enabled.

Disable Support for silence detection and suppression is disabled.

Table 5-6. ATM Trunking Bearer VCC Parameters Window Field Descriptions (Continued)


255-700-762R11.1 5-29


Chapter 5 Configuring ATM TrunkingCreating a Broadband Routing Entry

Note: You cannot delete a bearer VCC unless it is out of service.

End

Creating a Broadband Routing EntryTo create an ATM trunking broadband routing entry, perform the steps in the following procedure.

Begin







4 Under the ATM Trunking Local Node Configuration panel, click the right mouse button and a menu appears. Select Broadband Routing Table.

The View ATM Trunking Broadband Table window appears (see Figure 5-14).


5 In the View Broadband Table window, click the right mouse button and a menu appears. Select Create.

Figure 5-14. View Broadband Table Window

Button Function




5-30 255-700-762R11.1


Chapter 5 Configuring ATM TrunkingCreating a Broadband Routing Entry

The ADD ATM Trunking Broadband Routing Entry window appears (see Figure 5-15).



7 Click Add.

If this entry is valid, it is added to the ATM Trunking Broadband Routing Table.


9 Click Close.

End

Figure 5-15. ADD ATM Trunking Broadband Routing Entry Window

Button Function



Table 5-7. ADD ATM Trunking Broadband Routing Entry Window Field Descriptions


Broadband Address (Hex)

Default: N/A

Range: N/A

Format: Hexadecimal

Specifies the interworking function ATM addresses for the remote endpoint. Type an address in hexadecimal format up to 20 bytes (160 bits) long (10 groups of 4 characters each).

Num Bits Default: N/A

Range: 1–152

Format: Numeric

Specifies the number of bits for the ATM address mask.

Group ID Default: N/A

Range: 1–255

Format: Numeric

Specifies the group identifier for the broadband ATM address.

255-700-762R11.1 5-31


Chapter 5 Configuring ATM TrunkingCreating a Narrowband Routing Entry

Creating a Narrowband Routing EntryTo create an ATM trunking narrowband routing entry, perform the steps in the following procedure.

Begin







4 On the ATM Trunking Local Node Configuration panel, click the right mouse button and a menu appears. Select Narrowband Routing Table.

The View ATM Trunking Narrowband Table window appears (see Figure 5-16).


5 In the View Narrowband Table window, click the right mouse button and a menu appears. Select Create.

The ADD ATM Trunking Narrowband Routing Entry window appears (see Figure 5-17).

Figure 5-16. View Narrowband Table Window

Button Function




5-32 255-700-762R11.1


Chapter 5 Configuring ATM TrunkingCreating a Narrowband Routing Entry



7 Click Add.

If this entry is valid, it is added to the ATM Trunking Narrowband Rout-ing Table.


9 Click Close.

End

Figure 5-17. ADD ATM Trunking Narrowband Routing Entry Window

Button Function



Table 5-8. ADD ATM Trunking Narrowband Routing Entry Window Field Descriptions


Narrowband Address (Hex)

Default: N/A

Range: N/A

Format: Hexadecimal

Specifies the Interworking function ATM addresses for the remote endpoint. Type an address in hexadecimal format up to 20 bytes (160 bits) long (10 groups of 4 characters each).

Num Bits Default: N/A

Range: 1–152

Format: Numeric

Specifies the number of bits for the ATM address mask.

IWF ID Default: N/A

Range: 1–100

Format: Numeric

Specifies the interworking function identifier (IWF) for the remote IWF.

255-700-762R11.1 5-33


Chapter 5 Configuring ATM TrunkingViewing the Data Channel Table

Viewing the Data Channel TableTo view the ATM trunking data channel table, perform the steps in the fol-lowing procedure.

Begin









5 In the View ATM Trunking Remote IWF Table window, click the right mouse button and a menu appears (see Figure 5-3). Select Data Channel Table.

The View ATM Trunking Data Channel Table window appears (see Figure 5-18).


Figure 5-18. View ATM Trunking Data Channel Table Window

Button Function




5-34 255-700-762R11.1


6 Configuring System Properties

This chapter describes how to configure the properties for your client/server application using the EMS-PSAX EMS.

Configuring User PropertiesPerform the steps in the following procedure to view or change user proper-ties for your EMS-PSAX.

Configuring EMS-PSAX Properties

Begin

1 Select View > Properties on the Menu Bar.

The User Properties window appears (see Figure 6-1).

2 Select the values for each panel on the User Properties window as described in Table 6-1.

3 To apply the values you set, click Apply.

4 Click Close if you are done with the User Properties window, or see ”Specifying the Adobe Acrobat Reader Path” on page 6-4 to specify a Acrobat Reader path on your workstation.

End


255-700-762R11.1 6-1

Chapter 6 Configuring System PropertiesConfiguring User Properties


Figure 6-1. User Properties Window

Button Function

Browse Allows you to browse the local hard drive to find the path where Adobe Acrobat Reader is located.

Apply Applies the values you set in this window.

Cancel Closes this window.

6-2 255-700-762R11.1



Table 6-1. Panel Descriptions for the User Properties Window


Documentation Panel

Acrobat Reader path for viewing user documenta-tion

Default: C:\Program Files\Adobe\Acrobat5.0\ReaderAcroRd32 (Win-dows)

Default: /opt/Acrobat5/bin/acroread (Solaris)

Range: N/A


Indicates the path to open Adobe Acrobat Reader on your workstation. If the default value is incor-rect, enter the correct path and filename, or click Browse to specify another path and filename (see Figure 6-2).The correct pathname enables you to view the Release 11.1.0 EMS-PSAX user guides when you select the appropriate items under the Help menu in the EMS-PSAX Menu Bar. See ”Specifying the Adobe Acrobat Reader Path” on page 6-4 for a procedure to specify a Acrobat Reader path on your workstation.

Debug Level Panel

Default: None

Range: N/A

Format: Predefined

Indicates what system log information will be created.

None No system log file will be created (no debugging).

Normal User-specified actions are logged, along with any error messages returned by way of exceptions (normal debugging). Traps are also logged into the files.

Extensive Stack traces, and any other developer-required debugging information is logged, along with the trace information.

NSAP Format Panel

Use NSAP format Default: N/A

Range: N/A

(variable pre-defined algorithm)Format: Alphanumeric

The Navis® NSAP format will be used in the cre-ation and configuration of the NSAP address database and SPVC NSAP addresses. The text entry field remains ghosted until you click the checkbox beside Use NSAP format. Type navis in the text entry field (no other values are applicable).

255-700-762R11.1 6-3



Specifying the Adobe Acrobat Reader Path

Perform the steps in the following procedure to specify the path you want the EMS-PSAX EMS to use to open Adobe Acrobat Reader files so you can view EMS-PSAX documentation.

Begin

1 To select a path and filename other than the default, click Browse.

The Browse for Acrobat Reader Path window appears (see Figure 6-2).

Timeout Length Panel

Length of time in minutes to logoff due to inactivity

Default: Disabled

Range: Disabled or 10–60

Format: Minutes

Specifies the period of time that the session will remain active after the last detected keystroke or mouse click. 10 seconds before the session is automatically terminated at the end of the ses-sion period, you hear three audio alerts from the warning bell. If you do not perform a keystroke or mouse click during this 10-second period, the EMS-PSAX system will terminate. The EMS-PSAX client saves all the configurations of all open devices before it closes.You must have Administrator or Configurator security access privileges to change the value in this field.

Disabled Indicates that the session will remain active until you exit the EMS-PSAX system.

10–60 Indicates that the session will remain active for specified number of minutes after the last detected keystroke or mouse click. After the time has elapsed, the warning bell rings for 10 seconds before terminating the session.

Table 6-1. Panel Descriptions for the User Properties Window


Figure 6-2. Browse for Acrobat Reader Path Window

6-4 255-700-762R11.1


Chapter 6 Configuring System PropertiesEMS-PSAX Logging

2 In the Look In: field, select the drive where Acrobat Reader resides on your workstation.

3 Double-click the folders until you find Acrobat Reader.

4 Click on the filename.

The filename appears in the File name: field.

5 Click OK.

End

For more information about the EMS-PSAX system log and file properties, see the section, “EMS-PSAX System Log File.”

EMS-PSAX LoggingLogging is incorporated into the EMS-PSAX server to help you keep track of what actions the server performs. The logging also helps technicians and other personnel who troubleshoot problems to obtain debug information when server errors occur in testing labs and at client sites.

EMS-PSAX System Log Files

Security Log Files The security log is a log file found in the directory \opt\NEP\logs and is cre-ated for administrative use. It is created on the server side of the Cli-ent/Server application. This log file displays the following information:

• Logged-on users

• The date and time when the user logs on and off

• The PSAX device a user logged on to (by IP address)

• Exception errors pertaining to

~ Failure to access a PSAX device

~ Failure to open a device

~ Failure to log into the EMS-PSAX (entered incorrect password, etc.)

255-700-762R11.1 6-5



Each log file is named security.log.n, where n can be a value from 0–6 (for example, security.log.0). When the first log file, default 0, reaches approxi-mately 1 MB in size, the second log file, 1, is created (for example, secu-rity.log.1). This continues until it reaches the final log file, number 6, and then returns to log file 0. You can specify a different maximum value in the aqv file by editing the logfile.number field (see Table 6-2 on page 6-9).

The log file is automatically saved, so when you restart the server, the appending of the security log continues until it reaches the 1 MB size.

Config Log Files

The config log (see Figure 6-4) is a log file found in the directory \opt\NEP\logs and is created for administrative use. It is created on the server side of the Client/Server application whenever a user opens a PSAX device in the EMS-PSAX, if logging is enabled within the aqvproperties file.

This log file displays the following information:

• The name of the user who has logged on

• The time when the user logs on and off

• The PSAX device a user logged on to (by IP address)

Each log file is named config.log.n, where n can be a value from 0–6 (for example, config.log.0). When the first log file, default 0, reaches approxi-mately 1 MB in size, the second log file, 1, is created (for example, secu-rity.log.1). This continues until it reaches the final log file, number 6, and

Figure 6-3. security.log.0 Log File

6-6 255-700-762R11.1



then returns to log file 0. You can specify a different maximum value in the aqv file by editing the logfile.number field.

The log file is automatically saved, so when you restart the EMS-PSAX server, the appending of the config log continues until it reaches the 1 MB size.

Location of Log Files Log files are located under the logs directory in the EMS-PSAX home direc-tory.

Sun Solaris

On Solaris workstations, the default EMS-PSAX base directory is /opt/NEP. Both the EMS-PSAX server and EMS-PSAX client will detect the directory by searching for the aqv file in the directories listed in the CLASSPATH environ-ment variable. The aqv file is found in the /opt/NEP/conf directory. The log files are found in the /opt/NEP/logs directory.

Windows

On Windows XP/2000/NT workstations, the default EMS-PSAX base direc-tory is Program Files/Lucent Technologies/NEP. The aqv file is found in the NEP/conf directory. The log files are found in the NEP/logs directory.

Log Message Format The log message consists of the following information (see Figure 6-3):

• Time stamp—date and time that a user logs on and off, including failed logon attempts

• IP address of the PSAX device the user accesses, including failed logon attempts

• Object type affected—module, port, channel, interface, connection, switch (for Site-Specific, PNNI, IISP Routing, Diagnostics, and software manage-ment information)

• Identifier of module/port/channel/interface/connection (where applicable)

• Request type—Create, Delete, Configure

• Message—trap, exception thrown, or other informational message.

Figure 6-4. config.log.0 Log File

255-700-762R11.1 6-7



EMS-PSAX System Properties

The aqv file consists of the EMS-PSAX user-configurable attributes. As shown in Figure 6-5, the format for configuring these attributes is the attribute name, the equals sign, and the desired value, with no spaces.

Note: If you do not specify the values you wish to use, only the default values will be used and displayed.

To generate a log file, logging must be enabled within the aqv file by entering 1 (normal debugging mode) in the debug.level field (see Figure 6-5).

The current list of configurable EMS-PSAX attributes is described in Table 6-2.

Figure 6-5. aqv Log File

6-8 255-700-762R11.1



Table 6-2. Configurable EMS-PSAX Attributes in the aqv File

Attribute Name Values Description

poll.deletenode Default: 30

Range: Any Number

Format: Numeric (minutes)

Specifies the number of minutes which the EMS-PSAX poll server will continue to poll an inactive PSAX device before it deletes it from its list of PSAX devices to be polled.

reader.unix Default: /opt/Acrobat5/bin/acroread

Range: N/A

Format: Directory pathname

Indicates the path on your computer where the Acrobat Reader executable file is located for a Unix (Solaris) system.

Note: For this to work correctly on Windows workstations, enter two slashes between each directory in the path specification.

snmp.timeout Default: 5

Range: Any Number


Indicates the time in seconds that the EMS-PSAX system will wait for a get response from the PSAX device or SNMP agent.

Note: This value can be overridden by the value (if any) specified in the SNMP Timeout (Seconds) field on the Add Device Dialog window (see Chapter 3).

ping.feature Default: false

Range: N/A

Format: Predefined

Indicates whether the EMS-PSAX will ping any PSAX devices.

false Indicates that this feature is disabled; the EMS-PSAX will not ping any PSAX devices.

true Indicates that this feature is enabled; the EMS-PSAX will ping open PSAX devices to check whether or note they are reachable.

poll.interval Default: 5

Range: Any Number


Indicates that when you launch ovw, the EMS-PSAX server initiates a poll server and per-forms a poll on the PSAX device for the module and port status. The poll interval tells the number of minutes that the EMS-PSAX poll server will poll the PSAX device for module and port sta-tuses.

connection.restore Default: true

Range: N/A

Format: Predefined

Indicates whether the Connection Restore fea-ture is enabled or disabled. See the section, “Restoring Connections,” in the Navis® EMS-PSAX Connections Provisioning Guide

false The Connection Restore feature is disabled.

true The Connection Restore feature is enabled.

ping.sleeptime Default: 5

Range: Any number except zero


Indicates the number of minutes you want the EMS-PSAX to wait between each connectivity check; that is, how often the device should be pinged.

Note: If you change this value, you must restart the EMS-PSAX for the change to take effect.

255-700-762R11.1 6-9



conn.segment.view Default: false

Range: N/A

Format: Predefined

Allows you to load a segment view of connec-tions in the EMS-PSAX client depending on the settings on the Filter page.

false The Filter-Based Loading of Connections feature is disabled.

true The Filter-Based Loading of Connections feature is enabled.

reader.win Default: C:\\Pro-gram Files\\Adobe\Acrobat 5.0\\Reader\\AcroRd32.exe

Range: N/A

Format: Directory pathname

Indicates the path on your computer where the Acrobat Reader executable file is located for a Windows or Unix system.

Note: For this to work correctly on Windows workstations, enter two slashes between each directory in the path specification.

server.name Default: ACSERVER

Range: 1–75

Format: Alphanumeric,without spaces

Indicates the name of the server to which this instance of the EMS-PSAX is connected, regis-tered with osagent. This must be the same on both the server and client. It is the only config-urable environmental value for a client. To use the default name, click Use Default Server Name.

Note: Lucent recommends that you change the default name, ACSERVER, to another name of your choosing. You can also change this name during the client-only or client/server installa-tion. For more information, see the Navis® EMS-PSAX Quick-Start Guide for the Client/Server Application.

ping.maxtimeouts Default: 3

Range:

Format:

Indicates the maximum number of times you want the EMS-PSAX to retry connecting to the device before timing out and informing the EMS-PSAX client.


poll.debug Default: false

Range: N/A

Format: Predefined

Indicates whether a log file is created.

false Indicates that no log file is created.

true Creates a log file called poll.debug.log.x (where x can be a value from 0–6) in the conf/logs direc-tory, displaying the results of each poll that the poll server performs on each PSAX device. This log file is approximately 1 Mb.

The poll server only functions on the cli-ent/server version of the EMS-PSAX EMS when running HP OpenView NNM.



6-10 255-700-762R11.1



server.pre-load.devices

Default: true

Range: N/A

Format: Checkbox

Indicates—during the launching of the EMS-PSAX server— whether or not the EMS-PSAX server should preload any devices in the Device List window. Individual device pre-loading can be turned on and off in the Device List window by checking or unchecking the checkbox next to the Preload Devices field.

See the section, “Preloading Devices,” in Chapter 3.

true Indicates that the EMS-PSAX server will pre-load—in the Device List window—those devices that were previously flagged for preloading.

false Indicates that the EMS-PSAX server will not pre-load any devices in the Device List window.

server.pre-load.maxV2CThreads

Default: 5

Range: 1–5

Format: Numeric

Specifies the maximum number of threads, which can be spawned to simultaneously load, all the SNMPv2c PSAX devices with the preload option set. Adjust this value on a per-network basis to maximize EMS-PSAX performance.

server.pre-load.maxV3CThreads

Default: 5

Range: 1–5

Format: Numeric

Specifies the maximum number of threads, which can be spawned to simultaneously load, all the SNMPv3c PSAX devices with the preload option set. Adjust this value on a per-network basis to maximize EMS-PSAX performance.

server.client.ping Default: true

Range: N/A

Format: Checkbox

Indicates whether the EMS-PSAX server should ping the client, and check whether the client is reachable.

true The server will check whether clients are reach-able, and free resources if the client is not reach-able.

false The server will not check whether clients are reachable.

server.cli-ent.max.failures

Default: 3

Range: N/A

Format: Numeric

Indicates the number of times the EMS-PSAX server attempts to connect to the client can fail before the cleanup of the client session can occur.

server.cli-ent.ping.interval

Default: 180

Range: N/A

Format: Seconds

Indicates the time (in seconds) the EMS-PSAX server should wait before polling the client each time.



255-700-762R11.1 6-11



client.server.ping Default: true

Range: N/A

Format: Numeric

Indicates whether the EMS-PSAX client should ping the EMS-PSAX server, check whether the server is reachable, and alert if the server is not reachable.

true The client will check whether the server is reach-able, and alert if the server is not reachable.

false The client will check whether the server is reach-able.

client.server.max.failures

Default: 3

Range: N/A

Format: Numeric

Indicates the number of times EMS-PSAX Client attempts to connect to the Server can fail before the alerting the user.

client.server.ping.interval

Default: 180

Range: N/A

Format: Seconds

Indicates the time the EMS-PSAX client should wait before pinging the EMS-PSAX server each time.

client.server.agent.addr

Default: 0.0.0.0

Range: N/A


Indicates the IP Address of the EMS-PSAX server Host System, when the EMS-PSAX client and server are located in different subnets. This is an EMS-PSAX client property.

event.channel.port Default: 30000

Range: N/A

Format: Numeric

Indicates the port number which the event chan-nel uses in the EMS-PSAX client. This property is only applicable when the firewall.client property is set to true.

event.channel.queue.size

Default: 1000

Range: N/A

Format: Numeric

Indicates the maximum queue length of the event channel in the EMS-PSAX client.

user.auth Default: local

Range: N/A

Format: Predefined

Indicates the mode of user authentication.

local Authentication uses the local user database.

radius Authentication is done by the RADIUS server.

both Authentication is done by RADIUS server, but if for some reason RADIUS server cannot be con-tacted, authentication is done using the local user database.

logfile.size Default: 1 Mb

Range: 0–1048576


Indicates the maximum size of the log file. Once the log file reaches its capacity, the file is rotated and a new log file is created.

Note: If you do not specify this field and value, it will not be displayed in the aqv.properties file.

logfile.number Default: 7

Range: 0–6

Format: Numeric

Indicates the maximum number of log files cre-ated. Once the maximum number of logs are cre-ated, the log files are rotated.

Note: If you do not specify this field and value, it will not be displayed in the aqv.properties file.



6-12 255-700-762R11.1



snmp.retries Default: 1

Range: Any Number

Format: Numeric (retries)

Indicates the number of timeout retries before the EMS-PSAX considers the PSAX device unreachable.

Note: This value can be overridden by the value (if any) specified in the SNMP Retries Count field on the Add Device Dialog window (see Chapter 3).

client.timeout Default: disabled

Range: Disabled or 10–60

Format: Minutes

Specifies the period of time that the session will remain active after the last detected keystroke or mouse click. Ten seconds before the session is automatically terminated at the end of the ses-sion period, you hear three audio alerts from the warning bell. If you do not perform a keystroke or mouse click during this 10-second period, the EMS-PSAX system will terminate. The EMS-PSAX client saves all the configurations of all open devices before it closes.

disabled Indicates that the session will remain active until you exit the EMS-PSAX system.

10–60 Indicates that the session will remain active for 10 minutes after the last detected keystroke or mouse click. After 10 minutes, the warning bell rings for 10 seconds before terminating the ses-sion.

ping.timeout.wait Default: 5

Range: N/A

Format: Predefined

Indicates the number of seconds you want the EMS-PSAX to wait for the ping if it were to time out.


debug.level Default: 0

Range: 0–2

Format: Numeric

Indicates that the debug level setting is a server-specific setting. Even if normal (1) or extensive (2) is selected on a client (other than the server machine), no log files will be created.

0 Indicates that the default value indicates that no system log file will be created (no debugging).

1 Indicates that user-specified actions (actions done on the client side that cause the server to com-municate with the PSAX device) are logged along with any error messages returned by way of exceptions (normal debugging). Traps are also logged into this file.

2 Indicates that stack traces, and any other devel-oper-required debug information is logged along with the trace information at this level (extended debugging).



255-700-762R11.1 6-13


Chapter 6 Configuring System PropertiesAdding a PSAX Icon to an HP OpenView NNM Map

Adding a PSAX Icon to an HP OpenView NNM MapThe HP OpenView NNM automatic discovery process would work the usual way for PSAX devices too. But if PSAX devices are in a different sub network than your HP OpenView NNM workstation network, use the loadhosts com-mand (especially if you do not want HP OpenView NNM to discover and dis-play every pingable entity, just PSAX devices). Using loadhosts with -p and -c flags (for example: type loadhosts -p -c PSAX IP address to be added)

HP OpenView NNM by itself only monitors the reachabilty to PSAX nodes (that is, IP connectivity). If a PSAX device goes down and a ping fails, the PSAX device will be represented with a symbol color change in the HP Open-View NNM map.

nsap.format Default: navis

Range: N/A

Format: Predefined

Indicates that the Navis NSAP format will be used in the creation and configuration of the NSAP address database and SPVC NSAP addresses. This entry appears only when a value is specified in the Use NSAP Format field on the User Properties window and applied (see Chapter 5).

Note: If you do not specify this field and value, it will not be used or displayed.

max.notificationIDs Default: 150

Range: N/A

Format: Numeric

Indicates the maximum number of SNMP Notifi-cation (traps or informs) request IDs to be main-tained in the list per device (IP address) by the EMS-PSAX Notification Receiver. When a notifi-cation is processed by the EMS-PSAX server, its request ID is stored in that list. If the same notifi-cation is resent by the PSAX device, and it has already been processed by EMS-PSAX server, it will not be processed again. This property indi-cates the limit when the list is recycled.

server.pollserver.alarm.table

Default: False Indicates whether the Active Alarm Table can be used to update PSAX icons on the HP OpenView NNM Map.

false Indicates that the Active Alarm Table will not be used to update PSAX icons on the HP OpenView NNM Map.

true Indicates that the Active Alarm Table will be used to update PSAX icons on the HP OpenView NNM Map.

Note: When you set the server.pollserver.alrm.table value as true, you should enable the Active Alarm Table field in the site specific window and the PSAX system should have version 11.0 or higher.



6-14 255-700-762R11.1


Chapter 6 Configuring System PropertiesViewing the EMS-PSAX Poll Server

To monitor and map PSAX-specific alarms, an addition symbol called “CPU Status” is automatically added inside all PSAX symbols by an EMS-PSAX pro-cess. This symbol will then change color based on traps received from a PSAX device. These color changes will be propagated up the map based on scheme you have chosen for propagation of symbol colors up the map.

Viewing the EMS-PSAX Poll ServerThe EMS-PSAX Poll Server. The Poll Server polls all the PSAX devices in the network periodically and maintains their status.

When an HP OpenView NNM map (OVW) is launched on a workstation run-ning the EMS-PSAX client with NNM or client/server with NNM, the status of all the PSAX device symbols on the map are periodically updated by the EMS-PSAX Poll Client. Only the PSAX symbols in the Node Level of the OVW map are updated, not the symbols on the Network and Segment Lev-els.

To view the Poll status of a device, perform the steps in the following proce-dure.

Note: Before you perform the steps in the following procedure, the EMS-PSAX Client/Server application and HP OpenView NNM must be installed on the Sun Solaris workstation.

Begin

1 Log in to the Solaris workstation.

2 At the command prompt, type:

/opt/OV/bin/ovw &

The Poll Client starts as soon as you enter this command, and the Root window appears (see Figure 6-6).

255-700-762R11.1 6-15



3 To start or stop polling, select either Navis EMS-PSAX > PSAX > Start Polling, or Navis EMS-PSAX > PSAX > Stop Polling from the menu the active window.

4 Double-click the Internet symbol.

The Internet window appears (see Figure 6-7).

Figure 6-6. Root Window (Displaying Internet)

6-16 255-700-762R11.1



5 Double-click the PSAX symbol for which you want to view the CPU sta-tus.

The window for the PSAX device appears (see Figure 6-8).

Figure 6-7. Internet Window (Displaying PSAX Map)

255-700-762R11.1 6-17



The CPU status symbol changes color depending on the poll status of the par-ent PSAX device. The colors for the CPU Status symbol within the PSAX sym-bols on the OVW map are described in Table 6-3. The color can be com-pounded and viewed on the parent icon.

Figure 6-8. PSAX Symbol 172.26.41.83 (Displaying CPU Status Symbol)

6-18 255-700-762R11.1


Chapter 6 Configuring System PropertiesRADIUS Server Configuration

End

RADIUS Server Configuration

The RADIUS server feature1 introduced in Release 6.1.0 provides a central-ized user list for all EMS-PSAX servers. You have the option of configuring only one RADIUS server, or two RADIUS servers (a primary and secondary RADIUS server) for redundancy. The RADIUS server properties are located in the directory /opt/NEP/conf/radius.properties.

In order for a RADIUS user to be authenticated, the RADIUS server has to send a vendor-specific attribute in Access-Accept packets containing the appropriate PSAX security-level attribute of 0, 1, or 2 (see the attribute val-ues in the section, “Configuring the RADIUS Server”.

Configuring the RADIUS Server

You must configure the following parameters on the RADIUS server. These parameters are typically found in the RADIUS dictionary:

• Vendor name for vendor-specific attribute:

~ Name: “Lucent-PSAX”

~ Value: “1751”

• Attribute information:

~ Attribute name: “PSAX-Security-Level”

Table 6-3. PSAX Symbol Color Definitions

If the CPU Status

Color is...

Then the OV Type is...

Meaning...

Red OV_CRITICAL The PSAX device is not reachable using the Ping command nor SNMP.

Orange OV_MAJOR The operational status of any module installed in the PSAX device is not Primary, except for modules that are backups or not configured.

Yellow OV_MINOR The line status of at least one port of a mod-ule installed in the PSAX device has an alarm (for example, loss of signal).

Green OV_NORMAL The status is not any of the above men-tioned ones.

Blue OV_UNKNOWN This is the initial interim period, when a RW Poll Client session has started, and is waiting for the first status update from Poll Server.

1 The EMS-PSAX does not support the RADIUS Support for Console/Telnet Access Feature introduced in PSAX Release 8.1.0.

255-700-762R11.1 6-19



~ Vendor: “Lucent-PSAX”

~ Code or Vendor Type: “1”

~ Attribute type: “enumeration” (for NavisRadius)

~ PSAX security-level attribute values:

• 0–Superuser (similar to ADMIN1 security access privileges)

• 1–Readwrite (similar to CONFIG1 security access privileges)

• 2–Readonly (similar to MONITOR1 security access privileges)

Note: See Chapter 2 for details on the different security access privileges available in the EMS-PSAX system.

The PSAX security-level attribute must be associated with any user that will log into the EMS-PSAX. Otherwise, the EMS-PSAX will not allow that user to log in.

After configuring the RADIUS server properties, you can log into the EMS-PSAX with your RADIUS username and password. The EMS-PSAX Title Bar displays the access level associated with your RADIUS account.

Configuring RADIUS Properties in the EMS-PSAX

Setting Up the Aqv.properties File for the RADIUS Server

To use a RADIUS server, you must set the user.authentication property in the aqv.properties file (on the both the client and server workstations) to either radius or both. For information on the user.authentication property, see Chapter 6.

Setting Up the Radius.properties for the RADIUS Server

The radius.properties file is displayed in Figure 6-9. To set the RADIUS prop-erties to access a RADIUS server for user authentication, see Table 6-4.

Figure 6-9. The radius.properties File

6-20 255-700-762R11.1



Table 6-4. Field Descriptions for the RADIUS Properties File


radius.server.primary.ip

Default: 0.0.0.0

Range: N/A


The IP address of the primary RADIUS server. This server is always used first.

radius.server.secondary.ip

Default: 0.0.0.0

Range: N/A


The IP address of the secondary RADIUS server. This server is consulted only if authentication with the primary RADIUS server fails or if it is unreachable.

radius.server.timeout

Default: 3

Range: N/A

Format: Numeric

Indicates the number of seconds between attempts to contact each RADIUS server.

radius.server.attempts

Default: 3

Range: N/A

Format: Numeric

Indicates the number of times the EMS-PSAX will try to contact each RADIUS server. After all attempts, the EMS-PSAX will try to reach the sec-ondary RADIUS server.

radius.server.pri-mary.secret

Default: 0

Range: 1–16

Format: ASCII Characters

Indicates the shared secret between the EMS-PSAX RADIUS client and the primary RADIUS server. You cannot leave this field blank.

radius.server.sec-ondary.secret

Default: 0

Range: 1–16

Format: ASCII Characters

Indicates the shared secret between the EMS-PSAX RADIUS client and the secondary RADIUS server. You cannot leave this field blank.

radius.server.pri-mary.port

Default: 1812

Range: N/A

Format: Numeric

Indicates the UDP port on the primary RADIUS server that listens for authentication requests. Do not change the default value unless you have an older or non-standard RADIUS server configura-tion.

radius.server.sec-ondary.port

Default: 1812

Range: N/A

Format: Numeric

Indicates the UDP port on the secondary RADIUS server that listens for authentication requests. Do not change the default value unless you have an older or non-standard RADIUS server configura-tion.

radius.server.vendor.id

Range: 1751

Format: N/A

Format: Numeric

Indicates the vendor identifier for the RADIUS Lucent-PSAX vendor-specific attribute. Do not change the default value for PSAX V09.00.C00.

radius.server.vendor.type

Default: 1

Format: N/A

Format: Numeric

Identifies the Lucent-PSAX vendor-specific attribute as “PSAX-Security-Level.” Do not change this value for PSAX V09.00.C00.

255-700-762R11.1 6-21



6-22 255-700-762R11.1


7 Fault Monitoring

Overview of Fault Monitoring in the EMS-PSAXThis chapter describes how to do the following tasks:

• Navigate the Log page

• Find the description for a trap message

• Save the trap log

• Find specific text within a trap log

• Copy, cut, paste, and delete trap messages

• Activate traps

• Disconnect clients from the server

• Forcefully unload clients from the server

• Obtain Module Hardware Information

~ Hardware Operating Status Data

~ LED Status Indicator Data

~ Port Configuration Data

• Setting filters for the Active Alarm Table

Event, Alarm, and Trap MessagesThe EMS-PSAX system software identifies and displays trap messages from PSAX systems. Upon launching a session of the EMS-PSAX system, the EMS polls the specified PSAX device for the latest configuration information. The GUI is events-oriented, and thus, automatically updates each time the man-agement station receives a trap. You can refresh the window at any time by selecting Device > Refresh in the Device Menu Bar.

The EMS-PSAX system collects events from all opened devices for viewing by each individual device in its Log page (see Figure 7-2 and “EMS-PSAX Log Page”). You can use this log to troubleshoot a problem or to verify provision-ing changes. The EMS-PSAX system also uses trap messages to know when to retrieve new configuration information to update its GUIs, parameter fields and tables.

Note: Trap messages will appear only from the time that the device was opened in the EMS-PSAX GUI. To view previous traps, log into the console interface.

PSAX devices send a trap message when the PSAX device configuration changes because of a provisioning event or an abnormality in the operation of the device. These trap messages are monitored by the EMS-PSAX system, HP OpenView NNM, or another type of SNMP trap collector.


255-700-762R11.1 7-1

Chapter 7 Fault MonitoringEvent, Alarm, and Trap Messages

In SNMP, the actual text displayed on the Event Display window of an EMS/NMS (for example, see Figure 7-1) is a function of the NMS/EMS soft-ware being used. The NMS/EMS software uses the trap “DESCRIPTION” sec-tion of the PSAX MIB (see the document, PacketStar® PSAX Simple Network Management Protocol (SNMP) Trap Reference Guide) and other trap configuration information to display text on the Event Display window of an NMS/EMS. No text is sent in SNMP trap PDUs unless it is sent as a variable.

NMS/EMS software uses the PSAX MIB and other configurations to do the translation between OIDs (the .1.3.6.... numbers actually sent in an SNMP PDU—see the Event Identifier (Numeric) field in Figure 7-1) and text. The PSAX MIB shows the OIDs of all traps that the PSAX device sends, OIDs of variables sent with the trap, and valid ranges and enumerator (predefined text values for variables) descriptions for variables sent with the trap.

When integrated with HP OpenView NNM, the EMS-PSAX system delivers extensive network-level management features including network auto-dis-covery, hierarchical network topology maps (from which individual front panel views can be launched), centralized and customized event monitoring, statistics collection, and graphing.

HP OpenView NNM collects events from all devices that have designated its workstation or server as a trap destination. A finite number of messages are stored, and the oldest messages are discarded. For PSAX device management, these OpenView logs are better suited for central collection to assess the over-all stability of the network. Using the event manager in HP OpenView NNM, you can acknowledge the messages and trace their sources.

7-2 255-700-762R11.1


Chapter 7 Fault MonitoringEMS-PSAX Log Page

EMS-PSAX Log Page

Overview of the EMS-PSAX Log Page

Clicking the Log tab within the Device window displays all SNMP traps received by the EMS-PSAX server for a specific PSAX system while that PSAX system is open in the EMS-PSAX system. To be viewed in the EMS-PSAX sys-tem, traps must be stamped with the same IP address as the element that is currently being managed by the system. The EMS-PSAX server address IP address must be designated to receive traps.

Figure 7-1. Sample Event Display Window

255-700-762R11.1 7-3


Chapter 7 Fault MonitoringEMS-PSAX Log Page

Note: The EMS-PSAX system collects traps for a particular PSAX device only while the device is open. To view traps issued prior to the launching of the EMS-PSAX system for a particular device, see the Events Browser in the underlying HP OpenView NNM, or the trap log in the PSAX console interface.

The format of the trap messages displayed on the Log page is as follows:

Trap Msg: n [Month Day, Year Hour:Minute:Seconds AM/PM] Trap: Name of trap from the PSAX MIB

Name of Variable (if present) from the PSAX MIB sent with the trap=Value

Note: A trap message may contain any number of variables, including none.

Log Page Menu Options

The right-click menu options are described in Table 7-1.

Figure 7-2. Log Page

Table 7-1. Menu Options for the Log Page

Menu Option Function

Trap Descriptions Allows you to find the description for a specific trap displayed on the Log page.

Select All Selects (highlights) all the traps in the log.

Copy Copies any selected data in the Log tab to the clipboard. This data can then be pasted from the clipboard into another application, such as MS Word or Wordpad.

7-4 255-700-762R11.1


Chapter 7 Fault MonitoringTrap Descriptions

Trap Descriptions

Overview of Enhanced Trap Descriptions Feature

The PSAX system provides the capability to display SNMP trap messages on the console interface and on the Navis® EMS-PSAX. The trap message log is 128 KB in size and can hold up to 2,080 trap messages. If the trap log is full, the PSAX system dumps trap messages on a FIFO (first in, first out) basis. External SNMP managers can perform various functions in the PSAX system, and also receive trap and notification messages. The SNMP trap message log provides the following functions on the console interface and the EMS-PSAX:

• Searching for all instances of a specific character string in the log

• Viewing detailed information, the trap message help, for one or more trap messages

The procedure to access the console interface Trap Log Display window and decriptions of the SNMP trap messages are provided in the document, PacketStar® PSAX Simple Network Management Protocol (SNMP) Trap Reference Guide.

Finding a Trap Message Description

To obtain the description for a trap message, perform the steps in the follow-ing procedure.

Cut Cuts the selected data from the trap log and stores this data in the clip-board. The data can then be pasted from the clipboard into another application, such as Microsoft Word or Wordpad.Note: This action permanently removes the text from the trap log in the EMS-PSAX GUI; however, you can view all traps by logging into the console interface.

Delete Selection Deletes the selected data from the trap log (see Figure 7-13).

Save As Saves the trap log in a file that you specify (see “Saving the Trap Log”).

Find in Log Searches the trap log for text that you enter (see “Finding Text in a Trap Log”).

Table 7-1. Menu Options for the Log Page


255-700-762R11.1 7-5



Begin

1 From the Log page, right-click the mouse and a menu appears (see Figure 7-2). Select Trap Description.

The Enhanced Trap Description window appears (see Figure 7-3).

The buttons on this page have the following functions:

2 In the Enter Trap Message No field, enter the trap message number and click Get Description.

Figure 7-3. Enhanced Trap Description Window

Button Function

Get Description Searches the trap messages in the Log page for the trap message associated with the number entered in the Enter Trap Message No field, and displays the descrip-tion in the Enhanced Trap Description window.


7-6 255-700-762R11.1



The description of the trap message is displayed in the Enhanced Trap Description window (see Figure 7-4). If you make a mistake, a message appears (see Figure 7-5).

3 When you are finished searching and viewing trap message descriptions, click Close on the Enhanced Trap Description window.

End

Figure 7-4. Enhanced Trap Description Window (Displaying Description)

Figure 7-5. Trap Message Not Found Window

255-700-762R11.1 7-7


Chapter 7 Fault MonitoringSaving the Trap Log

Saving the Trap LogIf you select Save As from the right-click menu, the Save window appears (see Figure 7-6).

You must specify the folder in which you want to save the log in the Look in: pull-down menu (see Figure 7-7).

Click Save to save the log file, or click Cancel to go back to the Log tab.

Finding Text in a Trap LogTo search for text in a trap log, perform the steps in the following procedure.

Figure 7-6. Save Window

Figure 7-7. Save Dialog Box (Displaying Menu)

7-8 255-700-762R11.1


Chapter 7 Fault MonitoringFinding Text in a Trap Log

Begin

1 In the Log page, right-click the mouse button and a menu appears. Select Find in Log.

The Find in Log window appears (see Figure 7-8).

2 Click Find.

3 If the EMS-PSAX system finds the text you entered in the text box, that text will become highlighted in the Log page (see Figure 7-9). Click Find repeatedly to find other instances of this string within the Log page. Select Backward to search in reverse order.

4 To search for a different text string, click Clear, enter the new text string in the text box, and click Find.

While searching forward on the Log page (from the top to the bottom), when the final instance of the string is selected on the bottom of the page, the fol-lowing window appears (see Figure 7-10), confirming whether you want to continue searching forward from the beginning of the log.

5 Click Yes to continue the search or No to cancel the search.

While searching backward on the Log page (from the bottom to top), when the first instance of the string is selected on the top of the page, the following window appears (see Figure 7-11), confirming whether you want to con-tinue searching backward from the end of the log.

6 Click Yes to continue the search or No to cancel the search.

7 When finished, click Close.

End


Figure 7-8. Find in Log Window

Button Function

Find Searches for the next instance of the specified string entered in the text box.

Clear Removes text entered in the text box.

Close Removes this window from the Log tab.

255-700-762R11.1 7-9


Chapter 7 Fault MonitoringFinding Text in a Trap Log

The descriptions for the fields in the Find in Log window are given in Table 7-2.

Table 7-2. Field Descriptions for the Find in Log Window

Field Name Function

Find: Enter text that you want to search for within the trap log.

Case Sensitive Select this option if you want the EMS-PSAX system to find only the text that matches the case of the text you entered in the text box.

Backward Select this option to search the trap log backwards from where your cur-sor lies on the screen.

Figure 7-9. Find in Log Window

Figure 7-10. End of Log Window

Figure 7-11. Beginning of Log Window

7-10 255-700-762R11.1


Chapter 7 Fault MonitoringCopying Trap Messages

Copying Trap MessagesTo copy a trap message from the Log page and paste it into a text editor, per-form the steps in the following procedure.

Begin

1 Using the left mouse button, select the text that you want to copy from the Log page.

2 Click the right mouse button and a menu appears. Select Copy.

The selected text is copied from the Log page and onto a clipboard. You can then paste the information using the other application that you wish.

End

Cutting and Pasting Trap MessagesTo remove a trap message from the Log page and paste it into a text editor, perform the steps in the following procedure.

Begin

1 Using the left mouse button, select the text that you want to delete from the Log page.

2 Click the right mouse button and a menu appears. Select Cut.


3 Click Yes to delete the selected text, or No to cancel.

If you clicked Yes, the selected text is removed from the Log page and onto a clipboard. You can then paste the information using the other application that you wish. If you clicked No, the selected text remains highlighted in the Log page.

End

Deleting Trap MessagesTo delete a trap message, perform the steps in the following procedure.

Figure 7-12. Cut Confirmation Window

255-700-762R11.1 7-11


Chapter 7 Fault MonitoringSNMP Trap Log Capacity

Begin

1 Using the left mouse button, select the text that you want to delete from the Log page.

2 Click the right mouse button and a menu appears. Select Delete Selec-tion.


3 Click Yes to delete the selected text, or No to cancel.

If you clicked Yes, the selected text is removed from the Log page. If you clicked No, the selected text remains highlighted in the Log page.

End

SNMP Trap Log CapacityThe EMS-PSAX Log page can hold 500 lines of text at a time (approximately 100 events per session). If the trap log limit is exceeded, the EMS-PSAX sys-tem automatically discards the oldest traps first. For example, if 500 lines of trap messages appear in the Log tab, and another trap message appears, then the very first trap message in the Log tab will disappear. The HP OpenView NNM log can hold 3500 trap messages (one line per trap).

In order for the EMS-PSAX system to display traps and automatically update the Log tab for a specific PSAX system, that PSAX network element must be configured to send traps to the server on which the EMS-PSAX system resides.

MIB Objects Used for TrapsFor more information on traps and MIB objects, see the document, Packet-Star® PSAX Simple Network Management Protocol (SNMP) Trap Reference Guide, which describes the PSAX MIB objects. If the object has enumerated types, this document also provides the types of information the object presents, then the integer values, and their definitions are also described.

Trap ActivationThe Trap Activation feature is available in PSAX system software beginning with Release 5.1.0.

Figure 7-13. Delete Selection Confirmation Window

7-12 255-700-762R11.1


Chapter 7 Fault MonitoringTrap Activation

Perform the steps in the following procedure to enable traps.

Begin



2 Click the Trap Activation tab.

The Trap Activation page appears (see Figure 7-14).

Figure 7-14. Trap Activation Page

255-700-762R11.1 7-13


Chapter 7 Fault MonitoringTrap Activation

To find a specific trap by name, enter the string into the Trap Name field at the top of the page. As you type the letters, the entry that applies to the string will highlight automatically.

To filter the traps shown on this page by event type, select from the Show Traps From: pull-down menu at the top of the page (see Figure 7-15).

Table 7-3. Trap Activation Table Window Field Descriptions


Total: / (display only)

Default: 1/xxx where xxx represents the highest number of the last trap name in the table

Range: 1–255

Format: Numeric

Displays the number of the selected trap name and the total number of trap names in the table. The first number in this field identifies the num-ber of the trap name entry on the selected line of the currently displayed window. The second number indicates the total number of trap names in the table.

ID (display only)

Default: N/A

Range: 1–4

Format: Numeric

Displays the system-defined trap group ID:

• 1 = System

• 2 = Module

• 3 = Interface

• 4 = Connection

Ind (display only)

Default: N/A

Range: 1–126

Format: Numeric

Displays the system-defined trap index number within the trap group, for example, ConnectionEvent = 87, where 87 is the trap index number.

Trap Name (display only)

Default: N/A

Range: N/A

Format: Predefined

Displays the trap name.

Status Default: Activated

Range: N/A

Format: Predefined

Displays the current activation status of the trap name.

Activated Enables the display of the trap on the Trap Log Display window.

Deactivated Disables the display of the trap on the Trap Log Display window. When you select the line con-taining the trap name you want to deactivate and press Enter, Deactivated is displayed in this field.

Figure 7-15. Show Traps From Menu

7-14 255-700-762R11.1


Chapter 7 Fault MonitoringDisconnecting EMS-PSAX Clients On-Demand

3 To update the traps displayed on the page, click the right mouse button and select Refresh from the menu that appears (see Figure 7-16). You can select multiple traps and activate or deactivate them simultaneously.

To enable (Activate) or disable (Deactivate) traps, select the appropriate option from the right-click menu.

Note: You cannot activate or deactivate traps that display in the Status column as permanently activated.

End

Disconnecting EMS-PSAX Clients On-Demand

Administrators now have the ability to forcibly disconnect EMS-PSAX client sessions that may become corrupted. This feature frees server resources and reduces/prevents server data corruption.

To use this feature, perform the steps in the following procedure.

Begin

1 From the Main EMS-PSAX window, select View > Show Logged in Users.

The Users Logged On Server window appears (see Figure 7-17).

2 Select a client in the list, and right-click the entry.

3 Select Forced Client Shutdown in the menu that appears.

Figure 7-16. Trap Activation Page Menu

Figure 7-17. Users Logged On Server Window

255-700-762R11.1 7-15


Chapter 7 Fault MonitoringForcing the Unloading of EMS-PSAX Clients

4 A confirmation window appears (see Figure 7-18). Press Yes to discon-nect the client from the server. Press No to cancel.

You cannot disconnect the client session that you are working from. If you attempt to do so by mistake, an error message appears (see Figure 7-19).

End

Forcing the Unloading of EMS-PSAX Clients

Administrators now have the ability to forcefully unload devices regardless of whether they are preloaded open in any clients. This feature also frees server resources and clears corrupt device information for the affected clients.

To use this feature, perform the steps in the following procedure.

Begin

1 From the Main EMS-PSAX window, select View > Device List > SNMPv2cDeviceList.

The Device List window appears.

2 Select a device in the list and right-click the entry.

3 Select Unload Device > Force Unload from the menu that appears.

Figure 7-18. Client Shutdown Confirmation Window

Figure 7-19. Error - Cannot Terminate Client Window

7-16 255-700-762R11.1


Chapter 7 Fault MonitoringObtaining Module Hardware Information

A confirmation window appears (see Figure 7-20). Press Yes to unload the client from the server. Press No to cancel.

4 If you selected Yes, a final confirmation window appears (see Figure 7-21).

End

Obtaining Module Hardware Information

This section describes how to obtain hardware operating status data about a module. You can quickly obtain status information about ports, interfaces, and connection on the PSAX devices using the PSAX EMS. All of this informa-tion can be obtained from the Front Panel tab or the Device Tree.

Obtaining Hardware Operating Status Data

Data about the operating status of a module can be obtained from the Device Tree or from the Front Panel tab. The operating status of a module is reflected in the various colors displayed on the LED status indicators, the ports on the module in the Front Panel tab, and the modules and PSAX systems listed in the Device Tree. Alarms that display in the Front Panel tab and Device Tree clear automatically when the condition that created them is corrected.

Obtaining LED Status Indicator Data

The LED status indicators on the Front Panel tab (see Figure 7-22) directly reflect the status lights on the modules in the actual PSAX device. The color of the LEDs represent the current operational and alarm status values for that module, as described in Table 7-4.

Figure 7-20. Force Unload Confirmation Window

Figure 7-21. Force Unload Complete Window

255-700-762R11.1 7-17



Figure 7-22. Example of Module with LED Status Indicators

ACTIVE

UNSTRDS3/E3

CES

FAIL

TX

RX

TX

RX

TX

RX

1

2

3

LEDStatusIndicators

Table 7-4. LED Status Indicator Descriptions

Indicator LED Name on

Faceplate Description

Module Status Indi-cators

FAIL A red light at the top of a module indicates the com-plete failure of a module.

Possible causes include the following:

• Module was removed from chassis

• Module is improperly seated into the chassis

• Module is malfunctioning

• Module is not configured properly

ACTIVE A green light on the module indicates that the module is functioning properly.

Note: If both lights are displayed as gray in the Front Panel, the module is functioning properly but no ports, channels, or interfaces have been configured.

Line Signal Indicator LOS A yellow light indicates a loss of signal on that port.

7-18 255-700-762R11.1



Obtaining Port Configuration Data

The color of the ports on the Front Panel tab and of the modules in the Device Tree directly reflect whether the port is configured and if it is in or out of service. The current operational status of a PSAX device or any of the modules in the device also can be determined by looking at the color of the name of the PSAX device or module in the Device Tree. To obtain port status information about a specific module in a PSAX device, do one of the follow-ing:

• View the ports on the module in the Front Panel tab (see Figure 7-23)

• View at the status indicators in the Device Tree (see Figure 7-24)

Use the information in Table 7-5 to evaluate the color of a module’s ports.

Figure 7-23. Port Status Data

ACTIVE

UNSTRDS3/E3

CES

FAIL

TX

RX

TX

RX

TX

RX

1

2

3

A port changes colorto indicate its status.

255-700-762R11.1 7-19



Note: The actual color displayed for a port or interface corresponds to the color of the most severe state among the port state or interface state of all interfaces on that port. Therefore, a single interface with may change the port color to red, regardless of the port state and interface states of all other interfaces on the port.

Ghosted Modules

If a configured I/O or server module has failed or is removed from the PSAX chassis, a “ghosted” or light gray version of the module appears in the Front Panel tab.

Figure 7-24. Device Tree Status Indicators

Table 7-5. Port Status Data

Color Description

Dark Blue The port is unconfigured; no interface is applied to the port.

Light Blue The port is configured and out-of-service: an interface is applied to the port but it is neither administratively nor operationally in service.

Green The port is configured, operational, and in service.

Yellow The port is configured and administratively in service, but its operational status is unknown.

Red The port is configured and administratively in service, but it is operationally out of service. (Something other than an operator command has caused the port or interface to go out of service.)

PortIndicators

Module Indicator and Module Name

Operational Status

Name of PSAX Device

7-20 255-700-762R11.1


Chapter 7 Fault MonitoringPSAX Symbols on the HP OpenView NNM Submap

To correct this condition, you must do one of the following as described in Table 7-6.

PSAX Symbols on the HP OpenView NNM SubmapThe EMS-PSAX uses HP OpenView NNM’s default symbol status color scheme to reflect the status of PSAX devices on the HP OpenView NNM topology maps. With Release 11.1.0, the colors displayed in the EMS-PSAX GUI match the colors of traps from the HP OpenView NNM Event Viewer and wherever possible within HP OpenView NNM. PSAX-specific symbols are automatically used when PSAX nodes are added to the HP OpenView NNM submap.

Operational Status and Colors of Symbols

These symbol colors reflect operational status, which is derived from HP OpenView NNM’s regular status polling of managed devices.

Note: The status colors that are displayed on the EMS-PSAX Front Panel view and the Device Tree do not propagate up to the symbol on the HP OpenView NNM map.

This operational status may indicate a problem with the underlying device object.

Note: Within HP OpenView NNM, these underlying devices include any component the IP map considers as a network element, that is, anything that has an IP address. Thus, when a user selects a PSAX symbol, HP OpenView NNM displays the switch IP address and in-band management IP address of the PSAX device as underlying device objects which can influence status color.

Operational status is propagated according to the propagation scheme of the map. The operational status colors and conditions are as follows:

• Unknown (dark blue)—status of the underlying object (or child symbols) is unconfigured

• Normal/Up (green)—status of the underlying object (or all child symbols) is normal

• Warning (light blue)—status of all child symbols, except one, is normal

Table 7-6. Removing Ghosted Modules from the Front Panel

If a module... and you want to... then do this ...

has failed • retain all configurations on this module

• restore service

remove the failed module and insert an identical module.

has been removed in error

reinsert the original module into the chassis.

is being replaced with a dissimilar module

remove the ghosted module from the Front Panel

delete all interfaces to unconfigure the module (afterward you may insert and configure another module).

255-700-762R11.1 7-21


Chapter 7 Fault MonitoringEMS-PSAX Active Alarm Table

• Minor/Marginal (yellow)—status of multiple child symbols is normal, and status of multiple child symbols is not normal; the value in the LineStatus field of any port on a module within the PSAX device is not NoAlarm.

• Major (orange)—status of only one child symbol is normal, the rest are not normal; the operational status of any module within the PSAX device is not Primary, except for unconfigured and backup/protection modules.

• Critical/Down (red)—status of the underlying object (or all child symbols) is not normal; the PSAX device is unreachable either using the Ping com-mand or using SNMP

• Unmanaged (grey)

• Testing

• Restricted

• Disabled

CPU Status Symbol Colors

For each PSAX device in the HP OpenView NNM submap, the CPU Status symbol color is green (Normal) by default when no problems exist within the PSAX device. The CPU Status symbol color is updated upon a change in sta-tus as described in Table 7-7.

EMS-PSAX Active Alarm Table

Overview of the EMS-PSAX Active Alarm Table

The Active Alarm Table displays the list of alarms that are generated in the PSAX system. This table also provides the status and severity of the alarms.

Table 7-7. CPU Status Symbol Characteristics

When this condition exists... the CPU Status symbol color will change to...

the PSAX device is unreachable via SNMP

red (Critical)

a module-level problem orange (Major)

a port-level problem yellow (Minor)

7-22 255-700-762R11.1



Note: To view the list of alarms that are generated in the PSAX system, you should enable the Active Alarm Table field in the site specific window (see Figure 3-56).

Figure 7-25. Active Alarm Table

Table 7-8. Active Alarm Status Table Window Field Descriptions


Index Default: displayed indice

Range: 000–199

Format: Numeric

Indicates a system generated index number for the indicated alarm. The index is a unique identifier which allows the EMS to correlate data from multiple queries.

Alarm Name Default: displayed alarm

Range: N/A

Format: Predefined

Indicates active alarm names generated by the PSAX system. The alarms are described in Table 7-9

Start Time Default: displayed date and time

Range: N/A

Format: Numeric

Indicates the time the alarm was first generated by the sys-tem or last updated in date and time.

255-700-762R11.1 7-23



The alarms displayed in the Active Alarm Status Table window are described in Table 7-9.

Current Sever-ity

Default: displayed severity

Range: N/A

Format: Predefined

Indicates the severity (minor, major, or critical) of the alarm.

Status Default: displayed status

Range: N/A

Format: Predefined

Indicates the status of the alarm.

SS-PP-CCC Default: displayed SS-PC-CCC

Range: N/A

Format: Numeric

Indicates the source of the alarm in slot, port, and channel (SS PP CCC) format except for virtual UNI alarms (SS PP CCC VUNIId) and Gigabit Ethernet domain alarms (SS PP domain#).

Table 7-8. Active Alarm Status Table Window Field Descriptions (Continued)


Table 7-9. Active Alarm Status Table Window Alarms

Alarm Severity Description

ReferenceClock Critical Indicates that the backplane reference clock has failed or has been corrected as detected by the Stratum 3–4 module/component. If the clock fails, call Technical Support immediately to resolve the problem.

CompositeClock Critical Indicates that an error in the composite clock has been corrected or the composite clock has failed on the Stra-tum 3–4 module of the PSAX 1250, PSAX 2300, or PSAX 4500 chassis, or the Stratum 3–4 component of the PSAX 1000 Stratum 3–4/Power Supply modules. Call Technical Support immediately to resolve the prob-lem. If the composite clock fails, call Technical Support immediately to resolve the problem.

CompleteClock Critical Indicates that a clock source is now available or has failed on the Stratum 3–4 module of the PSAX 1250, PSAX 2300, or PSAX 4500 chassis, or the Stratum 3–4 component of the PSAX 1000 Stratum 3–4/Power Sup-ply modules.

InputPortClock Critical Indicates that the input port clock has been corrected or has failed. If the clock fails, call Technical Support immediately to resolve the problem.

PowerSupplyStatus Major Indicates the status of the indicated power supply mod-ule.

BackplaneCircuitry Critical Indicates that there is a change in the activity on the cell bus. If the cell bus fails, call Technical Support immedi-ately to resolve the problem.

7-24 255-700-762R11.1



Interface Critical Indicates that an interface has undergone a reduction in bandwidth, has been created, deleted, modified, failed, placed into service, taken out of service, or an attempt to modify it has failed.

IsdnLapd Major Indicates that the LAPD on the ISDN interface has gone down or come up.

PnniPortLnk Critical and Major

Indicates that the protocol status of the PNNI link is up but not advertising, the link is down, or the link is up and advertising.

AtmSvcIntfLayer2 Major Indicates that an ATM SVC Interface Assured Data Link is up or down.

VirtualUNIIntf Major Indicates that a virtual UNI has been created, an attempt to create a virtual UNI has failed, deleted, now in ser-vice, modified, an attempt to modify a virtual UNI has failed, or now out of service.

Gr303Ig Major Indicates that an attempt to create a GR-303 interface group has failed or adding an interface has failed.

Gr303TMCChan Major Indicates whether a TMC (LAPD) on the GR-303 inter-face has gone down or come up.

Gr303EOCChan Major Indicates whether an EOC (LAPD) on the GR-303 inter-face has gone down or come up.

V5InterfaceAdmin Major Indicates whether the V5 interface administrative status is coming into service or going out of service.

V5InterfaceVariant Major Indicates the addition of a variant in the V5 interface, an attempt to add a variant has failed, successful deletion of a variant from the V5 interface, variant is in service, a failure of modifying one of the parameters in the V5 interface variant, variant is out of service, failure of the variant switchover command initiated either by AN or LE, successfully executing the variant switchover com-mand initiated either by AN or LE.

V5InterfaceVariantSwitchover Major Indicates whether the variant switchover in the V5 interface succeeded or failed.

V5InterfaceProtectionSwitchover Major Indicates whether the V5 interface protection switcho-ver has occurred or failed.

V5InterfaceOper Major Indicates whether the V5 interface operational status is coming into service or going out of service.

V5InterfaceUserPort Major Indicates whether the V5 interface port is being blocked or unblocked.

V5LesInterface Major Indicates whether the V5 LES interface operational sta-tus is coming into service or going out of service.

V5E1LinkOperInServiceNotify Major Indicates whether the V5 E1 link operational status is coming into service or going out of service.

Table 7-9. Active Alarm Status Table Window Alarms (Continued)


255-700-762R11.1 7-25



Active Alarm Table Menu Options

The right-click menu options are described in Table 7-10.

Setting filters for the Active Alarm Table

To set filters for the Active Alarm Table, perform the steps in the following procedures.

Begin

1 From the Active Alarm Table window, right-click the mouse and select Filters (see Figure 7-25).

VpcPnniIntf Major Indicates that a VPC PNNI has been created, an attempt to create a VPC PNNI has failed, deleted, now in service, modified, an attempt to modify a VPC PNNI has failed, or now out of service.

GigeDomain Major Indicates that a Gigabit Ethernet domain has been cre-ated, deleted, modified, placed in service, taken out of service, updated, or a modification has failed.

Card Major Indicates that the module in an assigned slot has been inserted, removed, and/or it has failed.

LineStatus Critical, Major and Minor

The indicated port has had a change in the line status.

Table 7-9. Active Alarm Status Table Window Alarms (Continued)


Table 7-10. Menu Options for the Active Alarm Table


Refresh Allows you to refresh the Active Alarm Table

Filter Allows you to set filters for the Active Alarms

7-26 255-700-762R11.1



Set Filters window appears (see Table 7-26).


2 Set the values for the fields in the Set Filters window (see Figure 7-26 ) as described in Table 7-11.

3 Click Apply button.

Figure 7-26. Set Filters Window

Button Function

Apply Applies the values set for the fields on this window.


Reset Sets the values back to their previous state.

Table 7-11. Set Filters Window Field Descriptions


Severity Default: User defined

Range: N/A

Format: Predefined

Indicates the severity (major or critical) of the alarm.

Start Date Default: User defined

Range: N/A

Format: Predefined

Indicates the start date of the filters set.

Start Time Default: User defined

Range: N/A

Format: Predefined

Indicates the start time of the filters set.

255-700-762R11.1 7-27



End Date Default: User defined

Range: N/A

Format: Predefined

Indicates the end date of the filters set.

End Time Default: User defined

Range: N/A

Format: Predefined

Indicates the end time of the filters set.

Slot Default: N/A

Range: N/A

Format: Numeric

Indicates the PSAX chassis slot that the selected module occupies.

Port / VPN ID Default: N/A

Range: N/A

Format: Predefined

Indicates the ports selected. Each port offers different set of virtual channels.

Channel Default: N/A

Range: N/A

Format: Predefined

Indicates the channel selected.

Interface Default: N/A

Range: N/A

Format: Predefined

Specifies which end-to-end interface protocol the connec-tion will operate under.

OperStatus Default: N/A

Range: N/A

Format: Predefined

Specifies whether the interface is operational or not.

AdminStatus Default: N/A

Range: N/A

Format: Predefined

Specifies the administrative status of the interface. For example, in service, configured, and so on.

Table 7-11. Set Filters Window Field Descriptions (Continued)


7-28 255-700-762R11.1


8 Configuring ATM Routing DataUsing PNNI

Overview of This ChapterThis chapter describes how to view and configure routing data on PSAX devices using private network-network interface (PNNI) entities within the EMS-PSAX, in order to use PNNI routing in a PNNI network, as follows:

• Nodes

• Route addresses

• Metrics

• Summary addresses

• Map links

• Map nodes

• Map addresses

• Links

• Switched virtual channel connection (SVCC) routing control connection (RCC) information

• Neighbor peers

• Neighbor peer ports

• PNNI topology state elements (PTSEs)

• Statistics

Configuring PNNITo begin PNNI Configuration, click the PNNI tab, and the PNNI Node Config-uration Table page appears. Right-click within the PNNI tab, and a menu appears (see Figure 8-1).


255-700-762R11.1 8-1

Chapter 8 Configuring ATM Routing Data Using PNNIConfiguring PNNI

Menu Options The PNNI Node Configuration Table displays all of the nodes configured in the PNNI Routing tables. Options can be obtained by clicking the right mouse button within the PNNI Node Configuration Table to display a menu (see Table 8-1). Each of the tables accessed from this PNNI right-click menu also have right-click menu options.

Figure 8-1. PNNI Node Configuration Table Page (Displaying Menu)

Table 8-1. PNNI Page Menu Options

Menu Option Description

Display Opens a View PNNI Node Entry window for the selected PNNI Node

Create PNNI Node Entry Opens an Add PNNI Node Entry window, which can be used to create a PNNI Node. This window also includes buttons that open the PNNI Node PGL Configuration window (see Figure 8-3), PNNI Node Timer Configuration window (see Figure 8-4), PNNI Node SVCC Configuration window (see Figure 8-5), and PNNI Scope Mapping Configura-tion window (see Figure 8-6).

Update Opens an Update PNNI Node Entry window, which can be used to update an existing PNNI Node. This option is available only if the node is operationally out of service.

Delete Deletes the selected PNNI node. This option is avail-able only if the node is operationally out of service.

8-2 255-700-762R11.1



Refresh Updates the data in the PNNI Node Configuration Table.

Bring Into Service Brings the selected entries in the PNNI tab into ser-vice.

Take Out of Service Takes the selected entries in the PNNI tab out of ser-vice.

Route Address Configuration Opens the PNNI Route Address Configuration Table window, which contains the route address Configura-tion for the nodes (see Figure 8-7).

Route TNS Configuration Opens the PNNI Route TNS Table (see Figure 8-14).

Summary Address Configura-tion

Opens the PNNI Summary Address Table window, which contains IP addresses for all nodes to which the link table is attached by PNNI interfaces (see Figure 8-16).

Map Information Opens the PNNI Map Link Table window, which shows the mapping for the nodes and their links, and all original port and remote port PTSE identifiers and the metrics tag numbers (see Figure 8-18).

Map Node Information Opens the PNNI Map Node Table window, which con-tains a list of nodes as seen from the perspective of a local node, and all information learned by the local node from nodal information PTSEs (see Figure 8-20).

Map Address Information Opens the PNNI Map Address Table window, which contains a list of all reachable addresses from each node visible to the local node (see Figure 8-22).

Map TNS Information Opens the PNNI Map TNS Table (see Figure 8-24).

Link Information Opens the PNNI Link Table window, which contains an index of nodes and their associated links for this PSAX device (see Figure 8-25).

SVCC RCC Information Opens the PNNI SvccRcc Table window (see Figure 8-24).

Neighbor Peer Information Opens the PNNI Neighbor Peer Table window, which contains nodes that are on the same level as this node (see Figure 8-27).

Neighbor Peer Port Informa-tion

Opens the PNNI Neighbor Peer Port Table window, which displays all ports in hello state two-way inside to a given neighboring peer node, for lowest-level nodes (see Figure 8-29).

PTSE Information Opens the PNNI PTSE Table window, which describes the most recent instances of PTSEs in a node's topol-ogy database (see Figure 8-31).

PNNI Statistics Opens the PNNI Statistics window, which displays the PSAX system-wide statistics for PNNI (see Figure 8-33).

Table 8-1. PNNI Page Menu Options

Menu Option Description

255-700-762R11.1 8-3



Adding PNNI Routing Data

Since the PNNI interface is configured during this procedure, be sure that the ATM PNNI 1.0 interface has not been previously configured.

Note: You must follow the procedures in this section so that later, you can configure an I/O module with the ATM PNNI 1.0 interface type.

To create a node, that is, a point of connection into the PNNI network, per-form the steps in the following procedure to add PNNI data.

Begin

1 In the Device window click the PNNI tab.

The PNNI Node Configuration Table page appears (see Figure 8-1).

2 In the PNNI Node Configuration Table, click the right mouse button and a menu appears. Select Create.

The ADD PNNI Node Entry window appears (see Figure 8-2).

3 Create a node entry by adding the data as shown in the table below. Example:

Node Index = 1

ATM Address = 4701.1111.0000.0000.0000.0000.0000.0000.0000.0000

4 Enter values for the fields in this window according to the information provided in Table 8-2.

5 In the ADD PNNI Node Entry window, click Add.

The node entry appears in the PNNI Node Configuration Table.

6 Click Bring Into Service > Close.

7 Click the Front Panel tab.

8 Using the instructions in the appropriate Navis® EMS-PSAX Modules Con-figuration Guide, configure a port with the ATM PNNI interface, and bring the interface into service.


End

8-4 255-700-762R11.1




Figure 8-2. PNNI Node Entry Window

Button Function

Bring Into Service Brings this node entry into service. Changes button to Take Out of Service on the VIEW PNNI Node Entry window. This button is displayed on the Node Sta-tus panel.

Take Out of Service Takes this node entry out of service. This button is displayed on the Node Status panel of the VIEW PNNI Node Entry win-dow.

Pnni Node Pgl Table Displays the Pnni Node Pgl Configuration window.

Pnni Node Timer Table Displays the Pnni Node Timer Configura-tion window.

Pnni Node Svcc Table Displays the Pnni Node Svcc Configura-tion window.

Pnni Scope Mapping Table

Displays the Pnni Scope Mapping Config-uration window.

ATM Security Config - Routing SVCC

Displays the PNNI SVCC RCC Security Configuration window.

Add Adds this PNNI node entry. This button is displayed on the ADD PNNI Node Entry window.

255-700-762R11.1 8-5



Delete Deletes this PNNI node entry. This button is displayed on the VIEW PNNI Node Entry window.

Update Refreshes the statistics manually.

This button appears after you add the new node, and before you bring it into service. As long as the node is in service, you do not have an Update option on right-click menu. If you take the node out of service, the Update option appears on the right mouse menu.

Reset Changes all fields to the last applied val-ues.


Button Function

Table 8-2. PNNI Node Entry Window Field Descriptions


Node Index Default: 0

Range: 1–400

Format: Numeric

Displays the identity of a logical PNNI entity in the PSAX system. Enter the index number of each node in this field.

Node ID (Hex) Default: 0

Range: N/A

Format: Hexadecimal

Indicates the system generates your Node Id automatically. For more information, see Section 5.3.3, Node Identifiers, in the ATM Forum Specification, Private Network-Network Interface Specification Version 1.0 (PNNI 1.0), af-pnni-0055.000.

ATM Address (Hex) Default: 0

Range: N/A

Format: Hexadecimal

Enter your ATM NSAP address, a hexadecimal number within the network’s PNNI hierarchy that must begin with 39, 45, or 47, depending on your world region.

Peer Group ID (Hex)

Default: 0

Range: N/A

Format: Hexadecimal

Indicates the first 12 bytes (default) of the ATM address. This value is the combination of the ATM address and the node level. The first byte indi-cates the node level. The following bytes come from the ATM address where the number of bytes depend on the node level. For example, a node level of 96 bits (default) determines the next 12 bytes (96 bits) from the ATM address.

This value is generated and displayed by the sys-tem automatically. For more information, see Section 5.3.3, Node Identifiers, in the ATM Forum Specification, Private Network-Network Interface (PNNI 1.0) Specification Version 1.0, af-pnni-0055.000.

8-6 255-700-762R11.1



Domain Name Default: N/A

Range: N/A


Indicates the routing domain in which this node participates.

Node Level Default: 96

Range: 96 (deci-mal)=60 (hexadeci-mal); 1–104

Range: Hexadecimal

Indicates the level of PNNI hierarchy at which this node exists. Indicates the number of signifi-cant bits in the network portion of the ATM address on the PSAX system. This number is related to the first octet (two digits) of the node identifier. All PSAX systems within the same peer group should be in the same node level.

Enter in hexadecimal form and the system will generate and display the value automatically.

Node Lowest Default: True

Range: N/A

Format: Predefined

Indicates whether or not this node is the root node.

True The current node is the root.

False The current node is not the root.

Restricted Transit Default: False

Range: N/A

Format: Predefined

Indicates whether the node is restricted to not allowing support of SVCs transmitting from this node.

False Indicates SVC transmission from the node is allowed, or not restricted.

True Indicates SVC transmission from the node is not allowed, or restricted.

Complex Node Default: False

Range: N/A

Format: Predefined

Specifies whether this node uses the complex node representation. This attribute determines the setting of the nodal representation bit in the nodal information group originated by this node.

False Indicates that simple node representation is used.

True Indicates that the complex node representation is used.

Restricted Branch-ing(display only)

Default: False

Range: N/A

Format: Predefined

Indicates whether the node is able to support additional point-to-multipoint branches. This attribute reflects the setting of the restricted branching bit in the nodal information group originated by this node.

False Indicates that additional branches can be sup-ported.

True Indicates that additional branches cannot be sup-ported.

Table 8-2. PNNI Node Entry Window Field Descriptions (Continued)


255-700-762R11.1 8-7



Viewing PNNI Node PGL Information

Perform the steps in the following procedure, to view Node PGL information.

Begin

1 From the PNNI Node Configuration Table, select a node and click the right mouse button. Select Display.

The VIEW PNNI Node Entry window appears.

2 Click PNNI Node PGL Table.

The PNNI Node PGL Configuration window appears (see Figure 8-3).


Database Overload(display only)

Default: True

Range: N/A

Format: Predefined

Displays whether Database Overload is selected, which specifies whether the node is currently operating in a topology database overload state. This attribute has the same value as the nontran-sit for PGL election bit in the nodal information group originated by this node.

True Indicates the node is currently operating in a topology database overload state.

False Indicates the node is not currently operating in a topology database overload state.

Number of PTSEs(display only)

Default: 0

Range: N/A

Format: Numeric

Displays the total number of PTSEs currently in the topology database(s) for this node.


Default: N/A

Range: N/A

Format: Predefined

Displays the administrative status for this node.

Up The node is currently active.

Down The node is not currently active.

Operational Status(display only)

Default: N/A

Range: N/A

Format: Predefined

Displays the operational status for this node.

Up The node is currently active.

Down The node is not currently active.

Table 8-2. PNNI Node Entry Window Field Descriptions (Continued)


8-8 255-700-762R11.1




End


Figure 8-3. PNNI Node PGL Configuration Window

Button Function


Refresh Updates the read-only fields on this win-dow.


Table 8-3. PNNI Node PGL Configuration Window Field Descriptions


Node PGL Information Upper Panel

Node Index(display only)

Default: 0

Range: 1–400

Format: Numeric

Displays the identifier of a logical PNNI entity in the PSAX system.

Leadership Prior-ity

Default: 000

Range: 0–205

Format: Numeric

Indicates the user-assigned ranking of a logical node. Usually the node with the highest ranking in a peer group will be elected peer group leader (PGL).

Cfg Parent Node Index

Default: 00000

Range: 1–65535

Format: Numeric

Indicates a parent node is the logical group node that represents the contained peer group of a child node(s) at the next lower level of the hierarchy.

Initiation Time Default: 00015

Range: 0–15


Indicates the initiating time of the PGL election pro-cess. When this timer fires, the election begins after the time set by the user.

255-700-762R11.1 8-9



Override Delay Default: 00030

Range: 0–30


Indicates the amount of time the node should wait for all nodes to agree on which node should be elected PGL.

Reelect Time Default: 00015

Range: 0–15


Indicates the time interval the node should wait before restarting the PGL election process, after it discovers it has no connectivity to the current PGL.

State(display only)

Default: OperPgl

Range: N/A

Format: Predefined

Displays the status of this node PGL.

OperPgl Displays that the status of this node is the PGL. It con-tinues examining PTSEs sent by other nodes to see if another node has a higher priority than itself.

Starting Displays that this node is in the initial state of the state machine.

Awaiting Displays that this node has started the Hello Finite State Machine (FSM) on at least one link, and that no peer group has yet been found.

AwaitingFull Indicates that at least one neighboring peer has been found, but no database synchronization process has been completed.

InitialDelay Indicates that the database synchronization process has been completed with at least one neighboring peer, and the PGL initiation timer has started. The node must wait before for the period of time specified in the Initiation Time field before it can select and advertise its preferred PGL.

Calculating Indicates that the node is in the process of calculating its new choice for the preferred PGL.

AwaitUnanimity Indicates that the node has chosen itself as the PGL. The node will check whether all other nodes elect this node to be the PGL unanimously.

OperNotPgl Indicates that this node is not the PGL. It examines PTSEs sent by other nodes to determine whether another node has a higher priority than itself.

HungElection Indicates that the node has chosen itself as the PGL, but not all other nodes will advertise it as their pre-ferred PGL.

AwaitReElection Indicates that the node has lost connectivity to the current PGL. If the connectivity has not been reestab-lished before the period of time specified in the Reelect Time field, the election process is restarted.

Table 8-3. PNNI Node PGL Configuration Window Field Descriptions (Continued)


8-10 255-700-762R11.1



Viewing PNNI Node Timer Information

Perform the steps in the following procedure, to view PNNI Node Timer information.

Begin



2 Click PNNI Node Timer Table.

The PNNI Node Timer Configuration window appears (see Figure 8-4).



End

Preferred PGL(display only)

Default: 0

Range: N/A

Format: Hexadeci-mal address (up to 11 octets)

Displays the preferred PGL. To select, any node com-pares the leadership priorities and node IDs advertised in the PTSEs in the topology database, and determines which nodes reachable from itself.

Peer Group Leader(display only)

Default: 0

Range: N/A

Range: Hexadeci-mal address (up to 11 octets)

Displays a node of a peer group that does the extra work of collecting, aggregating, and building data that is used to represent the entire peer group as a single node. This information is available in the parent node.

Time Stamp(display only)

Default: 00:00:00

Range: N/A

Format: hh:mm:ss (hour, minute,sec-ond)

Displays the recorded completion time of a successful PGL election. If the PGL election is unsuccessful, the timer will display with the default value.

Table 8-3. PNNI Node PGL Configuration Window Field Descriptions (Continued)


255-700-762R11.1 8-11




Figure 8-4. PNNI Node Timer Configuration

Button Function




8-12 255-700-762R11.1



Table 8-4. PNNI Node Timer Configuration Window Field Descriptions



Default: 0

Range: 1–400

Format: Numeric

Displays the node index that identifies a logical PNNI entity in the PSAX system.

PTSE Holddown (100 msec)

Default: 10

Range: 1–65535

Format: Numeric multiplier of 100 msec

Indicates a PNNI Topology State Element (PTSE), a collection of PNNI information that is flooded among all logical nodes in a peer group. The hold-down timer prevents a node from sending hello packets at unacceptably high rates. The initial value of this timer is used by a node to limit the rate at which it can re-originate PTSEs.

Note: Each increment entered in this field is a multiplier of 100 msec. A value of 10 = 1 second, or 100 msec × 10.

Hello Holddown(100msec)

Default: 10

Range: 0–65535


Indicates the initial value for the Hello Hold-down timer, which is used by a node to limit the rate at which it sends Hellos.


Hello Inter-val(sec)

Default: 15

Range: 0–65535


Indicates the initial value for the Hello timer. In the absence of triggered Hellos, this node will send one Hello packet on each of its ports at this interval.

Hello Inactivity Factor

Default: 5

Range: 0–65535

Format: Numeric

Indicates the value this node will use to determine when a neighbor has failed.

Hlink Inact(sec) Default: 120

Range: 0–65535


Indicates the horizontal link inactivity time (horizontal links are between nodes in the same peer group at the same level). The length of time a node will continue to advertise a hori-zontal link for which it has not received and processed the logical group node (LGN) horizontal link information group (IG).

PTSE Refresh Interval(sec)

Default: 1800

Range: 0–65535


Indicates the time between re-originations of a self-originated PTSE in the absence of triggered updates. A node will reorigi-nate its PTSEs at this rate in order to prevent flushing of its PTSEs by other nodes.

PTSE Lifetime Factor

Default: 200

Range: 101–1000

Format: Numeric (percentage)

Indicates the formula which calculates this product: PTSE Refresh Interval × PTSE Lifetime Factor = PTSE Lifetime of self-originated PTSEs.

Rxmt Inter-val(sec)

Default: 5

Range: 0–65535


Specifies the retransmit interval, which is the period between retransmissions of unacknowledged database summary pack-ets, PTSE request packets, and PNNI Topology State Packets (PTSPs).

255-700-762R11.1 8-13



Viewing PNNI Node SVCC Information

Perform the steps in the following procedure, to view PNNI Node SVCC information.

Begin



2 Click PNNI Node SVCC Table.

Peer Delayed Ack Interval. (100 msec)

Default: 10

Range: 0–65535


Specifies the peer-delayed acknowledgement interval, which is the minimum number of milliseconds between transmis-sions of delayed PTSE acknowledgement packets.


AVCR Propor-tional Multiplier

Default: 50

Range: 1–99


Indicates the available cell rate (AVCR) proportional multi-plier (PM), which is used in an algorithm that determines sig-nificant change for average cell rate parameters.

AVCR Mini-mum Threshold

Default: 3

Range: 1–99


Indicates the available cell rate (AVCR) minimum threshold (MT), which is used in the algorithm that determines signifi-cant change for average cell rate parameters.

CDV Propor-tional Multiplier

Default: 25

Range: 1–99


Indicates the cell delay variance proportional multiplier, which is used in the algorithm that determines significant change for CDV metrics.

CTD Propor-tional Multiplier

Default: 50

Range: 1–99


Indicates the cell transfer delay proportional multiplier, which is used in the algorithm that determines significant change for CTD metrics. The multiplier is the percentage of the last advertised maximum CTD such that a change within the range maxCTD ± (maxCTD × maxCTD_PM ÷ 100) is not considered significant.

Table 8-4. PNNI Node Timer Configuration Window Field Descriptions (Continued)


8-14 255-700-762R11.1



The PNNI Node SVCC Configuration window appears (see Figure 8-5).




End

Figure 8-5. PNNI Node SVCC Configuration Window

Button Function




Table 8-5. PNNI Node SVCC Configuration Window Field Descriptions



Default: 00000

Range: 1–400

Format: Numeric


Init Time Default: 00004

Range: 0–65535


Indicates the initiating time, the amount of time this node will delay initiating establishment of an SVCC to a neighbor with a numerically lower ATM address, after determining that such an SVCC should be established.

Retry Time Default: 00030

Range: 0–65535


Indicates the number of times that this node will wait before attempting to re-establish a SVCC-based routing control channel (RCC).

255-700-762R11.1 8-15



Viewing PNNI Scope Mapping Information

Perform the steps in the following procedure, to view PNNI Scope Mapping information.

Begin



2 Click PNNI Scope Mapping Table.

Calling Integrity Time

Default: 00035

Range: 0–65535


Indicates the calling integrity time, which is the amount of time this node will wait for an SVCC that it has initiated establishment of as the calling party, to become fully established, before giving up and tearing the SVCC down.

Called Integrity Time

Default: 00050

Range: 0–65535


Indicates the called integrity time, which is the amount of time that this node should wait for an SVCC that it has decided to accept as the calling party, to become fully established, before giving up and tearing the SVCC down.

Traffic Descriptor Index

Default: 00000

Range: 1–65535

Format: Numeric

Indicates the traffic descriptor index to the ATM Traffic Descriptor Parameter Table, as defined in RFC 1695. This traffic descriptor is used when establishing SVCs for use as SVCC-based RCCs to or from PNNI logical group nodes.

Table 8-5. PNNI Node SVCC Configuration Window Field Descriptions (Continued)


8-16 255-700-762R11.1



The PNNI Scope Mapping Configuration window appears (see Figure 8-6).



End


Figure 8-6. PNNI Scope Mapping Configuration

Button Function

Refresh Updates the fields on this window.


255-700-762R11.1 8-17



Table 8-6. PNNI Scope Mapping Configuration Window Field Descriptions



Default: 0

Range: 1–400

Format: Numeric

Indicates the identifier of a logical PNNI entity in the PSAX system.

[Local Network] Default: 096

Range: 0–104

Format: Numeric

Indicates the highest level of PNNI hierarchy (or the smallest PNNI routing level) that lies within the Local Network organizational scope.

[Local Network Plus One]

Default: 096

Range: 0–104

Format: Numeric

Indicates the highest level of PNNI hierarchy (or the smallest PNNI routing level) that lies within the Local Network Plus One organizational scope.

[Local Network Plus Two]

Default: 96

Range: 0–104

Format: Numeric

Indicates the highest level of PNNI hierarchy (or the smallest PNNI routing level) that lies within the Local Network Plus Two organizational scope.

[Site Minus One] Default: 080

Range: 0–104

Format: Numeric

Indicates the highest level of PNNI hierarchy (or the smallest PNNI routing level) that lies within the Site Minus One organizational scope.

[Intra Site] Default: 080

Range: 0–104

Format: Numeric

Indicates the highest level of PNNI hierarchy (or the smallest PNNI routing level) that lies within the Intra Site organizational scope.

[Site Plus One] Default: 072

Range: 0–104

Format: Numeric

Indicates the highest level of PNNI hierarchy (or the smallest PNNI routing level) that lies within the Site Plus One organizational scope.

[Organization Minus One]

Default: 072

Range: 0–104

Format: Numeric

Indicates the highest level of PNNI hierarchy (or the smallest PNNI routing level) that lies within the Organization Minus One organizational scope.

[Intra Organization]

Default: 064

Range: 0–104

Format: Numeric

Indicates the highest level of PNNI hierarchy (or the smallest PNNI routing level) that lies within the Intra Organization organizational scope.

[Organization Plus One]

Default: 064

Range: 0–104

Format: Numeric

Indicates the highest level of PNNI hierarchy (or the smallest PNNI routing level) that lies within the Organization Plus One organizational scope.

[Community Minus One]

Default: 064

Range: 0–104

Format: Numeric

Indicates the highest level of PNNI hierarchy (or the smallest PNNI routing level) that lies within the Community Minus One organizational scope.

[Intra Community] Default: 048

Range: 0–104

Format: Numeric

Indicates the highest level of PNNI hierarchy (or the smallest PNNI routing level) that lies within the Intra Community organizational scope.

[Community Plus One]

Default: 048

Range: 0–104

Format: Numeric

Indicates the highest level of PNNI hierarchy (or the smallest PNNI routing level) that lies within the Community Plus One organizational scope.

8-18 255-700-762R11.1



Configuring Route Addresses and Metrics

To configure PNNI route addresses, perform the steps in the following proce-dure.

Configuring Route Addresses

Begin

1 On the PNNI tab, select Route Address Configuration from the right-click menu, and the PNNI Route Address Configuration Table window appears (see Figure 8-7).


[Regional] Default: 032

Range: 0–104

Format: Numeric

Indicates the highest level of PNNI hierarchy (or the smallest PNNI routing level) that lies within the Regional organizational scope.

[Inter Regional] Default: 032

Range: 0–104

Format: Numeric

Indicates the highest level of PNNI hierarchy (or the smallest PNNI routing level) that lies within the Inter Regional organizational scope.

[Global] Default: 000

Range: 0–104

Format: Numeric

Indicates the highest level of PNNI hierarchy (or the smallest PNNI routing level) that lies within the Global organizational scope.

Table 8-6. PNNI Scope Mapping Configuration Window Field Descriptions (Continued)


Figure 8-7. PNNI Route Address Table Window

Button Function


Reset Removes text entered in the Show table entry containing: field and de-selects any selected entries.


255-700-762R11.1 8-19



2 Click the right mouse button within this window and a menu appears. Select Create.

The ADD PNNI Route Address Entry window appears (see Figure 8-8).


Figure 8-8. ADD PNNI Route Address Entry Window

Button Function

Add Adds the route address Configuration values you enter into the PNNI Route Address Configuration Entry window as a route address entry in the PNNI Route Address Table window. This button is displayed on the ADD PNNI Route Address Configura-tion Entry window.

Delete Deletes this PNNI route address entry. This button is displayed on the VIEW PNNI Route Address Configuration Entry window.


Metrics Table

Opens the Metrics Table window (see Figure 8-11).

8-20 255-700-762R11.1




Table 8-7. PNNI Route Address Entry Window Field Descriptions


PNNI Route Address Identification Panel

Node Index Default:

Range: 1–400

Format: Numeric

Displays the identifier of a logical PNNI entity in the PSAX system. Enter the same value as assigned to the PNNI node. In the UPDATE window, this field is display-only and cannot be modified unless you delete this route.

Route Address Prefix (Hex)

Default: N/A

Range: N/A


Indicates the address prefix of the ATM end system, in 19 bytes (it does not include the NSAP address selector byte). In the UPDATE window, this field is display-only and cannot be modified unless you delete this route.

Advertising Node ID (Hex)

Default: N/A

Range: N/A


Indicates the node ID of the node advertising connectivity to the specified prefix. If the local node ID is 0, then this must be zeroes. This value is generated and displayed by the PSAX system automatically. A maximum of 50 PNNI routes can be advertised. In the UPDATE window, this field is display-only and cannot be modified unless you delete this route.

Interface Index Default: 0000000

Range: 0–2147483647

Format: Numeric

Indicates the local interface over which the advertised node is reachable. If the node is only reachable through a remote node, this must be set to 0. If the node is not set to zero, the address protocol (Address Proto field) must not be PNNI, and the Address Type field should not be set to Reject.

Advertised Port ID

Default: 0000000000

Range: N/A

Format: Numeric

Specifies the advertised port identifier, used for call routing purposes:

• For an SVC endpoint, set this field to 0 or enter the slot, port, and channel number of the interface to which you want the call forwarded.

• For an SPVC endpoint, set this field to 0, then the PSAX routing functionality will decide whether to route the call out of the PSAX on an available PNNI interface, or to ter-minate the call on the PSAX itself (in the case of SPVCs).

Prefix Length Default: 000

Range: 0–152

Format: Numeric

Enter a value that does not exceed 152 (19 octets = 152 bits). For an SPVC, enter the length of the Address Prefix which is accessible through this PNNI node for SPVC (1–152 bits). In the UPDATE window, this field is display-only and cannot be modified unless you delete this route.

Address Index Default: 00001

Range: 1–65535

Format: Numeric

Indicates an entry in a table that keeps track of which nodes can access which prefixes. In the UPDATE window, this field is display-only and cannot be modified unless you delete this route.

255-700-762R11.1 8-21



Address Type Default: Exterior

Range: N/A

Format: Predefined

Indicates the type of domain address.

Exterior Indicates a connection from the advertising node to the address prefix that belongs to an external domain address.

Other Indicates a domain address that is not defined as internal or external.

Reject Indicates that messages from a matching address prefix should be discarded as unreachable.

Internal Indicates the same domain address, administrative author-ity, or attached device.

Address Scope Default: 000

Range: N/A

Format: Numeric

Indicates the level of the PNNI hierarchy where the connec-tivity between the advertising node and the address prefix is located.

VP Capability Default: True

Range: N/A

Format: Predefined

Indicates whether virtual path connections (VPCs) can be established between the advertising node and the address prefix.

True VPCs can be established between the advertising node and the address prefix.

False VPCs cannot be established between the advertising node and the address prefix.

Originate Adver-tisement

Default: True

Range: N/A

Format: Predefined

Indicates whether the local node should advertise the reach-able address on its domain (where it originates).

True The local node should advertise the reachable address on its domain (where it originates).

False The local node should not advertise the reachable address on its domain (where it originates).

Table 8-7. PNNI Route Address Entry Window Field Descriptions (Continued)


8-22 255-700-762R11.1



4 Click Add.

This entry is added to the PNNI Route Address Configuration Table.

5 In the Provisioning Menu Bar, click Device > Save PSAX Configuration. (See the previous section, “Saving Configuration Values.”)

6 To add additional route addresses, repeat Step 1–Step 5.

After the route is created, you can select the entry in the Route Address Con-figuration table and view the route.

7 To view the route information, select the entry in the Route Address Configuration table and double-click it.

Address Proto(display only)

Default: Mgmt

Range: N/A

Format: Predefined

Displays the protocol by which connectivity from the adver-tising node to the address prefix was learned.

Mgmt Connectivity from the advertising node to the address prefix was learned through Management protocol.

Other Connectivity from the advertising node to the address prefix was learned through user-defined protocol.

Local Connectivity from the advertising node to the address prefix was learned through Local protocol.

Pnni Connectivity from the advertising node to the address prefix was learned through PNNI protocol.

Time Stamp(display only)

Default: 0 days 00:00:00

Range: N/A

Format: days, hh:mm:ss

Indicates when connectivity became known to the local node.

Table 8-7. PNNI Route Address Entry Window Field Descriptions (Continued)


255-700-762R11.1 8-23



The VIEW PNNI Route Address Entry window appears (see Figure 8-9).

8 To update the route information, click the right mouse button within this window and a menu appears. Select Update.

The UPDATE PNNI Route Address Entry window appears (see Figure 8-10).

Figure 8-9. VIEW PNNI Route Address Entry Window

Figure 8-10. UPDATE PNNI Route Address Entry Window

8-24 255-700-762R11.1



If you do not wish to configure metrics, click Close on the PNNI Route Address Entry window and on the PNNI Route Address Table window. Oth-erwise, proceed to “Configuring Metrics”.

End

Configuring Metrics Measurement of various PNNI route attributes are called metrics. A maxi-mum of 20 PNNI metric entries per PNNI route address entries can be created per interface.

To configure PNNI metrics, perform the steps in the following procedure.

Begin

1 Click Metrics Table on the PNNI Route Address Entry window or the Map Link Entry window.

The View PNNI Metrics Table window appears (see Figure 8-11).

2 Right-click the mouse and a menu appears. Select Create.

Figure 8-11. PNNI Metrics Table Window

255-700-762R11.1 8-25



The ADD PNNI Metrics Entry window appears (see Figure 8-12).



Figure 8-12. ADD PNNI Metrics Entry Window

Button Function

Add Adds the metrics Configuration values you enter into the PNNI Metrics Entry window as a metrics entry in the PNNI Metrics Table window. This button is displayed on the ADD PNNI Met-rics Entry window).

Delete Deletes this PNNI metrics entry. This button is displayed on the VIEW PNNI Metrics Entry window)


8-26 255-700-762R11.1



Table 8-8. PNNI Metrics Entry Screen Field Descriptions


PNNI Metrics Identification Panel

Node Index Default:

Range: 1–400

Format: Numeric


Metrics Tag Default: 1

Range: N/A

Format: Numeric

Indicates a user-defined number that identifies this set of traffic parameters. The value in this field should match the value in the Metrics Tag field on the PNNI Route Address Configuration window. A single metrics tag can be assigned to multiple routes if they all have the same set of traffic parameters.

A maximum of 20 PNNI metric entries per PNNI route address entries can be created per interface.

Metrics Direction Default: Incoming

Range: N/A

Format: Predefined

Specifies the direction, with respect to the adver-tising node, to which these parameters apply (may have multiple service categories).

Incoming Indicates that metrics parameters will be applied to the incoming direction of data traffic.

Outgoing Indicates that metrics parameters will be applied to the outgoing direction of data traffic

Metrics Index Default: 1

Range: 0–31

Format: Numeric

Indicates an index into a set of parameters associ-ated with the given tag and direction.

Metrics Class Default: 00

Range: 0–31

Format: Alphanumeric

Specifies the service class to which this metric belongs.

CBR Indicates constant bit rate service class.

rt_VBR Indicates real-time variable bit rate service class.

nrt_VBR Indicates nonreal-time variable bit rate service class.

ABR Indicates available bit rate service class.

Note: This value is not currently supported.

UBR Indicates unspecified bit rate service class.

Admin Weight Default: 0000

Range: 1–16777215

Format: Numeric

Indicates the administrative weight from the advertising node to the remote end of the PNNI entity or to the reachable address or transit net-work, for the specified service categories.

The lower the value of the administrative weight, the more preferable this interface.

Max Cell Rate (cps) (Hex)

Default: 0

Range: N/A

Format: Hexadecimal

Indicates the maximum cell rate, in hexadecimal notation, for directions and specific service cate-gories (see the descriptions for the fields Metrics Direction and Metrics Classes).

255-700-762R11.1 8-27



4 Click Add.

This entry is added to the PNNI Metrics table.

Available Cell Rate (cps) (Hex)

Default: 0

Range: N/A

Format: Hexadecimal

Indicates the available bandwidth on this inter-face, in hexadecimal notation.

Max Cell Transmit Delay (Hex)

Default: 0

Range: N/A

Format: Hexadecimal

Indicates the length of delay as cells are transmit-ted from point A to point B, in hexadecimal nota-tion.

Cell Delay Variation (Hex)

Default: 0

Range: N/A

Format: Hexadecimal

Indicates the variation in the cell transit delay, in hexadecimal notation.

Cell Loss Ratio (0) (Hex)

Default: 0

Range: N/A

Format: Hexadecimal

Indicates the cells lost/number of cells sent for the peak cell rate 0 category, in hexadecimal notation.

Cell Loss Ratio (0+1) (Hex)

Default: 0

Range: N/A

Format: Hexadecimal

Indicates the cells lost/number of cells sent for the peak cell rate 0+1 category, in hexadecimal notation.

Cell Rate Margin (Hex)

Default: 0

Range: N/A

Format: Hexadecimal

Indicates the difference between the effective bandwidth allocation and the allocation for sus-tainable cell rate (the safety margin above the sustainable cell rate), in hexadecimal notation.

Variance Factor (Hex)

Default: 0

Range: N/A

Format: Hexadecimal

Indicates the relative measure of the square root of cell rate margin, normalized by the variance of some of the cell rates of all existing connections, in hexadecimal notation.

GCAC CLP Default: ClpEqual0

Range: N/A

Format: Predefined

Indicates the cell loss priority for generic connec-tion admission control (GCAC).

ClpEqual0 Indicates the GCAC CLP is equal to 0.

ClpEqual0or1 Indicates the GCAC CLP is equal to 0 or 1

Table 8-8. PNNI Metrics Entry Screen Field Descriptions (Continued)


8-28 255-700-762R11.1



After the metric is created, you can select the entry in the Metrics table and view the route (see Figure 8-13).


6 To add additional metrics, repeat this procedure.

7 On the PNNI Metrics Entry window, click Close.

8 On the PNNI Metrics Table window, click Close.

9 On the PNNI Route Address Entry window or the Map Link Entry win-dow, click Close.

10 On the PNNI Route Address Table window or the Map Link Entry win-dow, click Close.

End

Configuring Route TNS Information

To configure PNNI route TNSs, perform the steps in the following procedure.

Figure 8-13. VIEW PNNI Metrics Entry Window

255-700-762R11.1 8-29



Begin

1 On the PNNI tab, select Route TNS Configuration from the right-click menu, and the View PNNI Route TNS Table window appears (see Figure 8-14).



The ADD PNNI Route TNS Entry window appears (see Figure 8-15).

Figure 8-14. PNNI Route TNS Table Window

Button Function




8-30 255-700-762R11.1





Figure 8-15. ADD PNNI Route TNS Entry Window

Button Function

Add Adds the route address Configuration values you enter into the PNNI Route TNS Entry window as a route address entry in the PNNI Route Address Table window. This button is displayed on the ADD PNNI Route TNS Entry window.

Delete Deletes this PNNI route TNS entry. This button is displayed on the VIEW PNNI Route TNS Entry window.


Table 8-9. ADD PNNI Route TNS Entry Window Field Descriptions


PNNI Route TNS Entry Panel

Node Index Range: 1–400

Format: Numeric

Displays the identifier of a logical PNNI entity in the PSAX system. Enter the same value as assigned to the PNNI node (see the Node Index field on the PNNI Node Configuration window).

255-700-762R11.1 8-31



TNS Type Default: National Network Identifi-cation

Range: N/A

Format: Predefined

Indicates the Transit Network Selection type; the type of network ID of a specified transit network.

National Network Identification

Indicates the National Network ID is being used.

Other Indicates a user-defined TNS type is being used.

TNS Plan Default: CarrierI-dentificationCode

Range: N/A

Format: Predefined

Indicates the network ID plan of a specified tran-sit network.

CarrierIdentifica-tionCode

The Carrier Identification Code TNS Plan is being used.

Other User-defined.

TNS ID Default: 0000.0000

Range: N/A

Format: octets

Indicates the TNS ID.

TNS Index Default: 0

Range: N/A

Format: Numeric

Indicates the TNS Index.

Adv Node ID Default: 0

Range: N/A

Format: 11 octets

Indicates the Advertised node ID.

PNNI Route TNS Configuration Panel


Range: N/A

Format: Numeric

Indicates the TNS Interface Index

Advertised Port ID Default: 0000000000

Range: 0–50

Format: Numeric

Indicates the Advertised port identifier. For an SVC endpoint, enter the slot, port, and channel).

You can create up to 50 routes manually, to dis-play in the Route Address table. However, more than 50 routes can be displayed by the PSAX sys-tem because route addresses are also learned dynamically.

Route Type Default: Exterior

Range: N/A

Format: Predefined

Indicates the route type being used.

Exterior Indicates a connection from the advertising node to the address prefix that belongs to an external domain address.

Other Indicates a user-defined route type.

Table 8-9. ADD PNNI Route TNS Entry Window Field Descriptions (Continued)


8-32 255-700-762R11.1



TNS Scope Default: 000

Range: N/A

Format: Numeric

Indicates the level of the PNNI hierarchy where the connectivity between the advertising node and the address prefix is located.

VP Capability Default: True

Range: N/A

Format: Predefined

Indicates whether virtual path connections (VPCs) can be established between the advertis-ing node and the address prefix.

True Indicates that VPCs can be established between the advertising node and the address prefix.

False Indicates that VPCs cannot be established between the advertising node and the address prefix.

Metrics Tag Default: 0000000000

Range: N/A

Format: Numeric

Indicates the primary routing metric for this route and the traffic parameter values that apply for the connectivity from the advertising node to the transit network. There will be one or more entries in the PNNI Metrics Table whose value matches the value in this field. The semantics of this metric are determined by the routing-proto-col specified in the TNS Proto field value of the route. If this metric is not used, enter 1 in this field.

Originate Adver-tisement

Default: True

Range: N/A

Format: Predefined

Indicates that the transit network specified by this entry is to be advertised by the local node into its PNNI routing domain.

True Indicates that the transit network that is specified by this entry is to be advertised by the local node. Set this value if the value of the corresponding instance of PNNI Route Node Protocol is other than PNNI.

False Indicates the transit network specified by this entry is not to be advertised by the local node into its PNNI routing domain.

Route TNS Status Panel

Advertised PTSE ID(display only)

Default: 0

Range: N/A

Format: Numeric

Displays the Advertised PTSE ID.



255-700-762R11.1 8-33



4 Click Add.

This entry is added to the PNNI Route Address Configuration Table.


6 To add additional route TNS entries, repeat Step 1–Step 5.

After the route is created, you can select the entry in the Route TNS table and view the entry.

7 To view the route information, select the entry in the Route TNS table and double-click it.

The VIEW PNNI Route TNS Entry window appears.

8 To update the route information, click the right mouse button within this window and a menu appears. Select Update.

Address Proto(display only)

Default: Mgmt

Range: N/A

Format: Predefined

Displays the local interface over which the adver-tised node is reachable.

Mgmt Indicates configured manually; for example, by the SNMP or the dynamically as displayed on the console interface.

Other Indicates that the local interface is configured in an unspecified manner.

Local Indicates that the local interface is learned by ILMI (UNI side routing address).

Pnni Indicates that the local interface is learned by PNNI (as described in the ATM Forum PNNI 1.0 specification).

Time Stamp Default: 0 days 00:00:00

Range: N/A

Format: days, hh:mm:ss

Displays when connectivity became known to the local node.

Operational Status Default: Inactive

Range: N/A

Format: Predefined

Displays whether the reachable address prefix is operational and is being advertised by this node.

Inactive Indicates that the reachable address prefix is not operational and is not being advertised by this node.

Advertised Indicates that the reachable address prefix is operational and is being advertised by this node. The system will display this value if the ATM PNNI 1.0 interface is in service, and at least two nodes have connectivity to each other.



8-34 255-700-762R11.1



The UPDATE PNNI Route TNS Entry window appears.

End

Configuring PNNI Summary Addresses

A summary address is a reachable address prefix that tells a node how to summarize reachability information. A maximum of 20 PNNI summary addresses can be created per interface.

To configure PNNI summary addresses, perform the steps in the following procedure.

Begin

1 On the PNNI tab, select Summary Address Configuration from the right-click menu, and the View PNNI Summary Address Table window appears (see Figure 8-16).



Figure 8-16. PNNI Summary Address Table Window (Displaying an Entry)

Button Function




255-700-762R11.1 8-35



The View PNNI Summary Address Entry window appears (see Figure 8-17).



4 Click Add.

This entry is added to the PNNI Summary Address table.


6 To add additional summary addresses, repeat the steps in this procedure.

7 On the PNNI Summary Address Entry window, click Close.

8 On the PNNI Summary Address Table window, click Close.

End

Figure 8-17. ADD PNNI Summary Address Entry Window

Button Function

Add Adds the summary address Configuration values you enter into the PNNI Summary Address Entry window as a metrics entry in the PNNI Summary Address Table window. This button is dis-played on the ADD PNNI Summary Address Entry window.

Delete Deletes this PNNI metrics entry. This button is displayed on the VIEW PNNI Summary Address Entry window.


8-36 255-700-762R11.1



Viewing PNNI Map Information

The PNNI Map Table contains attributes necessary to find and analyze the operation of all links and nodes within the PNNI hierarchy, as seen from the perspective of a local node. It also provides information for network manag-ers to map port identifiers, showing the ports and links between the nodes at both endpoints.

Table 8-10. PNNI Summary Address Entry Window Field Descriptions


Node Index Range: 1–400

Format: Numeric

Indicates the identifier of a logical PNNI entity in the PSAX system.

Summary Address (Hex)

Range: 1–20 per node

Format: Hexadecimal

Indicates the address prefix of the ATM end sys-tem. This tells a node how to summarize reach-ability information. A maximum of 20 PNNI sum-mary addresses can be created per node.

Address Prefix Length

Range: 0–152

Format: Numeric

Indicates the leading portion of the ATM address.

Summary Address Type

Default: Internal

Range: N/A

Format: Predefined

Indicates whether address is inside or outside a PNNI routing domain.

Internal Denotes that a link, node, or reachable address is inside a PNNI routing domain.

Exterior Exterior denotes that a link, node, or reachable address is outside a PNNI routing domain

Suppress Advertise-ment

Default: False

Range: N/A

Format: Predefined

Determines whether the summary is advertised within this peer group.

False True indicates you do not want to advertise sum-mary addresses, enabling the node to reach all the represented end systems and nodes.

True False indicates you want to advertise addresses that match the reachable address prefix, regard-less of scope.

Summary Address State(display only)

Default: Inactive

Range: 1–50

Format: Predefined

Indicates whether the summary is currently being advertised by the node within the PSAX system into its peer group. A maximum of 50 routes can be advertised.

Inactive Indicates the summary address is not being advertised by the node within the PSAX system into its peer group.

Advertising Indicates the summary address is being advertised by the node within the PSAX system into its peer group.

255-700-762R11.1 8-37



The PNNI Map Table is read-only, because the map is generated dynamically during operation of the PNNI protocol, not manually configured.

To view PNNI map links, perform the steps in the following procedure.

Begin

1 On the PNNI tab, select Map Information from the right-click menu, and the View PNNI Map Table window appears (see Figure 8-18).


The PNNI Map Table window displays the node index, originating node iden-tifier, originating port identifier, and map index for various map links.

2 Click the right mouse button within this window and a menu appears. Select Display.

Figure 8-18. PNNI Map Table Window

Button Function




8-38 255-700-762R11.1



The VIEW PNNI Map Information Entry window appears (see Figure 8-19).


3 The values for the fields in this window are described in Table 8-11.

Figure 8-19. VIEW PNNI Map Link Entry Window

Button Function

Metrics Table

Opens the Metrics Table window (see Figure 8-11).


Table 8-11. PNNI Map Link Entry Window Field Descriptions



Default: N/A

Range: 1–400

Format: Numeric

Displays the identity of a logical PNNI entity in the PSAX system.

Originating Node ID(display only)

Default: N/A

Range: N/A

Format: Hexadecimal

Displays the node identifier of the node originat-ing connectivity within itself or to other nodes.

Remote Node ID(display only)

Default: N/A

Range: N/A

Format: Hexadecimal

Displays the node identifier at the other end of the link from the originating node. A value of all zeroes means the node identifier is unknown.

255-700-762R11.1 8-39



4 On the PNNI Map Information Entry window, click Close.

5 On the PNNI Map Table window, click Close.

End

Peer Group ID(display only)

Default: N/A

Range: N/A

Format: Numeric

Displays the peer group identifier of the originat-ing node and its peers.

Originating Port ID(display only)

Default: N/A

Range: N/A

Format: Numeric

Displays the identifier of the port, as assigned by the originating node, to which the port is attached.

Remote Port ID(display only)

Default: N/A

Range: N/A

Format: Numeric

Displays the identifier of the port at the remote end of the link as assigned by the remote node. A value of all zeroes means the port identifier is unknown.

Aggregate Token(display only)

Default: N/A

Range: N/A

Format: Numeric

Displays which links to a given neighbor node are to be aggregated and advertised as a single logical link.

PTSE Identifier(display only)

Default: N/A

Range: N/A

Format: Numeric

Displays a PTSE identifier describing this link or node.

Map Index(display only)

Default: N/A

Range: N/A

Format: Numeric

Displays an index into the set of link and nodal connectivity associated with the originating node and port. This index is needed since there may be multiple entries for nodal connectivity from a specific node and port pair, in addition to any entry for a horizontal link or uplink.

Map Type(display only)

Default: Horizontal Link

Range: N/A

Format: Predefined

Displays the type of PNNI entity.

VP Capacity(display only)

Default: True

Range: N/A

Format: Predefined

Indicates whether virtual path connections (VPCs) can be established across this PNNI entity.

True VPCs can be established across this PNNI entity.

False VPCs cannot be established across this PNNI entity.

Metrics Tag(display only)

Default: N/A

Range: N/A

Format: Numeric

Associates a set of traffic parameters that are always advertised together. This value is used as an index into the PNNI Metrics Table. A value of zero indicates no metrics are associated with this PNNI entity.

Table 8-11. PNNI Map Link Entry Window Field Descriptions (Continued)


8-40 255-700-762R11.1



Viewing PNNI Map Node Information

The PNNI Map Node Table contains a list of nodes as seen from the perspec-tive of a local node, and all information learned by the local node from nodal information PNNI topology state elements (PTSEs). This table is read-only, because the map is generated dynamically during operation of the PNNI pro-tocol, not manually configured.

To view PNNI map nodes, perform the steps in the following procedure.

Begin

1 On the PNNI tab, select Map Node Information from the right-click menu, and the View PNNI Map Node Table window appears (see Figure 8-20).



The VIEW PNNI Map Node Entry window appears (see Figure 8-21).

Figure 8-20. View PNNI Map Node Table Window (Displaying an Entry)

Button Function




255-700-762R11.1 8-41



The fields in this window are described in Table 8-12.

Figure 8-21. VIEW PNNI Map Node Entry Window

Table 8-12. PNNI Map Node Information Window Field Descriptions


[Node Index] Default: 00000

Range: 1–400

Format: Numeric


[Map Node ID] Default: N/A

Range: N/A


Displays the node identifier whose nodal information is being described.

[Peer Group ID] Default: N/A

Range: N/A


Indicates the first 12 bytes (default) of the ATM address. This value is the combination of the ATM address and the node level. This value is generated and displayed by the system automatically. For more information, see Section 5.3.3, Node Identifiers, in the ATM Forum Specification, Private Network-Network Interface Specification Version 1.0 (PNNI 1.0), af-pnni-0055.000.

[ATM Address] Default: N/A

Range: N/A


Displays the ATM end system address of the originating node.

8-42 255-700-762R11.1



[Restricted Transit]

Default: True

Range: N/A

Format: Predefined

Indicates whether the originating node is restricted to only allow support of SVCs originating or terminating at this node. This attribute reflects the setting of the restricted transit bit received in the nodal information PTSE from the originating node.

True Indicates that the transit capabilities are restricted. Often, transit connections are not allowed. A restricted transit node is a node to be used to transmit by a call in restricted circum-stances. It is free from such restrictions when it is used to originate or terminate a call.

False Indicates that transit connections are allowed.

[Complex Rep] Default: False

Range: N/A

Format: Predefined

Indicates the complex node representation, a collection of nodal state parameters that provide detailed state information associated with the logical node.

False Indicates that the originating node does not use the complex node representation.

True Indicates that the originating node uses the complex node representation. If the value is True, the spokes and bypasses that make up the complex node representation should be found in the PNNI Map Address Table. This attribute reflects the setting of the nodal representation bit received in the nodal information PTSE from the originating node.

[Restricted Branching]

Default: False

Range: N/A

Format: Predefined

Displays whether the originating node is able to support addi-tional branches. This attribute reflects the setting of the restricted branching bit received in the nodal information PTSE from the originating node.

False Indicates that additional branches are supported.

True Indicates that restricted branching is supported.

[Database Overload]

Default: False

Range: N/A

Range: Predefined

Indicates whether the originating node’s topology database is currently overloaded. This attribute has the same value as the non-transit for PGL election bit in the nodal information group originated by this node.

False Indicates that the originating node’s topology database is not currently overloaded.

True Indicates that the originating node’s topology database is cur-rently overloaded.

[I Am Leader] Default: False

Range: N/A

Format: Predefined

Indicates whether the originating node claims to be the peer group leader (PGL) of its peer group. This attribute reflects the setting of the "I Am Leader" bit received in the nodal information PTSE from the originating node.

False Indicates the originating node does not claim to be the PGL of its peer group.

True Indicates that the originating node claims to be PGL.

Table 8-12. PNNI Map Node Information Window Field Descriptions (Continued)


255-700-762R11.1 8-43



3 On the PNNI Map Node Entry window, click Close.

4 On the PNNI Map Node Table window, click Close.

End

Viewing PNNI Map Address Information

The PNNI Map Address Table contains a list of all reachable addresses from each node visible to the local node. The table is read-only, reflecting the fact that reachable addresses are discovered during dynamic operation of the PNNI protocol, not manually configured.

To view PNNI map addresses, perform the steps in the following procedure.

Begin

1 On the PNNI tab, select Map Address Information from the right-click menu, and the View PNNI Map Address Table window appears (see Figure 8-22).

[Leadership Pri-ority]

Default: 0

Range: N/A

Format: Numeric

Indicates the node ranking in a peer group for the peer group leader position the next time a PGL is needed.

[Preferred Pgl] Default: N/A

Range: N/A


Displays the node that the originating node believes should be or is peer group leader (PGL) of its peer group. If the origi-nating node has not chosen a preferred PGL, this value is set to 0.

[Parent Node ID]

Default: N/A

Range: N/A


Displays the node identifier of the parent logical group node (LGN) when the originating node is a peer group leader. If the originating node is not peer group leader of its peer group, and the I Am Leader field is set to False, then this value is set to 0.

[Parent ATM Address]

Default: N/A

Range: N/A


Displays the ATM address of the parent LGN when the origi-nating node is a peer group leader. If the originating node is not peer group leader of its peer group, and the I Am Leader field is set to False, this value is set to 0.

[Parent Peer Group ID]

Default: N/A

Range: User-defined


Displays the node's parent peer group identifier when the originating node is a peer group leader. If the originating node is not peer group leader of its peer group, and the I Am Leader field is set to False, this value is set to 0.

[Parent Pgl Node ID]

Default: N/A

Range: User-defined


Displays the node elected as peer group leader of the parent peer group when the originating node is a peer group leader. If the originating node is not peer group leader of its peer group, and the I Am Leader field is set to False, this value is set to 0.

Table 8-12. PNNI Map Node Information Window Field Descriptions (Continued)


8-44 255-700-762R11.1





The VIEW PNNI Map Address Entry window appears (see Figure 8-23).


Figure 8-22. View PNNI Map Address Table Window (Displaying Multiple Entries)

Button Function




Figure 8-23. PNNI Map Address Entry Window

255-700-762R11.1 8-45



3 On the PNNI Map Address Entry window, click Close.

4 On the PNNI Map Address Table window, click Close.

End

Viewing PNNI Map TNS Information

The PNNI Map TNS Table is read-only, reflecting the fact that reachable addresses are discovered during dynamic operation of the PNNI protocol, not manually configured.

To view PNNI map addresses, perform the steps in the following procedure.

Table 8-13. PNNI Map Address Information Window Field Descriptions



Default: 00000

Range: 1–400

Format: Numeric


Advertising Node ID(display only)

Default: N/A

Range: N/A

Format: Numeric

Displays the identifier of a node advertising reachability to the address prefix.

Advertising Port ID(display only)

Default: 0

Range: N/A

Format: Numeric

Displays the port identifier the advertising node uses to reach the given address prefix.

Map Address Index(display only)

Default: 00000

Range: N/A

Format: Numeric

Displays an arbitrary index generated by the CPU that is used to number all of the map addresses advertised by the specified node.

Address(display only)

Default: N/A

Range: N/A

Format: Numeric

Displays the ATM end system address prefix.

Prefix Length(display only)

Default: 00000

Range: N/A

Format: Numeric

Displays the prefix length to be applied to the ATM end system address prefix.

8-46 255-700-762R11.1



Begin

1 On the PNNI tab, select Map TNS Information from the right-click menu, and the View PNNI Map TNS Table window appears (see Figure 8-24).



The VIEW PNNI Map TNS Entry window appears.

The fields in this window are described in Table 8-14 and Table 1-15.

3 On the PNNI Map TNS Entry window, click Close.

4 On the PNNI Map TNS Table window, click Close.

End

Figure 8-24. View PNNI Map TNS Table Window

Button Function




Table 8-14. PNNI Map TNS Table Window Field Descriptions


Map TNS Information Panel

Note: For more information on the values in the display columns below, see the Display Description Table for the PNNI Map TNS Configuration window.

255-700-762R11.1 8-47



Viewing PNNI Link Information

The PNNI Link Table window contains the attributes necessary to describe the operation of logical links attached to the PSAX system and the relation-ship with the neighbor nodes on the other end of the links. Links are

Node Index (display only)

Default: 0

Range: 1–400

Format: Numeric

Displays a unique identifier for this PNNI system node.

Advertising Node ID

Default: 0

Range: N/A

Format: Hexadecimal address

Displays the Node ID advertising reachability to the transit network.

Advertised Port ID Default: 0

Range: N/A

Format: 2 octets

Displays the Port ID used from the advertising mode to reach the given transit network.

Table 8-14. PNNI Map TNS Table Window Field Descriptions (Continued)


Table 8-15. PNNI Map TNS Configuration Window Field Descriptions


Map TNS Information Panel

[PNNI Node Index] Default: 0

Range: 1–400

Format: Numeric

Displays the node index, a logical PNNI entity in the PSAX system.

[Adv Node Id] Default:

Range:

Format: Hexadecimal

Displays the 11-octet advertising node identifier. This node is advertising reachability to the transit network.

[Adv Port Id] Default: 0

Range:

Format:

Displays the 10-digit port identifier of the node advertising to reach the given transit network (see Annex H, af-pnni-0055.000).

[TNS Type] Default: National-NetworkId

Range: N/A

Format: Predefined

Displays the type of network ID used for the transit network.

[TNS Plan] Default: CarrierId-Code

Range: N/A

Format: Predefined

Displays the type of network ID Plan that the net-work has been assigned.

[TNS Id] Default: 0

Range:

Format:

Displays the value of the transit network identifier.

8-48 255-700-762R11.1



attached to a specific node within the PSAX system. Links represent horizon-tal links between the lowest level of neighboring peers, outside links, uplinks, or horizontal links to or from logical group nodes (LGNs). A maximum of 100 PNNI links can be created per interface.

The PNNI Link Table window is read-only because the information in the PNNI link table is generated dynamically by the PNNI protocol, not manually configured. For more information, see the ATM Forum Specification, Private Network-Network Interface Specification Version 1.0 (PNNI 1.0), af-pnni-0055.000, Section 5.6.

To view PNNI links, perform the steps in the following procedure.

Begin

1 On the PNNI tab, select Link Information from the right-click menu, and the View PNNI Link Table window appears (see Figure 8-25).


The PNNI Link Table window displays the node index, and the link port iden-tifier for various PNNI links.


Figure 8-25. View PNNI Link Table Window

Button Function




255-700-762R11.1 8-49



The VIEW PNNI Link Entry window appears (see Figure 8-26).


Figure 8-26. VIEW PNNI Link Entry Window

Table 8-16. PNNI Link Entry Window Field Descriptions



Default: 00000

Range: 1–400

Range: Numeric

Displays the identity of a logical PNNI entity in the PSAX sys-tem.

Link Port ID(display only)

Default: 000000

Range: N/A

Format: Numeric

Displays the port identifier (slot, port, channel) of the link selected by the local node. This value has meaning only within the context of the node to which the port is attached.

Link Version(display only)

Default: Version1point0

Range: N/A

Format: Predefined

Displays the version of PNNI routing protocol used to exchange information over this link for horizontal and outside links between lowest-level nodes and for links of unknown type.

Version1point0 Indicates PNNI Version 1.0 is being used.

Unknown Displays the communication state with the neighbor.

• If the node has not yet been established, the version is set to Unknown.

• For uplinks (where the port ID is not also used for the under-lying outside link) or links to or from LGNs, the version is set to Unknown.

8-50 255-700-762R11.1



Link Type(display only)

Default: Low-estLevelHorizon-talLink

Range: Network-dependent

Format: Predefined

Displays the type of link being described.

Unknown Indicates that the link type is unknown.

LowestLevelHo-rizontalLink

Indicates that this link is the logical link between lowest nodes in the same peer group.

HorizontalLink-ToFromLgn

Indicates that this link is the logical link between logical group nodes (LGNs) in the same peer group.

LowestLev-elOutsideLink

Indicates that this link is the logical link between the lowest nodes in the same peer group.

Uplink Indicates that connectivity exists from a border node to an upn-ode; that is, this link is the uplink to a higher level node in the hierarchy.

OutsideLin-kAndUplink

Indicates that this link is the logical link between two border nodes, and the border nodes represent an upnode; that is, this link is the outside link to another network and uplink.

Table 8-16. PNNI Link Entry Window Field Descriptions (Continued)


255-700-762R11.1 8-51



Link Hello State(display only)

Default: N/A

Range: N/A

Format: Predefined

Displays one of the possible conditions that characterize Hello types and the node states that the Hellos originated from.

Down Indicates the initial state of the Hello Finite State Machine (FSM), a table displaying what the software does after receiving new information. This state is also reached when lower-level protocols have indicated that the link is not usable. No PNNI routing packets will be sent or received over such a link.

Attempt Indicates either no Hellos or Hellos with mismatch information have been received recently from the neighbor. In this state, attempts are made to contact the neighbor by periodically send-ing the neighbor Hellos with the period Hello Interval.

OneWayInside Indicates Hellos have recently been received from the neighbor and both nodes are members of the same peer group, but the remote node ID and remote port ID in the neighbor’s Hellos were set to 0.

TwoWayInside Indicates Hellos have recently been received from the neighbor and both nodes are members of the same peer group, and including the correct remote node ID and remote port ID fields. When this state is reached, it indicates that bidirectional com-munication over this link between the two nodes has been made. Database summary packets, PTSE Request packets, PTSPs, and PTSE acknowledgment packets can only be transmitted over links that are in the TwoWayInside state. For physical links and VPCs, only those links that are in the TwoWayInside state can be advertised by this node in PTSEs as horizontal links.

OneWayOutside Indicates Hellos have recently been received from the neighbor and that the neighbor node belongs to a different peer group, but the remote node ID and remote port ID in the neighbor’s Hellos were set to 0. In this state and in the TwoWayOutside state, the node searches for a common peer group that contains both this node and the neighbor node.

TwoWayOutside Indicates Hellos have recently been received from the neighbor, whose node belongs to a different peer group, and including the correct remote node ID and remote port ID fields, but with a nodal hierarchy list that does not include any common peer group. In this state and in the OneWayOutside state, the node searches for a common peer group that contains both this node and the neighbor node.

CommonOutside Indicates whether a common level of the routing hierarchy has been found, in addition to achieving full bidirectional commu-nication between the two nodes. Links that have reached the CommonOutside state can be advertised in PTSEs as uplinks to the upnode.



8-52 255-700-762R11.1



3 On the PNNI Link Entry window, click Close.


Default: N/A

Range: N/A


Displays the node identifier of the node at the remote end of the link.

Remote Port ID(display only)

Default: 000000

Range: N/A

Format: Numeric

Displays the identifier (slot, port, channel) of the port at the remote end of the link as assigned by the remote node. If Out-sideLinkAndUplink is displayed in the Link Type field, this is the port identifier assigned by the lowest-level neighbor node to identify the outside link. If Unknown is displayed in the Link Version field, or if Uplink is displayed in the Link Type field, the remote port ID is set to 0.

Derived Aggregate Token(display only)

Default: 000

Range: N/A

Format: Numeric

Displays a PNNI aggregation token, used to determine which links to a given neighbor node are to be aggregated and adver-tised as a single logical link.

Upnode ID(display only)

Default: N/A

Range: N/A

Format: Numeric

Displays the node identifier of the upnode (the neighbor node's identity within the common peer group) for outside links and uplinks. When the upnode, horizontal links, or link type is not yet known, this field is set to 0.

Upnode ATM Address(display only)

Default: N/A

Range: N/A


Displays the ATM end system address used to establish connec-tions to the upnode for outside links and uplinks. When the upnode, horizontal links, or link type is not yet known, this field is set to 0.

Common Peer Group ID(display only)

Default: N/A

Range: N/A

Format: Numeric

Displays the common peer group identifier. For outside links and uplinks, this attribute contains the peer group identifier of the lowest level common peer group in the ancestry of the neighboring node and the node within the PSAX system. This field value is determined by the Hello exchange of hierarchical information that occurs between the two lowest-level border nodes. When the common peer group, horizontal links, or link type is not yet known, this field is set to 0.

SVCC RCC Index(display only)

Default: 000

Range: N/A

Format: numeric

Displays the value of this object, which identifies the switched virtual channel connection (SVCC)-based routing control chan-nel (RCC) for which the entry contains management informa-tion.

Received Hel-los(display only)

Default: 0000

Range: N/A

Format: Numeric

Indicates the number of hello packets received over this link for horizontal and outside links between lowest-level nodes and for links of unknown type. If HorizontalLinkToFromLgn or Uplink is displayed in the Link Type field, this field is set to 0.

Transmitted Hellos(display only)

Default: 0000

Range: N/A

Format: Numeric

Displays the number of hello packets transmitted over this link for horizontal and outside links between lowest-level nodes and for links of unknown type. If HorizontalLinkToFromLgn or Uplink is displayed in the Link Type field, this field is set to 0.



255-700-762R11.1 8-53



4 On the PNNI Link Table window, click Close.

End

Viewing PNNI SVCC RCC Information

To view PNNI SVCC RCC and ATM security information, see Chapter 8.

Viewing PNNI Neighbor Peer Information

The PNNI Neighbor Peer Table window contains all the attributes necessary to describe the relationship a node in the PSAX system has with a neighbor-ing node within the same peer group. The PNNI Neighbor Peer Table window is read-only because neighboring peers are generated dynamically by the PNNI protocol, not manually configured. For more information, see the ATM Forum Specification, Private Network-Network Interface Specification Version 1.0, af-pnni-0055.000 (PNNI 1.0), Sections 5.7 and 5.8.

To view PNNI neighbor peers, perform the steps in the following procedure.

Begin

1 On the PNNI tab, select Neighbor Peer Information from the right-click menu, and the View PNNI Neighbor Peer Table window appears (see Figure 8-27).


The PNNI Neighbor Peer Table window displays the node index and neighbor peer remote node index for various neighbor peers, as created.


Figure 8-27. View PNNI Neighbor Peer Table Window

Button Function




8-54 255-700-762R11.1



The VIEW PNNI Neighbor Peer Entry window appears (see Figure 8-28).


Figure 8-28. VIEW PNNI Neighbor Peer Entry Window

Table 8-17. PNNI Neighbor Peer Entry Window Field Descriptions



Default: 00000

Range: 1–400

Format: Numeric



Default: N/A

Range: N/A

Format: Numeric

Displays the node identifier of the neighboring peer remote node.

255-700-762R11.1 8-55



State(display only)

Default: Npdown

Range: N/A

Format: Predefined

Displays the state of this node's neighboring peer state machine associated with the neighbor peer remote node ID.

Npdown The initial state of a neighboring peer FSM. This state indicates that there are no active links (that is, in Hello state 2-WayInside) to the neighboring peer. In this state, there are no adjacencies associ-ated with the neighboring peer.

Negotiating Indicates that this neighbor peer is currently in the first step in creating an adjacency between the two neighboring peers. The goal of this step is to decide which node is the master, and to decide upon the initial Database Summary (DS) sequence number.

Exchanging Indicates that the node is in the exchanging state, in which the node describes its topology database by sending Database Summary packets to the neighboring peer. As a result of processing DS packets, the node can request the required PTSEs.

Loading Indicates that the node is in the loading state, in which a full sequence of DS packets has been exchanged with the neighboring peer, the required PTSEs are requested, and at least one has not yet been received.

Full Indicates that the node is in the full state, in which the node has received all PTSEs known to be available from the neighboring peer. Links to the neighboring peer can now be advertised in PTSEs.

SVCC RCC ID(display only)

Default: 0

Range: N/A

Format: Numeric

Displays the switched virtual channel connection (SVCC)-based routing control channel (RCC) being used to communicate with the neighboring peer if one exists. If both the local node and the neighboring peer node are lowest-level nodes, this field is set to 0.

Port Count(display only)

Default: 0

Range: N/A

Format: Numeric

Displays a count of the total number of ports that connect to the neighboring peer. If the neighbor-ing peer only communicates via an SVCC-based RCC, the value of this field is set to zero. Other-wise it is set to the total number of ports to the neighboring peer in the Hello state two-way inside.

Received DB Sums(display only)

Default: 0

Range: N/A

Format: Numeric

Displays a count of the number of database sum-mary packets received from the neighboring peer.

Table 8-17. PNNI Neighbor Peer Entry Window Field Descriptions (Continued)


8-56 255-700-762R11.1



3 On the PNNI Neighbor Peer Entry window, click Close.

4 On the PNNI Neighbor Peer Table window, click Close.

End

Viewing PNNI Neighbor Peer Port Information

The PNNI Neighbor Peer Port table is a table of all ports in hello state two-way inside to a given neighboring peer node. This table is only used for low-est-level nodes.

For more information, see the ATM Forum Specification, Private Network-Net-work Interface (PNNI 1.0) Specification Version 1.0, af-pnni-0055.000, Section 5.7.1 "Port ID List."

To view PNNI neighbor peer ports, perform the steps in the following proce-dure.

Begin

1 On the PNNI tab, select Neighbor Peer Port Information from the right-click menu, and the View PNNI Neighbor Peer Port Table window appears (see Figure 8-29).

Transmitted DB Sums(display only)

Default: 0

Range: N/A

Format: Numeric

Displays a count of the number of database sum-mary packets transmitted to the neighboring peer.

Received PTSPs(display only)

Default: 000

Range: N/A

Format: Numeric

Displays a count of the number of PNNI topology state packets (PTSPs) received from the neighbor-ing peer.

Transmitted PTSPs(display only)

Default: 000

Range: N/A

Format: Numeric

Displays a count of the number of PTSPs retrans-mitted to the neighboring peer.

Received PTSE Requests(display only)

Default: 0

Range: N/A

Format: Numeric

Displays a count of the number of PNNI topology state element (PTSE) request packets received from the neighboring peer.

Transmitted PTSE Requests(display only)

Default: 0

Range: N/A

Format: Numeric

Displays a count of the number of PTSE request packets transmitted to the neighboring peer.

Received PTSE Acks(display only)

Default: 000

Range: N/A

Format: Numeric

Displays a count of the number of PTSE acknowl-edgement packets received from the neighboring peer.

Transmitted PTSE Acks(display only)

Default: 000

Range: N/A

Format: Numeric

Displays a count of the number of PTSE acknowl-edgement packets transmitted to the neighboring peer.

Table 8-17. PNNI Neighbor Peer Entry Window Field Descriptions (Continued)


255-700-762R11.1 8-57




The PNNI Neighbor Peer Port Table window displays the node index, neigh-bor peer remote node identifier, and neighbor peer port identifier for various neighbor peer ports, as created.


The VIEW PNNI Neighbor Peer Port Entry window appears (see Figure 8-30).


3 On the PNNI Neighbor Peer Port Entry window, click Close.

4 On the PNNI Neighbor Peer Port Table window, click Close.

End

Figure 8-29. View PNNI Neighbor Peer Port Table Window

Button Function




Figure 8-30. VIEW PNNI Neighbor Peer Port Entry Window

8-58 255-700-762R11.1



Viewing PNNI PTSE Information

A PNNI topology state element (PTSE) is a collection of PNNI information set among all logical nodes within a peer group. The PNNI PTSE table contains the attributes that describe the most recent instances of PTSEs in a node's topology database. For more information, see the ATM Forum Specification, Private Network-Network Interface (PNNI 1.0) Specification Version 1.0, af-pnni-0055.000, Section 5.8.2. The PNNI PTSE Table window displays PTSE entries currently residing in the PSAX system.

To view PTSEs, perform the steps in the following procedure.

Table 8-18. PNNI Neighbor Peer Port Entry Window Field Descriptions


Total:(display only)

Default: 0/0

Range: N/A

Format: Numeric

Displays the first number in this field indicates the identification number of the peer port table entry on the first line of the currently displayed window. The second number indicates the total number of peer port table entries for this connec-tion type.


Default: N/A

Range: 1–400

Format: Numeric


Remote ID(display only)

Default: N/A

Range: N/A

Format: Hexadecimal

Displays the Node identifier of the neighboring peer node.

Port ID(display only)

Default: N/A

Range: N/A

Format: Numeric

Displays a port identifier to the neighboring peer that is in the hello state two-way inside.

Port Flood Stat.(display only)

Default: N/A

Range: N/A

Format: Numeric

Displays whether the port is being used for trans-mission of flooding and database synchronization information to the neighboring peer.

255-700-762R11.1 8-59



Begin

1 On the PNNI tab, select PTSE Information from the right-click menu, and the View PNNI PTSE Table window appears (see Figure 8-31).



The VIEW PNNI PTSE Entry window appears (see Figure 8-32).


Figure 8-31. View PNNI PTSE Table Window (Displaying Multiple Entries)

Button Function




Figure 8-32. VIEW PNNI PTSE Entry Window

8-60 255-700-762R11.1



Table 8-19. PNNI PTSE Entry Window Field Descriptions


[Node Index] Default: 00000

Range: 1–400

Format: Numeric


[Originating Node ID]

Default: N/A

Range: N/A

Format: Hexadecimal

Displays the 20-octet node identifier of the node that originated the PTSE.

Identifier Default: 0

Range: N/A

Format: Numeric

Displays the value of the PTSE identifier assigned to the PTSE by its originator.

Type Default: Other

Range: N/A

Format: Predefined

Describes the architecture parameters set selected.

Other Indicates user defined.

NodalState Param-eters

Indicates that the nodal state parameter informa-tion is contained in the PTSE. A nodal state param-eter provides information that captures an aspect or property of a node.

Nodal Information Indicates that the nodal information is contained in the PTSE. Nodal information describes the node (including resource availability information, and not including reachability information). It specifi-cally includes:

• ATM end system address of the node

• Leadership priority

• Node information flags

• Preferred peer group leader node ID

• Next higher-level binding information (included if this node is Peer Group Leader

Internal Reachable Addresses

Indicates that an internal reachable address is an address of a destination that is directly attached to the logical node that advertises the address.

Exterior Reachable Addresses

Indicates that an exterior reachable address is an address that can be reached through a PNNI rout-ing domain but is not located in that PNNI routing domain.

HorizontalLinks Indicates that a horizontal link is between nodes in the same peer group.

Uplinks Indicates that an uplink is connectivity from a bor-der node to an upnode at a higher level in the PNNI hierarchy.

255-700-762R11.1 8-61



3 On the PNNI PTSE Entry window, click Close.

4 On the PNNI PTSE Table window, click Close.

End

Viewing PNNI Statistics

To view PNNI statistics, perform the steps in the following procedure.

Begin

1 On the PNNI tab, select PNNI Statistics from the right-click menu, and the PNNI Statistics window appears (see Figure 8-33).


2 To refresh this window, click Update.

3 To update the statistics in this window continuously, click Poll-. Click Poll+ to terminate polling.

4 Click Close.


End

[Sequence Number]

Default: 0

Range: N/A

Format: Numeric

Displays the sequence number of the instance of the PTSE as it appears in the local topology data-base.

[Checksum] Default: 00000

Range: N/A

Format: Numeric

Displays the value of the PTSE checksum as it appears in the local topology database.

[Life Time] Default: 0000

Range: N/A

Format: Numeric

Displays the value of the remaining lifetime for the given PTSE as it appears in the local topology data-base.

Table 8-19. PNNI PTSE Entry Window Field Descriptions (Continued)


8-62 255-700-762R11.1




Figure 8-33. PNNI Statistics Window

Button Function

Update Refreshes the statistics manually.

Poll Continuously update the statistics and changes the button label to Poll-.

Terminates polling and changes the button label to Poll+.


255-700-762R11.1 8-63



Table 8-20. PNNI Statistics Window Field Descriptions


DTL Count Origina-tor

Default: 0000000000

Range: N/A

Format: Numeric

The total number of designated transit list (DTL) stacks that the PSAX device has originated as the DTL originator and placed into signaling mes-sages. This includes the initial DTL stacks com-puted by the PSAX device and those for any alter-nate route. DTL stacks are computed by the PSAX device in response to crankbacks.

DTL Count Border Default: 0000000000

Range: N/A

Format: Numeric

The number of partial DTL stacks that the PSAX device has added into signaling messages as an entry border node. This includes the initial partial DTL stacks computed by the PSAX device and those for any alternate route. Partial DTL stacks are computed by the PSAX device in response to crankbacks.

Crankback Count Originator

Default: 0000000000

Range: N/A

Format: Numeric

The count of the total number of connection setup messages including DTL stacks originated by the PSAX device that have cranked back to the PSAX device at all levels of the hierarchy.

Crankback Count Border

Default: 0000000000

Range: N/A

Format: Numeric

The count of the total number of connection setup messages, including DTLs added by the PSAX device as an entry border node that have cranked back to the PSAX device at all levels of the hierarchy. This count does not include crank-backs for which the PSAX device was not the crankback destination. Only those crankbacks that were directed to the PSAX device are counted here.

Alternate Route Count Originator

Default: 0000000000

Range: N/A

Format: Numeric

The total number of alternate DTL stacks that the PSAX device has computed and placed into sig-naling messages as the DTL originator.

Alternate Route Count Border

Default: 0000000000

Range: N/A

Format: Numeric

The total number of alternate partial DTL stacks that the PSAX device has computed and placed into signaling messages as an entry border node.

Route Fail Count Originator

Default: 0000000000

Range: N/A

Format: Numeric

The total number of times where the PSAX device failed to compute a viable DTL stack as the DTL originator for a call. It indicates the number of times a call was cleared from the PSAX device due to originator routing failure.

Route Fail Count Border

Default: 0000000000

Range: N/A

Format: Numeric

The total number of times where the PSAX device failed to compute a viable partial DTL stack as an entry border node for some call. It indicates the number of times a call was either cleared or cranked back from the PSAX device due to border routing failure.

8-64 255-700-762R11.1


Chapter 8 Configuring ATM Routing Data Using PNNISaving Configuration Values




Route Fail Unreach-able Originator

Default: 0000000000

Range: N/A

Format: Numeric

The total number of times where the PSAX device failed to compute a viable DTL stack as the DTL originator because the destination was unreachable, that is, calls that were cleared with the message “specified transit network unreach-able” or the message “destination unreachable” in the cause incoming exclusion (IE).

Route Fail Unreach-able Border

Default: 0000000000

Range: N/A

Format: Numeric

The total number of times where the PSAX device failed to compute a viable partial DTL stack as an entry border node because the target of the path calculation was unreachable, that is, calls that are cleared or cranked back with the cause “specified transit network unreachable” or the cause “destination unreachable” in the cause IE.

Route Node Num-ber

Default: 0000000000

Range: N/A

Format: Numeric

The number associated with the route node from which the statistics on this window are being generated.

Route Address Number

Default: 0000000000

Range: N/A

Format: Numeric

The number associated with the route address from which the statistics on this window are being generated.

Table 8-20. PNNI Statistics Window Field Descriptions (Continued)


255-700-762R11.1 8-65


Chapter 8 Configuring ATM Routing Data Using PNNISaving Configuration Values

8-66 255-700-762R11.1


9 Configuring ATM Security

Overview of This Chapter

This chapter describes how to configure ATM security using the ATM UNI and ATM PNNI interfaces, and the PNNI system-wide configuration options.

Overview of the ATM Security FeatureThe ATM Security feature protects ATM traffic by encrypting the ATM con-trol plane, providing integrity and confidentiality security services to signal-ing messages or routing packets. It also provides a mechanism for signaling that can provide strong cryptographic data integrity with replay/reordering protection. ATM control plane entities are able to verify the source and con-tents of a signaling message before resources are allocated for the requests. This function can protect the network from certain security threats. The PSAX system supports control plane authentication and integrity security service.

On the PSAX system, users can configure ATM security integrity and confi-dentiality service for ATM UNI and ATM PNNI interfaces. For ATM PNNI, security agents are configured both at the PNNI node level and at the inter-face level for signaling and routing PVCs.

Configuring PNNI SVCC RCC Security Information

Setting the Values for PNNI SVCC RCC Security Information

To configure ATM security, you must first set system-wide parameters from the PNNI tab. Perform the steps in the following procedure.

Begin

1 In the Device window click the PNNI tab.

The PNNI Node Configuration Table page appears.

2 In the PNNI Node Configuration Table, click the right mouse button and a menu appears. Select Create.

The ADD PNNI Node Entry window appears.

3 From the ADD, VIEW, or UPDATE PNNI Node Entry window, click ATM Security Config - Routing SVCC.

The PNNI SVCC RCC Security Configuration window appears (see Figure 9-1).


255-700-762R11.1 9-1

Chapter 9 Configuring ATM SecurityConfiguring PNNI SVCC RCC Security Information



5 Click Create.

End

Figure 9-1. PNNI SVCC RCC Security Configuration Window

Button Function

Create Applies the values set for the fields on this window.

Delete Removes this entry.

Reset Restores the values on this window to the last applied values.

Bring Into Service Brings this configuration into service.

Take Out of Service Takes this configuration out of service.

9-2 255-700-762R11.1



Table 9-1. ATM PNNI SVCC RCC Security Configuration Window Field Descriptions

Field Name Field Values Descriptions

Peer Group ID (Hex)

Default: 0

Range: N/A

Format: Hexadecimal

Displays the first 12 bytes (default) of the ATM address. This value, which is generated and dis-played by the system automatically, is the combi-nation of the ATM address and the node level. The first byte indicates the node level. The fol-lowing bytes comes from the ATM address where the number bytes coming from the ATM address depend on the Node level. For example, a node level of 96 bits (default) then the next 12 bytes (96 its) are from the ATM address. For more information, see the ATM Forum Specification, Private Network-Network Interface (PNNI 1.0) Specifi-cation Version 1.0, af-pnni-0055.000, Section 5.3.3, Node Identifiers.

Service Profile Default: Integrity-172

Range: N/A

Format: Predefined

Specifies the service type that is provided by the ATM security agent on this signaling or routing PVC according to the ATM Forum Specification af-sec-0172.000.

Integrity-172 Indicates that the integrity security service with-out replay/reordering protection will be provided to this PVC.

Integrity-Confiden-tiality-172

Indicates that the integrity security service and confidentiality security service without replay/reordering protection will be provided to this PVC.

Integrity-ReplayReorderPro-tection-172

Indicates that the integrity security service with replay/reordering protection will be provided to this PVC.

Integrity-Confiden-tiality-ReplayReor-derProtection-172

Indicates that the integrity security service and confidentiality security service with replay/reor-dering protection will be provided to this PVC.

Master Key Length Default: Key-128-bits

Range: 40–256

Format: Predefined (bits)

Specifies the length of the master key in bits. Select a value from 40 to 256 bits (in increments of 8 bits).

Master Key Default: 0

Range: 5–32

Format: Hexadecimal (bits)

Specifies the value for the master key that is shared between two peer security agents for integrity or confidential security services or both.

255-700-762R11.1 9-3



SKU Encryption Algorithm

Default: MD5

Range: N/A

Format: Predefined

Specifies the encryption algorithm used for encrypting session keys that need to be for-warded from this security agent to the peer secu-rity agent.

MD5 Indicates that the MD5 encryption algorithm is used for session key update.

SHA-1 Indicates that the SHA-1 encryption algorithm is used for session key update.

Integrity Security Service Panel

MAC Algorithm Default: HMAC-MD5

Range: N/A

Format: Predefined

Specifies the type of MAC algorithm that is used for integrity security service on this interface.

HMAC-MD5 Indicates that the MAC algorithm used for integ-rity security service is HMAC-MD5.

HMAC-SHA-1 Indicates that the MAC algorithm used for integ-rity security service is HMAC-SHA-1.

SessKeyLength Default: Key-128-bits

Range: 40–256


Specifies the length of the integrity session key. Select a value from 40 to 256 bits (in increments of 8 bits).

Init Session Key A Default: 0

Range: 5–32

Format: Hexadecimal

Specifies the initial session key for integrity secu-rity service for communication from this security agent to the peer security agent (side A of the connection). The initial session key cannot be 0.

Init Session Key B Default: 0

Range: 5–32

Format: Hexadecimal

Specifies the initial session key for integrity secu-rity service for communication from the peer security agent to this security agent (side B of the connection). The initial session key cannot be 0.

SKU Time Interval Default: No-Auto-matic-SKU

Range: N/A

Format: Predefined

Specifies the frequency of the session key update for integrity security service for communication from this security agent to the peer security agent.

No-Automatic-SKU Indicates that the session key update will be per-formed only by executing a manual command.

Hourly Indicates that the session key will be updated automatically once per hour.

Daily Indicates that the session key will be updated automatically once per day.

Weekly Indicates that the session key will be updated automatically once per week.

Table 9-1. ATM PNNI SVCC RCC Security Configuration Window Field Descriptions (Continued)


9-4 255-700-762R11.1



Confidentiality Security Service PanelNote: The fields on this panel are displayed only when you select one of the following service profiles in the Service Profile field:

• Integrity-Confidentiality-172

• Integrity-Confidentiality-ReplayReorderProtection-172

Encryption Algo-rithm

Default: AES-128-CBC

Range: N/A

Format: Predefined

Specifies the type of encryption algorithm used for confidentiality security service is used.

AES-128-CBC Indicates that the AES-CBC algorithm with a key length of 128 bits is used.


AES-256-192-CBC Indicates that the AES-CBC algorithm with a key length of 256 bits is used.

Triple-DES-192-CBC

Indicates that the triple-DES-CBC algorithm with a key length of 192 bits is used.


Range: 5–32

Format: Hexadecimal

Specifies an initial session key for confidentiality security service for communication from this security agent to peer security agent. The initial session key cannot be 0.


Range: 5–32

Format: Hexadecimal

Specifies the initial session key for confidentiality security service for communication from peer security agent to this security agent. The initial session key cannot be 0.


Range: N/A

Format: Predefined

Specifies the frequency of the session key update for confidentiality security service for communi-cation from this security agent to the peer secu-rity agent.







255-700-762R11.1 9-5



Viewing PNNI SVCC RCC Information

To view PNNI SVCC RCC and ATM security information, perform the steps in the following procedure.

Begin

1 On the PNNI tab, select SVCC RCC Information from the right-click menu, and the View PNNI SvccRcc Table window appears (see Figure 9-2).



The VIEW PNNI Svcc Rcc Information page appears (see Figure 9-3).

Admin Status Default: OutOfSer-vice

Range: N/A

Format: Predefined

Displays the operational status of the ATM secu-rity agent.

OutOfService Indicates that the ATM security agent is out of service.

InService Indicates that the ATM security agent is in ser-vice.



Figure 9-2. View PNNI SvccRcc Table Window

Button Function




9-6 255-700-762R11.1



The fields on this page are described in Table 9-2.

End

Figure 9-3. PNNI SvccRcc Information Page

Table 9-2. PNNI SVCC RCC Information Window Field Descriptions


Node Index Default: 0

Range: 1–400

Format: Numeric

Displays the node index identifies a logical PNNI entity in the PSAX system.

SvccRcc Index Default: 0

Range: 1–65535

Format: Numeric

Displays the 5-digit switched virtual channel con-nection routing control channel (SvccRcc) index number.

SvccRcc Version Default: Version1point0

Range: N/A

Format: Predefined

Displays the PNNI version 1.0 routing protocol that is used to exchange information with the neighbor node.

SvccRcc Hello State Default: TwoWayIn-side

Range: N/A

Format: Predefined

Displays the state of the Hello protocol exchange over the SVCC-based RCC.

Remote Node ID Default: 0

Range: N/A

Format: 11-octet remote node address identifier

Displays the remote node where the SVCC-based RCC terminates.

255-700-762R11.1 9-7



Viewing PNNI SVCC RCC Statistics

Begin

1 Continuing from the previous section, “Viewing PNNI SVCC RCC Infor-mation”, click the ATM Security Statistics tab on the VIEW PNNI Svcc Rcc Information page.

The ATM Security Statistics- Routing SVC page appears (see Figure 9-4).

Remote ATM Address

Default: 0

Range: N/A

Format: 10-octet address of remote ATM device

Displays the ATM end system address where the SVCC establishment was attempted.


Range: N/A

Format: Numeric

Indicates the interface from which the SVCC-based RCC leaves the PSAX system. If the SVCC-based RCC has not been established, the default value is displayed.

Received Hellos Default: 0

Range: N/A

Format: Numeric

Displays the number of received Hello packets over this SVCC-based RCC.

Transmitted Hellos Default: 0

Range: N/A

Format: Numeric

Displays the number of transmitted Hello packets over this VCC-based RCC.

VPI Default: 0

Range: N/A

Format: Numeric

Indicates the VPI used at the interface from which the SVCC-based RCC leaves the PSAX sys-tem. If the RCC has not been established, the default value is displayed.

VCI Default: 0

Range: N/A

Format: Numeric

Indicates the VCI used at the interface from which the SVCC-based RCC leaves the PSAX sys-tem. If the RCC has not been established, the default value is displayed.

Table 9-2. PNNI SVCC RCC Information Window Field Descriptions (Continued)


9-8 255-700-762R11.1




The fields on this page are described in Table 9-3.

2 On the ATM Security Statistics page, click Close.

3 On the View PNNI SvccRcc Table window, click Close.

End

Figure 9-4. ATM Security Statistics - Routing SVC Page

Button Function

Update Session Key for Integ-rity Service

Requests a session key update for integrity security services.

Update Session Key for Confi-dentiality Service

Requests a session key update for confidentiality security services

Update Updates the information in the fields.

Clear Removes the values in this window and resets them to 0.

Poll Poll+ initiates the continuous update of statistics. Poll- sus-pends polling.

255-700-762R11.1 9-9



Table 9-3. ATM PNNI SVCC RCC Security Statistics Window Field Descriptions


Slot Default: N/A

Range: Depends on chassis type

Format: Numeric

Specifies the slot number containing the module, which contains the interface for which ATM security is being configured.

Port Default: N/A

Range: Depends on module type

Format: Numeric

Specifies the port number of the module for which the ATM security is being configured.



Format: Numeric

Specifies the channel number for the module port for which the ATM security is being config-ured.

VPI Default: N/A

Range: 0–255 (ATM UNI); 0–4095 (ATM NNI)

Format: Numeric

Displays the virtual path identifier for the con-nection associated with the interface for which ATM security is being configured.

VCI Default: N/A

Range: 32–65535

Format: Numeric

Displays the virtual channel identifier associated with the virtual path identifier for the connection associated with the interface for which ATM security is being configured.

Security Agent State

Default: Null

Range: N/A

Format: Predefined

Displays the current state of the ATM security agent.

Null Indicates that the ATM security agent for a PVC or SVC is not configured or it is configured with the service profile No-Security-Service.

Unavailable Indicates that the interface and the ATM security agent for a PVC or SVC are configured, but the ATM security agent has not yet received an Establish Confirmation or an Establish Indication (in case of preconfiguration), or the security negotiation through the security message exchange protocol is not yet initiated.

Unsecured Indicates that the interface and ATM security agent for a PVC or SVC are configured, but the security negotiation process through the security message exchange protocol has been initiated but not finished.

Secure Indicates that the interface and ATM security agent for a PVC or SVC are configured, and the security negotiation process through the security message exchange protocol has been initiated and finished.

9-10 255-700-762R11.1



Integrity Current Session Key A Timer

Default: 0

Range: N/A

Format: Numeric

Displays the number of minutes since the session key for integrity security service for communica-tion from this side (side A) to the peer side (side B) of the connection was last updated.

Integrity Current Session Key B Timer

Default: 0

Range: N/A

Format: Numeric

Displays the number of minutes since the session key for integrity security service for communica-tion from the peer side (side B) to this side (side A) of the connection was last updated.

Confidentiality Current Session Key A Timer

Default: 0

Range: N/A

Format: Numeric

Displays the number of minutes since the session key for confidentiality security service for com-munication from this side (side A) to the peer side (side B) of the connection was last updated.

Confidentiality Current Session Key B Timer

Default: 0

Range: N/A

Format: Numeric


SDU Sent Default: 0

Range: N/A

Format: Numeric

Displays the number of service data units sent to the upper layer.

SDU Received Default: 0

Range: N/A

Format: Numeric

Displays the number of service data units received from the lower layer

SDU Bad MAC Default: 0

Range: N/A

Format: Numeric

Displays the number of service data units received from the lower layer with an incorrect message authentication code.

SDU Bad Sequence Number

Default: 0

Range: N/A

Format: Numeric

Displays the number of service data units received from the lower layer with the wrong sequence number.

SKU OAM Cells Sent

Default: 0

Range: N/A

Format: Numeric

Displays the number of total OAM session key update cells sent by this security agent.

SKU OAM Cells Received

Default: 0

Range: N/A

Format: Numeric

Displays the number of total OAM session key update cells received by this security agent

SKU OAM Cells Discarded

Default: 0

Range: N/A

Format: Numeric

Displays the number of OAM session key update cells discarded by this security agent.

Duplicate SKU OAM Cells with Mismatched Keys

Default: 0

Range: N/A

Format: Numeric

Displays the number of mismatched session keys in duplicate session key exchange OAM cells.

Table 9-3. ATM PNNI SVCC RCC Security Statistics Window Field Descriptions (Continued)


255-700-762R11.1 9-11


Chapter 9 Configuring ATM SecurityEnabling ATM Security

Enabling ATM SecurityBefore you can configure ATM security parameters, you must enable ATM Security on the Feature Turn On/Off page.

Begin





3 In the Feature On/Off Configuration panel, select the AtmSec row.


5 To enable the ATM security feature, select Turn On Selected Feature (if the feature is already enabled, this option will not be selectable). The fol-lowing window appears (see Figure 9-7).



9-12 255-700-762R11.1


Chapter 9 Configuring ATM SecurityConfiguring ATM Security on the ATM UNI Interface


7 Reboot the PSAX device so that the values you selected will take effect.

End

Configuring ATM Security on the ATM UNI InterfaceThis section describes how to configure ATM security parameters on the ATM UNI interface.

Configuring a Signaling PVC

Begin

1 From the ATM UNI Interface Configuration window, click the ATM Secu-rity tab.


255-700-762R11.1 9-13



The Signaling PVC page appears (see Figure 9-8).

The buttons on this window (not shown in Figure 9-8) have the following functions:

Figure 9-8. Signaling PVC Page Window

Button Function

Create Establishes the connection you configured.

Delete Deletes an out-of-service interface and redisplays the Port and Channel Configuration window for the module you are configur-ing.

You must first take interface out of service (by clicking Take Out of Service) before you can use this button.


9-14 255-700-762R11.1




3 Click Create > Bring Into Service.

End

Bring Into Service Displays when the Administrative Status field is OutOfService. Brings an out-of-service configured interface to in-service status. The value InService appears in the Administrative Status field.

You must first configure the interface before you can use this but-ton.

Take Out of Service Displays when the Administrative Status field is InService. Takes an in-service configured interface to out-of-service status. The value OutOfService appears in the Administrative Status field.

You must use this button first before clicking the Delete.

Button Function

Table 9-4. ATM UNI Interface ATM Security Signaling PVC Configuration Page Field Descriptions


Slot Default: N/A


Format: Numeric


Port Default: N/A


Format: Numeric




Format: Numeric


VPI Default: N/A


Format: Numeric


VCI Default: N/A

Range: 32–65535

Format: Numeric


255-700-762R11.1 9-15




Range: N/A

Format: Predefined


Integrity-172 Indicates that the integrity security service with-out replay/reordering protection will be provided to this connection.


Indicates that the integrity security service and confidentiality security service without replay/reordering protection will be provided to this connection.


Indicates that the integrity security service with replay/reordering protection will be provided to this connection.




Range: 40–256




Range: N/A

Format: Hexadecimal

Specifies the master key that is shared between two peer security agents for integrity and/or con-fidential security services.

[SKU Encryption Algorithm]

Default: MD5

Range: N/A

Format: Predefined

Displays the encryption algorithm used for encrypting session keys that need to be for-warded from this security agent to the peer secu-rity agent for this interface.

MD5 Indicates that the encryption algorithm used on this interface will be MD5.

SHA-1 Indicates that the encryption algorithm used on this interface will be SHA-1.



Range: N/A

Format: Predefined




Table 9-4. ATM UNI Interface ATM Security Signaling PVC Configuration Page Field Descriptions (Continued)


9-16 255-700-762R11.1




Range: 40–256

Format: Predefined



Range: N/A

Format: Hexadecimal



Range: N/A

Format: Hexadecimal



Range: N/A

Format: Predefined











Range: N/A

Format: Predefined





Triple-DES-192-CBC




255-700-762R11.1 9-17



Viewing Signaling PVC Statistics

After creating a signaling PVC (under the ATM Security tab), you can view its statistics.

1 From the ATM UNI Interface Configuration window, click the ATM Secu-rity tab.


2 Click the Signaling PVC Stats tab.


Range: N/A

Format: Hexadecimal

Specifies the initial session key for confidentiality security service for communication from this security agent to the peer security agent (side A of the connection). The initial session key cannot be 0.


Range: N/A

Format: Hexadecimal

Specifies the initial session key for confidentiality security service for communication from the peer security agent to this security agent (side B of the connection). The initial session key cannot be 0.


Range: N/A

Format: Predefined







Range: N/A

Format: Predefined






9-18 255-700-762R11.1



The Signaling PVC Stats page appears (see Figure 9-9).

The buttons on this window (some of which are not shown in Figure 9-9) have the following functions:

The values for the fields on this window are described in Table 9-5.

Figure 9-9. Signaling PVC Stats Page Window

Button Function








255-700-762R11.1 9-19




End

Table 9-5. ATM UNI Interface ATM Security Statistics - Signaling PVC Window Field Descriptions


Slot Default: N/A


Format: Numeric


Port Default: N/A


Format: Numeric




Format: Numeric


VPI Default: N/A


Format: Numeric


VCI Default: N/A

Range: 32–65535

Format: Numeric


9-20 255-700-762R11.1




Default: Null

Range: N/A

Format: Predefined







Default: 0

Range: N/A

Format: Numeric



Default: 0

Range: N/A

Format: Numeric



Default: 0

Range: N/A

Format: Numeric



Default: 0

Range: N/A

Format: Numeric


SDU Sent Default: 0

Range: N/A

Format: Numeric



Range: N/A

Format: Numeric


Table 9-5. ATM UNI Interface ATM Security Statistics - Signaling PVC Window Field Descriptions (Continued)


255-700-762R11.1 9-21


Chapter 9 Configuring ATM SecurityConfiguring ATM Security on the ATM PNNI Interface

Configuring ATM Security on the ATM PNNI InterfaceThis section describes how to configure ATM security parameters on the ATM PNNI interface.

Configuring a Signaling PVC

Begin

1 From the ATM PNNI Interface Configuration window, click the ATM Security tab.



Range: N/A

Format: Numeric



Default: 0

Range: N/A

Format: Numeric


SKU OAM Cells Sent

Default: 0

Range: N/A

Format: Numeric



Default: 0

Range: N/A

Format: Numeric



Default: 0

Range: N/A

Format: Numeric



Default: 0

Range: N/A

Format: Numeric


Table 9-5. ATM UNI Interface ATM Security Statistics - Signaling PVC Window Field Descriptions (Continued)


9-22 255-700-762R11.1




Figure 9-10. Signaling PVC Page

Button Function





255-700-762R11.1 9-23





End





Button Function

Table 9-6. ATM PNNI Interface ATM Security Configuration - Signaling PVC Page Field Descriptions


Slot Default: N/A


Format: Numeric


Port Default: N/A


Format: Numeric




Format: Numeric


VPI Default: N/A


Format: Numeric


VCI Default: N/A

Range: 32–65535

Format: Numeric


9-24 255-700-762R11.1




Range: N/A

Format: Predefined










Range: 40–256




Range: N/A

Format: Hexadecimal


SKU Encryption Algorithm

Default: MD5

Range: N/A

Format: Predefined






Range: N/A

Format: Predefined




Table 9-6. ATM PNNI Interface ATM Security Configuration - Signaling PVC Page Field Descriptions (Continued)


255-700-762R11.1 9-25




Range: 40–256

Format: Predefined



Range: N/A

Format: Hexadecimal



Range: N/A

Format: Hexadecimal



Range: N/A

Format: Predefined











Range: N/A

Format: Predefined





Triple-DES-192-CBC




9-26 255-700-762R11.1



Viewing Signaling PVC Statistics

After creating a signaling PVC (under the ATM Security tab), you can view its statistics.

1 From the PNNI Interface Configuration window, click the ATM Security tab.


2 Click the Signaling PVC Stats tab.


Range: N/A

Format: Hexadecimal



Range: N/A

Format: Hexadecimal



Range: N/A

Format: Predefined







Range: N/A

Format: Predefined






255-700-762R11.1 9-27



The Signaling PVC Stats page appears (see Figure 9-9).



Figure 9-11. Signaling PVC Stats Page

Button Function








9-28 255-700-762R11.1




End

Table 9-7. ATM PNNI Interface ATM Security Statistics - Signaling PVC Window Field Descriptions


Slot Default: N/A


Format: Numeric


Port Default: N/A


Format: Numeric




Format: Numeric


VPI Default: N/A


Format: Numeric


VCI Default: N/A

Range: 32–65535

Format: Numeric


255-700-762R11.1 9-29




Default: Null

Range: N/A

Format: Predefined







Default: 0

Range: N/A

Format: Numeric



Default: 0

Range: N/A

Format: Numeric



Default: 0

Range: N/A

Format: Numeric



Default: 0

Range: N/A

Format: Numeric


SDU Sent Default: 0

Range: N/A

Format: Numeric



Range: N/A

Format: Numeric


Table 9-7. ATM PNNI Interface ATM Security Statistics - Signaling PVC Window Field Descriptions (Continued)


9-30 255-700-762R11.1



Configuring a Routing PVC

Begin

1 From the ATM PNNI Interface Configuration window, click the ATM Security tab.


Range: N/A

Format: Numeric



Default: 0

Range: N/A

Format: Numeric


SKU OAM Cells Sent

Default: 0

Range: N/A

Format: Numeric



Default: 0

Range: N/A

Format: Numeric



Default: 0

Range: N/A

Format: Numeric



Default: 0

Range: N/A

Format: Numeric


Table 9-7. ATM PNNI Interface ATM Security Statistics - Signaling PVC Window Field Descriptions (Continued)


255-700-762R11.1 9-31



The Routing PVC page appears (see Figure 9-12).


Figure 9-12. Routing PVC Page

Button Function





9-32 255-700-762R11.1





End





Button Function

Table 9-8. ATM PNNI Interface ATM Security Configuration - Routing PVC Page Field Descriptions


Slot Default: N/A


Format: Numeric


Port Default: N/A


Format: Numeric




Format: Numeric


[VPI] Default: N/A


Format: Numeric


[VCI] Default: N/A

Range: 32–65535

Format: Numeric


255-700-762R11.1 9-33




Range: N/A

Format: Predefined










Range: 40–256




Range: N/A

Format: Hexadecimal


[SKU Encryption Algorithm]

Default: MD5

Range: N/A

Format: Predefined






Range: N/A

Format: Predefined




Table 9-8. ATM PNNI Interface ATM Security Configuration - Routing PVC Page Field Descriptions (Continued)


9-34 255-700-762R11.1




Range: 40–256

Format: Predefined


InitSessKeyA Default: 0

Range: N/A

Format: Hexadecimal


InitSessKeyB Default: 0

Range: N/A

Format: Hexadecimal



Range: N/A

Format: Predefined











Range: N/A

Format: Predefined





Triple-DES-192-CBC




255-700-762R11.1 9-35



Viewing Routing PVC Statistics

After creating a routing PVC (under the ATM Security tab), you can view its statistics.

1 From the PNNI Interface Configuration window, click the ATM Security tab.

The Routing PVC page appears (see Figure 9-12).

2 Click the Routing PVC Stats tab.

InitSessKeyA Default: 0

Range: N/A

Format: Hexadecimal


InitSessKeyB Default: 0

Range: N/A

Format: Hexadecimal



Range: N/A

Format: Predefined







Range: N/A

Format: Predefined






9-36 255-700-762R11.1



The Routing PVC Stats page appears (see Figure 9-13).



Figure 9-13. Routing PVC Stats Page Window

Button Function








255-700-762R11.1 9-37




End

Table 9-9. ATM PNNI Interface ATM Security Statistics - Routing PVC Page Field Descriptions


Slot Default: N/A


Format: Numeric


Port Default: N/A


Format: Numeric




Format: Numeric


VPI Default: N/A


Format: Numeric


VCI Default: N/A

Range: 32–65535

Format: Numeric


9-38 255-700-762R11.1




Default: Null

Range: N/A

Format: Predefined







Default: 0

Range: N/A

Format: Numeric



Default: 0

Range: N/A

Format: Numeric



Default: 0

Range: N/A

Format: Numeric



Default: 0

Range: N/A

Format: Numeric


SDU Sent Default: 0

Range: N/A

Format: Numeric



Range: N/A

Format: Numeric




255-700-762R11.1 9-39



SDU with Bad MAC Default: 0

Range: N/A

Format: Numeric


SDU with Bad Sequence No

Default: 0

Range: N/A

Format: Numeric


SKU OAM Cells Sent

Default: 0

Range: N/A

Format: Numeric



Default: 0

Range: N/A

Format: Numeric



Default: 0

Range: N/A

Format: Numeric



Default: 0

Range: N/A

Format: Numeric




9-40 255-700-762R11.1


10 Using Diagnostics and UpgradingPSAX Components

Overview of This ChapterThis chapter explains how to use diagnostic tools for the PSAX devices and how to upgrade and backup PSAX devices using the EMS-PSAX.

Running System Diagnostics

Diagnostics Tab The Diagnostics tab contains the following pages as described in Table 10-1:

The data that appears on the Diagnostics page is static. To update the data, click Update.

Table 10-1. Page/Panel Descriptions for the Diagnostics Tab

Page/Panel Name Description of Tasks

Diagnostics Displays the CPU status, memory, and other system component information. Allows you to restart hardware compo-nents and switch CPUn modules.

OAM Loopback Test Performs OAM loopback tests.

OAM Activation - Deactivation

Configures activate or deactivate OAM functions.

Cell Test Determines whether a port is operating properly.

RTD / CLM Enables to measure end-to-end round trip time taken by the data cell on a given cir-cuit and the cell loss on a given circuit between two end points.

Module Connection Count

Displays the number of connections in a per module.


255-700-762R11.1 10-1

Chapter 10 Using Diagnostics and Upgrading PSAX ComponentsRunning System Diagnostics


Figure 10-1. Diagnostics Tab (Displaying Diagnostics Page)

Button Function

Restart Reboots the hardware components selected in the field to the right of this but-ton. For more information, see ”Restarting PSAX Device Hardware Components” on page 10-30.

Switchover to Backup CPU Changes the functioning of the PSAX device so that the primary CPUn module will be recognized as the standby CPUn module and vice versa. For more informa-tion, see ”Switching to the Standby CPUn Module” on page 10-32.

Remove Configuration Files Deletes the configuration data stored in the PSAX device. For more information, see ”Removing Configuration Files” on page 10-33.

10-2 255-700-762R11.1


Chapter 10 Using Diagnostics and Upgrading PSAX ComponentsViewing System Status

Viewing System StatusThe CPU Status panel on the Diagnostics page displays information about the active CPUn module in a PSAX device.

Perform the steps in the following procedure to view the status of the PSAX device.

Begin

1 Click the Diagnostics tab in the Device window.

The Diagnostics page appears (see Figure 10-1).

2 View the information about the CPUn module(s) in the CPU Status panel (see Figure 10-2).

The display-only fields on this window are described in Table 10-2.

Update Updates the values on the Diagnostics page to the latest values.

Poll Continuously updates the values on the Diagnostics page and changes the button label to Poll-.

Terminates polling and changes the but-ton label to Poll+.

Button Function

Figure 10-2. CPU Status Panel

255-700-762R11.1 10-3


Chapter 10 Using Diagnostics and Upgrading PSAX ComponentsViewing System Status

Table 10-2. CPU Status Panel Field Descriptions


System Software Version

Default: N/A

Range: N/A

Format: Predefined

Displays the version of the system software cur-rently running on the CPU.

System Time Default: N/A

Range: N/A

Format: Numeric (hours:minutes:sec-onds)

Displays the Universal Coordinated Time (UTC). This time value for the PSAX device is set on the Site-Specific page.

System Up Time Default: N/A

Range: N/A

Format: Numeric (hours:minutes:sec-onds)

Displays the amount of time the PSAX device has been running since the last time you applied power to the system, or booted (initialized) the CPU module.

Disk Space Free (Bytes) Disk Space Total (Kbytes)

Default: N/A

Range: N/A

Format: Numeric (kilobytes)

: Displays the amount of unused (available) sys-tem disk space in kilobytes on the CPU module.

Total(Bytes): Displays the amount of total system disk space in kilobytes on the CPU module.

Memory Free(Bytes) Mem-ory Total (Kbytes)

Default: N/A

Range: N/A


Free(Bytes): Displays the amount of unused (available) random access memory on the system disk of the CPU module.

Total(Bytes): Displays the amount of total ran-dom access memory on the system disk of the CPU module.

[Tx One Cell] Default: N/A

Range: N/A

Format: Numeric

Total: Displays the number of cells within the transmit-one-cell pool.

Used: Displays the number of cells currently being used within the transmit-one-cell pool.

High: Displays the high-water mark of cells used within the transmit-one-cell pool.

10-4 255-700-762R11.1


Chapter 10 Using Diagnostics and Upgrading PSAX ComponentsDisk and Memory Data

Disk and Memory DataThe Disk and Memory panel on the Diagnostics page displays data about the total and available memory and the disk space on the active CPUn module.

Perform the steps in the following procedure to view data about the disk space and memory of the active CPUn module.

Begin



2 View information about the disk and memory for the primary (active) CPUn module in the Disk and Memory panel (see Figure 10-3).

End

The fields on this display-only panel are described in Table 10-3.

[Rx One Cell] Default: N/A

Range: N/A

Format: Numeric

Total: Displays the number of cells within the receive-one-cell pool.

Used: Displays the number of cells currently being used within the receive-one-cell pool.

High: Displays the high-water mark of cells used within the receive-one-cell pool.

[Rx Multi Cell] Default: N/A

Range: N/A

Format: Numeric

Total: Displays the number of multiple cells within the receive-multicell-pool.

Used: Displays the number of multiple cells cur-rently being used within the receive-multicell-pool.

High: Displays the high-water mark of multicells used within the receive-multicell-pool.

[Message Pool] Default: N/A

Range: N/A

Format: Numeric

Total: Displays the total number of messages in the message pool.

Used: Displays the number of messages currently being used in the message pool.

High: Displays the high-water mark number of messages used in the message pool.

Table 10-2. CPU Status Panel Field Descriptions (Continued)


Figure 10-3. Disk and Memory Panel

255-700-762R11.1 10-5


Chapter 10 Using Diagnostics and Upgrading PSAX ComponentsBackplanes and Cell Bus Data

Backplanes and Cell Bus DataThe Backplanes and Cell Bus panel on the Diagnostics page displays informa-tion about the clock and cell circuits for the backplanes and data about errored received (RX) cells and misaligned cells.

Perform the steps in the following procedure to view data about the back-planes and cell bus data.

Begin



2 View the status of the backplanes and cell circuits in the Backplanes and Cell Bus panel (see Figure 10-4).

End


Table 10-3. Field Descriptions for the Disk and Memory Panel

Field Name Description

Disk Space(Free Kbytes)(display only)

Displays the amount of unused disk space on the active CPUn in kilobytes.

Memory(Free Kbytes)(display only)

Displays the amount of unused random access memory (RAM) on the active CPUn in kilobytes.

Disk Space(Total Kbytes)(display only)

Displays the amount of used and unused disk space on the active CPUn in kilobytes.

Memory(Total Kbytes)(display only)

Displays the amount of used and unused RAM on the active CPUn in kilobytes.

Figure 10-4. Backplanes and Cell Bus Panel

10-6 255-700-762R11.1


Chapter 10 Using Diagnostics and Upgrading PSAX ComponentsCell Buffers and Message Pool Data

Cell Buffers and Message Pool DataThe Cell Buffers and Message Pool panel on the Diagnostics page is used pri-marily by technical support personnel to diagnose problems.

Perform the steps in the following procedure to view cell buffers and message pool data about the active CPUn module.

Begin



2 View the information in the Cell Buffers and Message Pool panel (see Figure 10-5).


Operations Administration and Maintenance (OAM)For more information about OAM, see the appropriate PacketStar® PSAX Multiservice Media Gateway user guide.

Table 10-4. Field Descriptions for the Backplanes and Cell Bus Panel


Clock(display only)

Displays the status of the clock on one or more backplanes.

Cell Circuit(display only)

Displays the status of the cell circuits on one or more backplanes.

Errored (BIP 16) Rx Cells(display only)

Displays the number of errored cells received on one or more backplanes.

Misaligned Cells(display only)

Displays the number of misaligned cells received on one or more backplanes.

Figure 10-5. Cell Buffers and Message Pool Panel

255-700-762R11.1 10-7


Chapter 10 Using Diagnostics and Upgrading PSAX ComponentsOperations Administration and Maintenance (OAM)

Performing OAM Loopback Tests

Perform the steps in the following procedure to test OAM.

Begin



2 Click the OAM Loopback Test tab.

The OAM Loopback Table page appears (see Figure 10-6).

3 Within an area of the page without a displayed entry, right-click the mouse and a menu appears. Select Create.

The ADD OAM Loopback Table Entry window appears (see Figure 10-7).


Figure 10-6. OAM Loopback Test Page

Figure 10-7. ADD OAM Loopback Table Window

Button Function

Add Applies the values you enter in the this window.


10-8 255-700-762R11.1




Update Updates the fields in the OAM Statistics panel.

The test display update does not always keep pace with the actual PSAX device operation. Use this button to avoid misin-terpretation of test results.

Clear Resets the values in the OAM Statistics panel to zero (except the Loopback Status field).



Button Function

Table 10-6. OAM Loopback Window Field Descriptions


OAM Loopback Entry Panel

Slot Default: 1

Range: Depends on the chassis type

Format: Numeric

The module slot number of the ATM connection on which you want to perform the OAM loop-back test.

Port Default: 1

Range: Depends on the module type

Format: Numeric

The port number of the ATM connection on which you want to perform the OAM loopback test.

Channel Default: 1

Range: Depends on the module type

Format: Numeric

The channel number of the ATM connection on which you want to perform the OAM loopback test.

VPI Default: 0

Range:

Format: Numeric

The virtual path identifier of the ATM connec-tion.

VCI Default: 0

Range:

Format: Numeric

The virtual channel identifier of the ATM connec-tion. Must be zero for virtual path connections.

Loopback Location ID

Default: FFFF.FFFF.FFFF.FFFF.FFFF.FFFF

Range: N/A


The destination loopback location ID where the loopback must occur. This field is displayed only when Specific-Location is selected in the OAM Loopback Type field.

255-700-762R11.1 10-9



5 Click Apply Configuration.

The configuration you set is applied to the channel you selected.

6 To send a loopback cell, click Send Loopback Cell.

7 To update the fields in the Statistics panel, click Update.

8 To continuously update the statistics, click Poll-. To terminate polling, click Poll+.

9 To reset the statistics counters, click Clear.

End

OAM Activation and Deactivation

You can use the OAM Activation - Deactivation page to perform continuity checks on the circuit running between PSAX devices when the traffic is down.

Perform the steps in the following procedure to check OAM continuity.

Begin



2 Click the OAM Activation - Deactivation tab.

OAM Statistics Panel

Loopback Status Default: Inactive

Range: N/A

Format: Predefined

Active, Successful, Failure,Timed-out,Waiting-for-response

Indicates the current status of the loopback test.

Cells Transmitted Default: N/A

Range: N/A

Format: Numeric

Indicates the total number of loopback cells transmitted on the specified connection since the last reset.

Cells Received Default: N/A

Range: N/A

Format: Numeric

Indicates the number of loopback cells received correctly on the specified connection since the last reset.

Mismatch Count Default: N/A

Range: N/A

Format: Numeric

Indicates the number of times the cells received did not matched with the cells transmitted on the specified connection since the last reset.

Table 10-6. OAM Loopback Window Field Descriptions (Continued)


10-10 255-700-762R11.1



The OAM Activation - Deactivation page appears (see Figure 10-8).


The ADD OAM Activate & Deactivate Table Entry window appears (see Figure 10-9).


Figure 10-8. OAM Activation - Deactivation Page

Figure 10-9. ADD OAM Activate & Deactivate Table Entry Window

Button Function

Update Status

Updates the information in the Current Status panel.

255-700-762R11.1 10-11




Activate Starts the OAM test.

Deacti-vate

Terminates the OAM test.

Button Function

Table 10-7. OAM Activation-Deactivation Window Field Descriptions


Connection Interface Panel

Slot Default: 0


Format: Numeric

Specifies the module slot number of the ATM connection.

Port Default: 0


Format: Numeric

Specifies the port number of the ATM connec-tion.

Channel Default: 0


Format: Numeric

The channel number of the ATM connection.

VPI Default: 0

Range: 0–4095

Format: Numeric

Specifies the virtual path identifier of the ATM connection.

VCI Default: 0

Range: 0–65535

Format: Numeric

Specifies the virtual channel identifier of the ATM connection.

OAM Function Type

Default: Continuity-check

Range: N/A

Format: Predefined

Specifies the type of method for performing the OAM function.

Continuity-check Indicates that the OAM cells flow continuously throughout the length of a single connection is performed.

Pmbr-and-cc Indicates that forward performance monitor-ing/backward reporting and continuity checking is performed.

Pm-and-cc Indicates that forward performance monitoring and continuity checking is performed.

Fpm-and-br Indicates that forward performance monitor-ing/backward reporting is performed.

Fpm only Indicates that only forward performance moni-toring is performed.

10-12 255-700-762R11.1



Direction of Flow Default: Towards-near-end

Range: N/A

Format: Predefined

Specifies in which direction the OAM cells are transmitted.

Towards-near-end Indicates that OAM cells are transmitted only towards the near end of the connection.

Both-way Indicates that OAM cells are transmitted in both directions.

Towards-far-end Indicates that OAM cells are transmitted only towards the far end of the connection.

Flow Type Default: End-to-end

Range: N/A

Format: Predefined

Specifies the distance over which the OAM cells flow in this connection.

End-to-end Indicates that the OAM cells flow from one end of the connection to the other.

Segment Indicates that the OAM cells flow across only one segment of the connection.

Block Size A-B Default: 1024

Range: 128–32,768

Format: Predefined

Specifies the size of the block of OAM cells taken into consideration for performance monitoring in the A–B direction (from near end to far end of the connection).

Note: This field is displayed only when the selected value in the OAM Function Type field is a value other than Continuity-check, or the value Towards-far-end or Both-way is selected in the Direction of Flow field.

Size128 Indicates that the block size is 128 cells.



Size1024 Indicates that the block size is 1,024 cells.





Table 10-7. OAM Activation-Deactivation Window Field Descriptions (Continued)


255-700-762R11.1 10-13



Block Size B-A Default: 1024

Range: 128–32,768

Format: Predefined

Size128,Size256,Size512,Size1024,Size4098,Size8192,Size16384,Size32768

Specifies the size of the block of OAM cells taken into consideration for performance monitoring in the B–A direction (from far end to near end of the connection).

Note: This field is displayed only when the selected value in the OAM Function Type field is a value other than Continuity-check, or the value Towards-near-end or Both-way is selected in the Direction of Flow field.









Current Status Panel

Source Point ETE CC(display only)

Default: Deactivated

Range: N/A

Format: Predefined

Source point end-to-end continuity checking. Displays the current status of the request for con-tinuity checking of OAM cells from the source point end of the connection to the sink point end of the connection.

Deactivated Indicates that continuity checking is deactivated.

Activated Indicates that continuity checking is activated.

WaitActConfirm Indicates that continuity checking will be acti-vated pending activation confirmation by remote endpoint.

WaitDeactConfirm Indicates that continuity checking will be deacti-vated pending confirmation by remote endpoint.



10-14 255-700-762R11.1



Sink Point ETE CC(display only)


Range: N/A

Format: Predefined

Sink point end-to-end continuity checking. Dis-plays the current status of the request for conti-nuity checking of OAM cells from the source point end of the connection to the sink point end of the connection.

Deactivated Indicates that continuity checking is deactivated.

Activated Indicates that continuity checking is activated.

WaitActConfirm Indicates that continuity checking will be acti-vated pending activation confirmation by remote endpoint.

WaitDeactConfirm Indicates that continuity checking will be deacti-vated pending confirmation by remote endpoint.

Source Point ETE PM(display only)


Range: N/A

Format: Predefined

Source point end-to-end performance monitor-ing. Displays the current status of the request for performance monitoring of OAM cells from the source point end of the connection to the sink point end.

Deactivated Indicates that source point end-to-end perfor-mance monitoring is deactivated.

Activated Indicates that source point end-to-end perfor-mance monitoring is activated.

Sink Point ETE PM(display only)


Range: N/A

Format: Predefined

Sink point end-to-end performance monitoring. Displays the current status of the request for per-formance monitoring of OAM cells from the sink point end of the connection to the source point end.

Deactivated Indicates that sink point end-to-end performance monitoring is deactivated.

Activated Indicates that sink point end-to-end performance monitoring is activated.

Source Point ETE PMBR(display only)


Range: N/A

Format: Predefined

Source point end-to-end performance monitor-ing/backward reporting. Displays the current sta-tus of the performance monitoring/backward reporting activation/deactivation request at the source point.

Deactivated Indicates that source point segment performance monitoring/backward reporting is deactivated.

Activated Indicates that source point segment performance monitoring/backward reporting is activated.



255-700-762R11.1 10-15



Sink Point ETE PMBR(display only)


Range: N/A

Format: Predefined

Sink point end-to-end performance monitor-ing/backward reporting. Displays the current sta-tus of the performance monitoring/backward reporting activation/deactivation request at the sink point.

Deactivated Indicates that sink point segment performance monitoring/backward reporting is deactivated.

Activated Indicates that sink point segment performance monitoring/backward reporting is activated.

Source Point SEG CC(display only)


Range: N/A

Format: Predefined

Source point segment continuity checking. Dis-plays the current status of the source point’s seg-ment continuity check activation/deactivation request.

Deactivated Indicates that source point segment continuity checking is deactivated.

Activated Indicates that source point segment continuity checking is activated.

Sink Point SEG CC(display only)


Range: N/A

Format: Predefined

Sink point segment continuity checking. Displays the current status of the sink point’s segment continuity check activation/deactivation request.

Deactivated Indicates that sink point segment continuity checking is deactivated.

Activated Indicates that sink point segment continuity checking is activated.

Source Point SEG PM(display only)


Range: N/A

Format: Predefined

Specifies whether source point segment perfor-mance monitoring is active or not. The current status of the source point’s segment performance monitoring activation/deactivation request is dis-played.

Deactivated Indicates that source point segment performance monitoring is deactivated.

Activated Indicates that source point segment performance monitoring is activated.

Sink Point SEG PM(display only)


Range: N/A

Format: Predefined

Specifies whether sink point segment perfor-mance monitoring is active or not. The current status of the sink point’s segment performance monitoring activation/deactivation request is dis-played.

Deactivated Indicates that sink point segment performance monitoring is deactivated.

Activated Indicates that sink point segment performance monitoring is activated.



10-16 255-700-762R11.1



5 Click Activate to begin the test.

Source Point SEG PMBR(display only)


Range: N/A

Format: Predefined

Specifies whether source point segment perfor-mance monitoring/backward reporting is active or not. The current status of the source point’s segment forward performance monitoring/back-ward reporting for an activation/deactivation request is displayed.

Deactivated Indicates that source point segment performance monitoring/backward reporting is deactivated.

Activated Indicates that source point segment performance monitoring/backward reporting is activated.

Sink Point SEG PMBR(display only)


Range: N/A

Format: Predefined

Specifies whether sink point segment perfor-mance monitoring/backward reporting is active or not. The current status of the sink point’s seg-ment forward performance monitoring/backward reporting for an activation/deactivation request is displayed.

Deactivated Indicates that sink point segment performance monitoring/backward reporting is deactivated.

Activated Indicates that sink point segment performance monitoring/backward reporting is activated.

Result Last Req(display only)

Default: None

Range: N/A

Format: Predefined

Displays the reason for failure of the last activa-tion request on this connection from the local user.

None Indicates that no failure occurred or no reason for failure exists.

Denied Indicates that the OAM activation request is denied.

Timedout Indicates that the OAM activation request has been timed out.

Successful Indicates that the OAM activation request is suc-cessful.

BR Block Error(display only)

Default: 0

Range: 0–32768

Format: Numeric

Backward reporting of a block error on a perfor-mance monitoring connection.

BR Lost Inserted Cell(display only)

Default: 0

Range: 0–32768

Format: Numeric

Backward reporting of a lost inserted cell on a performance monitoring connection.

BR Mis Inserted Cell(display only)

Default: 0

Range: 0–32768

Format: Numeric

Backward reporting of a misinserted cell on a performance monitoring connection.



255-700-762R11.1 10-17


Chapter 10 Using Diagnostics and Upgrading PSAX ComponentsRunning Cell Test Diagnostics

6 Click Deactivate to terminate the test.

End

Running Cell Test DiagnosticsPerform the steps in the following procedure to determine whether a port is operating correctly.

Begin

1 In the Device window, click the Diagnostics tab.


2 Click the Cell Test tab.

The Cell Test page appears (see Figure 10-10).

Figure 10-10. Cell Test Page

10-18 255-700-762R11.1




3 To set up a connection for the port you want to test, select the values for the fields on the Connection Interface panel from the values given in Table 10-8.

4 Click Apply Payload.

5 In the Transmit Payload field, enter numbers in any sequence.

6 Click Apply Payload.

The values for the test payload are applied.

7 Click either Send Payload Once or Send Payload Continuously.

Button Function

Apply Connection Applies the connection with the values you set. This button is displayed on the Connection Interface panel.

Delete Connection Deletes the connection you set up in the Cell Test window. Click this button after you have sent a test payload by clicking the Send Payload Once button. This button is displayed on the Connection Interface panel only after you have sent a payload at least one time.

Poll+ or Poll- Poll+ initiates the continuous update of statistics and changes the button label to Poll-. Poll- suspends polling and changes the button label to Poll+.

This button is displayed on the Cell Test Statistics panel.

Reset Counters Sets the field values in the Cell Test Statis-tics panel to zero. This button is displayed on the Cell Test Statistics panel.

Apply PayLoad Applies the values you enter in the Trans-mit Payload field.

Reset Payload Sets the values in the Transmit Payload field to the last saved (applied) set of val-ues.

Send Payload Once Sends the payload one time.

Send Payload Continuously Sends the payload continuously 10 times per second.

Stop Test Stops a continuously running test and deletes the connection you set up on the Cell Diagnostics window. Press this button after you have sent a test payload by pressing the Send Payload Continu-ously button.

255-700-762R11.1 10-19



The protocol, cells transmitted or the cells received or both, depending on the type of flow you selected on the Cell Test window, are displayed in the Cell Test Statistics panel (see Figure 10-10).

The values for the fields on the Cell Test Statistics panel are described in Table 10-9.

End

Table 10-8. Connection Interface Panel Field Descriptions


Interface Default: Unconfig-ured

Range: N/A

Format: Predefined

Indicates the interface type configured on this channel. To run cell test diagnostics, use the value AtmUni4-0,AtmUni3-0, or AtmUni3-1.

Unconfigured Indicates that no interface has been applied to the channel.

AtmUni3-0 Indicates that the ATM UNI 3.0 interface is applied to the selected channel.



AtmIispUser Indicates that the ATM IISP User interface is applied to the selected channel.

AtmIispNetwork Indicates that the ATM IISP Network interface is applied to the selected channel.

AtmPnni1-0 Indicates that the ATMPNNI interface is applied to the selected channel.

CircuitEmulation Indicates that the Circuit Emulation interface is applied to the selected channel.

DbCirEm Indicates that the Dynamic Bandwidth Circuit Emulation interface is applied to the selected channel.

PriIsdnUser Indicates that the PRI ISDN User interface is applied to the selected channel.

PriIsdnNetwork Indicates that the PRI ISDN Network interface is applied to the selected channel.

TerminalEmulation Indicates that the Terminal Emulation interface is applied to the selected channel.


10-20 255-700-762R11.1


Chapter 10 Using Diagnostics and Upgrading PSAX ComponentsConfiguring RTD / CLM

Configuring RTD / CLMThe RTD / CLM feature helps to measure the end-to-end round trip time taken by the data in an ATM connection and to calculate the cell losses between two end points of an ATM connection. This section describes how to test an ATM connection for RTD and CLM.

Performing RTD / CLM Configuration

Perform the steps in the following procedure to configure RTD / CLM.

Begin



2 Click the RTD / CLM Test tab.

The RTD / CLM Table page appears (see Figure 10-12).


Figure 10-11. RTD / CLM Table Page

255-700-762R11.1 10-21



The ADD RTD / CLM Table Entry window appears (see Figure 10-12).


5 To apply the values for the fields, Click Add.


Figure 10-12. ADD RTD / CLM Table Entry Window

Button Function

Add Applies the values you enter in the this window.


Copy Displays the Copy RTD / CLM Configuration window.

Update Updates the fields in the Statistics panel.

The test display update does not always keep pace with the actual PSAX device operation. Use this button to avoid misin-terpretation of test results.

Clear Resets the values in the Statistics panel to zero.



10-22 255-700-762R11.1



Table 10-10. RTD / CLM Table Entry Window Field Descriptions


Slot Default: 0

Range: Depends on chassis

Format: Numeric

Displays the module slot number of the ATM connection for the RTD / CLM measurement.

Port Default: 0

Range: Depends on module

Format: Numeric

Displays the port number of the ATM connection for the RTD / CLM measurement.

Channel Default: 0


Format: Numeric

Displays the channel number of the ATM connection for the RTD / CLM measurement.

Interface Default: Uncon-figured

Range: N/A

Format: Pre-defined

Indicates the interface type configured on this channel. To run cell test diagnostics, use the value AtmUni4-0,AtmUni3-0, or AtmUni3-1.

Unconfigured Indicates that no interface has been applied to the channel.




AtmIispUser Indicates that the ATM IISP User interface is applied to the selected channel.

AtmIispNet-work

Indicates that the ATM IISP Network interface is applied to the selected channel.

AtmPnni1-0 Indicates that the ATMPNNI interface is applied to the selected channel.

CircuitEmula-tion

Indicates that the Circuit Emulation interface is applied to the selected channel.

DbCirEm Indicates that the Dynamic Bandwidth Circuit Emulation interface is applied to the selected channel.

PriIsdnUser Indicates that the PRI ISDN User interface is applied to the selected channel.

PriIsdnNetwork Indicates that the PRI ISDN Network interface is applied to the selected channel.

TerminalEmula-tion

Indicates that the Terminal Emulation interface is applied to the selected channel.

255-700-762R11.1 10-23



OperStatus(display only)

Default: InService

Range: N/A

Format: Pre-defined

Indicates whether conditions are currently affecting the operational status of this port.

OutOfService OutOfService Indicates that the interface is not operational.

InService InService Indicates that the interface is operational.

AdminStatus(display only)

Default: InService

Range: N/A

Format: Pre-defined

Indicates whether the interface is operational.


OutOfService Indicates that the interface is not operational.

VPI Default: 0

Range: Depends on the connection

Format: Numeric

Displays the virtual path identifier of the ATM connection.

VCI Default: 0


Format: Numeric

Displays the virtual channel identifier of the ATM connec-tion.

Right Panel - Statistics

[Oper Status] Default: Inactive

Range: N/A

Format: Pre-defined

Displays whether the operational status of the connection is inactive or active.

Inactive Indicates that the connection status is inactive.

Active Indicates that the connection status is active.

[Max Delay] Default: 00000

Range: N/A

Format: Numeric

Indicates the maximum round trip delay of an ATM cell on the circuit.

[Min Delay] Default: 0000

Range: N/A

Format: Numeric

Indicates the minimum round trip delay of an ATM cell on the circuit.

[Avg Delay] Default: 00000

Range: N/A

Format: Numeric

Indicates the average round trip delay of an ATM cell on the circuit.

[Lost Cells] Default: 0000

Range: N/A

Format: Numeric

Indicates the number of ATM cells lost on the circuit

[Aggregate Time (min’s)]

Default: 0000

Range: N/A

Format: Numeric

Indicates the aggregate time of the actions (round trip delay, Cell Loss and so on) performed on the circuit since the RTD / CLM feature is enabled in the module.

Table 10-10. RTD / CLM Table Entry Window Field Descriptions (Continued)


10-24 255-700-762R11.1



Copying RTD / CLM Configuration

The Copy button on the ADD RTD / CLM Table Entry window allows you to copy the RTD / CLM configuration to a range of connections, for a given module.

To copy the RTD / CLM configuration to a range of connections, perform the steps in the following procedure from the ADD RTD / CLM Table Entry win-dow.

Begin

1 In the ADD RTD / CLM Table Entry window, click Copy.

The Copy RTD / CLM Configuration window appears with the slot, port, and channel of the interface you selected (see Figure 10-13). Enter the Slot to which you wish the RTD / CLM configuration to be copied in the Slot, Port, and Channel fields as follows (see Figure 10-14).

2 In the Start At panel, choose the slot and port where the copying should begin.

The Stop At panel displays the selected slot where the copying should end. In the Stop At panel, choose the same slot and port that are selected in the Start At panel. You can also select a different port on the Stop At panel.

3 Click Copy.

The RTD / CLM configuration is copied to the range of connections you selected.

4 Click Close.

Note: When a Non-ATM interface or a wrong module is selected for copying the RTD / CLM configuration, the RTD / CLM copy func-tion will exit after reaching a maximum failure value of 100.

End

255-700-762R11.1 10-25




Figure 10-13. ADD RTD / CLM Table Entry Window

Figure 10-14. Copy RTD / CLM Configuration Window

Button Function


Copy Copies the RTD / CLM configuration to a range of connections.

10-26 255-700-762R11.1



Table 10-11. Copy RTD / CLM Configuration Window Field Descriptions


Slot Default: 0


Format: Numeric

Displays the starting module slot number of the ATM con-nection for the RTD / CLM configuration.

Port Default: 0


Format: Numeric

Displays the starting port number of the ATM connection for the RTD / CLM configuration.

Channel Default: 0


Format: Numeric

Displays the starting channel number of the ATM connec-tion for the RTD / CLM configuration.

VPI Default: 0


Format: Numeric


VCI Default: 0


Format: Numeric


Right Panel - Stop At Panel

Slot Default: 0


Format: Numeric

Displays the ending module slot number of the ATM con-nection for the RTD / CLM configuration.

Port Default: 0


Format: Numeric

Displays the ending port number of the ATM connection for the RTD / CLM configuration.

Channel Default: 0


Format: Numeric

Displays the ending channel number of the ATM connection for the RTD / CLM configuration.

255-700-762R11.1 10-27


Chapter 10 Using Diagnostics and Upgrading PSAX ComponentsDiagnostics for Module Connections

Diagnostics for Module ConnectionsThe Module Connection Count Table displays the number of connections per module. To view the Module Connection Count Table, perform the steps in the following procedure.

Begin



2 Click the Module Connection Count tab.

VPI Default: 0


Format: Numeric


VCI Default: 0


Format: Numeric


Disable traps during copy

Default: N/A

Range: N/A

Format: N/A

Displays the trap messages when the RTD / CLM configura-tion is copied. Select this option to disable the trap messages when the RTD /CLM configuration is copied.

Table 10-11. Copy RTD / CLM Configuration Window Field Descriptions (Continued)


10-28 255-700-762R11.1


Chapter 10 Using Diagnostics and Upgrading PSAX ComponentsDiagnostics for Module Connections

The Module Connection Count Table appears (see Figure 10-15).


The fields on this window are described in Table 10-12.

3 Click the Poll+ button to update the field values. Click Poll- to end the updates.

End

Figure 10-15. Module Connection Count Window

Button Description

Poll+ Continuously update the field values and changes the button label to Poll-.

Poll- Terminates polling and changes the button label to Poll+.

255-700-762R11.1 10-29


Chapter 10 Using Diagnostics and Upgrading PSAX ComponentsDiagnostics for PSAX Hardware Components

Diagnostics for PSAX Hardware ComponentsThe Restart Hardware Components panel enables both restarting of hardware components and switching from the primary CPUn module to the standby CPUn module (if present). This panel includes the Restart, Switchover To Backup CPU, and Remove Configuration Files buttons.

Restarting PSAX Device Hardware Components

Specific hardware components may need to be restarted for several reasons, including:

• When you want to revert to a saved configuration

• When a module is not adhering to its configuration

• When timing problems cannot be resolved automatically

• When firmware changes on a module

Perform the steps in the following procedure to reboot (initialize) one or more components in a PSAX device.

Note: Only a user with Administrator access privileges can restart hard-ware components.

Table 10-12. Module Connection Count Table Window Field Descriptions


Id Default: N/A


Format: Numeric

Displays the physical slot location of the module.

Input Default: N/A

Range: -1–2

Format: Numeric

Displays the count of input connections on the CPUn module.

Output Default: N/A

Range: -1–2

Format: Numeric

Displays the count of output connections on the CPUn mod-ule.

Output MCast Default: N/A

Range: -1–2

Format: Numeric

Displays the count of output multicast connections on the CPUn module.

I/O Input Default: N/A

Range: -1–2

Format: Numeric

Displays the count of input connections on the I/O module.

I/O Output Default: N/A

Range: -1–2

Format: Numeric

Displays the count of output connections on the I/O module.

I/O Output MCast Default: N/A

Range: -1–2

Format: Numeric

Displays the count of output multicast connections on the I/O module.

10-30 255-700-762R11.1



Begin



2 In the Restart Hardware Components panel, select the equipment that you want to restart from the pull-down menu (see Figure 10-16) and click Restart.

The following options are available for you to select from the pull-down menu next to the Restart button.

Figure 10-16. Restart Button

Table 10-13. Field Descriptions for the Restart Hardware Components Panel

Field Value Function

Slot Number, Module Name The I/O module you select will be reboo-ted. Clicking Restart while having this option selected is the equivalent to physically deinserting the selected module from and then reinserting it into the chassis.

All I/O Cards Reboots all I/O and server modules in the chassis, without affecting the CPUn mod-ule(s).This selection is the equivalent to physi-cally deinserting the modules from and then reinserting them into the chassis.

Entire Chassis Reboots the CPUn module (or modules), I/O and server modules in the chassis.This option removes the power from the chassis and then reapplies the power.

Backup CPU This option reboots (initializes) the backup (redundant) CPUn module, without affect-ing the primary CPUn module.

Primary CPU Reboots (reinitializes) the primary CPUn module in a PSAX 1000, 1250, 2300, or PSAX 4500 device.This option also reboots all I/O and server modules in the chassis, as instructed by the system software initialization process. In a system with redundant (two) CPUn modules, the primary CPUn module remains the primary CPUn module.

255-700-762R11.1 10-31



3 Click Restart.

A confirmation window appears (see Figure 10-17 and Figure 10-18).

4 Click Yes in the confirmation window to restart the hardware compo-nent. Click No to cancel.

End

Switching to the Standby CPUn Module

If the active CPUn module needs to be removed from the PSAX chassis for any reason, you can force a switchover to the standby CPUn module in a redundant PSAX device (that is, a device with more than one CPUn module module installed). The standby CPUn module then becomes the active CPUn module, and the active CPUn module becomes the standby CPUn module if it remains in the chassis.

Note: If the primary CPUn module failure occurs, the PSAX device auto-matically switches to use the standby CPUn module. Only a user with Administrator or Configurator access privileges can switch to the standby CPUn module in a PSAX device.

Perform the steps in the following procedure to switch to the standby CPUn module.

Begin



Figure 10-17. Restart Hardware Component Confirmation Window (Primary CPU Module)

Figure 10-18. Restart Hardware Component Confirmation Window (An I/O Module)

10-32 255-700-762R11.1



2 Click Switchover To Backup CPU on the Diagnostics page (see Figure 10-19).

If the device is a redundant system, a confirmation window appears (see Figure 10-20).

3 Click Yes.

A second window prompts you to save your current configuration.

4 Click OK if you wish to save the current configuration (that is, if you are not attempting to revert to a previous configuration) Otherwise, click No.

If the device is a nonredundant system, either of the following windows appear (see Figure 10-21).

End

Removing Configuration Files

Perform the steps in the following procedure to delete configuration files from a PSAX device.

Note: Only a user with Administrator or Configurator access privileges can delete configuration files from a PSAX device.

Begin



Figure 10-19. Switchover to Backup CPU Button

Figure 10-20. Switchover to Backup CPU Confirmation (Redundant PSAX Device)

Figure 10-21. Switchover to Backup CPU Message Window

255-700-762R11.1 10-33


Chapter 10 Using Diagnostics and Upgrading PSAX ComponentsSaving Configuration Values

2 In the Restart Hardware Components panel, click the Remove Configu-ration Files button.


3 Click Yes in the confirmation window to delete all configuration data from the PSAX device. Click No to cancel

End




PSAX System Software Upgrades and Maintenance

Before You Begin Upgrading PSAX System Software

Upgrading the system software on a PSAX device includes the following pre-requisites:

~ Ensuring that you have TCP/IP connectivity between the CPU module and the FTP server

~ Setting up the FTP server software on your management station

~ Specifying a source file on the FTP server from which the upgrade files are being downloaded

Figure 10-22. Remove Configuration Files Button

Figure 10-23. Remove Configuration Files Confirmation Window

10-34 255-700-762R11.1


Chapter 10 Using Diagnostics and Upgrading PSAX ComponentsPSAX System Software Upgrades and Maintenance

~ Specifying a source directory or CD from which the files will be down-loaded

~ Obtaining proper rights to the source directory to copy the files

~ Identify the correct path to the software upgrade files on the FTP server. This is your source file and directory.

~ Ensuring that you have a good connection between the FTP server and the destination CPU module. The upgrade can be done either over an Ethernet LAN or over an in-band connection.

~ Save your configuration files (select Device > Save PSAX Configuration from the EMS-PSAX Menu Bar)

System Maintenance Tab

To display the CPU Upgrade page (see Figure 10-24), click the System Main-tenance tab.


Figure 10-24. System Maintenance Tab (Displaying the CPU Upgrade Page)

Button Function

Start Transfer

Initiates the file transfer.

Abort Terminates the file transfer.

255-700-762R11.1 10-35



The CPU Upgrade page (see Figure 10-24) contains the following panels and fields as described in Table 10-14.

Upgrading the System Software

Perform the steps in the following procedure to upgrade the system software.

Begin

1 Click the System Maintenance tab.

The CPU Upgrade page appears (see Figure 10-24).

Reset Clicking this button prior to clicking Start Transfer results in the EMS-PSAX changing the read-write fields you typed in the FTP System Files panel to the values that existed before you made changes.

Upgrade Starts the software upgrade process.

Fallback Starts the process of reverting to the previous PSAX soft-ware version.

Transfer Config to Fallback

Retains the configuration files when a fallback (down-grade) is performed between minor versions of the same software release.

Set Auth Key

Applies the value entered in the Authentication Key field.

Table 10-14. CPU Upgrade Page Panel Descriptions

Panel/Field Name Description

FTP System Files Indicates the source and destination of an FTP file transfer. This transfer downloads files that are used to upgrade the CPU software.

Transfer Status Displays the status of the file transfer.

Error Status Displays messages about errors that occur dur-ing the file transfer.

Upgrade System Software

Displays the current, upgrade, and fallback versions of the CPU software.

Upgrade Status Displays the status of the upgrade or fallback during this procedure.

Upgrade Progress Displays the progress of the upgrade or fallback during this procedure.

Button Function

10-36 255-700-762R11.1



2 In FTP System Files panel of the CPU Upgrade page (see Figure 10-25), enter data in the fields as described in Table 10-15. Use the left mouse button to move between the fields.

The display-only fields on the Upgrade System Software panel (see Figure 10-27) are described in Table 10-16.

3 In the FTP System Files panel of the CPU Upgrade page, click Start Transfer.

The file transfer process begins.

The percentage of the process that is complete appears in the Transfer Status field (see Figure 10-25) and in the Log tab. One of the following error messages will appear in the Error Status field and the Log tab:

~ None

~ UserAbort

~ InvalidIpAddress,

~ InvalidAccountName

~ InvalidAccountPassword

~ InvalidCdromFile

~ LibraryCRCFail

Table 10-15. Field Descriptions for the FTP System Files Panel


Host IP Address Enter the address for the FTP server from which the new software will be obtained, which is the "source"

Account Name Enter the correct account name to access the FTP server

Password Enter the password to access the FTP server

CD-ROM File Path Enter the correct path to the FTP source file for the upgrade information (directorypath/upgrade.lib)

License Key Note: This field is not currently supported.

Transfer Status Displays the percentage of the transfer that is completed

Error Status Displays problems that occurred during the transfer

Table 10-16. Field Descriptions for the Upgrade System Software Panel

Field Description

Current Version The version of software currently active on the CPU module.

Upgrade Version The version of software most recently transferred to the CPU module using FTP, to which you can upgrade.

Fallback Version The version of software previously transferred to the CPU module using FTP, to which you can downgrade.

Authentication Key

Upgrade Status Displays messages about events that occur during the upgrade

Upgrade Progress Displays messages about the progress of the upgrade

255-700-762R11.1 10-37



~ UnableToOpenLibraryFile

~ UnableToLoadLibraryModule

~ UnableToFindTaskSymbolName

~ FailureInSpawningTask

~ FailureInCreatingMsgQ

~ FailureInCopyingDataFiles

~ FailureToRemoveNextTree

~ UnableToMakeNextTree

~ UnableToOpenFile

~ UnableToMakeFtpConnection

~ UnableToWriteFile

~ unableToCompleteFtp

~ FileCRCFail

~ UnableToWritePackageList

~ TaskSuspendOrDead

~ UnableToUpdateBackup

10-38 255-700-762R11.1



~ CpuAbort

If the file transfer was successful with no errors, the Transfer Status and Error Status fields will display confirmation messages (see Figure 10-26).

4 For a redundant system (a PSAX device with two CPU modules installed), do the following when you receive these messages indicating a successful file transfer in the Upgrade System Software panel of the CPU Upgrade page:

a. Select Device > Save PSAX Configuration from the EMS-PSAX Menu Bar.

Note: Do not click Upgrade (or Fallback, if reverting to an older soft-ware version) at this time.

Figure 10-25. FTP System Files Panel (System Upgrade 100% Completed)

Figure 10-26. Upgrade Done Successfully

255-700-762R11.1 10-39



Wait for the standby CPU module to come back into service before pro-ceeding.

Note: If you save the device configuration, the standby CPU module is taken out of service while SPVC retention is done. While the standby CPU module is out, you cannot upgrade the switch.

b. Click Upgrade (or Fallback, if reverting to an older software ver-sion).

5 For a nonredundant system, when you receive messages indicating a successful file transfer in the Upgrade System Software panel of the CPU Upgrade page, click Upgrade (or Fallback, if reverting to an older soft-ware version).

A window appears (see Figure 10-27), prompting you to confirm the upgrade.

6 Click Yes.

If your EMS-PSAX configuration has unsaved modifications, a window will appear (see Figure 10-28), prompting you to save the configuration.

7 Click No if you have a redundant system. Click Yes if you have a nonre-dundant system.

If you click Yes, the EMS-PSAX begins rebooting the device and saving the configuration files.

Figure 10-27. Upgrade System Software Panel (Displaying Upgrade Device Confirmation Window)

Figure 10-28. Save Configuration Files Confirmation Window

10-40 255-700-762R11.1



The Device Reboot Status window appears (see Figure 10-29).

8 Click OK.

During the device reboot, the Upgrade Status and Upgrade Progress fields on the Upgrade System Software panel display both error messages (if any) and progress of process messages (see Figure 10-30).

Standby means the device is in a reboot state and no communication can be made to the device. Any actions performed will not work until the device is finished booting and communication has been reestablished.

Once the upgrade is complete, the Upgrade Status and Upgrade Progress fields on the Upgrade System Software panel display the messages as shown in Figure 10-31. The new software release number is displayed in both the Upgrade Version field on the Upgrade System Software panel, and in the System Software Version field on the panel of the Diagnostics page.

End

Reverting to a Previous CPU Software Version

To revert to the previous version of the PSAX system software, perform the steps in the following procedure.

! CAUTION:Use the fallback procedure only after discussing the issue with your PSAX technical support personnel. Data may be lost because the PSAX CPU software reverts to the last saved settings before the upgrade.

Figure 10-29. Device Reboot Status Window

Figure 10-30. Upgrade Status—Standby

Figure 10-31. Upgrade Successfully Completed

255-700-762R11.1 10-41



Begin

1 Click the System Maintenance tab on the Device window.


2 In the System Maintenance tab, click Fallback. A prompt appears (see Figure 10-32), asking you to confirm that you want to revert to the pre-vious version of software.

3 Click Yes to fall back the previous version of the software. Click No to retain the current version of the software.

End

Upgrading Firmware

The System Maintenance tab also contains the Firmware Upgrade page (see Figure 10-33). Use this window when Lucent Technologies changes the firm-ware that runs on the various modules in a PSAX device.

The Firmware Upgrade page is used for PSAX systems running system soft-ware release 6.0.0 and higher. This window is used when there is a new soft-ware and firmware load to which users can upgrade. This enables local or remote upgrades of the firmware loaded on the modules. You no longer need to physically replace erasable programmable read-only memory chips (EPROMs) to upgrade modules.

Firmware Drivers In PSAX devices, the firmware driver is a binary file that is automatically downloaded from the system software resident on the CPU module to the I/O module or server, is used to initialize the module. The default driver and the nondefault (configurable) driver are the two types of drivers you can choose from (although on some I/O and server modules, only one type of driver is available).

Note: Lucent recommends that you use the default driver unless you know which specific driver to select. The default driver contains the most current version of the firmware.

The PSAX device selects only the default driver when the I/O or server mod-ule initializes for the first time. When selecting the version of the firmware you want to download to the module, the drivers displayed represent the only downloadable versions for the module highlighted under the Module Type field.

Figure 10-32. Sample Fallback Confirmation Window

10-42 255-700-762R11.1



During the upgrade of PSAX system software or a firmware patch, one of three scenarios can occur, depending on which driver you initially select. The three scenarios are described as follows:

• If you select the default driver on the Firmware Upgrade page, and you upgrade the system software to a version that has both types of drivers, the system will upgrade the driver to the next version of the default driver, because that is the type of driver you initially chose.

• If you select the nondefault driver on the Firmware Upgrade page, and you upgrade the system software to a version that has both types of drivers, the system will upgrade the driver to the next version of the nondefault driver, because that is the type of driver you initially chose.

• If you select either type of driver on the Firmware Upgrade page, and you upgrade the system software to a version that offers only one type of driver upgrade, the system will upgrade the driver to the one available driver, even if you did not originally select that type of driver before the upgrade.

Selecting Firmware Drivers

You can select either a default driver or a nondefault driver from the list of available drivers:

~ If you select the default driver, you can install any I/O or sever module into the slot.

~ If you select a nondefault driver, you can install only the particular I/O or server module into the slot that is meant for this driver. If you install an I/O or server module that was not meant for this driver, the message wrongcardtype is displayed at the bottom of the Firmware Version Control window.

The PSAX system attempts to download the driver for this I/O or server mod-ule for approximately six minutes. The PSAX device will recognize the I/O or server module automatically when you install the configured I/O or server module during the download time (six minutes). If the correct I/O or server module is not installed during the download time, you must click Upgrade on the Firmware Upgrade page.

Note: If you wish to install an I/O or server module other than the I/O or server module with a non-default driver in any particular slot, you must select the default driver in that slot, and click Upgrade on the Firmware Upgrade page. The new I/O or server module you have installed will appear on the Firmware Upgrade page.

Upgrading Firmware on I/O and Server Modules

To upgrade firmware on I/O and server modules, perform the steps in the fol-lowing procedure.

Begin

1 Click the System Maintenance tab on the Device window.


2 Click the Firmware Upgrade tab.

255-700-762R11.1 10-43



The Firmware Upgrade page appears (see Figure 10-33).

The I/O and server modules in this PSAX device are displayed in the Firm-ware Version Control Table panel.


In the Firmware Upgrade panel, the Slot, Current Firmware Version, and Firmware Download Status fields are display-only fields that reflect whatever entry is selected on the Firmware Version Control Table panel. These fields are described in Table 10-17.

Figure 10-33. Firmware Upgrade Page

Button Function

Upgrade Starts the firmware upgrade process.

Reset Sets the values back to their previous state.

10-44 255-700-762R11.1



Table 10-17. Firmware Upgrade Panel Field Descriptions


Slot (display only)

Default: N/A

Range: chassis dependent

Format: Numeric

Displays the chassis slot in which the I/O or server module is installed.

Module(display only)

Default: N/A

Range: N/A

Format: Predefined

Displays the name of the I/O or server module in the slot.

Current Firm-ware Version(display only)

Default: N/A

Range: dependent on installed soft-ware version

Format: Predefined

Displays the version of the firmware currently loaded on this module. The first four characters of the driver file-name correspond to the firmware release number (FRN) in hexadecimal format, and the last four characters corre-spond to the checksum in hexadecimal format.

Note: An asterisk (*) after the driver filename indicates the default version of the driver for this module.

Next Firmware Version(display only)

Default: N/A

Range: dependent on installed soft-ware version

Format: Predefined

Displays the version of the firmware you select to down-load to the module. The first four characters of the driver filename correspond to the firmware release number (FRN) in hexadecimal format, and the last four characters correspond to the checksum in hexadecimal format.

Select the firmware driver you want to download to the I/O and server module(s).

Note: An asterisk (*) after the driver filename indicates the default version of the driver for this module.

Firmware Down-load Command Type

Default: N/A

Range: N/A

Format: Predefined

Displays the type of firmware download action the PSAX system performed on the firmware driver currently dis-played in the Curr Ver field.

None Indicates that no firmware driver downloading has taken place.

normalDownload Indicates that the firmware driver displayed in the Curr Ver field was downloaded as a normal function of a PSAX system software upgrade.

forceDownload Indicates that the firmware driver displayed in the Curr Ver field was downloaded as a result of selecting the driver in the Next Version field and then selecting the Start Upgrade button.

255-700-762R11.1 10-45



Firmware Down-load Status

Default: None

Range: N/A

Format: Predefined

Displays the status of the firmware downloading after you select the Start Upgrade command. A system message is also displayed in the status line at the bottom of the win-dow.

Note: If you have just upgraded your PSAX system soft-ware, make sure that the value Done is displayed in this field for all modules before you do any of the following:

• Reboot the primary or standby CPUn module or the PSAX chassis

• Perform a primary CPU switchover

• Synchronize the standby CPUn module software ver-sion with the primary CPUn module

• Restore your database files from a separate storage medium to the PSAX system using the Remote Database Operation window

• Change any configuration values

None Indicates that a firmware download is not currently taking place.

Done Indicates that the firmware downloading on the module was complete and successful.

Progress Indicates that the new firmware is currently being down-loaded.

Retry Indicates that the PSAX system is attempting to download the firmware. After 2,048 attempts are tried unsuccess-fully, the value Failed is displayed in this field.

ReqRepTimeout Indicates that a request to download the firmware was made but no reply from the module was received during the designated time period.

RequestPending Indicates that a request to download the firmware was made and the system is waiting for a response from the module.

Failed Indicates that the attempt to download the new firmware failed.

RemoveCardBefore Finish

Indicates that while the firmware was being downloaded to the module, the user removed it from the PSAX chassis; therefore, the firmware download was not completed.

WrongCardType Indicates that one type of module was configured in this slot in the chassis, but now a different module occupies this slot.

WrongCardSType Indicates that one type of stratum module was configured in this slot in the chassis, but now a different stratum module occupies this slot.

Table 10-17. Firmware Upgrade Panel Field Descriptions (Continued)


10-46 255-700-762R11.1


Chapter 10 Using Diagnostics and Upgrading PSAX ComponentsScheduling PSAX Configuration Backups

The first four digits of the driver code correspond to the firmware release number. The last four digits of the driver code correspond to the check-sum.

Note: For more information about how to select firmware drivers, see ”Selecting Firmware Drivers” on page 10-43.

3 Click the entry or entries that contain(s) the I/O and server module(s) to which you want to download firmware.

4 Select the driver version you wish to download in the Next Firmware Version field.

5 Click Upgrade.

6 The following confirmation window appears (see Figure 10-35).

7 Click Yes.

The firmware download process begins.

Note: You can only start the firmware download process on one module at a time. You can start another firmware download before the cur-rent firmware download finishes.


End

Scheduling PSAX Configuration BackupsWith the Scheduled PSAX Configuration Backup feature (introduced in Release 6.1.0), you can schedule automatic backups, at specific intervals, of configuration files for specified PSAX devices.

Figure 10-34. Firmware Upgrade Panel (Selecting Next Firmware Version)

Figure 10-35. Firmware Upgrade Confirmation Window

255-700-762R11.1 10-47



The backup process is based on the IP address of the primary CPUn in the PSAX device and the community string. You may only have one backup con-figuration per PSAX IP address (CPUn). Within a single PSAX IP address, you can have a different backup configuration for each community string. HP OpenView NNM must be installed on the EMS-PSAX server before you can schedule or perform backup configurations.

You can also backup PSAX configuration files manually by using the Remote Database Operation feature described in a separate section in this chapter.

Creating an FTP-Only Account

For security reasons, it is suggested that you create an FTP only account (if you do not already have one) before setting up PSAX backup configurations. Contact your system administrator to create the FTP-only account; it is rec-ommended that your system administrator performs this procedure.

Begin

1 Type: su root.

2 To add /bin/false account, to /etc/shells,

a Type: ls /bin/*sh > /etc/shells (if /etc/shells does not already exist)

If this command is executed, delete any lines in /etc/shells that are not actual command interpreters.

b Type: vi /etc/shells (or use your favorite text editor)

c In the last line, type (if the entry does not already exist): /bin/false

The explanation of this change is that the shell named /bin/false will not allow $USER_NAME to log in. But the /bin/false entry appears in /etc/shells. This combination of circumstances permits you to FTP but not log in to a shell.

3 Decide upon a $GROUP_NAME, $USER_NAME, and $PASSWORD. $USER_NAME and $PASSWORD, should not contain control characters, like @, $, and so on. If so, when putting the entry into the crontab file, any such control characters in the password should be preceded by a "\" so that they may be interpreted correctly.

4 Verify that group $GROUP_NAME already appears in file /etc/group. If it not, create the group by typing:

groupadd $GROUP_NAME

5 Verify that directory $BACKUP_DIR (/opt/NEP/backup) exists and is owned and writeable by group $GROUP_NAME. If required, create a dif-ferent directory, $BACKUP_DIR by typing:

mkdir $BACKUP_DIR

chgrp $GROUP_NAME $BACKUP_DIR

chmod 1777 $BACKUP_DIR

6 Decide whether this directory should be viewable by the general anony-mous FTP public. If you want the files in the directory not to be viewable, type:

10-48 255-700-762R11.1



chmod o-rwx $BACKUP_DIR

7 Finally, look at the directory permissions and verify that they are as you wish. To add a user, type (on two lines only, not three as shown here):

(Line 1)useradd -c "AQueView Backup" -g $GROUP_NAME -d $BACKUP_DIR -s /bin/false $USER_NAME

(Line 2)passwd $USER_NAME

To create a new password, type: $PASSWORD

Reenter the new password: $PASSWORD

The system displays a confirmation message: passwd successfully changed for username

End

Setting Up a PSAX Backup Schedule

To schedule PSAX configuration backups, perform the steps in the following procedure.

Begin

1 In the Main EMS-PSAX window, select File > Config Backup.

The Backup Configuration window appears (see Figure 10-36).


Figure 10-36. Backup Configuration Window

255-700-762R11.1 10-49



Table 10-18. Field Descriptions for the Backup Configuration Window


PSAX IP Address Default: 0.0.0.0

Range: N/A


Indicates the CPU IP address of the PSAX device whose configuration you wish to back up.

Community String Default: N/A

Range: 1–53


Indicates the user’s current read-write commu-nity string. The value in this field is used as an authentication password to process an SNMP request for users who have read-write access to the EMS-PSAX.

Navis EMS-PSAX IP Server

Default: 0.0.0.0

Range: N/A


Indicates the IP address of the EMS-PSAX server for the network to which the specified PSAX device belongs, and the server in which the con-figuration backup files will be stored.

FTP User Name Default: N/A

Range:


Indicates your user name for your FTP account.

It is recommended to create a UNIX user name for the EMS-PSAX backup user because the FTP password is listed in root's crontab file.

FTP Password Default: N/A

Range:


Indicates your password for your FTP account.

Do not use control characters such as $ or \ in the new user's password, because the EMS-PSAX system will not automatically enter the shell escape character \.

10-50 255-700-762R11.1



3 Click BackUp.

A confirmation window appears (see Table 10-19).

Repeat Backup Default: None

Range: N/A

Format: Predefined

Indicates how often the backup procedure is to be performed for this PSAX device.

None Indicates the backup procedure will be performed immediately, but it will not be automatically repeated for this PSAX device.

Daily Schedules the backup procedure to occur once per day, beginning on the day that you perform step 3, at the time specified in the Hour (0-23) and Minute (0-59) fields.

Weekly Schedules the backup procedure to occur one time per week, beginning on the day that you perform step 3, at the time specified in the Hour (0-23) and Minute (0-59) fields.

Monthly Schedules the backup procedure to occur one time per month, beginning the day that you per-form step 3, at the time specified in the Hour (0-23) and Minute (0-59) fields.

Hour (0-23) Default: N/A

Range: 0–23

Format: Numeric

Indicates the hour (that is, according to the local time as configured on your workstation) that the backup procedure is scheduled to occur. For example, enter 0 to denote Midnight; enter 14 to denote 2 p.m.

This field is display-only when the value None is selected in the Repeat Backup field.

Minute (0-59) Default: N/A

Range: 0–59

Format: Numeric

Indicates the minute of the hour that the backup procedure is scheduled to occur.

This field is display-only when the value None is selected in the Repeat Backup field.

Table 10-18. Field Descriptions for the Backup Configuration Window


255-700-762R11.1 10-51



Table 10-19. Scheduled Backup Configuration Confirmation Window

If the backup process... then the following occurs...

successfully completes (when the value None is selected in the Repeat Backup field)

this confirmation window appears:

a See the section, “Checking the Status of a Backup Process”.

b Click OK > Close.

successfully completes (when a value other than None is selected in the Repeat Backup field)


a See the section, “Checking the Status of a Backup Process”.

b Click OK > Close.

fails due to error in one of the FTP fields or if HP Openview NNM is not installed


fails due to duplicate existing configuration


This error message means that the backup configuration failed because the selected IP address was previously configured in another backup configuration. Only one backup configuration can exist for each IP address, so you must delete the existing con-figuration before you can add a new one for this IP address. Click OK.

To create a new backup configuration, repeat the steps in the sec-tion, “Setting Up a PSAX Backup Schedule”.

To replace the existing backup configuration, perform the steps in the section “Deleting a PSAX Backup Schedule”, then repeat the steps in the section “Setting Up a PSAX Backup Schedule”.

10-52 255-700-762R11.1



4 When you have finished with all backup configurations, click Close on the Backup Configuration window.

End

Viewing Configured Backup Schedules

To view previously configured backup schedules, click Show Config on the Backup Configuration window. The Show Existing Configurations window appears (see Figure 10-37).

Checking the Status of a Backup Process

Upon successful completion of the backup process, the configuration files are saved in a file (within the /opt/NEP/backup directory) that is named with the same value you entered in the PSAX IP Address field. You may access the backup directory at any time to view the list of all the PSAX devices whose configuration files you have backed up. You can also check the status of the backup configuration by viewing the configsave_status.txt file within the /opt/Navis EMS-PSAX/logs directory.

The Backup Successful confirmation window (see Table 10-19) mentions the backup directory. You may optionally verify that the backup process has occurred by checking the backup directory on the EMS-PSAX server machine. Once you access the directory, located the IP address as indicated in the backup configuration, and then list the contents of that directory using the command ls -l to display the date and time the backup occurred.

Deleting a PSAX Backup Schedule

To remove a scheduled PSAX backup configuration, perform the steps in the following procedure.

Figure 10-37. Show Existing Configurations Window

255-700-762R11.1 10-53


Chapter 10 Using Diagnostics and Upgrading PSAX ComponentsRemote Database Operation

Begin

1 Enter the appropriate values in the following fields:

• PSAX IP Address

• Community String

• Navis EMS-PSAX Server IP

• FTP User Name

• FTP Password

2 Click Delete.

3 Click Close.

End

Remote Database OperationThe Remote Database Operation feature, introduced in Release 5.1, allows you to use FTP to transfer configuration files to a remote host (for example, a computer). This feature can also be used to backup and restore PSAX config-uration files.

Perform the steps in the following procedure to log in to a PSAX device.

Begin

1 In the Device window, click the System Maintenance tab.

The CPU Upgrade page appears.

2 Click the Remote Database tab.

10-54 255-700-762R11.1



The Remote Database page appears (see Figure 10-38).

The button on this window has the following function:

Field Descriptions 3 Select the values for the fields on the Remote Server Operation panel as described in the following table. Use the left mouse button to move between the fields.

Figure 10-38. Remote Database Page

Button Function

Execute Performs the remote database operation.

Table 10-20. Remote Database Page Field Descriptions


Remote Host IP Addr

Default: N/A

Range: 000–255

Format: Numeric

Specifies the IP address of the remote host com-puter, for example, a Unix or Windows-based workstation. The remote host computer must be running as an FTP server.

Login Default: N/A

Range: 1–20


Specifies the user-defined login name for the remote host computer.


Range: 1–20


Specifies the user-defined password for the remote host computer.

255-700-762R11.1 10-55



Directory Default: N/A

Range: 1–79


Specifies the user-defined directory path on the remote host computer where you will store the PSAX system backup database files. Plan on set-ting aside 40 MB of disk space on the remote host computer system disk.

Operation Default: NoOpera-tion

Range: N/A

Format: Predefined

Specifies the function you want to perform on the PSAX system database files.

NoOperation Aborts the file transfer operation. This value is not currently supported.

RemoteSave Performs a backup of the database files by trans-ferring them from the CPU module to the user-defined directory you specified on the remote host computer. When performing future backups, the PSAX system overwrites the existing files in the directory you specified the last time you per-formed a backup.

RemoteLoad Performs the restore function by transferring the database files from the user-defined directory on the remote host computer to the CPU module.

Note: After this operation is completed success-fully (DoneSuccessfully is displayed in the Oper Status field), the PSAX system immediately reboots.


Default: NoActivity

Range: N/A

Format: Predefined

Displays the operational status indicating what activity is currently taking place.

NoActivity Indicates that no operation is currently being done.

Working Indicates that the PSAX system is currently trans-ferring files from one location to another.

DoneSuccessfully Indicates that the file transfer operation was com-pleted successfully.

DoneWithError Indicates that the file transfer operation was attempted, but an error occurred.

Aborted Indicates that the file transfer operation was aborted. This status is not currently supported.

Table 10-20. Remote Database Page Field Descriptions (Continued)


10-56 255-700-762R11.1


Chapter 10 Using Diagnostics and Upgrading PSAX ComponentsProfiling Tool

4 Click Execute.

The Oper Status and Error Status fields will diagnose the stage of the file transfer.

End

Profiling ToolThe Profiling Tool, a feature introduced in Release 5.1, allows you to save configuration settings that you make on a PSAX device by using the EMS-PSAX. The profiling process is similar to the back up and restore pro-cesses. When profiling is enabled, configuration settings that you make on a PSAX device are stored in a file. You may enable profiling for a number of open PSAX devices simultaneously.

With profiling enabled, all configuration settings made on a PSAX device are saved to a file that you specify on the server in the /opt/NEP/profiles direc-tory (for Solaris workstations), or C://Program Files/Lucent Technolo-

Error Status(display only)

Default: None

Range: N/A

Format: Predefined

Displays the error status indicating whether an error has occurred during processing.

None Indicates that no error condition was detected.

UnableToMakeFtp-Connection

Indicates that the PSAX system was not able to connect with the remote host computer.

InvalidDirectory Indicates that the directory name you entered does not match any directory on the remote host computer.

UnableToOpenDa-tabaseFile

Indicates that during the remote load (restore) operation, the PSAX system was unable to open one or more database files on the CPU module.

UnableToCom-pleteFtp

Indicates that during the file transfer operation, an error occurred that interrupted this operation.

DatabaseSanityFail Indicates that during the remote load (restore) operation while sanity checking was being per-formed on the restored files in the temporary directory on the CPU module, the PSAX system found errors in these files.

UnableToUpdate-Backup

Indicates that during the remote load (restore) operation, the PSAX system was not able to transfer the database files from the temporary directory to the established current directory on the CPU module.

Table 10-20. Remote Database Page Field Descriptions (Continued)


255-700-762R11.1 10-57


Chapter 10 Using Diagnostics and Upgrading PSAX ComponentsProfiling Tool

gies/NEP/profiles/ (for Windows workstations). No maximum size is set for these files. The configurations saved to the file will not exceed the file alloca-tion size unless you exceed the hard disk space available on your OS.

The profile file contains the object identifier (OID) of the configuration vari-ables, values, and variable types for all SNMP set commands made to the PSAX device. The format of the file is in the form (see Figure 10-39):

snmpset.n

where n is the number of variables in that specific table entry

OID <Tab> Value <Tab> Variable Type

The profile file is configuration-specific, and should be produced only as needed.You should disable profiling if you do not need to copy, backup, or restore a configuration.

You can configure any number of and type of modules as a given hardware configuration. When the same hardware configuration is duplicated on a dif-ferent device, you can create a script to read a profile file and recreate the software configuration.

Perform the steps in the following procedure to create a profile file.

Figure 10-39. Example of Profile File

10-58 255-700-762R11.1


Chapter 10 Using Diagnostics and Upgrading PSAX ComponentsConfiguring Bulk Statistics

Begin

1 To enable profiling, select Device > Start Profiling from the Device Menu Bar.

The Profiler window appears (see Figure 10-40).

2 Enter the file name that you want to use in the Profile Name field, and click Profile. If that file currently exists, it will be appended to. If the file does not currently exist, then a new file will be created and opened for output. If you want to abort this command, click Cancel.

Any configuration changes made to the PSAX device after you enable profil-ing will be saved to the file you created in step 2.

Note: If you are using a Windows XP/NT/2000 workstation, be sure to name your file with a .txt extension, for example, "myprofile.txt." Be sure to name the file accordingly because it is possible to over-write a file. If you overwrite the file, you will lose all the configura-tion data that was in the file.

3 To disable profiling, select Device > Stop Profiling from the Device Menu Bar.

Any configuration changes made to the PSAX device after you disable profil-ing will not be saved to the file.

End

Configuring Bulk Statistics

Enabling Bulk Statistics

To enable bulk statistics, perform the steps in the following procedure.

Begin




Figure 10-40. Profiler Window

255-700-762R11.1 10-59




3 In the Feature On/Off Configuration panel, select the BulkStats row.


5 To enable the Bulk Statistics feature, select Turn On Selected Feature (if the feature is already enabled, this option will not be selectable). The fol-lowing window appears (see Figure 10-41).


7 Reboot the PSAX device so that the values you selected will take effect.

End




10-60 255-700-762R11.1



Viewing Bulk Statistics

Begin




The Special Features page appears (see Figure 10-42).

3 Click the Bulk Stats tab.

Figure 10-44. Special Features Page

255-700-762R11.1 10-61



The Bulk Stats page appears (see Figure 10-43).


4 Select values for the fields on this window as described in Table 10-20.

5 Click Apply.

End

Figure 10-45. Bulk Statistics Page

Button Function

Apply Applies the values set for the local node.

Reset Reverts to the last applied values.

Table 10-21. Bulk Statistics Window Field Descriptions


Statistics Server IP Addr

Default: 0.0.0.0

Range: N/A


Indicates the IP Address for statistics server.

Login Default: N/A

Range: N/A

Format: Character

Indicates the FTP account name for the statistics server.


Range: N/A

Format: Character

Indicates the FTP account password for the statis-tics server.

Directory Default: N/A

Range: N/A

Format: Character

Indicates the directory on the statistics server where statistics files are saved.

10-62 255-700-762R11.1



Collection Time Period

Default: 15

Range: 15–1440

Format: Numeric (Minutes)

Specifies the frequency (in minutes) at which bulk statistics are collected and sent to the statisitcs server. Enter a value in increments of 15 minutes, such as, 15, 30, 60, 120, 180 and so on up to 1440. For example, if you choose 60 min-utes, the PSAX system sends the collected bulk statistics to the statisitcs server at the beginning of every hour: 12:00 am, 1:00 am, 2:00 am, and so on. When the period is changed, the initial statis-tics file is abbreviated until the collection time matches the selected period.

Bulk Stats File For-mat

Default: NavisEx-tendStatsServer

Range: N/A

Format: Predefined

Specifies the statistics file format the PSAX system sends to the specified statistics server.

NavisExtend-StatsServer

Select to format the statistics file for the NavisEx-tend Statistics Server.

Generic-ASCII Select to format the statistics file for the a generic statistics server other than the NavisExtend Sta-tistics Server. The statistics file is a comma-delim-ited ASCII character format.

System Flag Default: Enabled

Range: N/A

Format: Predefined

Indicates whether the bulk stats files are pre-vented from FTPing records to stats server once there are some bulk stats flags enabled on con-nection level and port level.

Enabled Indicates that records will be FTPed to the statis-tics server.

Disabled Indicates that records will not be FTPed to the sta-tistics server.

Max Usage Status Default: 1000

Range: N/A

Format: Character

Specifies the maximum number of bulk statistics records that are supported in the PSAX system for collecting statistics data, including ATM and frame relay interface statistics, and ATM and frame relay PVC connections.

Current Usage Default: 0

Range: N/A

Format: Character

Specifies the number of bulk statistics records are enabled, including ATM and frame relay interface statistics, and ATM and frame relay PVC connec-tions.

Table 10-21. Bulk Statistics Window Field Descriptions (Continued)


255-700-762R11.1 10-63



Copying Thousands of Connections When the Bulk Statistics Feature is Enabled

The EMS-PSAX will abort the connection copy when 1,000 connections have been exceeded and the bulk statistics option is enabled. However, if a number of connections of a type that supports bulk statistics preexists before the copy function is initiated, then potentially a large number of connection failure traps will still be processed.

Operating Status Default: Inactive

Range: N/A

Format: Predefined

Specifies the current status for transferring bulk statistics files to the statistics server.

Inactive Indicates that no FTP activity is currently taking place.

InProgress Indicates that FTP file to statistics server is in progress.

Failed Indicates an FTP failure due to the error status indicated in the Error Status field.

Successful Indicates that the FTP was completed with no errors.

Error Status Default: None

Range: N/A

Format: Predefined

Specifies an error status that caused FTP failure.

None Indicates that no error has occurred during the FTP process.

UnableToMakeFTP-Connection

Indicates that the PSAX device was unable to make an FTP connection.

unableToWriteFile Indicates that the PSAX device was unable to write to the system.

unableToOpenFile Indicates that the PSAX device was unable to open input file.

unableToCom-pleteFTP

Indicates that the PSAX device was unable to complete the FTP process.

Table 10-21. Bulk Statistics Window Field Descriptions (Continued)


10-64 255-700-762R11.1


11 Configuring the GR-303 VoiceGateway

GR-303 Feature Availability

The GR-303 feature is available in PSAX system software beginning with PacketStar PSAX Release 6.5.0, and with the PSAX system EMS beginning with Release 4.5. To ensure optimal performance of your PSAX device while using this feature, be sure to use CPU2, CPU3, or CPU4 modules in your PSAX device.

The GR303 System-Wide tab will become enabled only after you have enabled the GR-303 feature under the Feature Turn On/Off tab. Otherwise, the GR303 System-Wide tab will be disabled. For information on enabling system-wide features, see the section “Enabling the GR-303 Feature”

Enabling the GR-303 Feature

To enable or disable system-wide features for your EMS-PSAX, perform the steps in the following procedure.

Begin





3 In the Feature On/Off Configuration panel, select an entry that you wish to enable (turn on) or disable (turn off).



255-700-762R11.1 11-1

Chapter 11 Configuring the GR-303 Voice GatewayEnabling the GR-303 Feature


5 To enable the feature, select Turn On Selected Feature. To disable the fea-ture, select Turn Off Selected Feature. When you select either of these options, the following window appears (see Figure 11-3).

6 The values for the fields on this window are described in Table 11-1.


8 Reboot the PSAX device so that the values you selected will take effect. See Chapter 9 for instructions.

End



11-2 255-700-762R11.1


Chapter 11 Configuring the GR-303 Voice GatewayEnabling the GR-303 Feature

Table 11-1. Feature Turn On/Off Page Field Descriptions


Feature Default: N/A

Range: N/A

Format: Pre-defined

Displays the PSAX system features that you can enable or dis-able.

Pnni Private network-to-network interface feature.

Note: Currently, this feature cannot be disabled.

Gr303 ITU-T GR-303 local loop emulation services feature. For exam-ples of applications using the GR-303 interface, see the Packet-Star® PSAX Configuring the GR-303 Voice Gateway User Guide.

Vipr Virtual Internet Protocol Router feature.

Note: This feature is not currently supported.

H248 Select this value to enable the H.248 protocol feature.

V5 European V5.2 local loop emulation services feature.

Iua ISDN Q.921 User Adaptation Layer Protocol feature. Enables OSI Layer 2 ISDN D-channel signalling between an Media Gateway Controller (for example, a Softswitch) and a Media Gateway (for example, a PSAX system) in PRI offload applications.

AtmSec Select this value to enable the ATM security feature.

BulkStats Select this value to enable the Bulk statistics feature.

CpuBridge Select this value to enable the CPU bridge feature only on the CPU3 module. See the procedure “Configuring the CPU3 Mod-ule Ethernet Bridge” on page 5-33 to configure the connection.

Minimum Memory Required (Bytes)

Default: PNNI: 0Gr303: 25165824Vipr: 262144H248: 3145728V5: 25165824Iua: 1507328AtmSec: 655360BulkStats: 262144CpuBridge: 262144

Range: N/A


Displays the amount of system memory in bytes required by the feature.

255-700-762R11.1 11-3


Chapter 11 Configuring the GR-303 Voice GatewayConfiguring I/O and Server Modules

Configuring I/O and Server Modules

Configuring the DSP2 Voice Server Module Values

Perform the following procedure to configure the DSP2C or DSP2D Voice Server module to be used in the GR-303 application.

Begin

1 Using a DSP2C or DSP2D Voice Server module, configure the DSP2 inter-face as shown in Table 11-2:

Desired Status Default: Enable or Disable (depends on the feature)

Range: N/A

Format: Pre-defined

Specifies whether the feature is to be made operational or not.

Note:

Disable Indicates that the selected enabled feature is to be made non-operational. After selecting this value, you must reboot the PSAX system to make this change take effect. After the system reboots, Disabled is displayed in the current status field.

Enable Indicates that the selected disabled feature is to be made opera-tional. After selecting this value, you must reboot the PSAX sys-tem to make this change take effect. After the system reboots, Enabled is displayed in the current status field.

Current Status Default: N/A

Range: N/A

Format: Pre-defined

Displays the current operational status of the feature.

Disabled Indicates that the selected feature is currently not operational.

Enabled Indicates that the selected feature is currently operational.

Table 11-1. Feature Turn On/Off Page Field Descriptions (Continued)


Table 11-2. Values to Choose for the DSP2x Voice Server Module

If you are using this module... then select these values in the following fields...

DSP2C Voice Server module DSP Mode: DSP2A

DSP2D Voice Server module • DSP Mode: AlgoSet6

• AAL2 Mode: Aal2-standard

• Interface Type: Dsp2

11-4 255-700-762R11.1


Chapter 11 Configuring the GR-303 Voice GatewayConfiguring I/O and Server Modules

Note: Compression less than 32 Kbps will not accurately pass tones between subscriber equipment and voice switch. This is a limita-tion of some IADs that support 64 Kbps noncompression and 32 Kbps.

2 Select Standard in the AAL2 Mode field.

3 Apply the configuration and bring the interface into service.

Note: For the detailed procedure to configure the DSP2 interface, see the DSP2x Voice Server Modules User Guide.

End

Configuring ATM I/O Module Values

To apply the GR-303 interface to an I/O module, perform the following pro-cedure.

Note: For this procedure as a part of the GR-303 application, use an I/O module that supports ATM.

Begin

1 Do one of the following to open the Port and Channel Configuration window:

• In the Front Panel, double-click the port to be viewed or configured.

• In the Front Panel, right-click the port and a menu appears. Select View.

• In the Device Tree, double-click the desired port symbol or identifier.

• In the Device Tree, select a port, then right-click the icon for the mod-ule within Device Tree and a menu appears. Select View.

The corresponding Port and Channel Configuration window appears.

2 On the Channel Configuration page, select AtmUni3-0,AtmUni3-1, or AtmUni4-0 in the Interface Type field.

3 Click Apply > Bring Into Service.

4 Proceed to the section, “Applying the GR-303 Interface to DS1s”

End

Applying the GR-303 Interface to DS1s

To apply the GR-303 interface to an I/O module, perform the following pro-cedure.

Note: For this procedure as a part of the GR-303 application, use an I/O module that supports GR-303.

Begin

1 Do one of the following to open the Port and Channel Configuration window:

255-700-762R11.1 11-5


Chapter 11 Configuring the GR-303 Voice GatewayConfiguring the GR-303 Interface

• In the Front Panel, double-click the port to be viewed or configured.

• In the Front Panel, right-click the port and a menu appears. Select View.

• In the Device Tree, double-click the desired port symbol or identifier.

• In the Device Tree, select a port, then right-click the icon for the mod-ule within Device Tree and a menu appears. Select View.

The corresponding Port and Channel Configuration window appears.

2 On the Port Configuration page, select Disabled in the Channelization field.

3 Click Apply.

4 On the Channel Configuration page, select Gr303 in the Interface Type field and take the appropriate action as shown in Table 11-3.

5 Proceed to the following procedure.

End

Configuring the GR-303 Interface

This section provides instructions for configuring a module for the GR-303 interface.

Begin

1 After applying the Gr303 interface type to a channel from the Channel Configuration page, do one of the following to access the GR-303 Inter-face Configuration window:

• Double-click the left mouse button on the channel for which you want to configure the interface.

• Right-click the channel that you want to configure and a menu appears. Select Configure in the menu.

Table 11-3. DS1 Configuration

If the DS1 being configured then do this...

will carry the primary EOC and TMC channels

proceed to the following procedure.

will not carry the primary EOC and TMC channels

Click Apply > Bring Into Service.

11-6 255-700-762R11.1



The GR-303 Interface Configuration window appears (see Figure 11-4).


Figure 11-4. GR-303 Interface Configuration Window

Button Function

Bring Into Service Displays when the Admin Status field is OutOfSer-vice. Brings an out-of-service configured interface to in-service status. The value InService is dis-played in the Admin Status field.

You must first configure the interface before you can use this button.

Take Out of Service Displays when the Admin Status field is InService. Takes an in-service configured interface to out-of-service status. The value OutOfService is dis-played in the Admin Status field.

You must use this button first before using the Delete button.

Delete Deletes an out-of-service interface and redisplays the Port and Channel Configuration window for the module you are configuring.

You must first take interface out of service (by clicking the Take Out of Service button) before you can use this button.

255-700-762R11.1 11-7



2 Select the values for the fields on this window from the values provided in Table 11-4.

3 Click Apply.

4 To activate the interface after you have applied the configuration values, click Bring All Into Service.

5 Continue to step 2 of the section, “Performing Bulk Operations,” in this chapter. When finished, repeat this procedure to create a second GR-303 interface (the backup interface).

End

Copy Copies this interface to a range of channels.

Configure H248 TID Displays the H.248 Termination ID Configuration window. For more information on using this mod-ule with H.248, see the H.248 Media Gateway Control User Guide for the PacketStar® PSAX Multiservice Media Gateways.


Apply Applies the configuration field value you set.


Apply Ds0 Channel Configura-tion

Applies the values you set.

Bring All Into Service This button is displayed when the Administrative Status field is OutOfService. Brings all out-of-ser-vice configured DS0 channels to in-service status. The value InService is displayed in the Admin Status field.

Take All Out of Service This button is displayed when the Administrative Status field is InService. Takes all in-service config-ured DS0 channels to out-of-service status. The value OutOfService is displayed in the Admin Status field.

Button Function

Table 11-4. GR303 Interface And DS0 Configuration Window Field Descriptions


Interface Type GR303 Indicates the interface type you are configuring.

11-8 255-700-762R11.1


Chapter 11 Configuring the GR-303 Voice GatewayConfiguring the GR-303 Gateway

Configuring the GR-303 Gateway

To configure a GR-303 interface group, perform the steps in the following procedure.

[Administrative Status](display only)

Default: OutOfService

Range: N/A

Format: Predefined

Indicates any condition that may prevent the port from being fully operational.

InService Indicates that no conditions are preventing the port from being fully operational.

OutOfService Indicates that some condition is preventing the port from being configured with an interface.

[OperationalStatus](display only)


Range: N/A

Format: Predefined

Indicates whether the channel has been config-ured or not.

Unconfigured Indicates that this channel has not been config-ured.

InService Indicates that the channel is operational.

OutOfService Indicates that the channel is configured, but not operational.

EOC Channel No Default: 0

Range: 1–24

Format: Numeric

Embedded operations channel (EOC) number. If the EOC channel is set to 0, no TMC channel will be on the corresponding DS1. Generally, the EOC channel should be specified on one of the DS1s in a GR-303 interface group, and should be on DS0 number 12.

Note: When using a primary and a backup EOC, this value must be set to 12.

TMC Channel No Default: 0

Range: 1–24

Format: Numeric

Timeslot management channel (TMC) number. If the TMC channel is set to 0 there will be no TMC channel on the corresponding DS1. Generally, the TMC channel should be specified on one of the DS1s in a GR-303 interface group, and should be on DS0 number 24.

Note: When using a primary and a backup TMC, this value must be set to 24.

Interface Name Default: N/A

Range: N/A

Format: Alphanumeric ASCII Characters

Specifies the name you assign to this interface (this field is optional; that is, you may leave this field blank).

Table 11-4. GR303 Interface And DS0 Configuration Window Field Descriptions


255-700-762R11.1 11-9



Begin





3 Click the GR303 System-Wide tab.

The GR303 System-Wide page appears (see Figure 11-5).

4 In the GR303 IG Configuration Table panel, right-click anywhere within the panel and a menu appears. Select Create.

The ADD GR303 IG Configuration Entry window appears (see Figure 11-6).

Figure 11-5. GR303 System-Wide Page

11-10 255-700-762R11.1




Figure 11-6. ADD GR303 IG Configuration Entry Window

Button Function

Create Adds this entry to the GR303 IG Configu-ration Table (see Figure 11-5).

Bring Into Service Brings an out-of-service configured inter-face to in-service status. The value InSer-vice is displayed in the Admin Status field.


Take Out of Service Takes an in-service configured interface to out-of-service status. The value OutOfService is displayed in the Admin Status field. You must use this button before using the Delete button.

Add DS1 Interface Displays the ADD DS1 GR303IG Interface Configuration Entry window.


255-700-762R11.1 11-11




Apply TMC Configuration Applies the values you set in the TMC Parameters panel.

Apply LAPD Configuration Applies the values you set in the LAPD Parameters panel.

Button Function

Table 11-5. GR- 303 Interface Group Configuration Window Field Descriptions


GR303 Interface Group Configuration Panel


Default: OutOfSer-vice

Range: N/A

Format: Predefined

Indicates whether the configured interface is ready to pass traffic or not.

InService No conditions are preventing the port from being fully operational.

OutOfService A condition is preventing the port from being configured with an interface.

Primary TMC Ch ID Default: 0


Format: Numeric

Specifies the primary Timeslot Management Channel (TMC) channel identifier in ssppccc (slot, port, channel) format. This is the DS1 connected to the local digital switch.

Default: Standby-OutOfService

Range: N/A

Format: Predefined

Displays the primary TMC channel status. This field is display only; next to Primary TMC Ch ID.

Standby-OutOfSer-vice

The TMC is out of service but in standby mode.

Active-OutOfSer-vice

The TMC is configured but out of service.

Active-InService The TMC is configured and in service.

Note: The GR-303 interface will function without a backup TMC; however, it is recommended that you configure both a primary and a backup TMC on the GR-303 interface for redun-dancy.

Backup TMC Ch ID Default: 0

Range: Equipment dependent

Format: Numeric

Specifies the backup TMC channel identifier in ssppccc (slot, port, channel) format.

11-12 255-700-762R11.1



(Backup TMC channel status dis-play only; next to Backup TMC Ch ID)


Range: N/A

Format: Predefined

Displays the backup TMC channel identifier oper-ational status.


The backup TMC is configured, but out of service and in standby mode.

Standby-InService The backup TMC is configured and in standby mode.

Primary EOC Ch ID Default: 0


Format: Numeric

Specifies the primary Embedded Operations Channel (EOC) channel identifier in ssppccc. (slot, port, channel) format.

Default: Active-Out-OfService

Range: Equipment-dependent

Format: Predefined

Displays the primary EOC channel status. This field is display only; next to Primary EOC Ch ID.

Active-OutOfSer-vice

The primary EOC channel is configured, but out of service.

Active-InService The primary EOC channel is configured and in service.


The standby EOC channel is configured and out of service.

Note: Both a primary and a backup EOC must be configured for the GR-303 interface to func-tion.

Backup EOC Ch ID Default: 0


Format: Numeric

Specifies the backup EOC channel interface iden-tifier in ssppccc (slot, port, channel) format.

(Backup EOC chan-nel status display only; next to Backup EOC Ch ID)



Format: Predefined

Displays the backup EOC channel status.

Standby-InService The backup EOC channel is configured and in service.


The backup EOC channel is configured, but out of service.

TMC ProtSw-ProvState

Default: Pps-enable

Range: N/A

Format: Predefined

Specifies the TMC path protection switch.

Pps-inhibit Inhibits (disables) the path protection switch.

Pps-enable Enables the path protection switch.

Table 11-5. GR- 303 Interface Group Configuration Window Field Descriptions (Continued)


255-700-762R11.1 11-13



EOC ProtSw-ProvState

Default: Pps-enable

Range: N/A

Format: Predefined

Specifies the EOC path protection switch.

Pps-inhibit Inhibits (disables) the path protection switch.

Pps-enable Enables the path protection switch.

TMC ProtSwCom-mand

Default: NoAction

Range: N/A

Format: Predefined

Specifies the type of manual switchover used on the TMC channel.

NoAction Indicates that no manual switchover will occur.

NormalSwitchTo-Backup

Initiates a manual switchover of the TMC chan-nels. If the channel you are trying to switch to is out of service, the switchover will not occur.

Note: The values NormalSwitchToBackup and NormalSwitchToPrimary each provide the same function.

NormalSwitch-ToPrimary

Initiates a manual switchover of the TMC chan-nels. If the channel you are trying to switch to is out of service, the switchover will not occur.


ForcedSwitchTo-Backup

Initiates a manual switchover of the active TMC channel to a backup channel regardless of whether it is in service.

Note: The values ForcedSwitchToBackup and ForcedSwitchToPrimary each provide the same function.

ForcedSwitch-ToPrimary

Initiates a manual switchover of the active TMC channel to a primary channel regardless of whether it is in service.




11-14 255-700-762R11.1



EOC ProtSwCom-mand

Default: NoAction

Range: N/A

Format: Predefined

Specifies the type of manual switchover used on the EOC channel.

NoAction Indicates that no manual switchover will occur.

NormalSwitchTo-Backup

Initiates a manual switchover of the EOC chan-nels. If the channel you are trying to switch to is out of service, the switchover will not occur.


NormalSwitch-ToPrimary

Initiates a manual switchover of the EOC chan-nels. If the channel you are trying to switch to is out of service, the switchover will not occur.


ForcedSwitchTo-Backup

Initiates a manual switchover of the active EOC channel to a backup channel regardless of whether it is in service.


ForcedSwitch-ToPrimary

Initiates a manual switchover of the active EOC channel to a primary channel regardless of whether it is in service.


Local Digital Sw Type

Default: Lucent-5ess

Range: N/A

Format: Predefined

Specifies the local digital switch type.

Lucent-5ess Lucent 5ESS switch.

Nortel-dms Nortel DMS switch.

Local Digital Sw Version

Default: Lucent-5ess-version-1

Range: N/A

Format: Predefined

Specifies the version of carrier-class CO switch used.

Lucent-5ess-ver-sion-1

Lucent 5ESS switch version 1.

Nortel-dms-ver-sion-1

Nortel DMS switch version 1. Software version on the PSAX system must be compatible with the DMS.



255-700-762R11.1 11-15



6 Click Create.

TMC Parameters Panel

T303 (MSecs) Default: 700

Range: 700–4700

Format: Msec. with a step size of 500 msec.

Specifies the length of time that the inter-machine digital trunk (IDT) and the remote digi-tal terminal (RDT) will wait for a reply to a SETUP message.

Note: You must specify the step size in incre-ments of 500 msec. for this timer to function properly, including parameter changes.


Range: 700–14700


Specifies the length of time that the RDT will wait for a reply to a SETUP message following the ini-tial expiration of timer T303.

Note: You must specify the step size in incre-ments of 1000 msec. for this timer to function properly, including parameter changes.

LAPD Parameters Panel


Range: 100–350


Specifies the waiting period for receipt of an acknowledgement or a transmitted frame.

Note: You must specify the step size in incre-ments of 50 msec. for this timer to function prop-erly, including parameter changes.

T203 (Secs) Default: 30

Range: 10–300

Format: Seconds with step size of 10 sec.

Specifies the timer used to time periods of inac-tivity on a data link. When the value T203 expires, a supervisory frame with a poll bit set to 1 is sent to determine if the other side of the interface is capable of sending and receiving frames.

Note: You must specify the step size in incre-ments of 10 sec. for this timer to function prop-erly, including parameter changes.

N200 (MSecs) Default: 3

Range: 1–10

Format: Times

Specifies the maximum number of frame retrans-missions allowed. Step size is 1.

Window Size (k) (Times)

Default: 7

Range: 1–7

Format: Numeric

Specifies the maximum number of outstanding I frames allowed.



11-16 255-700-762R11.1


Chapter 11 Configuring the GR-303 Voice GatewayUpdating GR-303 Interface Group Configuration

If this entry is valid, it is added to the GR303 IG Configuration Table and the IG Statistics tab appears (see Figure 11-7).


End

Updating GR-303 Interface Group ConfigurationTo update an existing GR-303 interface group configuration, perform the steps in the following procedure.

Begin

1 To update the interface group or perform a switchover, right-click the interface group within the GR303 IG Configuration Table panel, and a menu appears. Select Update.

Figure 11-7. VIEW GR303 IG Configuration Entry Window

255-700-762R11.1 11-17


Chapter 11 Configuring the GR-303 Voice GatewayUpdating GR-303 Interface Group Configuration

The UPDATE GR303 IG Configuration Entry window appears (Figure 11-8).



Figure 11-8. UPDATE GR303 IG Configuration Entry Window

Button Function

Apply TMC Command Applies the value selected in the TMC ProtSwCommand field.

Apply EOC Command Applies the value selected in the EOC ProtSwCommand field.

Bring Into Service Brings an out-of-service configured inter-face to in-service status. The value InSer-vice is displayed in the Admin Status field.


11-18 255-700-762R11.1


Chapter 11 Configuring the GR-303 Voice GatewayAdding DS1s to a GR-303 Interface Group

3 Click the appropriate button according to the action you want to perform as described below.

4 When finished, click Close.

End

Adding DS1s to a GR-303 Interface Group To add DS1s to an GR-303 interface group, perform the following procedure.

Begin

1 Do one of the following to open the ADD DS1 GR303IG Interface Con-figuration Entry window:

~ Within the DS1 GR303IG Interface Table panel on the GR303 System-Wide page (see Figure 11-5), click the right mouse button and a menu appears. Select Create.

~ Click Add DS1 Interface.

The ADD DS1 GR303IG Interface Configuration Entry window appears (see Figure 11-9).

Take Out of Service Takes an in-service configured interface to out-of-service status. The value OutOfService is displayed in the Admin Status field. You must use this button before using the Delete button.

Add DS1 Interface Displays the ADD DS1 GR303IG Interface Configuration Entry window.

Update Applies the field values on this window. The interface must be out of service before you can use this button.

Reset Refreshes the fields on this window.


Button Function

Figure 11-9. ADD DS1 GR303IG Interface Configuration Entry Window

255-700-762R11.1 11-19


Chapter 11 Configuring the GR-303 Voice GatewayAdding DS1s to a GR-303 Interface Group


3 Click Add.

4 On the Interface Group Configuration page (see Figure 11-6), click Bring Into Service.


6 Click Close.

End

Table 11-6. DS1 GR303 Interface Configuration Entry Window Field Descriptions


GR303 IG ID Default: 1

Range: 1–84

Format: Numeric

Indicates the number of the interface group you want to configure.

Interface ID Default: 1

Range: 1–28

Format: Numeric

Indicates the identifier of the interface group you want to configure.

Note: When using a primary and a backup GR-303 interfaces, the value on the primary GR-303 interface must be set to 1, and the backup GR-303 interface must be set to 2.

Interface DS1 Phys-ical ID

Default: 0

Range: Equipment dependent.

Format: Numeric

Indicates the identifier of the DS1 interface group in ssppccc format, where ssppccc are the slot, port, and channel numbers.

Interface Net ID(display only)

Default: 1

Range: 1–28

Format: Numeric

Displays the GR303IG Interface (DS1) Net ID assigned by the network.

Note: This value MUST match the Remote Ter-minal Facility ID (RT Term Fac) on the 5ESS Recent Change 18.15 Remote Terminal (TR303) screens.

11-20 255-700-762R11.1


Chapter 11 Configuring the GR-303 Voice GatewayViewing GR-303 Interface Group Statistics

Viewing GR-303 Interface Group StatisticsAfter creating a GR-303 interface group, the IG Statistics tab appears. Click the tab and the IG Statistics page appears (see Figure 11-10).

The fields on the IG Statistics page are described in Table 11-7.

Figure 11-10. IG Statistics Page

Table 11-7. GR303IG Statistics Window Field Descriptions


Current Incoming Calls

Default: User-defined

Range: N/A

Format: Numeric

Displays the total number of currently established incoming calls.

Current Outgoing Calls

Default: 0

Range: N/A

Format: Numeric

Displays the total number of currently established outgoing calls.

Outgoing Calls Suc-cessful

Default: 0

Range: N/A

Format: Numeric

Displays the total number of successful outgoing calls since statistics were last reset.

255-700-762R11.1 11-21


Chapter 11 Configuring the GR-303 Voice GatewayPerforming Bulk Operations

Performing Bulk Operations

Perform the following procedure to enable or disable trap messages.

Begin

1 Do one of the following:

A confirmation window appears (see the following table).

2 Do one of the actions described in the following table.

Outgoing Calls Failed

Default: 0

Range: N/A

Format: Numeric

Displays the total number of failed outgoing calls since statistics were last reset.

Incoming Calls Suc-cessful

Default: 0

Range: N/A

Format: Numeric

Displays the total number of successful incoming calls since statistics were last reset.

Incoming Calls Failed

Default: 0

Range: N/A

Format: Numeric

Displays the total number of failed incoming calls since statistics were last reset.

Table 11-7. GR303IG Statistics Window Field Descriptions


Table 11-8. Performing an Action on an Interface

If you want to... then do this...

create a new interface and apply it to a channel

From the Channel Configuration page, select a channel, select any value in the Interface Type field, and click Apply to Selected.

bring an interface into service From the Channel Configuration page, right-click the channel(s) and a menu appears. Select Bring Selected Into Service.

or

From the Front Panel or the Device Tree, right-click the port and select Bring All Interfaces Into Service.

take an interface out of service Right-click on the channel(s) and a menu appears. Select Take Selected Out of Service.

delete an interface From the Channel Configuration page, right-click the channel(s) and a menu appears. Select Delete Selected Interfaces.

or

From the Front Panel or the Device Tree, right-click the port and select Delete All Interfaces.

11-22 255-700-762R11.1


Chapter 11 Configuring the GR-303 Voice GatewayPerforming Bulk Operations

The confirmation window closes.

To view the status of interface traps, click the Trap Activation tab and select Interface Events in the Show traps from: field at any time.

End

Table 11-9. Enabling or Disabling Traps Decision Table

If you are performing this action... and you... then do this...

creating an interface and applying it to a channel

or

bringing an interface into service

or

deleting an interface

want to enable traps select Enable Traps Before Operation and click OK.

want to disable traps select Disable Traps Before Operation and click OK.

decide not to complete this action

click Cancel.

taking an interface out of service want to enable traps click OK.

want to disable traps click Cancel.

When taking an interface out of service, you cannot disable traps because the interfaceOutOfServiceNo-tify trap is permanently activated on the device.

decide not to complete this action

click Cancel.

255-700-762R11.1 11-23


Chapter 11 Configuring the GR-303 Voice GatewayCreating GR-303 AAL2 PVC Connections

Creating GR-303 AAL2 PVC ConnectionsThe tasks involved in creating a GR-303 AAL2 PVC connection are:

• Configuring an AAL2 trunk with GR-303 support enabled

• Provisioning a GR-303 AAL2 PVC connection

Adding an AAL2 Trunk Entry

To create a non-multiplexed AAL2 or AAL1 connection, you need a config-ured circuit emulation interface. To create a standard AAL2 connection, you need a configured circuit emulation interface and an AAL2 trunk.

Note: When creating the AAL2 trunk connection, ensure that the peak cell rate for the connection is correct as the PSAX Call Admission Control (CAC) function uses this value to determine whether or not a call can be completed to the subscriber line.

Perform the steps in the following procedure to add an AAL2 trunk.

Begin

1 Click the AAL2 Trunk tab in the Connections tab.

The AAL2 Trunk page appears, displaying the AAL2 Trunk Configuration Table (see Figure 11-11).

If the AAL2 Trunk Configuration Table is empty before you perform Step 2, the AAL2 Trunk Config Entry window will appear with the default values.

If you select an existing AAL2 trunk entry before performing Step 2, the AAL2 Trunk Config Entry window will appear as a template, containing the values of the original AAL2 trunk entry.

2 Right-click the mouse and a menu appears. Select Create.

The AAL2 Trunk Config Entry window appears (see Figure 11-12).

3 Click Add.

The AAL2 trunk is added to the AAL2 Trunk Configuration Table.

4 Click Close.

End

Figure 11-11. AAL2 Trunk Page (Displaying Menu)

11-24 255-700-762R11.1



Note: Upon initial configuration, this window displays “ADD” in its title; upon updating this configuration, this window displays “VIEW” in its title.

Figure 11-12. ADD AAL2 Trunk Config Entry Window (Top)

Figure 11-13. ADD AAL2 Trunk Config Entry Window (Bottom)

255-700-762R11.1 11-25



The buttons in these windows (not shown above) have the following func-tions:

5 In the GR303 Support field, select Enabled.

6 Select the values for the other fields on this window as described in the following table.

7 Click Add > Close.

End

Button Function

Add Adds this entry to the AAL2 Trunk Configuration table. Dis-played only on the ADD AAL2 Trunk Config Entry Window.

Delete Deletes the selected configuration and removes the entry from the AAL2 Trunk Configuration Table. Displayed only within pages in the VIEW AAL2 Trunk Config Entry Window.


Table 11-10. AAL2 Trunk Config Entry Window Field Descriptions


Slot Default: N/A

Range: Variable

Format: Numeric

Indicates the slot number for the module for which you want to add an AAL2 trunk on the ATM side output. The range of slot numbers varies with the chassis type.

Port/VPN ID Default: N/A

Range: Variable

Format: Numeric

Indicates the port number on the module indicated in the Slot field to which you want to add an AAL2 trunk on the ATM side output. The range of port numbers varies with the module type.


Range: Variable

Format: Numeric

Indicates the channel number associated with the port indicated on the Port field to which you want to add an AAL2 trunk on the ATM side output. The range of channel numbers varies with the module type.

VPI Default: 0

Range: 0–255 (user-to-user interface, out-put side), 0–4095 (network-to-net-work interface, out-put side)

Format: Numeric

Indicates a virtual path identifier value for the ATM output side of the connection. User-to-user and net-work-to-network interface types are configured on the ATM UNI or PNNI Configuration windows.

Note: If using FaxRelayMode on the DSP2C or DSP2D Voice Server Module, the send and receive sides must use the same value.

VCI Default: 0

Range: 32–65535, 5–32 (signaling dis-abled)

Format: Numeric

Indicates a virtual channel identifier value for the ATM output side of the connection. If using FaxRelayMode on the DSP2C Voice Server Module, the send and receive sides must use the same value.

11-26 255-700-762R11.1



VI Default: 0

Range: 0–255

Format: Numeric

Indicates a virtual interface value, which provides bandwidth allocation restrictions for the ATM output side. VI support must be enabled on the appropriate Interface Configuration window.

VUNI Default: 0

Range: 0–255

Format: Numeric

Specifies the virtual ATM UNI identifier, which provides bandwidth allocation restrictions.The VUNI parameter is associated with the egress side of the A to B or the B to A side of the connection.

Traffic Parameters In and Out Panels

Peak Rate(cps) Default: 1

Range: 0–999999999

Format: cps

Indicates the Peak Rate into the ATM side of the con-nection. Enter a peak rate value to set the maximum allowed cell transmission rate (cells per second), defin-ing the shortest time period allowed between cells. When setting this value, calculate the line rate for the module and the amount of bandwidth you are setting up for each interface for the module.

Note: Ensure that the peak cell rate for the connection is correct. The CAC function uses this value to deter-mine whether or not a call can be completed to the sub-scriber line.

Sustained Rate(cps) Default: 1

Range: 0–999999999

Format: cps

Indicates the sustained cell rate into the ATM side of the connection. Enter a SCR with CLP (cell loss priority) =0 (high priority) cells or the peak cell rate (PCR) with CLP=0 cells. For VBR traffic, the value you set is the SCR, or the average cell transmission rate (cells per sec-ond), for the CLP=0 cells, as allowed by your traffic contract. For CBR traffic, the value you set is the PCR, or the maximum allowed transmission rate (cells per second), for the CLP=0 cells, as allowed by your traffic contract. When setting this value, calculate the line rate for the module and the amount of bandwidth you are allotting for each interface on the module.

Max Burst Size(cells)

Default: 1

Range: 0–999999999

Format: cps

Indicates the maximum burst size into the ATM side of the connection. Enter a value for the maximum num-ber of cells that can be received at the peak cell rate. This setting allows a burst of cells to arrive at a rate higher than that of the sustained cell rate. If the burst is larger than anticipated, the additional cells are either tagged or dropped. When setting this value, calculate the line rate for the module and the amount of band-width you are setting up for each interface for the mod-ule.

OC-3c APS Module: When the Traffic Shaping field is set to Enabled, the cell queue depth for the Max Burst Size field is internally set to 1000, regardless of the value you enter. If you enter values other than 1000, these values matter for incoming signalling SPVC/SVC setup from the remote end of the connection.

Table 11-10. AAL2 Trunk Config Entry Window Field Descriptions (Continued)


255-700-762R11.1 11-27



Available Band-width

Default: N/A

Range: variable

Format: cps

Indicates the total ingress and egress bandwidth avail-able for the trunk. This value is based on line rate, or on what you set in the Peak Rate and Sustained Rate fields. Adding CE connections to the trunk decreases the amount of available bandwidth, as indicated in this field.

CDVT Default: 600

Range: 1–65535

Format: Numeric (microseconds)

Specifies the upper boundary of variability in the cell delay variation tolerance (CDVT) for the incoming traf-fic. This value is displayed as a read-only field if the associated interface does not have the value UserCon-fig set in the CDVT Calc Mode field on the interface configuration window.

Bulk Stats Flag Default: Disabled

Range: N/A

Format: Predefined

Specifies whether bulk statistics collection is opera-tional or not on this connection. To configure bulk sta-tistics on this connection, you must perform the follow-ing:

• Configure the bulk statistics server, and enable Bulk Statistics (Feature Turn ON/OFF), and configure the Bulk Statistics connection on the Bulk Statistics Con-figuration window.

• Select Enabled on the Bulk Stats Flag field on the ATM UNI, ATM IISP, or ATM PNNI Interface Configu-ration window, or the AAL2 Trunk Connection Con-figuration window, as appropriate.

Disabled Select to disable the collection of bulk statistics on this connection.

Enabled Select to enable the collection of bulk statistics on this connection.



11-28 255-700-762R11.1



Conformance Type(displayed on the Traffic Parameters In Panel only)

Default: Best-effort

Range: N/A

Format: Predefined

Indicates the type of traffic control option used for ATM cells. The traffic descriptor combination specifies which traffic parameters are used for traffic control, deter-mines the number and type of cells that are admitted into a congested queue, and determines whether high-priority cells are tagged as low-priority cells when traf-fic exceeds traffic parameter thresholds.

Best-effort This traffic descriptor allows the system to attempt to send all cells in a “best-effort” fashion, without specify-ing traffic parameters, similar to the AQueMan algo-rithm.

One-bucket-notag-0plus1

This traffic descriptor uses the parameters one bucket, no tagging, cell loss priority (CLP)=0+1 cells (high and low priority).

Two-bucket-notag-0plus1-0plus1

This traffic descriptor uses the parameters two buckets, no tagging, CLP=0+1 cells (high and low priority) for bucket 1, and CLP=0+1 cells (high and low priority) for bucket 2.

Two-bucket-notag-0plus1

This traffic descriptor uses the parameters two buckets, no tagging, CLP=0+1 cells (high and low priority) for bucket 1, and CLP=0 cells (high priority) for bucket 2.

Two-bucket-tag-0plus1

This traffic descriptor uses the parameters two buckets, CLP=0+1 cells (high and low priority) for bucket 1, and tagging for CLP=0 cells (high priority) in bucket 2.

Best-effort-tag This traffic descriptor allows the system to tag all CLP=0 (high priority) cells to always change them to CLP=1 (low priority) cells. The system then attempts to send all cells in a “best-effort” fashion, without specifying any other traffic parameters, similar to the AQueMan algorithm.

Traffic Shaping Default: Disabled

Range: N/A

Format: Predefined

Specifies whether traffic shaping is enabled or disabled on this connection. The traffic shaping feature uses an input cell selection algorithm (leaky bucket) that smooths bursts of input traffic. See the Peak Rate field in this table for minimum cps range restrictions on these modules.

Disabled Disables traffic shaping.

Enabled Enables traffic shaping. When enabled, the system ensures that the variable bit-rate (VBR) traffic on the egress side of the connection complies with the param-eters of established service contracts.

Connection Features Panel

FailCause B Default: None

Range: N/A

Format: Predefined

Indicates the AAL2 connection status reason code.



255-700-762R11.1 11-29



Load Count Default: Null

Range:

Format: Numeric

Displays the load count.

Oam Status Default: Unsupp

Range: N/A

Format: Predefined

Indicates the type of OAM to be used for the connec-tion.

GR-303 Applications: OAM is not required. Any failure on the ATM side will be detected by the DSP2x module through CAS monitoring.

Unsupp OAM is not in use.

GR-303/V.5 Applications: Do not select a value other than Unsupp if you are configuring AAL2 trunks to an IAD; the feature is not available on AAL2 trunks to IADs.

End-Pt The PSAX system is used as a termination point for ATM traffic, and will process AIS/RDI cells.

OAM loopback test is supported for end-to-end con-nections only.

Note: You must use Release 7.1.0 or later for the value End-Pt to work for GR-303 connections.

End-Seg-Pt Has the characteristics of both an end point and a seg-ment point.

Note: You must use Release 7.1.0 or later for the value End-Seg-Pt to work for GR-303 connections.

Service Type Default: Cbr-1

Range: N/A

Format: Predefined

Specifies a PSAX system-supported quality of service (QoS) class. For a description for the QOS classes, see the section, “Quality of Service Classes for ATM Traffic,” in the Reference Information Appendix of this guide.

For any CBR type selected, the CAC only allows 1 DS0 per connection. For any CBR type selected, the total available bandwidth for all DS0 connections is checked before DSPs are allocated, as VBR has no restrictions on the number of DS0s allowed per connection.

Cbr1 Constant bit rate, queue 1




Ubr Unspecified bit rate

Vbr-nrt2 Variable bit rate, non-real time queue 2

Vbr-nrt1 Variable bit rate, non-real time queue 1

Vbr-rt2 Variable bit rate, real time queue 2

Vbr-rt1 Variable bit rate, real time queue 1

Vbr-express Variable bit rate, express



11-30 255-700-762R11.1



Traffic Flow Default: Duplex

Range: N/A

Format: Predefined

Presents the direction of the flow of data traffic in this connection. Duplex data flows in two directions between the two connection points (interface side A and interface side B).

SimplexA2B Data flows in only one direction from side A to side B.

SimplexB2A Data flows in only one direction from side B to side A.

PointToMultipointA2B

Point-to-multipoint data flows in only one direction, from one point on side A to several points on side B, or from one point on side B to several points on side A.

GR303 Support Default: Disabled

Range: N/A

Format: Predefined

Disables or enables support for the GR-303 interface.

Disabled Disables the GR-303 interface.

Enabled Enables the GR-303 interface. This field must be enabled if you are using AAL2 trunking on a GR-303 interface.

Connection Status Default: Inactive

Range: N/A

Format: Predefined

Indicates the current status of the connection. The value indicates whether the connection is passing traf-fic.

Inactive The connection is inactive and not passing traffic.

Active The connection is active and passing traffic.

Combined Use Timer

Default: 4

Range: 0–99

Format: Numeric

Specifies the amount of time the host processor will wait for a cell to fill. The combined use timer (CuTimer) is set to zero, so that every ATM cell transmitted con-tains only one AAL2 packet. The first octet of the AAL2 packet header follows immediately after the Start Field in the ATM cell payload. If the AAL2 packet payload is less than 44 octets, the remainder of the ATM cell pay-load following the end of the AAL2 packet is filled with zeros as padding. Each increment of CuTimer is 5 msec waiting time. The default value 4 indicates a wait of 20 msec (4 x 5 msec) before an ATM cell is sent out.

If using the DSP2E/F Voice/Data Server modules, set this value to 1 (5 msec.).

GR-303 Applications: Set the value to 0 if using non-Lucent IADs.

V5.2 Applications: Set the value to 0 if fax or modem calls are supported. Any value greater than 0 causes jit-ter to drop fax/modem calls.



255-700-762R11.1 11-31



IWF Type Default: None

Range: N/A

Format: Predefined

Specifies the Interworking Function type on assigning AAL2 connections to compatible DSPs on the DSP2C through DSP2F Voice Server modules.

None Allows the assignment of standard AAL2 connections to DSPs on the DSP2C Voice Server module that are configured as AlgoSet1 through AlgoSet3, on the DSP2D as AlgoSet1 and AlgoSet6, and on the DSP2E as AlgoSet6. This parameter allows the mixture of pure voice (CE-to-ATM) with data (VBR-to-ATM) in the same AAL2 trunk group, such as is used in the V5.2 interface.

Packet-pipe Allows the assignment of standard AAL2 connections to DSPs on the DSP2E/F modules that are configured as AlgoSet7. This parameter will not allow the mixture of pure voice (CE-to-ATM) with data (VBR-to-ATM) in the same AAL2 trunk group. This value supports appli-cable connection types for pure data (VBR-to-ATM) in wireless applications.

Note: Packet-pipe cannot be used on the DSP2C/D Voice Server modules.

GSM Allows the assignment of standard AAL2 connections to DSPs on the DSP2E/F modules that are configured as AlgoSet8.

This parameter will not allow the mixture of pure voice (CE-to-ATM) with data (VBR-to-ATM) in the same AAL2 trunk group.

Note: GSM cannot be used on the DSP2C/D Voice Server modules.



11-32 255-700-762R11.1



DSP Resource Selection

Default: Automatic

Range: As noted below

Format: Predefined

Specifies how connections through DSP resources are to be re-routed in the event of DSP resource failure. (A DSP resource is a single channel on any DSP2x mod-ule).

The setting you select in this field must match the set-ting in the Selection Type column on the Dsp Resource Management Table (after the site-specific DSP Resource Configuration option), or your connections will not be assigned or activate.

Automatic If a DSP resource fails, connections are rerouted by a software DSP resource manager that selects replace-ment DSPs from a chassis-wide pool.

Manual If a DSP resource fails,If a DSP resource fails, the DSP resource manager selects DSPs from a particular mod-ule designated in DSP Slot ID field.

DSP Slot ID Default: 1


Format: Numeric

Specifies the slot number of the DSP2x Voice Server module from which the DSP Resource Manager selects replacement DSPs in the event of active DSP resource failure. If you selected Manual in the Dsp Resource Selection field, you must specify the DSP2x Voice Server module slot number in the DSP Slot ID field from which you want the DSP Resource Manager to select DSPs. If no DSP resource is available on the DSP2x module in the specified slot, the connection is rejected. If you selected Automatic in the Dsp Resource Selection field, the DSP Slot ID field displays which DSP2x module slot the trunk is using after it has been bound to a DSP2x module.

Num of DSP Reserved Chnl

Default: 0

Range: 0–384

Format: Numeric

Specifies the number of DS0s that can be reserved as DSP channels. If the IWF Type is Packetpipe, the bandwidth configured by you for the trunk calculates how many DS0s fit into the trunk. For example, the DS0 line rate is approximately 171 cps. If you want 200 cps, the bandwidth actually allocated is 200/171, or 1.16 DS0s.

If you have selected Packet-pipe in the Dsp Iwf Type field, how bandwidth is assigned to the DSP channels also depends on what type of CBR or VBR you select in the Service Type field (see the Dsp Iwf Type and Service Type fields for more details).

The CAC reserves the DS0 resources when the first con-nection is made on the trunk.

If the value is left at the default 0, the number of reserved DS0s is best-effort.



255-700-762R11.1 11-33



Provisioning a GR-303 AAL2 PVC Connection

Perform the steps in the following procedure to create a GR-303 AAL2 PVC connection.

Begin

1 In the Device window, click the Connections tab.

The Listing page appears.

2 Right-click any are within the Listing page and a menu appears (see Figure 11-16). Select Create New.

The Create window appears (see Figure 11-14).

3 Select GR303 for the Side A panel, and the slot, port, and channel values for the ATM interface created in the section, “Configuring ATM I/O Mod-ule Values” for the Side B panel.

4 Click Create.

The Create GR303 AAL2 PVC VCC Connection window appears, display-ing the Primary page (see Figure 11-15). The Primary page displays the information used to create the connection.

Figure 11-14. Create Connection Window

11-34 255-700-762R11.1




6 From the GR303 System-Wide tab, create interface group 1, using the primary and backup channel IDs you previously created.

End

Figure 11-15. Create GR303 AAL2 PVC VCC Connection Window

Table 11-11. Display Connection: GR303_AAL2_VCC_PVC Window Field Descriptions


GR303 Interface Panel

IG ID Default: 0

Range: 1–84

Format: Numeric

Specifies the interface group identifier number.

Ensure that the value in the IG ID field matches the value of the Interface Group ID field you con-figured on the ADD GR303 IG Configuration Entry window.

Call Reference Default: 0

Range: 1–2048

Format: Numeric

Specifies a number mapped to the customer phone number on a current connection. Used by the system management entity for call status tracking purposes.

255-700-762R11.1 11-35



[Conn Status] Default: Inactive

Format: Predefined

Specifies whether the connection is active (pass-ing traffic) or inactive (not passing traffic).

Inactive Indicates that the connection is not passing traf-fic.

Active Indicates that the connection is passing traffic.

Interface AAL2 Interface Panel

Slot Default: 0

Range: Chassis depen-dent

Format: Numeric

Specifies the slot in use for the AAL2 trunk side of the connection.

Port Default: 0

Range: Module depen-dent

Format: Numeric

Specifies the port in use in the slot for the AAL2 side of the connection.

Channel Default: 0

Range: Port dependent

Format: Numeric

Specifies the channel of the port in use in the slot for the AAL2 side of the connection.

VPI Default: 0

Range: 1–4095

Format: Numeric

Specifies the virtual path indicator.

VCI Default: 0

Range: 1–65535

Format: Numeric

Specifies the virtual channel indicator, a 16-bit field in the ATM cell header identifying the VC in which the data will travel from transmit device to receive device. The VC is located within the vir-tual path.

AAL2 Cid Default: 0

Range: 16–255

Format: Numeric

Specifies the AAL2 Channel Identifier. The AAL2 CIDs are located within the VCC (0–15 is reserved).

ConnectionFeatures

Note: In the on-hook monitoring state, the CAS refresh rate for all ITU-T profiles below is 5 seconds.

Table 11-11. Display Connection: GR303_AAL2_VCC_PVC Window Field Descriptions (Continued)


11-36 255-700-762R11.1



Encoding Profile Default: Itut-profile-1

Range: N/A

Format: Predefined

Specifies the ITU-T or ATM Forum parameter set that applies to the connection. A parameter set specifies the compression algorithm used, packet size, whether silence detection is included, and so on. For more information on ATM Forum pro-files, see the reference appendix in this guide.

Note: See the Valid Encoding/Compression Set-tings table following this table for a list of the compression and silence detection settings that are valid for the PSAX system and the CellPipe IAD when they are configured as interoperating devices. See also the ITU-T Transmission Profile Tables in the reference appendix of this guide.

Note: The Cellpipe IAD supports only the follow-ing profiles: ITU-T Standard Profile 1 and ATM Form Standard Profiles 9–11.

Itut-profile-1 Indicates that the connection uses the ITU-T Standard profile-1. This profile supports PCM G.711-64 Kbps (no compression).

Note: In the on-hook monitoring state, the CAS refresh rate for all ATM Forum profiles below is 5 minutes.

Af-profile-9 Indicates that the connection uses the ATM Form Standard Profile 9. This profile supports PCM-64, ADPCM-32, and silence detection. Data is trans-mitted in 44-octet packets.

Af-profile-10 Indicates that the connection uses the ATM Form Standard Profile 10. This profile supports PCM-64, ADPCM-32, without silence detection. Data is transmitted in 44-octet packets.

Af-profile-11 Indicates that the connection uses the ATM Form Standard Profile 11. This profile supports PCM-64, ADPCM-32, without silence detection. Data is transmitted in 40-octet packets.

Default Indicates that the connection uses the default encoding profile of the AAL2 trunk configura-tion.



255-700-762R11.1 11-37



Voice Compression Default: None

Range: N/A

Format: Predefined

Specifies the ITU-T standard of voice compression in Kbps.

Note: The CellPipe IAD requires the setting None or G726-32k.

None Indicates that no voice compression is used on this connection.

G726-16K Indicates that voice compression at 16 Kbps is used according to the ITU-T G.726 standard.

G726-24K Indicates that voice compression at 24 Kbps according to the ITU-T G.726 standard.



G729a-8K Indicates that voice compression at 8 Kbps according to the ITU-T G.729a standard.

Silence Detection Default: Disabled

Range: N/A

Format: Predefined

Specifies whether silence detection will be used on this connection or not. You can specify if you want periods of silence in the connection to gen-erate cells or not. To conserve bandwidth, select enabled.

Note: You must select Disabled if using the Cell-Pipe IAD.

Disabled Disables silence detection. Cells will be sent dur-ing silent periods in the connection.

Enabled Enables silence detection. No cells will be sent during silent periods in a connection.

Echo Cancellation Default: None

Range: N/A

Format: Predefined

Specifies what type of echo cancellation will be used on the connections. Echo cancellation allows for the isolation and filtering out of unwanted signals caused by echoes from the main transmitted signal. Echo strength is mea-sured in “tails” in msec.

G168 ITU-T Standard G.168.

Note: Select this value for the GR-303 Interface.

Tone Detection Default: Disabled

Range: N/A

Format: Predefined

Specifies what kind of fax or modem tone the connection will detect or bypass.



11-38 255-700-762R11.1



Viewing a GR-303 AAL2 PVC Connection

Perform the steps in the following procedure to view an existing GR-303 AAL2 PVC connection.

Begin

1 In the Device window, click the Connections tab.

The Listing page appears.

2 Select a GR-303 AAL2 entry in the Listing page and click the right mouse button.

Coding Translation Default: None

Range: N/A

Format: Predefined

Specifies the coding translation type on the con-nection. Mu law is the Japanese and North American PCM coding and companding standard. A law is the European PCM coding and com-panding standard.

Note: Use None or MuLaw2muLaw for the GR-303 Interface.

None Indicates that the coding translation type is auto-matically set to the Mu law to Mu law standard for the connection, even though the field displays the value None.

MuLaw2muLaw Indicates that the coding translation type is Mu law to Mu law.

ALaw2aLaw Indicates that the coding translation type is A law to A law.

MuLaw2aLaw Indicates that the coding translation type is Mu law to A law.

ALaw2muLaw Indicates that the coding translation type is A law to Mu law.

ALT Line Type Default: Alt-loopStart

Range: N/A

Format: Predefined

Specifies the analog line termination type used on this connection.

Note: Select the value Alt-loopStart or Alt-GroundStart for the GR-303 Interface.

Alt-loopStart Indicates that the line or trunk is seized by bridg-ing through a resistance tip and ring.

Note: This value is valid for the GR-303 interface.



255-700-762R11.1 11-39



3 Select Display in the menu that appears (see Figure 11-16).

The Display Connection window appears, displaying the Primary page (see Figure 11-17).

4 You may edit this connection by selecting the values for the fields in this window as described in Table 11-11.

5 Click Create > Close.

6 To save this connection in the PSAX system configuration database, click Device > Save PSAX Configuration in the Device Menu Bar.

End

Figure 11-16. Listing Page with GR-303 AAL2 Entry Selected (Displaying Menu)

Figure 11-17. Display Connection: GR303_AAL2_PVC_VCC Window

11-40 255-700-762R11.1


Chapter 11 Configuring the GR-303 Voice GatewaySaving Your Configuration

Saving Your Configuration



255-700-762R11.1 11-41


Chapter 11 Configuring the GR-303 Voice GatewaySaving Your Configuration

11-42 255-700-762R11.1


12 Configuring the H.248 Protocol

Overview of This ChapterThis chapter describes how to perform the following tasks:

• Enabling the H.248 protocol feature on a PSAX system

• Setting the call control value for the H.248 protocol feature

• Rebooting the PSAX system

• Setting site-specific values for the H.248 protocol feature

• Enabling channelization and signaling gateway on an I/O module

• Configuring the TIDs for the module slot and ports

• Generating the logical TIDs for the module channels

Before attempting the H.248 protocol configuration, users should be thor-oughly familiar with basic configuration of channelized DS1 and DS3 mod-ules, the call control resource allocation procedure, and the chassis reboot procedure. See these procedures in the Configuring the Basic System chapter in the appropriate PSAX user guide. For module port, channel, and interface configuration on DS1 or DS3 modules, see the appropriate PSAX module user guides.

Note: Several scenarios are described in Chapter 3 of this guide using the console interface. Although these scenarios are not described in this chapter, you can perform them in a similar fashion while using the EMS-PSAX.

Enabling the H.248 Protocol FeatureThe following procedures turn on the H.248 protocol feature, configure the call control resources, activates the feature in the PSAX system.

Turning On the H.248 Protocol Feature

Perform the following procedure to enable the H.248 protocol feature in the PSAX system.

Begin


The Site-Specific page is displayed (see Figure 12-1).


255-700-762R11.1 12-1

Chapter 12 Configuring the H.248 ProtocolEnabling the H.248 Protocol Feature


The Feature Turn On/Off Configuration page is displayed (see Figure 12-2).

3 Select the Feature value H248 on this window.

4 Click the right mouse button and a menu is displayed (see Figure 12-3).



12-2 255-700-762R11.1



5 To enable the feature, select Turn On Selected Feature. To disable the fea-ture, select Turn Off Selected Feature.

An informational window is displayed (see Figure 12-4).

6 Click OK.

7 Perform the procedure, “Configuring Call Control Resources,” to set the call control allocation.

End

Configuring Call Control Resources

Perform the following procedure to configure the call control resource set-tings for the H.248 MGC.

Begin


The Call Control page is displayed (see Figure 12-5).



255-700-762R11.1 12-3



2 On this window, change the cgSvcCutThroughOption field value to CgS-vcCgExplicitCutThrough.

3 Click Apply.

An informational window is displayed (see Figure 12-6).

4 Click OK.

5 In the Provisioning Menu Bar, click Device > Save PSAX Configuration. (see “Saving the System Configuration” on page 6-22 to save the modifi-cations).

6 Perform the following procedure, “Rebooting the PSAX System”, to reboot the PSAX system.

End


Figure 12-6. Call Control Confirmation Window

12-4 255-700-762R11.1


Chapter 12 Configuring the H.248 ProtocolConfiguring the H.248 Protocol Feature Parameters

Rebooting the PSAX System

Perform the following procedure to reboot (initialize) the PSAX system.

Note: Only users with Administrator access privileges can restart hard-ware components.

Begin


The Diagnostics page is displayed.

2 In the Restart Hardware Components panel, select Entire Chassis from the pull-down menu (see Figure 12-7) and click Restart.

3 Click Restart.

A confirmation window is displayed (see Figure 12-8).

4 Click Yes in the confirmation window to restart the hardware compo-nent. Click No to cancel.

End

Configuring the H.248 Protocol Feature ParametersThe following procedures provide instructions to access the H.248 protocol feature parameters, configure the MGC communication links, congestion handling, and tone generation and detection parameters.

Figure 12-7. Restart Button

Figure 12-8. Restart Hardware Component Confirmation Window (Primary CPUn Module)

255-700-762R11.1 12-5



Accessing the H.248 Protocol Feature Parameters

Perform the following procedure to set the H.248 protocol feature parameters such as the number of contexts, terminations, timer values, and execution times.

Begin


The Site-Specific page is displayed.


The Special Features page is displayed.

3 Click the H.248 Configuration tab.

The H.248 Management and Configuration page is displayed (see Figure 12-9). The buttons in the H.248 windows are described in Table 12-1.

Figure 12-9. H.248 Configuration Page

12-6 255-700-762R11.1



4 Right-click within the H.248 Management and Configuration page, and a menu is displayed (see Figure 12-10). The menu selections are described in Table 12-2.

5 Select the following options in turn and perform the procedures described for each option:

a Transport and Resource, see “Establishing the PSAX System to MGC Communication Links” on page 6-8

b Congestion Handling, see “Configuring the Congestion Handling between the PSAX System to MGC” on page 6-11

c Tone Generation and Detection, see “Configuring the Tone Genera-tion and Detection Parameter” on page 6-12

Note: The call tracing options are described in Chapter 7.

6 When completed with this process, save the changes, see “Saving the System Configuration” on page 6-22.

7 Continue the configuration process by configuring the TIDs at the mod-ule, port, and channel levels, see “Configuring the H.248 TIDs on the TDM-interface Modules” on page 6-13

End

Table 12-1. Buttons for the H.248 Configuration Page

Button Function

Apply Sets the values selected on the page or window.

Refresh Updates the values on this page or window by retrieving the associated MIB values from the PSAX system.

Retrieve Searches for a configured termination ID (from the H.248 Ter-mination Access window).


Figure 12-10. H.248 Configuration Page (Displaying Menu)

255-700-762R11.1 12-7



Establishing the PSAX System to MGC Communication Links

Perform the following procedure to set the H.248 transport connection parameters between the PSAX system and the MGC and base root package parameters.

Begin

1 Select the Transport and Resource menu option.

The H.248 Transport and Resource window is displayed (see Figure 12-11).



4 Continue the process with the following procedure, see the section, “Configuring the Congestion Handling between the PSAX System to MGC.”

End

Figure 12-11. H.248 Transport and Resource Window

12-8 255-700-762R11.1



Table 12-3. H.248 Transport and Resource Window Field Descriptions


MGC IP Address Panel

MGC IP Address1 MGC IP Address2 MGC IP Address3 MGC IP Address4

Default: 0.0.0.0

Range:


Specifies the MGC that controls the parts of the call state that pertain to connection control for media channels in the PSAX system. Enter up to four IP addresses. The PSAX system connects with the first MGC IP address that responds to a ping, starting with MGC IP Address1. The MGC must be config-ured to respond to a ping request for address avail-ability. MG is the PSAX system in these field descriptions.

Transport Protocol Type

Default: Tcp

Range: N/A

Format: Predefined

Specifies which type of IP transport protocol is used between the PSAX system and MGC for H.248 mes-sage transport.

Tcp Selects TCP as the transport protocol.

Stcp Selects SCTP as the transport protocol.

Message Encoding Format

Default: Text-std

Range: N/A

Format: Predefined

Specifies the text encoding format for the H.248 protocol transfer between the MGC and PSAX sys-tem.

Text-std Selects a standard text encoding format.

Text-cpt Selects a compact text encoding format that includes short keywords without unnecessary line breaks.

ACK from MG Default: Disabled

Range: N/A

Format: Predefined

Specifies whether the PSAX system acknowledges reply messages from the MGC with Transaction ResponseAck messages.

Disabled Disables the PSAX system from acknowledging reply messages from the MGC with Transaction ResponseAck messages.

Enabled Enables the PSAX system to acknowledge reply messages from the MGC with Transaction Respon-seAck messages.

Maximum Number of Terminations

Default: 2000

Range: 1–16000

Format: Numeric

Specifies the maximum number of terminations permitted on the PSAX system (). Each time you change this value, you must apply, save the config-uration, and perform a chassis reboot on the PSAX system.

Base Root Package Panel

Maximum Number of Contexts

Default: 1000

Range: 10–8000

Format: Numeric

Specifies the maximum number of contexts that can exist simultaneously on the PSAX system. As one context is always the null context with a default of 1000, 999 contexts are possible for con-texts other than null. Each time you change this value, you must apply, save the configuration, and perform a chassis reboot on the PSAX system.

255-700-762R11.1 12-9



Configuring the Congestion Handling between the PSAX System to MGC

Perform the following procedure to set the H.248 congestion handling parameters between the PSAX system and the MGC.

Begin

1 Right-click within the H.248 Management and Configuration page, and a menu is displayed (see Figure 6-10).

2 Select the Congestion Handling menu option.

The H.248 Congestion Handling window is displayed (see Figure 12-12).

Maximum Termi-nations Per Context

Default: 2

Range:

Format: Numeric

Specifies the maximum number of terminations possible in each non-null context. Currently, this field value cannot be changed.

Normal MG Execu-tion Time

Default: 1000

Range: 0 or 100–9999

Format: Numeric (milliseconds)

Specifies the interval within which the MGC expects a response to any transaction from the PSAX system (exclusive of the network delay). If this value is set to 0, no pending acknowledgement is sent by the PSAX system. For values between 100 and 9999, if the PSAX system does not respond in the specified time, a Pending Response is sent to the MGC.

Normal MGC Exe-cution Time

Default: 1000

Range: 100–9999


Specifies the interval within which the PSAX sys-tem expects a response to any transaction from the MGC (exclusive of the network delay). Currently, this field value cannot be changed.

MG Provisional Response Timer Value(msec)

Default: 1000

Range: 100–9999


Indicates the time within which the MGC should expect a Pending Response from the PSAX system if a Transaction cannot be completed. Initially set to Normal MG Execution Time, plus network delay, but may be lowered. Currently, this field value can-not be changed.

MGC Provisional Response Timer Value(msec)

Default: 0

Range: 0 or 100–9999


Indicates the time within which the PSAX system should expect a Pending Response from the MGC if a Transaction cannot be completed. Initially set to Normal MGC Execution Time, plus network delay, but may be lowered. If no reply response or pend-ing response is received by the PSAX system within the time period specified, the PSAX system will resend the transaction one more time. If the value is set to 0, the transaction will never be resent.

Table 12-3. H.248 Transport and Resource Window Field Descriptions (Continued)


12-10 255-700-762R11.1





5 If necessary, continue the configuration process with the following pro-cedure, see “Configuring the Tone Generation and Detection Parameter” on page 6-12.

If the following procedure is not required, continue the configuration process by saving the H.248 protocol feature configuration, see “Saving the System Configuration” on page 6-22.

End

Figure 12-12. H.248 Congestion Handling Window

Table 12-4. H.248 Congestion Handling Window Field Descriptions


MGCon (MG Con-gestion) Event

Default: Off

Range: 1–100

Format: Predefined

Specifies whether the 'MGCon' event is enabled for disabled. The 'MGCon' event can also be enabled or disabled through the H.248 protocol

Off Disables the 'MGCon' event.

On Enables the 'MGCon' event.

Congestion Moni-toring Window Size (Tick)

Default: 180

Range:

Format: Numeric ticks. 1 tick = 1/60 second

Specifies the H.248 congestion monitoring win-dow size in ticks (1 second = 60 ticks).

Maximum Contexts Created per Win-dow

Default: 60

Range:

Format: Numeric ticks. 1 tick = 1/60 second

Specifies the maximum number of context cre-ated by Add Requests allowed per Congestion Monitoring Window.

Maximum Termi-nations Added per Window

Default: 180

Range: 1–10000

Format: Numeric

Specifies the maximum number of termination Add Requests allowed per Congestion Monitor-ing Window.

255-700-762R11.1 12-11



Configuring the Tone Generation and Detection Parameter

Perform the following procedure to set the H.248 tone generation and detec-tion parameter.

Note: This procedure is only required when the PSAX system includes a Tones and Announcements Server module (23N28)

Begin


2 Select the Tone Generation Detection menu option.

The H.248 Tone Generation Detection window is displayed (see Figure 12-13).

3 Enter a value for the field on this window as described in Table 12-3.


5 Continue the process by saving the H.248 protocol feature configuration, see the section, “Saving the Configuration.”

6 Continue with the following procedure to configure the module TIDs, see the section, “Configuring the H.248 TIDs on the TDM-interface Mod-ules.”.

End

Maximum AAL2 Requests per Win-dow

Default: 180

Range: 1–10000

Format: Numeric

Specifies the maximum number of EME AAL2 setup requests allowed per Congestion Monitor-ing Window.

System Congestion Level %

Default: 0

Range: 1–10000

Format: Numeric

Displays the system congestion level percentage. A 0 % indicates no system congestion.

Load Reduction % Default: 0

Range: 1–100. See choices at right.

Format: Numeric

Displays the requested load reduction percentage to the MGC. A 0 % indicates no load reduction.

Table 12-4. H.248 Congestion Handling Window Field Descriptions (Continued)


Figure 12-13. H.248 Tone Generation Detection Window

12-12 255-700-762R11.1


Chapter 12 Configuring the H.248 ProtocolConfiguring the H.248 TIDs on the TDM-interface Modules

Configuring the H.248 TIDs on the TDM-interface Modules

Prerequisites for Configuring the H.248 TIDs

Perform the following procedure to enable the Channelization and the Sig-naling Gateway features. The 21-Port High-Density E1 Multiservice module is used in this section as an example.

Begin

1 On the Front Panel window, select an unconfigured port of a module that supports the H.248 protocol feature.

The corresponding module port and channel configuration window is displayed (see Figure 12-14).

2 Select Enabled in the Channelization field.

Table 12-5. H.248 Tone Generation and Detection Window Field Descriptions


DTMF Tone Dura-tion

Default: 200

Range: 40–64000

Format: Milliseconds

Specifies the DTMF tone duration for the Tones and Announcements Server module (23N28) DTMF tone generation when the PSAX system is controlled by the MGC. The module must be installed and configured in the PSAX system to be controlled by the MGC.

Figure 12-14. High-Density E1 Port and Channel Configuration Window

255-700-762R11.1 12-13



3 Select Enabled in the SG Feature (signaling gateway) field.

4 Click Apply.

By enabling the Channelization and Signaling Gateway feature, you can proceed to the task of slot and port configuration for the H.248 protocol feature.

End

Configuring the Pseudo TID at the Slot Level

Begin

1 From the Device Tree, select an unconfigured port of a module that sup-ports the H.248 gateway control protocol.

2 Right-click the mouse and a menu appears (see Figure 12-15). Select Configure H248 TID.

The Terminal ID Configuration window is displayed (see Figure 12-19).

3 Select the values for the fields on this window from the following table:

4 In the Pseudo Termination ID field, type your trunk name and the literal string as instructed on the Pseudo Termination ID field. The string instructs the H.248 system software to assign the physical port on this slot to the H.248 protocol.

5 At this time in the configuration, the H.248 Activation field should say Disable. If it says Enable, follow the instructions for this field in the Buttons table above.

6 Click Apply TID.

In this example, the Pseudo Termination ID field will display: Client_Trunk001/1/<lp>/<ch>. Note that the <pp> string has been replaced by “2.” This means that the media gateway controller (MGC) now recognizes the slot physical port 2.

7 Click Apply Activation.

Clicking this button activates the H.248 protocol for the selected slot.

Figure 12-15. Slot Menu (Displaying H.248 Option)

12-14 255-700-762R11.1



8 Click Close.

End

The next task is to select an available channel and configure the channel.

The buttons on this window are described in Table 12-6.

Figure 12-16. Terminal ID Configuration Window (Slot)

Table 12-6. Buttons for the Terminal ID Configuration (Slot) Window

Button Function

Apply TID Applies the Termination ID configuration.

Apply Activation Applies the Enabled or Disabled field value in the H.248 Activation field.

Note: If the H.248 Activation field displays the value Dis-abled, do nothing. If Enabled is displayed, then all the ready terminations associated with this port and then reset the H.248 Activation field, using the Reset button. The field will then display Disabled.

Reset Resets the fields to the last set of saved values.

Close Closes the H248 Termination ID Configuration window.

255-700-762R11.1 12-15



Table 12-7. Termination ID Configuration (Slot) Window Field Descriptions


[Slot] Default: 1


Format: Numeric

Indicates the slot number for the assigned module that is being configured with a TID.

Pseudo Termina-tion ID

Default:

Range: 1–32.

Format: Alphanu-meric:

Selects a unique identifier used by the MGC to control termination of the selected slot and subsequently the ports and channels. A logical TID can be assigned either manually or automatically through a pseudo TID template. The template provides a structured for-mat to enter the TID for all ports and channels on the selected slot (module), see Rules for Assigning TIDs below. The TID can be configured at the slot, port, and channel level. If you do not want to assign all slot- or port-wide channels using the template option, manu-ally type in the trunk name, physical port, logical port, and channel(s) you want to configure.

H.248 Activation Default: Disable

Range: N/A

Format: Predefined

Specifies whether the H.248 protocol feature is acti-vated on the selected module. This field is displayed only if you are configuring a channel for any interface type other than circuit emulation.

Disable Disables the H.248 protocol feature access to the TIDs.

Enable Enables all entered terminations associated with this slot. Enable is a transient action state. After the Apply ACTIVATION command is applied, Enable displays while the activation is being applied; after activation is completed, the field displays Disable, which is the current and desired state. The reason for this behavior is that activation is completed as a batch command; the user cannot know how many TIDs are activated. To determine if a TID is activated, go to the Termination ID Configuration window. If the H.248 Activation field displays Enable, then the selected TID is activated.

Rules for Assigning TIDs

TID template – Trunk_Name/<pp>/<lp>/<ch>

• Trunk_Name is a unique user-assigned trunk name that can be up to 32 characters long and consist of alphabetic (A–Z and/or a–z), numeric (0–9), or underscore (_) characters.

• Slash (/) is required as a separator between each item.

• The literal string, <pp>/<lp>/<ch>, assigns the physical port <pp>, logical port <lp> and channel <ch> numbers. Must enter this string as is at the slot level to allow subsequent TIDs to be properly formatted.

• TIDs are not case-sensitive.

• All TIDs must have unique ID strings in order to be valid.

• The TID “root” is reserved and cannot be used.

12-16 255-700-762R11.1



Configuring the Pseudo TID at the Port Level

Perform the following procedure to configure the port level TIDs on the TDM-interface module. This can be done whether the TDM-interface slot level was previously configured or not.

Begin

1 On the Front Panel, select an unconfigured port of a module that sup-ports the H.248 protocol feature.

2 The corresponding Port and Channel Configuration window is displayed.

3 Click H248 TID.

The Terminal ID Configuration window is displayed (see Figure 12-19).

Note: The trunk name shown in Figure 12-19 is for example purposes only.

4 Select the values for the fields on this window from Table 12-3.

5 In the Pseudo Termination ID field, type your trunk name and the literal string as instructed on the Pseudo Termination ID field. The string instructs the PSAX system to assign the physical port trunk name to this slot.

6 At this time in the configuration, the H.248 Activation field should say Disable. If it says Enable, follow the instructions described in Table 12-8.

7 Click Apply TID.

In this example, after the Apply TID button is applied, the Pseudo Ter-mination ID field displays Client_Trunk001/2/<lp>/<ch>. Note that the <pp> string has been replaced by a “2.” This means the MGC now recog-nizes physical port 2.

8 Click Apply Activation.

Clicking this button activates the H.248 protocol for the selected port.

The following new information is added on the window: [Port: 02] field has been added to the display after TID configuration. This is a local con-figuration on the PSAX system. The MGC cannot “see” this configura-tion, as the logical port and associated channels are not yet generated.

9 Click Close.

Figure 12-17. Terminal ID Configuration Window (Port)

255-700-762R11.1 12-17



10 When completed, to return to the port and channel configuration win-dow and repeat this procedure on the other available ports that are going to be controlled through the H.248 protocol feature, then go to Step 11.

11 Continue with the next procedure, “Configuring the Logical TID at the Channel Level”, to configure the channel TID.

End

Buttons The buttons on this window are described in Table 12-8.

Table 12-8. Buttons for the Terminal ID Configuration (Port) Window

Button Function

Apply TID Applies the Termination ID configuration.

Apply Activation Applies the Enabled or Disabled field value in the H.248 Activation field.

Note: If the H.248 Activation field displays the value Dis-abled, do nothing. If Enabled is displayed, then all the ready terminations associated with this port and then reset the H.248 Activation field, using the Reset button. The field will then display Disabled.

Reset Resets the fields to the last set of saved values.

Close Closes the H248 Termination ID Configuration window.

Table 12-9. Termination ID Configuration (Port) Window Field Descriptions


[Slot] Default: 1


Format: Numeric

Indicates the slot number for the assigned mod-ule that is being configured with a TID.

[Port] Default: 1

Range: Module dependent

Format: Numeric

Indicates the port number for the assigned mod-ule that is being configured with a TID.

Pseudo Termina-tion ID

Default: 1


Format: Numeric

Selects a unique identifier used by the MGC to control termination of the port and subsequently the channel. A logical termination ID can be assigned either manually or automatically through a pseudo termination ID specified from a higher level (slot). The TID template can be used to assign logical termination IDs to all ports and channels on the selected slot (module).

12-18 255-700-762R11.1



Configuring the Logical TID at the Channel Level

Perform the following procedure to configure the channel level on the TDM-interface module. This can be done whether the TDM-interface slot/port level was previously configured or not.

Begin

1 From the port and channel configuration window, click the Channel Configuration tab.

The Channel Configuration page appears.

2 Select an available channel.

Note: Leave the Signaling field at the default Disabled setting.

3 Select CircuitEmulation in the Interface field.

4 Click Apply to Selected.

5 Right-click the mouse and a menu appears (see Figure 12-18). Select Configure H248 TID.

H.248 Activation Default: Disabled

Range: N/A

Format: Predefined

Specifies whether the H.248 protocol feature has access to the TID.

Disabled Select to disable access to the TID through the H.248 protocol feature.

Enabled Select to enable access to the TID through the H.248 protocol feature.

Table 12-9. Termination ID Configuration (Port) Window Field Descriptions (Continued)


Figure 12-18. Channel Configuration Menu (Displaying H.248 Option)

255-700-762R11.1 12-19



The H.248 Termination ID Configuration window is redisplayed, with additional information (see Figure 12-19).

On this window, note that the Logical Termination ID field now shows the logical port 1 and channel 1 in addition to the physical port 2 shown on the Pseudo Termination ID window. This indicates that the MGC acknowledges the logical termination, whereas prior to TID activation, the MGC did not recognize the pseudo termination ID.

Also note that this configuration only applies to one channel, 1 in the Logical Termination ID field. The configured channel also shows in the Channel display-only field under the window title. The PSAX device can-not simultaneously configure all channels on a port for H.248 at this time. If you desire configure other channels for H.248 at this point, you must return to the Port and Channel Configuration window of the mod-ule you are using and individually select an additional channel to be con-figured for circuit emulation and apply the configuration. This will auto-matically apply H.248 protocol to the selected channel, which you can verify by clicking H248 TID.

The Termination ID Configuration window (channel level) is displayed (see Figure 12-19). Table 12-3 describes the fields on the window.

• Go to Step 10, if the previously configured port level TID was created with the TID template, and the trunk name and physical port number are displayed in the Logical Termination ID field (trunkname001/2/<1>/<01>), nothing more needs to be done with this window if the TID is correct for the configuration.

• Go to Step 6, if the slot-level TID was not configured at the slot level and the Logical Termination ID field is blank and a TID is required.

6 Use the template described in Table 6-7 to enter the TID value for the channel as required.

7 Select the Apply TID button. The TID is saved at this level.

8 Select the H.248 Activation field and change Disabled to Enabled.

9 Select the Apply Activation button.

The H.248 Activation: field displays Disabled (see Table 6-7 for an explanation of the H.248 Activation field).

10 When completed, Press Ctrl+G to return to the Console Interface Main Menu window and select the Save Configuration [Modified] option to save the TID configuration.

11 Repeat this procedure on the other available channels that are going to be controlled through the H.248 protocol feature, then go to Step 12.

12 Continue the process by configuring the ATM interface modules.

Figure 12-19. Terminal ID Configuration Window (Channel)

12-20 255-700-762R11.1


Chapter 12 Configuring the H.248 ProtocolSaving the System Configuration

On a DS1 module, you can run a script to configure up to 144 channels. On a DS3 module, you can run a script to configure up to 672 channels. Slots, ports and channels configured for H.248 can only be changed by deleting the configuration before applying another configuration.

End

Saving the System Configuration


Table 12-10. Termination ID Configuration (Channel) Window Field Descriptions


[Slot] Default: 1


Format: Numeric

Indicates the slot number for the assigned module that is being configured with a TID.

[Port] Default: 1


Format: Numeric

Indicates the port number for the assigned module that is being configured with a TID.

[Channel] Default: 1


Format: Numeric

Indicates the channel number for the assigned mod-ule and port that is being configured with a TID.

Logical Termina-tion ID

Default: N/A


Format: Predefined

Selects a unique identifier used by the MGC to con-trol termination of the channel. A logical termination ID can be assigned either manually or automatically through a pseudo termination ID specified from a higher level (slot, physical port, or logical port). The TID template can be used to assign logical termina-tion IDs to all channels on the selected slot or port.

[H.248 Activation] Default: Disable

Range: N/A

Format: Predefined

Displays whether the pseudo TID is controlled through the H.248 protocol feature.

Disable Indicates the last setting of the pseudo TID before the H.248 protocol feature was activated.

Enable Indicates the TID is currently enabled. You may have to visually inspect all TIDs to confirm this for the other channels.

255-700-762R11.1 12-21


Chapter 12 Configuring the H.248 ProtocolSaving the System Configuration


12-22 255-700-762R11.1


13 Tracing a Call

Purpose of This ChapterThis chapter describes how to trace calls through the PSAX system. With the H.248 protocol feature enabled and configured, calls can be traced through the PSAX system using the Call Tracing options located on the H.248 Man-agement and Configuration window. A call can be traced from either the context or termination IDs.

Tracing a Call with the Context ID

The H.248 protocol context information provides information at the PSAX system to trace calls between the end points of a call being switched through the PSAX system. Perform the following procedure to view H.248 protocol context information.

Begin


2 Select the Context Access menu option.

The H.248 Context Access window is displayed (see Figure 13-1).

The buttons on this page are described in Table 13-1.

Figure 13-1. H.248 Context Access Window

Table 13-1. Buttons for the H.248 Context Access Window

Button Function

Find Searches the table and displays a matching text string entered in the Show table entries containing: field.


255-700-762R11.1 13-1

Chapter 13 Tracing a CallTracing a Call with the TID

3 Double-clicking on an entry in this table displays another window with detailed information on the terminations identified in the window. See the section, “Tracing a Call with the TID” to view the context termina-tions.

The H.248 Context Access window is described in Table 1-2.

4 When finished viewing the information, click Close.

End

Tracing a Call with the TID

Perform the following procedure to trace calls through the PSAX system using the TID.

Begin


2 Select the Termination Access menu option.

The H.248 Termination Access window is displayed (see Figure 13-2).

Reset Removes text entered in the Show table entries con-taining: field and de-selects any selected entries.


Table 13-1. Buttons for the H.248 Context Access Window (Continued)

Button Function

Table 13-2. H.248 Context Access Window Field Descriptions


Number of Contexts Default: 1

Range: 1–8000

Format: Numeric

Displays the total number of contexts (physical, ephemeral, and null) listed in the table.

Context ID Default: N/A

Range: 1–8000

Format: Numeric

Displays the available context IDs listed in the table. Selecting a context ID displays the H.248 Context Information Display window.

Number of Termina-tions

Default: 1

Range: 1–2

Format: Numeric

Displays the available terminations in each con-text ID listed in the table. A value of 1 indicates the termination resides in the null context. A value of 2 indicates the context ID is terminated in either a physical or ephemeral context.

13-2 255-700-762R11.1



The fields on the H.248 Termination Access window are described in Table 1-1.

3 To search for an existing TID, enter the TID value in the Termination ID field, and click Retrieve.

If the value is found, another window is displayed, displaying detailed information about the TID.

4 When finished viewing the information, click Close.

End

Figure 13-2. H.248 Termination Access Window

Table 13-3. H.248 Termination Access Window Field Descriptions


Number of All Ter-minations

Default: 0

Range: 0–16000

Format: Numeric

Displays the total number of all terminations (physical, ephemeral, and null) created in the MG database.

Number of All Phys-ical Terminations

Default: N/A

Range: 0–16000

Format: Numeric

Displays the total number of physical TDM termi-nations created in the MG database.

Number of All Ephemeral Termina-tions

Default: N/A

Range: 0–16000

Format: Numeric

Displays the total number of ephemeral ATM ter-minations created in the MG database.

Number of Physical Terminations in the NULL Context

Default: 0

Range: 0–16000

Format: Numeric

Displays the total number of physical termina-tions listed in the null context.

Termination ID Default: N/A

Range: N/A


Selects the entered termination ID. Enter the desired termination ID and press Enter to display the H.248 Termination Information Display win-dow (provides details for the termination).

255-700-762R11.1 13-3



13-4 255-700-762R11.1


14 Configuring V5.2 European IDLC

Configuring the V5.2 InterfaceThe V5.2 feature is available in PSAX system software beginning with Release 6.0.

Overview of V5.2 ConfigurationThe tasks involved with configuring V5.2 are as follows:

Network Side

1. Enabling V5.2 on the PSAX device

2. Allocating call resources properly

3. Allocating V5.2 resources

4. Configuring I/O and server modules:

a. an I/O module that supports ATM (for specific configuration proce-

dures, see the appropriate Navis® EMS-PSAX Module Configuration Guide)

b. Configuring a DSP2D module (for specific configuration procedures,

see the Navis® EMS-PSAX Module Configuration Guide)

5. Configuring the V5.2 interface

6. Configuring the variant

7. Configuring the physical channel

8. Configuring the E1 link

9. Configuring the data link

User Side

10. Configuring ATM trunking

11. Configuring the user port

This chapter includes procedures for all tasks except task 4.

Enabling V5.2The V5.2 feature is disabled on a PSAX device by default. Perform the steps in the following procedure to enable the V5.2 feature.


255-700-762R11.1 14-1

Chapter 14 Configuring V5.2 European IDLCEnabling V5.2

Begin


The Site-Specific page is displayed (see Figure 14-1).



3 Select the Feature value V5 on this window.


5 To enable the feature, select Turn On Selected Feature. To disable the fea-ture, select Turn Off Selected Feature.

End

You must reboot the PSAX device before this V5.2 feature will become enabled (see “Rebooting the PSAX Device” in this chapter. You may opt to set your call control resources (see “Setting Call Control Resources for V5.2” in this chapter) before rebooting the PSAX device.


14-2 255-700-762R11.1


Chapter 14 Configuring V5.2 European IDLCSetting Call Control Resources for V5.2

Setting Call Control Resources for V5.2Perform the steps in the following procedure to allocate call resources for a PSAX device.

Begin


The Call Control page appears (see Figure 14-4).

2 Change the value of the ATM Trunk VCC field to 4096, and adjust other fields to free 4,096 call resources.

3 Enter the values in the other fields on this window according to the information provided in Table 14-1.

4 Click Apply.




255-700-762R11.1 14-3



6 Follow the instructions in “Rebooting the Device,” in this chapter, to restart hardware components so that the call control configuration val-ues will take effect on your PSAX device.

End

14-4 255-700-762R11.1




255-700-762R11.1 14-5



Table 14-1. Call Control Page Field Descriptions


Important: The ranges of values for numeric fields are software imposed. When changing the val-ues in these fields, keep in mind that the PSAX system calculates the percentage of the memory allocation usage from the combination of values you have entered in the fields. This calculation is displayed in the Call Control Resource Allocation Usage field. When all the values of SVC calls and parties, SPVC calls, CG API endpoints, and CG API calls and parties are calculated as a percentage of memory allocation, this percentage value cannot exceed 100 percent of the memory allocation. If you enter a combination of values that exceeds 100 percent when calculated by the system, the fol-lowing error message is displayed: T-CallControlResAllocFail. If you receive this error message, adjust the values in the fields and click Apply to recalculate the allocation usage percentage value. Read the configuration guidelines and the PSAX System Performance Capabilities per Node table in the preceding section before you enter values in the fields on this window.

SVC Point To Point Calls

Default: 2000

Range: 0–15000

Format: Numeric

Specifies the maximum number of SVC point-to-point calls to be supported by the PSAX system.

H.248 Applications: For AAL2, this field must be greater than or equal to the sum of the values in the atmTrunkNarrowBandCalls and atmTrunkVccs fields.

Set this field to the same value as the sgApiPtToPtSvc-Calls field. Example: If the Maximum Number of Con-texts field on the H.248 Configuration window is set to 4000 and the Maximum Number of Terminations field on that window is set to 8000, then recommended val-ues for this field are:

• AAL1: 4000

• AAL2: 4100

• AAL1/AAL2: 4100

SVC Point To Multi Point Calls

Default: 2000

Range: 0–4000

Format: Numeric

Specifies the maximum number of SVC point-to-mul-tipoint calls to be supported by the PSAX system.


SVC Point To Multi Point Parties

Default: 2000

Range: 0–4000

Format: Numeric

Specifies the maximum number of parties on SVC point-to-multipoint calls to be supported by the PSAX system.


SPVC Ce Point To Point Calls

Default: 1000

Range: 0–10000

Format: Numeric

Specifies the maximum number of SPVC circuit emu-lation point-to-point calls to be supported by the PSAX system.



14-6 255-700-762R11.1



SPVC Te Point To Point Calls

Default: 100

Range: 0–10000

Format: Numeric

Specifies the maximum number of SPVC terminal emulation point-to-point calls to be supported by the PSAX system.



SPVC ATM Point To Point Calls

Default: 2000

Range: 0–10000

Format: Numeric

Specifies the maximum number of SPVC ATM point-to-point calls to be supported by the PSAX system.



SPVC Fr Point To Point Calls

Default: 900

Range: 0–10000

Format: Numeric

Specifies the maximum number of SPVC frame relay point-to-point calls to be supported by the PSAX sys-tem.


SPVC Point To Multi Point Calls

Default: 500

Range: 0–500

Format: Numeric

Specifies the maximum number of SPVC point-to-mul-tipoint calls to be supported by the PSAX system.


SPVC Point To Multi Point Parties

Default: 1000

Range: 0–4000

Format: Numeric

Specifies the maximum number of parties on SPVC point-to-multipoint calls to be supported by the PSAX system.


Aal2 Cir-ATM SPVC Calls

Default: 1000

Range: 0–4000

Format: Numeric

Specifies the maximum number of circuit emulation-to-ATM standard AAL2 SPVC calls to be supported by the PSAX system.


Aal2 Vbr-Atm SPVC Calls

Default: 100

Range: 0–4000

Format: Numeric

Specifies the maximum number of VBR-to-ATM stan-dard AAL2 SPVC calls to be supported by the PSAX system.


SPVC ERM Point-To-Point Calls

Default: 100

Range: 1–1000

Format: Numeric

Specifies the maximum number of Enhanced Router-to-ATM SPVC calls supported on this PSAX system.



255-700-762R11.1 14-7



SPVC Global Prior-ity Scheme

Default: Disabled

Range: N/A

Format: Predefined

Specifies whether the PSAX systemwide priority scheme must be supported for all SPVCs and SPVC trunks.

Disabled Indicates that the priority scheme is not in force (dis-abled).

Enabled Indicates that the priority scheme is in force (enabled). If you select the value Enabled in this field, the total number of calls specified in all of the SPVC call fields and the number of ATM trunk VCCs cannot exceed 32 calls.

Note: For SPVC reconnections in priority scheme-enabled trunks in an IMA link, the limit is 32 SPVCs.

SPVC Priority Scheme

Default: Disabled

Range: N/A

Format: Predefined

An indication that the priority scheme should be sup-ported in SPVCs.

Disabled The priority scheme is disabled for SPVCs.

Enabled The priority scheme is enabled for SPVCs.

SPVC Trunking Pri-ority Scheme

Default: Disabled

Range: N/A

Format: Predefined

An indication that the priority scheme should be sup-ported in SPVC trunks.

Disabled The priority scheme is disabled for SPVC trunks.

Enabled The priority scheme is enabled for SPVC trunks.

SPVC Global Auto Reversion Scheme

Default: Disabled

Range: N/A

Format: Predefined

An indication that the auto reversion scheme should be supported across SPVCs and SPVC trunks.

Disabled The auto reversion scheme is disabled for SPVCs and SPVC trunks.

Enabled The auto reversion scheme is enabled for SPVCs and SPVC trunks.

SPVC Auto Rever-sion Scheme

Default: Disabled

Range: N/A

Format: Predefined

An indication that the auto reversion scheme should be supported in SPVCs.


Disabled The auto reversion scheme is disabled for SPVCs.

Enabled The auto reversion scheme is enabled for SPVCs.



14-8 255-700-762R11.1



SPVC Trunking Auto Reversion Scheme

Default: Disabled

Range: N/A

Format: Predefined

An indication that the auto reversion scheme shoul be supported in SPVC trunks.


Disabled The auto reversion scheme is disabled for SPVC trunks.

Enabled The auto reversion scheme is enabled for SPVC trunks.

Signalling Gateway Panel

SG API CirEm End Points

Default: 1000

Range:

Format: Numeric

Specifies the maximum number of circuit emulation endpoints for the Connection Gateway API to be sup-ported by the PSAX system.


SG API ATM Svc End Points

Default: 0

Range:

Format: Numeric

Specifies the maximum number of ATM SVC end-points for the Connection Gateway API to be sup-ported by the PSAX system.


Connection Gateway Panel

SCG API Point To Point Svc Calls

Default: 0

Range:

Format: Numeric

Specifies the maximum number of SVC point-to-point calls for the Connection Gateway API to be supported by the PSAX system.

H.248 Applications: Specifies the maximum number of point-to-point calls through H.248. Set this field to the same value as the svcPtToPtCalls field. Example: If the Maximum Number of Contexts field on the H.248 Configuration window is set to 4000 and the Maxi-mum Number of Terminations field on that window is set to 8000, then recommended values for this field are:

• AAL1: 4000

• AAL2: 4100

• AAL1/AAL2: 4100

SCG API Point To Multi Point Svc Calls

Default: 0

Range:

Format: Numeric

Specifies the maximum number of SVC point-to-mul-tipoint calls for the Connection Gateway API to be sup-ported by the PSAX system.


SCG API Point To Multi Point Parties

Default: 0

Range:

Format: Numeric

Specifies the maximum number of parties on SVC point-to-multipoint calls for the Connection Gateway API to be supported by the PSAX system.




255-700-762R11.1 14-9



ATM Trunking Panel

ATM Trunk VCCs Default: 100

Range: 1–1024; 1–4096 for V5 appli-cations

Format: Numeric

Specifies the maximum number of VCCs supported by ATM trunking.

H.248 Applications: Specifies the maximum number of AAL2 trunks. For AAL1 call setups, this field does not apply and should be set to 0. Example: If the Maxi-mum Number of Contexts field on the H.248 Configu-ration window is set to 4000 and the Maximum Num-ber of Terminations field on that window is set to 8000, then recommended values for this field are:

• AAL1: 0

• AAL2: 100

• AAL1/AAL2: 100

SPVC Priority Configurations: The total of all call fields and atmTrunkVccs cannot exceed 32 when the spvc-GlobalPriorityScheme field is Enabled.

V5.2 Applications: You can enter up to the value 4096. If you enter 4096, be sure that you have first freed enough resources in other fields in order to enter a high value in the atmTrunkVccs field.

ATM Trunk Nar-rowband Calls

Default: 1000

Range: 1–4000

Format: Numeric

Specifies the maximum number of switched narrow-band calls supported by ATM trunking.

H.248 Applications: Specifies the maximum number of simultaneous calls through AAL2. For AAL1 call set-ups, this field does not apply and should be set to 0. Example: If the Maximum Number of Contexts field on the H.248 Configuration window is set to 4000 and the Maximum Number of Terminations field on that window is set to 8000, then recommended values for this field are:

• AAL1: 0

• AAL2: 4000

• AAL1/AAL2: 2000

Call Control Resource Allocation Usage

Default: N/A

Range: 0–100

Format: Numeric

Displays the percentage of memory allocated to call control. A portion of the total system memory is allo-cated for call control. The value in this field represents the amount of this allocation that is currently in use. This percentage value is calculated by the system from the values you enter in the other fields.



14-10 255-700-762R11.1


Chapter 14 Configuring V5.2 European IDLCConfiguring V5.2 Resources

Configuring V5.2 ResourcesPerform the steps in the following procedure to allocate call resources for a PSAX device.

Begin




SVC Cut Through Option

Default: CgSvcAcI-mplicitCutThrough

Range: N/A

Format: Predefined

Specifies whether the PSAX system or the connection gateway device (connection manager) sends a cut-through message to initiate an SVC connection.

Note: The value in this field is relevant only if you have enabled a media gateway control feature (the Connection Gateway API feature or the H.248 fea-ture).

CgSvcAcImplicit-CutThrough

Indicates that the PSAX system sends a cut-through message to the connection gateway device to initiate an SVC connection.

CgSvcAcExplicit-Cuthrough

Indicates that the connection gateway device deter-mines when to send a cut-through message to the con-nection manager to initiate an SVC connection.

H.248 Applications: You must use the value cgSv-cAcExplicitCutThrough if you are using the H.248 Media Gateway Control protocol feature.

Number Of Calls Supported

Default: 60000

Range: 30000-60000

Format: Numeric

The total number of calls that a CPU module can sup-port including PVC, SVC, SPVC and others. Reducing this number can increase system memory to be used for other applications such as GR-303 or V5.2. Since the call ID range is also reduced, the calls with call IDs greater than the new ID range will be dropped in the next boot up and need to be re-established. It is recom-mended that this be changed only during a mainte-nance window. The minimum is set to 30,000 calls to ensure system functionality.



255-700-762R11.1 14-11




3 Click the V5 Configuration tab.

The Interfaces page appears.

4 Click the Resources tab.

The Resources page appears, displaying the V5 Resource Allocation Con-figuration panel (see Figure 14-6).

5 Enter the values in the fields on this window according to the informa-tion provided in Table 14-2.

6 Click Apply.


End

Figure 14-5. Special Features Page

14-12 255-700-762R11.1




Figure 14-6. Resources Page

Button Function

Apply Executes configuration changes on the PSAX device made

in the Site-Specific page in the EMS-PSAX. To save

changes to the PSAX system, click Device > Save PSAX Configuration in the Device Menu Bar.

(See the section, “Saving Configuration Values.”)

Reset Restores all of the fields in the Site-Specific page to the lat-est values that were applied to the device.

V5 DSP Over Subscription Table

Displays the V5 Dsp Over Subscription Table window.

255-700-762R11.1 14-13



Table 14-2. Resources Page Field Descriptions


Max V5 Interfaces Default: 4

Range: 0–10

Format: Numeric

Indicates the maximum number of V5 interfaces that can be supported in this system.

Max User Ports Default: 8000

Range: 1–16000

Format: Numeric

Indicates the maximum number of User Ports that can be used in this system. This includes both PSTN and ISDN ports.

Max User Ports Per V5 Interface

Default: 8000

Range: 1–16000

Format: Numeric

Indicates the maximum number of User Ports per V5 interface. This includes both PSTN and ISDN ports per V5 interface.

Max ISDN Ports Default: 8000

Range: 1–8176

Format: Numeric

Indicates the maximum number of ISDN ports that can be supported in this system. This value is less than or equal to the Max User Ports value. A non-zero value for this parameter does not neces-sarily imply that maximum number of PSTN ports is the number of Max User Ports minus the number of Max Isdn Ports.

Max ISDN Ports Per V5 Interface

Default: 8000

Range: 1–8176

Format: Numeric

Indicates the maximum number of ISDN ports per V5 interface. This value is always less than or equal to the value of the Max User Ports /V5 Interface field. A non-zero value for this parame-ter does not necessarily imply that maximum number of PSTN ports/V5 interface is this value minus the value of the Max Isdn Ports/V5 Inter-face field.

TPL1 Timer Default: 15

Range: 1–30


This timer is used by the ISDN basic rate access (BRA) port manager to supervise the unblock procedure of a port. Values are represented in seconds.

T1 Timer Default: 15

Range: 1–30


This timer is used by the BRA port manager to supervise the access activation procedure of a port. Values are represented in seconds.

BccTbcc5 Timer Default: 1000

Range: 500–1500


This timer is used by the Bearer Channel Control (BCC) protocol. An AN fault message is sent to LE whenever AN detects the internal failure and starts this timer. AN is expected to receive the AN fault acknowledge message within this time. The values are represented in milliseconds.

SetSA7Bit Timer Default: 50

Range: 50–200


This timer is used to guarantee that the SA7 bit is set to zero before the message is sent to LE that says the bit has been set. Values are represented in milliseconds.

14-14 255-700-762R11.1



Configuring V5.2 DSP Parameters

Perform the steps in the following procedure to configure V5.2 DSP oversub-scription parameters.

ReadSA7Bit Timer Default: 50

Range: 50–200


This timer is used to guarantee that the SA7 bit change has been reported to the AV5 stack. When a message is received from the LE indicating the SA7 bit is set to zero, the AV5 stack waits for the ReadSA7BitTimer value before it reads the status from Layer 1 FSM. Values are represented in mil-liseconds.

Link ID Timeout Default: 0

Range: 0–30

Format: N/A

This timer is used for the Link Id procedure. This is the maximum time the AN should take to com-plete the Link Id procedure. This timer can be dis-abled by setting this value to 0.

Target DSP Over Subscription

Default: 0

Range: 1-99999

Format: Predefined

Specifies the limit of the DSP resource oversub-scription for V5 voice calls. A trap will be sent if the oversubscription goes beyond this limit due to the configuration of the ISDN ports.

Note: The value is given in %, so 25% means the resources will be undersubscribed and 800% means the resources can be oversubscribed up to 8 times.

Current DSP Over Subscription(display only)

Default: 0

Range: 0-99999

Format: Numeric

Specifies the current value of the DSP resource oversubscription for V5 voice calls. The calcula-tion of the current DSP resource oversubscription in the chassis is as follows:

the number of DSP resources left in the chassis after configuration = [{(number of DSP2D mod-ules * 384) – number of AAL2 trunks} – (number of AAL2 trunks * no. of ISDN ports/trunk)]. The preceding formula assumes that 1 DSP resource is needed for ELCP connection per IAD and 1 DSP resource is required for the D-channel per ISDN port on an IAD). To calculate oversubscription = (no. of B channels for ISDN + no. of PSTN ports configured) / (no. of DSP resources left in the chassis after configuration). There are 30 B-chan-nels for PRA and 2 B-channels for BRA. The value is expressed as a percentage (see Note in Description for Target DSP). This calculation of the oversubscription is valid only if the Least Used algorithm is chosen for the DSP resource allocation scheme.

Table 14-2. Resources Page Field Descriptions


255-700-762R11.1 14-15


Chapter 14 Configuring V5.2 European IDLCAccessing the DSP Over Subscription Window

Begin







4 Click the Resources tab.

The Resources page appears, displaying the V5 Resource Allocation Con-figuration panel (see Figure 14-6).

5 Click V5 DSP Over Subscription Table.

The V5 Dsp Over Subscription Table window appears (see Figure 14-7).

6 To view or update the entries in the table, right-click the entry and select either View or Update.

7 Click Close.

End

Accessing the DSP Over Subscription WindowPerform the following procedure to access the V5 DSP Over Subscription window.

Begin

Accessing the V5 Interface Configuration Window, Part 1

1 From the V5 Resource Allocation Configuration window, click the V5 DSP Over Subscription Table button.

Figure 14-7. V5 Dsp Over Subscription Table Window

14-16 255-700-762R11.1



The V5 DSP Over Subscription Table window appears (see Figure 14-8). Table 14-3 describes the fields on this window.

2 To update the target subscription percentage for an entry, double-click the desired entry.

The UPDATE V5 DSP Over Subscription Configuration Window appears (see Figure 14-9).

End

Figure 14-8. V5 DSP Over Subscription Table Window

Figure 14-9. UPDATE V5 DSP Over Subscription Configuration Window

255-700-762R11.1 14-17



Table 14-3. V5 DSP Over Subscription Table Window Field Descriptions


DSP Resource ID Default: N/A

Range: N/A

Format: Predefined

Identifies the V5 DSP resource pool.

Pool-1 Identifies the first user prioritized V5 DSP resource pool.

Pool-2 Identifies the second user prioritized V5 DSP resource pool.

Pool-3 Identifies the third user prioritized V5 DSP resource pool.

Pool-4 Identifies the fourth user prioritized V5 DSP resource pool.

Target Subscription Default: 400

Range: 1-99999

Format: Percentage

Specifies the limit of the DSP resource oversubscrip-tion for V5 voice calls. A trap will be sent if the oversubscription goes beyond this limit due to the configuration of the ISDN ports.

Note: The value is given in %, so 25% means the resources will be undersubscribed and 800% means the resources can be oversubscribed up to 8 times.

Current Subscrip-tion

Default: 0

Range: 0-99999

Format: Percentage

Specifies the current value of the DSP chip resources oversubscription for V5 voice calls. The-calculation of the current DSP resource oversub-scription in the chassis is as follows: the number of DSP resources left in the chassis after configuration = [{(number of DSP2D mod-

ules * 384) – number of AAL2 trunks} – (number of AAL2 trunks * no. of ISDN ports/trunk)]. The pre-ceding formula assumes that 1 DSP resource is needed for ELCP connection per IAD and 1 DSP resource is required for the D channel per ISDN port on an IAD). To calculate oversubscription = (no. of B channels for ISDN + no. of PSTN ports configured) / (no. of DSP resources left in the chas-sis after configuration). There are 30 B-channels for PRA and 2 B-channels for BRA. The value is expressed as a percentage. This calculation of the oversubscription is valid only if the Least Used algo-rithm is chosen for the DSP resource allocation scheme.

14-18 255-700-762R11.1


Chapter 14 Configuring V5.2 European IDLCConfiguring V5.2 Interfaces

Configuring V5.2 InterfacesPerform the steps in the following procedure to configure V5.2 interfaces.

Begin






The Interfaces page appears, displaying the V5 Interface Configuration Table (see Figure 14-10).

4 Right-click within the V5 Interface Configuration Table and a menu appears (see Figure 14-11). Select Create.

The ADD V5 Interface Table Entry window appears (see Figure 14-12).


6 Click Add.

The new entry appears in the V5 Interface Configuration Table window.

7 Click Close.


End

Figure 14-10. Interfaces Page (Displaying V5 Interface Configuration Table)

255-700-762R11.1 14-19




Figure 14-11. Interfaces Page (Displaying V5 Interface Configuration Table Menu)

Figure 14-12. ADD V5 Interface Table Entry Window

Button Function

Add Displayed on the ADD V5 Interface Table Entry window when creating a V5.2 interface. Adds this V5.2 interface to the V5 Interface Configuration Table.

Update Displayed on the UPDATE V5 Interface Table Entry win-dow when updating a V5.2 interface. Updates the entry in the V5.2 Interface Configuration Table with the values you select.

Delete Displayed on the VIEW V5 Interface Table Entry and UPDATE V5 Interface Table Entry windows. Removes the entry from the V5.2 Interface Configuration Table.

Reset Displayed on the UPDATE V5 Interface Table Entry win-dow when updating a V5.2 interface. Restores the config-urable values for this entry to the last saved values.


Bring Into Service Brings this interface into service.

Take Out of Service Takes this interface out of service.

14-20 255-700-762R11.1



Viewing a V5.2 Interface

Begin

1 From the Site-Specific tab, click the V5 Configuration tab.


2 Right-click within the V5 Interface Configuration Table and a menu appears (see Figure 14-11). Select Display.

The VIEW V5 Interface Table Entry window appears (see Figure 14-13).


End

Updating a V5.2 Interface

Begin



2 Right-click within the V5 Interface Configuration Table and a menu appears (see Figure 14-11). Select Update.

Figure 14-13. VIEW V5 Interface Table Entry Window

255-700-762R11.1 14-21



The VIEW V5 Interface Table Entry window appears (see Figure 14-14).

Note: The only fields you can change on this window without deleting the V5.2 interface are the Active Variant, Switchover Command, and Admin Status fields.

3 After modifying the desired values, click Update. To cancel, click Reset.

4 Click Close.

End

Deleting a V5.2 Interface

Begin



Figure 14-14. UPDATE V5 Interface Table Entry Window

14-22 255-700-762R11.1




End

Table 14-5. Deleting a V5.2 Interface

To delete a V5.2 interface... do this...


a View the attributes of the entry first. Follow steps 1 and 2 in the section, “Viewing a V5.2 Interface”

b Click Delete.



when you are sure which entry you want to delete


b Right-click the mouse within the V5 Interface Configuration Table and a menu appears (see Figure 14-10). Select Delete.



255-700-762R11.1 14-23


Chapter 14 Configuring V5.2 European IDLCConfiguring V5.2 Variants

Configuring V5.2 VariantsPerform the steps in the following procedure to configure V5.2 variants.

Begin







4 Click the Variants tab.

The Variants page appears, displaying the V5 Variant Configuration Table (see Figure 14-10).

5 Right-click within the V5 Variant Configuration Table and a menu appears (see Figure 14-11). Select Create.

The ADD V5 Variant Table Entry window appears (see Figure 14-12).


7 Click Add.

The new entry appears in the V5 Variant Configuration Table window.

8 Click Close.


End

Figure 14-15. Variant Page (Displaying V5 Variant Configuration Table)

14-24 255-700-762R11.1




Figure 14-16. Variant Page (Displaying V5 Variant Configuration Table Menu)

Figure 14-17. ADD V5 Variant Table Entry

Button Function

Add Adds this V5.2 variant to the V5 Variant Configuration Table.

Update Displayed on the UPDATE V5 Variant Table Entry window when updating a V5.2 variant. Updates the entry in the V5 Variant Configuration Table with the values you select.

Delete Displayed on the VIEW V5 Variant Table Entry and UPDATE V5 Variant Table Entry windows. Removes the entry from the V5 Variant Configuration Table.

Reset Displayed on the UPDATE V5 Variant Table Entry window when updating a V5.2 variant. Restores the configurable values for this entry to the last saved values.


255-700-762R11.1 14-25



Bring Into Service Brings this interface into service.

Take Out of Service Takes this interface out of service.

Button Function

Table 14-6. ADD V5 Variant Entry Window Field Descriptions


V5 Interface ID Default: 1

Range: 1–10

Format: Numeric

Specifies the V5 interface identifier.

V5 Variant ID Default: 0

Range: 0–127

Format: Numeric

Specifies the V5 variant identifier.


Default: OutOf-Service

Range: N/A

Format: Pre-defined

Specifies the Administrative Status of the Variant channel.

OutOfService The variant channel is not in service.

InService The variant channel is in service.

Protection Status(display only)

Default: Active

Range: N/A

Format: Pre-defined

Specifies whether the variant protection status is active or inactive. This fields also shows which variant is active or passive in this particular V5 interface.

Active Active shows this variant is active and operational.

Passive Passive shows this variant is not active but in standby mode.

Interface Type(display only)

Default: V52

Range: N/A

Format: Pre-defined

V.5.2 standard as defined in ETSI EN 300 347-x. Type of V5 interface being provisioned. V5.2 is most widely used by customers as it has additional feature sets over V5.1.

Interface Edition Default: Sec-ondEdition

Range: N/A

Format: Pre-defined

Specifies the V5 interface edition being provisioned. First Edition and Second Edition differs in the application of these procedures:

• Periodic Pulse Metering

• Accelerated Alignment

• V5 Interface startup

Refer to ETSI EN 300 324-1 V2.1.1, Section 13.1.2 for details.

FirstEdition First edition interface is used

SecondEdition Second edition interface is used.

14-26 255-700-762R11.1



Align Ports Method Default: V5SecondEditionPor-tAlign

Range: N/A

Format: Pre-defined

Indicates type of flag used for port alignment method to use along with interface type.

V5PortAlignUndefined

Port align protocol not defined.

V5PortIndividualPortAlign

Informs the V5 stack to unblock all relevant PSTN and ISDN ports one by one.

V5FirstEditionPortAlign

Informs the V5 stack to unblock all relevant PSTN and ISDN ports as a single entity.

V5SecondEditionPortAlign

Informs V5 stack to unblock or block all relevant PSTN and ISDN ports as a separate entity.

AN Initiate Link Proc

Default: False

Range: N/A

Format: Pre-defined

This flag indicates whether the Access Network or Local Exchange initiates the Link Id procedure. If true, the AN should initiate it. If False, the LE should initiate it.

False False informs the V5 stack not to initiate the link identifi-cation procedure.

True True informs V5 stack to initiate the link identification procedure.

L1 Fsm Normal Timer(display only)

Default: 1

Range: 1–1000


Specifies the L1 finite state machine normal timer, that the E1 facility uses to enter into the NORMAL operational state. Values are given in milliseconds.

L1 Fsm LosOrLof Timer(display only)

Default: 1

Range: 1–2500


Specifies the L1 finite state machine loss of signal or loss of frame timer for the E1 facility to enter into the non-operational state when LOS/LOF is set. Values are given in milliseconds.

L1 Fsm Ais Timer(display only)

Default: 1

Range: 1–2500


Specifies the L1 finite state machine alarm indicator signal timer that the E1 facility uses to enter into the non-opera-tional state when there is an alarm indication. Values are given in milliseconds.

L1 Fsm Rai Timer(display only)

Default: 1

Range: 1–2500


Specifies the L1 finite state machine RAI signal timer for the E1 facility to enter into the non-operational state when an RAI occurs. Values are given in milliseconds.

Resource Manager TR1

Default: 500

Range: 500–1500


Specifies the timer used by resource manager to send BCC:ALLOCATION REJECT message if it does not receive a V5ConnectComplete message within this time. Values are given in milliseconds.

Table 14-6. ADD V5 Variant Entry Window Field Descriptions (Continued)


255-700-762R11.1 14-27



Viewing a V5.2 Variant

Begin

1 In the Site-Specific tab, click the V5 Configuration tab.




3 Right-click within the V5 Variant Configuration Table and a menu appears (see Figure 14-11). Select Display.

The VIEW V5 Variant Table Entry window appears (see Figure 14-18).


End

Updating a V5.2 Variant

Begin



Figure 14-18. VIEW V5 Variant Table Entry Window

14-28 255-700-762R11.1





3 Right-click within the V5 Variant Configuration Table and a menu appears (see Figure 14-11). Select Update.

The UPDATE V5 Variant Table Entry window appears (see Figure 14-19).

Note: The only fields you can change on this window without deleting the V5.2 variant are the Admin Status, Interface Edition, Align Ports Method, AN Initiate Link Proc, and Resource Manager TR1 fields.

4 After modifying the desired values, click Update. To cancel, click Reset.

5 Click Close.

End

Deleting a V5.2 Variant

Begin




Figure 14-19. UPDATE V5 Variant Table Entry Window

255-700-762R11.1 14-29




3 Do one of the following as shown in Figure 14-7:

End

Table 14-7. Deleting a V5.2 Variant

To delete a V5.2 interface... do this...


a View the attributes of the entry first. Follow steps 1–3 in the section, “Viewing a V5.2 Variant”

b Click Delete.





b Right-click the mouse within the V5 Variant Configuration Table and a menu appears (see Figure 14-11). Select Delete.



14-30 255-700-762R11.1


Chapter 14 Configuring V5.2 European IDLCConfiguring V5.2 Physical C Channels

Configuring V5.2 Physical C ChannelsPerform the steps in the following procedure to configure V5.2 physical C channels.

Begin








The Variants page appears, displaying the V5 Variant Configuration Table.

5 Right-click within the V5 Variant Configuration Table and a menu appears. Select Physical C Channel Table.

The View V5 Physical C Channel Table window appears (see Figure 14-20).

6 Right-click within the table and a menu appears (see Figure 14-21). Select Create.

The ADD V5 Physical C Channel Table Entry window appears (see Figure 14-22).


8 Click Add.

The new entry appears in the View Physical C Channel Table window.

9 Click Close.


End

255-700-762R11.1 14-31




Figure 14-20. View V5 Physical C Channel Table Window

Button Function




Figure 14-21. V5 Physical C Channel Table Menu

14-32 255-700-762R11.1




Figure 14-22. ADD V5 Physical C Channel Table Entry Window

Button Function

Add Adds this V5.2 physical C channel to the View V5 Physical C Channel Table.

Update Displayed on the UPDATE V5 Interface Table Entry win-dow when updating a V5.2 physical C channel. Updates the entry in the View V5 Physical C Channel Table with the values you select.

Delete Displayed on the VIEW V5 Interface Table Entry and UPDATE V5 Interface Table Entry windows. Removes the entry from the View V5 Physical C Channel Table.

Reset Displayed on the UPDATE V5 Interface Table Entry win-dow when updating a V5.2 physical C channel. Restores the configurable values for this entry to the last saved val-ues.


255-700-762R11.1 14-33



Viewing a V5.2 Physical C Channel

Begin







4 Right-click within the V5 Variant Configuration Table and a menu appears. Select Display.

Table 14-8. V5 Physical C Channel Configuration Window Field Descriptions


Protection Grp Num

Default: Pg-1

Range: N/A

Format: Pre-defined

Specifies whether this logical/physical channel belongs to Protection Group Number 1 or 2. Protection Group 1 always uses the user-assigned value 16. Protection Group 2 uses the timeslot value 15 or 31 (2 timeslots are necessary to provide sufficient bandwidth on V5.1 systems with ISDN and most V5.2 systems).

Pg-1 Pg-1 supports one active C-Channel and one Standby C-Channel where N1 = 1, K1 = 1.

Pg-2 Pg-2 supports 1 <= N2<(3*L-2-K2) Active C-Channels where L = number of E1 links, and 1<=K2<=3 Standby C-Channels.

14-34 255-700-762R11.1



The VIEW V5 Physical C Channel Table Entry window appears (see Figure 14-23).


End

Updating a V5.2 Physical C Channel

Begin







4 Right-click within the V5 Variant Configuration Table and a menu appears. Select Update.

Figure 14-23. VIEW V5 Interface Table Entry Window

255-700-762R11.1 14-35



The UPDATE V5 Physical C Channel Table Entry window appears (see Figure 14-24).

Note: The only field you can change on this window without deleting the V5.2 physical C channel is the Protection Grp Num field.

5 After modifying the configuration, click Update. To cancel, click Reset.

6 Click Close.

End

Deleting a V5.2 Physical C Channel

Begin







Figure 14-24. UPDATE V5 Interface Table Entry Window

14-36 255-700-762R11.1




End

Table 14-9. Deleting a V5.2 Physical C Channel

To delete a V5.2 physical C channel... do this...



b Click Delete.





b Right-click the mouse within the V5 Interface Table Entry window and a menu appears (see Figure 14-21). Select Delete.



255-700-762R11.1 14-37


Chapter 14 Configuring V5.2 European IDLCConfiguring V5.2 E1 Links

Configuring V5.2 E1 LinksPerform the steps in the following procedure to configure V5.2 E1 Links.

Begin





3 Right-click within the V5 Variant Configuration Table and a menu appears. Select E1 Link Table.

The View V5 E1 Link Table window appears (see Figure 14-25).


The ADD V5 E1 Link Table Entry window appears (see Figure 14-27).


6 Click Add.

The new entry appears in the View V5 E1 Link Table window.

7 Click Close.


End

Figure 14-25. View V5 E1 Link Table Window

14-38 255-700-762R11.1





Button Function




Figure 14-26. V5 E1 Link Table Menu

Figure 14-27. ADD V5 E1 Link Table Entry

Button Function

Add Adds this V5.2 E1 link to the View V5 E1 Link Table.

Update Displayed on the UPDATE V5 Interface Table Entry win-dow when updating a V5.2 E1 Link. Updates the entry in the View V5 E1 Link Table with the values you select.

255-700-762R11.1 14-39



Using the Timeslot Channel Table

To access the Timeslot Channel table, perform the steps in the following pro-cedure.

Delete Displayed on the VIEW V5 Interface Table Entry and UPDATE V5 Interface Table Entry windows. Removes the entry from the View V5 E1 Link Table.

Reset Displayed on the UPDATE V5 Interface Table Entry win-dow when updating a V5.2 E1 link. Restores the config-urable values for this entry to the last saved values.


Button Function

Table 14-11. V5 E1 Interface Configuration Panel Field Descriptions


Physical ID(display only)

Default:

Range: N/A

Format: ssppccc

This index identifies the V5 Interface configuration table.

V5 Interface ID(display only)

Default: 1

Range: 1–10

Format: Numeric

This index identifies the variant channel number in the V5 interface.

E1 Link ID(display only)

Default: 0

Range: 0-15

Format: Numeric

This index identifies the E1 Link Configuration Table.

C-Channel 1(display only)

Default: 0

Range: 15, 16, 31

Format: Numeric

Specifies a C-Channel which carries signalling informa-tion. Generally, this channel should be specified on a single E1 in a V5 interface group and should be on timeslot 16.


Default: 0

Range: 15, 16, 31

Format: Numeric

Specifies a C-Channel which carries signalling informa-tion. Generally, this channel should be specified on a single E1 in a V5 interface group and should be on timeslot 15.


Default:

Range: 15, 16, 31

Format: Numeric

Specifies a C-Channel which carries signalling informa-tion. Generally this channel should be specified on a single E1 in a V5 interface group and should be on timeslot 31.


Default: OutOf-Service

Range: N/A

Format: Predefined

Specifies the E1 interface physical operational status.

OutOfService The interface is out of service.

InService The interface is in service.

14-40 255-700-762R11.1



Begin







4 Right-click within the table and a menu appears (see Figure 14-26). Select TS Chan Table.

The View V5 Timeslot Channel Table window appears (see Figure 14-28).

5 To perform an action other than viewing the timeshot channel, do one of the following as described in Table 14-12.

6 On the View V5 Timeslot Channel Table, click Close.

7 On the View V5 E1 Link Table, click Close.

End

Table 14-12. Performing Actions on Timeslot Channels

To... do this...

bring the timeslot interface into ser-vice

Select the desired timeslot channel and right-click it. A menu appears (see Figure 14-29). Select Bring Interface Into Service.

take the timeslot interface out of ser-vice

Select the desired timeslot channel and right-click it. A menu appears (see Figure 14-29). Select Take Inter-face Out Of Service.

refresh the timeslot interface to see the latest values

Select the desired timeslot channel and right-click it. A menu appears (see Figure 14-29). Select Refresh.

255-700-762R11.1 14-41




End

Viewing a V5.2 E1 Link

Begin


Figure 14-28. View V5 Timeslot Channel Table Window

Button Function




Figure 14-29. V5 Timeslot Channel Table Menu

14-42 255-700-762R11.1









The VIEW V5 E1 Link Table Entry window appears (see Figure 14-30).


End

Updating a V5.2 E1 Link

Begin







4 Right-click within the V5 Variant Configuration Table and a menu appears. Select Update.

Figure 14-30. VIEW V5 E1 Link Table Entry Window

255-700-762R11.1 14-43



The UPDATE V5 Interface Table Entry window appears (see Figure 14-24).

Note: The only field you can change on this window without deleting the V5.2 E1 Link is the Admin Status field.

5 When finished modifying this configuration, click Update. To cancel, click Reset.

6 Click Close.

End

Deleting a V5.2 E1 Link

Begin







Figure 14-31. UPDATE V5 E1 Link Table Entry Window

14-44 255-700-762R11.1




End

Table 14-13. Deleting a V5.2 E1 Link

To delete a V5.2 E1 Link... do this...



b Click Delete.





b Right-click the mouse within the View V5 E1 Link Table window and a menu appears (see Figure 14-25). Select Delete.



255-700-762R11.1 14-45


Chapter 14 Configuring V5.2 European IDLCConfiguring V5.2 Data Links

Configuring V5.2 Data LinksPerform the steps in the following procedure to configure V5.2 Data Links.

Begin









5 Right-click within the V5 Variant Configuration Table and a menu appears. Select Data Link Table.

The View V5 Data Link Table window appears (see Figure 14-32).


The ADD V5 Data Link Table Entry window appears (see Figure 14-34).


8 Click Add.

The new entry appears in the View V5 Data Link Table window.

9 Click Close.


End

14-46 255-700-762R11.1




Figure 14-32. View V5 Data Link Table Window

Button Function




Figure 14-33. V5 Data Link Table Menu

Figure 14-34. ADD V5 Data Link Table Entry

255-700-762R11.1 14-47




Button Function

Add Adds this V5.2 data link to the View V5 Data Link Table.

Delete Displayed on the VIEW V5 Interface Table Entry window. Removes the entry from the View V5 Data Link Table.


Table 14-14. V5 Data Link Configuration Window Field Descriptions


Configuration Left Panel


Range: 1–10

Format: Numeric

Specifies the ID the PSAX uses internally for the interface after the interface is created.

Variant ID Default: 0

Range: 0–127

Format: Numeric

Specifies the associated ID or the Interface ID.

Comm Path Id Default: V5DLCPathProtection1

Range: N/A

Format: Pre-defined

The types described below refer to Data Link Control protocol.

V5DLCPathProtection1

This path carries messages for synchronizing switching between primary and secondary links. protection level 1 on the digital loop carrier system.

V5DLCPathProtection2

This path carries messages for synchronizing switching between primary and secondary links at protection level 2 on the digital loop carrier system.

V5DLCPathControl

V5DLCPathControl. This path carries messages to unblock links and initiate link identification on the digital loop carrier sys-tem.

V5DLCPathLinkControl

The V5 Link Control Protocol is sent by the AN or the LE to convey information required for the coordination of the link control functions for each individual 2048 kbps link.

V5DLCPathBcc The link control path for the bearer channel connection. This path carries messages to allocate and deallocate timeslots on the digital loop carrier system.

V5DLCPathPstn

This path carries messages for call processing of PSTN (analog) circuits such as ESTABLISH, ESTABLISH ACK, DISCONNECT, DISCONNECT COMPLETE, and SIGNAL.

Logical C Chan ID

Default: 0

Range: 0–65503

Format: Numeric

This value must match the value displayed in the Oper Logical C Channel ID field in the View V5 Physical C Channel Table window.

14-48 255-700-762R11.1



Viewing a V5.2 Data Link

Begin








The VIEW V5 Data Link Table Entry window appears (see Figure 14-30).


End

Deleting a V5.2 Data Link

Begin







Figure 14-35. VIEW V5 Data Link Table Entry Window

255-700-762R11.1 14-49




End

Table 14-15. Deleting a V5.2 Data Link

To delete a V5.2 Data Link... do this...



b Click Delete.

A confirmation window appears. l




b Right-click the mouse within the View V5 Data Link Table window and a menu appears (see Figure 14-32). Select Delete.



14-50 255-700-762R11.1


Chapter 14 Configuring V5.2 European IDLCConfiguring ATM Trunking for the V5.2 Application

Configuring ATM Trunking for the V5.2 ApplicationThe tasks involved with configuring V5.2 are as follows:

In this chapter, you will find detailed procedures for configuring ATM trunk-ing. The specific tasks involved in configuring ATM trunking with the V5.2 application described in this section.

Begin

1 Configuring the local node (a maximum of 4096 allowable nodes). Be sure to match the value you set in the ATM Trunk VCCs field on the Call Control page (see step 2 in the section, “Setting Call Control Resources for V5.2,“ in this chapter) with the value in the Max Remote IWF field on the ATM Trunking page).

a On the ATM Trunking page, click Apply to add the local node.

b Bring the node into service.

2 Configuring the remote IWF.

a Add an entry.

b On the ADD ATM Trunking Remote Entry window, select the value Non-switched in the Remote IWF ATM Trunk Mode field.

c Click Add > Close.

d On the ATM Trunking page, select the value Up in the Admin Status field.

3 Configuring the bearer VCC.

a Add an entry.

b Be sure to match the value you set in the ATM Trnk Br VCC ID field on the ADD ATM Trunking Bearer VCC Entry window (see step c in the section, “Configuring ATM Trunking for the V5.2 Application,“ in this chapter) with the value in the ATM Trnk Br VCC ID field on the ADD V5 User Port Entry window (see the section, “Configuring V5.2 User Ports,” in this chapter).

c In the SAR Type field, select Aal2.

d In the VCC Interface ID field, enter the slot/port/channel combina-tion for the ATM I/O module you are using in the V5.2 application. For example: If you are using the 1-Port STM-1 MM 1+1 MSP mod-ule in slot 5, port 1, and channel 1, you would enter the following in the VCC Interface ID field: 0501001.

e In the App Type field, select V5.

End

255-700-762R11.1 14-51


Chapter 14 Configuring V5.2 European IDLCConfiguring V5.2 User Ports

Configuring V5.2 User PortsPerform the steps in the following procedure to configure V5.2 User Ports.

Note: You must have a variant configured prior to accessing the User Port Table window.

Begin









5 Right-click within the V5 Variant Configuration Table and a menu appears. Select User Port Table.

The View V5 User Port Table window appears (see Figure 14-36).


The ADD V5 User Port Entry window appears (see Figure 14-38).


8 Click Add.

The new entry appears in the View V5 User Port Table window.

9 Click Close.


End

14-52 255-700-762R11.1




Figure 14-36. View V5 User Port Table Window

Button Function




Figure 14-37. V5 User Port Table Menu

255-700-762R11.1 14-53




Figure 14-38. ADD V5 User Port Entry

Button Function

Add Adds this V5.2 user port to the View V5 User Port Table.

Update Displayed on the UPDATE V5 User Port Entry window when updating a V5.2 user port. Updates the entry in the View V5 User Port Table with the values you select.

Delete Displayed on the VIEW V5 User Port Entry and UPDATE V5 User Port Entry windows. Removes the entry from the View V5 User Port Table.

Reset Displayed on the UPDATE V5 User Port Entry window when updating a V5.2 user port. Restores the configurable values for this entry to the last saved values.


14-54 255-700-762R11.1



Table 14-16. V5 User Port Table Entry Window Field Descriptions



Range: 1–254

Format: Numeric

Specifies the ID the PSAX system uses internally for the inter-face after the interface is created.

Variant ID Default: 0

Range: 1–127

Format: Numeric

Specifies the Variant Id which is active for this V.25 Interface. Only one variant is the active variant ID. Variants permit an interface group to have multiple configurations to connect to the voice switch. Changing variants only affects the network portion from the Gateway to the voice switch. The network portion from the gateway to the subscriber is not affected.

LE Port ID Default: 0

Range: 0–32767

Format: Numeric

LE port number used to identify the ISDN and PSTN ports on a V5.2 interface. This value maps directly to a specific call con-nection.

Port Type Default: Pstn

Range: N/A

Format: Pre-defined

Specifies whether port is ISDN or PSTN in a V5.2 interface.

Pstn Select this value if you are using PSTN ports. The sample con-figuration uses this value.

Isdn Select this value if you are using ISDN ports. When you select this value, eight additional fields are displayed for configura-tion. They are labeled “ISDN” on the left panel and the P-, F-, and D-Logical Chan ID fields on the upper right panel.

AAL2 Trunk-ing VCC ID

Default: 1

Range: 1–1024

Format: Numeric

Specifies the AAL2 trunk between the CP-IWF and the CO-IWF which carries the CIDs.

Remote IWF ID Default:

Range: 1–255

Format: Numeric

Specifies the remote IWF connecting to the near-end IWF.

LES Interface Port Id

Default: 1

Range: 1–255

Format: Numeric

Specifies the port number of the IAD used on the connection.

Encoding Stan-dard

Default: Itut

Range: N/A

Format: Pre-defined

Specifies the encoding standard used.

Itut ITU-T standards are used for voice encoding. Use this value for voice and voiceband data defined by ITUT specifications.

Af ATM Forum standards are used for voice and voiceband data. Use this value for PSTN connections.

Custom Custom encoding algorithms are not defined by standards.

255-700-762R11.1 14-55



Encoding Pro-file Num

Default: 1

Range: 1–255

Format: Numeric

Specifies the user-assigned profile number for use by voice and voiceband data. Profile 3 and Profile 7 are ITU-T predefined profiles which specify the voice compression and silence removal algorithms. If the custom profile is chosen, all DSP specific parameters have to be specified by the user. If the default profile is chosen, all parameters on the AAL2 trunk, containing this CID, will be used. Enter the profile as a numeric value.

Note: For PSTN connections, use 9,10, or 11. Enter 9 or 10 if using an CellPipe IAD in the configuration.

Admin Status Default: Blocked

Range: N/A

Format: Pre-defined

Specifies the administrative status of the user port.

Blocked The port is not open; no traffic can pass. If the Port Type is Pstn, the status is either Blocked or UnBlocked.

UnBlocked The port is open; traffic can pass. If the Port Type is Pstn, the status is either Blocked or UnBlocked.

Shutdown The port is was open but has been administratively closed; no traffic can pass.


Default: Blocked

Range: See Admin Status field

Format: Pre-defined

Specifies the operational status of the user port on both LE and LES sides. See Admin Status field on lower left panel.

LE Oper Status(display only)

Default: Blocked


Format: Pre-defined

Specifies the operational status of the user port on LE side.

LES Oper Sta-tus(display only)

Default: Blocked


Format: Pre-defined

Operational status of the user port on LES side.

Note: The DSP parameters you select below must be compatible with the selected Encoding Profile Num field. For more information, see the Reference Information Appendix in the DSP2x Voice Server Modules User Guide. The CellPipe IAD supports ATM Forum Profiles 9 and 10.



14-56 255-700-762R11.1



Voice Com-pressionAlgorithm

Default: None

Range: N/A

Format: Pre-defined

Specifies the user-assigned voice compression algorithm used.

None No compression is used on the connection.





G729a-8K Voice compression ITU-T G.729a standard at 8-Kbps.

Silence Detec-tion

Default: Disabled

Range: N/A

Format: Pre-defined

Indicates whether support for silence detection is disabled or enabled.

Enabled Support for silence detection is enabled.

Disabled Support for silence detection is disabled.

Echo Cancella-tion Algorithm

Default: None

Range: N/A

Format: Pre-defined

Specifies which echo cancellation algorithm. is used.

None No echo cancellation is used.

G165-nearEnd ITU-T G.165-nearEnd near end echo cancellation.

G168 ITU-T G.168 echo cancellation.

Tone Detection Algorithm

Default: Disabled

Range: N/A

Format: Pre-defined

Specifies whether fax/modem tone detection is disabled or bypassed.

Disabled Fax modem tone detection is disabled.

Bypass Fax modem tone detection is bypassed Indicates that the fax tones are to be recognized and data sent by fax is not to be pro-cessed by compression and echo cancellation algorithms.

Note: For PSTN connections, use this value.



255-700-762R11.1 14-57



Viewing a V5.2 User Port

Begin







4 Right-click within the V5 Variant Configuration Table and a menu appears (see Figure 14-37). Select Display.

Translation Type

Default: None

Range: N/A

Format: Pre-defined

Specifies which companding standard is used. A law is Euro-pean; Mu law is Japanese and North American.

None Not companding standard is used.

MuLaw2muLaw

Companding standard is Mu law to Mu law.

ALaw2aLaw Companding standard is A law to A law.

V5.2 Applications: You must use this value for V5.2 applica-tions.

Note: Use this setting for PSTN and ISDN Port Types.

MuLaw2aLaw Companding standard is Mu law to A law.

ALaw2MuLaw Companding standard is A law to Mu law.



14-58 255-700-762R11.1



The VIEW V5 User Port Entry window appears (see Figure 14-39).


End

Updating a V5.2 User Port

Begin






he View V5 User Port Table window appears (see Figure 14-36).

4 Right-click within the V5 Variant Configuration Table and a menu appears (see Figure 14-37). Select Update.

Figure 14-39. VIEW V5 User Port Entry Window

255-700-762R11.1 14-59



The UPDATE V5 User Port Entry window appears (see Figure 14-40).

Note: The only field you can change on this window without deleting the V5.2 User Port is the Admin Status field.

5 After modifying the configuration, click Update. To cancel, click Reset.

6 Click Close.

End

Deleting a V5.2 User Port

Begin







Figure 14-40. UPDATE V5 User Port Entry Window

14-60 255-700-762R11.1




End

Table 14-17. Deleting a V5.2 User Port

To delete a V5.2 User Port... do this...



b Click Delete.





b Right-click the mouse within the V5 User Port Entry win-dow and a menu appears (see Figure 14-37). Select Delete.



255-700-762R11.1 14-61


Chapter 14 Configuring V5.2 European IDLCAccessing the V5 B Channels CID Table

Accessing the V5 B Channels CID Table

Begin

1 On the V5 User Port Configuration window select Isdn in the Port Type field.

2 Select Pra in the ISDN Port Type field.

3 Enter the appropriate values in the P-Logical Chan ID, F-Logical Chan ID, and D-Logical Chan ID fields. For descriptions of these field values see Table 1-1.

4 Select UnBlocked in the Admin Status field.

5 Click Add.

The B Channels Table button becomes active.

6 Click B Channels Table.

The View V5 B Channel CID Table window appears (see Figure 14-41).

Figure 14-41. V5 B Channels CID Table Window

Table 14-18. V5 B Channel CID Table Window Field Descriptions


IntfId: Default: 001

Range: 1-256

Format: Numeric

Identifies the interface ID number.

VariantId: Default: 000

Range: 0-127

Format: Numeric

Identifies the variant ID number for the interface.

14-62 255-700-762R11.1



Begin

LEPortId: Default: 00001

Range: 0-32767

Format: Numeric

Identifies the LE Port ID number.

Chnl Default: N/A

Range: 1-31

Format: Numeric

Identifies the channel number.

CIDNum Default: 000

Range: 16-223

Format: Numeric

Identifies the CID number.

Table 14-18. V5 B Channel CID Table Window Field Descriptions (Continued)


255-700-762R11.1 14-63



14-64 255-700-762R11.1


A Troubleshooting the EMS-PSAX

Troubleshooting TopicsThis appendix addresses several troubleshooting topics for problems involv-ing:

• Installing/launching the EMS-PSAX

• Windows accessed from the Main Menu Bar

• IP addresses

• I/O and server modules

• Configuring interfaces or connections

• NSAP addresses

• Using HP OpenView NNM with the EMS-PSAX

• Using the EMS-PSAX on Solaris

• Other miscellaneous problems when using the EMS-PSAX

Before you begin troubleshooting problems with the EMS-PSAX, make sure that you understand the problem and the condition of the EMS-PSAX at the time of the reported problem. You should have the following information available to help expedite problem isolation and resolution:

• A description of the problem

• How often the problem occurred

• The events, including any system or network configuration changes, that immediately preceded the problem

• The amount of traffic running on the EMS-PSAX and the interface(s) con-figured immediately before the problem occurred

• The scope of the problem, including the parts of the network impacted and the number of users affected

Launching and Logging in to the EMS-PSAX

Cannot Log Into the EMS-PSAX

Possible Causes/Items to Check

The EMS-PSAX server will not launch if HP OpenView NNM background processes are not started. Check to be sure that the EMS-PSAX server is run-ning. Check to see that you used the correct username, password, and case.

Corrective Action

After doing the checks mentioned above, if you are still unable to log in, con-tact your Administrator.

Reference

See Chapter 5 in the appropriate Navis® EMS-PSAX Quick-Start Guide.


255-700-762R11.1 A-1

Appendix A Troubleshooting the EMS-PSAXTroubleshooting Topics

Setting Up a Client on the Same Subnet as the EMS-PSAX Server Causes the Client to Malfunction


Configuration problems may exist with the way your network is set up. These problems may have prevented broadcast messages coming from the EMS-PSAX server from reaching the client.

Corrective Action

Treating the client as if it were on a different subnet may resolve these issues; try setting the client up as if were on a different subnet than the server.

Reference


The EMS-PSAX Client Does Not Connect to the Server


Unfavorable network conditions or possible failure in the network. The EMS-PSAX uses SNMP, while ping uses ICMP and telnet uses TCP. If you lose connectivity to the EMS-PSAX, check whether you have SNMP access to the PSAX from the workstation running the EMS-PSAX.

Corrective Action

1. Perform the appropriate action according to the OS of your workstation (press Enter after typing the command line).

2. If you are using the Client/Server application, the workstation running the EMS-PSAX EMS is the server workstation. To check whether you have SNMP access to the PSAX from the workstation running the EMS-PSAX, you must have HP OpenView NNM on the workstation. Type snmpget from the /opt/OV/bin directory.

Reference


Table A-1. Enabling Client and Server Connectivity

If you have this OS...

do this...

Solaris a Launch osagent.

b Locate the directory cd \EMS-PSAX direc-tory\VBAgent\SOLARIS.

c At the command prompt, type: osagent

Windows XP/2000/NT

a Launch osagent.

b Locate the directory cd \C:EMS-PSAX direc-tory\VBAgent\NT.

c At the command prompt, type:osagent -C

A-2 255-700-762R11.1



Using the Main Menu Bar

Cannot Open a Device

Scenario 1

If you are an unauthorized user for a given PSAX device, an error message similar to Figure A-1 will appear when you attempt to open the device.


You must be an authorized user in order to log into certain devices, as config-ured by an Administrator user. An Administrator can specify user access lists for devices to provide authorization.

Corrective Action

After doing the checks mentioned above, if you are still unable to log in, con-tact your Administrator.

An Administrator can do the following:

Begin

1 In the Main EMS-PSAX window, select View > Device List.

2 Right-click the device that you want to open. Select Update.

3 In the Update Device Dialog window, do either a or b:

a Select the User Access List field so that the checkmark does not appear in the checkbox.

b Click User Access List, and add a user to the User Access List win-dow by right-clicking within it and selecting Add a User. Select the appropriate user (your choices are the same users found in the User List) and click Add.

End

Reference

See Chapter 3 in the appropriate Navis® EMS-PSAX User Guide.

Scenario 2

When attempting to open a device, an error appears, such as “Device open failed: null.”

Figure A-1. Unauthorized User Error Message

255-700-762R11.1 A-3




An Administrator can forcibly disconnect EMS-PSAX client sessions if they become corrupted. This feature frees server resources and reduces/prevents server data corruption.

Determine whether an EMS-PSAX client has the affected PSAX device open or not. If so, use Procedure 1 below. If not, use Procedure 2.

Corrective Action

Procedure 1.

Begin

1 From the Main EMS-PSAX window, select View > Show Logged in Users.

The Users Logged On Server window appears (see Figure A-2).

2 Select a client in the list, and right-click the entry.

3 Select Forced Client Shutdown in the menu that appears.

4 A confirmation window appears (see Figure A-3). Press Yes to discon-nect the client from the server. Press No to cancel.

Figure A-2. Users Logged On Server Window

Figure A-3. Client Shutdown Confirmation Window

A-4 255-700-762R11.1



You cannot disconnect the client session that you are working from. If you attempt to do so by mistake, an error message appears (see Figure A-4).

End

Procedure 2.

Begin

1 From the Main EMS-PSAX window, select View > Device List > SNMPv2cDeviceList.

The Device List window appears.

2 Select a device in the list and right-click the entry.

3 Select Unload Device > Force Unload from the menu that appears.

A confirmation window appears (see Figure A-5). Press Yes to unload the client from the server. Press No to cancel.

4 If you selected Yes, a final confirmation window appears (see Figure A-6).

End

Cannot Add Users to the User List


Only users with Administrator access privileges can modify the User List to add new users and to change the default password.

Figure A-4. Error - Cannot Terminate Client Window

Figure A-5. Force Unload Confirmation Window

Figure A-6. Force Unload Complete Window

255-700-762R11.1 A-5



Check to see if you are logged in as an Administrator by doing one of the fol-lowing:

• Click View > User List and view your status in the Role column.

• View the Title Bar on the Main EMS-PSAX window—it displays the user’s name and security access level.

Corrective Action

Contact your Administrator to change your security access level or to add users to the User List.

Reference

See "Adding Users to the User List" in Chapter 3.

Cannot Add Devices to the Device List


Only users with Administrator or Configurator access privileges can add devices to the Device List and modify the Device List. Only Administrators can view and modify the User List. Check your security access privilege level.

Check to see if you are logged in as an Administrator or Configurator by doing one of the following:

• Click View > User List and view your status in the Role column.

• View the Title Bar on the Main EMS-PSAX window—it displays the user’s name and security access level.

Corrective Action

Contact your Administrator to change your security access level or to add devices to the Device List.

Reference

See "EMS-PSAX System Security" the appropriate Navis® EMS-PSAX Quick-Start Guide. See also "Adding a Device to the Device List" .

Cannot View User Documentation From the Help Option in the Menu Bar


To view the user documentation, you must have Acrobat Reader installed on your workstation. Check to see if the Acrobat path listed in the User Proper-ties window is correct.

Corrective Action

Close the EMS-PSAX. Install Acrobat Reader on your workstation. Log in to the EMS-PSAX.

Reference

See Chapter 3 of the appropriate Navis® EMS-PSAX User Guide.

Cannot Change User Properties for Your EMS-PSAX


Check the properties set in the aqv.properties file for your workstation.

A-6 255-700-762R11.1



Corrective Action

To change user properties for your EMS-PSAX Client/Server application, you must change the properties in the aqv.properties file on the server machine, then restart the server.

You can also change the debug level from the client on the server machine only. Changing the debug level on clients that are not on the server machine will have no effect.

Reference

See "EMS-PSAX System Properties" in Chapter 5.

IP Addresses

Cannot Determine IP Address or Community Name of a Device


N/A

Corrective Action

To determine the IP address of a device, log on to the device through the con-sole port on a CPUn module in the device. On the Console Interface Main Menu, select the Site-Specific Configuration menu option and view the value in the Switch IP Address field. If this value is blank, view the value in the CPU IP Address field.

To determine the community name of a device, log on to the device through the console port on a CPUn module. On the Console Interface Main Menu, select the User Options menu option and view the value in the [Current SNMP readwrite community string] field (appears when in the Hybrid authentication mode). To change this value, enter up to 53 characters in the Next SNMP readwrite community string field.

After making these changes, you must save the PSAX configuration and reboot the PSAX device.

Reference

See Chapter 5.

Cannot Set the Switch IP Address Using the EMS-PSAX

Possible Causes/Items to CheckN/A

Corrective Action

The switch IP address and IP Mask must be set locally over the serial console port on the appropriate primary PSAX 1000, 1250, 2300, or 4500 CPUn mod-ule.

ReferenceSee Chapter 4.

255-700-762R11.1 A-7



Cannot Open a Device

Symptom

You receive a “Device Opened Failed” error message.


N/A

Corrective Action

Close all EMS-PSAX clients accessing the PSAX device and unload the PSAX device from the EMS-PSAX server.

Reference

N/A

Cannot Open a Device Using Windows XP/2000

Symptom

You are unable to open a device and receive the following error message:

“EMS-PSAX client encountered an error; Explanation: Device Open Failed. Check device IP address and community name.”


The IP path to the PSAX may not allow UDP traffic such as SNMP or large packets.

Corrective Action

Ensure that the switch IP address and SNMP community name are correct. The SNMP community name is case-sensitive, and you must use the read/write community name.

ReferenceSee the section, "EMS-PSAX System Security" in the appropriate Navis® EMS-PSAX Quick-Start Guide.

See Chapter 3 in the appropriate Navis® EMS-PSAX Quick-Start Guide for a list of the system software versions supported by the PSAX devices.

Cannot Open a Device from theOpen Device Window


If you are unable to open a device from the Open Device window, check the following:

• Ensure that you have TCP/IP connectivity to the PSAX device by pinging the device from the HP OpenView NNM Fault Menu or from the command line.

• Ensure that the system software revision on the PSAX device is supported by the version of EMS-PSAX software you are running.

• Ensure that the switch IP address and SNMP community name are correct. The SNMP community name is case-sensitive.

Corrective Action

After doing all the checks described above, press Ctrl+O to open a device.

A-8 255-700-762R11.1



Reference

See the section, "EMS-PSAX System Security" in the appropriate Navis® EMS-PSAX Quick-Start Guide.

See Chapter 3 in the appropriate Navis® EMS-PSAX Quick-Start Guide for a list of the system software versions supported by the PSAX devices.

Cannot Update the EMS-PSAX GUI Display; Do Not Receive SNMP Trap Messages


If the EMS-PSAX GUI does not automatically update, or refresh the window, panel, or tab, check to see that the managed PSAX devices are configured to send traps to the management workstation hosting the EMS-PSAX ( the server). This may also be caused by not getting a trap that has been discarded by a congested management network.

Corrective Action

When configuring PSAX devices to direct traps to the management worksta-tion, click the Site Specific tab in the EMS-PSAX GUI, enter the IP address of the EMS-PSAX server as one of the five designated trap recipients in the SNMP Trap Destinations panel, and click Apply. In the Main EMS-PSAX Menu Bar, click Device > Save PSAX Configuration.

The EMS-PSAX will not operate properly nor display accurate data unless the management station or server on which the EMS-PSAX resides is designated to receive traps from a PSAX device.

If the EMS-PSAX detects that the management station IP address or server IP address is not one of the SNMP trap destinations for the PSAX system, a mes-sage displays to prompt you to automatically enter the address. Click OK and the EMS-PSAX will add you to the device's trap list, if space is available.

Reference

See Chapter 5.

Installing/Upgrading the EMS-PSAX Software

Diagnosing Errors Using the EMS-PSAX Installation Log File

The EMS-PSAX creates various installation logs to aid in diagnosing problems encountered during EMS-PSAX installation.

The log files that are created during EMS-PSAX installation are as follows:

• /opt/NEP/install.log (on Solaris workstations)

• C:\Program Files\NEP\install.log (on Windows workstations)

These logs contain a list of all the files installed.

• /tmp/nep_install.log (on Solaris workstations)

• C:\temp\nep_install.log (on Windows workstations)

The following logs detail the various installation steps and include any errors that occur during installation.

• /opt/NEP/OV_AQV/Configure_Aqv.log (on HP OpenView NNM worksta-tions)

255-700-762R11.1 A-9



This is an HP OpenView NNM configuration log, created if /opt/NEP/OV_AQV/configure.aqv fails. This file is created only for the EMS-PSAX Client/Server application.

• /opt/NEP/OV_AQV/Unconfigure_Aqv.log (on HP OpenView NNM work-stations)

This is an OpenView configuration log, created if /opt/NEP/OV_AQV/unconfigure.aqv fails. This file is created only for the EMS-PSAX Client/Server application.

To print installation data to the console for debugging, set the following envi-ronment (env) variable by typing:

LAX_DEBUG=true

Cannot Access the EMS-PSAX CD-ROM Using File Manager on Solaris Workstation


To install the EMS-PSAX software using the File Manager application in Sun Solaris, you must be logged in as root. You cannot enter an su command in one window, such as a terminal window, while logged into the Solaris work-station as a user other than root and use the File Manager application to install the EMS-PSAX software.

Corrective Action

If you are not logged in as root on the Solaris workstation, you must log out and then log in as root.

Reference

See the appropriate Navis® EMS-PSAX Quick-Start Guide.

Cannot Install the EMS-PSAX on Solaris


1. The Sun Solaris operating system software, including specific JRE patches, must be loaded on your management station before you can install and run the EMS-PSAX software. If the installation wizard does not appear during installation, your Solaris machine probably does not have the Solaris JRE patches required for the EMS-PSAX operation.

2. Before you install the EMS-PSAX software on a Solaris workstation, check that the $DISPLAY environment variable has been set correctly. If this variable is not set correctly, the EMS-PSAX install command (./install.me) will not work because you will have no way to supply the required input. Administrators should perform this task when they are creating root or user accounts. However, it is possible that this variable is not set correctly on a given workstation. To view your current display setting, type at the command prompt: echo $DISPLAY

A-10 255-700-762R11.1



Corrective Action

1. Install the required JRE patches on your workstation that are listed in the section mentioned in the Reference section below.

2. To verify that the $DISPLAY environment variable is set correctly, type at the command prompt: /opt/openwin/bin/xtermIf an xterm window appears, then the $DISPLAY environment variable is set correctly. If the command does not work, and the xterm window does not appear, then the variable is not set correctly, and you will have to use the appropriate commands to set it. The commands to use are dependent on the UNIX shell you are using, and are available in Sun Solaris user manuals.

Reference

See "JRE Patches" in Chapter 3 in the appropriate Navis® EMS-PSAX Quick-Start Guide for a list of required patches. See also the Navis® EMS-PSAX Quick-Start Guide for the Client/Server Application.

Checking Which Version of the EMS-PSAX Is Installed on Your Workstation


The ways to check your workstation to see if a version of the EMS-PSAX EMS is installed on your workstation and/or identify the version are:

Solaris. At the command prompt, type: /opt/NEP/bin/nepversion and press Enter. The EMS-PSAX software ver-sion (if any) is displayed (see Figure A-7 and Figure A-8).

Figure A-7. Terminal Window (Displaying EMS-PSAX Software Version)

Figure A-8. Terminal Window (When EMS-PSAX Software Does Not Exist on This Workstation)

255-700-762R11.1 A-11



Windows. Select Start > Programs > Lucent Technologies > Navis EMS-PSAX VersionNumber and view the version number (see Figure A-9). If it is not dis-played on the menu item, then select the menu item and log in. After logging in, select Help > About from the Main Menu Bar.

Corrective Action

N/A

Reference

See in the appropriate Navis® EMS-PSAX Quick-Start Guide.

I/O and Server Modules

Cannot Change Values on a Port and Channel Configuration Window


All interfaces must be out of service before changes can be made to the port settings; otherwise, the Apply button will appear to be ghosted.

Corrective Action

If you make modifications to a port and channel configuration and want to revert back to the original settings, click Reset before clicking Apply. Once you click Apply, the settings cannot be reset by clicking the reset button. The original settings will be restored if the PSAX device is rebooted before the configuration is saved.

Reference

See the Navis® EMS-PSAX Modules Configuration Guide.

Cannot Remove Ghosted Modules


If a configured I/O or server module is removed from the PSAX device, a "ghosted" version of the module displays in the Front Panel tab.

Corrective Action

For the ghosted module to disappear, perform the appropriate instructions as described in the referenced section below.

Reference


Figure A-9. Programs Menu (Displaying EMS-PSAX Menu Items)

A-12 255-700-762R11.1



Cannot Overwrite the Existing Interface Configuration on the Copy Interface Configuration Window


The Overwrite configured interfaces box on the Copy Interface Configu-ration window is ghosted.

Corrective Action

Click the box beside Copy interface configuration.

Reference


Cannot Create a Backup PVC Connection


Corrective Action

To establish a backup PVC connection, you must do the following:

1 Create a primary PVC connection.

2 Select an ATM interface type in the Backup ATM Interface panel by selecting the appropriate values in the Slot, Port, and Channel fields (the Interface field reflects the interface type, if any).

3 Click the Create Backup PVC button.

Reference

See the Navis® EMS-PSAX Interface and Connection Provisioning Guide.

Cannot Restore a Connection


Check that you have power to your workstation, and that the EMS-PSAX is running.

Corrective Action

The Connection Restore feature cannot be used after the EMS-PSAX is termi-nated, nor if you lose power to your workstation while the EMS-PSAX is running. Lucent recommends that you immediately reconfigure the desired interface after deleting it, and then restore its corresponding connection.

Reference

See Chapter 3.

Cannot View Slot 25 in the Front Panel for a PSAX 2300 Device


The Front Panel will not display slot 25 in the Device Tree for the PSAX 2300 system unless an Alarm module is present.

Corrective Action

Install an Alarm module in slot 25 of the PSAX 2300 chassis.

255-700-762R11.1 A-13



Reference

See Chapter 3.

NSAP Database

Cannot View the Remote NSAP Address in the NSAP Database


N/A

Corrective Action

You must assign a local NSAP address to the ATM, circuit emulation, frame relay or HDLC Pass Through interface on the appropriate Interface Configu-ration window before creating an SPVC connection and specifying a remote NSAP address.

Reference


Cannot View a Remote Device in the Remote Switch IP Menu


Corrective Action

If the desired remote device does not appear in the Remote Switch IP pull-down menu, do the following:

1 Highlight the Remote Switch IP field and enter the IP address that corre-sponds to the PSAX device you want to include.

2 Type the desired values into the Slot, Port, and Channel fields.

3 Click Add.

Reference


Cannot Delete an NSAP Address Entry


Corrective Action

To delete a device from the NSAP database completely, you must edit the text file through Microsoft Excel or another text editor application.

Reference


A-14 255-700-762R11.1



General

Cannot Modify an IISP VBR/CBR Route Entry


Corrective Action

If you wish to modify an IISP VBR or CBR route, you must delete it and cre-ate a new route entry.

Reference

Cannot Update or Delete a PNNI Node


You can update or delete a PNNI node only if the node is operationally out of service, and all ATM PNNI 1.0 interfaces using this node are deleted.

Corrective Action

Take out of service and delete all ATM PNNI 1.0 interfaces using this node.

Reference

See Chapter 7.

Cannot View a Current List of SVCs (or Other Data)


SVCs are not automatically updated in the EMS-PSAX GUI.

Corrective Action

From the SVC Connections tab, right-click within the window and a menu appears. Select Refresh to view the current list of SVCs and other connections in the EMS-PSAX.

To display current values for other configuration data, select Device > Refresh Device.

Reference

See "Using the Device Window" in Chapter 3.

Need to Monitor Disk and Memory Usage on CPU


Corrective Action

To check the disk and memory usage on the CPU module(s) installed in the PSAX device, view the Disk and Memory panel on the Diagnostics page.

Reference

See Chapter 9.

255-700-762R11.1 A-15


Appendix A Troubleshooting the EMS-PSAXChecking the Crontab File

Checking the Crontab FileAfter scheduling and performing a PSAX backup configuration, you may optionally check the crontab file to verify that the backup process has occurred. The community name and password are not encrypted in the crontab file.

To check the crontab file, type: crontab -l

The system will display an output similar to this (the lines will wrap the text):

12 23 1 * 4 /opt/NEP/bin/configsave.ksh IP Address Community Name Server IP Address FTP UserName FTP Password

where:

• 12 denotes the value in the Min (0-59) field on the Backup Configuration window

• 23 denotes the Hour (0-23) field on the Backup Configuration window

• 1 denotes the day of the month that the backup occurred

• * is a wildcard, and in this position, it denotes that the backup is performed every month of the year

Note: Whenever the symbol * appears in the crontab string, it denotes that the backup frequency occurs “every,” day/week/month denoted by the position it is in.

• 4 denotes the day of the week

Note: If a * were in this position, it would denote that a backup is per-formed every day.

These descriptions are also described in the crontab manual file. You can access this file by typing: man crontab

Errors Displaying In-band Addresses in HP OpenView NNM

Operational Conditions

The following situations may result in PSAX devices displaying incorrectly in the HP OpenView NNM map:

• If you leave the in-band address at 0.0.0.0, the symbol for the in-band management interface will be displayed with an IP address of 255.255.255.254, which is a broadcast address. This address displays as an extra subnet on the HP OpenView NNM submap if the auto-discovery option is enabled. The in-band address displays only under the first PSAX symbol on the map because HP OpenView NNM only allows the same interface address to display only once on a map.

• HP OpenView NNM will read the secondary CPU IP address and add an additional PSAX symbol on the map for it. If you perform a CPU switcho-ver, it will produce a third PSAX symbol. These symbols will turn red when the switch IP takes over.

These addresses may also display in Router tables.

A-16 255-700-762R11.1


Appendix A Troubleshooting the EMS-PSAXErrors in Applying Interfaces to Ports

Workaround to HP OpenView NNM Problems with Addresses

Do the following to hide secondary CPU IP addresses or unwanted in-band management addresses from the HP OpenView NNM submap.

Begin

Hiding Addresses From HP OpenView NNM Submap

1 Select the HP OpenView NNM symbol belonging to the secondary CPU IP address.

2 Select the Edit >Unmanage Objects option.

3 Select the View Hidden Objects > Hide Selected From All Submaps option.

The secondary CPU IP addresses will not display in the HP OpenView NNM submap.

End

For more information, see the HP OpenView NNM Welcome Collection or NNM Developer’s Collection manual sets.

Errors in Applying Interfaces to PortsAn error may occur when you apply an interface to a channel. If an error condition occurs, the PSAX device sends an SNMP trap that appears in the EMS-PSAX Log tab. The list below includes the most common interface errors that cause the PSAX system to display a message.(See the PacketStar® PSAX Simple Network Management Protocol (SNMP) Trap Reference Guide for more information about the SNMP traps related to interface errors).

• Entering field values that are outside of the configurable range of values

• Attempting to configure an interface for a port or channel that has already been configured

• Attempting to configure an interface that is already in service (must be out of service to be configured or change field values)

• Entering field values that are not recognized by the PSAX system software

For more information configuring ports and channels on the PSAX I/O and server modules in the EMS-PSAX, see the Navis® EMS-PSAX Modules Configu-ration Guide.

Errors in Creating ConnectionsThis section provides instructions on how to create connections and describes the errors that can occur when you are creating them.

If an error occurs while creating a connection, the EMS-PSAX displays an error message. There are many causes for these errors, but the errors that occur the most frequently are described below:

• Using an out-of-range VPI, VCI, or DCLI

255-700-762R11.1 A-17


Appendix A Troubleshooting the EMS-PSAXDisplaying Graphics Properly on Solaris

• Selecting an interface that does not support flow settings that are entered

• Selecting out-of-range transmission parameters

• Attempting to create a connection on an unconfigured interface or an interface that has never been brought into service

• Exceeding the maximum bandwidth available for a VBR and CBR connec-tion

• Attempting to create a connection that already exists

• Attempting to use a VCI, VPI, DCLI, or channel that is already allocated elsewhere

For more information about these SNMP trap messages, see the PacketStar® PSAX Simple Network Management Protocol (SNMP) Trap Reference Guide.

Note: An interface for the appropriate port and channels must be applied and the interfaces must be brought into service at least once before creating a connection.

Note: To create a non-UBR connection type, the committed rates and burst sizes must be adjusted to match a portion of the available bandwidth.

For more information provisioning connections for the PacketStar® PSAX I/O and server modules with the EMS-PSAX, see the Navis® EMS-PSAX Interface and Connection Provisioning Guide.

Displaying Graphics Properly on SolarisIf you launch the EMS-PSAX on a Solaris workstation and opaque boxes dis-play on the screen, perform the steps in the following procedure to display graphics properly on a Solaris workstation.

Begin

Fixing Graphics on a Raptor GFX Video Card

1 Log in as root.

2 To determine the type of graphics card you have, enter the /dev/fbs directory (either in File Manager or using the command prompt).

3 List the contents of the directory by typing ls.

4 If the device file listed is gfxp0, then your system has a PGX32 (Raptor GFX), which has problems in the 8/24 auto-sensing mode.

5 Find the utility program called GFXconfig in the /usr/sbin directory.

6 To see the options’ syntax, type: GFXconfig -help

7 To see your current settings, type: GFXconfg -prconf

The last line should display the following message:

Current Depth: 8/24

A-18 255-700-762R11.1



! CAUTION:You must logout and then login to the system again after making this change.

8 Type GFXconfig -24only

This forces the PGX32 (Raptor GFX) device to use 24 bit color.

9 Type GFXconfig -prconf

The last line should display the following message:

Current Depth: 24

10 Launch the EMS-PSAX and you should be able to view the Login win-dow.

End

255-700-762R11.1 A-19



A-20 255-700-762R11.1


B Setting Up Firewall Support

Overview of This AppendixThis appendix describes how to set up a client workstation, Gatekeeper, and firewall by performing specific tasks when using the EMS-PSAX:

• Set up a firewall between the EMS-PSAX client and server

• Set up a firewall between the EMS-PSAX server and a PSAX device

• Set up an EMS-PSAX client/server configuration in a NAT environment

Firewall SupportThis section describes how to configure a firewalls between the EMS-PSAX server and a PSAX device. If the firewall is between the EMS-PSAX client and server, then a different set of configuration is required (see the section, ““).

For SNMP communication between the EMS-PSAX server and PSAX device, the UDP ports used by the EMS-PSAX server are as follows:

To send SNMP requests or responses, a random UDP port is used. It is selected, dynamically, when the EMS-PSAX server is started (and does not change unless the EMS-PSAX server is restarted). The packets are always sent to port 161 on the PSAX device, the standard SNMP port for an agent.

For receiving traps, the UDP port 162 is used by the EMS-PSAX server, the standard SNMP port where an agent sends traps. (Another port, 6001, is also used, but that traffic is between two processes on the EMS-PSAX server workstation and would not go through the firewall.)

Firewall Between the EMS-PSAX Client and Server

When the EMS-PSAX client and server are separated by firewalls, the Visi-broker Gatekeeper must be used as an IIOP proxy so that the client and server can communicate with one another. The Firewall Support feature described in this section includes procedures for one sample configuration, but is only one of several possible configurations. This feature is available with the EMS-PSAX Client/Server application beginning with Release 5.1.1.

The components must be installed in the following configuration (see Figure B-1).


255-700-762R11.1 B-1

Appendix B Setting Up Firewall SupportFirewall Support

See one of the following sections as shown in Table B-1.

The Gatekeeper should be able to open up connections to the EMS-PSAX Server workstation.

Note: The order in which the following steps are done is optional.

Setting Up the Client Workstation

On the EMS-PSAX client workstation, do the following:

• Change the firewall.client property to true in the aqv.properties file.

• Change the client.properties files according to the directions in the file.

Setting Up the Gatekeeper

On the EMS-PSAX server workstation, do the following:

• If using a Solaris workstation, at the command prompt, type: ./start_gatekeeper

• Change the gatekeeper.properties files according to the directions in the file.

Figure B-1. Sample Network Configuration With Firewall and Gatekeeper

Table B-1. Setting Up Network Components for Firewall Support

If you want to set up this network component for Firewall Support...

See the section...

EMS-PSAX client “Setting Up the Client Workstation”

Gatekeeper “Setting Up the Gatekeeper”

Firewall “Setting Up the Firewall”

Client 1

Client 2

Client 3

Firewall

Gatekeeper

Server

B-2 255-700-762R11.1



Setting Up the Firewall

On the Firewall, open the following TCP ports as described below.

Launching Network Components

Launch each of the following in order:

a Gatekeeper

b EMS-PSAX server (if applicable)

c EMS-PSAX client (if applicable)

End

Visibroker Gatekeeper is a product of Borland Software Corporation (http://www.borland.com/visibroker/gatekeeper/). The Visibroker Gate-keeper can be configured in several different ways and several different envi-ronments. For more information, consult the Borland web site, and refer to the Gatekeeper Guide included on the EMS-PSAX CD-ROM.

Firewall Between the EMS-PSAX Server and a PSAX Device

This section describes how to configure a firewalls between the EMS-PSAX server and a PSAX device. If the firewall is between the EMS-PSAX client and server, then a different set of configuration is required (see the section, ““).

For SNMP communication between the EMS-PSAX server and PSAX device, the UDP ports used by the EMS-PSAX server are as follows:

To send SNMP requests or responses, a random UDP port is used. It is selected, dynamically, when the EMS-PSAX server is started (and does not change unless the EMS-PSAX server is restarted). The packets are always sent to port 161 on the PSAX device, the standard SNMP port for an agent.

Table B-2. Firewall Ports

Map This TCP Port Number... From/To...

TCP Port 683 From any client port to Port 683 on Server.To any client port from Port 683 on Server.

TCP Port 8088 From any client port to Port 8088 on Server.To any client port from Port 8088 on Server.

TCP Port 15000 (or the port defined as the callback port in the gatekeeper.properties file)

From any client port to Port 15000 on Server.To any client port from Port 15000 on Server.

TCP Port 30000 (or the event channel port selected in the aqv.properties file on the client workstation)

From 30000 client port to any port on the ServerTo 30000 client port from any port on the Server.

255-700-762R11.1 B-3



For receiving traps, the UDP port 162 is used by the EMS-PSAX server, the standard SNMP port where an agent sends traps. (Another port, 6001, is also used, but that traffic is between two processes on the EMS-PSAX server workstation and would not go through the firewall.)

EMS-PSAX Client/Server Configuration in NAT Environments

This section describes the configuration to use in a network address transla-tion (NAT) environment since this would facilitate simultaneous use of EMS-PSAX clients for both internal and external NAT environments to con-nect simultaneously (see Figure B-2).

Configuring the Server Workstation

Servers Outside a NAT Environment

Perform the steps in the following procedure to update the configuration of a server workstation inside a NAT environment.

Figure B-2. EMS-PSAX/NAT Environment Scenario

EMS-PSAX ServerEMS-PSAX Client

EMS-PSAX ClientEMS-PSAX Client

Router with NAT

B-4 255-700-762R11.1



Begin

1 Type the following line to the gatekeeper.properties file:

vbroker.se.exterior.proxyHost=host_ip

where host_ip is the external/public IP address of the NAT host.

2 Terminate the EMS-PSAX server by typing: stop_aqvserver

3 Launch Gatekeeper by typing: start_gatekeeper

When launching Gatekeeper, wait until the confirmation message (Gatekeeper for VisiBroker is started) appears before launching the EMS-PSAX server. You may see output similar to:

Starting Gatekeeper for VisiBroker ... Request Forwarding Service is started.Callback Service is started.Administrative Service is started.IOR is stored in gatekeeper.ior.Gatekeeper for VisiBroker is started.

4 Launch the EMS-PSAX server by typing: start_aqvserver

End

Servers Inside a NAT Environment

For server workstations inside a NAT environment, you do not need to make any changes to your default configuration.

Configuring the Client Workstation

Clients Outside a NAT Environment

Perform the steps in the following procedure to update the configuration of a client workstation outside a NAT environment.

Begin

1 In the aqv.properties file, set firewall.client=true (from false)

2 Change the client.properties file and update host_name with the external IP address of the NAT server.

End

Clients Inside a NAT Environment

For client workstations inside a NAT environment, you do not need to make any changes to your default configuration.

Receiving Traps From the NAT EMS-PSAX Server

When a PSAX device is opened for the first time, manually add the exter-nal/public IP address as a trap destination using the Notify and Target Address Table page in the EMS-PSAX GUI. By default, the EMS-PSAX will add the actual IP address of the server as the trap destination.

255-700-762R11.1 B-5



B-6 255-700-762R11.1


C EMS-PSAX Configuration Optionswith HP OpenView NNM

Overview of This ChapterThis appendix describes how to perform specific tasks when using the EMS-PSAX with HP OpenView NNM:

• Generating reports

• Setting up data collection from PSAX devices

• Checking for threshold violations

• Generating alarms and traps

Generating Reports Using HP OpenView NNMWhen the EMS-PSAX Client/Server application is installed on a workstation with HP OpenView NNM, HP OpenView NNM can be used to collect data and generate custom reports using its data collection, data export and report gen-eration capabilities. The PSAX MIB contains the information to support accounting needs. This information can be used to support service-based accounting and billing as follows:

Once the initial configuration is complete, HP OpenView NNM can be pro-grammed to automatically generate this report at regular intervals (weekly, monthly, and so on).

Periodic polling must be performed to obtain usage information from a PSAX device. A PSAX device sends a several connection-based SNMP traps (up to five different destinations at one time) which also can be used for accounting if you want to limit periodic polling. See the PSAX MIB for a complete list and explanation of connection based traps.

For further information on HP OpenView NNM data collection and report generation capabilities, see the Hewlett-Packard web site at http://www.hp.com.

Data Collection and ThresholdingThis section describes how to setup data collection from PSAX devices, check for threshold violations and generate alarms/traps. These tasks are especially useful when monitoring error counter fields such as Errored Seconds, Severely Errored Seconds, and Line Coding Violations for changes in values.

When the EMS-PSAX system is installed with HP OpenView NNM, the EMS-PSAX EMS can be configured to collect the data at predetermined inter-vals, check for any changes from the previous values collected, and check whether the value has changed to indicate that error conditions have occurred, to notify the user using traps.


255-700-762R11.1 C-1

Appendix C EMS-PSAX Configuration Options with HP OpenView NNMData Collection and Thresholding

Setting Up Data Collection

For this section, E1 Port Statistics (Errored Seconds, Severely Errored Sec-onds and Line Coding Violations) are used as an example, but this configura-tion could be performed for any error or other statistic value available from the PSAX device using SNMP.

Begin

1 Launch ovw from the HP OpenView NNM map view (if it is not already running).

2 From the menu, select Options > Data Collection & Thresholds:SNMP.

The Data Collection & Thresholds: SNMP for phobos window appears (see Figure C-1).

3 Select Edit > Add > MIB Objects (see Figure C-2).

Figure C-1. Data Collection & Thresholds: SNMP for phobos Window

C-2 255-700-762R11.1



The MIB Object Selection window appears (see Figure C-3).

Figure C-2. Data Collection & Thresholds: SNMP for phobos Window (Displaying the Edit Menu)

255-700-762R11.1 C-3



4 Double-click through the fields of the MIB Object ID panel and select e1PortStatsCurrentESs (see Figure C-4), and click OK.

Figure C-3. Data Collection & Thresholds / MIB Object Selection Window

C-4 255-700-762R11.1



The Add Data Collection for 'Server' window appears.

a Add the PSAX IP address in the Source slot and click Add.

Note: You can collect the statistics from multiple PSAX devices using the same configuration by adding more PSAX devices using the same process.

b Set the Polling Interval field to 10m.

c Set the Collection Mode field to Store, Check Thresholds.

d Click OK.

Figure C-5 and Figure C-6 show how the Add e1PortStatsCurrentESs Collection for phobos window will look before and after you have made the customizations.

Figure C-4. Data Collection & Thresholds / MIB Object Selection Window (Displaying Selection)

255-700-762R11.1 C-5



Figure C-5. Add e1PortStatsCurrentESs Collection for phobos Window (Before Configuration)

C-6 255-700-762R11.1



On the main data collection window, you can see that Errored Seconds is already added to the collected items list.

5 To add the next two items, Severely Errored Seconds and Line Code Vio-lations, select Edit > Copy > MIB Objects with the newly added collection selected (see Figure C-7).

Figure C-6. Add e1PortStatsCurrentESs Collection for phobos Window (After Configuration)

255-700-762R11.1 C-7



The Data Collection & Thresholds / MIB Object Selection window appears (see Figure C-8).

Figure C-7. Data Collection & Thresholds: SNMP for phobos Window (Displaying the Edit Menu and Selection)

C-8 255-700-762R11.1



6 Select e1PortStatsCurrentSESs and click Apply.

7 Select e1PortStatsCurrentCVs and click Apply.

8 Click Cancel.

On the main data collection window, you can see that the three variables are now collected.

Figure C-8. Data Collection & Thresholds /MIB Object Selection Window (Displaying Selection)

255-700-762R11.1 C-9



9 Select File > Save to save this configuration (see Figure C-9).

Note: If you do not perform step 9, all your changes will be lost upon exit.

10 Select File > Close to close the data collection window.

If any of these values changes from its previous value you will receive an event in the Threshold Alarms category of HP OpenView NNM event display stating the parameter changed and the size of the change.

End

Viewing Collected Data

The collected data can also be viewed either in table or graph form. To view collected data, perform the steps in the following procedure.

Begin

1 Select the appropriate collection line in the window

2 Select Actions > Show Data.

The Data Collection & Thresholds / Show Data window appears (see Figure C-10).

Figure C-9. Data Collection & Thresholds: SNMP for phobos Window (Displaying File Menu)

C-10 255-700-762R11.1



3 You can also choose to graph the data by clicking Graph.

If one specific instance Is selected it will graph that instance. If no instance is selected (just click once more on the selected instance to deselect it) all instances will be graphed up to a 25 line limit.

An example is shown in the OpenView Grapher window (see Figure C-11).

Figure C-10. Data Collection & Thresholds / Show Data Window

255-700-762R11.1 C-11


Appendix C EMS-PSAX Configuration Options with HP OpenView NNMUsing the HP OpenView NNM Events Log and Browser

In this graph, all the values collected are 0 because there were no errors dur-ing the period of collection. If there were errors, a spike will be shown in the graph denoting the time and magnitude of the error.

End

Using the HP OpenView NNM Events Log and BrowserHP OpenView NNM collects events from all PSAX devices that have desig-nated its workstation as a trap destination. A finite number of messages are stored, and the oldest messages are discarded. For PSAX device management, these OpenView logs are better suited for central collection to assess the over-all stability for the network. Using the event manager in OpenView, you can acknowledge the messages.

Note: The EMS-PSAX client/server application for HP OpenView NNM automatically installs both the PSAX trap definitions and the PSAX event categories in HP OpenView NNM during installation. The ac120.my MIB definition file is also copied to the /var/opt/OV/shared/mibfiles/Vendor/Lucent directory to be used with HP OpenView NNM.

Figure C-11. Openview Grapher Window

C-12 255-700-762R11.1


Appendix C EMS-PSAX Configuration Options with HP OpenView NNMEvent Logs

Event LogsThe OpenView Events Log serves as a central repository for all incoming events received by the NNM ovtrapd background process. By default, all incoming events are logged to $OV_LOG/trapd.log. When trapd.log reaches 4 MB in size, it is moved to $OV_LOG/trapd.log.old and a new trapd.log file is started.

Events Browser

Overview

The Events Browser is a view of the received events contained in $OV_LOG/trapd.log and $OV_LOG/trapd.log.old. Each user has their own events browser, identified by that user’s login name. By default, each user’s browser can display the most recent 3500 events. As a user deletes events, only that user’s browser is affected (that is, the events are not removed from the trap log files).

Event Browser List

A significant amount of information about each event is listed in the browser:

Ack—Indicates whether or not the event has been acknowledged

Severity—Indicates the importance of this event

Date/Time—Identifies when the event was received

Source—Identifies the node that sent the event

Message—Contents of the message (description of the event)

Once you open your browser, you may select one or more particular events for action. The menus in the browser provide a number of functions for deal-ing with these events.

Tips for Using the Event Browser

Important tips for navigating the event browser:

1. Many messages in a browser will extend well beyond the viewing area of the browser itself. This makes viewing the message somewhat trouble-some in that the scroll bar at the bottom of the browser must be used to move parts of the message into the browser viewing area. However, holding down the right mouse button on a particular message will dis-play the entire message at one time.

2. A second feature has to do with getting to the correct submap for the node that sent the event. Since many environments may have over 1,000 submaps, getting to the correct submap may take a long time. However, you can simply double-click on the event of interest, and the submap containing that node will automatically be opened.

255-700-762R11.1 C-13


Appendix C EMS-PSAX Configuration Options with HP OpenView NNMEvents Browser

Actions on Events

The events browsers are not only useful for cataloging events, but for acting on those events.

Assigning Categories and Severity

Since every operator will have their own events browser, it is possible for you to modify where an event is placed. Assigning an event to another category allows you to 'move' events around as needed.

For example, the administrator could create a new category called "Acknowl-edged Events." Operators could then reassign acknowledged events to this category and keep the main part of the browser "clean." Remember how-ever, that every event is always in the All Events category.

In much the same way, assigning severity allows you to raise or lower the importance of an event. This is a tool that allows the you to maintain individ-ual browsers.

Acknowledging and Deleting Events

After an event has been dealt with, you can acknowledge an event by click-ing the left mouse button in that event's Ack column of the browser. The color of an acknowledged event no longer affects the color of its correspond-ing category in the Event Browser. You can toggle the acknowledgement of an event by clicking in the same Ack column.

You can delete an event from the browser through an option in the Actions > Delete submenu.

Note: These events are not deleted from the event log of the system, only from this specific view.

Saving and Restoring Events

You can perform a text copy of all the events in the All Events Browser by selecting the File > Save Browser State menu option from the browser menu bar. This is then stored in a file named xnmevents.User_name, located in the logging directory. This file is also written automatically when exiting an OpenView session.

Restoring from the browser state file is useful if events are accidentally deleted from the browser. By reloading from the state file, the browser will be reloaded with all events stored in the state file, plus all events received since the state file was last written.

It is also possible to reload the browser with all of the most recent events (3,500 is the maximum by default) from the system-wide trapd.log file by selecting the File > Reload Event Log > Unfiltered menu option from the events browser window. Reloading from trapd.log is useful if the events that are of interest are not in the current browser, nor in the browser state file.

C-14 255-700-762R11.1


Appendix C EMS-PSAX Configuration Options with HP OpenView NNMAdditional Operations

Highlighting Event Sources

You can call this function without using the menu options. However, if you select Action > Highlight Source, the source will become highlighted, and will also open the submap of the source. This is the same function that is pro-vided by double-clicking on an event in the browser, this makes it easy to locate nodes that may have serious problems.

Additional OperationsThe Additional Actions area is designed to hold any number of desired func-tions. These functions include:

• Sorting Events

• Printing Events

• Custom Actions for Events

The custom actions are created by the administrator to address site-specific needs. Actions in this and other areas may be taken on selected events, fil-tered events, or all events.

Filtering Events

Even with multiple event categories, individual event browsers can become overloaded with hundreds of events. Trying to sort through this many events can make even a simple task much more complex and thus more prone to error. To help resolve this problem, there is event filtering.

Browser filters may be defined and assigned to temporarily restrict the view to a desired subset of events. Once a filter is defined, it can be saved for future use. The bottom line of the browser window will list all filters currently in use.

Note: All events that are not currently in the filtered view are still in the browser, and will be saved if a browser state file is saved.

Event Filter Elements

Accessing the View > Set Filters menu option displays a dialog box that allows you to define the scope of the filter. By default, nothing is filtered, so all of the events in a particular category will be displayed. Virtually every aspect of an event can be used as a means of filtering. You may select from the following options:

• Match Severity—This restricts the displayed events to only those that have the specified severity level. Select the button for the severities you wish to display.

• Match Acknowledged/Unacknowledged—To view only those events that have (or have not) been acknowledged.

• Match by Time Received: On or After—This function allows the definition of a time window for the events being viewed. It also has a button that allows setting the resolution of the time window, which makes it easier to zero in on a desired time frame. Low resolution allows increments of days

255-700-762R11.1 C-15


Appendix C EMS-PSAX Configuration Options with HP OpenView NNMAdditional Operations

and hours, while high resolution allows increments of minutes and sec-onds. For example, this selection would allow the operator to view only events that came in since noon yesterday.

• Match by Time Received: On or Before—Like the previous selection this also sets a time based on viewing window, and can be used in conjunction with it to further narrow the viewing time.

• Match Source—The operator may select systems from the map, or enter the system names directly in the dialog box. When used this selection restricts the displayed events to those from the listed sources.

• Match Message String—For cases where a particular message is being sought, this selection works well. It prompts for a matching string and then displays events that contain that string. Patterns based on regular expressions can also be used.

• Match Event Type—This selection has two choices:

~ All Events that do not provide a filter

~ Selected Event Type Only—matches only events that are of the same type as the selected message. (Events are of the same type if they come from the same type trap.)

Note: Any or all of these filter settings may be used. In addition, the set-tings may be saved for reuse at a later time. This means that you can create a set of filters that are most common. Filtered browsers may also be saved such that the filtered messages may be reloaded later. To clear the filters, select View > Clear Filters and the full set of events for that browser will return to the display.

C-16 255-700-762R11.1


Navis EMS-PSAX User Guide for the Client/Server Application

Documents

Transcript of Navis EMS-PSAX User Guide for the Client/Server Application