ORCA RDT-8G SOFTWARE ANUAL

Transcription

ORCA RDT-8G
SOFTWARE MANUAL
Release 7.0
299-297-501
ORCA RDT-8g Software Manual
Nuera Communications, Inc.
February, 2003
First Edition (February, 2003)
This edition applies to the Nuera Communications, Inc. , ORCA RDT-8g
release 7.0 gateway. The licensed product described in this document and
all licensed materials that are available for it are provided by Nuera
under terms of the agreement for Nuera licensed products. Nuera periodically makes additions, deletions, or changes to the information in this document. Before you use this document, consult Nuera or your distributor
for the most recent Nuera edition.
The author and publisher have made reasonable efforts to ensure the
accuracy and timeliness of the information in this book. However, neither
the author nor the publisher shall have any liability with respect to loss
or damage caused or alleged to be caused by reliance on any information
in this book.
Nuera may have patents or pending patent applications covering material
in this document. Furnishing this document does not of itself constitute a
grant of any license or immunity under any patents, patent applications,
trademarks, copyrights, or other rights of Nuera, or of any third party, or
any right to refer to Nuera in any advertising or other marketing activities. Nuera assumes no responsibility for any infringement of patents or
other rights of third parties that may result from use of the material in
this document or for the manufacture, use, lease, or sale of machines or
software programs described herein, outside of any responsibilities
assumed in the original or subsequent purchase or lease agreements.
This document may contain information about, or make reference to,
Nuera products, programming, or services that are not available in your
country. This information must not be construed to mean that Nuera
intends to make available such products, programs, or services in your
country.
A form for your comments is provided at the back of this document. If the
form has been removed, address your comments to: Nuera Communications, Inc., Information Development Group, 10445 Pacific Center Court,
San Diego, CA 92121.
Nuera may use or distribute any of the information you supply in any way
it believes appropriate without incurring any obligation to you.
No part of this publication may be reproduced in any manner without the
written permission of Nuera, Inc. For information, write to: Nuera Communications, Inc., Legal Office, 10445 Pacific Center Court, CA 92121.
© 2001, 2003 by Nuera Communications, Inc.
Important Notices
Warnings!
See the “Regulatory Information” appendix in
this book for specific regulations for various localities.
These are Class A products. In a domestic environment, these products may
cause radio interference, in which case the user may be required to take
adequate measures. The domestic environment is an environment where
the use of broadcast radio and television receivers may be expected within
a distance of 10 meters of the apparatus concerned.
10445 Pacific Center Court, San Diego, CA 92121 (858) 625-2400; FAX (858) 625-2422
ORCA User Library
All books that support the ORCA product line are provided
on a compact disc (CD) in Adobe Acrobat format. Included on
the CD is the appropriate version of Adobe Acrobat Reader.
This section lists the titles of all the books in the ORCA
library. To order any of these books, contact your distributor
or Nuera directly. To make comments or suggestions regarding any of these books, direct your correspondence to
tac@nuera.com.
Number
Book
299-225-4nn
ORCA SSC Softswitch User’s Guide
This book presents conceptual information about the use and functionality of the ORCA SSC
Softswitch. It also provides information about installing and configuring SSC for use with other
equipment.
299-193-5nn
ORCA GX-Series Software Manual
This book is designed for the system integrator/system administrator who needs to configure
ORCA GX gateways at an end-user site. Its purpose is to guide this individual through the configuration steps required to get the ORCA GX gateway correctly configured using network management software.
299-297-5nn
ORCA RDT8g gateways at an end-user site. Its purpose is to guide this individual through the
configuration steps required to get the ORCA RDT8g gateway correctly configured using network management software.
299-298-5nn
ORCA RDT-8v Software Manual
ORCA RDT8v gateways at an end-user site. Its purpose is to guide this individual through the
configuration steps required to get the ORCA RDT8v gateway correctly configured using network management software.
299-252-5nn
ORCA BTX-8 Software Manual
ORCA BTX-8 gateways at an end-user site. Its purpose is to guide this individual through the
configuration steps required to get the ORCA BTX-8 gateway correctly configured using network management software.
299-335-1nn
ORCA Gateway Hardware Manual
This book presents conceptual information about the use, functionality, and specifications of the
ORCA gateways, including installation steps and information.
Additional ORCA books are available in hard copy form
from Nuera. For information regarding pricing and availability, contact a sales representative at:
10445 Pacific Center Court
San Diego, CA 92121
858-625-2400
Trademarks Used in This Manual
The following list contains trademarks that are used in this
manual. In the United States, these trademarks are registered trademarks; in World Trade countries, these trademarks are not registered.
Trademark
Trademark Owner
Access Plus F50/F50ip/F100/
F120/F200/F200D/F200ip
Amphenol
Amphenol, Inc.
ANSI
American National Standards
Institute
Cisco
Cisco Systems, Inc.
CS-ACELP
Lucent, SiproLab, and NTT
E-CELP
IBM
International Business Machines, Inc.
Microsoft
Microsoft Corporation, Inc.
OpenView
Hewlett-Packard Company
ORCA
Teflon
E. I. duPont de Nemours and
Company
UNIX
The Open Group
VT100
Compaq Digital Equipment
Corporation
Trademark
Trademark Owner
Windows 95/98/NT/2000
Microsoft Corporation, Inc.
Procomm Plus
Symantec Corporation
TABLE OF CONTENTS
About This Book . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xv
Who Should Use This Book . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xv
How To Use This Book . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xv
Conventions Used in This Book . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xvi
How Numbers Are Used . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xvi
Replaceable Input Values. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xvii
Textual Callouts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xviii
Getting Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xix
Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xix
Last Resort . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xx
Contacts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xx
Chapter 1. Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Nuera Configurator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
NueraView . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
RDT-8g Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
21
21
22
22
Chapter 2. Nuera Configurator Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Installing the Nuera Configurator. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Installation Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Installation with a Firewall . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
25
26
26
28
Chapter 3. Configuring a Gateway . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Main Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
System Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Basic Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Adding Cards. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Adding the Interface Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Adding New Subscribers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Editing the Media Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Configuring the DSXs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Add a Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
31
31
31
36
40
41
44
45
48
51
53
Chapter 4. Typical Network Application Configuration . . . . . . . . . . . . . . . . . . . . . . . . .
General Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Functional Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
GR-303 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
NCS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
55
55
56
56
57
58
Chapter 5. Managing an ORCA Gateway . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Checking the System Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Card Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
ix
ORCA BTX-8 Software Manual
DS1 Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
DS0 Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Power and Fan Modules’ Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Interface Group Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Checking the System Performance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Ethernet Performance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Checking the System Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Determining Clock Reference. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Version Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Software Upgrade Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Downloading Code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Maintenance Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Resetting a Card . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Forcing a CM Switchover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Resetting an ORCA RDT Remotely . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
67
68
69
70
70
70
71
71
72
73
74
76
76
77
77
Chapter 6. Viewing Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Alarm Tree . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Alarm Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Pop-up Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Alarm List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Pop-up Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Alarm Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Status Bar Display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Severity Levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
System-wide Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
History Size . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Alarm Throttling. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
How to Remedy an Alarm State . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Using HP OpenView to View Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
79
79
80
81
82
82
83
84
84
85
86
86
86
87
88
Appendix A. NueraView Installation and Configuration. . . . . . . . . . . . . . . . . . . . . . . . . 89
Installing HP OpenView . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
Installing NueraView . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
Installation with a Firewall . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
Setting Up NNMBroker . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
NNMBroker Menu Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
NueraView Maintenance Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
Directing Alarms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
Updating the MIBs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
Bibliography . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
Hardware Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
Network Management Publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
Hewlett Packard Publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
Warranty . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
Reader’s Comment Form . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
x
LIST
OF
FIGURES
Figure 1. Initial Installer Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 2. License Agreement Screen. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 3. Installation Menu Screen. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 4. Nuera Configurator Main Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 5. Nuera Configurator System Configuration Screen . . . . . . . . . . . . . . . . . . . . .
Figure 6. Default View of Unconfigured Cards. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 7. HUB2/HUB2X Configuration Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 8. CM/CMX Configuration Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 9. UPM3/UPMX Configuration Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 10. GR-303 Configuration Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 11. Subscribers Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 12. Voice Template Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 13. The DSX Configuration Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 14. The Manager Config Tab on the System Screen . . . . . . . . . . . . . . . . . . . . . .
Figure 15. Cable Access Network Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 16. Interface Group Addition Wizard, Screen One . . . . . . . . . . . . . . . . . . . . . . . .
Figure 17. Interface Group Addition Wizard, Screen Two. . . . . . . . . . . . . . . . . . . . . . . .
Figure 18. Interface Group Addition Wizard, Screen Three . . . . . . . . . . . . . . . . . . . . . .
Figure 19. DS0 Configuration Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 20. DS1 Status Tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 21. DS0 Status Tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 22. System Status Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 23. The Ethernet Performance Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 24. System Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 25. Card Detail Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 26. Advanced Configuration Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 27. Nuera TFTP Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 28. Advanced Unit Configuration Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 29. Alarm Sheet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 30. NNMBroker Initial Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
26
27
28
32
37
41
42
43
44
45
46
49
52
54
59
60
61
62
64
67
68
69
70
71
72
73
74
75
80
93
xi
xii
LIST
OF
TABLES
Table 1. Out of Warranty Repairs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
Table 2. Extended Warranty . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
xiii
xiv
ABOUT THIS BOOK
This book presents information that explains the concepts
behind the design and operation of the Open Reliable Communications Architecture (ORCA) telephony gateway. Specifically, this book provides information on the RDT-8g
release 7.0 gateway. It provides system design and application information, and product features. The purpose of this
information is to help you install, use, and maintain an
ORCA gateway.
Who Should Use This Book
This book is for product distributors, systems integrators,
systems analysts, and network administrators who design,
install, configure, and maintain wide area networks (WANs)
and large-scale communications applications. It contains
conceptual and practical information about how to use the
ORCA gateway within your network.
How To Use This Book
If the ORCA gateway is new to you, you should read all the
chapters in this book to familiarize yourself with all of the
product features and functions. In addition, see "ORCA User
Library" on page vi for an annotated list of books in the
ORCA library.
If your network is already functional, you can use the ORCA
Hardware Manual to install a gateway, and then use the
included software manual, (e.g., ORCA GX-Series Software
Manual) to learn how to use the Nuera network management software to configure the gateway. If you need more
information to help you integrate an ORCA gateway into
your network, refer to the manuals that support your network components.
Conventions Used in This Book
This book uses specific conventions to show the following
types of information:
•
Number usage
•
Replaceable input values
•
Messages
Read the following sections to learn more about how this
information is shown in the rest of the book.
How Numbers Are Used
When numbers are shown in this book, they can appear as
descriptive values or as data to be manipulated internally.
Decimal values are used frequently; however, alternate
number bases are useful when internal data is shown.
Large Decimal Numbers
Numbers greater than 9999 display in SI metric style,
where whole numbers that contain more than four digits are
broken into groups of three digits that are separated by
spaces. For example, the number sixteen thousand three
hundred eighty three is shown as 16 383. This avoids confusion between American and European punctuation conventions.
xvi
About This Book
However, a number that is internally manipulated by a computer is shown without punctuation or spaces. For example,
notice how the value 65 535 appears in the following
instruction without a space or a thousands separator within
the number:
Specify 65535 as a maximum value
Numbers with Different Bases
All numbers shown in this book are decimal values unless
the number base is binary or hexadecimal. There are two
ways to show a number with a different base:
•
•
An identifier can precede a binary or hexadecimal number. The following expressions use an identifier:
•
the value of binary 1010
•
the value of hex 4F
A type-format indicator can precede a binary or hexadecimal number that is enclosed in single quotation marks.
The following expressions use the binary and hexadecimal indicators:
•
B’1010’
•
X’4F’
Replaceable Input Values
In some cases, you can insert user-defined values into commands or you can specify local paths and filenames. These
variable values are shown in italic typeface.
For example, you might be asked to specify the name of your
server in this path:
A:\LOGIN\LOGIN servername
The italic typeface shows that you need to replace servername with your local server name.
xvii
When you are prompted for variable input that is represented by lower-case letters, follow these conventions:
When You See This
Variable Value
Substitute This Value
b
Any binary digit
h
Any hexadecimal digit
n
Any decimal digit
x
Any alphabetic value, such as:
x:\DOS
where you substitute the correct
drive letter for x
Multiple letters
A series of digits, such as:
FIRST 2 HEX BYTES: hhhh
where you substitute four hexadecimal digits for hhhh
When you are prompted for variable input with embedded
decimal points, replace the variable digits and let the decimal points remain to separate 32-bit dotted-decimal address
segments. For example, you might be prompted to supply a
32-bit, dotted-decimal address in this format:
nnn.nnn.nnn.nnn
where nnn is a decimal value from 0 through 255. Leading
zeros are not required.
Textual Callouts
This book uses two distinct symbols displayed in the textual
margins to call the reader’s attention to information that is
of particular interest.
xviii
About This Book
These callouts are presented and described below:
Note
Caution
This callout indicates that the information presented may be
of particular use when operating an ORCA gateway or
accompanying devices.
This callout indicates that the information presented may
prevent damage to an ORCA gateway or accompanying
device when operating the equipment or may prevent personal injury when installing, operating, or maintaining an
ORCA gateway or accompanying devices.
Getting Help
If after installing and configuring your Nuera equipment,
you cannot establish communications to or from the unit,
carefully review the information in this book and in the
other ORCA books prior to calling Technical Assistance Center (TAC).
Checklist
Ensure that you have checked the following possibilities:
1. Configuration of the console port. Check that the baud
rate of your terminal matches the preset settings of the
Nuera units being installed.
2. Reset the equipment. When cycling power, be sure to
leave the power off for a minimum of 30 seconds before
reapplying power to the unit.
3. Review the ORCA gateway commands. See the Configuration chapter of the ORCA Gateway Hardware Manual.
4. Check your software version. To ensure that all our customers have the latest enhancements and product fea-
xix
tures, Nuera ships every new or factory-upgraded unit
with the latest software version. Therefore, whenever
you are installing or reinstalling units into your system,
check each unit to verify that all units are equipped with
identical software versions.
Last Resort
If after carefully reviewing the information in this book and
in the other ORCA books, your problem persists, contact
either your product representative or a service representative at Nuera’s Technical Assistance Center. Prior to calling,
ensure that you have assembled all the pertinent data that
will assist in resolving your problem. These items include:
•
A detailed description of your problem
•
A complete listing of your system components and
configuration. Include your unit’s serial number and
the software version number it is running
•
A narrative of the actions you performed prior to the
problem
•
A list of all system messages posted by your unit.
Your Nuera service representative will advise you as to the
appropriate course of action.
Contacts
Address:
San Diego, CA 92121 USA
tac@nuera.com
Telephone:
1-858-625-9220, Extension 1391
1-800-966-8372, Extension 1391
xx
1
OVERVIEW
The ORCA RDT product family is designed to bridge the gap
between traditional, circuit-based Public Switched Telephone Networks (PSTNs) and emerging, packet-switched
telephony networks, such as cable or DSL. The ORCA RDT
uses advanced signal processing techniques to characterize
and compress signal sources into data packets, making it an
excellent solution for merging digital broadband access networks with the legacy telephone network in a seamless, reliable manner.
This book contains information on how to set up and maintain an ORCA gateway using the configuration software
provided with the product: either the Nuera Configurator or
NueraView.
Nuera Configurator
The Nuera Configurator is Nuera’s gateway configuration
tool. The Configurator allows configuration of speech processing to the DS0 level, as well as configuration of the hardware components of the gateway.
The graphical user interface reduces the time and effort
required to train technicians and operators to effectively
configure, install and troubleshoot ORCA networks. In the
event of a network catastrophe, the Configurator can down-
21
load a stored configuration and restore a network element.
In addition, the Configurator can also download operating
software to any ORCA gateway.
NueraView
NueraView integrates the Nuera Configurator with the HP
OpenView Network Node Manager, enabling quick deployment while effectively maintaining the network. Through
integration with the HP OpenView Network Node Manager,
NueraView allows operators to monitor all the ORCA gateways in a network. NueraView lets operators easily recognize fault conditions, and then isolate the problem to a
particular subsystem or network component. Operators can
utilize a single tool for monitoring network events and
alarms.
HP OpenView also allows data to be collected at user-selectable intervals to produce statistics that help manage
throughput and response time. Statistics can be presented
in table format or graphed as a line chart. In addition, operators can define threshold-crossing alerts to detect degrading network performance.
NueraView provides click-and-launch integration with HP
OpenView and the ability to receive traps from the gateway.
NueraView comes bundled with the Nuera Configurator.
RDT-8g Features
The RDT supports the new CM4 module. The CM4 is a
switched hub which supports simultaneous two-way traffic.
For more information on the card modules, see the ORCA
Gateway Hardware Manual.
22
Overview
The Nuera Configurator has been updated to support the
new hardware. The Configurator has also been improved to
support these new features:
•
enhanced voice activity detection, lost packet recovery, and comfort noise generation schemes;
•
fax and modem upspeed;
•
Diffserv;
•
packet periodization;
•
new alarm tree view;
•
and new provisioning and statistics tools.
Community Strings
SNMP community strings allow you to set low-level
access restriction for your gateway. With community
strings, names can be assigned to each RDT. This feature is set through the console port, so please refer to the
ORCA Gateway Hardware Manual for more information.
G.726 32K Compression
G.726 32K (ADPCM) compression is a common vocoder
that the RDT gateway now supports, along with G.711
(PCM).
Voice Activity Detection
Voice Activity Detection (VAD), also known as silence
suppression, minimizes the amount of IP bandwidth
needed to sustain a voice call by suppressing packet traffic when no signal is present.
Fax and Modem Upspeed
When fax or modem upspeed is enabled, the RDT gateway will force a DS0 voice channel into 64Kbps G.711
vocoder mode if a modem or fax signal is detected on that
channel.
23
Diffserv
Diffserv bits can be set in the Configurator to help minimize network latency.
Packet Periodization
Packet periodization determines the number of voice
packets that are consolidated into one IP packet. The
packet periodization can be set in the Nuera Configurator to 10, 20, or 30 milliseconds. The intervals are the
time lapse between sending out each packet. The higher
the number of milliseconds, the more network bandwidth is minimized.
New Alarm Tree View
The Nuera Configurator has been revised to provide a
new Alarm tree view. New alarm categories are added as
well as right-click menu features.
New Provisioning Tools
New provisioning tools in the Configurator help make
setting up subscribers and interface groups as simple as
possible, including the ability to import a file containing
provisioning information.
24
2
NUERA CONFIGURATOR
INSTALLATION
This chapter provides instructions for installing Nuera’s
ORCA Configurator. The Nuera Configurator is a configuration tool included with all ORCA RDT gateways. It differs
from NueraView in that it cannot link with HP OpenView to
get detailed alarm statistics.
If you are installing ORCA RDT software and require HP
OpenView functionality, see "NueraView Installation and
Configuration" on page 89.
Nuera recommends the following minimum system requirements to run the Nuera Configurator: a PC with an Intel
Pentium processor of 200 MHz or higher, with 128 MB of
RAM, a CD-ROM drive, and 80 MB of free hard drive space.
Nuera also recommends a 17” monitor with at least 800 x
600 resolution, a SVGA video card, a 3.5” floppy disk drive,
and an ethernet interface. The Nuera Configurator runs on
Microsoft Windows NT (with Service Pack 6), 2000 (with
Service Pack 2), and XP operating systems, and requires
Internet Explorer version 6.0 or higher.
Note
When installing the ORCA RDT Configurator, you do not
need to have Hewlett Packard OpenView NNM installed on
the ORCA Configurator workstation.
Installing the Nuera Configurator
Use the procedure in this section to install the ORCA Configurator software on the Configurator workstation.
Note
Be sure to read the information in the Nuera Configurator
Readme file and check the Application Notes for recent
updates that are not included in the RDT documentation.
Installation Procedure
1. Place the ORCA RDT CD-ROM in the CD-ROM drive of
the PC workstation.
2. If you have Autorun enabled, the program will start
automatically. Otherwise, on the PC workstation, click
Start, then Run, then Browse. Navigate to the CD-ROM
drive and select Launch.exe.
3. Click Open.
4. From the Run dialog, click OK. The opening Nuera
Installation Launcher screen, as shown in Figure 1,
appears. Click on Installation.
Figure 1. Initial Installer Screen
26
Nuera Configurator Installation
5. Next, the License Agreement screen will appear as shown
in Figure 2. Read through the license statement, and
click Accept if you agree to the terms. Click the Close
button to exit the Installer, or the Back button to return
to the Main screen.
Figure 2. License Agreement Screen
6. The next screen is the Installation Menu shown in Figure 3 on page 28. Choose which software components you
wish to install. Configurator 7.0 is the software that will
allow you to configure your RDT gateway. The Embedded Software 7.0 software is not software to run on your
PC, but programming code to download to a RDT. For
more information about downloading code images to
your RDT card modules, see "Downloading Code" on
page 74. Choose the software to be installed by checking
or unchecking the boxes next to the name of the software. Use the Browse button and entry field in Step Two
to install the software on the drive of your choice.
27
Figure 3. Installation Menu Screen
7. Once you have set the software to install correctly, click
the Begin Install button to begin the installation. Or,
click the Close button to exit the installation.
8. The installation will only take a few moments. A screen
declaring the installation to be complete will appear.
Click OK to continue.
Installation with a Firewall
If there is a firewall located between the PC running the
Nuera Configurator and the RDT, the following UDP ports
must be opened on the firewall to allow communication
between them:
28
•
UDP 69, 161, 1024–65535 on the primary CM's IP
address for SNMP traffic.
•
UDP 162 on the primary CM's IP address for SNMP
traps.
•
UDP 69 and 1500 on the primary CM's IP address (to
download code via TFTP).
Nuera Configurator Installation
Note
The secondary CM assumes the IP address of the primary
CM in the event of a switchover. Therefore, only setting up
the sole IP address is necessary.
Nuera recommends that you do not place firewalls between
premise equipment and the RDT. If a firewall is placed
between them, the following ports will need to be opened in
the firewall:
•
UDP 2427 and 2727 on the primary CM's IP address
(for MGCP/TGCP traffic).
•
UDP 7000-7361 for the UPM traffic.
29
30
3
CONFIGURING
A
GATEWAY
After the hardware has been assembled and the basic gateway settings have been entered into the console port, it is
time to fully configure your ORCA gateway. Gateways are
configured using the Nuera Configurator application. The
Configurator can be used as a standalone application, or
bundled into NueraView for use with HP OpenView.
Overview
This section illustrates the most commonly-used screens in
the Configurator, explaining each element of the screens
and the possible configuration options.
Main Screen
The first time the Nuera Configurator is opened, the Storage
File Error dialog appears. This dialog indicates a mismatch
between the unit’s configuration and the Nuera Configurator storage file representing that unit. This mismatch occurs
because the storage file does not yet exist. To resolve the
mismatch, select one of the following options:
Upload: Select this option to transfer the actual configuration as it exists in the RDT to the Nuera Configurator
31
storage file. This is the normal response to a mismatch
when a unit is first accessed.
Unit Only: Select this option to configure the unit’s configuration directly by sending commands to the unit.
This option does not update the Configurator storage
file. To resolve the mismatch after configuring a unit in
this mode, you must execute an Upload to copy the
newly configured unit’s configuration into the storage
file.
Storage Only: Select this option to configure the storage
file directly by sending commands to the storage file.
This option does not update the ORCA RDT’s configuration.
Abort: Select this option to quit the application.
The gateway can be configured either directly, in unit only
or normal mode, or by configuring a storage file then downloading that file to the gateway.
Figure 4. Nuera Configurator Main Screen
The main screen has a number of key elements:
32
•
the menu bar,
•
the mode selection list,
•
the major operation buttons,
Configuring a Gateway
•
the status windows,
•
and the card view.
Menu Bar
The main menu bar contains a number of simple functions
that are common with most Windows applications.
File Menu
The file menu’s Save File As option enables you to save a
copy of the current configuration as a storage file. The
name of the storage file must be in the form of an IP
address. The Exit option ends the Configurator session.
View Menu
The Refresh Alarms and Views option updates the current alarms and card status.
The Properties option enables you to set how the cards
display on the screen.
Tools Menu
The Upload (From Unit) option enables you to copy the
ORCA RDT’s configuration to the local storage file.
The Download (To Unit) option enables you to copy the
local storage file configuration to the ORCA RDT. This is
intended for pre-configuring a unit or for restoring configuration to a gateway in a catastrophic situation. DS1s
should be removed from service at the switch before performing a configuration download.
The Download Code (TFTP) option launches the TFTP
utility that enables you to load code updates to the
ORCA RDT.
The Condense Storage File option writes an optimized
version of the current (in-memory) configuration to the
storage file.
33
Help Menu
The Help Topics option provides a pull-down, online
ORCA RDT help facility. (Contextual help is provided for
each ORCA screen.)
The About option provides information regarding the
release of the ORCA RDT NMS currently running.
Mode Selection List
Use this pull-down list to change the operational mode.
Normal
In this mode, the Configurator stores all of an ORCA
gateway's configuration settings in the storage file.
When you query the target ORCA RDT, the Configurator
obtains the chassis data from the configuration file in its
own storage, thereby eliminating the network delay that
would be encountered when communicating between the
computer and the chassis. In this mode, commands to a
gateway are sent to the storage file and the gateway
simultaneously.
Unit Only
In this mode, the Configurator communicates directly
with the ORCA gateway through the IP connection in
order to obtain status information and issue commands.
The storage file is not accessed in this mode. This communication mode could be slower than the Normal mode
because all data must pass through the network.
Storage Only
In this mode, the Configurator stores and retrieves data
on the storage file only, using the configuration settings
in that file as a virtual gateway. Therefore, any queries
regarding a gateway do not come across the network
from the target gateway.
34
Major Operation Buttons
These buttons open the Configurator’s major operation
screens.
Alarms & Traps
Opens the Alarms window, which displays specified system alarms. If alarms exist, the color of this button
changes to the color specified in the Properties window.
This button is deactivated when the system is in Storage
Only mode.
System
Displays the System window, where you can assign system settings.
Media
Displays the Media Configuration window for editing.
GR-303
Displays the GR-303 window, where you can add, edit, or
delete interface groups.
Subscribers
Displays the Subscribers window, where you can add,
edit, or delete subscribers. It is also possible to export or
import a subscriber list.
GR-303 Status
Displays the GR-303 Status window, which displays the
current status of the TMC and EOC management channels.
Status Window
The top right section of the screen displays a message window, and the ORCA RDT activity animation.
35
The animation is active when the Configurator is busy communicating with the gateway or performing a task. The Message window provides information as to what activity is
taking place. When the Configurator is idle, this window
displays the message: Ready.
The bottom of the screen has another message window that
shows the trap receiver status, and the throttle status. For
more information, see "System-wide Settings" on page 86.
This window is deactivated when the system is in Storage
Only mode.
Card View
The default card view in the main screen automatically
shows current card status, as well as allowing you to configure the cards.
Card status is shown by the color of the card. If the card is
installed and operating normally, it is shown as grey. All
other warning states are shown with user-configurable
bands of color. To see or change the color settings, go to the
View menu and select Properties.
The card view is also used for adding cards to the system.
Cards plugged into the chassis must be configured using the
Configurator before they become usable by the gateway.
Double-clicking on a card will bring up a configuration
screen. Once the card is added, clicking on any of the supported ports will bring up a configuration screen for the
port.
System Screen
The system screen allows you to set a number of configurables and check the system status screens. The system
screen gives information about the system itself, including
serial numbers, IP addresses, and programmed status
states versus actual status states. To reach this screen, click
on the System button on the Main screen.
36
Figure 5. Nuera Configurator System Configuration Screen
The system screen has tabs along the top to access the different configuration and status screens contained in the system screen.
Configuration Tab
Internal Date/Time Section
Use this section to set the gateway to the correct time,
dependant on time zone.
Cards
This section lists the specifications of the cards in each
slot in the gateway. The information includes the type of
card in the slot, the hardware and software version of
each card, and its configuration state are located in this
box. Click on a single slot then click on Card Detail to
examine the card’s configuration, verify the code it’s currently running, or to virtually eject the card.
Virtually ejecting a card will make the selected card display a blue light, thereby indicating to remote site personnel which card should be removed. In the case of a
37
UPM3 card, the card will drop all the active calls it is
currently processing.
Net Clock Reference
This display box lists the current net clock reference the
gateway is using. The Refresh button next to the display
box will refresh the Active Reference without leaving the
System screen.
Use the pull-down boxes to identify the network clock
references. The main clock reference should be set as A.
If clock reference A fails, B will then become the main
clock reference. If clock reference A is brought back
online, the gateway will not automatically switch back
over to clock reference A.
To update the settings after changing them, close the
System screen after pressing Apply, and then open it
again.
System Description
The System Description display box is a quick reference
tool to easily show the user which type of gateway the
Configurator is connected to and which version of code is
currently running on the gateway. The Edit control will
allow the user to copy that text and send it to Nuera’s
Technical Assistance Center.
Advanced Configuration
The Advanced Configuration button leads to a screen full
of advanced functions, including:
38
•
forcing a CM switchover,
•
updating the embedded code on installed cards,
•
activating the backup code on any of the installed
cards.
•
preparing a card for ejection.
This screen also lists which CM is currently active, and
the code version that all the cards are currently running
and which version they have as backup.
Manager Tab
Managers
Use this box to add, edit, or delete managers. Adding the
IP addresses of all the remote computers that might be
manipulating or viewing the gateway via the Nuera Configurator is recommended, but not required for functionality.
Agent Mode
Choose from universal or individual mode. Universal mode will allow any Configurator to connect to
the gateway, while individual mode will only allow
the listed managers to access the gateway.
DNS Tab
This tab allows you to enable or disable domain name
service (DNS). If you wish for the gateway to recognize
domain and host names, enter in your primary and secondary name servers by clicking the Add button, then enable
DNS.
Click the Flush DNS Cache button to clear all the saved
DNS lookups from memory.
IP Tab
IP Addresses
This box lists the card type, IP address, and MAC
address of each card by slot. Click on a card to select it,
and click on the Configure button to change a card’s IP
address.
39
TOS Diffserv
The Type Of Service (TOS)/Diffserv configuration boxes,
Media and Signaling, allow you to set the quality of service feature Diffserv to match with the Diffserv routing
tables in the network routers.
Network
This status box displays the subnet mask and gateway
IP information necessary to establish a network connection. These settings are not configured in the Configurator, but through the console port. For more information
on configuring the gateway through the console port, see
the ORCA Gateway Hardware Manual.
System Status Tab
Start
Click this button to start the status polling option. The
Configurator will poll for status periodically. Only the
status indicators that are checked will be shown.
Stop
Click this button to stop polling for status.
Refresh
Click Refresh to force an immediate status poll.
Status Boxes
These boxes list the current status of the gateway power
supplies and fan modules.
Basic Configuration
Use the configuration instructions below as a general model
of how to set up your gateway. Be aware that these steps are
40
a guideline; you must configure the gateway to work in your
unique network.
Adding Cards
The first step in configuring a gateway is to add the cards.
The cards that reside in the chassis cannot be used until you
configure them. Unconfigured cards will be marked with colored parallel lines. Check the Properties under the View
menu to see what color the “Unconfigured” cards will display.
Figure 6. Default View of Unconfigured Cards
Double-click on a card to configure it.
Adding the HUB2/HUB2X Cards
Double-click on a HUB2 or HUB2X card. You will have to
add both card pairs manually.
41
Figure 7. HUB2/HUB2X Configuration Screen
Choose the Type of HUB2 and HUB2X cards that are
installed in the system. Though there is only one choice, it
still must be selected manually.
Once you have selected the correct card types, click Apply,
then OK to dismiss the dialog.
Adding the CM/CMX Cards
Double-click on a CM or CMX card. You will have to add
both card pairs manually.
42
Figure 8. CM/CMX Configuration Screen
Choose the Type of CM card that is installed in the system.
Though there is only one choice, it still must be selected
manually. Then choose the correct type of CMX card.
Once you have selected the correct card types, press Apply,
Adding the UPM3/UPMX Cards
Double-click on a UPM3 or UPMX card. You will have to add
both card pairs manually.
43
Figure 9. UPM3/UPMX Configuration Screen
Choose the Type of UPM3 and UPMX cards that are
installed in the system. Though there is only one choice, it
still must be selected manually. Also, the correct Density
must be set for the UPM3. The correct setting is: four-dsx.
Once you have selected the correct card types, click Apply,
Adding the Interface Groups
To configure your interface groups, click on the GR-303 button on the Main screen. The GR-303 screen will open.
44
Figure 10. GR-303 Configuration Screen
Use this screen to add, edit, or delete interface groups. Click
the Add button to create a new interface group, with the
help of a software wizard to guide you through the process.
Click Edit to edit the selected interface group, and Delete to
delete the selected interface group. Remember to press
Apply to delete an interface group.
Adding New Subscribers
Click the Subscribers button on the Main screen to add new
subscribers to the system The system holds a maximum of
4000 subscribers, with up to 2048 subscribers allowed on
each interface group.
45
Figure 11. Subscribers Screen
Interface Group ID
This pull-down menu lists the ID numbers of the current
configured interface groups. Choose the interface group
you wish to add subscribers to or edit subscribers on.
Members Box
Select All
Selects all the configured subscribers to apply a single
operation to the entire list.
Delete
Click Delete to delete selected subscribers.
Unblock
Click this button to restore the selected subscribers to
service.
Block
Click this button to remove the selected subscribers from
service.
46
CRV
The Customer Reference Value (CRV) is the number the
switch will use to identify the individual customer. This
number must match on the RDT gateway and on the
switch.
Endpoint
The endpoint defines the customer’s end of the connection, the individual analog phone port on the MTA or
IAD. The format of an endpoint is: aaln/0@mydomain.com, where aaln/0 refers to the phone port. If
name service is not available on the network, then the
domain name can be substituted for an IP address (e.g.:
aaln/0@[192.168.0.1]).
Local Status
The Local Status lists the service state of each subscriber. This status state can be altered by the user by
selecting the subscriber and using the Block or Unblock
buttons to either restore the subscriber to service or
remove them from service.
State
The state field defines the far-end state of the endpoint.
The state is displaye as up, alarm, or blank. A state of
up indicates that the MTA is physically connected to the
network, and does not report an alarm. A state of alarm
indicates that the endpoint reports an alarm. The current alarm condition can be found in the Alarms screen.
A blank state means that the MTA has never been connected. The MTA is in a pre-provisioned state, whereby
the RDT will not report subscriber communication failure alarms until an MTA is connected. This field is not
available in Storage Only mode.
Total number of endpoints
This field displays the total number of endpoints for the
selected interface group.
47
Connected endpoints
This field displays the number of connected endpoints. A
connected endpoint is an endpoint whose MTA has been
connected on the remote end at least once since the RDT
was powered up. An additional field displays the number
of endpoints that reported an alarm. If an endpoint
shows a local status of blocked, it will report an alarm,
hence increasing the count of connected endpoints, even
if the MTA has never previously been connected. This
field is not available in Storage Only mode.
Bulk Operations Box
Import Subscribers
Use this button to choose a CSV file to import and automatically provision subscribers.
The Comma Separated Values (CSV) file must contain
one line per each subscriber, with a hard return at the
end of each line. The values entered must be the CRV
and the endpoint, separated by a comma:
•
1,aaln/0@mydomain.com
Export Subscribers
Use this button to create a CSV file from the current
subscriber settings.
Selection Only
Click this checkbox if you wish to create a CSV file containing only the selected subscribers.
Editing the Media Configuration
Click on the Media Configuration button on the Main screen
to open the Media Configuration window. If you have
already created and configured the interface groups, the
voice template has been configured based on the selections
48
made for the interface groups. You can now edit the template to make sure the settings match your network.
Figure 12. Voice Template Screen
Voice
Vocoder
Specify the desired voice compression rate: g71164000-ulaw or g726-32000.
Packetization Period
The packetization period is the amount of TDM signal
included in each IP voice packet, measured in milliseconds. Each vocoder has a base packetization period that
it supports. In addition, each vocoder supports several
multiples of its base packetization period.
Fax/Modem Upspeed
Mode
Choose from enable or disable. When fax or modem
upspeed is enabled, the RDT gateway will force a DS0
voice channel into 64Kbps G.711 vocoder mode if a
modem or fax signal is detected on that channel.
49
If the vocoder is set to g711-ulaw, then this field will be
grayed-out (unselectable).
Network
Call Processing Type
Mgcp-trunk is the default and only selection in RDT-8g
7.0.
Packet Protocol
Rtp is the default and only selection in RDT-8g 7.0.
Echo Cancel
Mode
Enable or disable echo cancellation.
NLP
Enable or disable non-linear processing. This feature
further reduces echo cancellation to imperceptible levels.
It is also referred to as a center clipper, or a residual
echo suppressor.
TD
Enable or disable the tone disable feature.
VAD
Mode
Choose from none, adaptive, or fixed to configure the
voice activity detector (VAD) feature. Select none to disable VAD, adaptive to dynamically select the VAD
threshold, or fixed to specify a fixed value for the VAD
threshold.
Threshold
This setting specifies a fixed threshold level in dBmO for
voice ports that are set to a VAD mode of fixed. Specify
an integer from 0 to 45.
50
Hangover Time
This setting specifies the overhang time in milliseconds
after which the speech has ended and VAD silence suppression begins. Specify an integer from 0 to 3825. This
field can be set only when VAD is set to fixed.
Signaling
RFC2833 ABCD Relay
The ABCD Relay is automatically set to enable.
ABCD Tx Translation
Set the sent (transmitted) ABCD bits in hex code.
ABCD Rx Translation
Set the received ABCD bits in hex code.
Configuring the DSXs
The DSXs must be set to online for the gateway to work.
There are also other settings related to the DSX that can be
configured.
To configure a DSX, go to the Main screen and double-click
on the graphic of the desired port connection in the back
card view. The configuration screen will open.
51
Figure 13. The DSX Configuration Screen
Configuration Tab
Alias
This field allows you to enter in a descriptive name for
the DS1 to help with quick identification. This name is
not recognized by an external controller.
Mode
This setting allows you to turn the circuit on or off
remotely, as well as perform troubleshooting and diagnostic tasks. Choose out-of-service, online, or
span-loop-to-subscriber.
•
span-loop-to-subscriber: DS1 subscriber loop
where the receive signal is transmitted back out the
interface. Loops back the entire frame including
framing bits in the subscriber direction.
Type
Choose the length of the span. Choose t1-long if the
cable is longer than 68 meters, or choose t1-short if the
cable is shorter than 68 meters.
52
Clock
Choose the clock type: h110 or span. If h110 (the default
setting) is selected, the gateway will get its clocking off
its own H.110 bus. Span will force the gateway to use an
external clocking source.
CAS
Enable or disable CAS signaling. The default setting
is disable. For the RDT gateway to work properly, CAS
must be enabled.
Line Code
Choose from b8zs or ami to match the configuration of
your network.
LBO
The LBO (Line Buildout) setting configures the DSUB
T1 port to control transmit signal attentuation.Choose
from: 0.0 dB, -7.5 dB, -15 dB, or -22.5 dB.
T1 Superframing
Select the T1 superframing option that is running on
your network: d4, or esf. D4, also known as super frame
(SF), is a data transmission format composed of 12
frames of 192 bits each. The 193rd bit is used for link
control and error checking. Esf, extended super frame,
is composed of 24 frames of 192 bits each. ESF provides
16 signalling states in the 193rd bit to ensure synchronization, supervisory control, and maintenance capabilities.
Add a Manager
Manager configuration allows the ORCA gateway to permit
select software managers (such as the Nuera Configurator,
or HP OpenView) to access the gateway. This functionality
also restricts managers, or limits certain manager access.
53
Figure 14. The Manager Config Tab on the System Screen
There are two manager agent modes: universal and
individual. Universal mode allows all managers access
to the gateway. Managers do not need to be added to the system to view and change the gateway’s configuration. Individual mode allows only those managers listed in the
Managers field to access the gateway configuration according to their defined privileges and restrictions. Managers
that are not listed will be unable to contact the gateway. The
Agent Mode setting is selected in the Agent Mode drop box.
54
4
TYPICAL NETWORK APPLICATION CONFIGURATION
This chapter presents two possible network applications for
the ORCA RDT 7.0 gateway. The gateway is designed for
providing a bridge between packet-switched telephony networks and existing public telephone networks. It acts as a
dual termination point, terminating the aforementioned
networks. This chapter also provides a basic understanding
of both networks' protocols, functional features of both protocols, and how the ORCA RDT conforms to both standards.
General Overview
The GR-303 and NCS standards are both open protocols
that allow for maximum flexibility and network scalability.
The GR-303 specification was defined by Telcordia to create
a standard for access telephony networks. GR-303 defines a
communication protocol between a Class 5 switch (IDT) and
a remote network device (RDT). The NCS protocol was created by PacketCable and it defines the signaling relationship between a cable network termination point
(PacketCable Call Agent) and a trunking gateway (Residential Trunking Media Gateway). By blending the two protocols together in the ORCA RDT, it is possible to provide a
cable telephony access network.
55
Functional Descriptions
GR-303
Integrated Digital Loop Carrier (IDLC) systems incorporate
leading edge technology to reduce operating and capital
equipment costs, and they deliver a full range of telecommunications services. Telcordia's GR-303 protocol defines a set
of next-generation IDLC standard criteria that create an
integrated access system. The GR-303 standard:
•
Supports multiple distribution technologies and
architectures, as well as a wide range of services
(both narrowband and broadband) on a single access
platform.
•
Specifies requirements on signaling, performance,
and provisioning to ensure connectivity and consistent operations across the digital network.
•
Is a standard of modern Operating System to Network Element (OS/NE) interfaces, providing a means
of remote circuit provisioning, remote testing of both
POTS and special services, and performance monitoring of DS1/ISDN.
•
Specifies a consistent set of alarms.
•
Defines a set of requirements for Integrated Access
Systems that includes: open interfaces for mix-andmatch of Local Digital Switches (LDSs) with Remote
Digital Terminals (RDTs), and RDTs and Element
Management Systems (EMSs).
The physical interface between a RDT and an IDT (which is
a logical part of the LDS) is based on DS1 using ESF format.
The number of DS1 lines is limited to a minimum of two and
a maximum of 16 per interface group. The lower limit allows
IDLC systems to meet the needs of small line size applications, while also providing the ability to back up critical
operations data-links. The RDT also supports analog POTS
services.
56
Typical Network Application Configuration
GR-303 specifies that the Operations Systems (OS) interface
to the RDT should use CMIS/ROSE/ASN.1 protocols over
the EOC channel. CMIS and ROSE are a means for the IDT
to manage resources in the RDT. The resources are modeled
as Managed Objects. ASN.1 is a notation for describing data
formats and BER (Binary Encoding Rule) specifies the rules
for encoding data over communication links. GR-303 defines
the OS interface using Managed Object Classes (MOC).
These classes are defined using a methodology framework
called Guidelines for the Definition of Management Objects
(GDMO) as stated in X.722. Instances of a class are called
Managed Object Instances (MOI). A class defines the
attributes, which are the actions that can be taken on the
MOC, and the notifications that the MOC can give to the
system. There are classes that cover all possible data that
can be accessed over the Embedded Operations Channel
(EOC).
The RDT uses the LDS as a gateway to the OS network.
Facilities connecting to the narrow-band digital switch (i.e.,
LDS) are assigned using the Time-Slot Management Channel (TMC), and managed with remote operations functions
supported over the EOC of the GR-303-based Integrated
Access System.
The TMC channel is used to exchange call-processing messages between the RDT and the LDS for call set up and call
release procedures. TMC includes a 16-state robbed-bit signaling for transmitting call-processing messages between
the RDT and the LDS. The call processing data link is based
on the LAPD protocol, which is the same protocol used on
ISDN D channels. The call processing messages are based
on the CCITT Q.931 message standard.
NCS
Network Call Signaling (NCS) is PacketCable's version of
Media Gateway Control Protocol (MGCP) that is approved
by the Internet Engineering Task Force (IETF). NCS is
almost identical to MGCP with a few minor exceptions. A
57
key difference is the endpoint naming convention. NCS protocol defines the signaling relationship between residential
and trunking gateways and their controlling call agent. NCS
is a master-slave protocol with the call agent as the master
and the media gateways under its control as slaves. The
media gateway devices (residential or trunking) do not contain call processing intelligence, so they use NCS to report
telephony events observed at their local telephony ports and
interfaces to an external call agent. The call processing logic
in the call agent is responsible for responding to queries
from the media gateways and commanding the media gateway devices to carry out call processing actions. The combination of media gateway and media gateway controller
defines a distributed IP telephony domain.
The ORCA RDT has an embedded lightweight call agent
application. This call agent application is responsible for
controlling the residential end-points (cable modems at customer premises) and the trunking endpoints (preset within
the ORCA RDT). Additionally, the call agent application
converts GR-303 signaling into NCS and vice versa.
Configuration
Two of the most common applications of the RDT gateway
are: in a cable access network, and in a DSL telephony network. The network diagram below shows the network topology for both systems.
58
PSTN
DSL
Modem
DSLAM
Router
Cable
Modem
RDT-8
CMTS
Local
Exchange
Figure 15. Cable Access Network Application
The RDT gateway configuration procedure for each network
application, cable or DSL, is the same. Use the Nuera Configurator to follow the procedure below for step-by-step
instructions to configure a gateway for one of the network
applications above. In order to complete this configuration
procedure correctly, make sure you have familiarized yourself with “Configuring a Gateway” on page 39.
1. Verify the gateway hardware is installed correctly and
that the console port configuration has been done. Refer
to the ORCA Gateway Hardware Manual for more information.
2. Add the HUB2, HUB2X, CM, CMX, UPM3 and UPMX
cards to the system. Refer to “Adding Cards” on page 41
for more information.
3. Add the interface groups. Click the GR-303 button on the
Main screen to open the Interface Groups window. Click
the Add button to add new interface groups. A configuration wizard will open to guide you through the process:
59
Figure 16. Interface Group Addition Wizard, Screen One
Step 1
Choose the Group ID. There are a maximum of four
interface groups possible to configure. Make sure the
Group ID matches the group ID on the switch side.
Use the Alias option to name the interface group if
you desire.
Choose the correct Switch Type that will connect
with the new interface group. Choose from: lucent5ess or nortel-dms100.
Click Next when the fields are configured correctly.
60
Figure 17. Interface Group Addition Wizard, Screen Two
Step 2
Use this screen to configure the GR-303 links for the
interface group. The list on this screen presents all
the available links. Select the link to make changes.
Click the checkbox in the Add column to add the link
to the interface group.
Select the type of traffic that this link will carry in
the Type column: primary, secondary, or voice.
Primary means the selected link will carry the
active TMC/EOC signaling channels. Secondary
means the link will carry the backup signaling channels. Voice means the link will carry voice traffic.
Both a primary and secondary link must be configuredl.
Note
The primary and secondary links should be located on different UPM3 cards for redundancy.
Choose the Link ID under the ID column.
61
Click Next when the configuration is complete.
Figure 18. Interface Group Addition Wizard, Screen Three
Step 3
The wizard will create the new interface group, and
configure the links, the new interface group, and
voice templates automatically.
4. Add the subscribers. For more information on the Subscribers screen, see "Adding New Subscribers" on page
45.
There are two ways to add subscribers to the system:
manually, or by preparing a CSV document that can be
imported and applied to this screen.
Adding Subscribers Manually
Before adding any new subscribers, make sure you
have selected the correct interface group of which the
subscribers will be members. The Interface Group ID
pull-down menu shows the current interface group.
Once this is verified, continue to the main element of
the Subscribers screen, the list control. This spreadsheet-like list of subscribers can be edited by clicking
on an entry. A subscriber can be created by clicking
on a blank line.
62
When you add a subscriber by clicking on a blank
line in the list control, you can click first on the CRV
column if you desire to have non-sequential CRV
numbers. Enter the CRV, then press Enter to edit the
Endpoint column. Or, double-click on a blank line in
the Endpoint column to let the Configurator fill in
the CRV numbers sequentially. Once the endpoint is
entered in, the Apply button must be clicked to configure the new subscriber.
Adding Subscribers Using a CSV File
Click on the Import Subscribers button to configure
bulk subscribers. The Import Subscribers window
will open. Click Browse to select the CSV file, and a
standard Open File dialog box will appear. Select the
correct file. The Configurator will then import the
subscriber list. The import log will show in the window. Click the Close button when the importing process is finished.
5. Edit the voice template. The voice template was automatically assigned at the interface group creation, and
this template determines the media configuration for the
entire gateway. There are certain features like echo cancellation or VAD that you might want to change. For
more information on the voice template settings, see
"Editing the Media Configuration" on page 48.
6. Configure the DSXs. The DSXs must be turned online in
the Configurator for the gateway to start functioning.
Double-click on the graphic representation of the DSX
you wish to configure in the card view on the Main
screen. You must set the Mode to online, and CAS to
enable. Also, in order for your GR-303 connection to
work correctly, the Line Code and T1 Super settings
must be left as the default (b8zs and esf, respectively).
Nuera recommends that the Clock setting be set to h110.
For more information on the DSX configuration settings,
see "Configuring the DSXs" on page 51.
7. Add the Managers. For more information about adding
managers, see "Add a Manager" on page 53.
8. Edit the DS0s. If desired, edit the Input Level Gain and
63
Output Level Gain on the individual DS0s. To edit a
DS0, go to the DSX Configuration screen and double
click on a DS0 in the DS0 Table. The following screen
should appear:
Figure 19. DS0 Configuration Screen
9. Set the Network Reference Clock. Go to the System
screen, and set the primary (A) and secondary (B) network reference clocks.
64
5
MANAGING
AN
ORCA GATE-
WAY
This chapter explains how to check status and perform various maintenance tasks using the Nuera Configurator.
Note
It is important to remember to refresh all status and statistical screens to receive current information. The screens will
not automatically update when there is new information.
Checking the System Status
Card Status
To determine the current status of all the front and back
cards in the RDT, use the main screen of Nuera Configurator. The colors and cross-hatching of the cards indicate their
state. The default settings are:
65
•
Normal: gray with no cross-hatching
•
Unconfigured: gray with gray cross-hatching
•
Missing: gray with black cross-hatching
•
Unknown: blue with blue cross-hatching
•
Warning: cyan with cyan cross-hatching
•
Minor Alarm: yellow with yellow cross-hatching
•
Major Alarm: orange with orange cross-hatching
•
Critical Alarm: red with red cross-hatching
The cards that are not gray are reporting alarms. To view
the alarm log, click on the Alarms and Traps button on the
same screen. For more information about alarms and resolving them, see "Viewing Alarms" on page 79.
66
Managing an ORCA Gateway
DS1 Status
Status of the DS1s can be determined by double-clicking on
the desired DS1 port in the card view on the Main screen.
Then click on the DS1 Status tab.
Figure 20. DS1 Status Tab
Detailed statistics can be obtained by checking the boxes
next to the desired statistics, and clicking the Refresh button. The Clear button can be used to reset the checked statistics to 0 (where appropriate).
Present Performance statistics are reset back to 0 every 15
minutes. The statistics reflect the data gathered since the
last reset.
Threshold alarms monitor the 15 minute and 24 hour statistic blocks and generate alarms when the error thresholds
are exceeded.
This screen automatically refreshes every 60 seconds by
default. To stop the automatic refresh feature, click the Stop
button. To restart it, click Start.
67
DS0 Status
Status of all the DS0s may be determined by double-clicking
on the DS11 port in the backplane view then clicking on the
DS0 Status tab.
Figure 21. DS0 Status Tab
The table at the top of the screen lists all the DS0s, how
each is configured, and the actual state of that DS0 (which
may be different from the configured state).
Detailed statistics for a particular DS0 can be obtained by
highlighting the desired DS0 in the table, checking the
boxes next to the desired statistics, and clicking the Refresh
button. The Clear button can be used to reset the checked
statistics to 0 (where appropriate).
This screen automatically refreshes every 60 seconds by
default. To stop the automatic refresh feature, click the Stop
button. To restart it, click Start.
68
Power and Fan Modules’ Status
The status of the power supplies and fans can be viewed by
double-clicking on the System button, then selecting the System Status tab. The presence or absence, and condition of
each power supply is indicated, as is the period for each fan.
Figure 22. System Status Tab
69
Interface Group Status
Checking the System Performance
Use the information found in the following screens to determine the statistical performance of the ORCA gateway. The
screens are also useful to help troubleshoot, as they report
certain line errors.
Ethernet Performance
To view the current performance of the ethernet network,
double-click on a card in the backplane, and click its Status
tab. This will show statistics for the individual card. To get
overall system ethernet statistics, click on a CM card.
Figure 23. The Ethernet Performance Screen
70
Checking the System Settings
This section contains a few helpful references to quickly
check current system settings that are not immediately
apparent.
Determining Clock Reference
The current active clock reference can be determined from
the Net Clock Reference box. Click the System button from
the main screen, then click the Configuration tab (which is
the default). The Active Reference field is displayed in the
lower left. Use the Refresh button next to the field to get the
most up-to-date information
Figure 24. System Screen
Note
The term “local oscillator” is a synonym for “internal clock.”
71
Version Information
Hardware Version
Click the System button from the main screen, then click the
Configuration tab (see Figure 24). The Assembly Number
and BOM Revision columns together give the hardware revision for each card. The Serial Number column gives the
serial number for each card. Click on an individual card and
then click on Card Detail to see more information about the
card, such as the current embedded code the card is running, or the type of daughter cards on the card.
Figure 25. Card Detail Screen
Software Version
Click the System button from the main screen, then click the
Configuration tab (see Figure 24). Click on the Advanced
Configuration button.
Choose cm in the Code Images on CM section to view the
software version installed on the CM cards. The active and
backup code versions will be displayed in the Slot Selection
section.
Choose upm3 in the Code Images on CM section to view the
software version installed on the upm3 cards. The active
72
and backup code versions will be displayed in the Slot Selection section.
Figure 26. Advanced Configuration Screen
Software Upgrade Procedure
Exact upgrade procedures for each version of the software
are available in the Release Notes included on the CD-ROM
with the software. Please check the Release Notes to see if
there are any special procedures that need to be followed to
upgrade. Otherwise, follow the procedure below to update
the version of software on the card modules.
To update the Nuera Configurator, follow the installation
procedure in “Nuera Configurator Installation” on page 25.
To update NueraView, you will also follow the installation
procedure in “NueraView Installation” on page 29.
Always check the Release Notes thoroughly before upgrading.
73
Downloading Code
The following procedure explains how to download code to
an RDT and activate it on each individual CM and upm3
card using NueraView.
1. Select Download Code (TFTP) from the Tools menu. The
dialog shown in Figure 27 on page 74 appears.
Figure 27. Nuera TFTP Dialog
2. The CM IP address appears for the unit you are currently controlling. If you want to specify a different CM,
type its IP address in the CM IP field.
3. Specify a delay (in seconds) for the retry interval. One
hundred twenty seconds is the default interval sufficient
to enable code to be automatically mirrored to the redundant CM.
4. Click Browse to locate and select the version of code you
want to download.
5. Depending on the card you are configuring and its usage,
click CM Module and/or upm3 Module.
6. Click Send to begin the download. The progress of the
download is shown in the status bar at the bottom of the
dialog.
7. Now, you need to activate the new code and propagate
the code from the CM modules to the upm3 modules.
From the TFTP dialog, click on the Advanced Configuration button (see Figure 28 below). Code Images on CM
should list the current code versions for the CMs and
upm3s.
74
Figure 28. Advanced Unit Configuration Screen
8. To upgrade the CM code, look under Code Images on CM
and highlight the row with type cm and the version of
your choice. The existing active and backup CM code versions will appear in the Slot Selection portion of the window.
•
You will need to activate the backup code on the
standby CM. First, highlight the standby CM and
press the Add button. To determine which CM is currently the standby CM, check the status display at
the top of the window. Next, press the Activate
Backup button at the bottom of the screen.
•
Once the Activate Backup process is completed, use
the CM Switch button at the top of the screen to
switch the standby CM to active status.
•
Wait until the new standby CM reports standby in
the CM Status window, then repeat the procedure
with the new standby CM to finish updating the code
on both CMs.
9. To upgrade the upm3 code, look under Code Images on
CM and highlight the row with type upm3 and the version of your choice. The existing active and backup upm3
code versions will appear in the Slot Selection portion of
the window.
•
Highlight the individual upm3s to be updated and
click the Add button to enter it in the box to the
right. All upm3s can be entered without highlighting
by clicking the Add All button.
•
Click the Update Code button. The top right-hand
75
corner of the dialog box will detail the progress of the
update. It will show Ready once the process is complete.
•
Wait for a few minutes for the process to complete.
The Slot Selection will list the new code as the
backup version on all selected upm3s upon completion.
•
Highlight the individual upm3s that need the new
code as its active code version and click the Add button to enter it in the box to the right. All upm3s can
be entered by clicking the Add All button. Whatever
traffic the upm3 is processing will be interrupted by this Activate Backup process.
•
Click the Activate Backup button. The top right-hand
corner of the dialog box will detail the progress of the
update. It will show Ready once the process is complete.
10. Wait for a few minutes for the process to complete. The
Slot Selection will list the new code as the active version
on all upgraded cards upon completion.
Maintenance Procedures
Resetting a Card
All front cards, save for the active CM, can be reset
remotely. To reset a card on-site, remove the card from the
chassis then re-insert it. For more information on removing
and installing cards, see the ORCA Gateway Hardware
Manual. The following procedure will reset the upm3 and
HUB2 cards.
1. Click on the System button on the main screen of the
Nuera Configurator.
2. Select the card to be reset.
3. Click on the Card Detail button.
4. Click the Reset button.
76
Forcing a CM Switchover
This procedure will force the ORCA gateway to switch from
the current active CM to the current standby CM. Forcing a
switchover is often required when updating code images on
the cards.
1. Click on the System button on the main screen of the
Nuera Configurator.
2. Click on the Advanced Configuration button on the System tab.
3. Click the CM Switch button.
Resetting an ORCA RDT Remotely
Please read through this entire procedure before beginning
it.
Note
Before starting this procedure, insure that the SNMP timeout is set to 5 seconds (default setting).
1. Determine the state of the CM cards by clicking on the
System button in the backplane view. Double click on the
active CM. In the third column of the dialog box is a field
called CM State. This will normally indicate active or
standby. Repeat for the standby CM.
2. If neither of the CMs are listed as standby, skip down to
step 4 (the “Reset the Active CM” step). Otherwise, reset
the standby CM. To do that, click on the System button
from the backplane view. Double click on the standby
slot. Press the Reset Card button. The upper right corner
of the dialog will read "Polling card for completion". The
following bulleted steps below and the next two
steps must be completed in the next 60-90 seconds
while the standby CM is resetting:
•
click the Cancel button under this message
•
Cancel out of the dialog
77
•
Cancel out of the System sheet.
3. Refresh the Main screen card view. The CM that was
just reset should change on the Configurator display to
diagonal lines, indicating it is missing.
4. Reset the active CM by clicking on the System button
from the backplane view. Double click on the active slot.
Press the Reset Card button. NueraView will temporarily lose communication with the RDT. Wait until the
dialog is re-enabled. This will take about 2 minutes.
Cancel out of the dialog. Cancel out of the System sheet.
Refresh the system state by choosing Refresh Alarms and
Views from the View menu. The CM that was just reset may
be the only card in service. While the other cards are resetting, they will be displayed with diagonal lines. If traps are
enabled, the UPM3s will change from missing to in-service
automatically. If not, keep refreshing the alarms and views
until all the UPM3s are back in service.
78
6
VIEWING ALARMS
This chapter contains information about viewing events in
the Nuera Configurator using the alarm sheet.
Overview
The Alarm sheet shown in Figure 29 displays incoming
alarms in the Alarm Tree control independently of the current operation. This enables you to view/modify settings on
other configurator dialogs while still viewing alarm information. When the Alarm sheet is closed or minimized, alarms
are still processed.
Figure 29. Alarm Sheet
The Alarm sheet is organized in three main sections:
•
Alarm Tree
•
Alarm List
•
Alarm Operations
Alarm Tree
The Alarm Tree is located in the left pane of the Alarm
sheet. It is organized as a hierarchical structure consisting
of a root-level node (labeled Alarm) under which is listed a
set of alarm group nodes.
Each incoming alarm is actively sorted into its associated
node according to its group type. The Alarm Tree provides a
cumulative number of the alarms that were processed since
the last refresh or initialization. The alarm count is indicated by the number displayed in parentheses next to each
logical alarm group type.
80
Viewing Alarms
Each node is color-coded based on the severity of the alarm,
and the group node is color-coded according to the highest
severity level of its child node.
A newly-arrived alarm dynamically updates its group type
in the Alarm Tree. If the alarm does not already exist in the
group, the count is incremented.
If duplicate alarms are received, only the most recent alarm
is listed, based on its time stamp.
If the received alarm type is Clear:
•
The corresponding Set alarm, if any, is deleted from
the Alarm Tree. The new Clear alarm is added to the
Alarm Tree and the count remains unchanged.
•
If the corresponding Set alarm is not found in the
Alarm Tree, the alarm count is incremented.
Alarm Groups
The Alarm Tree is organized into the following alarm categories:
•
System Alarms – includes gateway hardware and various driver-related alarms.
•
Digital Alarms – includes all DSP-related alarms.
•
Links Alarms – includes T1-related alarms.
•
Protocol Alarms – includes MGCP-related alarms.
•
Logical Alarms – includes general alarms.
•
GR-303 Alarms – includes the interface group and management channel alarms.
•
Subscribers Alarms – includes all RDT subscriber
alarms.
81
Pop-up Menu
The Alarm Tree pop-up menu activates when you right-click
on a node. This enables you to:
Acknowledge All Alarms
When invoked at the root level, all Set and Clear alarms
in all group nodes are acknowledged. When invoked at
the group level, all Set and Clear alarms in the selected
group are acknowledged.
Remove All Clear Alarms
When invoked at the root level, all Clear alarms from all
group nodes are removed. When invoked at the group
level, all Clear alarms in the selected group are removed.
Acknowledge Alarm
Acknowledges alarms at the alarm node level.
Remove Clear Alarm
Removes the Clear alarm at the alarm node level.
For a selected group node, right-clicking enables the
Acknowledge All and Remove Clears options. For a selected
alarm node (child level) whose type is Set, the Remove
Clears option is grayed out. For a selected alarm whose type
is Clear, the Acknowledge option is grayed out.
Alarm List
The Alarm List is located in the right pane of the Alarm
sheet. Clicking on a group node in the Alarm Tree displays
all alarms under the selected group in the Alarm List.
82
Viewing Alarms
The Alarm List supports the following features:
•
Multiple selection of alarms
•
Pop-up menu to acknowledge or remove alarms
•
Color-coded severity column based on the severity of
the alarm
•
Sorting based on column selection.
The Alarm List is refreshed if the newly-arrived alarm is in
the current set of alarms being viewed. If the new alarm
does not belong to the current set, the Alarm List is not
refreshed.
Pop-up Menu
The Alarm List pop-up menu activates when you right-click
on an individual alarm or a selected range of alarms listed
in the Alarm List. This enables you to:
Acknowledge
Enables you to delete one or more selected alarms from
the Alarm List and the Alarm Tree.
Remove Clears
Enables you to remove all Clear alarms in the pool of
selected alarms.
For a selected alarm whose type is Clear, the Acknowledge
option is grayed out.
83
Alarm Operations
Maximize button
The Maximize button toggles between a full-screen or
smaller window view of the Alarm sheet.
Minimize button
The Minimize button toggles between a dialog view, or
minimizes the Alarm sheet while keeping the process
alive.
OK
The OK button dismisses the dialog although alarms are
still processed.
Refresh
The Refresh button forces the refresh of the Alarm Tree
control thereby clearing the Alarm List control. Clicking
Refresh clears the history of alarms, fetches and displays
all the alarms from the device.
Go to Latest
Clicking this button moves focus to the latest (most
recent) alarm. If the group corresponding to the latest
alarm is not expanded, the group is populated and the
node is expanded automatically. The latest alarm will be
highlighted in the list control.
This button is grayed out if there are no alarms.
Status Bar Display
The status bar is located at the bottom of the Alarm sheet. It
displays the following status indications:
84
Viewing Alarms
Time Stamp
The time at which the last alarm was received is displayed in the lower left section of the status bar.
Throttling Status
The Throttling status is indicated in the lower right section of the status bar. A color-coded icon indicates the
throttling status as follows:
•
Green – indicates the Idle state in which no alarms
are being received.
•
Orange – indicates the Busy state in which alarms
are being processed.
•
Red – indicates the Throttled state in which no
alarms are being processed.
Severity Levels
Alarms can be one of four severity levels:
•
Critical
•
Major
•
Minor
•
Normal
Critical
A critical alarm occurs when any circuit module fault or
failure is detected. This includes environmental conditions such as high temperature or low air flow.
Major
A major alarm is declared as a result of any carrier failure alarms (red, yellow, and blue) or as a result of
selected facility or WAN performance counters.
85
Minor
A minor alarm is a non-service affecting alarm that is
also triggered as a result of selected facility or WAN performance counters.
Normal
Normal alarms either clear previously-active (Set)
alarms or provide informational messages.
System-wide Settings
History Size
You can optionally specify the number of alarms to be stored
in the cumulative history of alarms. History size is configured from the View|Properties|Default Settings tab. The
history size ranges from 5 to 1000 alarms.
If the number of alarms exceeds the history size, the oldest
alarms are deleted. For example, if one alarm arrives and
the history is full, it will replace the oldest alarm that was
received.
Note
After adjusting the History Size, be sure to refresh the screen
by clicking View|Refresh.
Alarm Throttling
If too many alarms are received in a given amount of time,
Throttling Mode is invoked. In this case, alarms are no
longer being received. When this occurs, throttling status is
displayed as a red light in the status bar of both the Alarm
86
Viewing Alarms
sheet and the Configurator Main screen. Additionally, the
lower-left pane indicates that the Trap Receiver is throttled
in the Configurator’s status bar as well as in the Alarm
sheet’s status bar.
When the rate of incoming alarms drops below the configured threshold, the GUI is once again updated and alarms
are processed accordingly. In this event, throttling status is
displayed as a green light in the status bar.
Throttling Threshold
You can set the upper limit of incoming alarms per second
before throttling is invoked. The Throttling Threshold is
configured from the View|Properties|Default Settings tab.
The Throttling Threshold ranges from 1 to 25 alarms per
second.
Note
This rate depends on the processing overhead of the system.
For a heavily-loaded system, it may be necessary to increase
the threshold value if the Configurator throttles too early.
How to Remedy an Alarm State
If necessary, remedies to alarms can be found in the
Orcatrap.mib file, which is installed on the PC workstation along with the Nuera Configurator. The file is located in
the MIB folder under the Nuera folder in the Program
Files directory of Windows. The file is a text file that can
be opened with Notepad.
This file contains a list of the alarms, organized by alarm
group. The full text of the alarm is listed, along with the
severity of the alarm (low, medium, or high), a comprehensive description of what the alarm text means, and possible
87
remedies for the situation. To find the listing quickly, search
on the last four digits of the trap ID number.
Using HP OpenView to View
Alarms
For more information on using HP OpenView, please refer
to the Managing Your Network document, found on the
Hewlett-Packard website in PDF format. It is recommended
to read all chapters pertaining to fault isolation before using
OpenView to isolate problems.
88
Appendix A
NUERAVIEW INSTALLATION
AND CONFIGURATION
This chapter provides instructions for installing NueraView
software. NueraView enables you to set up an ORCA RDT
application with the components required to provide network management functions through Hewlett Packard’s
OpenView.
Nuera recommends the following minimum system requirements to run the NueraView Network Management System:
A PC with an Intel Pentium processor of 200 MHz or higher,
with 128 MB of RAM, a CD-ROM drive, and 80 MB of free
hard drive space. Nuera also recommends a 17” monitor
with 800 x 600 resolution, a SVGA video card, a 3.5” floppy
disk drive, an ethernet interface, and the HP OpenView
Network Node Manager.
Installing HP OpenView
You will need to install HP OpenView before installing
NueraView. Follow the steps below carefully to correctly
install both programs. Make sure you install both programs
before trying to configure or use either one.
89
Note
This procedure is for installing HP OpenView 6 only.
1. To begin, you will need to verify that either Windows NT
4.0 or Windows 2000 and these associated programs are
already installed on your computer:
For Windows NT 4.0:
•
Internet Explorer 5.0 or higher.
•
Internet Information Service (IIS) from the NT
Option Pack CD. Once installed, you will have to
manually Add Peer Web Server by opening the Control Panel and clicking on Network, then Services.
•
Service Pack 6.0a or higher (must be installed following IIS).
For Windows 2000:
•
Internet Explorer 5.0 or higher.
•
IIS from the Windows 2000 CD. This is done by opening the Control Panel, selecting Add/Remove Programs, and then selecting Add/Remove Windows
Components.
•
SNMP Services from the Windows 2000 CD. This is
done by opening the Control Panel, selecting Add/
Remove Windows Components, and then selecting
Management and Monitoring Tools.
•
Service Pack 2 for Windows 2000.
2. Next, you will need to:
90
•
Uninstall any previous versions of NueraView and
HP OpenView.
•
Assign your computer a static IP address if it does
not already have one. Consult your network administrator if you need a static IP. Note down the IP
address and the subnet mask of your computer and
the ORCA RDT.
•
Verify that your SNMP services are enabled. To do
this, open the Control Panel, and click on Network,
then Services.
•
Verify that IP and UDP connectivity is running
smoothly between your PC and the ORCA RDT. It is
important that there are no bottlenecks between the
NueraView Installation and Configuration
computer and the RDT. Run a continuous ping or
other network test to determine that there is low
latency in the connection.
3. Install HP OpenView from the CD. Dismiss all the popup windows. Make sure to choose Custom Installation.
This allows you to bypass the auto-discovery feature,
which can take hours (depending on the size of your network). Leave all the installation selections as the default
except for auto-discover, which you must uncheck.
For more information about installing OpenView, see
Hewlett Packard’s OpenView manuals.
Installing NueraView
1. Place the NueraView for ORCA CD-ROM (labelled
NueraView SNMP Network Manager) in the CD-ROM
drive of the NueraView PC workstation.
2. If you have Autorun enabled, the program will start
automatically. Otherwise, on the PC workstation, click
Start, then Run, then Browse. Navigate to the CD-ROM
drive and select Launch.exe.
3. Click Open.
Follow the directions that appear in each dialogue to complete the installation.
Installation with a Firewall
If there is a firewall located between the PC running NueraView and the RDT, the following UDP ports must be opened
on the firewall to allow communication between them:
•
UDP 69, 161, 1024–65535 on the primary CM's IP
address for SNMP traffic.
•
UDP 162 on the primary CM's IP address for SNMP
traps.
•
UDP 69 and 1500 on the primary CM's IP address (to
download code via TFTP).
91
Note
The secondary CM assumes the IP address of the primary
CM in the event of a switchover. Therefore, only setting up
the sole IP address is necessary.
Nuera recommends that you do not place firewalls between
premise equipment and the RDT. If a firewall is placed
between them, the following ports will need to be opened in
the firewall:
•
UDP 2427 on the primary CM's IP address (for
MGCP/NCS traffic).
•
UDP 7000-7361 for all 4 of the upm3's IP addresses.
Setting Up NNMBroker
Nuera’s NNMBroker is installed during the installation of
NueraView. The Broker is a tool to help organize a network
with numerous managed objects by linking the Nuera Configurator to network node managers, such as HP OpenView.
When you open your network node manager, the NNMBroker icon appears in your Windows desktop tray. Double click
on this icon and the NNMBroker window shown in Figure
30 on page 93 appears.
92
Figure 30. NNMBroker Initial Window
NNMBroker Menu Options
NNMBroker provides the following menu selections:
•
Options
•
View
•
OpenView
•
Help
Options
The Options menu provides the following choices:
Settings
The NNMBroker polls the unit, and will generate an
OpenView application event if it cannot communicate
with the RDT, or a CRC mismatch indicates a configuration change. Use this option to set the polling interval.
Select a value (expressed in minutes) from 0 to 100.
After setting the interval, click OK to apply the selection.
93
Close
Select Close to minimize the program.
Exit
Select Exit to terminate the program.
View
Under the View option, select Refresh List to update the list
of displayed devices.
OpenView
The OpenView menu provides the following choices:
Manage
Use this option to enable OpenView to manage a selected
device. This option enables you to select the code version
of the device and enable polling. Click OK to apply your
choices.
Unmanage
Use this option to release a selected device from OpenView management. Click Yes to apply your choices.
Help
The Help menu provides the following choices:
Help Topics
Use this option to display online help information.
About NNMBroker
Use this option to display product information.
Note
94
If a single HP OpenView station is monitoring ten or more
ORCA gateways, the polling interval should be set to 5 minutes. If a single HP OpenView station is monitoring less than
ten gateways, the polling interval should be set to 1 minute.
NueraView Maintenance Notes
Directing Alarms
To direct alarms to your Nuera workstation PC, remember
to:
1. Launch the ORCA icon.
2. Under the System menu, select Manager Config and
enter the IP address of the PC.
Updating the MIBs
New releases of NueraView often include new MIBs that
need to be loaded into OpenView. Follow the procedure
below to load in new alarm traps:
1. Install the latest version of NueraView onto your Nuera
workstation PC. It will contain the orcatrap.mib file
with the new alarms.
2. In OpenView, go to the Options menu and select Load/
Unload MIBs:SNMP.
3. Highlight orcaTrap.mib. Click on Load.
4. Select the file: C:\Program Files\Nuera\NueraViewORCA\7.0\Mib\orcatrap.mib
5. Click OK to all warnings. Click Close.
6. Go to the Options menu and select Event Configuration.
7. In the upper window (Enterprises), scroll down and
select orcaTrap. In the lower window (Events for Enterprise orcaTrap), select each new alarm in turn and do
the following:
•
Double click on the alarm.
•
Click on the Event Message tab.
•
Click the Log & Display radio button.
•
Select Error Alarms.
•
Click OK.
95
8. When all the new alarms have been updated, close the
dialog box. When you are prompted to save the changes,
click Yes.
96
BIBLIOGRAPHY
This appendix provides a brief, annotated bibliography of
publications that provide information relevant to the understanding of the design and management of the ORCA communications platform.
Hardware Specifications
“CompactPCI 2.0, R2.1 cPCI Specification”, PICMG. Rogers Communications, Wakefield, MA, September, 1997.
CompactPCI is a high-performance industrial computer
platform based on the standard PCI electrical specification
in rugged Eurocard packaging, with a high-quality 2mm
metric pin and socket connector.
CompactPCI is suited for telecommunications, computer
telephony, real-time machine control, industrial automation, real-time data acquisition, instrumentation, military
systems and other applications requiring high speed computing and modular and robust packaging design. The CompactPCI specification defines both 3U (100 x 160mm) and
6U (233 x 160mm) card formats for modular, rack-based systems.
Version 2.1 incorporates many additions and clarifications
over the previous Version 1.0 that was released in November 1995. Enhancements in the CompactPCI 2.1 specification include:
•
Clarified/corrected interrupt routing
•
IEEE1101.10 enhanced Eurocard mechanics
•
Adoption of a consistent method for rear panel I/O connections as defined by the IEEE 1101.11 Draft specification
97
•
Rear panel I/O drawings and pin assignments provided
•
Geographic addressing defined that allows a card to read
its slot ID
•
Physical vs. logical slot addresses defined
•
The concept of bus segments vs. backplanes
•
Pull-up resistor now required on boards implementing
GNT#
•
Backplane and board decoupling requirements clarified
•
Backplane termination requirements illustrated
•
Updated mechanical drawings
•
Dedicated clock routing and other provisions for future
hot swap
•
32-bit trace lengths for 64-bit and 32-bit systems
Revision 2.1 of the specification provides features useful to
telecom, including geographic addressing, standardized rear
panel I/O connection methods, and mechanics that address
tough international safety and emissions standards.
“CompactPCI 2.1, R1.0 cPCI Hot Swap Specification”, PICMG.
Rogers Communications, Wakefield, MA, August, 1998.
This document details how to implement the "hot swapping"
of components in CompactPCI systems; that is, the capability of removing and replacing components without turning
off the system. Hot Swap capability is increasingly important in systems used for applications such as telecommunications, which require that the system be operational at
some level continuously. CompactPCI is a high-performance
industrial computer platform based on the standard PCI
electrical specification in rugged Eurocard packaging, with a
high-quality 2mm metric pin and socket connector.
The new CompactPCI Hot Swap Specification defines pin
sequencing and other enabling hardware technologies, as
well as the software architecture required to support live
insertion and extraction of boards in a running CompactPCI
system. The new specification was approved in July 1998 by
PICMG's Executive membership. Copies are presently being
distributed to all members of the organization.
98
Bibliography
The Hot Swap specification is also available to non-members
for a nominal fee
The Hot Swap Specification provides a framework for
designing CompactPCI Hot Swap components (boards, backplanes, ICs, platforms, etc.). This framework gives vendors
some flexibility to choose the features appropriate for their
products, and still operate with all other CompactPCI components (Hot Swap and non-Hot Swap).
“CompactPCI 2.5 R1.0 cPCI Computer Telephony Specification”,
PICMG. Rogers Communications, Wakefield, MA, April, 1998.
This document defines the utilization of CompactPCI userdefinable pins for the computer telephony functions of a
standard TDM (Time Division Multiplexed) bus, telephony
rear I/O, 48 Volts DC and ringing distribution in a 6U chassis environment. CompactPCI is a high-performance industrial computer platform based on the standard PCI electrical
specification in rugged Eurocard packaging, with a highquality 2mm metric pin and socket connector.
The Computer Telephony Specification extends the capabilities of the CompactPCI architecture to support specific
application needs of the industry:
•
Hot swappable TDM bus on J4 complying with the ECTF
H.110 specification
•
Two and four wire I/O of J5 for analog and digital telephony
•
Frame grounding techniques based on IEEE 1101.11
•
Sub-bus and front panel keying
•
Geographical slot addressing and shelf enumeration
This specification provides guidance for backplane/chassis
vendors, CT card vendors, and CT system integrators, so as
to promote multi-vendor interoperability and the design of
open, standards based components and systems.
99
Network Management Publications
Leinwand, Allan; Conroy, Karen. Network Management: A
Practical Perspective 2nd Edition. Addison-Wesley Publishing Company, 1996. ISBN 0-201-60999-1
Comer, Douglas. Internetworking With TCP/IP: Principles,
Protocols, and Architecture 2nd Edition. Englewood Cliffs,
New Jersey: Prentice-Hall, 1988. ISBN 0-13-470154-2
Rose, Marshall T. The Simple Book: An Introduction to Management of TCP/IP-based Internets. Englewood Cliffs, New
Jersey: Prentice-Hall, 1989. ISBN 0-13-812611-9
Murray, James. Windows NT SNMP 1st Edition. O’Reilly &
Associates Publishing, 1998. ISBN 1-56592-338-3
Hewlett Packard Publications
HP OpenView Network Node Manager Installation
Quick Start
This book contains instructions about installing and configuring NNM.
Welcome to Network Node Manager
An overview of NNM, its features, and its capabilities.
Managing Your Network with HP OpenView Network
Node Manager
This book contains detailed information to help network
administrators configure, maintain, and troubleshoot
NNM.
100
Bibliography
Guide to Scalability and Distribution for Network
Node Manager
This advanced book outlines steps you need to take to
deploy NNM across multiple management stations
within your organization. It contains specific configuration procedures for using the scaling and distribution
features of NNM. These features are important when the
size of your organization’s network exceeds the resources
of one NNM management station. They enable you to
divide the work load among multiple management stations, yet share the network management information,
as needed.
101
102
WARRANTY
Nuera's standard warranty is one year from the date of shipment and is verified by
serial number of the system. Any defective component will be replaced or repaired at
no charge during this period. An advance replacement will be sent or on-site repair
performed at Nuera's discretion, at no charge, if any equipment fails within the first
90 days of shipment. After that period, and for the reminder of the warranty, defective modules will be repaired at Nuera and then returned to the customer.
Once the warranty has expired, the components can either be returned to Nuera for
repair, or an advance replacement can be provided. The repair and advanced replacement pricing are described in Table 1 and Table 2.
OUT OF WARRANTY REPAIRS
Out of Warranty Repairs are described in Table 1.
Table 1. Out of Warranty Repairs
Part No.
Number of Units
800-027-063
ORCA GX / RDT component
Discount
F
List Price
500
In order to exercise your rights to repair under this warranty, you must first contact
Nuera to obtain a repair authorization (RA) number. If you must return the unit to
Nuera for repair while the unit is under warranty, Nuera will pay the cost of shipping
it to and from Nuera.
EXTENDED WARRANTY
The standard warranty period can be extended up to five years (in one year increments), with an optional extended warranty. The extended warranty requires a
maintenance plan of equal duration and must be purchased within the initial 90 day
standard warranty period.
The Extended Warranty is described in Table 2.
Table 2. Extended Warranty
Part No.
Description
800-027-069
Extended warranty provides repair of all components during the 12 month period of the
plan.
Discount
F
List Price
2% of list price (including all hardware and
software) per year
SOFTWARE LICENSE AGREEMENT
Any software product, including any documentation relating to or describing such
software (hereafter collectively called “Software”), provided by Nuera is furnished to
you for installation and use on a single computer. The Software may not be copied, in
whole or in part, except for archival purposes, to replace a defective copy, or for program error verification.
You may not reverse engineer, decompile, or disassemble the Software, except to the
extent such foregoing restriction is expressly prohibited by applicable law.
Unless earlier terminated by Nuera as herein provided, the term of each paid-up
license shall expire at such time as you discontinue use of the applicable Software on
the single processor specified above but otherwise shall be without restriction as to
time.
The Software (including any images, applets, photographs, animations, video, audio,
music, and text incorporated into the Software) is owned by Nuera or its suppliers
and is protected by United States copyright laws and international treaty provisions.
Therefore, you must treat the Software like any other copyrighted material (for
example, a book or musical recording) except that you may either (a) make one copy
of the Software solely for backup or archival purposes, or (b) transfer the Software to
a single hard disk provided you keep the original solely for backup or archival purposes. You may not copy the printed materials accompanying the Software.
You may not rent or lease the Software, but you may transfer the Software and
accompanying written materials on a permanent basis provided you retain no copies
and the recipient agrees to the terms of this Agreement. If the Software is an
upgrade, any transfer must include the most recent upgrade and all prior versions.
299-297-501
READER’S COMMENT FORM
This book is part of a library that serves as a reference for network communications
managers and systems integrators who want to incorporate advanced voice compression
technology and data transmission over IP networks for remote access to host sites or to
other remote sites. If you have any comments regarding this book (including its content,
organization, and format), use this form to communicate them directly to Nuera. You can
also send your comments by e-mail to Nuera at tac@nuera.com. If you have received any
revision pages to update this book, please identify them in your correspondence.
Your comments will be reviewed and appropriate action taken, as necessary. Nuera may
use or distribute the information you supply without incurring any obligation to you.
If you would like additional information regarding the ORCA product series, or any other
Nuera product, please contact our marketing department at the following address:
San Diego, California 92121
U.S.A. 1-(800) 966-8372
U.S.A. 1-(858) 625-2400
105
Fold along dotted lines and tape. Please do not staple
Place
Postage
Here
Information Development
San Diego, CA 92121
USA
Fold along dotted lines and tape. Please do not staple
299-297-501
10445 Pacific Center Court, San Diego, CA 92121 (858) 625-2400; FAX (858) 625-2422

ORCA RDT-8G SOFTWARE ANUAL

Transcription

Similar documents

JOSOS project completed (PDF Document)

Data Sheet - Pulse Supply

Strategies for Infusing Global Concepts and Content into the K

VulCAin

marmolada orbea

Money`s wasted, animals are mutilated

Equipment Catalogue - Orca Coast Playgrounds

ORCA - Foundry Toolkit for Government Business

Newsletter Week 8 - Point View School

sponsorship package