UIReference - Arris PDF

Cornerstone
User Interfaces
Reference Guide
Release 8.1 Standard 1.0 September 2001
ARSVD00399
Cornerstone
User Interfaces Reference Guide
Document number: ARSVD00399

Release 8.1 Standard 1.0
September 2001
 2001 ARRIS
All rights reserved
The information in this document is subject to change without notice. The statements, configurations, technical data, and
recommendations in this document are believed to be accurate and reliable, but are presented without express or implied warranty.
Users must take full responsibility for their applications of any products specified in this document. The information in this document
is proprietary to ARRIS.
ARRIS, ARRIS Interactive, and Voice Port are trademarks of ARRIS Licensing Company. Cornerstone is a registered trademark
of ARRIS Licensing Company. AccessNode is a registered trademark of Nortel Networks. All other trademarks and registered
trademarks are the property of their respective holders.
User Interfaces Reference Guide Release 8.1 Standard 1.0 September 2001
iii
Publication history
September 2001
Release 8.1, Standard 1.0 version of this document which includes changes for
CsV08.1.
September 2000
Release 6, Standard 2.0 version of this document which includes changes for
CS06.2.
June 1999
CS06.1.
April 1999
CS06.
December 1998
CsV05.2.
August 1998
CsV05.
March 1998
Release 3, Standard 1.0 of this document.
October 1997
Release 2, Standard 1.0 of this document.
October 1996
Release 1, Standard 2.0 version of this document.
July 1996
Release 1, Standard 1.0 version of this document.
iv Publication history
Cornerstone ARSVD00399 Release 8.1 Standard 1.0 September 2001

v
Contents
About this document 1-xi
Terminology 1-xi
References in this document 1-xi
Warnings and safety precautions 1-xii
Network element user interface 1-1
Overall features 1-1
Screen layout 1-2
Command inheritance 1-8
The concept of “context” 1-8
Editable fields 1-8
Toggled fields 1-9
Status messages 1-9
Input and output editing features 1-11
Command input 1-11
Macros 1-12
Command parameter prompting 1-12
Last command recall 1-13
Multiple command entry 1-13
Command output 1-13
Command confirmation 1-13
Common menu commands or options 1-13
Line editing 1-15
Operational commands 1-16
Help 1-16
Paging 1-17
Scrolling 1-17
Event logs 1-17
Command menus 1-20
OPC character-mode user interface 2-1
Logging in to the CMT environment 2-1
For HP host systems 2-1
For Sun host systems 2-2
User Session Manager 2-3
Status icons 2-4
vi Contents
Moving through the CMT user interface 2-5

Using the keypad 2-5
Using the keyboard 2-5
Moving the cursor 2-7
Exiting or canceling a mode 2-7
Using tools 2-8
Opening a tool 2-10
Returning to the User Session Manager 2-10
Accessing an open tool 2-10
Refreshing the screen 2-11
Moving from one open tool to another 2-11
Closing a tool 2-12
Using menus 2-12
Displaying a menu 2-13
Menu mode 2-15
Scrolling 2-16
Processing a single list item 2-18
Working with the list as a whole 2-19
Using dialogs 2-20
Moving a dialog 2-20
Moving from dialog to dialog 2-21
Closing a dialog 2-21
Getting help 2-22
Fields 2-24
Choosers 2-24
Scrolling fields 2-24
Radio buttons 2-24
Check boxes 2-25
Action buttons 2-25
Did you make an error? 2-25
Editing text 2-26
Basic editing 2-26
Selecting text 2-26
Cutting and pasting text 2-26
Copying and replacing text 2-26
Editing shortcuts 2-27
Closing a tool 2-27
Logging out 2-28
Using UNIX 2-29
OPC graphical user interface 3-1
Logging in 3-1
Moving through the graphical interface using the mouse and keyboard 3-3
Using the mouse 3-3
Using the keyboard 3-4

Contents vii
Using tools and toolsets 3-5

Using the workspace 3-5
Displaying a tool in the toolset menu 3-6
Starting a tool from a toolset menu 3-7
Status icons 3-8
Closing a tool 3-9
Using the main window 3-10
Using menus 3-11
Menu bar menus 3-11

Using lists 3-13
Scrolling 3-14
Managing the workspace 3-16
Targeting a window 3-18
Sending windows forward or backward 3-19
Moving windows 3-19
Minimizing windows 3-20
Maximizing windows 3-20
Restoring a maximized window 3-21
Restoring a minimized window 3-21
Sizing a window 3-22
Getting Help 3-23
Entering information 3-26
Fields 3-27
Buttons 3-30
Action buttons 3-31
Editing text 3-32
Entering text 3-32
Selecting blocks of text 3-32
Cutting, copying, pasting, and replacing text 3-33
Editing commands 3-34
Command areas 3-35
Closing a tool 3-37
Logging out 3-38
CI tool user interface 4-1
Commands common to all Cornerstone CIs 4-2
Voice Port aliases 4-2
Opening a CI tool 4-2
CSOPTCI commands 4-3
CVALRM CI commands 4-6
CVEQPT CI commands 4-10
CVLOADER CI commands 4-33
CVPATH CI commands 4-41
CVPROV CI commands 4-68
RF concentration 4-69
CVSPMN CI commands 4-98
CVTRAF commands 4-105
Field definitions 4-105
CVV5 commands 4-115
viii Contents
MVIPROV commands 4-142

Requirements 4-142
FAMCI commands 4-148
OMCCI commands 4-154
VLCMCI commands 4-159
User-interface overview 5-1
Levels of control 5-1
Access to the user interfaces 5-4
NEUI 5-4
OPCUI 5-5
Description of the network element user interface 5-6
Menu based screens 5-6
Description of the OPC user interface 5-7
Software tools and toolsets 5-7
User Session Manager 5-9
Software administration toolset 5-10
OPC administration toolset 5-14
Network administration toolset 5-18
Network surveillance toolset 5-24
SLAT toolset 5-27
Provisioning administration toolset 5-29
Utilities toolset 5-30
Network element user interface procedures 6-1
Chapter task list 6-1
Requirements 6-2
Procedure 6-1 Connecting a local terminal to the network element LCAP 6-3
Procedure 6-2 Connecting a remote VT100-compatible terminal using an
external modem 6-5
Procedure 6-3 Logging in to the network element, and logging out 6-7
If you cannot log in to the FWPUI 6-10
Procedure 6-4 Logging in to the far-end NE from the local NE 6-11
Procedure 6-5 Logging in to a network element from the OPC, and logging out
6-13
Logging in 6-13
Logging out 6-15
Procedure 6-6 Logging in to the Cornerstone toolset 6-16
Procedure 6-7 Opening a network element user interface session from other
levels of the interface 6-17
Changing your network element password 6-19
Procedure 6-8 Working with line cards 6-20
Procedure 6-9 Determining NE status on V5.2 systems 6-22
OPC user interface procedures 7-1
Requirements 7-2
Procedure 7-1 Connecting a terminal to an OPC 7-4
Procedure 7-2 Connecting a terminal to the portable OPC 7-13
Procedure 7-3 Connecting the portable OPC to the network element 7-15
Procedure 7-4 Connecting a remote terminal to the OPC using an external

Contents ix
modem 7-17
Procedure 7-5 Logging in to the OPC 7-19
Procedure 7-6 Logging in to the remote OPC from a local OPC 7-23
Procedure 7-7 Logging in to an OPC from a network element 7-26
Procedure 7-8 Logging in to the Cornerstone toolset 7-28
Procedure 7-9 Opening an OPC tool 7-31
Procedure 7-10 Closing an OPC tool 7-33
Procedure 7-11 Logging out of the OPC 7-34
Procedure 7-12 Changing your password 7-36
Procedure 7-13 Displaying OPC status 7-39
Procedure 7-14 Changing the name of an OPC 7-41
Other OPC procedures 8-1
Requirements 8-2
Procedure 8-1 Shutting down an OPC 8-3
Procedure 8-2 Checking the OPC tape identification 8-7
Procedure 8-3 Saving OPC data to tape 8-9
Procedure 8-4 Restoring OPC data from tape 8-15
Procedure 8-5 Transferring data between OPCs 8-24
Procedure 8-6 Detecting and/or removing existing OPC software 8-27
Procedure 8-7 Installing software in a local OPC 8-31
Procedure 8-8 Restoring an NE database 8-34
Procedure 8-9 Setting the time zone, date, or time 8-39
Using the CI tool user interface 9-1
Procedure 9-1 Opening a CI tool 9-2
Procedure 9-2 Displaying the help screen for a CI tool 9-4
Procedure 9-3 Entering a CI command 9-5
Procedure 9-4 Closing the CI tool 9-6
OPC Ethernet port configuration and connections 10-1
How to Use this Chapter 10-2
Requirements 10-2
X terminal support 10-3
X terminal equipment recommendations 10-4
X terminal setup requirements 10-5
Instructions for X terminal setup 10-7
Replacing or exchanging X terminals 10-8
LAN considerations 10-8
Cabling options 10-9
Session-terminating conditions 10-12
Troubleshooting guidelines for X terminals 10-13
Engineering guidelines for OPC X terminal sessions 10-15
Procedure 10-1 Initializing the OPC Ethernet port 10-16
Procedure 10-2 Enabling and disabling the OPC Ethernet port 10-20
Procedure 10-3 Connecting the OPC to network equipment 10-23
Procedure 10-4 Establishing a telnet session between an X terminal and the OPC
10-24
Procedure 10-5 Adding, changing, or deleting an NCD19 configuration file 10-25
Procedure 10-6 Loading the NCD19 configuration data from the OPC to an NCD19
x Contents
X terminal running NCDware v.2 10-29

Procedure 10-7 Loading the NCD19 configuration data from the OPC to an NCD19
X terminal running NCDware v.3 10-31
Procedure 10-8 Reconfiguring X terminals following an OPC upgrade 10-32
Index 11-1

xi
About this document

This document contains reference information and procedures describing the
Cornerstone® user interfaces.
Chapters 1 through 4 describe the user interfaces available for a Cornerstone

system. The remaining chapters provide user interface procedures that are used
commonly while setting-up and maintaining a system.
If you cannot successfully complete any of the procedures in this manual,

contact your next level of support.
Terminology
The terms “downstream” and “upstream” used in this document refer to the
direction of transmission towards the customer site and towards the head-end,
respectively. This nomenclature follows that of the telephony industry.
Equivalent cable industry terminology is “forward” and “return”, respectively.
References in this document

This document refers to the following documents in the Cornerstone
documentation suite:
• Engineering Guidelines, ARSVD00388
• HDT Commissioning and Testing Guide, ARSVD00391
• System Administration Guide, ARSVD00400
The following is a list of other related reference documents:

• An Introduction to Display Editing with Vi by W.M. Joy and M. Horton
• Vi Comand and Function Reference by A.P.W. Hewett and M. Horton
xii About this document
Warnings and safety precautions

To avoid injury, follow all danger warnings provided with this product, as well
as safety procedures established by your company.
To avoid damage to equipment or service interruptions, follow all caution

warnings provided with this product, as well as procedures established by your
company.
Samples of danger and caution warnings follow.
DANGER
Risk of personal injury
A danger warning advises you of a risk of personal injury.
DANGER
This warning advises you of a possible electrical hazard. When
you see this warning, proceed with care, to avoid personal
injury.
CAUTION
Risk of service interruption or equipment damage
A caution warning advises you of a risk of service interruption
or equipment damage.
CAUTION
Risk of equipment damage
This warning advises you of possible equipment damage.
Observe precautions for handling electrostatic sensitive
devices.

1-1
Network element user interface 1-

This chapter discusses the features available on the Network Element User
Interface (NEUI). The full-screen layout is described and the input and output
editing features are explained to simplify the use of CI User Interface Quick
Reference, ARSVD00412 of the NEUI. Table 1-6 on page 1-19 summarizes
the editing and control keys. Only a subset of these features is offered when
using the line-by-line mode.
The command menus provided in the user interface are included at the end of
this chapter.
Overall features
The NEUI is a menu-based, user-friendly interface to the network. The menu
hierarchy of the user interface allows access to the following:
• alarms
• configuration and provisioning
• performance monitoring
• maintenance
• protection switching
• on-line inventory
The NEUI provides the following screen attributes:

• screen partitioning
• display of alarms, alerts, and other log messages
• access control by means of user IDs and passwords
• recall of the last three commands
• on-line command Help
• paging of the output
• command entry macros
• command entry by menu number
• wide range of command line editing features
1-2 Network element user interface
• categorized on-screen alarm indicators

• automatic parameter prompting
• remote access to other network elements
• use of appropriate defaults and context for commands
Each network element allows multiple users to be connected to the user

interface. A total of three local and eight remote NE login sessions from the
Operations Controller (OPC) users can be connected at one time. The NEUI
also provides single-ended maintenance. This means that from a central
location you can remotely monitor, provision, maintain, and troubleshoot
network elements that are in your span of control.
Screen layout
The user interface allows you to access all system alarms, status and control
information, and commands. The user interface screens are organized to make
it easy for the new user to read, understand, and use the Video Display
Terminal (VDT). The following shows the screen template:
CS-10232
CS-10232
Selected NE System Status Area
Work Area
Static area
Command Status Messages
Menu
Display
Area
Screen dependent
Output Scroll Area

(Conversation area)
Host NE Command Input Area

Time 00:00 >
As shown above, the screen is partitioned into six areas:

• system status area
• work area (static area)
• command menu display area
• output scroll area (conversation area)
• command input area
• NE identity and time area

System status area

The system status area occupies the top portion of the screen and consists of
three lines of 78 characters each. This area displays:
• counts of the critical, major, and minor alarms
• system warnings
• the NE that is currently displayed
Changes to the critical, major, minor and warning fields are shown in inverse
video to indicate when new alarms are generated and that they should be
investigated.
The system status area also contains fields indicating current protection
activity failures and lockouts, and a field to alert of performance degradation.
A question mark “?” in the top left corner of the system status area indicates
that system level data may be incorrect due to a temporary loss of
communication with the OPC.
CS-10224
CS-10224
Critical Major minor warning FailProt Lockout ActProt PrfAlrt
1 Ottawa 2 3 1 1 * . . .
Command menu display area

The Command menu display area consists of 19 lines of 12 characters each
located at the left-most part of the screen. It displays all the functions available
to you in the form of a numbered menu. This area is updated as you move up
or down in the hierarchy of commands. The first line of the command menu
contains the title of the current display.
FW-10199
CSV Nodes
FW-10199
0 Quit
2
3 Alarms
4 ListNEs
5
6 PerfMon
7
8
9
10 Protectn
11
12
13 JackAcc
14
15 Equipmnt
16 Facility
17 Admin
18 Help

Command input area

The Command input area occupies the bottom line of the screen and consists
of a line of 64 characters. The Command line prompt is the “greater than” (>)
symbol. This area provides an echoed response of the command you are
entering.
FW-10197
FW-10197
NE 1
Time 17:35 >
NE identity and time area

The NE identity and time area consists of 2 lines of 12 characters located at the
bottom left of the screen. This area displays the:
• network element number (1 to 9999) to which the terminal is physically
connected or remotely logged into
• current time where the Time area is separated from the Command input
area by a “>” prompt.
Conversation area
The conversation area is located just below the work area and just above the
command line, and consists of 20 lines of 68 characters each. The conversation
area displays the information in a scroll format for displaying large amounts of
data.
FW-10196
FW-10196
NewAlms
Alm Class Type Sh Reason Severity
21 Env CE 1 SP Datacomm 0 station fail LOS C,SA
20 Env Input 1 Door Latch Open Clear

Work area
The work area displays information as a result of the commands you entered
on the command line.
The work area displays the information in a page format. It also displays
system status or information depending on the command you entered.
FW-10217
FW-10217
Network Element Status Shelf: 1
NE ID Alarms Protection Prf

Fac Eqp Env Svc Fail Lckt Act Alrt
1 Ottawa 2C+ 2M+ . - * . . .
Header information
For some screens in monitor mode, header information is not monitored even
though the screen’s contents are. For example, you are viewing protection
switching information, which is in monitor mode. The header information
(NE, shelf, or CLLI) is not being monitored. However, this header information
will rarely, if ever, change once provisioned.
Note: When an object is deleted, its screen is not updated in monitor mode.
The screen should be reselected to display the new status of deleted
objects.
Command inheritance
When you display a screen, the commands displayed become available. When
you display a “child” screen, the commands on the “parent” screen continue to
be available. Thus all commands from the main menu level down to the current
screen are available. Note that in some cases, a shortcut exists to move from
one menu hierarchy to another. In this case, only the commands in the new
menu hierarchy are available (for example, moving from the equipment to the
facility screens).
Commands on the main menu (a “parent” of all other menus) are available at
all levels. These commands (and abbreviations) are:
• Alarms (or AL)
• ListNES
• PerfMon (or PM)
• Protectn (or Prot)
• Equipment (or EQ)
• Facility (or FA)
• Admin (or AD)
The concept of “context”

The specific NE and shelf, once selected by a menu command, becomes the
context for any subsequent commands until they are explicitly changed. If no
NE/shelf is selected, the local NE and shelf are used as the default. The circuit
pack and, in some cases, port number can also be specified and included as part
of the context.
Note that some menu screens are specific to a certain type of context, and thus
changing the context is not always possible. In this case, you must return to the
main menu and re-enter the main menu command with the new context.
Editable fields
A field which is displayed within angled brackets (<...>) indicates that the field
contains a string which can be edited.

Toggled fields
Some fields contain a user-selected value which is one of a limited set of
possible values. You can either select the desired value explicitly with the
appropriate command or can toggle the value by entering the command
without any parameters. For parameters with two possible values, the
parameter toggles from its current value to the other possible value. For
parameters with more than two values, the parameter toggles from its current
value to the next “larger” value.
Note: It is not possible to toggle a parameter on a number of objects

simultaneously. Therefore, if you have selected all facilities or circuit
packs, you must state parameters explicitly.
Status messages
The fourth line of the screen (first line of the static work area) is normally
blank. This line is used to display important system messages. Messages
displayed in the scrolling conversation area are lost whenever the conversation
area is updated. A message displayed in the first line of the static work area is
not lost unless the condition which it reflects is corrected, or is no longer
relevant. The messages which may be displayed and the conditions which they
indicate are:
Monitoring Unavailable - Autonomous updating of the current screen (that

is, monitor mode) is not possible. Messaging which supports queries or edits
is functional between the user interface and is automatically updated as values
change.
Communications Lost - The communications link to the indicated network

element has failed. The NEUI will automatically attempt to re-establish this
link on a periodic basis and any time you invoke a command targeted for the
NE to which the association has failed.
Object Deleted - The object instance which was displayed on the current
screen has been deleted, possibly by another user. This message displays when
any posted unit is displayed. The “unit” might be a circuit pack group, a
facility, or a protection group. This indicates that any further operations against
this unit will be rejected, as the unit is no longer provisioned.
Could Not Retrieve Screen Data - The data required to display the current
screen could not be retrieved for some reason. The specific reason associated
with this indication is displayed in the conversation area. The reason will either
be that the requested instance does not exist (and may be added) or there was
a messaging failure. The most likely messaging failure is a timeout (that is, no
response received) due to either congestion of the OAM network or loading of
the target NE.
Fields Will Remain Blank Until You Change Them - Whenever you
display a screen with all instances of an object selected, no data is displayed in
the screen fields because the values for different object instances will generally
not be the same. For any fields that can be changed with all instances selected,
a value is shown in the field, if you successfully edit the field.
Operation In Progress, Please Wait - On initial entry to the Network

Status Screen, an attempt is made to establish a link with an OPC to provide
the network view. This attempt takes approximately one minute (depending on
the proximity of the OPC and other OAM activity). This message remains on
the fourth line until the OPC link is established or until the attempt times out.
Network Data Unavailable - The data that is used to maintain the network
banner line is unavailable. Most often, this is due to a failure of the link
between the NE which is hosting the login session and the OPC. The NEUI
will automatically attempt to re-establish this link on a periodic basis. In
addition, any time the user re-enters the Network Element Status screen from
CI or MAPCI, the NEUI attempts to establish this link.

Input and output editing features

The following describes input and output editing features of the NEUI.
Command input
The entry of commands is based on the VT100 key set. Some variations in
identification of keys may exist if another type of keyboard is used.
Throughout this documentation, to “enter” a command means to type in the

specified information and then press the Return key.
When selecting commands from the command menu display area, either the
entire string or just the number of the command can be specified.
All alphabetic input is case insensitive and is converted to uppercase.

However, single quotes (’ ’ ) can be used to enforce lower case for a string
input. These can be used when entering an NE name or FacID string and case
sensitivity is important. This must also be done if you include spaces or special
characters (!, ?, =), or if the first character is a number.
Any field on the screen containing a text string, which you can change, is
displayed with angled brackets (<...>). The brackets indicate the maximum
width of the text field, regardless of what has been entered for the string. The
brackets are intended to provide you with an indication that a field contains an
editable string, and the maximum allowable size of the string. The string may
be numeric, alphabetic, or alphanumeric, depending on the particular field.
The brackets are shown around such fields regardless of whether or not you are
permitted to edit the field. The brackets do not appear around toggled fields
which you can indirectly change or around display-only fields (that is, fields
which a user cannot alter using the user interface).
Commands with optional parameters have default values assigned to the

associated parameter if it is omitted when entered.
Replies to user input, error message, and confirmation sequences are displayed
at the output scroll area.
Refer to “Command menus” for a list of command menus and any associated
parameters.
Macros
The command macros are built into the operating system to allow repetitive
commands that do not require confirmation. You can group frequently used
sequences of commands as user-defined macros which can be called from the
NEUI. All macros are used when you log out from the operating system (using
Logout).
To create a macro, type:

Command <macro name> (menu commands separated by semi-colons)
where <macro name> is a string of up to 16-characters (valid characters are A
to Z, a to z, and 0 to 9).
Examples:
Command DS1prot (FWP; PROTECTN; DTLProt DS1)
Command DS1AlmPts (FACILITY DS1 G1 1; ALMPROV)
A macro command can call another macro, or several macros. Example:
Command Macro3 (macro2; macro1)
Note: Do not use macro names that are the same as existing commands.
To use a macro, type:

<MacroName> ↵
The add command, followed by an edit of the added object, should not be
entered using multiple command entry. This can cause the edit command to
begin while status messaging for the newly added object is still occurring. An
error message displays:
object does not exist
Caution should be used when a recursive macro is created (that is, the macro
name appears in the menu command brackets). This can cause the system to
be caught in a loop.
Command parameter prompting

If a command is entered with missing parameters, you are prompted at the
command input area for the required data. If more than one parameter is
required, a previously entered value(s) will be displayed in the output scroll
area. Enter Abort in response to a prompt to halt parameter prompting for a
command.

Last command recall

If you enter “=” or “?” at the first column of the command input area, the last
command entered is recalled and displayed in the command input area. This
step can be repeated to recall the last three commands.
Multiple command entry

A series of commands, each separated by a semicolon (;) can be entered at the
same time.
Note: Use of the menu number shortcut is only permitted for the first
command in a multiple command entry.
Command output
If a command cannot be carried out or fails, a command fail notification is
displayed at the output scroll area. Examples are as follows:
• The XXXXXXXX command failed. Please re-enter the command.
• If the problem persists, call the NT Technical Assistance
Service and quote error number NNN.
Command confirmation
A command confirmation sequence is provided when entering service
affecting commands such as deleting data. This function prompts you to
confirm the associated command by entering y (yes) or n (no).
Common menu commands or options

Table 1-1 lists and describes menu commands or options found throughout the
menu structure.
Table 1-1
Common menu commands or options
Command/Option Description
Forceout This allows a user with “admin” privileges to login to a

network element either locally or remotely (by means of the
OPC) and logout another user already logged into the same
Network Element. The command is issued by typing:
forceout <UserID> ↵
where userID is the identity of the user to be logged out.
FWP Displays the main menu (system level status screen). FWP
can be used at the FWPUI command interpreter level.
Help Displays help text specific to the current screen hierarchy (for
example, Alarms help, Facility help, etc.)
—continued—
ListNEs This command lists all NEs (by name and number) which you
can view.
Table 1-1
Common menu commands or options (continued)
Command/Option Description
Logout Log out from the user interface. This command is available at
any time.
Mainmenu Displays the main menu and selects the NE to which you are
physically connected.
Msg The message command allows you to send messages to one

or all other users logged into an NE. To send a message,
type:
msg all <message>
or replace “all” with a specific userID to send the message to
only one user.
New Displays any new alarms since the last new command.
Print users Lists all users who are logged into the NE in context.
Query This menu item is similar to the select menu option except
that the requested data is placed in the output scroll area so
as to not delete the original data. However, the output scroll
area displays data in snapshot mode and is not updated if
changes occur.
Quit Returns to the parent level menu in the current menu

hierarchy.
Note: When a shortcut is used to move from one hierarchy to
another, the quit command does not return you to the
previous hierarchy. A “number of levels” parameter can be
assigned optionally to the quit command. This indicates the
number of levels you want to quit. The syntax is Quit # (or
0#). Quit all brings you to the Command Interpreter (CI) level.
Quit all; MAPCI This can be used to determine who is logged in at a terminal.
The userID is displayed in the bottom left-hand corner.
show users Lists all users who have access to the NE in context. (This
command is available to users with command classes 1, 2,
and 3 only).
Showval On the performance screens, this command shows values in

full precision (that is, 52E2 as 5243).
—end—

Line editing
Table 1-2 lists and describes the line editing functions available in the
command input area.
Table 1-2
Line editing
Command Description
<ctrl> E Deletes all characters from the cursor position to the end of the
line.
<ctrl> F Moves the cursor to the right, one position.
<ctrl> I Switches the cursor to the insert mode.
<ctrl> U Deletes the entire input line.
<ctrl> X Switches the cursor to overwrite mode, any subsequent input will
overwrite existing characters.
<- Also called the BACKSPACE key, moves the cursor to the left
one position.
Note: Inappropriate use of an editing command can cause the terminal to

beep. This depends on the keyboard setup.
Operational commands
Table 1-3 lists and describes the operational commands which allow you to
control processes started by the interface commands and are available
throughout the UI.
Table 1-3
Operational commands
Command Description
<break> HX Clears the screen and exits to the Command Interpreter (CI)
level.
SIL Stops all flashing on-screen indicators and inverse video until the
next status change occurs.
ABORT When entered in response to a request for parameters for a

command, abort halts the prompting and cancels the associated
command.
ACO Alarm Cut-Off. Turns off audible alarms in a CO environment.

HT Halts the currently scrolling output.
REFRESH Redraws the current screen.
leave Quits to the parent screen.
Note: The <break> command is sent with the <break> key on the VT100
terminal (usually F5). The <break> command is always received at the NE
to which you are logged on. However, if you have logged in to a remote NE
(using the NE Login Manager or by using the rlogin command), you must
enter CTRL_B instead of <break>.
Help
Prefixing any command with Q displays the function and format of that
command. A space is required between Q and the command being queried.
If a parameter is missing or invalid when entering a command, a parameter

description appears in the output scroll area along with a prompt in the
command input area for the associated parameter. You should then enter the
parameters. When the Help command (available on each menu) is entered, you
are provided with a description of the current screen, the primary functions
available, a list of hidden commands, definitions of symbols, and other useful
information.

Paging
If the amount of data generated in response to a command exceeds the
available display area, a prompt appears, indicating the number of pages. To
view the pages, the commands shown in Table 1-4 can be used.
Table 1-4
Paging commands
Command Description
F Forward - next page of data
B Back - previous page of data
H Home - first page of data
P <n> - page “n” of data
Scrolling
If the amount of data generated in the conversation area exceeds the available
area for display (for example, during parameter prompting), the prompt
“more...” appears. Use the Return (↵) key to view subsequent data. Enter ht to
halt the scrolling of data. The last page of data is identified by the absence of
the “more...” prompt.
Event logs
The event log system records all status changes in the network element. The
event log messages can be automatically routed to a printer connected to a
local RS-232 port provisioned for a printer. It can also be printed at operator
request through a printer attached to the VT100 or compatible user terminal.
There are five categories of event messages generated by the network element
system. These include facility (FAC), equipment (EQP), communications
(COML), database (FWDB), and exceptions (miscellaneous - EXCP). Reports
can be set up and printed based on the different categories. To get a list of
available reports, type ListReps in LOGUTIL. Each buffer handles 40 event
messages. When a particular buffer is full, a first-in first-out algorithm
accommodates additional incoming messages.
The LOGUTIL menu offers the options shown in Table 1-5.

Table 1-5
LOGUTIL options
LOGUTIL Description
Option
Open Select a log buffer for viewing and displaying the current report
entry.
ClearLog Erase the contents of a log buffer.
Format Change the output format of reports, when OPENED.

This command has no effect on reports when generated.
Type Display the current report entry.
First Display the first report entry.
Last Display the last report entry.
Back Display the report entry before the current entry.
Forward Display the report entry after the current entry.
Start Start displaying reports as they are generated.
Stop Stop displaying reports as they are generated.
StartDev Start the specified device for outputting logs.
StopDev Stop the specified device for outputting logs.
ListLogs List all logs defined in the user interface database.
ListReps List all report types for selected logs or categories.

Table 1-6 provides a summary of the editing and control keys.

Table 1-6
Summary of editing and control keys
Type of editing or
function control Keys Function
Command input <ctrl> E deletes all characters from the cursor to the
editing end of the line
<ctrl> F moves the cursor to the right, one position
<ctrl> I toggles the cursor between insert mode and

overwrite mode
<ctrl> U deletes the entire line
<ctrl> X switches the cursor to overwrite mode
<- backspaces
<del> deletes a character
= [1st column] recalls the last command
Operational <break> HX clears the screen and exits to the command

command interpreter (CI) level
SIL stops all flashing on-screen indicators and

inverse video until the next status change
occurs
ABORT when entered in response to a request for

parameters for a command, “abort” halts the
prompting and cancels the associated
command
ACO alarm cut-off; turns off audible alarms in a CO

environment
HT halts the currently scrolling output
REFRESH redraws the current screen
Scrolling <CR> views subsequent page after more... prompt
ht stops display of subsequent pages
Paging F Forward displays next page of data

B Back displays previous page of data
H Home displays first page of data
P <n> displays page “n” of data
Command menus
This section provides a summary of all the menus provided in the user
interface. Table 1-7 lists these menus.
Table 1-7
Menu layouts
Figure Menu layout
Figure 1-1 Mapci menus
Figure 1-2 Alarms menus
Figure 1-3 Protection menus
Figure 1-4 Performance monitoring menus
Figure 1-5 and Figure 1-6 Facility menus
Figure 1-7 through Figure 1-9 Equipment menus

Figure 1-10 and Figure 1-11 Administration menus
Figure 1-12 Help menus
Note: The commands available to you are determined by the your

command classes.

Figure 1-1
Mapci menus
Mapci S/DMS Nodes

0 Quit 0 Quit
2 2
3 FWPUI 3 Alarm
4 4 ListNEs
5 5
6 6 PerfMon
7 7
8 8
9 9
10 10 Protectn
11 11
12 12
13 13 JackAcc
14 14
15 15 Equipmnt
16 16 Facility
17 17 Admin
18 18 Help
Figure 1-2
Alarms menus
FW-21457
CS Nodes Alarms DtlAlms

0 Quit 0 Quit 0 Quit
2 2 2 Next
3 Alarms 3 Filter 3 Prev
4 ListNEs 4 Update 4
5 5 History 5
6 PerfMon 6 AlmRpt 6
7 7 NewAlms 7 NewAlms
8 8 8
9 9 DtlAlms 9
10 Protectn 10 DtlProt 10 DtlProt
11 11 11
12 12 12
13 JackAcc 13 13 JackAcc
14 14 14 Port
15 Equipmnt 15 15 Equipmnt
16 Facility 16 16 Facility
17 Admin 17 17
18 Help 18 Help 18 Help
Figure 1-3
Protection menus
CS Nodes Protectn DS1Prot ProtProv

0 Quit 0 Quit 0 Quit 0 Quit
2 2 2 2
3 Alarms 3 3 3
4 ListNEs 4 4 4
5 5 ListProt 5 ListAlms 5 WaitToR
6 PerfMon 6 6 AlmRpt 6
7 7 7 Lockout 7 Priority
8 8 8 Forced 8
9 9 9 Manual 9
10 Protectn 10 DtlProt 10 10
11 11 11 11
12 12 TrefProt 12 12
13 JackAcc 13 13 13
14 14 14 14
15 Equipmnt 15 15 Equipmnt 15
16 Facility 16 16 Facility 16
17 Admin 17 17 ProtProv 17
18 Help 18 Help 18 Help 18 Help
Figure 1-4
Performance monitoring menus
CS Nodes PerfMon FP Stats

0 Quit 0 Quit 0 Quit FP History
2 2 2 Select 0 Quit
3 Alarms 3 3 2 Select
4 ListNEs 4 4 3
5 5 ListAct 5 Clear 4
6 PerfMon 6 AlmRpt 6 StartUnt 5 Clear
7 7 7 6 LineCV
8 8 8 7 LineES
9 9 9 8 LineSES
10 Protectn 10 ProtSwit 10 9 PathCV
11 11 11 ShowRsrc 10 PathES
12 12 12 11 PathSES
13 JackAcc 13 13 12 PathSAS
14 14 14 13 PathUAS
15 Equipmnt 15 EqpPerf 15 14 PathFC
16 Facility 16 FacPerf 16 History 15 Stats
17 Admin 17 17 Threshld 16
18 Help 18 Help 18 Help 17 Threshld
18 Help

Figure 1-5
Facility menus (sheet 1 of 2)
CS Nodes
0 Quit
2
3 Alarms
4 ListNEs
5
6 PerfMon
7
8
9
10 Protectn
11
12
13 JackAcc
14
15 Equipment
16 Facility
17 Admin
18 Help
DS1
DS 1/3 Fac Edit Fac AlmProv
2 Select 2 Select 2 Select
3 Query 3 Query 3
4 4 4
5 ListAlms 5 FacID 5 ListAlms
6 AlmRpt 6 LCoding 6 ALMRpt
7 Loopback 7 LBO 7
8 ChgState 8 FrameFmt 8
9 9 AlarmEnc 9
10 DtlProt 10 Synchr 10
11 Edit 11 PMProv 11 EditStat
12 12 12
13 Add 13 13
14 Delete 14 14
15 Equipmnt 15 15
16 16 16
17 AlmProv 17 17
TIC
TIC Fac AlmProv TIC Fac AlmProv
2 Select 2 Select 2 Select 2 Select
3 Query 3 3 Query 3
4 4 4 4
5 ListAlms 5 ListAlms 5 ListAlms 5 ListAlms
6 AlmRpt 6 AlmRpt 6 AlmRpt 6 AlmRpt
7 SubPtSel 7 7 7
8 ChgState 8 8 ChgState 8
9 9 9 9
10 TrlateSP 10 10 TrlateSP 10
11 11 EditStat 11 11 EditStat
12 12 12 12
13 13 13 13
14 14 14 14
15 Equipmnt 15 15 Equipmnt 15
16 16 16 16
17 AlmProv 17 17 AlmProv 17
Figure 1-6
Facility menus (sheet 2 of 2)
CS Nodes Comm Fac OMC/VLCM EOC/CSC/TMC CNET

0 Quit 0 Quit 0 Quit 0 Quit 0 Quit
2 2 2 Select 2 Select 2 Select
3 Alarms 3 3 3 3
4 ListNEs 4 Ports 4 Update 4 Update 4 Update
5 5 ListAlms 5 ListAlms 5 ListAlms 5 ListAlms
6 PerfMon 6 AlmRpt 6 AlmRpt 6 AlmRpt 6 AlmRpt
7 7 7 7 7
8 8 8 8 8
9 9 LstNodes 9 9 9
10 Protectn 10 Routes 10 10 10
11 11 11 11 11
12 12 12 12 12
13 JackAcc 13 13 13 13
14 14 14 14 14
15 Equipmnt 15 15 DtlPort 15 DtlPort 15
16 Facility 16 16 16 16
17 Admin 17 17 17 17
18 Help 18 Help 18 Help 18 Help 18 Help
Figure 1-7
Equipment menus (sheet 1 of 3)
DS1
CS Nodes
DS1 Equip AlmProv
0 Quit
2 0 Quit 0 Quit
3 Alarms 2 Select 2 Select
4 ListNEs 3 Query 3
5 4 4
6 PerfMon 5 ListAlms 5 ListAlms
7 6 AlmRpt 6 AlmRpt
8 7 7
9 8 ChgState 8
10 Protectn 9 9
11 10 DtlProt 10
12 11 11 EditStat
13 JackAcc 12 12
14 13 Add 13
15 Equipmnt 14 Delete 14
16 Facility 15 15
17 Admin 16 Facility 16
18 Help 17 AlmProv 17
18 Help 18 Help

Figure 1-8
OPC CRVLC/VPLC
CS Nodes OPC Equip LC Equip
2 2 Select 2 Select
3 Alarms 3 Query 3 Query
4 ListNEs 4 4
5 5 ListAlms 5 ListAlms
6 PerfMon 6 AlmRpt 6 AlmRpt
7 7 7
8 8 ChgState 8 ChgState
9 9 9
10 Protectn 10 10
11 11 11 Next
12 12 12 Diagnose
13 JackAcc 13 Add 13
14 14 Delete 14
15 Equipmnt 15 15
16 Facility 16 16 ResetLC
17 Admin 17 17 AlmProv
MIC TIC AIC
MIC Equip TIC Equip AIC Equip

2 2 Select 2 Select
3 Query 3 Query 3 Query
4 4 4
5 ListAlms 5 ListAlms 5 ListAlms
6 AlmRpt 6 AlmRpt 6 AlmRpt
7 7 7
8 ChgState 8 ChgState 8 ChgState
9 9 Switch 9
10 Ordwire 10 10
11 11 11
12 Diagnose 12 Diagnose 12 Diagnose
13 13 Add 13 Add
14 14 Delete 14 Delete
15 15 EditAINS 15 EditAINS
16 16 Facility 16
17 AlmProv 17 AlmProv 17 AlmProv
OW Equip Shelf Equip Edit Shelf AlmProv

0 Quit Shelf 0 Quit 0 Quit 0 Quit
2 2 2 2
3 3 3 3
4 4 4 4
5 5 Inventry 5 Location 5 ListAlms
6 6 ListCpks 6 ShPos 6 AlmRpt
7 7 LampTest 7 Function 7
8 8 BackupDB 8 8
9 9 Restore 9 9
10 EditSID 10 Restart 10 TimeZone 10
11 11 Edit 11 ClockSrc 11 EditStat
12 12 12 12
13 13 13 13
14 14 14 14
15 15 ACO 15 15
16 16 Exercise 16 16
17 17 AlmProv 17 17
Figure 1-9
PROC TAC
CS Nodes PROC Equip
TAC Equip
0 Quit 0 Quit
2 2 Select 0 Quit
3 Alarms 3 Query 2
4 ListNEs 4 Restart 3 Query
5 5 ListAlms 4
6 PerfMon 6 AlmRpt 5 ListAlms
7 7 DataSync 6 AlmRpt
8 8 ChgState 7
9 9 Switch 8 ChgState
10 Protectn 10 9
11 11 RexEna 10
12 12 Diagnose 11
13 JackAcc 13 Add 12 Diagnose
14 14 Delete 13
15 Equipmnt 15 EditAINS 14
16 Facility 16 Exercise 15 EditAINS
17 Admin 17 AlmProv 16
18 Help 18 Help 17 AlmProv
18 Help

Figure 1-10
Administration menus (sheet 1 of 2)
NE Profile
CS Nodes NE Profile NE Schedule Edit Sched

2 2 2 2
3 Alarms 3 3 3
4 ListNEs 4 4 4
5 5 5 5 Frequncy
6 PerfMon 6 6 6 StrtTime
7 7 7 7 StrtDate
8 8 8 8 EndTime
9 9 NeName 9 9 EndDate
10 Protectn 10 10 10
11 11 11 Edit 11
12 12 12 12
13 JackAcc 13 Schedule 13 13
14 14 14 14
15 Equipmnt 15 15 15
16 Facility 16 Logs 16 16
17 Admin 17 17 17
Log Utility
0 QuitLogs
2 ListLogs
3 Open
4 Current
5 Forward
6 Back
7 First
8 Last
9 Start
10 Stop
11 ClearLog
12 Format
13 ListReps
14 ListDevs
15 StartDev
16 StopDev
17
18 Help
Figure 1-11
Administration menus (sheet 2 of 2)
Ports 1, 2
CS Nodes Ports Stats UI Port Edit UI
2 2 2 Select 2 Select
3 Alarms 3 Query 3 Query 3 Query
4 ListNEs 4 4 4
5 5 5 5 BaudRate
6 PerfMon 6 6 6 Parity
7 7 7 7 CharSize
8 8 8 ChgState 8 StopBits
9 9 9 9
10 Protectn 10 10 10
11 11 11 Edit 11
12 12 DtlProt 12 12
13 JackAcc 13 Add 13 13
14 14 Delete 14 14
15 Equipmnt 15 15 15
16 Facility 16 16 16
17 Admin 17 17 17
Port 6 Ports 3, 4
Tel Output TBOS Port Edit TBOS
4 4 4
5 5 5 Status
6 Operate 6 6 Display
7 Release 7 7
8 8 ChgState 8
9 9 9
10 10 10
11 Edit 11 Edit 11
12 12 12
13 13 13
14 14 14 DelDisp
15 15 15
16 16 16
17 17 17
Port 5
Edit Output Tel Input Edit Input
4 4 4
5 Status 5 5 Status
6 Display 6 6 Severity
7 7 7 SvcImpct
8 Byte 8 8 Descript
9 Bit 9 9
10 Descript 10 10
11 11 Edit 11
12 12 12
13 13 13
14 DelDisp 14 14
15 15 15
16 16 16
17 17 17

Figure 1-12
Help menu
CS Nodes Help
0 Quit 0 Quit
2 2
3 Alarms 3
4 ListNEs 4
5 5
6 PerfMon 6
7 7
8 8
9 9
10 Protectn 10
11 11
12 12
13 JackAcc 13
14 14
15 Equipmnt 15
16 Facility 16
17 Admin 17
18 Help 18

2-1
OPC character-mode user interface 2-

This chapter introduces the OPC Character Mode Terminal (CMT) user
interface. If you are using the OPC graphical user interface, refer to Chapter 3.
Logging in to the CMT environment

This section describes how to log into the CMT environment. The
administrator will set up a user ID and password for you.
For HP host systems

Once the system starts, it displays a login prompt.
Step Action
1 Type your userID after the login prompt and press Enter.
2 Type your password after the password prompt and press Enter.
Note: The password does not appear in the field as you type it. Do
not use capital letters unless the capitalization is part of the
password, because the system treats uppercase and lowercase
letters differently.
3 Type OPCUI and press Enter.
2-2 OPC character-mode user interface
For Sun host systems

Once the system starts, the cursor is placed at the beginning of the User_ID
field prompting you to enter your userID and password.
Step Action
1 Type your userID in the User ID field.
2 Tab to the Password field and type in your password.
3 Tab to the OK button and press Return.
Result: The User Session Manager appears, containing your

authorized tools and toolsets.
Note: The password does not appear in the field as you type it. Do
not use capital letters unless the capitalization is part of the
password, because the system treats uppercase and lowercase
letters differently.
4 Type OPCUI and press Enter.

User Session Manager

The User Session Manager (shown below) is similar to a main menu. It opens
automatically when you log on and displays the tools (grouped in toolsets) that
are available to you as well as the tools that have already been opened. From
here, you can open and access your tools. Whenever you return here, you see
the current status of your session.
A session is defined as all interaction between you and the system from the
time you log in until the time you log out.
The User Session Manager lets you control your movement among tools.
List of available
tools
Disabled icon
List of open
tools
Logout button
In the User Session Manager window shown above, there are several toolsets
available for use. Toolsets with a disabled icon in front remind you that the
toolset cannot be selected.
There are also a number of tools that have already been opened. These tools
are shown under the Open tools list, and represent an instance of the tool.
Note: In a session, you can open more than one instance of the same tool.
However, when you reach the maximum number of instances allowed for
a particular tool, no further instances of that tool are allowed and a disabled
icon displays in front of the tool in the Available tools list.
Status icons
Status icons appear in the title bar of the main window, beside a list item, or
beside a command in a history field.
Title bar of main window

The following is a list of the status icons that can appear in the title bar of a
window:
OK >•
Busy ><
Error >X
Printing >>
Major Alarm !M
Critical Alarm *C
Minor Alarm !m
List item and history field

The following is a list of the status icons that can appear beside a list item or a
command in a history field:
OK >•
Error >X
Printing >>
Contains data +
Contains data in error +X
Contains data pending +<
Contains no data —
Major alarm !M
Critical alarm *C
Minor alarm !m
Busy ><
Background command >&
Foreground command >@

Moving through the CMT user interface

To navigate through the CMT environment, you can use either the keypad or
the keyboard combination equivalent.
Using the keypad

The keypad lets you perform basic operations quickly.
CS-10235
CS-10235
PF1 PF2 PF3 PF4

Window... Drag... Abort
(no save)
7 8 9 -
Home Previous Next End
(and save)
4 5 6 ,
Step Jump Window Tool
scroll... scroll... menu menu
1 2 3 Enter
Drag Global Chooser/
menu List menu List item
Select menu
to here...
Field
0 . menu
Select Multiselect
Button
Choose menu item menu
Keys shown with ellipsis (...) require the use of other keys to activate their
functions:
• The Scroll, Select to here, and Drag keys must be followed by arrow keys.
• The Window key must be followed by the Next or Previous key.
Using the keyboard

If your terminal does not have a keypad—or your keypad cannot be used in this
way—you must use keyboard combinations for all operations.
Keyboard strokes are often preceded by either a Control key or an Escape key.
When you use the Control key as part of a keyboard combination, hold the
Control key down while you press the other key—an underscore, as in Ctrl_T,
denotes this hold-and-press action. If you use Ctrl_T plus another key (such as
Ctrl_T plus 0), you hold the Control key down while you press T, next you
release both the Control and T keys, then you press the 0 key.
When you use the Escape key (represented as a black ◊ in menus and on action
buttons to indicate a shortcut) as part of a keyboard combination, press the
Escape key, release it, then press the other key. A space, as in Esc H, indicates
this press-and-release action.
Using the Keyboard
KBD Item Down Item Left Item Right

Figure 2-1
Set-Up On Line Local Locked L1 L2 L3 L4 Scroll Scroll Scroll

Cas- Cas-
Item Up cade cade
Scroll Parent Menu
Esc ! Recall @ (Macro) # $ % ^ & * ( Open ) Close _ + New ~ Back Break

1 2 3 4 5 6 7 8 9 0 - = . Space
Abort
Escape { }
Using the keyboard
Tab Back Tab Q Quit W E R T Tool Y U I User O P Print { } Delete

or Previous Window / Shortcuts Modify Shortcuts
Object
[ ] Cancel
Dialog Pane Resize Tool Select Tab or Object;
Tab or next object X-On Mode On Mode On Mode On / - Start Next Object Home Escape End
Ctrl Caps A Select S Save D (Dupli- F Find G Tool H Help J K L : Sort " Return OK | Again
All cate) Next Shortcuts Home / ; ' \
Lock
Select / Scroll Delete Left Item New Line Quiet
Select Start X-Off Mode On or Left Mode On Menu Character Character
No Shift Z X Cut C Copy V Paste B N M < > Refresh ? Help Shift Line
, . Screen /
Scroll Feed
Previous New Line
Drag Object Character Help
Legend:
Function

Shortcut assigned to key;
use after escape key (example, Esc H);
H Help case sensitive for keys with two symbols
Delete Left (example, use Esc ( to open, not Esc 9)
or Item Left
Control function assigned to key;

use with control key (example, Ctrl_H);
case sensitive for keys with two symbols
(example, use Ctrl_^ to abort, not Ctrl_6)
CS-10236
CS-10236
Moving the cursor

Before you perform any action, you must find out where the cursor is on the
screen and how to navigate from object to object (such as from a list to a field
or a button), within objects (as in a menu or a list), and how to return to the
home object.
To move... Use...
from object to object Tab or Keypad 9 (for next object);
Ctrl_B or Keypad 8 (for previous object)
within an object up, down, left, and right arrow keys
home Ctrl_P or Keypad 7
Exiting or canceling a mode

You will sometimes find yourself in a mode—such as scrolling, dragging
(moving a dialog), and resizing (enlarging or shrinking a window or dialog).
• To abort: To exit from any mode and ignore the changes that you have
made while you were in that mode, press Keypad PF4 or Ctrl_^ or Esc Esc.
• To end: To exit from any mode and save the changes that you have made
while you were in that mode, press Keypad — or Ctrl_].
Using tools
Every session begins at the User Session Manager window. To manage a
session, you need to know how to do a few things:
• opening a tool
• returning to the User Session Manager
• accessing an open tool
• refreshing the screen
• moving from one open tool to another
To perform procedures effectively, it is important that you are familiar with the
OPC user interface. Figure 2-2 shows a brief summary of the keyboard
conventions used with the VT100-compatible user interface.
Figure 2-2
Character-mode interface conventions
FW-21118A
Starting your session

The session manager opens automatically when you log in,
and it displays the current status of the session.
To open a tool
Move your cursor down the FW-21118
Available tools list to the tool
> . User Session Manager : admin
you want and then select it
(Keypad 0 or Ctrl_A).
Available tools Open tools
The main window for that tool opens. Toolset/Tools ID State Tool
Software Admin 2 > . OK OPC Status : Primary/Active
Reboot/Load Manager 3 >. OKEvent Browser
Backup/Restore Mngr
Event Browser
To access an open tool NE SW Delivery Mngr
Move your cursor down the Network Upgrade Mngr
OPC Amin
Open tools list to the tool Group and User Setup
you want, and then select it Remote OPC SW Inst.
OPC Save and REstore
(Keypad 0 or Ctrl_A). OPC Shutdown
OPC Date
or Unix Shell
Network Admin
Press Ctrl_T, followed by the ID Remote Telemetry
Utilities
of the tool ( for example, Ctrl_T 3 to
[ Logout ]
access the Event Browser tool).
C 0 M 0 m 1 w 2 FailProt 0 Lckt 0 ActProt 0 PrfAlrt 0 10:59
The main window for the tool opens.
To move through the tools

Press Ctrl_T + or - and continue to press
+ or - until you reach the tool you want.
To refresh the screen

Press Ctrl_T, then a period (that is, Ctrl_T.)

Figure 2-3 shows a summary of the cursor movement keys.

Figure 2-3
Cursor movement keys
CS-10237
Moving the cursor

• from object to object (example, from a button to a field, or a field to a list item)
PF1 PF2 PF3 PF4

CS-10237
7 8 9 - Tab Q W E
Back Next Next
4 5 6 , Ctrl A S
OR
1 2 3 Enter Z X C V B
0 .
• within an object (example, from list item to list item, or menu item to menu item).
Figure 2-4 shows a summary of the object selection keys.

Figure 2-4
Object selection keys
CS-10238
Selecting an object
• a button (selecting a button activates it)

CS-10238
• a list item
PF1 PF2 PF3 PF4
7 8 9 - Tab Q W E
4 5 6 , Ctrl A S
OR
1 2 3 Enter Z X
0 .
Opening a tool
To open a tool, you must be in the User Session Manager window. Move your
cursor into the User Session Manager window, if necessary, by pressing the
Tab key. Then, move your cursor (using your arrow keys) down the Available
tools list to the tool you want and select it (Keypad 0 or Ctrl_A).
For example, if you select the Event Browser tool, the OPC displays a screen
similar to the following.
Returning to the User Session Manager

To return to the User Session Manager anytime during the session, press Ctrl_T
plus 0 (0 is the permanent window ID of the User Session Manager).
The tool you were in before returning to the User Session Manager does not
close and remains active.
Accessing an open tool

To access any of the tools in the Open tools list, use the Tab key to move your
cursor with the arrow keys to the tool you want, and select it (Keypad 0 or
Ctrl_A).
Another way to access any of the tools is as follows:
Step Action
1 Note the ID of the tool instance (see the ID column in the Open
tools list for the number).
2 Press Ctrl_T followed by the ID of the tool.

Refreshing the screen

Under certain circumstances, the screen might become garbled. If this occurs,
refresh the screen by pressing Ctrl_T, then a period (that is, Ctrl_T .).
Moving from one open tool to another

You can get to another tool a number of ways:
• Press Ctrl_T followed by the ID of the tool.
• Press Ctrl_T followed by + (to get to the next tool) or - (to get to the
previous tool).
Using the main window

The first window of a tool is called the main window. It has a title bar across
the top, that has a tool status indicator, the name of the tool, and a tool menu.
The main window of the tool shown below contains a list of alarms.
The tool status indicator tells you whether or not the window is ready to be
used. A >• symbol means the window is ready for use.
Tool name Tool menu
Title bar
Status indicator
List
Window
border
Status line
Closing a tool
When you are finished with a tool such as in the following example, choose
Exit from the window menu (Keypad 6) of the main window.
Window
menu
Using menus
Each tool has an assortment of menus, as follows:
Window menu
Tool menu
Global menu
List menu
Background
menu
Keyboard shortcut

Displaying a menu
As shown in Figure 2-5, the keypad allows you to access specific menus.
Figure 2-5
Menus accessed by the keypad
CS-10235
PF1 PF2 PF3 PF4

Window... Drag... Abort
(no save)
7 8 9 -
Home Previous Next End
(and save)
4 5 6 ,
Step Jump Window Tool
scroll... scroll... menu menu
1 2 3 Enter
Drag Global Chooser/
menu List menu List item
Select menu
to here...
Field
0 . menu
Select Multiselect
Button
Choose menu item menu
Table 2-1 shows you the different types of menus and how to display them
using the keypad or keyboard.
Table 2-1
Displaying different types of menus using the keypad or keyboard
Type Function Keypad Keyboard

command command
Window menu provides a menu of commands that Keypad 6 Ctrl_L plus W

affect the window (for example, Exit)
Tool menu provides a menu of commands that Keypad , Ctrl_L plus T

affect the tool as a whole
List item, field, provides a menu of commands that Keypad Ctrl_L

and button affect an object in the window Enter
menus
List menu and provides a menu of commands that tab to a list tab to a list or a
chooser menu affect a list as a whole or a field, field, then
Valid data entries for a field are then press press Ctrl_L
shown on a chooser menu. Keypad 3 plus /
Background provides help for the window or Keypad 2 Ctrl_L plus +

menu dialog area
Global menu gives you quick access to all the Keypad 2 Ctrl_L plus G
menus available to you. That is, you
are provided with a list of the menus
based on the position of your cursor.
• To move up or down in a menu, use the arrow keys.

• To move into a cascaded menu, press the right arrow key.
• To move back from the cascaded menu, press the left arrow key.
• To exit from a menu, press Keypad PF4 (Abort) or Ctrl_^.

Menu mode
Displaying a menu puts you in menu mode. Once in menu mode, you can:
• choose the menu item
• go to the previous or next menu in the hierarchy for this object
• go to a specific menu
• go to the cascaded menu (if there is one)
Note: Note that keyboard shortcuts are provided for some menu
commands. To use a shortcut, press the Esc key (represented as a black ◊
on the menu) and the letter associated with the command.
To abort: To exit from any mode and ignore the changes that you have made
while you were in that mode, press Keypad PF4 or Ctrl_^ or Esc Esc.
To end: To exit from any mode and save the changes that you have made while
you were in that mode, press Keypad – or Ctrl_].
Table 2-2 lists the different modes and the effects of the End and Abort
commands on them.
Table 2-2
Menu modes and effects of End and Abort
Mode End Abort
Drag (moving a dialog) dialog will remain at the dialog returns to its original
current position position
Menu (equivalent to not applicable closes the menu but does not
choosing an item) select the item
Resize (command pane) command pane keeps the command pane returns to its
current size change original size
Scrolling view remains as is view returns to its original

place
Select (for multi-select or item or object stays returns to the previous
text) selected selection
Window/dialog current window/dialog returns to initial the

stays in view window/dialog
Scrolling
When a window, dialog, scrolling field, or list cannot fully display its contents,
a view bar displays.
Scrolling view
bar
The view bar represents the size and location of the current view in relation to
the whole object. For example, the view bar in the main window indicates that
the information currently displayed is only a portion of the information
available.

To scroll (using the keyboard)

Once the cursor is in the text field in which you want to scroll:
Step Action
1 Enter scroll mode: Ctrl_F.
2 Choose the amount of scroll you want:

• by steps (line by line; default), press: 1 or period
• by half jump (half of the scroll area), press: 2 or colon
• by a full jump (whole scroll area), press: 3 or vertical bar
3 After setting the scroll amount, use the arrow keys to scroll.
• for vertical scrolling, use up and down arrow keys.
• for horizontal scrolling, use left and right arrow keys.
To scroll (using the keypad)

Once the cursor is in the text field in which you want to scroll:
Step Action
1 Enter scroll mode and amount at the same time:

• by step, press: Keypad 4
• by full jump, press: Keypad 5
2 After setting the scroll amount, use the arrow keys to scroll:
• for vertical scrolling, use up and down arrow keys
• for horizontal scrolling, use left and right arrow keys
Experiment with the scrolling. When you are finished, scrolling can be either
ended (where you remain at the current cursor position) or aborted (where you
return to the cursor position you were in before you began scrolling).
• To end, use Keypad – or Ctrl_].
• To abort, use Keypad PF4 or Ctrl_^.
Using lists
Lists allow you to select things for processing.
There is a menu for the list and for each list item. Commands on the list menu
affect the list as a whole. The commands on the list item menu apply to an item
(or items). Inactive commands have a disabled icon beside them.
List menu
List item
List item menu
Disable icon
Processing a single list item

To process a single list item, perform the following:
Step Action
1 Move the cursor to an item and select it by pressing Ctrl_A

(or Keypad 0)
2 Display the list item menu by pressing Ctrl_L (or Keypad Enter).
The menu shows what can be done with the selected item.
3 Move the cursor down to the command you want. For example, if
you want to delete an item; then choose Delete this item by
pressing Space (or Keypad 0).
The selected item is deleted.

Working with the list as a whole

Although your cursor is on a list item, you can work on the list as a whole. Try
this procedure on the list.
Step Action
1 Display the list menu by pressing Ctrl_L_/ (or Keypad 3).
2 Use the arrow keys to move to the menu item you want to select.
3 Press Space (or Keypad 0 ) to select the menu item.
Using dialogs
Dialogs are subsidiary windows associated with a window. They appear in
front of the tool in which they belong. This particular dialog, Alarm Details,
displays detailed information about a particular alarm. It appears on top of the
Alarm Monitor.
FW-20306
Alarm Details
Alarm #: 349 Major

Unit: DS1 G2 14 SA
Address: 33 CLLI Shelf 1 19:22:55
Location: Frame Frame Name ShPos 1 Slot 3 29 Mar 92
Reason: Rx loss of signal Facility
Facility ID: CLFI
[ D
Done Return]
Moving a dialog
The main window cannot be moved because a window occupies the whole
screen. However, the dialog can be moved so that it is positioned where you
would like it. To move a dialog box, perform the following procedure:
Step Action
1 Enter the drag mode by pressing Ctrl_Z (or Keypad 3).
2 Set the drag rate—press keyboard 1 (for 1 line or 2 characters),

keyboard 2 (for 2 lines or 5 characters) or keyboard 3 (for 5 lines
or ten characters).
3 Use the arrow keys to move left, right, up or down, as required.

(Because of the size of this dialog, you can move it to the right and
left only.)
4 When the dialog is where you want it, exit the mode (Keypad — or
Ctrl_]) or, if you want to restore it to its original position, abort the
mode by pressing Ctrl_^ (or Keypad 4).

Moving from dialog to dialog

To navigate between dialogs, perform the following steps:
Step Action
1 Press the window/dialog key Ctrl_W (or Keypad 2 ) to enter the

window/dialog mode.
2 Press + (to go to the next dialog) or - (to go back to the previous

dialog) or h (to go to the home window).
3 When the window/dialog you want is on top—in this case, the Set
an Alarm dialog—exit the mode by pressing Ctrl_]
(or Keypad –).
Note: Another way to return to the initial dialog is to abort the

mode by pressing Ctrl_^ (or Keypad 4).
Closing a dialog
To close the dialog, tab to the Cancel or OK button and select it by pressing
Keypad 0 or Ctrl_A.
Getting help
Online Help is available for all windows, dialogs and objects in them.
• For help on objects, choose Help from the list, list item, field, and button
menus.
• For help on windows and dialogs, choose Help from the window or
background menu.
Open the dialog menu by pressing Keypad 6 or Ctrl_ L plus W, and choose
Help (Keypad 0 or Space). Help appears in a dialog, as follows.
Help types
Done button
Four types of help are available for the Alarm Monitor window, as indicated
by the buttons at the bottom of the window. Concepts, Commands, Navigation,
and Help on Help are always provided; other types (such as Procedures) may
or may not be provided.
When the Help dialog first appears, it displays Concepts Help, which gives
you a general explanation of the purpose of the object (in this case, the Alarm
Monitor window).
To see one of the other types of Help, you select the appropriate button.
• Commands Help describes the effects of commands on the object.
• Navigation Help tells you how to use menus, move around the screen,
manage the session, and scroll.
• Procedures Help tells you how to perform tasks with a tool.
• Help on Help documents the use of the Help dialog.

Move the cursor to Help on Help (by using the Tab key move to the group of
radio buttons, then the arrow keys to move among the buttons) and select it
(Keypad 0 or Ctrl_A). Notice that the content of the Help dialog changes.
If you were to ask for Help on another object, the content of the help dialog
would change again, showing Help for that object.
You could close the Help dialog by tabbing to the Done button and selecting it
(Keypad 0 or Ctrl_A).
Entering information into fields

The Network Element Commissioning Data dialog is used to set up an HDT
with essential data.
Field
Chooser
Radio
buttons
Fields
The “>” in front of a field name means that it is a mandatory field. A cursor
will appear.
Choosers
Choosers allow you to select a preset value from a menu. Display the chooser
menu by pressing Keypad 3 or Ctrl_L plus /.
Scrolling fields
Scrolling fields (not shown in this example) allow you to type in several lines
of information.
To use a scrolling field, tab to the field and type the desired message. When
you get to the edge of the box, the text wraps to the next line. When the box is
full, it scrolls downwards and a vertical view bar appears.
Radio buttons
Radio buttons allow you to select only one of a set of options. When you select
a radio button, your previous selection is turned off.
These radio buttons let you choose whether the HDT has an OPC, and if so,
whether the OPC is the primary or backup. A black diamond appears between
the brackets when the item is selected.

Check boxes
Check boxes allow you to turn options on or off. More than one option can be
active at a time.
Action buttons
Action buttons tell the system to do something. Inactive buttons are displayed
with the disabled icon preceding the label.
Did you make an error?

If you make a mistake, a message is displayed. For instance, if you did not fill
in a required field and tried to close the dialog, a message similar to the
following would be displayed
.
The status indicator on the main window changes to an >X and the mandatory
icon (>) beside the Time field changes to an X to indicate an error.
You must respond to the message by selecting the OK button (Keypad 0 or

Ctrl_A). If you try to return to the dialog without responding, you will not be
able to enter the window/dialog mode.
Editing text
The following describes some of the text editing capabilities in the tools.
Basic editing
If you want to insert text, or delete a few characters, position the cursor where
you want to edit. You can insert text, or use the delete or backspace keys to
delete.
Selecting text
To move, copy, or delete larger blocks of text, you must select the text first
before you can use the editing commands. To select text, move the cursor to
the text field you want to select, press Keypad Enter or Ctrl_L to display the
Field menu, then choose Select All.
If you want to change the selection, you can use your arrow keys.
Cutting and pasting text

Once the text has been selected, press Esc followed by X to cut the selected text
(or display the field menu and choose Cut).
To paste the text, position the cursor at the beginning of the field (where it is
to be pasted). Then press Esc followed by a V (or display the field menu and
choose Paste).
Copying and replacing text

To copy and replace text, perform the following:
Step Action
1 You have a choice:

• press Esc followed by C, or
• display the field menu and choose Copy instead of Cut.
2 Press the Select to here key (Keypad 1 or Ctrl_Z).
3 Using the arrow keys, go to the beginning of the field to where you
want the text replaced.
4 Press Esc followed by V to paste.

Editing shortcuts
The following is a list of the basic editing commands as well as some
miscellaneous commands. (Remember that shortcuts can only be used when
the menu is not displayed.)
Short cut Description
Esc A Select all
Esc X Cut
Esc C Copy
Esc V Paste
Backspace or Del Delete backward
Esc ( Open
Esc ) Close
Esc Return OK
Esc Del Cancel
Esc H or Esc ? Help
Closing a tool
When you are finished with a tool, open the window menu (Keypad 6 or Ctrl_L
plus W) and choose Exit to close it.
Logging out
When you close a tool, you return to the User Session Manager.
Logout
To log out, tab to the Logout button and select it (Keypad 0 or Ctrl_A). A
message box appears, asking you to confirm your selection.
If you select the Cancel button, the log out command is canceled.
If you select the Logout button, you are logged out. All open windows are
closed automatically. If there are any unsaved changes in a window, a dialog
is presented asking whether to save changes before closing, or whether to
cancel the logout command.
Tab to the Logout button and select it (Keypad 0 or Ctrl_A).

Using UNIX
The following items are described for UNIX systems.
UNIX command strings

The UNIX command string that is entered at the OPC user interface is printed
in bold type, followed by a (↵) Return or Enter symbol, as follows:
more /etc/services↵
Each command string must be typed exactly as shown (including spaces) and
end by pressing the Return key. If a command string shows characters in
uppercase letters, enter these characters in uppercase on your keyboard. All
UNIX commands are case sensitive.
If the command string continues onto a second line, ellipsis (…) are shown at
the end of the first line to indicate a space and not to press Return. Press the
Return key only when you see the ↵ symbol in the instructions.
Variable parameters are enclosed by angle brackets. An explanation of the

variable including a range of values is included immediately after the
command string, as follows:
more <file>↵
where... is the...
<file> name of the file to display
System prompts and responses are printed and capitalized as they appear on
the screen, as follows:
Password:
The result of an action is shown in italic type, as follows:
The alarm screen is displayed.
Common UNIX commands

Table 2-3 shows the UNIX commands that you will use most often.
Table 2-3
Common UNIX commands
Command Description
ls, ll Lists the files in the current directory.
opcui Starts the OPC character-based user interface.
more <file> Displays the specified file, pausing every 22 lines.
cd <dir> Changes the current directory to <dir>.
cp <orig> <dest> Copies the file <orig> to the location <dest> (which can be a
directory or a complete file name).
mv <orig> <dest> Moves (or renames) the file <orig> to the location <dest> (which
can be a directory or complete file name).
vi <file> Opens the specified <file> in the standard UNIX text editor. See
“UNIX editor (vi) quick reference” on page 2-31 for a brief
description of the text editor.

UNIX editor (vi) quick reference

The vi text editor can be used in the UNIX environment to edit OPC files. This
section provides a brief vi guide, which is adequate for OPC administration.
The vi editor has many more commands and capabilities. For more
information, consult a book such as An Introduction to Display Editing with Vi,
by W.M. Joy and M. Horton, or vi Command and Function Reference, by
A.P.W. Hewett and M. Horton.
The vi editor has two basic modes: command mode and insert mode. Letters
typed in command mode execute the commands listed in Table 2-4. Letters
typed in insert mode are added as text. To enter the insert mode, type a or i. To
return to command mode, press the Esc key.
Table 2-4
Common actions in vi
Function Action Command
managing files open a file vi [filename] ↵

save a file :w [filename] ↵
quit :q ↵
save a file and quit :wq ↵
quit, without saving changes :q! ↵
moving around up/down 1 line up/down arrows

left/right 1 character left/right arrows
inserting text append text after the cursor a

insert text before the cursor i
open new line below current line o
end insertion, return to command mode ESC
deleting text delete character x

delete line dd
finding text search forward /<text> ↵

find next instance n
find previous instance N
copying text copy lines to temporary storage [number of lines]Y

paste copied lines below current line p
other commands undo last change u

3-1
OPC graphical user interface 3-

This chapter introduces the OPC graphical user interface.
If you are using a character-mode (VT100 type) terminal with your OPC, refer
to Chapter 2.
Logging in
When the system starts, it displays a message which asks for your name and
password. All workstation users must have their own user names (user IDs)
and passwords. If you do not know yours, consult your system administrator.
Enter your user ID and password in the appropriate fields. Your password is not
displayed in the field when you enter it. Do not use capital letters unless the
capitalization is part of the password, as the system treats capitals and lower
case letters differently. You can use the mouse or your Tab key to move
between fields.
When you have finished, press Return, or click Select on the OK button. If you
have successfully logged in, a grey workspace appears, with toolset icons at
the top left.
If you make a mistake, the system asks you to try again, displaying the
following message.
FW-21158
FW-21158
Login incorrect
OK Return
Click on OK with the Select button of your mouse. Both fields are cleared, and
you must reenter both your userID and password correctly.
3-2 OPC graphical user interface
There is a limit to the number of attempts you can make at entering your
password after which the following message appears.
FW-21159
FW-21159
You have exceeded the permitted number

of sign on attempts.
Please consult your administrator.
OK Return
If this happens, the system administrator must log in as the root user and reset
the system’s record of invalid login attempts before you will be able to try
again.

Moving through the graphical interface using the mouse and

keyboard
Both the mouse and the keyboard can be used to perform any operation.
Using the mouse

The mouse is a small plastic box with two to three buttons on it, attached to
your workstation by a cord and sitting on a pad. As you move the mouse, the
pointer on the screen moves with it.
Figure 3-1
Mouse buttons
FW-20044
Select
Modify
Menu
Note: For an optical mouse to work properly, the pad should be aligned so
that the long sides are at the top and bottom. (An optical mouse has an LED
on its underside.)
Select Use the Select button (usually the left mouse button) to select items,
by pressing and releasing it.
Modify Use the Modify button (usually the center mouse button) to modify
selections.
Menu Use the Menu button (usually the right mouse button) to display a menu
of commands, or a choice of values. Move the pointer to a specific place on the
screen, press and hold down the right mouse button, move the pointer to the
menu item you want and release the button.
The Select, Modify and Menu buttons also have window manipulation
functions, described in “Using the workspace” on page 3-5.
Using the keyboard

Keyboard strokes are often accompanied by either a Control, Alt, or Shift key.
Note: On the HP 9000 keyboard, the Alt key is labeled “Extend char.” On
some Sun keyboards, it is labeled “Left” and “Right”, and on others with a
symbol. On NCD X terminals, it is labeled “Alt.”
When you use the Control, Alt, or Shift key as part of a keyboard combination,
hold the Control/Alt/Shift key down while you press the other key; for
example, Ctrl+K denotes this hold-and-press action.

Using tools and toolsets

OPC software is organized into small parts called “tools.” Tools are grouped
into toolsets, which are groups of related tools.
Using the workspace

The workspace is a gray screen with one icon in the top left corner and a
pointer (which looks like an X).
The icon in the top left corner of the workspace represents the training toolset.
Toolsets are collections of tools which allow you to perform tasks.
The workspace menu (see Figure 3-2) enables you to log off the workstation
or redraw the workspace. To display the workspace menu, press and hold the
Menu mouse button while the pointer is on the workspace background.
Figure 3-2
Workspace menu
FW-20243
FW-20243
Workspace Menu
Refresh Workspace
Logout
Help
The following options are available:
Option Description
Refresh Workspace Redraws the entire workspace.
Logout Logs you out of the workstation. A dialog asks you to confirm
your intent:
FW-21157
FW 21157
Logging out will close all windows.

Logout Cancel
Click Logout to end your session, or Cancel to stop the logout

process.
Help Provides online help for each option in the workspace menu.
Displaying a tool in the toolset menu

To display the tools in the toolset menu using the mouse, perform the
following:
1 Move the pointer over the toolset icon.
2 Press and hold the Menu mouse button.
To display the tools in the toolset menu using the keyboard, perform the
following:
1 Tab to the toolset icon.
2 Press F4.
Figure 3-3 shows a toolset icon, with its menu of tools.

Figure 3-3
Example toolset icon

Starting a tool from a toolset menu

To start a tool from a toolset menu using the mouse, perform the following:
1 Move the pointer over the tool you want to start.
The menu item is highlighted.
2 Release the Menu button on the mouse.
After a short delay, the tool opens.
To start a tool from a toolset menu using the keyboard, perform the following:
1 Move cursor with arrow keys to the tool you want to start.
The menu item is highlighted.
2 Press Return.
After a short delay, the tool opens.
Tools can sometimes be started from within other tools. When this happens,
the new tool can inherit context from the previous tool. For example, if you
invoke Help from within another tool, it will give you help on the tool from
which you invoked Help.
Status icons
The status icons listed in Figure 3-4 can appear in the tool’s main window
status area (at the left of the title bar), or beside a list item or field. They
indicate the current state of a tool, list item, or field.
Figure 3-4
Status icons
FW-20202
OK Ready for keyboard or pointer input. No alarm is active.
FW-20202
Error The window contains errors, or the tool has encountered

X an error.
Printing The window cannot accept input because the tool

is printing.
Processing The window cannot accept input because the tool

is processing data, doing calculations, or accessing a disk.
Contains data The item contains data (is not empty).
Minor alarm The window contains information about an

equipment or network alarm of minor severity.
Major alarm The tool contains information about an equipment

! or network alarm of major severity.
Critical alarm The window contains information about

an equipment or network alarm of critical severity.

Closing a tool
To close a tool using the mouse, perform the following:
1 Move your pointer to the file menu, and hold the Menu mouse button.
The file menu appears.
2 Choose Exit.
A dialog appears, asking you whether you want to save the changes you have
made to the tool.
3 Choose Yes or No.
After a short delay, the window and all its associated dialogs closes.
To close a tool using the keyboard, perform the following:

1 Press F10.
The left-most menu on the menu bar appears.
2 Press the right arrow key to move to the File menu.
3 Choose Exit.
A dialog appears, asking you whether you want to save the changes you have
made to the tool.
4 Choose Yes or No.
After a short delay, the window and all its associated dialogs close.
Using the main window

The first window of a tool is called the main window. It has a menu bar across
the top, which contains a tool status indicator, followed by the File menu, any
tool-related menus (optional), and a Help menu.
The tool status indicator tells you what the status of the window is (for
example, whether the window is being used for the task of printing or is in an
error condition). A check mark (√) means that the window is ready for
keyboard or pointer input, and no error or alarm condition is indicated by its
contents.
From the main window, you can access all the tasks available to the tool.
Figure 3-5 shows the main window of our demonstration tool, Alarm Monitor,
with a list of alarms. To open this window, click the Menu mouse button over
the Network Surv. toolset icon, then click the Select button on Alarm
Monitor.
Note: All windows and dialogs are surrounded by a frame. The frame
allows you to manage the screen.
Figure 3-5
Example main window
Status indicator Menu bar Help menu
File menu
Options menu
List
Window
frame

Using menus
Menu bar menus

These are the menus that are provided by the menu bar across the top of every
window. To display the menu bar menus using the mouse, perform the
following:
1 Move your pointer to a menu label, and press and hold the Menu mouse
button.
The menu appears.
2 To display another menu bar menu, move to another menu label.
To display the menu bar menus using the keyboard, perform the following:
1 Press F10.
The left-most menu on the menu bar appears.
2 Press the appropriate arrow key to move to other Menu bar menus.
• To cancel a menu without choosing a command using the mouse, move

your pointer outside the menu and release the Menu mouse button.
• To cancel a menu without choosing a command using the keyboard, press
the Esc key.
The types of menus on the menu bar include the following.
Menu Description
Status indicator This menu is located on the left side of the menu bar.
The label (in the form of a status indicator) shows the
current status of the tool (see “Status icons” on page
3-8). When displayed, the menu contains one entry,
Help.
File This menu is labeled File and is located directly to the

right of the status indicator menu on the menu bar.
Tool (Options and others) One or more tool menus may appear to the right of the
FIle Menu. These menus contain commands that affect
the tool as a whole.
Help This menu is labeled Help and is located on the right

side of the menu bar. When displayed, the menu
contains commands such as Tool overview, Using
Help, Navigation, and Product Information.
Object menus
Every object in the window has a menu, containing commands that affect it.
• To display the object menus using the mouse, move your pointer to the
object and press and hold the Menu mouse button. The menu appears.
• To display the object menus using the keyboard, tab to the object for which
you want to display a menu and press F4. The menu appears.
There are two exceptions when using the keyboard:

• To display a chooser menu, move to the associated field and press Shift+F4.
• To display a list title menu, move to any list item and press Shift+F4.
The types of object menus include the following:
Menu Description
List item menu This menu is located at a list item. This menu contains
commands (such as Select, Deselect, Delete) that affect the
list item chosen.
List menu This menu is located in the heading area of a list. This menu
contains commands (such as Sort and New) that affect the list
as a whole.
Button menu(s) This menu is located in the button area, and contains the Help
command.
Field menu This menu is located within the field area. This menu contains
commands (such as Select, Deselect, Delete) that alter the
text in the field.
Chooser This menu is located under a boxed rectangular label at the

end of a field and contains preselected information.
Background menu This menu is located in the background of dialogs and

windows, and contains the Help command.
Keyboard shortcuts are provided for some menu commands.

Using lists
Lists enable you to select one or more of a number of objects for further action.
Some lists allow only one selection; others allow any number of selections at
once. Lists can have any number of items and can be scrolled to show items
not currently displayed. (Refer to “Scrolling” on page 3-14 for information on
scrolling.)
Lists have a list menu and a list item menu. The list menu provides commands
that affect the list as a whole. List item menu commands affect an individual
item (or group of items). An example list, showing a list menu and a list item
menu, is shown in Figure 3-6.
Figure 3-6
Lists and associated menus
FW-21063
List title
Inactive item
List item
List menu List item menu
• To select one or more list items using the mouse, move the pointer to a list
item and click the Select mouse button. To select more than one list item,
press and hold the Select mouse button and drag.
• To select one or more list items using the keyboard, tab to the list. The first
item is highlighted. Use the arrow keys to move. To select more than one
list item, hold the Shift key and then use the arrow keys.
Table 3-1 lists and describes the standard list item menu commands:
Table 3-1
List item menu commands
Command Description
Open Opens a dialog filled with data about the selected list item.
This command applies only to lists with items that can be
opened, such as lists of data records. You can also use the
keyboard shortcut Alt+O.
Select all Selects all items in the list. You can also use the keyboard
shortcut Alt+A.
Select to here Selects all items in the list up to this point.
Select this item Selects the item that was under the pointer.
De-select this item Cancels the selection of a single item.
De-select all Cancels all selections.
Scrolling
Scroll bars appear when a window (or a scrolling field or list) cannot fully
display its contents. Both vertical and horizontal scroll bars can appear. Scroll
bars have three distinct areas, shown in Figure 3-7.
Figure 3-7
Scroll bar areas
FW-21112
FW-21112
Step-scroll View bar Jump-scroll Step-scroll

left area right
A scroll bar consists of two arrow buttons on either end of a trough and a slider
(or view bar) in the trough. The slider represents the current position and size
of the viewed portion of the data relative to all the data (as represented by the
trough). When the slider totally fills the trough, all the data is visible.

To scroll using the mouse, perform the following:

1 Drag scrolling: Move the pointer to the slider (or view bar), press and hold the
Select mouse button, and drag it until the information you want is visible on
the screen.
2 Step scrolling: Move the pointer to the arrow buttons located at the end of the
trough, and click the Select button.
3 Page scrolling: Move the pointer to the trough on either side of the view bar
and click the Select mouse button to page up or down (or left or right).
4 Direct access scrolling: Move the pointer to the desired place on the trough,
and click the Menu mouse button.
To scroll using the keyboard, perform the following:

1 Page up (or left): Press Page Up (for NCD), Prev (for HP), F29 (for SUN3),
PgUp (for SUN4).
2 Page down (or right): Press Page Down (for NCD), Next (for HP), F35 (for
SUN3), PgDn (for SUN4).
3 Line by line (for lists and multi-line text fields): Press arrow keys to move the
location cursor or text cursor up or down.
Managing the workspace

All windows are surrounded by a frame. The frame allows you to use the
mouse to manipulate the window. Using the frame, you can:
• target a window
• raise and lower a window
• move a window around the workspace
• resize a window
• change a window into an icon (minimize)
• enlarge a window to its maximum size (maximize)
• restore a minimized or maximized window to the previous size and
location of the window
The keyboard can also be used to perform the same window operations. When
using the keyboard, the Alt key is often used. On the HP 9000 keyboard, the
Alt key is labeled “Extend char.” On some Sun keyboards, it is labeled “Left”
and “Right”, and on others with a symbol. On NCD X terminals, it is labeled
“Alt.”
The frame around windows appears as shown in Figure 3-8.

Figure 3-8
Parts of a window frame
FW-21113
Title bar FW-21113
Window frame
menu button Restore Alt+F5
Move Alt+F7
Window frame Alt+F8
Size
menu
Minimize Alt+F9
Maximize Alt+F10
Lower Alt+F3
Raise Alt+F2
Close Alt+F4
Minimize button
Maximize button
Resize borders
Note: The frames around dialogs do not have a title bar, a minimize button,
a maximize button, or a frame menu button. There are also no handle bars
or resize borders.

All the window operations can also be performed using the window frame
menu. Once you have gone through the following sections on window
operations using the pointer and keyboard, you might want to try the window
operations using the menu. If so, note the following:
• To display the window frame menu, click the Select mouse button on the
window frame menu button (if using the keyboard, press Alt+Space).
• To choose the operation you want off the menu, click the Select mouse
button. If you are using the keyboard, use the arrow keys to move to the
operation and then press Return.
Targeting a window
Keyboard input only affects a window (or dialog) when you are focused on that
window.
The window on which you are currently focused is known as the target
window. The target window is indicated as follows: The frame of the window
is grey, while the title bar and the left border of the window is dark. (For
dialogs, the left and top borders are dark.)
To target the windows and dialog one at a time using the mouse, move the
mouse into the desired window. Note how each window takes the focus as you
move the pointer into that window.
Note that when you move the pointer into a window that is partially covered
by another window, that window takes the focus but does not come to the front.
To bring a window to the front, click the Select button in that window’s title
bar. To send a window to the back, click the Menu button in that window’s title
bar.
To target the windows or associated dialogs one at a time using the keyboard,
perform the following:
1 Press Alt+F6 to move from a tool’s main window to its (open) dialogs. Note
that this does not open a new dialog box.
2 Press Alt+Tab to move from main window to main window.

Sending windows forward or backward

Sometimes windows are stacked behind other windows making it necessary to
move the window you want to the front.
For example, to move the Help window to the front using the mouse, perform
the following:
1 Position the pointer on the frame of the Help window.
2 Click Select.
To move the Help window to the front using the keyboard, press Alt+F2.
Remember when you are using the keyboard that the window or dialog that
you want to move to the front must be targeted first.
Note: You cannot raise a main window over any of its dialogs.
You can also send any window or dialog to the back. To send a window or
dialog to the back using the mouse, perform the following:
1 Position the pointer on the frame.
2 Hold down the Shift key and click Select.
To move a window to the back using the keyboard, press Alt+F3. Remember
when you are using the keyboard that the window or dialog that you want to
move to the back must first be targeted.
Moving windows
Both windows and dialogs can be moved about the workspace. To move a
window or dialog, perform the following:
1 Position the pointer anywhere on the frame, then press and hold the Modify
button (the second mouse button).
2 Move the pointer to the left and down.
The dialog moves with the pointer.
3 Release the Modify button when the dialog is correctly positioned.
To move a window or dialog using the keyboard, perform the following:

1 Press Alt+F7.
2 Press the appropriate arrow keys.
The dialog moves in the direction of the arrow keys.
3 When the dialog is correctly positioned, press Return.
Minimizing windows
You can minimize any window into an icon. Minimized windows are still
active and will continue processing.
To minimize the main window into an icon using the mouse, perform the
following steps:
1 Position the pointer on the minimize button of the main window.
2 Click Select.
The window and associated dialogs become an icon and is placed starting in
the bottom left.
To minimize the main window into an icon using the keyboard, perform the
following steps:
1 Press Alt+F9.
The window and associated dialogs become an icon.
2 Move the icon to the left side of the workspace to keep it out of the way. You
can move icons the same way you move windows.
Maximizing windows
You can increase the size of any window to the maximum allowable size.
To increase the size of the Help window to the maximum using the mouse,
perform the following steps:
1 Position the pointer on the maximize button of the help window.
2 Click Select.
The window fills the screen.
To increase the size of the Help window to the maximum using the keyboard,
Press Alt+F10.

Restoring a maximized window

You can restore a maximized window to the previous size and location of the
window.
To restore a maximized window to the previous size and location using the
mouse, perform the following steps:
1 Position the pointer on the maximize button of the help window.
2 Click Select.
The window returns to the previous size and location.
To restore a maximized window to the previous size and location using the
keyboard press Alt+F5.
Restoring a minimized window

You can restore a minimized window to the previous size and location of the
window.
To restore a minimized window to its previous size and location using the
1 Position the pointer on the icon.
2 Double click the Select button.
The main window and its associated dialog return to their previous size and
location.
To restore a minimized window to its previous size and location using the
1 Make certain the icon has focus.
Note: If not, use Alt+Tab until it has focus.0
2 Press Alt+F5.
The main window and its associated dialog return to their previous size and
location.
Sizing a window
You can increase or decrease the size of any window horizontally, vertically,
or proportionally.
To change the size of a window using the mouse, perform the following steps:
1 Position the pointer on the border you want to change (left, right, top, bottom,
or any corner).
The cursor changes shape to indicate the direction of size change chosen.
2 Press and hold the Select mouse button.
3 Now move the pointer in the direction you want to go.
The border of the window follows the cursor.
4 Release the Select button when you reach the desired size.
The sizing stops.
To change the size of a window using the keyboard, perform the following
steps:
1 Press Alt+F8.
The window title bar lightens.
2 Press and hold the appropriate arrow key (for example, if you want to resize
the width of the window, choose the left or right arrow key).
3 Release the arrow key when you reach the desired size.
The sizing stops.
4 Press Return to exit from the resize mode.

Getting Help
Online Help is available for every window and dialog, and for all objects
within a window or dialog.
To obtain Help on a window using the mouse, perform the following steps:
1 Move the pointer to the background menu, and press the Menu mouse button.
The background menu appears.
2 Move the pointer to the Help entry and choose it by releasing the Menu
mouse button.
Note: You can also choose Help from the Help menu at the right-most position
of the Menu bar (which contains <tool> overview, Using Help, Navigation, and
Product Information). For dialogs, there is no Menu bar, so Help is available
only from the background menu.
To obtain Help on a window using the keyboard, press F1.
Help appears at the top right of the screen in a separate window, similar to that
shown in Figure 3-9.
Figure 3-9
Example help screen
FW-21073
Help menu FW-21073
Help for Message Alarm Window

File Help
File Exit Help on Help F1
The Message Alarm tool demonstrates how to use the user
menu interface. Product Information
Help It lets you create reminders to yourself that
pop up on your screen at a specified time.
Every object in the window has a menu associated with it,

which you can display and choose Help.
Use the menu for the Alarm list title bar to create new
alarms, sort the list, and delete old alarms.
Use the menu for any list item to see or change the settings
for any particular alarm.
The Options menu on the window menu bar is a menu of

commands that affect the tool as a whole. Choose Default to
set general characteristics for all your alarms, and choose
Command area if you want to type commands.
When you want to quit Message Alarm, choose Exit from the
File menu on the window menu bar.
Concepts Commands Navigation
When the Help window first displays, it presents Concepts Help. Concepts
Help gives you a general explanation of the purpose of an object (in this case,
the Message Alarm main window). Concepts and Navigation help types are
always provided; other types may or may not be.
To view another type of Help using the mouse, perform the following:
1 Move your pointer to the appropriate button at the bottom of the window.
2 Click the Select mouse button.
To view another type of Help using the keyboard, perform the following:
1 Use the arrow keys to move to the appropriate Help type.
2 Press Return.
Commands Help describes the commands on the menu. (In the case of Help on
an object such as a list menu, Commands Help describes the commands on the
list menu.) Navigation Help tells you how to navigate around the screen, as
well as how to perform basic functions.
To obtain information on how to operate the Help window using the mouse,
1 Move the pointer to the Help menu on the Help window.
2 Choose Help on Help.
To obtain information on how to operate the Help window using the keyboard
(see Figure 3-10), you have a choice:
• Press Ctrl+H
• Press F1
Figure 3-10
Help on help
FW-21075
FW-21075
Help on Help
i This help describes the help window and how it works. It

is displayed in a separate dialog, and can be referred to
as you use or manipulate a help window.
THE HELP WINDOW
The window manager's title bar names the object for which
help is being provided. Beneath the title bar is the menu
bar, which holds the File and Help menus. Next is the
information area; if there is more information than can be
displayed at once, use the scroll bars to scroll the
unviewable text. At the bottom of the window is a listing
of the help types that can be selected.
Done Alt+Return

Help On Help describes the Help window and how it works. It appears in a
separate dialog, and can be referred to as you use or manipulate a Help
window.
To remove the Help on Help information dialog using the mouse, perform the
following:
1 Move the pointer to the Done button.
To remove the Help on Help information dialog using the keyboard, perform
the following:
1 Tab to the Done button.
2 Press Return.
You can close the help window by choosing Exit from its File menu.
Entering information
The NE Commissioning Data dialog is used for setting up an HDT. To open
this dialog, click the Menu mouse button on the SLAT toolset, select
Commissioning Manager from the menu, then click the “Commission New
Network Element” button in the Commissioning Manager window.
Figure 3-11 shows the NE Commissioning Data dialog box.
Figure 3-11
NE Commissioning Data dialog
Field
Radio buttons
Action button
This dialog is filled with fields and buttons, and you must be able to navigate
throughout the dialog to enter information.
To navigate from object to object within a window or dialog using the mouse,
1 Move the pointer to the object.
Note: Clicking the Select mouse button on some objects—such as action
buttons— activates their functions.
To navigate from object to object within a window or dialog using the

keyboard, you have a choice:
• Press Tab
• Ctrl+Tab

Fields
This section describes the major types of fields that accept typed data. “Editing
text” describes how to modify the contents of a field.
Standard fields
Figure 3-12 shows a standard field, and its associated menu.
Figure 3-12
Example text field
FW-21110
Field Menu
FW-21110
Field label field text
Select all Ctrl+/
Deselect all Ctrl+\
Cut Shift+Delete Char
Copy Ctrl+Insert Char
Paste Shift+Insert Char
Delete Ctrl+K
Help Ctrl+H
To move to a field, either click Select on it, or press the Tab key until the cursor
appears there.
To type information into a standard field using the mouse, perform the
following:
1 Move the pointer over the box and click Select.
A pointer, looking like an inverted T, appears in the field.
2 Type the information. You might be able to type more characters than fit in the
box.
If so, the field scrolls automatically to the right so that you can see what you
are typing.
To type information into a standard field using the keyboard, perform the
following:
1 Tab to the field.
A pointer, looking like an inverted T, appears.
2 Type the information. You might be able to type more characters than fit in the
box.
If so, the field scrolls automatically to the right so that you can see what you
are typing.
Fields can be mandatory or optional: mandatory fields are marked with a black
triangle at the left side of the field, and require you to enter information.
Optional fields do not require you to enter information.
Choosers
Choosers enable you to select a preset value from a menu. The box at the right
end of the field is the chooser. Figure 3-13 shows an example of a field with a
chooser, its chooser menu, and the field menu (note that the appearance of a
chooser may vary from system to system).
Figure 3-13
Example chooser
FW-21106
Field Menu Chooser
FW-21106
Field label Option a
Option a
Option b
To display and enter the correct chooser value using the mouse, perform the
following:
1 Move your pointer to the rectangular box.
2 Press and hold the Menu mouse button and choose one of the options.
The option that you have chosen appears in the field.
To display and enter the correct chooser value using the keyboard, perform the
following:
1 Press Shift+F4.
2 Use your arrow keys to move to the option you want, and choose it by
pressing Return.
The option that you have chosen appears in the field.

Scrolling fields
Scrolling fields are much like standard fields, but they allow you to type many
lines of information. Figure 3-14 shows an example of a scrolling field and its
menu.
Figure 3-14
Example scrolling field
FW-21105
Field Menu Scroll bar
Field label FW-21105
Selectbe
Here is some text that might all in a Ctrl+/
scrolling field. Deselect all Ctrl+\
When you type past the border of the
field, a scroll bar appears. You can then
Delete Ctrl+K
Help Ctrl+H
Click Select in the box and start typing. When you get to the edge of the box,
the text wraps to the next line. When the box is full, it scrolls downward to
allow more typing and a scroll bar appears. Scroll bars are described under
“Navigation.”
To move from a scrolling field to another object within the window or dialog
using the mouse, perform the following:
1 Move the pointer to the object.
To move from a scrolling field to another object within the window or dialog
using the keyboard, press Ctrl+Tab.
Buttons
Three different types of buttons are used in the graphical user interface; radio
buttons, check boxes, and action buttons. They look different, and are used for
different purposes.
Radio buttons
Radio buttons allow you to choose one of a set of options. They appear as an
array of labeled diamonds, one of which is highlighted as shown in
Figure 3-15.
Figure 3-15
Example radio buttons
FW-21107
FW-21107
Option A
Option B
Option C
To select a radio button using the mouse, click Select on the radio button that
you want to choose. The diamond beside that radio button is highlighted.
To select a radio button using the keyboard, perform the following:

1 Press the appropriate arrow key to move to the radio button you want.
2 Press Return.
The diamond beside that radio button is highlighted.

Check boxes
Check boxes allow you to activate one or more of a set of options. They appear
as an array of labeled boxes. Active options have check marks in them, as
Figure 3-16
Example check boxes
FW-21108
FW-21108
✔ Option 1
Option 2
To select or deselect a check box using the mouse, Click Select on the box.
If a check mark appears in the box, the option is on. If the check mark disappears from
the box, the option is off.
To select or deselect a check box using the keyboard, perform the following:
1 Press the appropriate arrow key to move to the check box you want.
2 Press Return.
If a check mark appears in the box, the option is on. If the check mark
disappears from the box, the option is off.
Note: Inactive check boxes are dimmed.
Action buttons
Action buttons tell the system to do something, such as apply changes to the
system, or cancel a dialog. Action buttons contain their labels, and can have
keyboard shortcuts assigned to them. Figure 3-17 shows examples of three
action buttons.
Figure 3-17
Example action buttons
FW-21109
FW-21109
OK Alt+Return Clear Ctrl+C Cancel Ctrl+Escape
To select an action button using the mouse, Click Select on the button. The
action associated with the button is activated.
To select an action button using the keyboard, perform the following steps:
1 Tab to the action button you want.
2 Press Return.
The action associated with the button is activated.
Note: Inactive action buttons are dimmed.
Editing text
The following procedures describe the methods available for entering,
selecting, and editing text.
Entering text
Before you can insert or delete text, you must first position your cursor.
To position your cursor using the mouse, perform the following:

1 Move the pointer to where you want to edit.
To position your cursor using the keyboard, use the arrow keys to move to
where you want to edit.
You can insert text once you have positioned the cursor, or you can use the
Backspace key to delete text.
Selecting blocks of text

To move, copy, or delete larger blocks of text, you must first select them.
To select a block of text using the mouse, perform the following:

1 Move the pointer to the beginning of the text you want to select, press and
hold the Select mouse button, and drag the pointer to the end of the text.
The selected text is highlighted.
2 Release the Select mouse button when you have completed your selection.
To select a block of text using the mouse, perform the following:

1 Use the arrow keys to move to the beginning of the text you want to select,
then press Shift and use your arrow keys as required. The selected text is
highlighted.
2 Release the Shift key when you have completed your selection.

Cutting, copying, pasting, and replacing text

Editing can be performed on selected text.
To cut selected text using the mouse, perform the following:

1 Press Menu on the text field.
2 Choose Cut from the field menu.
The previously selected text disappears.
To cut selected text using the keyboard, Press Ctrl+Delete Char. The previously
selected text disappears.
To copy the selected text using the mouse, perform the following steps:
1 Press Menu on the text field.
2 Choose Copy from the field menu. The selected text does not disappear.
To copy the selected text using the keyboard, Press Ctrl+Insert. The selected
text does not disappear.
To paste the cut or copied text using the mouse, perform the following:
1 Click the Select mouse button at the place where you want the text to be
pasted.
2 Press the Menu mouse button, and choose Paste from the field menu.
The previously cut or copied text reappears in the new location.
To paste the cut or copied text using the keyboard, perform the following:
1 Use the arrow keys to move to the place where you want the text to be pasted.
2 Press Shift+Insert.
The previously cut or copied text reappears in the new location.
To replace text with cut or copied text using the mouse, perform the following:
1 Press the Menu mouse button in the field in which you have the selected text.
2 Choose paste from the field menu.
New text replaces the old text.
To replace text with cut or copied text using the keyboard, select the text to
replace and then press Shift+Insert. The new text replaces the old text.
Editing commands
If you want to edit a block of text, use the editing commands on the menu
associated with the field you are editing (or use the keyboard equivalents).
Table 3-2 shows a list of editing commands.
Table 3-2
Editing commands
Command Keyboard Action
equivalent
Select All Ctrl+/ Selects all text in the field.

Deselect All Ctrl+\ Cancels a text selection.
Cut Shift+Delete Char Removes the selected text and places it
in temporary storage from where you
can paste the text.
Copy Ctrl+Insert Char Places a copy of the selected text in
temporary storage from where you can
paste the text.
Paste Shift+Insert Char The text most recently copied or cut is
inserted at the point you have chosen.
Delete Delete, Backspace, Deletes the selected text.
or Ctrl_K
Note: Shortcut keys affect the object with keyboard focus, which might not
be the object that your pointer is on. Be sure the cursor is in the field you
want to edit before using a shortcut key sequence.

Command areas
Command areas are used for sending typed commands to a tool. They have two
main parts: a command field where you type commands and a history field
which keeps a record of the commands you have typed. Figure 3-18 shows an
example of a command area.
Note: Command areas are not common in the graphical interface.

Commands are more commonly chosen from menus.
Figure 3-18
Example command area
FW-21103
FW-21103
Separator
History field
Again
>
Command field Select this command
Select all Ctrl+/
Deselect this command
Deselect all Ctrl+\
Command field menu
Help Ctrl+H
History field menu
Delete Ctrl+K
Help Ctrl+H
The Command field menu presents the standard editing commands, which are
discussed in “Editing text.” The History field menu commands are the
following:
Command Description
Again Copies and executes the selected command.
Select this command Selects the command.
Deselect this command Cancels a text selection.
Copy Places a copy of the selected text in temporary

storage from where you can paste the text. You can
also use the keyboard shortcut Ctrl+Insert Char.
History fields
History fields can be resized.
To change the size of a history field using the mouse, perform the following:
1 Move the pointer to the separator line box.
The pointer becomes a double-ended arrow.
2 Press and hold the Select mouse button, and move up or down.
The history field area increases or decreases respectively.
3 Release the Select mouse button when you are finished sizing the history
field.
To change the size of a history field using the keyboard, perform the following:
1 Tab to the separator line box.
The box is highlighted.
2 Use the up or down arrow keys.
The history field area increases or decreases respectively.

Closing a tool
When you are finished with a tool, choose Exit from the File menu on the
Menu bar.
FW-21092
Exit menu
In some cases, a dialog appears, asking you whether you want to save the
changes you have made.
FW-21096
FW-21096
? Save changes for Message Alarm?
Yes Alt+Return No Ctrl+ - Cancel Ctrl+Escape
Select the Yes button to save changes and exit, No to exit without saving, or
Cancel to return to the tool.
Logging out
When you are ready to leave the workspace, move the pointer to the workspace
background, press Menu to open the workspace menu and select Logout.
FW-20243
FW-20243
Workspace Menu
Refresh Workspace
Logout
Help
A message box appears, asking you to confirm your intention.

FW-21157
FW-21157
Logging out will close all windows.

Logout Cancel

4-1
CI tool user interface 4-

This chapter describes the command interpreter (CI) user interfaces used to
control the Modem Shelf, Spectrum Manager, and Voice Ports.
Table 4-1 lists the CIs available for a Cornerstone system.
Table 4-1
CIs available for a Cornerstone system
CI name Purpose Refer to
csoptci Cornerstone optionality commands page 4-3
cvalrm Alarm details—to view detailed information about modem- page 4-6
shelf and Voice Port alarms
cveqpt Equipment maintenance—to maintain modem-shelf and page 4-10

Spectrum Manager equipment and Voice Ports
cvloader Load management—to download firmware loads to page 4-33

modem-shelf equipment and Voice Ports
cvpath Carrier path provisioning—to provision and deprovision page 4-41

carrier paths and headend modems
cvprov Voice Port provisioning—to provision and deprovision page 4-68

customers’ cable-TV and phone services
cvspmn Spectrum Manager maintenance—to perform spectrum page 4-98

maintenance
cvtraf Cornerstone—traffic monitoring page 4-105
cvv5 V5.2 Switch Interface page 4-115
famci Facility Assignment Manager tools page 4-148
omcci OMC provisioning tools page 4-154
vlcmci VLCM maintenance—to display vlcm status page 4-159
For a detailed description of the commands available for each CI tool, refer to
the appropriate page for the CI tool listed in Table 4-1.
Note: The command names and keywords are not case sensitive.
4-2 CI tool user interface
Commands common to all Cornerstone CIs

The following table lists the commands that are common for all CI tools.
Table 4-2
Commands common to all CVS CIs
Command Description
cvHelp an alias for help
help displays help for current level
help COMMANDS displays all Cornerstone commands
help <level> displays help on requested level

(for example, help cvpath)
quit quits the CI tool
Voice Port aliases

To avoid having to use a Voice Port ID, you may assign a Voice Port an alias.
The VP alias should consist of a string of up to 20 characters that should be
enclosed in single quotes; for example: ‘Smith_8425’. Although the
Cornerstone system may accept the alias without single quotes, the result may
be a garbled alias, a voice port that cannot be deleted, a stuck CRV, or another
anomaly.
If you are using TL1, use only alphanumeric characters and underscores in
alias strings.
Opening a CI tool
If you want to initiate a CI, perform the following steps.
1 Log in to the OPC.
2 Open the NE Login Manager tool.
3 Log in to the network element.
4 At the prompt, enter the following:
quit all ↵
5 At the CI prompt, enter the following:
cornerstone ↵
The CORNERSTONE CI prompt appears.
6 Open the CI tool by entering the name of the CI tool. For example, if you want
to perform spectrum maintenance, enter:
cvspmn ↵
Once you have initiated the CI, you enter CI commands to carry out the desired
operations. Refer to Chapter 9 for detailed instructions on how to use the CI
tool user interface.

CSOPTCI commands
Use the optionality commands to enable or query a particular Cornerstone
option.
The detailed description of the commands includes syntax and parameters and
gives examples of their use. When a given parameter value exceeds the valid
range, the system indicates “out of range” followed by the proper range and
prompts the user to reenter the data.
Table 4-3
CSOPTCI commands
Command For a detailed description, refer to
queryOpt page 4-4
enable page 4-5
queryOpt
Syntax
queryopt
Description
Queries optionality. Displays the entire set of optional features and which
features have been enabled.
Parameters
None.
Example Command
> QueryOpt
Successful Response
PEC Feature Status
--------- ------------------ ------
NTBN47AB RF_CONC ON
NTBN74AB EXTENDEDRANGE ON
NTBN74AC ENCRYPTION OFF
NTBN74AE ENCRYPTION OFF
NTBNXXX4 FEAT_3 OFF
NTBNXXX5 FEAT_3 OFF
NTBNXXX6 FEAT_3 OFF
NTBNXXX7 FEAT_3 OFF
NTBNXXX8 FEAT_3 OFF
NTBNXXX9 FEAT_3 OFF
NTBNXXXA FEAT_3 OFF
Error Response
None.

Enable
Syntax
Enable <token> <token_value> <parameter> <Opt_Code>
Description
Enables an optional feature on a given system and extended range for the
HDT.
Parameters
<token> is the desired addressing method for the feature. It will be
either FEAT to address the feature by the feature name or PEC
to address the feature by the PEC code.
<token_value> is the name of the feature if FEAT was selected as the token;
otherwise, <token_value> must be the PEC code for the
optional feature. Both values will be displayed on the
optionality code printout received from Cornerstone
Operations.
<parameter> is the desired addressing method for the feature. It will be
either FEAT to address the feature by the feature name or PEC
to address the feature by the PEC code.
<Opt_code> is the 16-digit optionality code obtained from Arris
Commercial Operations. This optionality code is specific to
the ABM system and the feature specified.
Example Command
> Enable PEC NTBN47AB 52e0b4893e4dd991
> Enable FEAT RF_CONC 52e0b4893e4dd991
> Enable FEAT EXTENDEDRANGE 633daf0ecc94adf4

> Enable PEC NTBN74AB 633daf0ecc94adf4
Successful Response
RF Concentration has been enabled.
RF Concentration has already been enabled.
EXTENDEDRANGE (NTBN74AE) has been enabled.

Error Response
I’m sorry, that optionality code is invalid for this system. Please contact your
Cornerstone Sales Representative to obtain a valid code.
CVALRM CI commands
Use the alarm details commands to view detailed information about modem-
shelf and voice-port alarms.
Table 4-4
CVALRM CI commands
alrmdisp page 4-7
alrmrpt page 4-8
history page 4-9

alrmdisp
Syntax
alrmdisp <filter criteria>
Description
This command allows you to display all of the active alarms in the Modem
Shelf alarm buffer.
Parameters
<filter criteria> is filter criteria for the alarms to be displayed:
ALL — displays all alarms. This is the default value.
FA — displays facility alarms.
EQ — displays equipment alarms.
SP — displays spectrum alarms.
C — displays critical alarms.
MA — displays active major alarms.
MI — displays active minor alarms.
Example Command
> alrmdisp
Successful Response
Active Alarms
Alm Class Shelf Type Unit Reason Severity
--- ----- ----- ---- ---------- -------------------------------------- --------
3 EQP MS1 DMC 9 DMC Circuit Pack Total Fail M,SA
Raised: 15:17:32 04/12/1999
Error Response
No alarms match filter criteria.
alrmrpt
Syntax
alrmrpt <alarm report ID>
Description
This command allows you to display details of a specific alarm.
Parameters
<alarm report ID>is the alarm report ID given in the alarms list.
Example Command
> alrmrpt 4
Successful Response
There are three different detail alarm formats:
Equipment -
ALARM 4
Address: DMC 3 m,nsa
Location: Modem Shelf 1 Slot 3 21:17:52
Reason: Circuit pack fail 04/12/1999
Equip ID: <Equip_id> PEC: <PEC_code> Equipment
Facility -
ALARM 4
Address: Head End Modem 13-2 m,SA
Location: Modem Shelf 1 Slot 13 Modem 2 21:18:37
Reason: DMC Head End Modem Loss of Signal 04/11/1999
Carrier Path: <CP_id> Facility
Spectrum -
ALARM 4
Address: Spectrum Manager m,nsa
Location: 21:23:05
Reason: Minimum Upstream Protection Band Limit 04/12/1999
Carrier Path: <CP_id> Spectrum
The Address and Location fields of the alarm details convey different
information depending on the maintenance entity raising/clearing the alarm.
Maintenance Entity Address Location
MSC MSC <#> Modem Shelf <#>

Slot <#>
DMC DMC <#> Modem Shelf <#>

Slot <#>
Voice Port Voice Port Voice Port ID <VP id>
Head End Modem HEM <DMC> <Modem> Modem Shelf <#>

Slot <#>
Modem <#>
Spectrum Manager Spectrum Manager
Error Response
ERROR: Unused Alarm Specified.

history
Syntax
history <filter criteria>
Description
This command allows you to display all of the alarms in the Modem Shelf
alarm history buffer that match the filter criteria.
Parameters
<filter criteria> is filter criteria for the alarms to be displayed:
ALL — displays all alarms. This is the default value.
FA — displays facility alarms.
EQ — displays equipment alarms.
SP — displays spectrum alarms.
C — displays critical alarms.
MA — displays active major alarms.
MI — displays active minor alarms.
Example Command
> history
Successful Response
Alarm History
Alm Cls Shlf Type Unit Reason Severity
--- --- ---- ---- ------ ---------------------------- --------
24 Eqp MS1 DMC 1 Circuit Pack Failure clear
23 Fac REM VP <VPid> Voice Port Facility Degraded clear
4 Eqp MS1 DMC 3 Circuit Pack Failure M,SA
2 Fac MS1 HEM 13-2 DMC Head End Modem LOS m,SA
41 Spe MS1 CP <CPid> Marshalling Frequency Unavail. m,nsa
Error Response
EITHER incorrect optional parameter(s) OR too many parameters.
CVEQPT CI commands
Use the equipment maintenance commands to maintain modem-shelf
equipment and Voice Ports.
gives examples of their use.
Table 4-5
CVEQPT CI commands
addDMC page 4-11
checkvp page 4-12
chgModemChan page 4-14
chgstateDMC page 4-15
chgstateModem page 4-16
chgstateSM page 4-17

chgstateVP page 4-18
delDMC page 4-19
delSM page 4-19
delVP page 4-21
diagSM page 4-22
queryBattery page 4-23
queryDMC page 4-24
queryMS page 4-25

queryMSC page 4-26
querySM page 4-27
queryVP page 4-28
resetMSC page 4-31
resetVP page 4-32

addDMC
Syntax
addDMC <dmc id>
Description
This command allows you to manually provision the selected DMC.
Parameters
<dmc id> is the DMC id: 1 to 14.
Example Command
> addDMC 10
Successful Response
DMC 10 has been successfully provisioned.
Error Response
DMC request rejected because DMC is in an invalid state.
Specified DMC has already been added.
Checkvp
Syntax
checkvp <id type>
checkvp dist <parameter1> <parameter2>
checkvp HEM <DMC> {1 to 14} <modem> {1 to 2} DIST
<parameter1> <parameter2>
checkvp CP <direction> DIST <parameter1> <parameter2>
Description
This CsV04 and newer command allows you to list Voice Ports that do not fit
the specified criteria: PEC or LOAD names, distance, level, HEM, or carrier
path. CsV06 and later versions also allow listing Voice Ports by signal quality.
In CsV06.2 and later, the CheckVP command replaces the LEVEL parameter
with a new DBMV parameter. This allows checking for explicit transmit levels
rather than relative levels.
In CsV08 and later, reflects the extended range delays in meters when Voice
Ports are within the extended range.
Parameters
<id type> specifies the Voice Ports to exclude from the list, based on
one of the following criteria:
PEC <code> [<code>...] — one or more Voice Port PEC codes
LOAD <loadname> [<loadname>...] — one or more Voice Port
software load names
DIST <low> <hi> — distance from the headend, in km (0 to 80)
DBMV <low> <hi> — Voice Port transmit level (5 to
55 dBmV)
HEM <DMC> <modem> <id type> — list Voice Ports attached
to a specific HEM, excluding those that match PEC, LOAD,
DIST, or DBMV criteria as specified above. You can also
specify a signal quality range using SIGQUAL <low> <high>
(0 to 50).
CP <direction> <id type> — list Voice Ports assigned to a
specific carrier path (US <path> for upstream or DS <path> for
downstream, 0 to 56 in either case), excluding those that match
PEC, LOAD, DIST, or DBMV criteria as specified above.
<parameter> specifies the parameter for 1 or 2.
parameter1: <low (km)> {0 to 144}
parameter2: <high (km)> {0 to 144}
direction: US <US> {1 to56}

DS <DS> {1 to 56}

Example Command
> checkvp hem 1 1 dist 70 80
> checkvp dist 0 80
> checkvp hem 6 1 dist 0 80
> checkvp cp us 1 dist 0 80
> checkvp cp ds 10 dist 0 80
Successful Response
The command displays the Voice Port ID and specified criteria; for example:
VP no. VP ID Distance (m)
---------- -------- ---------------------
1 11110002 120600
2 222220045 98600
3 1111010113 98600
4 11110088 98600
5 570482561 98600
6 570442636 98600
7 570426694 98600
8 214799934 98600
9 214749926 150600
VP no. VP ID Distance (m)

------ ------------- -------------
1 11110002 0
2 2147496892 0
Error Response
No Voice Ports are assigned to the specified <id type>.
An US CP was expected, but a DS CP was entered.
A DS CP was expected, but an US CP was entered.
chgModemChan
Syntax
chgModemChan <DMC> <modem> <direction> <channel code>
Description
This command allows you to change up or down stream communication
frequency for the specified modem.
Parameters
<direction> is the direction of the frequency: US (upstream) or
DS (downstream).
<channel code> is the downstream and upstream communication frequency
range represented as a channel code.
For downstream, the frequency range is a 1.792 MHz
frequency range of channels from 375 - 750 MHz: 98 to 1562.
For upstream, the narowband frequency range is a 1.792 MHz
For upstream, the wideband frequency range is a 1.792 MHz
frequency range of channels from 5-65 MHz: 1 to 234.
Note: Refer to Appendix C: Channel center frequencies of the
Engineering Guidelines, ARSVD00388, for upstream and
downstream channel codes.
<modem id> is the modem id: 1 or 2.
Example Command
> chgModemChan 14 2 US 135
Successful Response
Modem frequency is changed to upstream channel 135.
Error Response
Specified modem does not exist.
Specified frequency is not provisioned.
Specified frequency is not available.

chgstateDMC
Syntax
chgstateDMC <dmc id> <target state>
Description
This command allows you to change the primary state of the selected DMC.
Parameters
<target state> is the target service state: IS or OOS.
Example Command
> chgstateDMC 10 OOS
Successful Response
DMC 10 is now OOS.
Error Response
Specified DMC does not exist.
chgstateModem
Syntax
chgstateModem <dmc id> <modem id> <target state>
Description
This command allows you to change the primary state of the selected modem.
Parameters
<dmc id> is the DMC ID: 1 to 14.
<modem id> is the modem ID: 1 to 2.
Example Command
> chgstateModem 10 1 OOS
Warning: This command will affect service.
Please confirm (“Yes” or “No”):
Successful Response
Modem 1 of DMC 10 is now OOS.
Error Response
Request rejected because HEM is in an invalid state.
HEM unequipped.
Specified HEM is already <target state>

chgstateSM
Syntax
chgstateSM <sm id> <target state>
Description
This command allows you to change the selected Spectrum Manager
equipment state.
Parameters
<sm id> is the Spectrum Manager on which the carrier path is carried:
1 to 4.
Note: Although the range is 1 to 4, only two Spectrum
Managers are supported.
Example Command
> chgstateSM 2 OOS
Successful Response
Spectrum Manager #2 is OOS.
Error Response
The specified Spectrum Manager ID does not exist.
Request rejected because Spectrum Manager is in an invalid state.
Specified Spectrum Manager is already <target state>.
chgstateVP
Syntax
chgstateVP <id type> <target state>
Description
This command allows you to toggle the Voice Port between the in-service and
out-of-service state.
Parameters
<id type> specifies the Voice Port by alias or VPID:
ALIAS <alias> — where <alias> is a 20-character string
enclosed in single quotation marks (see “Voice Port aliases” on
page 4-2).
VP <id> — where <id> is a decimal number: 1 to 4294967295.
Example Command
> chgstateVP ALIAS ‘Norcross’ OOS
> chgstateVP VP 123456 IS
Successful Response
Voice Port state changed to OOS.
Error Response
Voice Port equipment does not exist.
Specified voice port alias does not exist.
Specified voice port is already <target state>.

delDMC
Syntax
delDMC <dmc id>
Description
This command allows you to deprovision the selected DMC.
Parameters
Example Command
> delDMC 10
Successful Response
DMC 10 has been deleted.
Error Response
DMC must be OOS to be deleted.
delSM
Syntax
delSM <sm id>
Description
This command allows you to delete the selected Spectrum Manager.
Parameters
1 to 4.
Example Command
> delSM 2
Successful Response
Spectrum Manager #2 has been deprovisioned.
Error Response
Request rejected because Spectrum Manager is in an invalid state.
Spectrum Manager must be OOS to be deleted.

delVP
Syntax
delVP <id type>
Description
This command allows you to delete the Voice Port provisioning data and the
equipment data.
This command can be used when a homeowner moves.
Parameters
page 4-2).
Example Command
> delVP ALIAS ‘new_customer_4567890’
Warning: VP will be deleted.
> delVP VP 123456
Warning: VP will be deleted.
Successful Response
Provisioning and equipment records of Voice Port have been
deleted.
Error Response
Voice Port equipment does not exist.
Specified Voice Port alias does not exist.
Voice Port has service provisioned.
No response from the modem shelf.
diagSM
Syntax
diagSM <sm id>
Description
This command allows you to run diagnostics on the selected Spectrum
Manager chassis.
Parameters
1 to 4.
Example Command
> diagSM 2
Successful Response
Diagnostics are currently underway. Please refer to CV
logs for the results.
Error Response
Spectrum Manager is in an invalid state for this request.
Specified spectrum manager is busy - try again later.

queryBattery
Syntax
QueryBattery <ID Type>
Description
The QueryBattery command displays all Voice Ports that match one of the
specified battery conditions.
Parameters
<id type> designates how to list the Voice Ports:
ALL <valid states> — lists all Voice Ports assigned to this HDT
for the valid state specified (NORMAL, REPLACE,
NO_BATTERY, NO_AC_GOOD_BATT, NO
_AC_REPLACE_BATT, N_A).
HEM <dmc> <modem> <valid states> — lists Voice Ports
connected to a specified DMC (1 to 14) and a specified modem
(1 or 2) in a valid state.
COUNT ALL <valid states> — counts all Voice Ports assigned
to this HDT for a specified valid state.
COUNT HEM <dmc> <modem> — counts all Voice Ports
assigned to this HDT
Example Command
> querybattery all no_ac
> querybattery hem 8 2 no_ac_good_batt
> querybattery count all no_battery
> querybattery count all normal
Successful Response
Count VPID Power Condition
------ ------------- -----------------
1 16783413 No AC Power 1 1
2 16774611 No AC Power, Battery Good
3 16778993 No AC Power, Replace Battery
1 16783413 Normal 0 1
2 16733443 No AC Power 0 1
1 16819791 Normal
2 16774611 No AC Power, Battery Good
3 16721935 Normal
4 16687434 Normal
5 16687555 Normal
Error Response
No Voice Ports are assigned to the specified modem.
No response from the modem shelf ... aborting.
queryDMC
Syntax
queryDMC <dmc id>
Description
This command allows you to show the status of the selected DMC.
Parameters
Example Command
> queryDMC 1
Successful Response
> Unit: DMC 1
Primary State: IS
FW Load in FLASH A: DDM18DR01
FW Load in FLASH B: DDM18DR01
Circuit Pack: NTBN19DA
Serial Number: L1AMP7Y
Manufacturer’s Date:08/FEB/1999
Modem 1: Primary State: IS Secondary State:
DS CP: 2 Spectrum_Chan_Code:400
US CP: 1 Spectrum_Chan_Code:72
TX Level: 30 dBmV RX Level: 15 dBmV
Modem 2: Primary State: IS Secondary State:
DS CP: 4 Spectrum_Chan_Code:353
US CP: 3 Spectrum_Chan_Code:66
TX Level: 30 dBmV RX Level: 15 dBmV
Error Response
No response from modem shelf.

queryMS
Syntax
queryMS
Description
This command displays the status of the Modem Shelf (MS) equipment and
Spectrum Managers.
Parameters
None.
Example Command
> queryMS
Successful Response
Slot Type PEC Primary Secondary
---- ---- ---------- ------- ---------
1 DMC NTBN19CA IS
2 DMC NULL
3 DMC NULL
4 DMC NTBN19CA IS
5 DMC NULL
6 DMC NULL
7 DMC NTBN19AA IS
8 DMC NTBN19AA IS
9 DMC NULL
10 DMC NULL
11 DMC NTBN19CA IS
12 DMC NULL
13 DMC NULL
14 DMC NTBN19CA OOS
15 MSC NTBN20AB IS
-- SM NTBN21AB IS
-- SM NULL NULL
-- SM NULL NULL
-- SM NULL NULL
Error Response
queryMSC
Syntax
queryMSC
Description
This command allows you to query the MSC equipment.
Parameters
None.
Example Command
> queryMSC
Successful Response
Unit: 1
State: IS
FW Load in RAM: CMSNAD18BG00
FW Load in FLASH A: CMSNAD18BG00
FW Load in FLASH B: CMSNAD18BG00
MSC Current Active Flash: Bank B
Circuit Pack: NTBN20AC
Serial Number: A1A2T8U
Manufacturer's Date: 12/DEC/1996
Error Response
None.

querySM
Syntax
querySM <sm id>
Description
This command allows you to show the status of the selected Spectrum
Manager.
Parameters
1 to 4.
Example Command
> querySM 2
Successful Response
Unit: Spectrum Manager 1
Primary State: IS
Secondary State:
FW Load in RAM: - vAU.01
Circuit Pack: NTBN21AB
Error Response
Specified Spectrum Manager does not exist.
queryVP
Syntax
queryVP <id type> <parameter1> <parameter2>
Description
This command allows you to query the status, marshalling state, and
configuration of a Voice Port.
For CsV06:
• This command includes an indication for battery condition and status of
local power supplies via telemetry. This feature is not supported by all voice
ports and will show "N/A" for those that do not support this feature.
For CsV08:
• This command displays the status of line card modules installed in the MAX
24 Voice Port. The MAX 24 does not have specific battery telemetry points,
so battery telemetry only applies to the AC power condition.
1 = normal (AC power is present
2 = no AC power
In addition, MAX 24 supports two General Telemetry Points (GTP) whose

states are also displayed.
1 = Telemetry point pulled to ground
0 = Telemetry point not pulled to ground
• This command reflects the extended range delays in meters when the Voice
Ports are within the extended range.
Parameters
<id type> the query type, one of the following. Where the [<#lines>]
option is present, you can specify how many lines of output
display (1 to 100) before waiting for a carriage return. The
default is 20. You can enter 0 for a continuous display.
ALIAS <name> — Queries a single Voice Port by alias.
VP <id> — Queries a single Voice Port by serial number:
1 to 4294967295.
MODEM <DMC> <modem> [<database>] [<#lines>] —
Queries all Voice Ports assigned to a particular HEM. You can
specify the database to search (PROV for provisioning or EQPT
for equipment).
SERVICE <type> [<#lines>] — Queries all Voice Ports by
service; one of NIL, MVIPOTS, LCMPOTS, V5POTS, or EBS.
STATE <state> <sort by HEM> [<#lines>] — Queries Voice
Ports with the specified state; one of IS, IS_TRBL, OOS,
OOS_MTCE, UNASGN (marshalled but not provisioned),
UNEQPD (provisioned but not marshalled), UNDETERMINED
(lines are provisioned but the Voice Port is neither provisioned
nor marshalled), COMMS_DOWN (lost communications with

the HEM), or HEMMISMATCH (HEM mismatch between

provisioning and equipment database). The <sort by HEM>
parameter is either Y or N.
CATV <state> [<#lines>] — Queries Voice Ports by whether
CATV is enabled; either OFF or ON.
LOAD <string> [<#lines>] — Queries Voice Ports by the
specified load name.
PEC <code> [<#lines>] — Queries Voice Ports by the
specified PEC code.
COUNT <type> — Displays a count of Voice Ports. The <type>
can be ALL <disp> to count all Voice Ports using a BRIEF or
FULL display, HEM <DMC> <modem> for a specific HEM,
STATE <state> for the specified state, LOAD <name> for the
specified load, or PEC <code> for the specified PEC code.
LOOPCURRENT <type> — Displays Voice Ports provisioned
with high loop current. The <type> can be ALL to display all
such Voice Ports, HEM <DMC> <modem> for Voice Ports on
a specific HEM, or CP <id> for Voice Ports on a specific
upstream carrier path.
<parametern> the query parameter n, where n is 1 or 2.
ALIAS <name> — Queries a single Voice Port by alias.
VP <id> — Queries a single Voice Port by serial number:
1 to 4294967295.
Example Command
> queryvp vp 123456789
> queryvp alias BOB
Successful Response
In CsV06.2 and later, the listing for individual Voice Ports shows marshalled
and current transmit levels in dBmV instead of a relative level.
GTP 1 & 2 are only displayed for the MAX 24 Voice Port.
> queryVP vp 1679935

Getting voice port data...please wait.
VP Id: 123456789
Alias: BOB
State: IS
Attached Modem: DMC 7 1
Marshalled TX Level: 52 dBmV (62)
Current TX Level: 51 dBmV (61)
Power Condition: Normal
Range Delay: 148600 meters
Voice Port Load: CVPMML20AD01
Circuit Pack: NTBN67LA08
Line Card Module 1: Equipped
GTP 1: 0
GTP 2: 1
> queryvp modem 5 1

Getting voice port data... please wait.
--------------------------------------------------------
VP No | MSN | State | Tx | CATV | Line | Service |LC Inst
--------------------------------------------------------
1 16798981 IS 31 ON 1 MVIPOTS 1
IS 42 ON 2 EBS 2
2 16798987 IS 30 ON 1 MVIPOTS 4
IS 25 ON 2 EBS 7
>queryvp count all full

CP Eqpt Prov IS OOS ISTrbl Unasgn Uneqpd CommDown
DMC:HEM (D,U) (=e) (=p) (e=p) All(e) All(e) (e) (p) (p)
---------------------------------------------------------------------------
1:1 1, 2 5 5 5 0 0 0 0 0
1:2 1, 2 2 2 2 0 0 0 0 0
....
Error Response
Specified voice port id does not exist.
Specified modem id does not exist.
No voice port assigned to the specified modem id.
No voice ports are provisioned with the specified service.
No response form the modem shelf.
No voice ports are in the specified CATV mode.
No voice ports found.
No voice ports are in the specified state.

resetMSC
Syntax
resetMSC [FORCE]
Description
This command allows you to reset the MSC equipment.
Parameters
FORCE Optional parameter, resets the MSC in cases where the MSC
is not responding to commands, but the lower level
communications is present. Do not use this option unless
instructed by support.
Note: If lower level communications are not present, you will
see a message when executing the queryMS command. The
FORCE option can be used to reset the MSC remotely in cases
where the MSC SW application is not responding (for
example, a database vintage mismatch).
Example Command
> resetMSC force
Successful Response
Initiated MSC reset. Check logs for diag results.
Error Response
Unable to send message to modem shelf, RC=bmBadLink.
resetVP
Syntax
resetVP <id type>
Description
This command allows you to manually restart the software on a Voice Port.
Parameters
page 4-2).
Example Command
> resetVP ALIAS ‘Norcross’
> resetVP VP 123456
Successful Response
Initiated Voice Port reset. Check logs for reset results.
Error Response
Unable to send message to modem shelf, RC=bmBadLink.

CVLOADER CI commands
Use the load management commands to download firmware loads to modem-
shelf equipment and Voice Ports.
Table 4-6
CVLOADER CI commands
cvload page 4-34
listdefaults page 4-35
mscflswact page 4-35
queryCVswldFile page 4-37
queryload page 4-36
setCVswldFile page 4-39
syncdefaults page 4-40
cvload
Syntax
cvload <proc type> <loadname>
Description
This command allows you to load the specified processor. Use this command
to reload or upgrade software in the HDT.
Parameters
<proc type> is the processor to be loaded; one of:
VP <id type> — a Voice Port; use ALIAS <alias> to specify by
alias or VP <id> to specify by VPID (1 to 4294967295).
DMC <id type> — specifies a Dual Modem Card by slot
number (1 to 14)
MSC — specifies the Modem Shelf Controller.
SM <proc> — specifies a Spectrum Manager (1 or 2)
Note: The Spectrum Manager must already have the AV01 or
newer firmware load before using this command. While
loading the Spectrum Manager, out-of-band Voice Port
marshalling is suspended and frequency agility is impaired.
<loadname> is the name of the file on the OPC that contains the software
that is to be loaded on the processor.
Example Command
> cvload DMC 12 CDMNAL11AA01
> cvload vp vp 16801614 CVPPHL16AX99
Successful Response
In addition to the following response, this command generates a CVLDxxx log
containing details of the load attempt.
****************** WARNING ********************

This action is service affecting.
***********************************************
>Y
<proc type> MTC will process the request. Check loader
logs for result.
Error Response
CVLOADER ERROR: OPC not responding, check association.
Spectrum Manager <id> is not in a valid state to load.
The Spectrum Manager must be in either the IS or OOS state to load.
Spectrum Manager <id> is unequipped.
The specified Spectrum Manager does not exist.
Specified Voice Port ID does not exist.

listdefaults
Syntax
listdefaults
Description
Starting in CsV04, this command allows you to display the loads currently
contained in the default load entity set on the MSC. This includes Voice Port,
DMC, Modem Shelf Controller, and Spectrum Manager loads.
Parameters
None.
Example Command
> listdefaults
Successful Response
The current CV Modem Shelf Load Lineup file is CV_1900MS.load.
---------------------------------------------------------
Processor PEC Date Load Name
--------- --- ---------- ------------
MSC NTBN20AA 02-02-99 CMSNAL19AA01
SM NTBN21AB 02-02-99 CSMNAL11AV01
Error Response
No Default loads assigned. Use SyncDefaults command.
CVLOADER ERROR: OPC not responding, check association.
mscflswact
Syntax
mscflswact
Description
This command swaps the MSC flash and resets to the processor (CsV04 and
newer).
Parameters
None.
Example Command
> mscflswact
Successful Response
Swact command sent Check loader logs for result.
Error Response
Msc communication failure; please try again later.

queryCVswldFile
Syntax
queryCVswldFile
Description
This command displays the current Modem Shelf Load Lineup file.
Parameters
None.
Example Command
> queryCVswldFile
Successful Response
The CV modem shelf load lineup file that will be used in
the next potential upgrade situation is CV_1803MD.load.
The APU database release number currently associated with
it is REL1803.
Error Response
None.
queryload
Syntax
queryload <proc id> <id type>
Description
This command allows you to display the load that is currently on the specified
processor.
Parameters
<proc type> is the processor to be loaded; one of:
VP <id type> — a Voice Port; use ALIAS <alias> to specify by
alias or VP <id> to specify by VPID (1 to 4294967295).
DMC <id type> — specifies a Dual Modem Card by slot
number (1 to 14)
MSC — specifies the Modem Shelf Controller.
SM <sm id> — specifies a Spectrum Manager, either 1 or 2.
Example Command
> queryload VP VP11087
Successful Response
<proc type> is running firmware release: <release type>
Error Response
The specified processor instance does not exist
Voice port<#> not found in the database. Try again.

setCVswldFile
Syntax
setCVswldFile <file> [FORCE]
Description
This command updates the Modem Shelf Load Lineup file.
Parameters
<file> is the name of the new load lineup file.
FORCE optional parameter; forces an update.
Example Command
> setCVswldFile CV_1803MD
Successful Response
The CV Modem Shelf Load Lineup File has been successfully
updated from CV_1802MD.load to CV_1803MD.load.
Error Response
Invalid CV Modem Shelf Load Lineup Filename
The file name must begin with CV_ and be between 4 and 14 characters in
length. Do not append the “.load” extension.
<file>.load is not accessible.
The load file must be in /users/VFS/users/csv on the OPC, and must have
read permissions.
There is no need to update the CV Modem Shelf Load Lineup File
The specified file is already the current load lineup file.
syncdefaults
Syntax
syncdefaults
Description
This command allows the MSC to read the defaults load file on the OPC and
to update the default load entity set on MSC to match the file on OPC. If there
was a discrepancy between the OPC version and the MSC version, loads on
the OPC are propagated to the appropriate processors which reset to allow the
new load to take effect.
Parameters
None.
Example Command
> syncdefaults
Successful Response
Warning: This action is service affecting. All processors
will be downloaded with their defaulted loads.
Please confirm (Yes or No):
Y
Default load synchronization complete.
Error Response
Default load synchronization failed.
Command Rejected. SM1 is currently downloading.
The SyncDefaults command cannot run while a Spectrum Manager is
being loaded.
MSC communication failure; please try again.

CVPATH CI commands
Use the carrier path CI commands to provision and deprovision carrier paths
and headend modems.
The Modem Shelf Controller (MSC) is the centralized entity to validate the
consistency of the provisioning input. The cvpath CI requires the MSC to be
in service to process every command except queryCP and queryPortThSM.
The CI indicates the MSC is not in service even though this error response is
not explicitly specified for each command.
Table 4-7
CVPATH CI commands
addCP page 4-43
allocMarshSpectCP page 4-45
allocSpectCP page 4-46
asgnModemCP page 4-47
chgMarshMode page 4-49
chgNameCP page 4-50

chgSMPortCP page 4-51
deallocMarshSpectCP page 4-52
deallocSpectCP page 4-53
deasgnModemCP page 4-54
delCP page 4-55
queryCP page 4-57
queryPortThSM page 4-58
queryTG page 4-59
setMinMarshDistance page 4-60
setModemRxPower page 4-61
setModemTxPower page 4-62

—continued—
Table 4-7
CVPATH CI commands (continued)
setPortThSM page 4-63
setProtBandCP page 4-64
setRouteDiversity page 4-65
tieCP page 4-66
untieCP page 4-67

—end—

addCP
Syntax
addCP <cp id> <name> DS <marshalling mode>
<marshalling parameter> <HE to nearest VP>
addCP <cp id> <name> US <sm id> <sm port> <ds cp id>
<HE to nearest VP>
Description
This command allows you to add a new carrier path to the cable network. The
path can be either downstream or upstream.
To define an upstream path, specify the monitoring Spectrum Manager port
and identify the correlating downstream path.
To define a downstream path for multiple upstream paths, specify the
marshalling mode, either in band or out of band. For out-of-band marshalling,
specify the common Voice Port marshalling channel shared by all the return
paths. For in-band marshalling, specify the minimum marshalling delay by
entering the distance between head end and the nearest Voice Port installed on
the defining path.
If the specified Spectrum Manager does not exist, you are prompted to
continue. If you choose to continue, the HDT places the (non-existent)
Spectrum Manager in an IS-Trbl-Comms-Down state.
Add an additional marshalling channel using the allocMarshSpectCP
command to handle marshalling frequency agility. Refer to
“allocMarshSpectCP” on page 4-45.
Parameters
<cp id> is the ID for either upstream or downstream carrier path:
1 to 56. Up to half of the IDs are used for upstream, the other
28, at most, are used for downstream.
<name> 20 character carrier path name.
US, DS indicates the direction of this carrier path, either upstream or
downstream.
<marshalling mode>
is the marshalling mode of the carrier path: IB (in band) or
OOB (out of band).
<marshalling parameter>
for the desired marshalling mode:
IB - distance between the headend and the nearest Voice Port
(in km): 0 to 64.
OOB - common upstream frequency channel set aside for out-
of-band Voice Port marshalling: 4 to 141 for narrowband; 4 to
231 for wideband.
1 to 4.
<sm port> is the Spectrum Manager port associated with the upstream
carrier path:1 to 14.
<ds cp id> is the downstream carrier path that corresponds to this
upstream carrier path: 1 to 56.
<HE to nearest vp>
is the minimum distance between the head end and nearest
Voice Port (in km): 0 to 64.
Example Command
case 1> addcp 1 ‘downstream_1’ DS OOB 237
case 2> addcp 3 ‘upstream_3’ US 1 1 1
case 3> addcp 4 ‘upstream_4’ US 1 2 2
case 4> addcp 2 ‘downstream_2’ DS IB 9
Successful Response
case 1: Downstream carrier path 1, ‘downstream_1’, is
defined. The common upstream channel 140 is used for Voice
Port out-of-band marshalling.
case 2: Downstream carrier path 2, ‘downstream_2’, is
defined to utilize in-band marshalling. The nearest Voice
Port is 9 kilometers away from its head end.
case 3: Upstream CP 3, ‘upstream_3’, is defined and
monitored by Spectrum Manager 1 port 1. It correlates to
downstream path 1.
case 4: Upstream CP 4, ‘upstream_4’, is defined and
monitored by Spectrum Manager 1 port 2. It correlates to
downstream path 2.
Error Response
Unable to set narrowband. Wideband Channel is in use.
The specified carrier path id is in use.
The correlating downstream CP does not exist.
Maximum number of SM addresses exceeded.
The specified Spectrum Manager port is in use.
Multiple return paths requires a marshalling channel allocated.
Exceeded the maximum number of provisioned cp for the specified direction.
No response from the Modem Shelf.

allocMarshSpectCP
Syntax
allocMarshSpectCP <ds cp id> <us freq>
Description
This command allows you to allocate a common frequency, specified as a
channel code, used by headend modems assigned to various return paths to
marshall Voice Port on the same downstream carrier path.
The specified marshalling channel should be disjoint from communication
channel bands. The maximum number of marshalling channels is 10.
This command is acceptable when marshalling mode is out of band.
Parameters
<us freq> is the upstream marshalling (frequency) channel: 4 to 141 for
narrowband; 4 to 234 for wideband.
Example Command
> allocMarshSpectCP 1 70
Successful Response
Marshalling frequency channel 70 allocated to carrier
path 1.
Error Response
Specified CP does not exist.
Specified path is not a DS CP.
Specified channel is already allocated for Voice Port communication.
Maximum number of marshalling channels exceeded.
Marshalling mode is not OOB.
Cannot allocate Wideband Marshalling Channel on Tied Group.
allocSpectCP
Syntax
allocSpectCP <cp id> <low> <high>
Description
This command allows you to assign the frequency channel range, used by
modem communication, of a given carrier path.
The maximum of communication channel bands is 42. To accommodate 28
headend modems per Modem Shelf, the required maximum number of discrete
channel bands is 28. Also, to support a 2:1 protection ratio, additional 14
channel bands are available.
If the number of contiguous channel to cover the bandwidth of 2 MHz
required by one headend modem is 7, then, (n x 7) contiguous clear channels
are required to provide the bandwidth for n headend modems to communicate
with the attached Voice Ports.
Parameters
<low> and <high>
is the downstream and upstream communication frequency
For upstream, the frequency range is a 1.792 MHz frequency
range of channels from 5 - 65 MHz: 1 to 144 for narrowband;
1 to 234 for wideband.
Note: Refer to Appendix C: Channel center frequencies of the
Engineering Guidelines, ARSVD00388, for upstream and
Example Command
> allocSpectCP 2 180 194
Successful Response
Frequency channels [180..194] added to carrier path 2.
Error Response
Specified upstream channel range contains marshalling channel.
Maximum number of channel bands exceeded.
Frequency overlap with tied group. Cannot allocate spectrum.
CP tied together and in narrowband. Cannot change to Wideband.

asgnModemCP
Syntax
asgnModemCP <dmc id> <modem id> <ds cp id> <us cp id>
<tx power> <rx power>
Description
This command allows you to assign a modem to the specified upstream and
downstream carrier path.
To avoid affecting service, the bandwidth of the specified paths must be
sufficient for frequency assignment to the given modem, in addition to
protection bands. Refer to “queryCP” on page 4-57 to determine the
availability of those bandwidth.
Parameters
<modem id> is the modem: 1 or 2.
<ds cp id> and <us cp id>
are the downstream and upstream carrier path ids to which the
modem will be connected: 1 to 56.
<tx power> is the downstream transmission power level for the modem (in
dBmV): 25 to 55.
<rx power> is the upstream transmission power level for the modem (in
dBmV): -5 to 20.
Note: The transmit and receive power levels are average
engineered levels that the modem will be transmitting and
receiving respectively. Refer to the Engineering Guidelines,
ARSVD00388 for details on how to set these levels.
Example Command
> asgnModemCP 6 1 1 2 25 5
Successful Response
Ok.
Modem 1 on DMC 6 assignments made:
downstream - 1
upstream - 2
TX power - 25 dBmV
RX power - 5 dBmV
Error Response
Specified carrier path does not exist. Provision it with addCP followed by
allocSpectCP command.
Specified modem is already assigned to other CPs.
Specified upstream carrier path does not have enough bandwidth.
Specified downstream carrier path does not have enough bandwidth.
Specified upstream path is not a return path of the specified downstream path.
Specified path is not used for upstream direction.
Unable to assign modem carrier path due to incorrect shelf type. Please insert
DMC into corresponding modem shelf slot and reassign modems to carrier
path.

chgMarshMode
Syntax
chgMarshMode <cp id> <marshalling mode>
Description
This command allows you to change the marshalling mode. All the related
parameters associated with the previous marshalling mode are reset. For
instance, after changing to in-band marshalling, the out-of-band marshalling
channel count resets to zero.
Parameters
<marshalling mode>
is the marshalling mode of the carrier path: IB (in band) or
OOB (out of band).
is the marshalling parameter for the desired marshalling mode.
For IB, this parameter is the distance between the head end
and the nearest Voice Port (in km): 0 to 64.
For OOB, this parameter is the common upstream frequency
channel set aside for out-of-band Voice Port marshalling:
4 to 141 for narrowband, 4 to 231 for wideband.
Example Command
> chgMarshMode 2 IB 5
Successful Response
OK.
Error Response
Specified carrier path does not exist.
Marshalling mode was already the same as specified.
More than one return path is associated with the specified down stream carrier
path.
chgNameCP
Syntax
chgNameCP <cp id> <name>
Description
This command allows you to rename the specified carrier path.
Parameters
<name> is the 20 character carrier path name.
Example Command
> chgNameCP 1 ‘first_downstreamPath’
Successful Response
Carrier path 1 renamed to [first_downstreampath].
Error Response
Unable to send message to modem shelf: bmBadLink.

chgSMPortCP
Syntax
chgSMPortCP <cp id> <old sm id> <old sm port> <new sm id>
<new sm port>
Description
This command allows you to use a different port of a Spectrum Manager to
monitor an upstream carrier path.
Parameters
<old sm id> is the Spectrum Manager on which the carrier path is carried:
1 to 4.
<old sm port> is the old Spectrum Manager port: 1 to 14.
<new sm id> is the Spectrum Manager on which the carrier path is carried:
1 to 4.
<new sm port> is the new Spectrum Manager port: 1 to 14.
Example Command
> chgSMPortCP 2 4 1 4 11
Successful Response
Carrier path 2’s Spectrum Manager changed to SM ID:4,
PORT: 11.
Error Response
Specified upstream CP does not exist.
Carrier path is not used for upstream direction.
Carrier path was not monitored by the Spectrum Manager port being specified.
Maximum number of SM addresses exceeded.
New SM port is already in use.
deallocMarshSpectCP
Syntax
deallocMarshSpectCP <ds cp id> <us freq>
Description
This command allows you to deallocate a marshalling frequency channel on
the given downstream carrier path when out-of-band marshalling mode is
used.
To support out-of-band marshalling for a topology configured with one
downstream path and multiple return paths, provision at least one common
marshalling channel.
Parameters
<us freq> is the upstream marshalling (frequency) channel: 1 to 141 for
narrowband, 1 to 234 for wideband.
Example Command
> deallocMarshSpectCP 3 231
Successful Response
Marshalling frequency channel 231 deallocated from carrier
path 3.
Error Response
Specified channel is not used for marshalling.
Invalid to deallocate the last marshalling frequency code for a multiple return
paths topology.
Marshalling mode is not OOB.

deallocSpectCP
Syntax
deallocSpectCP <cp id> <low> <high>
Description
This command allows you to reduce or deallocate the frequency range, used
by modem communication, of a given carrier path.
The maximum number of communication channel band is 42 (refer to the
description of “addCP” on page 4-43 for the rationale of this limitation). To
deallocate frequency channel bands you can break one allocated band into two
sub-bands. The upper bound must be followed.
To avoid affecting service, the reduced bandwidth must be sufficient to serve
all the assigned modems as well as the protection bands.
In addition, the specified channel band should exclude any marshalling
channel. Use “deallocMarshSpectCP” on page 4-52 to free a marshalling
channel.
Parameters
<low> and <high>
is the downstream and upstream communication frequency
For upstream, the frequency range is a 1.792 MHz frequency
range of channels from 5 - 42 MHz for narrowband: 1 to 144,
or 5 - 65 MHz for wideband: 1 to 234.
Note: Refer to Appendix C: Channel center frequencies in the
Engineering Guidelines, ARSVD00388, for the upstream and
Example Command
After using the command allocSpectCP 1 98 200
deallocSpectCP 1 98 124
Warning: Delete channel may impact service.
Successful Response
Frequency [180..194] deallocated from carrier path 2.
Error Response
Insufficient bandwidth for the modems currently assigned or for the protection
band limit currently set on this CP..
Maximum number of channel bands exceeded.
deasgnModemCP
Syntax
deasgnModemCP <dmc id> <modem id>
Description
This command allows you to deassign the specified headend modem from the
cable network.
To avoid service interference, no Voice Port must be assigned to this headend
modem. If a Voice Port was assigned to this modem, copy the vp_id along
with its provisioned data first. Use deasgnVp to delete those affected Voice
Ports provisioning data. After deasgnModemCP is completed, use
appropriate commands to recover those deleted provisioning data. If a line was
provisioned as CSC POTS, use the DMS MAPCI to make the necessary
corrections as well.
Parameters
Example Command
> deasgnModemCP 5 1
This will delete CP assignments for modem 2 on DMC 6.
Please confirm ("Yes" or "No"):
>y
Successful Response
Modem is deassigned.
Error Response
Command rejected. This modem is serving provisioned Voice Ports.
The specified receive power level does not match the DMC version.
Specified modem is not assigned to a carrier path.

delCP
Syntax
delCP <cp id>
Description
This command allows you to remove a carrier path from the cable network by
specifying the id.
To avoid service interference, ensure that no headend modems are currently
provisioned on this carrier path. If required, use “deasgnModemCP” on page
4-54 to move those affected modem first.
All upstream carrier paths associated with a downstream carrier path must be
deleted prior to deleting the downstream path.
Parameters
Example Command
> delCP 1
About to delete CP 1, “first_downstreamPath”
Successful Response
Carrier path 1 deleted.
Error Response
There are modems provisioned on the specified carrier path.
There are Voice Port provisioned on the specified carrier path.
There are return paths associated with the specified DS CP.
Canot delete CP. CP tied together.
Enable_ExtRange
Syntax
Enable_ExtRange
Description
This command allows you to extend the range for the HDT by setting the
extended range ON (for the entire HDT). This is only available after extended
range has been enabled via CSOPTCI.
Parameters
None.
Example Command
> Enable_ExtRange
Successful Response
Extended distance for this HDT is ON.

queryCP
Syntax
queryCP [<cp id>]
Description
This command displays the upstream or downstream direction, the name, the
modem list, the allocated modem communication frequency channel bands of
the carrier path table. The Spectrum Manager port and the associated
downstream path id are associated with an upstream carrier path; the out-of-
band marshalling channel is associated with a downstream carrier path using
out-of-band marshalling; the distance between head end and the nearest Voice
Port is associated with a downstream carrier path using in-band marshalling.
Parameters
<cp id> is an optional parameter that specifies the ID for either
upstream or downstream carrier path: 1 to 56. Up to half of
the IDs are used for upstream, the other 28, at most, are used
for downstream. When path is specified, a detailed
information, rather than a summary, is displayed.
Example Command
> queryCP
> queryCP 1
Successful Response
> queryCP
scan #of marshalling DS
id CP name dir port PB dist.(Km)/chan Cp Comm Channels
-- --------- --- ---- --- --------------- --- -------------
1 Norcross DS - - 141 - 500-1500
2 Windward DS - - 135 - 500-1500
3 Atlanta US 1 2 - 1 40- 140
4 Suwanee US 1 2 - 1 24- 133
> queryCP 1
CPid = 1, CPname = Norcross
Direction : DS
Marshalling mode : OOB
Marshalling channel : 141
Communication channel : 500-1500
Modems connected : 1,1 1,2 2,1 2,2 3,1 3,2 4,1 4,2
> queryCP 2
CPid = 1, CPname = Atlanta
Direction : US Downstream CP id :1
Spec Mgr Id : 1 Spec Mgr Port :1
Route Diversity : On
Communication channel : 1-100
Modems connected : 4,1 4,2
Num of prot band :1 Noise threshold : -25.00 dBmV
Error Response
queryPortThSM
Syntax
queryPortThSM <cp id>
Description
This command allows you to show the noise threshold setting for the selected
carrier path.
Parameters
Example Command
> queryPortThSM 2
Successful Response
The threshold is 30.00 dBmV.
Error Response

queryTG
Syntax
queryTG [<tg id>]
Description
This command allows you to show all of the tied groups that have been created
and lists all of the carrier paths associated with each group. This command is
only available in wideband markets using Cornerstone release 8.1 and later.
Parameters
<tg id> is an optional parameter that specifies the ID for a specific tie
group: 1 to 27.
Example Command
> queryTG
> queryTG 1
Successful Response
>queryTG
> Group ID US Carrier Path Band
-------------------------------------------
1 3 NB
5 WB
2 8 NB
7 WB
>queryTG 1
> Group ID US Carrier Path Band
-------------------------------------------
1 3 NB
5 WB
Error Response
No tie groups have been provisioned.
This feature is available only on Wideband system.
setMinMarshDistance
Syntax
setMinMarshDistance <cp id> <HE to nearest vp>
Description
This command sets the minimum distance, in kilometers, between the head
end and the nearest Voice Port assigned to the specified downstream carrier
path.
This command is valid only when the marshalling mode is in band.
Parameters
<HE to nearest vp>
is the minimum distance between the head end and nearest
Voice Port (in km): 0 to 100.
Example Command
> setMinMarshDistance 2 2
Successful Response
OK.
Error Response
Specified CP does not exist
Specified CP is not a downstream CP.
The marshalling mode is not IB.

setModemRxPower
Syntax
setModemRxPower <dmc id> <modem id> <us rx power>
Description
This command allows you to set the specified modem upstream receiving
power level.
Parameters
<us rx power> is the upstream receiving power level for the modem
(in dBmV):
Model 1 DMC: 0 to 20
Model 2 and Model 3 DMC: –5 to 20
Example Command
> setModemRxPower 5 1 15
Successful Response
Input power lever of modem 1 on DMC 5 set to 15 dBmV.
Error Response
setModemTxPower
Syntax
setModemTxPower <dmc id> <modem id> <ds tx power>
Description
This command allows you to set the specified modem downstream
transmission power level.
Parameters
<ds tx power> is the downstream transmitted power level for the modem
(in dBmV): 25 to 55
Example Command
> setModemTxPower 5 1 35
Successful Response
Modem 1 on DMC 5 transmission power level set to 35 dBmV.
Error Response

setPortThSM
Syntax
setPortThSM <us cp id> <threshold value>
Description
This command allows you to set the noise threshold power level for the
selected upstream carrier path.
Parameters
<us cp id> is the carrier path: 1 to 56.
<threshold value>
is the maximum acceptable RF noise level for channels
associated with the carrier path (dBmV x 100): -3375 to 3000
(in increments of 25)
Note: An input of -2500 corresponds to -25.00 dBmV..
Note: The Spectrum Manager converts the value entered into
an equivalent dBmV value that is used to determine if the
channel is acceptable for voice communication.
Example Command
> setPortThSM 2 425
Successful Response
The threshold of CP 2 is set to 4.25 dBmV.
Error Response
Specified path is not used for upstream.
Invalid threshold value
setProtBandCP
Syntax
setProtBandCP <us cp id> <num pb>
Description
This command allows you to set the minimum number of 2 MHz upstream
frequency protection bands to the specified upstream carrier path before
alarming.
To avoid affecting service, the bandwidth of the specified path must be
sufficient to support the given protection bands in addition to all the assigned
modems. Refer to “queryCP” on page 4-57 to determine the availability of the
bandwidth.
Parameters
<us cp id> is the carrier path: 1 to 56.
<num pb> is the minimum number of protection bands: 0 to 14.
Example Command
> setProtBandCP 12 2
Successful Response
2 protection channel bands are reserved for carrier path
12.
Error Response
Specified path is not an upstream carrier path.
Insufficient spectrum available for protection band assignment.

setRouteDiversity
Syntax
setRouteDiversity <us_cp> <mode>
Description
This command lets you change route diversity settings for the specified carrier
path. It is available in CsV06.2 and later releases.
Use this command in systems that do not use diversely-routed fiber paths; this
minimizes service impacts resulting from the HDT’s response to fiber outages.
If your system supports redundant fiber paths, do not disable route diversity;
otherwise, Voice Port recovery times will increase significantly in the event of
a fiber switch.
Parameters
<us_cp> is the upstream carrier path id: 1 to 56.
<mode> is the route diversity mode for this carrier path: OFF or ON
Example Command
> setRouteDiversity 2 off
Successful Response
Turning RouteDiversity OFF for a CP that actually has multiple routes can increase
the recovery time for a route switch from under 5 minutes to over an hour.
Are you sure you want to turn RouteDiversity OFF for CP: 2?
>yes
Ok.
The RouteDiversity for CP 2 is set to OFF.
Error Response
tieCP
Syntax
tieCP <tied group id> <carrier path id> <carrier path id>
Description
This command allows you to tie logical upstream carrier path’s together as a
single physical upstream. When tieing carrier paths together, 1 narrowband
and 1 wideband carrier path must be tied together and the marshalling channel
must be in the narrowband spectrum. This command is only available in
wideband markets using Cornerstone release 8.1 and later.
Parameters
<tied group id> is the ID for that identifies a particular group of carrier paths
that are tied: 1 to 27.
<carrier path id> is the ID associated with a provisioned upstream carrier
path: 1 to 56.
Example Command
> tieCP 1 1 4
Successful Response
Carrier paths have successfully been tied together.
Error Response
Invalid upstream carrier path id. No carrier paths have been tied together.
Carrier path is already tied together. Command rejected.
Carrier path id is out of range. No carrier paths have been tied together.
Too many carrier path id’s specified. No carrier paths have been tied together.
Two upstream carrier path id’s must be identified. No carrier paths have been
tied together.
Marshalling channel must be narrowband. No carrier paths have been tied
together.
Carrier path frequencies are overlapping. No carrier paths have been tied
together.
Wideband must be set to use this command. Command rejected.
Invalid group id. No carrier paths have been tied together.
No response from modem shelf. No carrier paths have been tied together.
Tied Group ID already exists. Command rejected.
Both CPs are NB. Only NB and WB carrier paths can be tied.
Both CPs are WB. Only NB and WB carrier paths can be tied.
No marshalling channel allocated. No carrier paths have been tied together.

untieCP
Syntax
untieCP <tied group id>
Description
This command allows you to logically separate the two carrier paths that were
assigned to a group. This command is only available in wideband markets
using Cornerstone release 8.1 and later.
Parameters
<tied group id> is the ID for that identifies a particular group of carrier paths
that are tied: 1 to 27.
Example Command
> untieCP 1
Successful Response
Carrier paths have successfully been removed from the
group.
Error Response
Invalid group id. No carrier paths have been untied.
No response from modem shelf. No carrier paths have been untied.
CVPROV CI commands
Use the Voice Port provisioning commands to provision and deprovision
customers’ cable TV and phone services.
Table 4-8
CVPROV CI commands
addLine page 4-71
asgnVpHEM page 4-73
CATV page 4-74
chgVpID page 4-75
clearTstAcc page 4-76
correlate page 4-77
cpCapacity page 4-78
deasgnVP page 4-79
delLine page 4-80
enableconc page 4-81
modemCapacity page 4-82
movevp page 4-83
queryCapacity page 4-84
queryEncryption page 4-85
queryLCMsvc page 4-86
queryLCTemplate page 4-87
queryMVIsvc page 4-88
queryTstAcc page 4-89
queryVpSvc page 4-90
queryWideband page 4-91
setEncryption page 4-92
setLCTemplate page 4-93

Table 4-8
CVPROV CI commands
setLoopCurrent page 4-94
setTstAcc page 4-95
setWideband page 4-96
VPmap page 4-97
RF concentration
Figure 4-1 shows an example of the CVPROV commands when RF
concentration is enabled.
Figure 4-1
RF concentration enabled
>addline
Next par is: <Id Type> {Alias <Alias> STRING,
VP <ID> {1 TO 4294967295} }
Enter: <Id Type> <Line Number> <Service Type>
>alias engleman 1 MVIPOTS

Next par is: <Host ID> {1, 5}
Enter: <Host ID> <CRV> <Conc Mode> {ON, OFF}
>1 10 on
The line was allocated with a 1-based LC instance: 6
Provisioning accepted, check LC LOG for service activation.
Figure 4-2 shows an example of the CVPROV commands when RF

concentration is not enabled.
Figure 4-2
RF concentration not enabled
>addline
Next par is: <Id Type> {Alias <Alias> STRING,
VP <ID> {1 TO 4294967295} }
Enter: <Id Type> <Line Number> <Service Type>
>alias engleman 1 MVIPOTS

Next par is: <Host ID> {1, 5}
Enter: <Host ID> <CRV>
>1 10
Provisioning accepted, check LC LOG for service activation.
Note: When RF concentration is enabled using the optionality feature, the new
conc mode parameter appears. This may require some changes to your
existing provisioning scripts.

addLine
Syntax
addLINE <id type> <line_number> <svc_type>
Description
Provisions a line service to be either a MVI POTS, LCM POTS, V5.2 POTS,
or EBS.
Parameters
page 4-2).
<line_number> is the line number, 1 to 24, on the Voice Port.
<svc_type> <device>
is the service to be provisioned. The supported types are:
LCMPOTS <vlcm> <lsg> <slot> [<conc>] — service is
provisioned against a VLCM number, lsg number, and slot
number. The VLCM number ranges from 1 to 7. The lsg
number is from 0 to 19. The slot number is from 0 to 31.
LCMPOTS service applies to Chile, Japan and DMS100.
V5POTS <if> <port> [<conc>] — service is provisioned
against a V5.2 interface and port ID. The interface ID ranges
from 1 to 16777215. The port ID ranges from 0 to 32767.
MVIPOTS <host> <crv> [<conc>]
EBS <host> <crv> — service is provisioned against host id and
Call Reference Value. The host id is 1 to 5. CRV ranges from
1 to 2048.
<conc> is a flag to indicate if the line is concentrated or non-
concentrated. Enter ON for a concentrated line and OFF for a
non-concentrated line. The choice for the flag can only be
entered if the RF Concentration feature is enabled in
Cornerstone optionality for MVIPOTS, LCMPOTS, and
V5POTS.
Example Command
Adding a (Voice Port=16780139, Line Card=1) as a V52POTS (Interface
ID=111, Port ID=95) w/RF Concentration
ex1> addLine VP 16780139 1 V5POTS 111 95 ON
Adding a (ALIAS "SUMMIT BLDG 1" Line Card=7) as V5 POTS (Interface

ID=222, Port ID=13) w/o RF Concentration
ex2> addLine ALIAS "SUMMIT BLDG 1" 7 V5POTS 222 13 OFF
Successful Response

Provisioning accepted, check LC LOG for service
activation.
Error Response
CRV value is used by another MVI line service.
The specified host is not assigned to a TR303-MVI switch. Please use the
Host Prov Mgr tool over OPC to verify.
The EBS feature has not been enabled.
The EBS Feature is not enabled on the Cornerstone HDT. Enable it via
CSOPTCI or provision a difference service.
The specified Interface ID does not exist.
The specified <if_id> is not provisioned on the Cornerstone HDT. Use
the queryV5 CI to identify provisioned Interface ID values.
The specified Port ID has already been used.
Identify a Port ID value that is not in use via the queryFreePort command.
RF Concentration not Enabled.
The RF Concentration Feature is not enabled on the Cornerstone HDT.
Enable it via CSOPTCI or set the <rf_conc> flag to OFF.
Provisioning rejected, that line already exists.
Instance 7 has been deallocated.
The specified line number is not available for the specified voice port.
Instance 7 has been deallocated.
The EBS feature has not been enabled.
The addline command has been rejected.
Please use the CSOPTCI tool to enable this feature before attempting to
rovision service.
The specified host, CRV is used by a TR-303 service.

asgnVpHEM
Syntax
asgnVpHEM <id type> <dmc id> <modem id>
Description
This command allows you to assign a Voice Port to a headend modem with
CATV enabled.
This command has been deleted from CsV06.
Parameters
page 4-2).
<modem id> is the modem: 1 or 2.
Example Command
> asgnVpHEM ALIAS ‘Voice Port ABC’ 1 1
> asgnVpHEM VP 123456 1 1
Successful Response
Voice Port alias ‘Voice Port ABC’ assigned to DMC1
modem 1.
Voice Port 123456 assigned to DMC 1 modem 1.
Error Response
Voice Port was assigned to another upstream path than the one connecting to
the specified headend modem.
All 24 PCM channels are used by the specified modem.
The voice port is already assigned to a different HEM.
CATV
Syntax
CATV <id type> <catv status>
Description
This command allows you to turn on or turn off a CATV service by either
specifying Voice Port alias or Voice Port id.
This command is not supported for Multi-line Voice Ports (MVP) or the Max
24 voice port. An MVP will indicate that CATV service has been enabled even
though the Voice Port does not support CATV.
Parameters
page 4-2).
<catv status> is ON or OFF.
Note: This command defaults to OFF for Chile and Dutch
loads, ON for all other loads.
Example Command
> CATV VP 123456 ON
> CATV ALIAS ‘Voice_Port_ABC’ OFF
Successful Response
CATV service turned ON for Voice Port 123456.
CATV service turned OFF for VP Alias Voice_Port_ABC.
Error Response
This command is not applicable.

chgVpID
Syntax
chgVpID <old vp id> <new vp id>
Description
This command allows you to change an old Voice Port id to a new one when a
Voice Port is replaced. Use this command if your cable system strictly uses vp
id, not Voice Port alias, to provision a service.
Once a Voice Port is detected, the system generates a database record to
monitor the equipment. This command triggers the deletion of the old Voice
Port equipment record and changes the association of the provisioning record
from the previous Voice Port id to the newly installed Voice Port id.
When detecting a Voice Port, the system generates an equipment record and a
provisioning record, if needed, and associates both records with the Voice Port
id.
When the Voice Port is replaced by a new one, the system generates a second
equipment record. The provisioning record is still associated with the previous
Voice Port id. The system deletes the equipment record of the first Voice Port
and changes the provisioning record association to the new Voice Port id.
Parameters
<old vp id> and
<new vp id> are the decimal ids of the old and new Voice Ports
respectively: 1 to 4294967295.
Note: Voice Port aliases cannot be used in this command.
Example Command
> chgVpID 123456 112233
Successful Response
Warning: This command will affect service.
Yes
Ok.
Error Response
The specified original Voice Port id does not exist.
The specified new Voice Port id is already in use.
clearTstAcc
Syntax
ClearTstAcc <vp id> <line>
<line> {2, 4, 6, 8, 12, 16, 24}
Description
This command deprovisions a line that was previously provisioned for Digital
Test Access (DTA). It applies only to E1-based systems.
Parameters
<vp id> is the Voice Port id: 1 to 4294967295.
<line> is the Voice Port line previously provisioned for DTA.
Example Command
> cleartstacc 16798981 8
Successful Response
This will deprovision the following DTA line:
Voice Port:16788981
Line Card:2
>Yes
Command is in progress, check LC LOG for result.
Error Response
Line 8 is not a valid DTA line for VP 16798981.
Line 8, 16, or 24 must be used for Test Access on VP 16798981.
The specified Voice Port provisioning record does not exist.
Line number <line> is not provisioned with DTA service.

Correlate
Syntax
Correlate <vp alias> <vp id>
Description
This command associates a Voice Port alias with a VPID.
The Cornerstone HDT generates an equipment record upon detecting a Voice
Port for the first time. If a provisioning record does not exist for the Voice
Port, the HDT also creates a provisioning record using the VPID.
Preprovisioning a Voice Port using an alias also generates a provisioning
record. The correlate command merges both provisioning records into one
and relates this record to the equipment record of the same VPID.
If the preprovisioned line is a POTSRT or a MVIPOTS, refer to LC LOG for
the provisioning result.
If the alias is already associated with a VPID, the new VPID overrides the
existing one. This allows another Voice Port to replace an installed Voice Port
that malfunctions.
Parameters
<vp alias> is the Voice Port alias (see “Voice Port aliases” on page 4-2).
<vp id> is is the Voice Port id: 1 to 4294967295.
Example Command
> correlate ‘a_Voice Port_name’ 123456
Successful Response
Warning: This will affect service on the Voice Port.
Please confirm (“Yes” or “No):
>Yes
OK
Error Response
Neither the specified voice gate id nor the specified alias exist.
The specified VP id is already in use.
Unable to send message to modem shelf: BmBadLink.
cpCapacity
Syntax
cpCapacity [<us cp id>]
Description
This command allows you to display the total upstream capacity in terms of
total available PCM channels on the carrier path for provisioning of dedicated
lines. The display can be focused on one upstream carrier path, if the
parameter is specified; or towards all upstream carrier paths.
Parameters
[<us_cp_id>] optional parameter; specifies the carrier path id: 1 to 56.
Example Command
> cpCapacity
Successful Response
Num Num Total Num
# NonConc Conc Proved Avail
CPid CPname modem Lines Lines Lines Chans
==== ==================== ===== ======= ====== ====== =======
2 US_IB1 6 0 177 177 144
4 US_OOB1 10 0 646 646 240
6 US_OOB2 6 5 142 147 139
7 US_OOB3 6 0 231 231 144
Error Response
The specified carrier path is not provisioned for upstream.

deasgnVp
Syntax
deasgnVp <id type>
Description
This command allows you to delete the Voice Port provisioning data.
This command is typically useful when tenants change in an apartment
complex.
If this command is intended to move Voice Port to a different modem, make a
copy of the Voice Port id along with all the provisioning data. The following
commands are useful when recovering those provisioning data: asgnVpHEM
or asgnVpCP, addLine, CATV, and correlate.
Parameters
page 4-2).
Example Command
> deasgnVp ALIAS ‘new_customer_4567890’
Successful Response
Warning: VP will be de-provisioned.
>Yes
OK
Error Response
delLine
Syntax
delLine <id type> <line number>
Description
This command allows you to delete a line service.
Parameters
page 4-2).
<line number> is the line number being deleted: 1 to 24.
Example Command
> delLine VP 123456 2
Successful Response
This will deprovision the following subscriber on the
Voice Port:
Voice Port: 123456

Line Card: 2

>y
Command is in progress, check LC LOG for result.
Error Response

enableConc
Syntax
enableConc <unit>
Description
Modifies the RF Concentration mode from non-concentrated to concentrated
for the specified unit. In order to execute this command, concentration must
first be enabled using the CSOPTCI toolset. Enabling concentration is
password protected. This command is not service affecting.
Parameters
<unit> is the type of equipment for which the RF Concentration mode
will be changed. Use one of the following:
ALL — all lines on the HDT.
CP <us_id> — all lines on the specified carrier path: 1 to 56.
HEM <DMC> <modem> — all lines on the specified HEM.
LINE <vp> <line> — a single line. The <vp> parameter is either
ALIAS <alias> or VP <id> to specify a Voice Port by alias or
VPID. The <line> parameter specifies the line on the Voice
Port: 1 to 24.
Example Command
> enableConc LINE VP 11523 1
> enableConc HEM 3 1
> enableConc CP 6
> enableConc ALL
Successful Response
WARNING! RF concentration will be rejected for UAP-2
resident lines. All other lines on the specified unit will
have their concentration mode changed from OFF to ON.
>Yes
Proceeding with command! UAP-2 resident line cards will be ignored.
Error Response
The specified HEM does not exist.
The specified Carrier Path does not exist.
Enableconc command is unavailable. RF concentration is not enabled.
The specified line is already provisioned as a concentrated line.
The specified line card provisioning record does not exist.
Concentration mode can not be enabled. The specified line has TR-08 service.
Specified upstream CP does not exist.
I’m sorry, that optionality code is invalid for this system. Please contact your
Cornerstone Sales Representative to obtain a valid code.
modemCapacity
Syntax
ModemCapacity <cp id>
Description
This command allows you to focus on the PCM channels consumed by those
Voice Ports grouped on HEMs assigned to the specified upstream carrier path.
Parameters
Example Command
> modemCAPACITY 2
Successful Response
CPid = 2, CPname = US_IB1
Num Num Total Num

modem NonConc Conc Proved Avail
id Lines Lines Lines Chans
========== ======= ====== ====== ======
DMC 8 1 0 24 24 24
DMC 8 2 0 24 24 24
DMC 10 1 0 34 34 24
DMC 10 2 0 47 47 24
DMC 1 1 0 24 24 24
DMC 1 2 0 24 24 24
Error Response
The specified carrier path is not provisioned for upstream.
No modem is provisioned.

Movevp
Syntax
movevp <Id type> <to DMC> <modem>
Description
This CsV04 and later command allows you to move a Voice Port from one
HEM to another. This command allows headend engineering of RF
concentration.To be used properly, the following items must be true:
• the Voice Ports must have all lines provisioned as concentrated
• the destination HEM must not have any non-concentrated, provisioned
lines.
Lines in a “Traffic busy” state are not moved. If this command is used to move
a Voice Port that is OOS to another HEM, the Voice Port state becomes IS at
the new HEM.
Parameters
<id type> is a specific Voice Port or all Voice Ports on a HEM; one of
the following:
ALIAS <alias> — specifies a Voice Port by its alias.
VP <id> — specifies a Voice Port by VPID: 1 to 4294967295.
MODEM <DMC> <modem> — specifies all Voice Ports on the
specified DMC and modem.
<to DMC> is the destination DMC: 1 to 14.
<modem> is the destination modem: 1 or 2.
Example Command
> movevp vp 12345678 4 1
Successful Response
Working. Please wait.
Moving VP 12345678.
Moving VP 12345678 to a different CP?
>Yes
Moving VP 12345678.
Moved VP 12345678.
Done.
Total Voice Ports moved: 1
Total Lines moved: 2
Error Response
RF Concentration must be enabled to use movevp.
The NE is not a DFA type. Command aborted.
Alias <alias name> not found.
VP ID <msn> not found.
Absence of Voice Ports
NO VP found on source DMC <dmc #> <modem #>.
MOVEVP aborted. Destination HEM cannot exceed 240 lines provisioned.
Non-conc Line Message
queryCapacity
Syntax
queryCapacity <unit>
Description
This CsV04 and newer command displays the capacity data for the specified
unit. It displays the following information on a per HEM basis:
• number of non-concentrated lines
• number of concentrated lines
• total lines provisioned
• number of RF Channels available for concentrated lines
Parameters
<unit> equipment for which the RF Concentration data will be
displayed. The display can be for all lines on a HEM, all lines
on a carrier path, or all provisioned lines:
ALL — all provisioned lines.
CP <us_cp> — all lines on the specified upstream carrier path:
1 to 56.
HEM <DMC> <modem> — all lines on the specified DMC
(1 to 14) and modem (1 to 2).
Example Command
> queryCapacity HEM 3 1
> queryCapacity CP 6
> queryCapacity ALL
Successful Response
Num Num Total Avail Ch
HEM NonConc Conc Proved for Conc
id Lines Lines Lines Lines
=== ======== ===== ====== ==========
1 1 1 2 23
Error Response
The specified Carrier Path does not exist.
No DMC card present for this HEM id.
HEM 2 is unprovisioned.
The specified carrier path is not provisioned for upstream
No modem assigned to the specified US CP id

queryEncryption
Syntax
queryEncryption
Description
Use this CSV05.2 and newer command to display encryption status for the
HDT.
Note: The queryEncryption command is available only if encryption has been
enabled for the HDT (using the Enable command). Encryption also requires
the Model 3 DMC.
Parameters
None.
Example Command
queryEncryption
Successful Response
Encryption for this HDT is ON.
queryLCMsvc
Syntax
queryLCMsvc [<vlcm number> <LSG number> <slot number>]
Description
This command allows you to display provisioning data regarding LCM
services.
Parameters
If you do not specify any parameters, the provisioning data for all LCM lines
is displayed. Otherwise, LCM lines are displayed to level of detail specified.
<LSG number> is the line subgroup number: 00 to 19.
<slot number> is the slot number within the LSG: 0 to 31.
<vlcm number> is the virtual line concentration module id: 1 to 7 or all.
Example Command
ex1> queryLCMsvc 2
ex2> queryLCMsvc 2 0
ex3> queryLCMsvc 8 19 31
Successful Response
%% ex 1> queryLCMSvc
VLCM LSG Slot VP VP Line Srvc Provisioning
# # # id alias # Type Status
---- --- ---- ---------- -------------------- ---- ------- -------------
1 0 0 C. Smith 2 LCMPOTS Head End OnlyNote 1
1 0 1 112233 1 LCMPOTS Head End OnlyNote 1
2 0 3 112234 D. Alda 1 LCMPOTS Head End OnlyNote 1
2 1 2 - - - LCMPOTS Switch OnlyNote 2
8 19 31 123456 B. Goodall 2 LCMPOTS CompletedNote 3
%% ex 2> queryLCMsvc 2
---- --- ---- ---------- -------------------- ---- ------- -------------
2 1 2 - - - LCMPOTS Switch OnlyNote 2
%% ex 3> queryLCMsvc 2 0
---- --- ---- ---------- -------------------- ---- ------- -------------
%% ex 4> queryLCMsvc 8 19 31
---- --- ---- ---------- -------------------- ---- ------- -------------
8 19 31 123456 B. Goodall 2 LCMPOTS CompletedNote 3
Note 1: The data displayed originated from one or more CVPROV commands.
(for example, addLine, correlate, asgnVpHEM, etc.)
Note 2: The data displayed originated from a DMSX switch.
Note 3: The data displayed originated from one or more CVPROV commands
and a DMSX switch.
Error Response
No LCM service is provisioned.

queryLCTemplate
Syntax
queryLCTemplate
Description
This command queries the database on the APU and displays the template type
that is allowed to be provisioned on the Network Element. The available
template types are:
• NORTH_AMERICAN_STANDARD (7 dB Rx / 5 dB Tx loss plan)
• NORTH_AMERICAN_HIGH (3 dB Rx / 3 dB Tx high-gain loss plan)
• CHILE_PHILIPPINES
• JAPAN
• GERMANY
• NETHERLANDS
• AUSTRALIA
• AUSTRIA
• SPAIN
• FRANCE
• ARGENTINA
• BRAZIL
• COLUMBIA
• VENEZUELA
• IRELAND
• SWEDEN
• CZECH REP
• HUNGARY
• HOLLAND
• PORTUGAL
• POLAND
Parameters
None.
Example Command
> queryLCTemplate
Successful Response
Country specific line card template is region
Error Response
Cannot query at this time.
queryMVIsvc
Syntax
queryMVIsvc <record type> <host> <CRV begin> <CRV end>
Description
Queries provisioning information regarding MVI services. This command is
available in CsV04 and newer releases.
Parameters
< record type > specifies the type of CRVs to search for: USED to search for
provisioned CRVs or FREE to search for available CRVs.
< host > is the host ID: 1 to 5
< CRV begin > is the beginning CRV in the range to search: 1 to 2048
< CRV end > is the ending CRV in the range to search: 1 to 2048
Example Command
> querymvisvc used 1 2 5
Successful Response
Host CRV Valid VP VP Line Srvc
# # Combo Id alias # Type
--- --- ----- ----------- ------------------ ---- ----
1 2 YES 16798171 T.Jones 1 MVIPOTS
1 3 YES 16798172 J.Wayne 2 EBS
1 4 YES 16798170 J.Stewart 1 EBS
1 55 YES 16798145 K Douglas 2 MVIPOTS
Error Response
Bad input: number of parameters is 104.
Command must include the record type and a host ID. The acceptable record
type parameters are USED or FREE. Re-enter the command with USED to
search for provisioned CRVs or free to search for available CRVs.
The acceptable range for a host ID is 1 to 5. Please re-enter the command
making sure the first parameter is between 1 and 5.
The acceptable range for CRV values is 0 to 2048. Please re-enter the
command making sure the second parameter is between 0 and 2048.
The acceptable range for CRV values is 0 to 2048. Please re-enter the
command making sure the third parameter is between 0 and 2048 and that it
is greater than the second parameter.
No MVI Services are provisioned.

queryTstAcc
Syntax
QueryTstAcc
Description
This command lists all Voice Port lines previously provisioned for Digital Test
Access (DTA).
Parameters
None.
Example Command
> querytstacc
Successful Response
VP id Line # Mapper Port DS0
---------- ------ ------ ---- ---
54095 4 G1 1 20
Error Response
There are no DTA lines provisioned.
queryVpSvc
Syntax
queryVpSvc <id type>
Description
Display services provisioned on either the specified Voice Port, or all the
Voice Ports assigned to the specified modem or carrier path.
For CsV06, this command has been changed to include line card status for
each line provisioned. For digital test access lines only, a column showing
digital test access status is provided.
For CsV06.2, this command provides loop current status for Voice Ports that
support provisionable loop current (Voice Ports that do not support this feature
show N/A in this field).
Parameters
<id type> specifies one or more Voice Ports:
ALIAS <alias> — specifies a Voice Port by alias, where <alias>
is a 20-character string enclosed in single quotation marks (see
“Voice Port aliases” on page 4-2).
VP <id> — specifies a Voice Port by VPID: 1 to 4294967295
MODEM <DMC> <modem> — all Voice Ports on the specified
DMC (1 to 14) and modem (1 to 2).
CP <id> — all Voice Ports on the specified carrier path: 1 to 56
Example Command
ex 1> queryVpSvc VP 123456
ex 2> queryVpSvc MODEM 1 1
Successful Response
VP id VP alias Prov Modem CATV
========== ==================== ========== ====
16801614 DMC 14 1 on
L1: Service LC Host Conc LC LoopC

Type Instance id CRV Mode State Status
------- --------- ---- ---- ---- ------- ------
MVIPOTS 1 1 1 ON IS NORM
L2: Service LC Host Conc LC LoopC

Type Instance id CRV Mode State Status
------- --------- ---- ---- ---- ------- ------
MVIPOTS 62 2 7 ON IS HIGH
Error Response
Specified Voice Port id does not exist
Specified modem id does not exist.
No Voice Port assigned to the specified modem id.

queryWideband
Syntax
QueryWideband
Description
This command queries the status of the system based wideband flag.
Example Command
> queryWB
Successful Response
Case 1> The Wideband Flag is Currently Enabled.
Case 2> The Wideband Flag is Currently Disabled.
Error Response
Unable to read database.
No Response from modem shelf.
setEncryption
Syntax
setEncryption <mode>
Description
Use this CSV05.2 and newer command to enable or disable encryption for the
HDT.
Note: The setEncryption command is available only if encryption has been
enabled for the HDT (using the Enable command). Encryption also requires
the Model 3 DMC.
Parameters
<mode> is the desired encryption setting: ON or OFF.
Example Command
> setEncryption ON
Successful Response
Encryption for this HDT is ON.

setLCTemplate
Syntax
setLCTemplate <region>
Description
This command sets the LC template to an integer value which is used by Voice
Ports to determine which template to use.
Using this command requires that you reset all DMCs on the HDT.
Parameters
<region> specifies the line card template for a region, one of:
• NORTH_AMERICAN_STANDARD (7 dB Rx / 5 dB Tx loss plan)
• NORTH_AMERICAN_HIGH (3 dB Rx / 3 dB Tx high-gain loss plan)
• CHILE_PHILIPPINES
• JAPAN
• GERMANY
• NETHERLANDS
• AUSTRALIA
• AUSTRIA
• SPAIN
• FRANCE
• ARGENTINA
• BRAZIL
• COLUMBIA
• VENEZUELA
• IRELAND
• SWEDEN
• CZECH REP
• HUNGARY
• HOLLAND
• PORTUGAL
• POLAND
Example Command
> setLCTemplate JAPAN
Successful Response
The line card template is set to JAPAN.
Please reset DMC to make new LC template effective.
Error Response
Unable to send message to Modem Shelf.
Internal error, please check the swerr log.
setLoopCurrent
Syntax
setLoopCurrent <id type> <line number> <current>
setLoopC <id type> <line number> <current>
Description
This command sets high or normal loop current on the specified line. Applies
only to Voice Ports that support provisionable loop current.
This command is available in CsV06.2 and later releases.
Note: Only eight lines per Voice Port can be set to HIGH. The rest have to be
set to NORM.
Parameters
<id type> specifies one or more Voice Ports:
ALIAS <alias> — specifies a Voice Port by alias, where <alias>
is a 20-character string enclosed in single quotation marks (see
“Voice Port aliases” on page 4-2).
VP <id> — specifies a Voice Port by VPID: 1 to 4294967295
<line number> is the line number to provision: 1 to 24.
<current> is the loop current to use on this line: NORM or HIGH.
Example Command
setloopc vp 16801901 2 high
Successful Response
OK
Error Response
The specified line card provisioning does not exist.
Line specified is unavailable on the VP.
Find out how many lines the specified Voice Port has.
The Line is provisioned with DTA service.
SetLoopCurrent command is rejected
Do not attempt to set loop current on a line provisioned as Digital Test
Access (DTA).
The hardware specified does not support this command.
SetLoopCurrent command is rejected.
The specified Voice Port does not support provisionable loop current. You
will see this message only if the specified Voice Port has already been
marshalled.
Unable to send message to modem shelf.
Out of range parameter entered.
The specified Voice Port or line number are not in the ranges shown
above.
Internal Error: invalid response code from the modem shelf.
Internal Error: please check the swerr log.

setTstAcc
Syntax
settstacc <vp id> <line> <mapper> <port> <DS0>
<line> {2, 4, 6, 8, 12, 16, 24}
Description
This command provisions a Voice Port line for Digital Test Access (DTA).
Parameters
<vp id> is the Voice Port serial number: 1 to 4294967295
<line> is the Voice Port line number on the Voice Port: 2, 4, 8, 12,
16, or 24.
<mapper> is the mapper: g1, g2 or g4
<port> is the mapper port number: 1 to 7 for an E1 system; 1 to 14 for
a DS1 system
<DS0> is the DS0 time slot to use for DTA: 1 to 31 for an E1 system;
1 to 24 for a DS1 system.
Example Command
> settstacc 16798981 8 g1 1 1
> settstacc 16798981 16 g1 1 1
> settstacc 16798981 24 g1 1 1
Successful Response
Provisioning accepted, check LC LOG for service
activation.
Error Response
Line number 8 is not provisioned with DTA service.
Line 8, 16, or 24 must be used for Test Access on VP 16798981.
The specified line card provisioning record does not exist.
setWideband
Syntax
SetWideband on
SetWideband off
Description
This command enables and disables wideband channels on the HDT. If you
answer “YES”, the Cornerstone software checks the Spectrum Manager PEC
codes to verify the ability to support wideband. The system based wideband
flag is then set. All command prompts and checks for the upstream channel
numbers will use a maximum US channel code of 234. If a system is not
wideband enabled, the number will be 144.
Example Command
setWideband on
Successful Response
The system is now a wideband system.
The system is now a narrowband system.
Error Response
Installed Spectrum Manager(s) do not support this feature.
Wideband Channels are still provisioned on carrier paths.
Unable to Write DataBase.
No Response from Modem Shelf.
At least 1 tied group present. Cannot turn Wide Band OFF.

VPmap
Syntax
VPmap <LC inst>
Description
This command allows you to display the Voice Port id, alias, modem CATV,
service type, line card instance, and service specific data.
Parameters
<LC inst> is the line card number: 1 to 3360.
Example Command
> vpmap 7
Successful Response
VP id VP alias Prov Modem CATV
========== ==================== ========== ====
16799308 T Jones DMC 1 1 on
L1: Service LC VLCM LSG Slot Conc

Type Instance Number Number Number Mode
------- --------- ------ ------ ------ ----
LCMPOTS 1 1 0 0 ON
Error Response
No line card uses the specified LC instance number.
CVSPMN CI commands
Use the Spectrum Manager maintenance commands to perform spectrum
maintenance.
Table 4-9
CVSPMN CI commands
chanMap page 4-99
chgChanState page 4-100
freqMap page 4-101
querychannel page 4-102

qchan
queryRF page 4-103

QRF

chanMap
Syntax
chanMap <direction> <low chan> <high chan>
Description
This command allows you to display mapping from channels to frequencies.
Parameters
DS (downstream).
<low chan> is the lowest channel number: 1 to 144(narrowband upstream);
1 to 234 (wideband upstream) or 98 to 1562 (downstream)
<high chan> is the highest channel number: 1 to 144(narrowband
upstream); 1 to 234 (wideband upstream) or 98 to 1562
(downstream)
Example Command
> chanMap US 144 148
> chanMap DS 1 50
Successful Response
Downstream:
Channel Frequency (kHz)
------- ---------------
55 18944
56 19200
57 19456
58 19712
59 19968
60 20224
Upstream:
------- ---------------
144 41728
145 42240
146 42496
147 42752
148 43008
Error Response
None.
chgChanState
Syntax
chgChanState <cp id> <channel number> <new state> [FORCE]
Description
This command allows you to change the service state of a channel in the
spectrum range allocated for use on the specified carrier path. This allows the
channel’s status to be updated while controlling its availability for assignment
to a modem. If the channel to be taken out of service (OOS) is active, you can
only change the status to OOS if the FORCE flag is set to TRUE; otherwise,
the command will be rejected.
Parameters
<channel number>
is the number of the channel whose state will change:
1 to 144 (narrowband upstream), 1 to 234 (wideband
upstream) or 98 to 1562 (downstream).
<new state> is the new state of the channel(s): IS or OOS.
FORCE optional parameter; use it to take an active channel out of
service.
Example Command
> chgChanState 2 200 IS
> chgChanState 2 200 OOS
Successful Response
The following response is only received when changing a channel(s) from In
Service to Out of Service. There is no response when changing a channel from
Out of Service to In Service.
This will take the specified channel OOS.

>Yes
OK
Error Response
Channel already in requested state.
Invalid carrier path id. (Specified carrier path is out of range or not
provisioned.)
Specified channel is out of range for an US carrier path.
item not provisioned.

freqMap
Syntax
freqMap <direction> [<low freq> <high freq>]
Description
This command allows you to display mapping from frequencies to channels.
Parameters
DS (downstream).
<low freq> when specifying a range of frequencies, this is the lowest
frequency in the range. The default is to display all
frequencies in the specified direction. The range is 5 to 42
(narrowband upstream), 5 to 65 (wideband upstream) or 375
to 750 (downstream).
<high freq> when specifying a range of frequencies this is the highest
frequency in the range. The range is 5 to 42 (narrowband
upstream), 5 to 65 (wideband upstream) or 375 to 750
(downstream).
Example Command
> freqmap US 41 42
> freqMap DS 400 410
Successful Response
Downstream:
------- ---------------
1 5120
2 5376
3 5632
4 5888
5 6144
Upstream:
------- ---------------
141 40960
142 41216
143 41472
144 41728
145 41984
146 42240
147 42496
148 42752
149 43008
150 43264
151 43520
Error Response
None.
queryChannel/qchan
Syntax
querychannel <cp id> [<low channel> <high channel>]
qchan <cp id> [<low channel> <high channel>]
Description
This command allows you to generate a display giving the status of each of the
specified channels.
• If a range of channels is specified, this command displays RF energy levels
in the range of channels on the specified carrier path.
• If no range is supplied, this command displays the RF energy levels detected
on the currently provisioned channels in the specified carrier path’s
spectrum.
Parameters
<low channel> when specifying a range of channels, this is the lowest
channel in the range. The default is to display all channels in
the specified carrier path. The range is 5 to 42 (narrowband
upstream), 5 to 65 (wideband upstream) or 375 to 750
(downstream).
<high channel> when specifying a range of channels, this is the highest
channel in the range.
Example Command
> querychannel 3 1 1
Successful Response
A Spectrum Availability Report display will be generated.
Error Response
The specified channel XX is invalid.
Invalid carrier path id. (Specified carrier path is out of range or not
provisioned.).
No response from Modem Shelf.

queryRF
Syntax
queryRF <cp id> <range> <dwell time>
qrf <cp id> <range> <dwell time>
Description
This command generates a display of detected RF energy levels on each of the
specified upstream spectrum channels.
Parameters
<low channel> when specifying a range of channels, this is the lowest
channel in the range. The default is to display all channels in
the specified upstream carrier path. The range is 5 to 42
(narrowband upstream), 5 to 65 (wideband upstream) or 375
to 750 (downstream).
<high channel> when specifying a range of channels, this is the highest
channel in the range.
<dwell time> is the dwell time (ms): 0 to 500
Example Command
> queryRF 2 152 162 50
Successful Response
Channel Frequency (kHz) RF Level
---------- ------------------- -----------
152 40.960 -33.75
153 41.216 -33.75
154 41.472 -33.75
155 41.728 -33.75
156 41.984 -33.75
157 42.240 -33.75
158 42.496 -33.75
159 42.752 -33.75
160 43.008 -33.75
161 43.264 -33.75
162 43.520 -33.75
Error Response
The specified channel XX is invalid.
Invalid carrier path id.
No RF Spectrum Manager response. (The RF Spectrum Manager assigned to
the specified carrier path is unequipped or failed).
No response from Modem Shelf.
Invalid carrier path direction.

CVTRAF commands
Use the CVTRAF commands to monitor completed and non-completed calls.
prompts you to reenter the information.
Table 4-10
CVTRAF commands
QueryCallInfo page 4-108
QueryTopBH page 4-109
QueryBHBrief page 4-110
QueryGOS page 4-111
ConcLog page 4-112
CVClear page 4-113

TrafUnits page 4-114
Field definitions
The following table lists and describes the fields that appear as output from the
CVTRAF commands
Table 4-11
CVTRAF output fields
Field Definition
ACB Total number of seconds that all PCM channels were in use
Secs during the reporting period.
Avg Average length of completed calls, in seconds, for the

Hold indicated reporting period.
Avg Average number of PCM channels in use during the reporting

OCC period.
Blk Number of concentrated calls where the subscriber had to

Orig wait at least three seconds for a dial tone.
Blk Number of terminated (incoming) calls that were blocked

Term because of no available PCM channels.
—continued—
Table 4-11 (continued)

CVTRAF output fields
Field Definition
Blk% Number of blocked calls divided by the total number of

concentrated calls times 100.
CCS/ Number of Centum Call Seconds per concentrated and non-

Line concentrated line (0-36). Measures how heavily the modems
have been used where 0 is no usage and 36 is maximum
usage.
Comp Total number of completed non-concentrated calls (originated

Noncon and terminated).
Comp Number of completed concentrated originated calls.
Orig
Comp Number of completed concentrated terminated (incoming)

Term calls.
Conc Number of concentrated lines on the HEM.

Line
Date Date on which the activity was reported.
DS Downstream Carrier Path on which the HEM is located.

CP
HEM Head End Modem number.
Hour Hour of the day (0-23).
Log Type The list of all possible logs.

Operand Indicates how the threshold value will be used to determine
log output.
Min Minimum number of channels available during the reporting

Chan period.
NCon Number of non-concentrated lines.

Line
Rank Ranking of busiest hours where 1 is the busiest.
Status Indicates whether a log has been enabled or disabled.
Threshold User-defined value to indicate which items will appear on log

reports.
US Upstream Carrier Path on which the HEM is located.

CP
—end—

querycallinfo
Syntax
querycallinfo <scope> <time_unit> <time_period>
Description
Displays call statistic totals.
The completed calls counter is limited to recording 65,535 calls on a single
HEM in a single day.
Parameters
<scope> specifies the entity to display call statistics; one of:
CP <cpid> — displays statistics for the specified carrier path.
HEM <DMC> <modem> — displays statistics for the
specified HEM.
ALL — displays statistics for all available entities.
<time_unit> is the amount of time over which to display statistics: Year,
Month, Week or Day
<time_period> is the period on which to display statistics: Curr or Prev (if
the <time_unit> is Month, the time_period can also be Jan,
Feb, Mar, and so on)
Example Command
> querycallinfo hem 2 1 day prev
Successful Response
Hour| Comp | Comp | Comp |Conc|Ncon| CCS/ | Avg |Blk |Blk |Blk% |Min |Avg | ACB
| Orig | Term |Noncon|Line|Line| Line | Hold|Orig|Term| |Chan|Occ | Secs
================================================================================
0 | 0| 0| 0| 0 | 0 | . | 0 | 0| 0| . | 24 | 0 | 0
1 | 0| 0| 0| 0 | 0 | . | 0 | 0| 0| . | 24 | 0 | 0
2 | 0| 0| 0| 0 | 0 | . | 0 | 0| 0| . | 24 | 0 | 0
3 | 0| 0| 0| 0 | 0 | . | 0 | 0| 0| . | 24 | 0 | 0
4 | 0| 0| 0| 0 | 0 | . | 0 | 0| 0| . | 24 | 0 | 0
5 | 0| 0| 0| 0 | 0 | . | 0 | 0| 0| . | 24 | 0 | 0
6 | 0| 0| 0| 0 | 0 | . | 0 | 0| 0| . | 24 | 0 | 0
7 | 0| 0| 0| 0 | 0 | . | 0 | 0| 0| . | 24 | 0 | 0
8 | 0| 0| 0| 0 | 0 | . | 0 | 0| 0| . | 24 | 0 | 0
9 | 0| 0| 0| 0 | 0 | . | 0 | 0| 0| . | 24 | 0 | 0
10 | 0| 0| 0| 0 | 0 | . | 0 | 0| 0| . | 24 | 0 | 0
11 | 0| 0| 0| 0 | 0 | . | 0 | 0| 0| . | 24 | 0 | 0
Error Response
None.

querytopbh
Syntax
querytopbh <scope> <time_unit> <time_period>
Description
Displays peak periods of usage.
Parameters
<scope> specifies the entity to display; one of:
CP <cpid> — displays peak periods for the specified carrier
path.
HEM <DMC> <modem> — displays peak periods for the
specified HEM.
ALL — displays peak periods for all available entities.
<time_unit> is the amount of time over which to display statistics: Year,
Month, Week or Day
<time_period> is the period on which to display statistics: Curr or Prev
Example Command
> querytopbh hem 14 1 month curr
Successful Response
Rank|Modem| Date |Hour| Comp | Comp | Comp |Conc|Ncon|CCS/ | Avg |Blk |Blk |Blk%
| | | | Orig | Term |Noncon|Line|Line|Line | Hold|Orig|Term|
================================================================================
1 | 14,1| 0| 0 | 0 | 0 | 0 | 0 | 0 | . | 0 | 0| 0| .
2 | 14,1| 0| 0 | 0 | 0 | 0 | 0 | 0 | . | 0 | 0| 0| .
3 | 14,1| 0| 0 | 0 | 0 | 0 | 0 | 0 | . | 0 | 0| 0| .
4 | 14,1| 0| 0 | 0 | 0 | 0 | 0 | 0 | . | 0 | 0| 0| .
Error Response
None.
querybhbrief
Syntax
querybhbrief <time_unit> <time_period>
Description
Displays the busiest hour for each modem.
Parameters
<time_unit> is the amount of time over which to display busy hours: Year,
Month, Week or Day
<time_period> is the period on which to display busy hours: Curr or Prev
Example Command
> querybhbrief month curr
Successful Response
HEM|US |DS |Date |Hour |Conc|Ncon| Comp| Comp| Comp |CCS/ |Blk |Blk |Blk%
|CP |CP | | |Line|Line| Orig| Term|Noncon|Line |Orig|Term|
============================================================================
1,1| 2 | 1 |Dec11| 9 | 3 | 2 | 0| 0| 0| 2.8 | 0 | 0 | .
1,2| 2 | 1 |Dec18| 14 | 1 | 0 | 2| 0| 0| .1 | 0 | 0 | .
Error Response
None.

querygos
Syntax
querygos <scope> <time period> <% blocking>
Description
Displays busy hours that exceed the specified blocking percentage.
Parameters
<scope> specifies the entity to display; one of:
CP <cpid> — displays the specified carrier path.
HEM <DMC> <modem> — displays the specified HEM.
ALL — displays all available entities.
<time period> can be CURR or PREV
<% blocking> can be 0 to 100
Example Command
> querygos hem 14 1 prev 8
Successful Response
HEM |Hour|Comp |Comp |Comp|Conc|Ncon| CCS/ |Avg |Blk |Blk |Blk% |Min |Avg | ACB
| |Orig |Term |Ncon|Line|Line| Line |Hold|Orig|Term| |Chan|Occ | Secs
===============================================================================
14,1| 17 | 1092| 813| 0| 58 | 0 | 5.0 | 15| 9| 255|12.1 | 0 | 8 | 420
14,1| 13 | 1262| 974| 0| 58 | 0 | 6.0 | 15| 39| 255|11.6 | 0 | 9 | 465
14,1| 19 | 1370| 1122| 0| 58 | 0 |11.9 | 27| 42| 238|10.1 | 0 | 19 | 755
Error Response
None.
conclog
Syntax
conclog <action> <log_type> [<value>]
Description
This command enables, disables, or queries settings for monitoring logs.
Parameters
<action> is enable, disable, or query (read-only users only)
<log_type> can be CCS, Block, MinChan, BusyLine, Blkalarm, and
CallInfo
[<value>] can be CCS (1 to 36), Block (0 to 250), MinChan (0 to 23),
BusyLine (1 to 60), or BlkAlarm (0 to 250)
Note: For CsV06, this command has been changed to increase
the resolution for the blocking alarm and log. Prior to CsV06,
the blocking threshold for alarm or log generation was from
0% to 100% in 1% increments. With CsV06, this range
changes to 0% to 25% in 0.1% increments. The user is
required to enter the number without a decimal place in a
similar fashion as the spectrum manager threshold setting. For
example, to enter a blocking percentage of 12.5%, the user
would enter 125.
Example Command
> conclog enable block 200
Successful Response
Log Output enabled for Blocking Percentage greater than
20.0 %.
>conclog query
Log Type | Operand | Threshold | Status
======================================================
CCS/Line | greater than | 200 CCS | Disabled
MinChan | less than or equal | ** chan | Disabled
BusyLine | greater than | ** min | Disabled
CallInfo | n/a | n/a | Disabled
Block % | greater than | 20.0 % | Enable
BlkAlarm | greater than | 20.0 % | Disabled
Error Response
EITHER incorrect optional parameter(s) OR too many parameters.

cvclear
Syntax
cvclear
Description
This command clears all traffic monitoring counters.
Parameters
None.
Example Command
> cvclear
Successful Response
Warning: This will PERMANENTLY erase all traffic
statistics.
>Yes
Traffic statistics have been cleared.
Error Response
None.
trafunits
Syntax
trafunits <units>
Description
This command toggles the display between CCS and erlangs.
Parameters
<units> can be CCS or ERLANGS
Example Command
> trafunits ccs
Successful Response
Warning: This will change the display units and
disable the CCS/Erlang log.
Error Response
None.

CVV5 commands
The CVV5 CI provides necessary OAM&P commands relating specifically to
the V5.2 switch interface.
prompts you to reenter the information.
Table 4-12
CVV5 commands
actIF page 4-116
addIF page 4-117
addLink page 4-118
chgIFVariant page 4-120
chgInitialRing page 4-121
chgLCtimings page 4-122
chgLinkId page 4-123
chgLinkState page 4-124
chgPortState page 4-125
chgRingCadence page 4-126
deactIF page 4-127
delIF page 4-128
delLink page 4-129
queryFreePort page 4-130
queryInitialRing page 4-131
queryLCtimings page 4-132
queryLink page 4-133
queryPort page 4-134
queryRingCadence page 4-136
queryV5 page 4-137
setDefLCTimings page 4-139
setDefRingCadence page 4-140
actIF
Syntax
ActIF <if_id> [<FORCE>]
Description
This command activates a V5.2 switch interface on the Cornerstone HDT.
Parameters
<if_id> is the V5.2 switch interfaceID: 0 to 16777215
Example Command
> actIF 119
Successful Response
---------------------------------------------------------
Activation of the V5 Interface may take a few minutes.
---------------------------------------------------------
Do you wish to continue ?
>y
Activation of V5 Interface 119 has been requested.
Check V5 Log for completion.
Error Response
Undefined Interface ID (<if_id>)
The interface has not been provisioned; it must first be created with the
addIF command.
Interface reactivation timer (2 minutes) has not expired. Interface <if_id> will
be activated within 2 minutes. The DEACTIF command will cancel the delayed
activation.
Interface will activate automatically when the activation timer expires.
The DEACTIF command will cancel the delayed activation.
Interface <if_id> already activated
The specified interface has already been activated.
Another interface is currently being activated. This interface will activate when
resources allow.
Only one interface can be started simultaneously. As soon as the interface
currently being started completes, this interface will begin startup
automatically.

addIF
Syntax
addIF <if_id> <variant_id> <log_comm_chan_id>
[<error_timer>] [<ok_timer>]
Description
This command provisions a new V5.2 switch interface on the Cornerstone
HDT.
Log V5600 is generated as a result of this command.
Parameters
<if_id> is the new V5.2 interface ID: 0 to 16777215
<variant_id> is the Variant ID to associate with the V5.2 interface: 0 to 127
<log_comm_chan_id>
is the Logical Comm Channel identifier for this interface:
0 to 127
<error_timer> (optional) the time, in 100 ms increments, for Debounce
alarms for E1 facilities associated with this interface:
0 to 65535. Default: 2 (200ms)
<ok_timer> (optional) the time, in 100 ms increments, for an E1 alarm to
clear for facilities associated with this interface: 0 to 65535.
Default: 15 (1.5s)
Example Command
> addIF 111 0 0
Successful Response
Timers will be set to: Error=DEFAULT Ok=DEFAULT
V5 (Interface ID=111, Variant ID=0) add in progess.
Check V5 LOG for final result.
Error Response
Interface ID already in use
The interface has already been provisioned on the Cornerstone HDT. Use
Maximum switch interfaces already provisioned.
The maximum number of concurrent switch interfaces has already been
provisioned.
addLink
Syntax
addLink <e1_mapper> <e1_port> <if_id> <link_id>
<link_type>
Description
This command associates a physical E1 facility with a V5.2 switch interface,
specified by (Interface ID, Link ID).
The initial state of a newly added link is Local Blocked. The link state can be
put Available using the chgLinkState command.
The first link created with <link_type> = COMM is designated the Primary
link. The second link created with this type is designated the Secondary link.
A combination of the addLink, delLink, and chgLinkId commands can be
used to re-assign the Primary and Secondary designations.
Parameters
<e1_mapper> is the E1 mapper card: G1, G2, or G4
<e1_port> is the physical E1 link located on the given E1 mapper card: 1
to 7.
<if_id> is the V5.2 interface ID: 0 to 16777215.
<link_id> is the new Link ID.
<link_type> determines how time slot 16 of the E1 facility is used:
COMM — V5 communications
TRAF — voice traffic
Example Command
Assigning (E1 G1 1) facility to (Interface ID=111, Link ID=0) as a
Communication link. (It will be designated as Primary since it is the first
comm link within interface ID 111.)
> addLink G1 1 111 0 COMM

Assigning (E1G1 3) facility as (Interface ID=111, Link ID=2) as Traffic link.
> addLink G1 3 111 2 TRAF

Successful Response
Association (G1 1) to V5 (Interface ID=111, Link ID=0) add
as Primary link in progress. Check V5 LOG for final
result.

Error Response
E1 facility (<mapper>, <port>) unavailable.
The specified <e1_facility> is currently in use. Either choose another
<e1_facility> or unassign the one currently using it.
Interface <if_id> undefined.
The specified <if_id> has not been provisioned on the Cornerstone HDT.
Use the queryV5 CI to identify provisioned Interface ID values.
Link ID <link_id> currently in use.
The specified <link_id> is already in use within the specified interface.
Choose another link id.
Too many COMM links.
Both the Primary and Secondary links have already been assigned. Use the
queryV5 CI to identify these links. To reprovision a link as a COMM link,
first use the delLink CI to deprovision an existing COMM link.
Too many TRAF links.
All available traffic links for the given interface id have been allocated.
The Interface must be Deactivated before you can add a link.
Use the deactIF CI to deactivate the interface before adding a link.
chgIFVariant
Syntax
chgIFVariant <interfaceID> <variantID>
Description
This command assigns <variant_id> as the start Variant ID value for the V5.2
interface <if_id>. The interface must be deactivated at both the LE and HDT
for the new variant ID to take effect.
Parameters
<interfaceID> is the V5.2 interface ID: 0 to 16777215.
<variantID> is the new Variant ID value: 1 to 127.
Example Command
> chgIFVariant 111 5
Successful Response
Please ensure that the Variant ID has been changed on the
switch to match the change being made here.
**This change will not take effect until the next RTS**
-------------------------------------------------------
Do you wish to make the change here?
>Yes
V5 Varient ID for interface 111 has been changed to 5.
Error Response
Undefined Interface ID <if_id>.
the queryV5 command to identify provisioned Interface ID values.

chgInitialRing
Syntax
chgInitialRing <duration_type> <duration>
Description
This command modifies the initial ring pulse duration for each of the 32
allowed pulse duration types.
Parameters
<duration_type>is the Ring type: 0 to 31.
<duration> specifies the time, in 50ms increments, that ring is applied for
that interval: 0 to 5000 (0 to turn off the specified ring type.)
Example Command
ex1> chgInitialRing 0 400
ex2> chgInitialRing 13 0
Successful Response
ex1 Duration 0 : 400ms
ex2 Duration 13 : OFF

Error Response
None.
chgLCtimings
Syntax
chglctimings <hit_time_max> <disc_time_min>
<flash_time_min> <idigits_time_min>
Description
This command changes Line Card timings.
Parameters
<hit_time_max>
is the maximum hit time in milliseconds. This value must be
less than all other parameters. 1 to 5000.
<disc_time_min>
is the minimum disconnect time in milliseconds.This value
must be greater than the flash_time_min. Also, this value must
be greater than the idigits_time_min. 1 to 5000.
<flash_time_min>
is the minimum flash time in milliseconds. 1 to 5000.
<idigits_time_min>
is the minimum digits time in milliseconds. 1 to 5000.
Example Command
> chglctimings 40 1000 100 150
Successful Response
Line Card Timings updated
-------------------------------------------------
| Current line card timing settings (msecs) |
-------------------------------------------------
| Hit Time Disc Time Flash Time Idigits Time |
| max min min min |
-------------------------------------------------
40 1000 100 150
Error Response
Disc Time Min must be a value greater than the Hit Time Max.
Flash Time Min must be a value greater than the Hit Time Max.
Flash Time Min must be a value less than the Disc Time Min.
Idigit Time Min must be a value greater than the Hit Time Max.
Re-execute the command with correct data values

chgLinkId
Syntax
chgLinkId <if_id> <link_id_old> <link_id_new>
Description
This command changes the value of an existing Link ID.
Parameters
<if_id> is the V5.2 interface ID: 0 to 16777215
<link_id_old> is the old V5.2 Link ID: 0 to 255
<link_id_new> is the new V5.2 Link ID: 0 to 255
Example Command
> chgLinkId 111 122 0
Successful Response
----------------------------------------------------------
Please ensure that the Link ID has been changed on the
switch to match the change being made here.
----------------------------------------------------------
Do you wish to continue? (y/n)
y
V5 (Interface ID=111, Link ID=122) reassigned as Link ID=0
in progress. Check V5 LOG for final result.
Error Response
Link ID <link_id_old> currently In-Service.
<link_id_old> is currently In-Service. Put the link OOS via the
chgLinkState CI.
Undefined Old Link ID.
The specified <link_id_old> is not provisioned on the Cornerstone HDT.
Use the queryV5 CI to identify provisioned Link ID values.
Link ID <link_id_new> already in use by Interface <if_id>.
<link_id_new> is an existing Link ID currently associated with <if_id>.
Use the queryV5 CI to identify provisioned Link ID values.
Undefined Interface ID.
chgLinkState
Syntax
chgLinkState <if_id> <link_id> <link_state> [DEFER]
Description
This command attempts to put a V5.2 link in a given state.
Parameters
<link_id> is the V5.2 Link ID: 0 to 255.
<link_state> is the state to place the V5.2 link into, one of:
IS — The Cornerstone HDT requests the LE to put the link into
an Unblocked state.
OOS — The Cornerstone HDT requests the LE to put the link
into a Blocked state immediately. (Non-Deferred Block)
DEFER optional, used only with the OOS state. If specified, the
Cornerstone HDT requests the LE to put the link into a
Blocked state when all traffic on that link has been completed
(Deferred Block).
Example Command
> chgLinkState 111 4 OOS
Successful Response
V5 (Interface ID=111, Link ID=4) Non-Deferred Block in
progress. Check V5 LOG for final result.
Error Response
Undefined Link ID.
The specified <link_id> is not assigned to the specified <if_id>. Use the
queryV5 CI to identify Link ID associations.
Invalid state change request.
The specified <link_state> is not a valid state transition.
Change request rejected. Secondary COMM channel is not active.
Deactivate interface to put both COMM links OOS. Only one COMM link
can be put OOS (blocked). In order to disable both of the COMM links the
interface must be deactivated.

chgPortState
Syntax
chgPortState <if_id> <port_id> <port_state> [DEFER]
Description
This command attempts to put a V5.2 port in a given state.
Parameters
<port_id> is the V5.2 Port ID: 0 to 32767.
<port_state> is the State to place the V5.2 link into.
IS — The Cornerstone HDT requests the LE to put the port into
an Unblocked state.
OOS — The Cornerstone HDT requests the LE to put the port
into a Blocked state immediately. (Non-Deferred Block)
DEFER optional, used only with the OOS state. If specified, the
Cornerstone HDT requests the LE to put the link into a
Blocked state when all traffic on that link has been completed
(Deferred Block).
Example Command
> chgPortState 111 4 OOS
Successful Response
V5 (Interface ID=111, Port ID=4) Non-Deferred Block in
progress.
Error Response
Undefined Port ID.
The specified <port_id> is not assigned to the specified <if_id>. Use the
queryPort CI to identify Port ID associations.
Invalid state change request.
The specified <port_state> is not a valid state transition.
chgRingCadence
Syntax
chgRingCadence <ring_type> <On_1> [<Off_1>] <On_2>
[<Off_2>]<On_3> [<Off_3>]<On_4> [<Off_4>]
Description
This command modifies the ring cadence for a particular ring type. This
command also allows a particular ring type to be turned off.
Parameters
<ring_type> is the type of ring: 0 to 127.
<On_x>
specifies the time, in 50ms increments, that ring is applied for
that interval: 50 to 12750 (rounded to nearest 50ms), or 0 to
turn off the specified ring type.
<Off_x>
specifies the time in 50ms increments of silence after ring for
that interval: 50 to 12750 (rounded to nearest 50ms).
Example Command
> chgRingCadence 0 1000 4000 500 500
> chgRingCadence 13 0
Successful Response
Example 1:
Interval 1 ON : 1000ms
Interval 1 OFF: 4000ms
Interval 2 ON : 500ms
Interval 2 OFF: 500ms
Record updated.
Example 2:
Ring Type 13 does not exist. Will be
created.
Ring Type 13 will be set to NOT USED.
Record updated.
Error Response
You must specify at least 1 OFF period.
Ring Type 0 cannot be set to NOT USED.
Ring Type 0 (default National Ringing) cannot be turned off.
Intervals must be at least 50ms in 50ms increments.
Specify a time greater than 50ms.
You must specify ON/OFF periods in pairs.
Specify an even number of timings.

deactIF
Syntax
deactIF <if_id>
Description
This command deactivated a V5.2 switch interface on the Cornerstone HDT.
A two minute timeout period is required after Deactivation before the Interface
can be reactivated.
Parameters
Example Command
> deactIF 119
Successful Response
---------------------------------------------------------
Deactivation of the V5 Interface may take a few minutes.
---------------------------------------------------------
>y
Deactivation of V5 Interface 119 has been requested.
Check V5 Log for completion.
Error Response
Undefined Interface ID (<if_id>).
<if_id> has not been provisioned; it must first be created with the addIF
command.
Delayed activation of Interface <if_id> has been cancelled.
This is not an error. The deactIF command was used to cancel a delayed
activation request.
<if_id> already deactivated.
The specified interface has already been deactivated.
delIF
Syntax
delIF <if_id>
Description
This command removes a V5.2 switch interface from the Cornerstone HDT.
Parameters
Example Command
> delIF 111
---------------------------------------------------------
Deleting a V5 switch interface requires symmetrical change
on the LE.
---------------------------------------------------------
Do you wish to continue?
Please confirm (“Yes” or “No”():
>yes
>
Successful Response
V5 Interface ID=111 delete in progress. Check V5 LOG for
final result.
Error Response
Interface <if_id> is currently In-Service.
The specified <if_id> is currently In-Service. Deactivate the interface
before deleting it, by using the deactIF command.
Undefined Interface ID <if_id>.
The specified <if_id> is not provisioned on the Cornerstone HDT. Use the
queryV5 command to identify provisioned Interface ID values.
Association to a Link ID exists.
A Link-ID is currently associated with the <if_id>. Use the delLink
command to remove the association.
Association to a Port ID exists.
Port-ID is currently associated with the <if_id>. Use the delLine
command to remove the association.

delLink
Syntax
delLink <if_id> <link_id>
Description
This command unassigns a physical E1 facility from a V5.2 interface.
Parameters
<link_id> is the V5.2 Link ID: 0 to 255.
Example Command
> delLink 111 0
----------------------------------------------------------
Removing this link requires a symmetrical change to the
LE.
----------------------------------------------------------
Please confirm (“Yes” or “No”():
>yes
>
Successful Response
Association between (G1 1) and V5 (Interface ID=111, Link
ID=0) is begin removed. Check V5 LOG for final result.
Error Response
Link In-Service.
The specified Link ID is currently in the In-Service state. Put the link OOS
using the chgLinkState command.
Interface-ID=<if_id>, Link-ID=<link_id>) is not provisioned.
The specified facility is currently not assigned to any interface.
queryFreePort
Syntax
queryFreePort <if_id> [<how_many>] [<start>]
Description
This command displays up to 8 unassigned Port ID values.
Parameters
<how_many> optional, specifies the number of Port IDs to display. The
default is 8.
<start> optional, specifies the beginning Port ID. The default is 0.
Example Command
> queryFreePort 111 8
Successful Response
12 102 103 104 105 106 109 120
Error Response
No more Port IDs.
All 3360 Port ID values have been assigned.
Retry the queryFreePort command, specifying an interface ID.

queryInitialRing
Syntax
queryInitialRing <duration_type>
Description
This command displays current settings for a particular provisioned initial ring
pulse duration.
Parameters
<duration_type>is the ring type to display: 0 to 31.
Example Command
> queryInitialRing 0
Successful Response
| Duration | Interval |
| Type | Time |
|==========|==========|
| 0 | 400 |
Note: Times are expressed in milliseconds
Error Response
None.
queryLink
Syntax
queryLink
Description
This command displays the associations of the physical E1 facilities.
Parameters
None.
Example Command
> queryLink
Successful Response
Mapper Port Association
Card #
-------- ------ ------------
G1 1 V5 (IF ID=111, Link ID=0) COMM
G1 4 V5 (IF ID=111, Link ID=3) TRAF
G1 5 Unassigned
G1 6 Unassigned
G1 7 Unassigned
G2 2 V5 (IF ID=111, Link ID=1) TRAF
G2 3 Unassigned
...
Error Response
None.

queryLCtimings
Syntax
queryLCtimings
Description
This command displays the current settings for Line Card Timings.
Parameters
None.
Example Command
> querylctimings
Successful Response
------------------------------------------------
------------------------------------------------
| max min min min |
------------------------------------------------
40 1000 100 150
Error Response
None.
queryPort
Syntax
queryPort [<if_id>] [<port_id>]
Description
This command displays the port status, as well as the association between the
Port ID value and a (Voice Port, Line Card).
If no parameters are specified, the a complete list of all assigned Port ID
values will be displayed. If this list will exceed the normal text screen (i.e. 24
lines), then the customer will be prompted to continue to display another
screen of information.
If an <if_id> is specified without the optional <port_id> value, then all Port
IDs assigned to <if_id> will be displayed.
If the optional <port_id> parameter is specified, then only the information for
(Interface ID=<if_id>, Port ID=<port_id>) will be displayed.
Parameters
<if_id> optional, specifies the V5.2 interface ID (0 to 16777215). The
default is to display a list of all assigned Port ID values on all
interfaces.
<port_id> optional, specifies the V5.2 Port ID (0 to 32767). The default
is to display all Port IDs assigned to the specified <if_id> (or
all Port IDs on all interfaces).
Example Command
ex1> queryPort 111 1
ex2> queryPort 111
ex3> queryPort
Successful Response
%%ex1>
Port Interface Port Vp Line Vp Alias LC
ID ID Status ID Card State
------- -------- --------- -------- ---- -------------------- -----------
95 111 Available 16780139 1 6015 STATE BRDG IS_NR
%%ex2>
------- -------- --------- -------- ---- -------------------- -----------
2 111 Available 65 1 7748 MEDLOCK BRDG IS_NR
%%ex3>
------- -------- --------- -------- ---- -------------------- -----------
2 111 Available 65 1 7748 MEDLOCK BRDG IS_NR
7 222 Available 50060001 1 SUMMIT BLDG 1 IS_NR
8 222 Local Blk 50060001 2 SUMMIT BLDG 1 IS_ANR
13 222 Available 50060001 7 SUMMIT BLDG 1 IS_NR

Error Response
queryV5 CI to identify provisioned Interface ID values.
Undefined Port ID.
The specified <port_id> value is not provisioned within the Cornerstone
HDT.
No provisioned ports with V5.2 service.
Provision Ports via the addLine CI.
No provisioned ports for Interface ID.
Use the queryPort command without any parameters to display a complete
list of all V5.2 Port IDs and their associations to the Interface ID.
Port <port_id> is not provisioned on Interface ID <if_id>.
Use the queryPort command without any parameters to display a complete
list of all V5.2 Port IDs and their associations to the Interface ID.
queryRingCadence
Syntax
queryRingCadence
Description
This command displays current settings for all provisioned ring cadence ring
types.
Parameters
None.
Example Command
> queryRingCadence
Successful Response
Ring |Interval 1 |Interval 2 |Interval 3 |Interval 4 |
Type | On Off | On Off | On Off | On Off |
==== |===== =====|===== =====|===== =====|===== =====|
0 | 400 200| 400 2000| 0 0| 0 0|
1 | 1500 4500| 0 0| 0 0| 0 0|
2 | 1500 500| 1500 2500| 0 0| 0 0|
3 | 1500 500| 500 3500| 0 0| 0 0|
4 | 1500 500| 500 500| 500 2500| 0 0|
5 | 1500 500| 500 500| 1000 2000| 0 0|
6 | 1000 500| 1000 3500| 0 0| 0 0|
7 | 500 500| 500 500| 1000 3000| 0 0|
8 | 500 500| 1000 500| 500 3000| 0 0|
9 | 1700 600| 250 250| 250 2950| 0 0|
10 | 1700 600| 250 250| 900 2300| 0 0|
11 | 250 5750| 0 0| 0 0| 0 0|
13 | 2500 50| 0 0| 0 0| 0 0|
Error Response
None.

queryV5
Syntax
queryV5 [<if_id>]
Description
This command displays the following information about the V5.2 interface(s)
provisioned on the Cornerstone HDT:
• State of the Interface
• Variant ID associated with Interface ID
• Links associated with Interface ID
• State of the links as discussed in
• Alarm currently raised against the interface
Parameters
<if_id> optional parameter, specifies a particular Interface ID to
display (0 to 16777215). The default is to display a list of
V5.2 Interface ID values provisioned on the system.
Example Command
ex1> queryV5
ex2> queryV5 111
ex3> queryV5 222
Successful Response
%% ex1>
Interface ID State Activation
------------ ----- ------------
111 IS Activated
222 IS-Wt-Strt Activated
%% ex2>
Interface ID: 111
Activation: Activated
State: IS
Variant ID: 0
Logical Comm Channel: 0
Link ID State E1 Facility State
------- --------------------------- ----------- -----
PRI 1 Available G1 1 In-Service
SEC 2 Available G2 1 In-Service
TRF 3 Blocked G1 2 In-Service Trouble
TRF 4 Available G1 3 In-Service
%% ex3>
Interface ID: 222
Activation: Activated
State: IS-Wt-Strt
Variant ID: 0
Logical Comm Channel: 0
Link ID State E1 Facility State

------- --------------------------- ----------- -----
SEC 1 Available Awaiting IF G1 1 In-Service
PRI 2 Available Awaiting IF G2 1 In-Service
Error Response
queryV5 CI without any parameters.
V5 service not provisioned.
No V5.2 interfaces have been provisioned on the Cornerstone HDT.
No Links for this Interface
No V5.2 links have been added to the specified <if_id>. Use the addLink
CI to perform this provisioning.

setDefLCTimings
Syntax
setDefLCTimings
Description
This command sets default values for Line Card Timings.
Parameters
None.
Example Command
> setdeflctimings
Successful Response
Line Card Timings updated
------------------------------------------------
------------------------------------------------
| max min min min |
------------------------------------------------
20 1000 300 500
Error Response
None.
setDefRingCadence
Syntax
setDefRingCadence <region>
Description
This command sets default values for Line Card Timings.
Parameters
<region> specifies the set of default timings to use; one of:
• NORTH_AMERICAN_STANDARD (7 dB Rx / 5 dB Tx
loss plan)
• NORTH_AMERICAN_HIGH (3 dB Rx / 3 dB Tx high-gain
loss plan)
• CHILE
• JAPAN
• GERMANY
• NETHERLANDS
• PHILIPPINES
• AUSTRALIA
• AUSTRIA
• SPAIN
• FRANCE
• ARGENTINA
• BRAZIL
• COLUMBIA
• VENEZUELA
Example Command
> setDefRingCadence japan

Successful Response
The ring cadences have been set to the default for JAPAN
Ring |Interval 1 |Interval 2 |Interval 3 |Interval 4 |

Type | On Off | On Off | On Off | On Off |
==== |===== =====|===== =====|===== =====|===== =====|
0 | 400 200| 400 2000| 0 0| 0 0|
1 | 1500 4500| 0 0| 0 0| 0 0|
2 | 1500 500| 1500 2500| 0 0| 0 0|
3 | 1500 500| 500 3500| 0 0| 0 0|
4 | 1500 500| 500 500| 500 2500| 0 0|
5 | 1500 500| 500 500| 1000 2000| 0 0|
6 | 1000 500| 1000 3500| 0 0| 0 0|
7 | 500 500| 500 500| 1000 3000| 0 0|
8 | 500 500| 1000 500| 500 3000| 0 0|
9 | 1700 600| 250 250| 250 2950| 0 0|
10 | 1700 600| 250 250| 900 2300| 0 0|
11 | 250 5750| 0 0| 0 0| 0 0|
13 | 2500 50| 0 0| 0 0| 0 0|
Error Response
None.
MVIPROV commands
When the first GR-303 MVI host is provisioned, Cornerstone sets up a
preprovisioning table (HDT slot association table) for all slots on the HDT.
Use the MVIPROV commands to display or modify the slot assignments as
follows:
• Set up the CRV ranges for each interface group (IG) in a Multi-IG
GR-303 MVI configuration. This is usually a required step in the
provisioning process. During autoprovisioning, the system sets up
CRVs 1 to 2048 on IG 1 and CRVs 1 to 1312 on IG 2.
• Change the service assignment on one or more HDT slots to
MVIPOTS or EBS. All slots initially default to MVIPOTS service.
(Service pre-assignment is required because GR-303 switch
provisioning commands do not uniquely distinguish MVIPOTS and
EBS service types.)
Note: Modifying the service type using MVIPROV at the HDT immediately
changes the current service to the new service type. This change is
immediately service affecting. You should delete the existing service (at the
switch) before reassigning its slot at the HDT
Table 4-13
MVIPROV commands
EditCRV page 4-143
MoveCRV page 4-144
QueryProv page 4-145
QueryIDT page 4-146
EditIDT page 4-147
Requirements
A GR-303 MVI host switch has been added to HDT data using the OPC Host
Provisioning Manager tool before using the MVIPROV commands.

EditCRV
Syntax
editcrv <edit method>
Description
This command modifies call reference values (CRV) or interface group (IG)
values for one or more lines.
Parameters
<method> is the method for specifying the lines to modify; one of:
slot <shelftype> <CDS> <shelf> <slot> <CRV> — modified
CRVs based on shelftype
range <shelftype> — the shelftype can be <CDS> <start shelf>
<start slot> <end shelf> <end slot <start CRV> <end CRV> to
edit a range of CRVs on a certain shelf or MODEM <start
instance> <end instance> <start CRV> < end CRV> to edit a
range of CRVs by modem.
instance <instance> <CRV> — edit a range of CRVs by their
starting and ending line instance numbers (1 to 3360) and CRVs
(1 to 2048)
Example Command
editcrv instance 25 25 1
Successful Response
The command as entered:
Instance - 25
CRV - 25
IG - 1
>Y
Operation successful.
Error Response
Operation failed - GR-202 line termination exists on the slot range specified.
MoveCRV
Syntax
movecrv <source start> <source end> <source IG> <dest
start> <dest end> <dest IG>
Description
This command reassigns lines to a different interface group and CRV.
Parameters
<source start> and <source end>
are the starting and ending CRVs on the source IG.
<source IG> is the IG currently assigned to the specified lines.
<dest start> and <dest end>
are the starting and ending CRVs on the destination IG.
<dest IG> is the new IG for the specified lines.
Example Command
MOVECRV 1 6 1 1 6 3 ↵
Successful Response
The command as entered:
Source Start CRV - 1 Dest Start CRV - 1
Source End CRV - 6 Dest End CRV - 6
Source Host - 1 Dest Host - 3

>y
CRV 1 IG 1 moved to CRV 1 IG 3
Operation complete. 6 CRVs moved.
Error Response
Operation failed - Invalid dest CRV range.
CRV # IG # has service provisioned and will not be moved.
Operation complete. 0 CRVs moved.

QueryProv
Syntax
queryprov <method>
Description
This command displays the current line assignments.
Parameters
<method> specifies the lines to display; one of:
all — displays assignments for all lines on the HDT.
slot CDS <shelf> <slot> <CRV> — displays assignments for
all lines within the specified CDS shelf (1 to 7), slot (1 to 96)
and CRV (1 to 2048).
shelf CDS — displays assignments for all lines on a CDS (1 to
7).
range CDS <start shelf> <start slot> <end shelf> <end slot> —
displays assignments for all lines within a particular range of
start and end shelves (1 to 7) and slots (1 to 96).
range modem <start> <end> — displays assignments for the
specified line instance range: 1 to 3360.
instance <instance> — displays assignments of a particular
line instance (1 to 3360).
serv <service type> — displays assignments of a particular
service type (MVIPOTS, MVIUVG, MVICOIN, MVIMPY,
EBS).
CRV <CRV> <IG> — displays assignments of a particular
CRV (1 to 2048) on a particular IG (1 to 5).
Example Command
queryprov range modem 50 55
Successful Response
Note: Successful responses will vary depending on the parameters entered.
* Applies only to LOOP and GRND services.

Card CRV IG Default Service* Current Service Current GSFC Instance
---- ----- ---- ---------------- --------------- ------------ --------
1 50 75 1 MVIPOTS no service -- 50
Error Response
No response from modem shelf.
QueryIDT
Syntax
queryidt
Description
This command displays the IG, interface type, and CLLI (trunk group ID) for
the current HDT.
Parameters
None.
Example Command
queryidt
Successful Response
GR-303
IG CLLI IDT Interface
-- ---------------- ----- ---------
1 JCRKGALAB01 111 MVI
-------------------------------------
Error Response
None.

EditIDT
Syntax
editidt <IG> <host IDT>
Description
This command reassigns all lines in the specified interface group to a different
interface group.
Parameters
<IG> is the original IG number: 1 to 5.
<host IDT> is the new IG number: 0 to 9999.
Example Command
editidt 1 2
Successful Response
The IDT value for IG 1 is about to be changed to 111.
Please ensure that 111 is the correct IDT value

before continuing with this change.

>y
Operation successful.
Error Response
The command has been aborted...
FAMCI commands
Use the FAM tools to provision or de-provision a facility as well as display
current facility assignments. These tools apply only to E1-based systems.
The detailed descriptions of the commands includes syntax and parameters

and gives examples of their use. When a given parameter value exceeds the
valid range, the system indicates “out of range” followed by the proper range
and prompts the user to reenter the data.
Table 4-14
FAMCI commands
famassign page 4-149
famquery page 4-150
famunassign page 4-151
qbitinv page 4-152
sbitinv page 4-153

famassign
Syntax
famassign <unit> <port#> <service type>
Description
This command provisions a facility.
Parameters
<unit> is the group number: G1, G2, or G4
<port#> is the port number: 1 to 7
<service type> is the service type; one of the following:
V5 <if_id> <link_id> <link_type> — provisions a V5.2 facility
with the specified interface ID (0 to 16777215), link ID (0 to
255), and type (COMM or TRAF).
VLCM <vlcm> <link> — provisions a VLCM facility with the
specified VLCM number (1 to 7) and link number (0 to 5).
DTA — provisions a Digital Test Access (DTA) facility.
Example Command
> famassign g2 1 vlcm 1 0
Successful Response
E1=G2 Port=1 Factype=VLCM VLCMNum=1 VLCMPort=0
Association (G2 1) to VLCM (Unit=1, Link=0) added.
Error Response
None.
famquery
Syntax
famquery
Description
This command displays current facility assignments (CsV04 and newer).
Parameters
None.
Example Command
> famquery
Successful Response
Mapper Port Association
====== ==== ===========
G1 1 V5 (IF ID=204, Link ID=1) Comm
G1 3 V5 (IF ID=204, Link ID=3) Traffic
G1 4 V5 (IF ID=205, Link ID=3) Traffic
G1 5 Unassigned
G1 6 Unassigned
G1 7 Unassigned
G2 3 Unassigned
G2 4 Unassigned
G2 5 Unassigned
G2 6 Unassigned
G2 7 Unassigned
G4 3 Unassigned
G4 4 Unassigned
G4 5 Unassigned
G4 6 Unassigned
G4 7 Unassigned
Error Response
None.

famunassign
Syntax
famunassign <unit> <port#>
Description
This command deprovisions a facility.
Parameters
<unit> is the group: G1, G2, or G4
<port#> is the port number: 1 to 7
Example Command
> famunassign g2 1
----------------------------------------------------------
Removing this link requires a symmetrical change to the
LE.
----------------------------------------------------------
>y
Successful Response
Association between (G2 1) and VLCM (Unit=1, Link=0) has
been removed.
Error Response
None.
qbitinv
Syntax
qbitinv <unit> <port#>
Description
This command queries bit inversion on an E1 port.
Parameters
<unit> is the E1 group number: g1, g2 or g4
<port#> is the E1 port number: 1 to 7
Example Command
> qbitinv g1 1
Successful Response
TS 0 = NONE
TS 1 = ODD
TS 2 = NONE
...
Error Response
None.

sbitinv
Syntax
sbitinv <unit> <port#> <timeslot> <inv>
Description
This command sets bit inversion on a timeslot.
Parameters
<unit> is the E1 group number: g1, g2 or g4
<port#> is the E1 port number: 1 to 7
<timeslot> is the timeslot number: 1 to 31
<inv> is the bit inversion: none, odd, even, or all
Example Command
> sbitinv g1 1 2 odd
Successful Response
Setting bit inversion = ODD
Bit inversion set successfully.
Database updated successfully
Error Response
None.
OMCCI commands
Use the OMCCI commands to provision and maintain OMC links in DS1-fed
HDTs.
Table 4-15 lists the available OMCCI commands.

Table 4-15
OMCCI commands
omc add page 4-155
omc setdlchan page 4-156
omc delete page 4-157
omc query page 4-158

omc add
Syntax
omc add <link #> <unit> <port> <bandwidth> [<linkname>]
Description
Use this command to provision an OMC link. Any DS1 not assigned to carry
traffic can be provisioned as an OMC link.
Make sure that the OMC bandwidth and DS1 facility parameters are identical
at each end of the link.
The first OMC link added to an HDT automatically becomes the OMC
software download channel. This link is used as a backup software transfer
between the OPC and the HDT.
Parameters
<link #> is the OMC link number: 1 to 10.
<unit> is the HDT DS1 group number: g1, g2, or g4.
<port> is the DS1 port number within the group: 1 to 14.
<bandwidth> is the number of DS0s used for the OMC data link: 3 to 6.
<linkname> (optional) link name, up to 20 characters.
Example Command
omc add 1 g2 14 4 ‘Backup 111/113’
Successful Response
Success. Link 1 has been added
Success. Download channel set.
Error Response
****** Operation failed.
Ensure that the current facility is available and that the limit of 31 DS0s is not
being exceeded. Please check the Facility Assignments and/or the
provisioning information.
omc setdlchan
Syntax
omc setdlchan <link #>
Description
Use this command to assign a software download channel to a different OMC
link. The first OMC link added to an HDT automatically becomes the OMC
software download channel; use this command to change it.
Parameters
<link #> is the OMC link number: 1 to 10.
Example Command
omc setdlchan 3
Successful Response
Success. Download channel set.
Error Response
****** Operation failed.

omc delete
Syntax
omc delete <link #>
Description
Use this command to delete an OMC link.
Parameters
<link #> is the OMC link number to delete: 1 to 10.
Example Command
omc delete 3
Successful Response
Success, Link 3 has been deleted
Error Response
Deletion of the OMC download channel is only allowed from an HMOI port..
omc query
Syntax
omc query <link #>
Description
Use this command to query OMC link assignments.
This command indicates the software download channel with an asterisk (*) in
the D/L column.
Parameters
<link #> is the OMC link number: 1 to 10 to display a single link, or all
to display all link assignments.
Example Command
omc query all
Successful Response
Link# Connected To #DS0 State D/L Name
1 Not Assigned
2 Not Assigned
3 Not Assigned
4 Not Assigned
5 Not Assigned
6 Not Assigned
7 Not Assigned
8 Not Assigned
9 Not Assigned
10 Not Assigned
Error Response
None.

VLCMCI commands
Use the VLCM maintenance commands to display vlcm status. These
commands are for use only with VLCM interfaces.
Table 4-16
VLCMCI commands
linkstatus page 4-160
setloadname page 4-161
unknown page 4-162
vlcmstatus page 4-163
zero page 4-164
linkstatus
Syntax
linkstatus <vlcm value>
Description
This command displays the current state of provisioned VLCM DS1/E1 links.
The tabular output displays five values for each DS1/E1 provisioned:
• The VLCM number the link is associated with
• The switch port number (0 to 5)
• The HDT VT number the link maps to
• The status of the link
• Whether the link is a PCM only or a PCM/signal link
Parameters
<vlcm value> is the VLCM link for which data is to be displayed or all
provisioned links: 1 to 8, or all.
Example Command
> linkstatus all
Successful Response
VLCM PORT DS1 STATE SIGNAL/PCM
---- ---- ----- ------ ----------
1 0 G1- 1 In Ser signal
Error Response
No records found.

setloadname
Syntax
setloadname <VLCM instance number> <VLCM unit number>
<VLCM load number>
Description
This command sets the load name for VLCM in CsV04 and newer.
Parameters
<vlcm instance number>
is the VLCM instance: 1 to 8.
<vlcm unit number>
is the VLCM unit: 0 or 1.
<vlcm load number>
is the name of the VLCM load; this can be any alphanumeric
string.
Example Command
> setloadname 4 1 alpha
Successful Response
None.
Error Response
Cannot store the load name.
The DB error is : 1.
unknown
Syntax
unknown
Description
This command displays unexpected messages.
Parameters
None.
Example Command
> unknown
Successful Response
MSG NUM COUNT
------- -----
44 32767
Error Response
None.

vlcmstatus
Syntax
vlcmstatus
Description
This command displays the current state of all provisioned VLCM units. The
tabular output lists the VLCM number, unit number within a VLCM, the state
for each unit, and whether the activity is raised.
Parameters
None.
Example Command
> vlcmstatus
Successful Response
VLCM NUM UNIT NUM STATE ACTIVITY
-------- -------- ----- --------
1 0 IS RAISED
1 1 IS RAISED
Error Response
None.
zero
Syntax
zero
Description
This command resets the unexpected message list.
Parameters
None.
Example Command
> zero
Successful Response
VLCM NUM UNIT NUM STATE ACTIVITY
-------- -------- ----- --------
1 0 IS RAISED
1 1 IS RAISED
Error Response
No VLCM instances provisioned.

5-1
User-interface overview 5-
The term “user interface” refers to the method by which you give commands
to the system to tell it what to do. In the user interface, you control the
operations, administration, maintenance, and provisioning (OAM&P) of the
system.
Levels of control
For a Cornerstone system, there are three levels at which you can exert control
over the system. Each level has its own user interface, as summarized in the
following table.
Table 5-1
Levels of control
Level of control User interface
network element network element user interface (NEUI)
cluster operations-controller user interface (OPCUI)
network an external surveillance system, for example,

Network Manager
Note: For information on how to access the user interfaces, see “Access to
the user interfaces” on page 5-4.
Figure 5-1 shows the three levels of control. The illustration shows a network
with an external surveillance system, for example, Network Manager. The
network has two operations controllers, each of which serves a cluster of
network elements.
5-2 User-interface overview
Figure 5-1
Scope of control for the Network Manager, the OPCUI, and the NEUI
CS-10167
CS-10167
Cluster #1 HDT HDT HDT HDT
OPC UI
OPC
HDT HDT HDT
Cluster #2 HDT HDT HDT HDT
Network
Manager
OPC UI
OPC
NE UI
HDT HDT HDT
Note: Figure 5-1 uses images of the operations-controller faceplate to

represent the operations controllers. The figure does not try to show the
network elements in which the operations controller modules are located.
You use the network element user interface (NEUI) to control an individual
network element. An example of a function performed in the network
element user interface is changing the status of equipment from
out-of-service to in-service.

You use the operations-controller user interface (OPCUI) to control a cluster

of network elements. A cluster includes all the network elements served by the
operations controller. (A single operations controller can serve up to 16
DS1-fed NEs, or up to 10 E1-fed NEs.) An example of a function performed
in the OPC user interface is transferring and installing a load from the
operations controller to a network element in the cluster. Using the OPC user
interface, you can perform this function for each network element in the
cluster.
While working in the OPC user interface, you can access the network element
user interface of any network element in the cluster.
The Network Manager is an optional software application that runs on a UNIX

workstation. The application gives you a user interface that can control up to
100 clusters, that is, 100 operations controllers and all the network elements
served by those operations controllers. An example of a function performed by
the Network Manager is viewing a graphical representation of the network
topology.
While working with the Network Manager, you can access the OPC user
interface of any operations controller in the network, or the network element
user interface of any network element in the network.
Access to the user interfaces

To carry out an operation, you can go to the NEUI or the OPCUI.
NEUI
If you need to use the network element user interface (NEUI) to carry out an
operation, you can go to the network element and access its NEUI locally, or
you can access the NEUI remotely.
Local access to the NEUI

If you are at the network element, you can connect a VT100-compatible
terminal to the user-interface port on the local craft access panel.
Remote access to the NEUI

You can gain remote access to the NEUI in the following ways:
• If you have a modem connection to the network element, you can access
the NEUI by way of that connection. At the network element, the modem
connector is the J08 connector on the left side of the access bandwidth
manager shelf.
• If you using the OPC user interface (OPCUI), you can use the NE Login
Manager software tool to log in to the NEUI of any network element in the
cluster.
Note: If you are at one network element in a cluster, you can log in to the
OPCUI remotely (as explained in a following section), and then use NE
Login Manager software tool to log in to the NEUI of another network
element in the cluster.
• If you have a Network Manager, it gives you access to the NEUI of each
network element in the network.

OPCUI
If you need to use the operations controller user interface (OPCUI) to carry out
an operation, you can go to the operations controller and access its OPCUI
locally, or you can access the OPCUI remotely.
Note: The operations controller is housed in a host digital terminal (HDT).
Local access to the OPCUI

If you are at the operations controller, you can access the OPCUI in the
following ways:
• You can connect a graphics terminal or a VT100-compatible terminal to
the OPC connector. The OPC connector is the J07 connector on the left
side of the access bandwidth manager shelf.
• You can connect an X11 terminal or a workstation to the Ethernet port on
the face plate of the operations controller module.
Remote access to the OPCUI

You can gain remote access to the OPCUI in the following ways:
• If you are at one of the other network elements in the cluster, you can
connect a graphics terminal or a VT100-compatible terminal to the OPC
connector. The OPC connector is the J07 connector on the left side of the
access bandwidth manager shelf. By way of this connection, you can
access the OPCUI remotely.
• You can access the OPCUI by way of a modem connection to the OPC
connector on one of the network elements in the cluster. The OPC
connector is the J07 connector on the left side of the access bandwidth
manager shelf.
• If you have a Network Manager, it gives you access to the OPCUI of each
operations controller in the network.
Description of the network element user interface

Note: For information on how to access this user interface, see “Access to
You use the network element user interface (NEUI) to control a single network
element, for example, a host digital terminal (HDT). The NEUI is composed
of two parts:
• a set of menu-based screens that control the equipment in the access
bandwidth manager shelf
• a set of command interpreters (CIs) that control the modem shelf and the
Voice Ports
For information on the menu-based screens, see the next section.
Menu based screens

You use the menu based screens in the network element user interface to
control the equipment in the access bandwidth manager shelf. The screens
allow access to the following:
• alarms
• configuration and provisioning
• performance monitoring
• maintenance
• protection switching
• online inventory
When you log in to the network element user interface, the first screen that
appears is the Network Element Status screen, as shown in the following
figure.
CS-10216
CS-10216
1 . . . 1 . . . .
S/DMS Nodes
0 Quit Network Element Status Shelf: CE
2
3 Alarms NE ID Alarms Protection Prf
4 ListNEs Fac Eqp Env Fail Lckt Act Alrt
5 1 . . . . . * .
6 PerfMon
7 FWPUI:
8
9
10 Protectn
11
12
13 JackAcc
14
15 Equipmnt
16 Facility
17 Admin
18 Help
NE 1
Time 20:13 >

The menu-based screens are arranged in a tree structure, with the Network
Element Status screen at the root. You move through the tree structure from
one screen to another by:
• locating the command you want from the command menu display area at
the left side of the screen, then typing its number in the command input
area, or
• typing the command name in the command input area at the bottom of the
screen
Description of the OPC user interface

The operations controller is the element manager for the Cornerstone system.
It supports a multiple-window graphical interface for local management of the
cluster.
It also provides TL1 interfaces to allow network management from higher

layers of the telecommunications-management network.
The OPC user interface supports communications with X terminals, LANs,

and the Network Manager.
Note: For information on how to access this user interface, see “Access to
Software tools and toolsets

To perform functions in the OPC user interface, you use OPC software tools.
Each software tool has a main menu window from which you operate. OPC
software tools can be customized to display information for all the network
elements in the OPC span of control or for network elements of particular
interest to you. With many of the tools, you can display details about a specific
event and then print the details directly from the display.
The OPC tools are grouped into toolsets. There is one toolset for each of the
following areas of OPC functionality:
• software administration
• OPC administration
• network administration
• network surveillance
• system lineup and test (SLAT)
• provisioning administration
• test administration
• utilities access
This chapter shows examples of software tools using the character-based user
interface.

User Session Manager

When you log in to the character-based OPC user interface, the User Session
Manager window appears automatically. This window displays a list of
toolsets and tools as shown below.
> User Session Manager: Jsmith

Toolset/Tools ID State Tool
Software Admin 1 >< Busy Event Browser
Reboot/Load Manager
Backup/Restore Manager
Event Browser
NE Software Delivery
Manager
Network Upgrade Manager
Utilities
NE Login Manager
DMSTerm
Password Update
[ Logout ]
C0 M0 m1 w2 FailProt 0 Lckt 0 ActProt 0 PrfAlrt 0 11:09
The User Session Manager window is like the main menu for the OPC user
interface. It displays the OPC software tools that are available to you, as well
as the instances of tools that have already been opened. You can select a tool
and open an instance or, if there is an instance open already, you can access
that instance.
Note: In a session in the OPC user interface, you can open more than one
instance of the same tool. However, when you reach the maximum number
of instances allowed for the tool, no further instances of that tool are
allowed and a disable icon appears in front of the tool in the list of available
tools.
When you open an instance of an OPC software tool or access an already open
instance, the main menu for the tool appears. The main menus of many of the
OPC tools are shown on the following pages.
Software administration toolset

Software administration performed by the OPC includes initial software
loading, software recovery, and software upgrades. Software can be loaded
from the original tape to the local OPC or from a remote OPC to the local OPC.
The software administration toolset allows you to manage the software in the
network elements in the cluster. The toolset includes the following tools:
• Reboot/Load Manager tool
• Backup/Restore Manager tool
• Event Browser tool
• NE Software Delivery Manager tool
• Network Upgrade Manager tool
Reboot/Load Manager tool

Use the Reboot/Load Manager tool to upgrade the software in network
elements. You can specify the startup software release for the processors in a
network element, or send a software load to a specific processor. You can also
change or reset the startup load for the processor.
CS-10046
CS-10046
>. Reboot/Load Manager Options
Network Element Shelf Release Download Status

7 ABM <Rel #> -
1 Change startup release
8 ABM <Rel #> In Progress
2 Manage loads
3 Select
4 Deselect
5 Help H
The Reboot/Load manager is responsible for rebooting network elements that

have requested an automatic reboot.

Backup/Restore Manager tool

The OPC automatically stores backup files of the network element database.
With the Backup/Restore Manager tool, you can use the backup files to restore
data to a network element after it has rebooted or after a software release
upgrade.
CS-10065
CS-10065
>• Backup/Restore Manager Options
Network Element Shelf
641 Montreal 1 1 Manage backups
642 Vancouver 1 2 Select
3 Deselect
4 Help H
C 0 M 0 m 1 w 2 FailProt 0 Lockout 1 ActProt 0 PrfAlrt 3 11:35
You can also list all the backup files that exist, and delete backup files that are
no longer required.
Event Browser tool

Logs and alarms are generated by Cornerstone systems when problems arise
with the equipment (modem shelf, Spectrum Manager, and Voice Port),
facilities, or spectrum management.
Use the Event Browser tool to view the history of the OPC and network
element logs, alarms, and alerts for a network element. You can also display
and print details about specific events.
CS-10043
CS-10043
>. Event Browser
Event sorted by time [ Update List ]

Showing: logs, alarms, alerts, all sev, and all NEs
NE# NE Name Evt# Cls Type Unit Reason Date Time Sv
0 OPC 292 Stat log COM501 OPC to NE 12 17 Jul 15:34:10 w
1 Filter...
0 OPC 291 Stat log COM502
2 SortOPC to NE 12>>17 Jul 15:33:40 M
0 OPC 290 Trbl log NAD351
3 ShowCannot colle
details... Jul 15:12:52 m
1 by17severity
0 OPC 289 Cmpl log GEN618 Log/Alarm2 da Jul 15:06:20
by17network w
element
0 OPC 288 Stat log COM501
4 HelpOPC to NE3 12
by Jul 15:06:16 w
H17time
0 OPC 287 Cmpl log by17class
GEN618 Loc/Alarm4 da Jul 14:43:32 w
0 OPC 284 Stat log COM502 OPC to NE 12 17 Jul 14:31:09 M
0 OPC 283 Cmpl log GEN618 Log/Alarm da 17 Jul 14:28:36 w
0 OPC 281 Trbl log NAD351 Cannot colle 17 Jul 14:11:47 m
0 OPC 278 Cmpl log GEN618 Log/Alarm da 17 Jul 11:35:58 w

NE Software Delivery Manager tool

Use the NE Software Delivery Manager to transfer and install loads from the
OPC to the network elements. Files can be transferred locally from the tape to
the disk of the local OPC or from the local tape or disk to a remote OPC, or
remotely, from the disk of a remote workstation or OPC to the local OPC.
CS-10048
CS-10048
>. NE Software Delivery Manager Utilities
Destination OPCs
OPCM027P (Local OPC)
OPCM001B [ Transfer Return]
NE Loads To Transfer
Load Name Source Size (kB) Shelf Processor Vintage Release
<Load Name> DISK 8808 ABM RFT APU 0 <Rel #>
ABM RFT APU 0 <Rel #>
<Load Name> DISK 439 ABM RFT HMU 0 <Rel #>
ABM RFT HMU 0 <Rel #>
Network Upgrade Manager tool

This command exists but is not used by Cornerstone software.
OPC administration toolset

OPC administration functions are performed by authorized members of the
administrative user group; access is controlled by user accounts and
passwords. OPC administration includes remote software installation, save
and restore functions for OPC data, OPC shutdown when necessary, setting of
time-of-day clock and time zone for the OPC, and configuration of OPC serial
ports.
The OPC administration toolset includes the following tools:

• Centralized User Administration tool
• Remote OPC Software Installation tool
• OPC Save and Restore tool
• OPC Shutdown tool
• OPC Date tool
• UNIX Shell tool
• Port Configuration tool
• IP Routing Admin tool
• OPC Status Tool
• OPC Clock Tool
Centralized User Administration tool

Use the Centralized User Administration tool to create, modify, or delete NE
user accounts. You can also set security parameters to limit user access to
selected network elements and to specify the type of access permitted.
CS 10050 CS-10050
>. Centralized User Administration Configure Utilities
Users sorted by : User Id Number of users shown : 7 of 7
Showing groups : All
User Id Group Status User Name Detail

admin admin valid admin admin
1 Open... (
netsurv netsurv valid netsurv netsurv
2 Show user account info...
operator admin valid operator admin
3 Assign user password...
slat slat valid slat slat
test test valid test test
4 Select >>
prov prov valid prov prov
5 Deselect >>
6 Duplicate...
7 Enable
8 Disable
9 Delete
10 Help H
[ Create a new user... +]

Remote OPC Software Installation tool

Use the Remote OPC Software Installation tool to transfer OPC software from
the local OPC tape drive and automatically install it on remote OPCs. From
lists stored on the local OPC, you can select the software packages for a
number of remote OPCs and initiate installation of all the selected items in the
list. You can also monitor the progress as the software is being installed.
CS-10051
CS-10051
> . Remote OPC Software Installation Utilities
[ Setup ] [ Install ]
Release to be installed:
Installations to be Performed
Status OPC Packages
1 Cancel
2 Continue
3 Retry
4 Delete
5 Swap Order
6 Details...
7 Select >>
Status Messages 8 Deselect >>
9 Help H
OPC Save and Restore tool

Use the OPC Save and Restore tool to create a backup tape of OPC data. You
can use the backup tape to restore OPC data when necessary, or to transfer
OPC data from the local OPC disk to the backup OPC.
CS 10052 CS-10052
>. OPC Save and Restore
Operation to perform: ( ) Save to tape

( ) Restore from tape
Scheduler is disabled.
Saving OPC data to tape:
=> 1. [ Display tape details 1]
2. [ Save OPC data to tape 2]
3. [ Enable scheduler 3]
4. [ Edit schedule 4]
OPC Shutdown tool

Use the OPC Shutdown tool to shut down the OPC before disconnecting it
from its power source or removing it from its shelf; for example, during
configuration or troubleshooting. When you select the Shutdown command, a
confirmation dialog informs you of the amount of time the process will take
and prompts you for authorization to proceed with the shutdown.
OPC Date tool

Use the OPC Date tool to set the OPC time-of-day clock and the time zone in
which the OPC is operating. For adjustments of less than 30 minutes, the time
is adjusted gradually with no impact on the OPC operation. Larger changes in
time, date, or time zone are made immediately, shutting down the OPC
temporarily.
CAUTION
Risk of software damage
Only set the date or time forward. Setting an earlier date or time
causes a trap that requires reloading the OPC to recover.
Always use the OPC Date tool to change the date or time. Using
the Unix shell command to set the clock does not properly update
the system data.

You can also specify whether the OPC clock uses the system’s 1 Hz pulse as
its source.
UNIX shell tool

The UNIX shell tool is available through the OPC User session manager. It
provides access to the UNIX shell when it is necessary to execute UNIX shell
commands.
Port Configuration tool

Use the Port Configuration tool to access a menu-based user interface for
configuring the OPC serial ports. By selecting the appropriate options from a
succession of menus you can completely configure each port.
CS-10053
CS-10053
Port Configuration Main Menu
1 Query Port Configuration

2 Configure a service
3 Unconfigure a service
4 View config_port file
9 Exit
Enter the number for your selection:
IP Routing Admin tool

The IP Routing Admin tool is a menu-based user interface for adding and
deleting entries from the gateway to network routing table. This tool is used to
define the gateways that connect networks when TCP/IP is enabled. The
gateway to network routing table allows communication between the local
network and remote networks.
OPC status tool

Use the OPC status tool to view information about the OPC.
OPC Name: OPC111PP

OPC Function: Primary
OPC Status: Active
Network Element: 111 NE111
SW Version: ACNL14VN
Backup OPC Status: Unknown
Network administration toolset

Network administration includes assigning serial telemetry displays to TBOS
ports and cluster alarms to specific signal distribution points, and monitoring
the alarms for both. Also included are managing the STS-1 connections,
assigning services to DS1s, setting line card events as either alarms or logs,
and defining the alarm severity where appropriate.
The network administration toolset includes the following tools:

• Telemetry - TBOS
• E2A Alarm Manager tool
• Configuration Manager tool
• Connection Manager tool (DS1 only)
• Data Direct Manager tool
• Cluster Level Inventory tool
• Host Provisioning Manager tool (DS1 only)
• Alarm Provisioning Manager tool

E2A Alarm Manager tool

The E2A Alarm Manager provides parallel telemetry for the cluster of network
elements under an OPC span of control. With this tool you can assign a cluster
alarm to a signal distribution point, monitor the cluster-wide alarm states, and
specify which cluster-wide alarm is transmitted to remote monitoring
equipment.
CS-10055
CS-10055
>. E2A Alarm Manager
Active Network Elements
Network Element Equipment
>. 7 RFT RFT
>. 8 RFT FCOT
Signal Distribution Point Assignments

SDP Status Condition Assigned Alarm
1 On Active See Assignment at the NE
2 On Inactive See
3 On Inactive See 1 Assign SDP... S
4 On Active See 2 Unassign SDP
5 On Inactive See 3 Cluster default
6 On Inactive Una 4 Select
7 On Inactive Una 5 Deselect
8 On Inactive Set
9 On Active Any 6 Help H
10 On Inactive Set
Connection Manager tool

Use the Connection Manager tool to:
• View, set up, delete, or change all STS-1 connections in the configuration.
• Designate the type of traffic to be carried by DS1 facilities (TR-303 DMS
or GR-303 MVI traffic). E1 facilities use the FAMCI and CVV5 toolsets
for this purpose, instead of the Connection Manager tool.
• Provision nodal default connections to STS-1 cross-connects on DS1/E1
systems.
• Audit and back up connection data.
CS-10223
CS-10223
> . Connection Manager View Options
Connections sorted by End NE A
Showing: All STS-1 connections
Connection ID End NE A Tributary End NE Z Tributary Chann
[ Add +] [ Manage VT Connections... 3]

Cluster Level Inventory tool

Use the Cluster Level Inventory tool to generate and print reports on the
hardware components in the cluster. You can select an inventory report for a
domain or a summary report for that domain. Reports can also be saved for
retrieval at a later date.
CS-10058
CS-10058
>. Cluster Inventory Options
NE ShPos Slt Equip Id Type Service PEC Info Serial No. RL SW

9 RFT 1 Show Inventory Shf+F4 >>
1 NEs K 2 Sort by
10 CE RFT >>
2 shelves F 3 Summarize
>>
3 circuit packs Z
4 slots J 4 Choose Type
>>
5 Choose Service >>
6 Choose PEC >>
7 Choose PEC vintage >>
8 Choose REL (release) >>
9 Choose SW (version) >>
10 Choose Circuit Pack State >>
11 Save Report... S
12 Show Inventory Timestamps... T
13 Print details P
14 Help H
[ Retreive B] [ Update U] [ Save report S]
Host Provisioning Manager tool

The Host Provisioning Manager tool identifies the switches (hosts) to which a
Cornerstone system is connected.
FW-22168
FW-22168
>. Host Provisioning Manager
RFT: > <
IG Host Interface Primary
[ Add +]
Using the Host Provisioning Manager, you can select an HDT from the list of
provisioned HDTs in the OPC span of control. After you select an HDT, the
system displays the following:
• host names provisioned on the HDT
• interface group (IG) numbers
• interface types (GR-303 DMS or GR-303 MVI)
• the primary alarm recipient indicator

Alarm Provisioning Manager tool

Use the Alarm Provisioning Manager tool to set line card trouble events as
either logs or alarms. With the alarm setting you can also define the alarm
severity level. The alarm setting could apply to a group of network elements
within the OPC span of control, a single network element, or a line card on a
network element.
CS-10060
CS-10060
>. Alarm Provisioning Manager
[ Line card alarm provisioning L]
Network surveillance toolset

Network surveillance functions are designed to locate failures by monitoring
network status and alarm activity at the network element level. Network status
information includes both current and historical data on alarm, protection, and
performance for all network elements. Alarm activity information includes the
alarm counts for all the network elements and a brief summary of each active
alarm. The display can be modified to show a maximum number of alarms of
a specific severity, for a specific network element, within a specified time.
A number of tools are available to monitor the status of the network. You can
customize the display to include information for all the network elements in
the OPC span of control for elements of particular interest to you.
CS-10252
CS-10252
>. User Session Manager : netsurv

Network Surv. 2 >.OK OPC Status:Primary/Active
Alarm Monitor 3 >.OK Alarm Monitor
Network Summary 4 >.OK NE Login Manager
Event Browser
Network Browser
Utilities
NE Login Manager
DMSTerm
Password Update
[ Logout ]
The following network surveillance toolset includes the following tools:

• Alarm Monitor tool
• Network Summary tool
• Network Browser tool

Alarm Monitor tool

Use the Alarm Monitor tool to display alarm counts for the network elements.
You can modify the display to show specific alarms in a specific order and in
greater detail, and you can print alarm details for selected alarms. With this
tool you can also select automatic or manual updating of the alarm list.
CS-10044
CS-10044
>. Alarm Monitor Options
Critical Major Minor Warning FailProt Lockout ActProt PrfAlrt
Network View . 1 3 20 . . . .
Alarms sorted by severity [ ] Auto Update List

Showing: All Severities, All NEs
NE# NE Name Alm# Cls Sh Type Unit Reason Updated Sev
1 Filter... F
71 ack 0 Fac 1 DS3 G1 1 Rx loss of signal 12:48:42* M,SA
2 Sort >>
+ 70 NewEngl 384 Env 1 CE Telemetry Input 1 08:38:57 m,nsa
3 Update List
+4816 Amsterd 139 Env 1 CE Telemetry Input 1 08:38:35 m,nsa
71 ack 23 Fac 1 DS3 G8 3 Rx AIS 12:48:43* w,SA
4 Help H
Network Summary tool

Use the Network Summary tool to monitor changes in the number of alarm,
protection switching, and performance alerts for network elements. This
includes counts of both cleared and new alarms.
CS-10045
CS-10045
>. Network Summary Protection
Critical Major Minor Warning FailProt Lockout ActProt PrfAlrt
Network View . . *1* . . *2* *1* .
Showing alarms: active and (*) New since reset (*) Cleared since reset
Network Element Reset Crit Major Minor Warn Fail Lock ActP Prf
1 Ottawa On 14:46 Act . . . . . . . .
New . . . . . . . .
Clr . . . . . . . .
+2 Montreal_108 18:46 Act . . . . . 1 . .
New . . 1 .Reset Counts
. . 1 . .
Clr . . . . . . . .
+3 MONTPQ01D33 18:46 Act . . 2 .Select . . >> . 1 .
New . . 3 .Deselect
. . >> . . .
Clr . . . . . . 1 .
4 Ottawa_ne_4 Jun23 Act . . 4 .Help . . H . . .
New . . . . . . . .
Clr . . . . . . . .
+5 Ottawa_ne_5 18:46 Act . . . . . 1 . .
New . . . . . 1 . .
Clr . . . . . . . .
Event Browser tool

Refer to “Event Browser tool” on page 5-12 for information on this tool.

Network Browser tool

Use the Network Browser tool to view network status information such as
alarm, protection and performance data for all network elements. You can also
display a summary of protection switching data or details about a shelf in a
network element.
CS-10042
CS-10042
>• Network Browser
Network: Atlantic Canada

System: Atlantic 1
Network Element Fac Eqp Env FailProt Lockout ActProt PrfAlrt

1 St.John's . . . . . . .
2 Halifax . . . .
1 Protection .
summary . .
3 Charlottetown . . . .
2 Shelf details. . .
4 Sydney . . . . . . .
5 Gander . . . .
3 Select . >> . .
6 Yarm . 1m . .
4 Deselect DS3 >> . .
7 Frederickton . . . . . . .
8 Gaspe . . . .
5 Help . H . .
9 Moncton . . . . . . 3
10 Goose Bay . . . . . . .
11 Truro . . . . . . .
SLAT toolset
SLAT functions include bringing a new system on line or upgrading an
existing one, managing configuration data, defining the test type for network
elements, and loading or upgrading the software in network elements.
The SLAT toolset includes the following tools:

• Commissioning Manager tool
• Configuration Manager tool
• PGTC/MTA Provisioning Manager tool
• Reboot/Load Manager tool
• OPC Shutdown tool
• OPC Date tool
• OS Connection Manager tool
Commissioning Manager tool

Use the Commissioning Manager tool to bring a new system, or a new network
element within an existing system to an operating level.
CS-10061
CS-10061
> . Commissioning Manager Options
System: NE06 OPC Serial Number: A1e3e0146
1. [ Clear commissioning data 1]
2. [ Edit system data 2]
=> 3. [ Commission new network element 3]
Commissioned network elements:

NE Type Function FCOT Serial Number OPC
9 ABM RFT 10 A2 1 0403379
10 ABM RFT - A2 7 0403380 Primary
4. [ Transfer data to Primary OPC (from SLAT OPC) 4]
5. [ Transfer data to Backup OPC (from Primary OPC) 5]
Event Browser tool

Refer to “Event Browser tool” on page 5-12 for information on this tool.
Reboot/Load Manager tool

Refer to “Reboot/Load Manager tool” on page 5-10 for information on this
tool.
OPC Shutdown tool

Refer to “OPC Shutdown tool” on page 5-16 for information on this tool.
OPC Date tool

Refer to “OPC Date tool” on page 5-16 for information on this tool.

OS Connection Manager tool

Use the OS Connection Manager tool to define connection profiles and
manage virtual circuit connections. With this tool you can create a new OS
connection profile, and modify or delete an existing connection profile. You
can also define or change the protocol identifier that is used to identify the type
of messages from the OS that the OPC will process, and define or modify the
target identifiers for testing and non-testing OSs.
CS-10062
CS-10062
>. OS Connection Manager Options
Primary Second User Name Remote AddressOS OPC VC Init

OOS Normal gamma 123451 Edit NMA bckup swtch inbnd
IS Normal Alpha 4041234567
2 Select NMA >>prime swtch inbnd
OOS Normal gamme 123453 Deselect
NMA >>prime swtch inbnd
4 Connect
5 Disconnect
6 Reset
7 Delete
8 Help H
Provisioning administration toolset

Provisioning administration includes managing the STS-1 connections,
designating the type of traffic to be carried by the DS1s feeding each HDT,
setting line card events as either alarms or logs, and defining the alarm severity
where appropriate.
The provisioning administration toolset includes the following tools:

• Provisioning Manager tool
• Default Provisioning Manager tool
• Host Provisioning Manager tool
• Connection Manager tool
• Data Direct Manager tool
• TR-08 Def. Prov. Manager tool
• Alarm Provisioning Manager tool
Connection Manager tool

See “Connection Manager tool” on page 5-20 for information on this tool.
Host Provisioning Manager tool

See “Host Provisioning Manager tool” on page 5-22 for information on this
tool.
Alarm Provisioning Manager tool

Refer to “Alarm Provisioning Manager tool” on page 5-23 for information on
this tool.
Utilities toolset
Utilities provide user management functions such as creating authorized users
for the OPC, creating and maintaining user groups, and performing security
checks when a user signs on to use the OPC or to access a remote network
element from the OPC.
The utilities toolset includes the following tools:

• NE Login Manager tool
• Password Update tool
• Remote OPC Login tool
• Logout tool
NE Login Manager tool

Use the NE Login Manager to log in to one node at a time from the OPC. You
can log in to a node in two ways: auto login, which allows you to log in directly
to a node without entering a userID and password, and login, which requires
you to enter a userID and password for the session.
When this tool is started, it displays a list of all the nodes that have established
communications with the OPC. From this list you can select a node to log in
to. You can also update this list periodically to include nodes that have
established communications with the OPC since the last update.

CS-10064
CS 10064
>. NE Login Manager
1 Exit )
Available Nodes:
2 Help H
NE ID NE Name
35 Ottawa
1 Refresh list R
36 London
Network Element: > 36 London 2 Help H
[ Auto login U] [ Login L] 1 Select

2 Deselect
3 Auto login
4 Login
5 Help H
[Refresh list R]
Password Update tool

Use the Password Update tool to change your OPC login password.
CS-10047
CS-10047
>. Password Update for: User1
1 Exit )
2 Help H
Enter old password followed by Return
[ Update ]
To be acceptable, a password must meet certain criteria. If the password you

select fails to do so, you are prompted to select a new password.

6-1
Network element user interface

procedures 6-
This chapter contains procedures for common network element user interface
tasks. Use these procedures as required during testing, or when reference is
made to them in other procedures.
Chapter task list

The following table lists the tasks that are documented in this chapter.
If you cannot successfully complete these procedures, contact your next level
of support.
Task Procedure Refer to
Connecting a local terminal to the network element 6-1 page 6-3

LCAP
Connecting a remote VT100-compatible terminal using 6-2 page 6-5

an external modem
Logging in to the network element, and logging out 6-3 page 6-7
Logging in to the far-end NE from the local NE 6-4 page 6-11
Logging in to a network element from the OPC, and 6-5 page 6-13
logging out
Logging in to the Cornerstone toolset 6-6 page 6-16
Opening a network element user interface session from 6-7 page 6-17
other levels of the interface
Working with line cards 6-8 page 6-20
Determining NE status on V5.2 systems 6-9 page 6-22
6-2 Network element user interface procedures
Requirements
Before performing the procedures in this chapter, review the following
requirements.
• Procedures involving connection to a network element (NE), require the

following:
— you must have a terminal. It may be a VT100-compatible terminal or
laptop computer with VT100 terminal emulation. (The customer is
responsible for obtaining the laptop computer and emulation package
from a third-party source.)
— you must obtain an RS-232C cable terminated with D-subminiature
25-pin male connectors, such as NT7E44FA (5 m, 16 ft) or NT7E44FB
(20 m, 66 ft)
Note: If you use a VT100-compatible terminal that has a 9-pin connector

rather than a 25-pin connector, it supports only some of the standard
RS-232 signals. The standard RS-232 signals are CD, TXD, RXD, CTS,
DSR, DTR, and RTS. Terminals with 9-pin connectors, such as North
American models of the VT320 and VT420, support only TXD, RXD,
DSR, and DTR. Use of these terminals is not recommended. However,
if you attempt to use such a terminal, connect together pin 1 (CD) and
pin 4 (DTR) of an NT7E44RA (or RB) at the 25-pin end. Even this
modification may not permit you to communicate from these terminals.
• Procedures involving the NE user interface, require the following:

— network element software has been loaded
— you must have a terminal connected to the NE
— you need a userID and password that allows access to the network
element
— you must be familiar with the network element user interface. A
description of the NE interface is given in Chapter 1. Some procedures
also require use of the operations controller (OPC) user interface.
Description of the OPC user interfaces are provided in Chapter 2 (CMT
user interface) and Chapter 3 (graphical user interface).
Requirements unique to a procedure are listed in the procedure itself.

Procedure 6-1
Connecting a local terminal to the network element
LCAP
Use this procedure to:
• connect a local user terminal to the network element
• set the communication parameters of the user terminal
• display the login screen
Action
Perform the following steps:
1 Connect the RS-232C cable to the user terminal according to the
manufacturer’s instructions.
2 Connect the RS-232C cable to the female D-subminiature 25-pin connector
on the local craft access panel (LCAP) as shown in Figure 6-1 for the single
HDT and dual HDT LCAPs, respectively.
Figure 6-1
LCAP RS-232 ports
FW-11339
25-pin female D-sub

user interface port
FW-11339
RS-232
User
interface
port
3 Plug in the power cord and switch on power to the user terminal.
—continued—
Procedure 6-1 (continued)

Connecting a local terminal to the network element LCAP
4 Set the terminal communication parameters according to the manufacturer’s

instructions. The following are the factory default values for the LCAP port:
Parameter Values
data bits 8
baud rate 9600
stop bits 1
parity none
echo no local echo (full duplex)
flow control xon/xoff
5 If your terminal has the Autobaud feature turned on, press Return twice.
Otherwise, press the Break key once.
The prelogin screen appears.
6 If the prelogin screen fails to appear, try the following, as necessary:
• Check whether your VT100-compatible terminal has a 9-pin connector. If
so, see the note on page 6-2.
• Find out from your system administrator if the communications
parameters for this LCAP have been altered.
• Try a different RS-232C cable.
7 Leave the terminal powered up.
—end—

Procedure 6-2
Connecting a remote VT100-compatible terminal
using an external modem
Use this procedure to connect a remote VT100-compatible terminal to user
interface port 1 using an external modem.
Requirements
Verify that the remote terminal has been configured for VT100 emulation. The
following are default parameters (these are found on the terminal
communication setup screen):
• VT100
• data bits (8)
• stop bit (1)
• parity (none)
• no local echo (full duplex)
• baud rate = 2400 (most modems, default for modem [DTE] port on shelf
right wing)
To perform this procedure, one user interface cable, NT7E44EA or EB, is
required.
Action
1 Connect the 9-pin end of the NT7E44EA/EB user interface cable to the port
1 connector J08 on the left hand side of ABM shelf.
2 Connect the 25-pin end of the cable directly to the modem. Pin assignments
for the shelf connector are provided in the following table:
Pin Function Pin Function
8 DCD 6 Not connected
3 Rx 4 RTS
2 Tx 5 CTS
20 DTR 1 Not connected
7 GND
—continued—

Connecting a remote VT100-compatible terminal using an external modem
3 Ensure that the User Interface Port 1 baud rate is set to 2400. Set these
parameters in the NEUI, from a local or LAN connection.
Enter:
admin ip ↵
dtlport 1↵
chgstate oos ↵
yes ↵
edit ↵
baudrate 2400 ↵
quit ↵
chgstate is ↵
4 Set the following parameters for the external modem:
Assignment On or Off
Enable DTR recognition On
Provide word result codes On
Send result codes On
Echo commands Off
Auto-answer enable On
Carrier detect On
RJ-11 jack On
Enable commands Off
Enable RTS detection Off
Constant CTS On
Note: The above setup procedure provides default configuration parameters
for user interface port 1. These default configurations are used when the shelf
is first installed or after a system reboot. However, these user interfaces may
have been reprovisioned. In this case, the terminal, or modem, or both, must
be configured accordingly.
—end—

Procedure 6-3
Logging in to the network element, and logging out
Use this procedure to:
• log in to the network element user interface from a local terminal
• log out of the network element session, and log out of the terminal
Action
Logging in

1 Display the login screen by pressing the Break key (or Keypad 5). If your
terminal has the Autobaud feature turned on, press Return twice instead.
The terminal displays the prompt: ?
2 Enter:
login ↵
The terminal responds with: Enter User Name
3 Enter:
<userID> ↵
The terminal responds with: Enter Password
—continued—

4 Enter:
<password> ↵
The Network Element Status screen appears, as shown below. You are now
logged in.
C
CS-10216
1 . . . 1 . . . .
S/DMS Nodes
2
5 1 . . . . . * .
6 PerfMon
7 FWPUI:
8
9
10 Protectn
11
12
13 JackAcc
14
15 Equipmnt
16 Facility
17 Admin
18 Help
NE 1
Time 20:13 >
Note: If you cannot log in, obtain the current user ID and password from your
system administrator.
If you are the ninth person trying to log in, your login attempt will be rejected.
See page 6-10 for additional explanation.
If the system locks you out while you are typing your user name or password,
you or someone at another terminal might have accidentally typed Ctrl_S.
This prevents further keyboard input from any terminal connected to the DTE
and DCE ports of the network element.
To correct the lockout, type Ctrl_Q at your terminal, then retry this procedure.
If you are still locked out after typing Ctrl_Q, connect a terminal to the other
port (DCE or DTE), type Ctrl_Q, then retry this procedure.
—continued—


Line-by-line terminal
To provide a usable display at a line-by-line terminal, enter:

mapci nodisp ↵
fwpui ↵
Note: The line-by-line terminal has a very limited display capability, so only
experienced system users should use it.
Displaying the main menu

From any screen in the user interface, including the command interpreter (CI)
level, you can display the main menu (Network Element Status screen) of the
network-element user interface. At a VT100-compatible terminal, enter:
fwp ↵
If fwp is not recognized by the system, enter the command string:
mapci;fwpui ↵
Closing FWPUI
At any level in the UI menu hierarchy, you can close the network element user
interface session and display the command interpreter (CI):
quit all ↵
The command interpreter prompt (>) appears.
Logging out
At any level in the UI menu hierarchy, including the CI level, you can log out
directly, by entering:
logout ↵
The user interface ports on the network element have an autologout feature. If
you did not logout normally, the user interface session automatically
terminates five seconds after one of the following events:
If, once you turn off power to the user terminal, the DTE connection is lost:
• such as if the RS-232 cable to the LCAP is unplugged.
• such as if the modem carrier signal is lost, or if the cable to the Modem
connector on the left-side interconnect is unplugged.
—continued—

If you cannot log in to the FWPUI

The FiberWorld product user interface (FWPUI) can be accessed by way of
two local physical ports and up to eight remote login sessions. However,
FWPUI can be in use by up to eight users at any time, not ten.
The local ports are the DTE port on the LCAP and the DCE port on the side
interconnect left circuit pack. One login session to FWPUI is supported from
each local port. The eight remote login sessions can include a login session
from another network element, and rlogin sessions from an OPC using the
rlogin manager.
If eight remote login sessions are in progress, then one of the following
messages appears to the person trying to log in to the ninth FWPUI session:
“Unable to connect to remote host: no session entity”
(if attempted from an OPC rlogin session)
“Could not connect to server”
(if attempted from another network element FWPUI session)
These messages are displayed because the communication connection to the
network element cannot be established when all remote communication ports
are in use. The messages will also be displayed if the network element is not
operational (software is not running) or if connection to the network element
is not possible due to network connectivity problems.
If eight login sessions are in progress, and at least one of the sessions is via the
local port, then the following message appears to the person trying to establish
the ninth login session:
“Maximum of 8 FWPUI sessions already active. Try again
later when some of the users currently logged in, have
logged out or quit from FWPUI.”
This message appears because, although the communication connection to the
network element is established (one local port and one remote port were
available, or two remote ports), the maximum number of FWPUI login
sessions is exceeded. In this condition, the user is locked out of FWPUI, but
retains the communication connection, with access to the command interpreter
(CI) and MAPCI. The user can continue in a CI or MAPCI session, or cancel
the communication connection using the logout command.
—end—

Procedure 6-4
Logging in to the far-end NE from the local NE
Use this procedure to log in to the far-end network element from the local
network element.
Requirements
You must be logged in to the user interface of the local network element, not
the OPC. (If you are logged in to the OPC user interface, then use the
procedure “Logging in to the network element from the OPC, and logging out”
on page 6-13 to gain access to another network element.)
You must have a username (userID) and password for the far-end network
element.
Action
1 If you do not know the NE number of the far-end network element, display a
list of NEs by entering:
listnes ↵
A list of network element number displays.
2 From any screen of the local network element user interface, log in to the
far-end network element:
rlogin ne <NE #> ↵
The login screen for the far-end NE appears, with the following prompt:
Enter User Name
3 Enter:
<username> ↵
The terminal responds with:
Enter Password
4 Enter:
<password> ↵
You are now logged in to the far-end network element. (You also remain
logged in to the local network element.)
Note:
• If you can’t log in, obtain the current userID and password from your
system administrator.
• If you are the ninth person trying to log in, your login attempt will be
rejected. See page 6-10 for additional explanation.
—continued—

Logging in to the far-end NE from the local NE
5 To log out of the far end and return to the local network element user interface,
enter the following command from any screen:
logout ↵
You are logged out of the far-end network element and the CI screen appears
for the local network element.
6 Display the main screen for the local network element:
fwp ↵
The Network Element Status screen appears for the local network element.
Note: When you need to log in to the far-end network element again, repeat
this procedure from step 2.
—end—

Procedure 6-5
Logging in to a network element from the OPC, and
logging out
Use the following procedure to log into or out of a network element from the
OPC. You can log in directly using the Auto login button. The tool then uses
the userID you entered for the current session. You can also log in by
specifying a new userID for this login session only. The maximum number of
NE login sessions from an OPC is 12.
Note 1: The Network Element field is case sensitive. Either select the node
from the Available Nodes list or type the network element name exactly as
it appears in the list.
Note 2: If you are denied access to the node, you can return to the NE
Login Manager main window by pressing Ctrl_B. When the question mark
(?) prompt appears, type “logout” then press Return.
Action
The following procedures describe how to log into and out of an NE.
Logging in
To log in, perform the following steps:
1 Log into the OPC and open the NE Login Manager tool.
The NE Login Manager main window appears.
FW-22023
FW 22023
>. NE Login Manager

Available Nodes:
NE ID NE Name
35 Ottawa
36 London
Network Element: >
[ Auto login U] [ Login L]
[Refresh list R]
—continued—

Logging in to a network element from the OPC, and logging out

• if you know the NE ID or name you want to use, type the ID or name
directly in the Network Element field and go to step 4.
• If you do not know the NE ID or name that you want to use, go to step 3.
3 Tab to the Available Nodes list and select the node that you want.
The ID (and name) of the selected node appears in the Network Element
field.
• if you want to log in with the same userID and password used to log in to
the OPC, then go to step 5.
• if you want to log in using another userID and password, then go to step
6.
5 To log in without reentering your userID and password, select the Auto login
button.
If a connection is possible at this time, you are logged in directly to the node.
The Network Element Status Screen of the network element user interface
displays. You can now enter network element commands.
CS-10216
CS-10216
1 . . . 1 . . . .
S/DMS Nodes
2
5 1 . . . . . * .
6 PerfMon
7 FWPUI:
8
9
10 Protectn
11
12
13 JackAcc
14
15 Equipmnt
16 Facility
17 Admin
18 Help
NE 1
Time 20:13 >
Note: If the Auto login was not successful, you will be prompted for a different
userID and password.
—continued—


Logging in to a network element from the OPC, and logging out
6 To log in by specifying a userID and password:

a. Select the Login button.
A blank screen appears, followed by the userID prompt.
FW-21218
FW-21218
Trying...
Trying...
Enter User Name

>
b. Type the following:

<userID> ↵
The password prompt appears.
c. Enter:
<password> ↵
Note: If the userID and password are correct, and connection is possible at
this time, you are logged in to the node. The Network Element Status Screen
of the network element user interface appears. You can now enter network
element user interface commands.
Logging out
To log out, perform the following steps:
7 When you no longer need the connection, log out from the network element
by typing:
logout ↵
A message appears, prompting you to press Return.
8 Press Return to return to the NE Login Manager main window, then close the
tool.
—end—
Procedure 6-6
Logging in to the Cornerstone toolset
Use this procedure to log in to the Cornerstone toolset from the network
element user interface (NEUI).
Action
1 From any screen on the NEUI, quit to the CI level of the user interface by
entering:
quit all ↵
The CI prompt appears.
2 Log in to the Cornerstone toolset by entering:
cornerstone ↵
You are now logged into the Cornerstone toolset, and can enter any of the
Cornerstone tools by entering the tool name (CVALRM, CVEQPT,
CVLOADER, CVPATH, CVPROV, CVSPMN, VLCMCI).
—end—

Procedure 6-7
Opening a network element user interface session
from other levels of the interface
Use this procedure to open a network element user interface session at a
different level, while already logged in. You can begin either a full-screen or a
single-line session.
This procedure is most often used after you have finished an OPC session from
the network element and you want to return to the network element user
interface session.
Use Figure 6-2 to identify whether you are at the command interpreter (CI)
level or the maintenance and administration position command interpreter
(MAPCI) level.
Figure 6-2
Interface levels
FW-2529
CI software FW-10175
quit mapci
command command
quit all fwp

command MAPCI software command
quit fwpui
command command
NE User Interface software
Requirements
Identify your current network user interface level.
—continued—

Opening a network element user interface session from other levels of the interface
Action
1 Decide what type of user session you want:
If you want a... then go to...
full-screen session step 2.
single-line session step 3.
Note: The single-line session provides very limited screen display capabilities
and is intended for experienced users.
2 You can begin a full-screen session from both levels of the interface as
follows:
If your screen prompt is:... then enter...
CI fwp ↵
MAPCI fwpui ↵
Note: The Network Element Status screen appears.

CS-10216
CS-10216
1 . . . 1 . . . .
S/DMS Nodes
2
5 1 . . . . . * .
6 PerfMon
7 FWPUI:
8
9
10 Protectn
11
12
13 JackAcc
14
15 Equipmnt
16 Facility
17 Admin
18 Help
NE 1
Time 20:13 >
—continued—


Opening a network element user interface session from other levels of the interface
3 You can begin a single-line session from either level of the interface as
follows:
If your screen prompt is:... then enter...
CI mapci nodisp; fwpui ↵
MAPCI quit all; mapci nodisp; fwpui ↵
Result: The single-line network element user interface appears.

FW-2531
FW-2531
MAPCI > FWPUI:
4 To end a session from any screen in the network user interface, log out from
the network element by typing:
logout ↵
A message appears, prompting you to press Return.
5 Return to the NE Login Manager main window and close the tool.
Changing your network element password

The OPC controls user identifiers and passwords. To change the network
element password, you must log in to the OPC and change your password as
described in the procedure “Changing your password” on page 7-36.
—end—
Procedure 6-8
Working with line cards
Use this procedure to access the Line Card Provisioning screen and change the
State of a line card. This procedure applies to all switch interfaces.
Requirements
Identify your current network user interface level.
Action
1 From any screen on the NEUI, enter either of the following commands:
eq vplc vp <vpid> <line> ↵
or
eq vplc v5 <interface> <port ID>↵
or
eq crvlc <ig #> <crv> ↵
or
eq almlc <lc instance> ↵
2
The line card equipment screen displays.
3 You can change the state of the line card by entering either of the following:

chgstate oos ↵
or
chgstate is ↵
—end—
Procedure 6-9
Determining NE status on V5.2 systems
The "fa comm;ports v5 IF id" command presents the V5 NE Status Screen for
V5 interfaces provisioned using the “addif CI.” This screen provides much the
same information as provided by the “queryv5” CI command, but is
automatically updated as interface and link status’ change. All the commands
associated with this screen act only with respect to the posted interface. The
only exception to this is the NextIF command.
NE status commands
The following table lists and describes each of the NE status commands:
Command Description
NextIF This command posts data on the next provisioned interface. If

there is only one interface provisioned, the NextIF command has
no effect. If there are no V5 interfaces provisioned, an error
message is displayed.
DtlLink This command provides details about the selected link. The link
can be specified using either the link id number, or the E1 circuit
pack/port identifiers. For example to detail the link on E1 G1 2:
DtlLink L 2 ( L – link)
or
DtlLink f g1 2 ( F – facility)
—continued—

Command Description
ChgLink This command changes the link state to in-service or

out-of-service in the same fashion as the ChgLinkState
command. The link is specified with the L or F qualifier as in the
DtlLink command described above.
ClrLink This command removes the data displayed via the DtlLink
command.
ActIF This command activates the posted interface. It behaves

identically to the ActIF command.
DeactIF This command deactivates the posted interface. It behaves

identically to the DeactIF command.
—end—
Configuring LC Timings
It is possible to change the line card timing registers for all line cards on the
system. It should be noted that under normal conditions these values will not
need to be changed. These commands are only made available to provide
flexibility for the user. The following parameters can be configured:
Parameter Description
HIT_TIME_MAX The maximum time tip and ring can be shorted for the
line card to detect a "hit". A hit is considered noise and
is disregarded. Any short between tip and ring longer
than this value is considered an "event". An event can
be either a digit pulse, a flash or an on-hook. Default
value: 40 msec.
FLASH_TIME_MIN The minimum time tip and ring must be shorted for a
flash event to be recognized. Default value: 100 msec.
DISC_TIME_MIN The minimum time the tip and ring must be shorted for
an on-hook (or disconnect) event to be generated.
Default value: 1 sec.
IDIGIT_TIME_MIN The minimum time period between pulses that

separates pulse digits. For example, this time period
allows the line card know the difference between a "2"
digit pulse and two "1" digit pulses. Default value: 500
msec.
—end—

7-1
OPC user interface procedures 7-

This chapter contains procedures for common OPC user interface tasks. Use
these procedures as required during testing, or when reference is made to them
in other procedures.
Chapter task list

The following table lists the tasks described in this chapter. If you cannot
successfully complete these procedures, contact your next level of support.
Procedure Task Refer to
7-1 Connecting a terminal to an OPC page 7-4
7-2 Connecting a terminal to the portable OPC page 7-13
7-3 Connecting the portable OPC to the network element page 7-15
7-4 Connecting a remote terminal to the OPC using an page 7-17

external modem
7-5 Logging in to the OPC page 7-19
7-6 Logging in to the remote OPC from a local OPC page 7-23
7-7 Logging in to an OPC from a network element page 7-26
7-8 Logging in to the Cornerstone toolset page 7-28
7-9 Opening an OPC tool page 7-31
7-10 Closing an OPC tool page 7-33
7-11 Logging out of the OPC page 7-34
7-12 Changing your password page 7-36
7-13 Displaying OPC status page 7-39
7-14 Changing the name of an OPC page 7-41
7-2 OPC user interface procedures
Requirements
Before performing any of the procedures in this user guide, review the
following requirements:
• Procedures involving connection to an OPC or network element (NE),
require the following:
— You must have a terminal. It may be a VT100-compatible terminal or
laptop computer with VT100 terminal emulation. (The customer is
responsible for obtaining the laptop computer and emulation package
from a third-party source.)
— you must obtain the appropriate connection cable (see the section
“Cable connectors and pinouts” on page 7-5 for details on cable
requirements)
• Procedures involving the OPC user interface (such as logging on or

opening an OPC tool), require the following:
— You must have a terminal connected to the OPC with the OPC port
configured as terminal.
— You need a userID and password that allows access to the OPC.
— You need a userID and password that allows access to the network
element.
— You must be familiar with the OPC user interface (refer to Chapters 2
and 3 in this guide for descriptions of the character-mode terminal
(CMT) and graphical user interfaces respectively).
Other requirements specific to a procedure are listed in the procedure itself.

CAUTION
When handling the equipment, the following precautions
must always be observed.
Extreme temperatures Do not operate the equipment

immediately after exposure to extreme temperatures. If
exposed, leave it in room temperature environment for two
hours before operation. The operating range is 0°C to 40°C
(32°F to 149°F).
Static discharge A carpeted floor can generate a static
charge capable of damaging equipment. The use of
antistatic mats or antistatic carpets is recommended.
Air vents Do not obstruct air vents. Leave 76.2 mm (3 in.) in
front and behind to ensure adequate ventilation.
Safety earth ground The equipment must be provided with
an uninterruptible safety earth ground through the power
cord.
Servicing Any servicing, adjustment, maintenance, or repair
of this product should be performed only by trained service
personnel.
Power Before connecting power, make sure that the
equipment is configured for the local power source.
Equipment handling Improper handling could cause loss of
data or equipment damage. Avoid sharp shocks, and always
repackage the equipment in approved packaging before
transporting it from one place to another.
Procedure 7-1
Connecting a terminal to an OPC
Use this procedure to connect a local user terminal to a primary or backup OPC
via OPC port 1 (also referred to as OPC port B).
You can also reach the OPC by connecting a VT100-compatible terminal to a

network element on port 2 on the LCAP and logging in to the OPC from the
network element user interface.
OPC port 3 can also be configured for terminal communications. Port 3 is only
available on an ABM shelf (on an I/O card in slot 40) or on a portable OPC
(ESP port 2).
To access the OPC, use either a VT100-compatible terminal or a laptop

computer with a VT100 emulation package. If you want to connect an X
terminal to the OPC, refer to the chapter “OPC Ethernet port configuration and
connections” in this document.
Table 7-1 shows port locations and designations for an OPC in an ABM shelf.
Port connections can also be seen in following illustrations.
Table 7-1
Port locations and labels
UI Port ABM Shelf Port Connector
OPC Port 1 SIL OPC J07 9-pin (or DB9)
OPC Port 3 I/O slot 40 25-pin (or DB25)
NEUI 2 LCAP (DTE) 25-pin
SIL - side interconnect left panel

LCAP - local craft access panel
Note: OPC Port 2 is an EIA 530 port offering RS422 signals.

—continued—


Cable connectors and pinouts

A number of EIA RS-232C standard compliant cables can be used to connect
terminals to network element port 1; port 1 requires a 9-pin male connector.
Generally, a VT100-compatible terminal is equipped with a 25-pin connector,
whereas a laptop uses a 9-pin connector.
Nortel provides cables listed in Table 7-2.

Table 7-2
Terminal and laptop cables
Terminal Type OPC 1 (B) OPC 3 NEUI 2
VT100 or printer NT7E44RA/B NT7E44VA/B NT7E44FA/B
Laptop NT7E44SA/B NT7E44EA/B not supported
Note: Code endings A and B correspond to 5 m and 20 m cables, respectively. The

20 m cables are limited to a maximum of 9600 bps data rates. (The OPC supports
a maximum data rate of 9600 bps on OPC ports 1 and 3, regardless of cable length.)
Table 7-3 provides pinouts for the NT7E44RA and NT7E44RB cables.
Table 7-3
RS-232 cable pinouts
Pin number and function Wire color Pin number and function
(9-pin connector) (25-pin connector)
1 DCD BK 4 RTS
2 RXD BR 2 TXD
3 TXD R 3 RXD
4 DTR O 5 CTS
4 DTR Y 6 DSR
5 GND G 7 GND
6 DSR BL 20 DTR
7 RTS V 8 DCD
8 CTS W 20 DTR
9 Not connected — —
The network elements use the data carrier detect (DCD) line (pin 1) of the OPC
port 1 to ensure proper logging off when the terminal is disconnected or the
modem line is dropped.
—continued—

The North American version of the DEC VT320 and VT420 are two examples
of terminals that do not support the full RS-232 protocol through their RJ-11
connectors. This prevents the use of such terminals with the current
NT7E44RA/RB cable. The international version of these models support the
full RS-232 protocol (25-pin connector).
For such North American terminals to operate, the cable must be modified.
Connect pin 1 (DCD) to pin 4 (DTR) on the 9-pin connector side (going into
the OPC port 1 connector). This disables the security feature.
Table 7-4 provides pinouts for the NT7E44SA and NT7E44SB cables.
Table 7-4
Pinouts for NT7E44SA and NT7E44SB cables
9-pin connector at laptop 9-pin connector at ABM shelf

(see note 1)
Pin Signal Pin
1 DCD (data carrier detect) 4 see note 3
2 Rx (receive) 3
3 Tx (transmit) 2
4 DTR (data terminal ready) 6 see note 2
4 DTR (data terminal ready) 1 see note 2
5 signal ground 5
6 DSR (data set ready) 4 see note 3
7 RTS (ready to send) 8
8 CTS (clear to send) 7
9 not used
Note 1: Pin 9 at the ABM shelf end of the cable is not used.
Note 2: Pin 4 at the lap-top end of the cable connects to pins 1 and 6 at the ABM
shelf end of the cable.
Note 3: Pin 4 at the ABM shelf end of the cable connects to pins 1 and 6 at the Lap
Top end of the cable.
—continued—


VT100 terminal requirements

If you are using a VT100-compatible terminal, ensure that the configuration
settings are as shown in Table 7-5.
Table 7-5
Configuration settings for a VT100
Parameter Value
data bits 8
baud rate 9600
stop bits 1
parity none
duplex full (no local echo)
emulation VT100
scroll jump
autowrap off
—continued—

Figure 7-1
OPC and terminal connections
FW-11176
FW-11176
VT100 compatible
OPC
Port 1 (B)
Access
bandwidth
manager
OP
(J0 C
7)
Local craft
access panel
NEUI
Port 2


Action
1 Proceed as follows:
• If you are using a VT100-compatible terminal, then go to step 7.
• If you are using a laptop computer, then go to step 2.
2 Power up the laptop.
3 Consult and follow the vendor documentation for the emulation package you
are using to determine how to configure your laptop as a VT100-compatible
terminal.
4 If required by the emulation package, select the following options:
baud rate 9600
emulation mode VT100
port 1 (serial port A) as COM yes
data bits 8
stop bits 1
parity none
full duplex no local echo
scroll jump
autowrap no
protocol ASCII
modem type direct connect (no modem)
Note: For the rest of the options, accept the defaults.

See Table 7-6 on page 7-12 for a suggested key mapping assignment for
laptop function keys. This allows you to use the function keys for many of the
common VT100-terminal user interface functions.
5 Save the settings in the emulation installation program, as described in the
vendor documentation.
—continued—

6 Connect the laptop to the OPC by first connecting one end of the RS-232
cable to OPC port 1 on the network element, then connect the other end of
the cable to the serial port A on the laptop.
Go to step 12.
7 Connect the terminal to OPC port 1, using the appropriate RS-232 cable.
8 Power up the terminal.
9 Press Return.
The OPC login prompt (login:) should appear on your screen:
If the prompt... then...
does appear you are successfully connected. Go to the procedure
“Logging in to the OPC” on page 7-19 to log in to the
OPC.
does not appear go to step 10.
10 Check all connections between the OPC port and the terminal. Ensure that
the terminal is powered up, then repeat step 9. If the prompt still does not
appear, suspect that the port is not set up for terminal operation and proceed
to the next step.
11 Connect a VT100-compatible terminal to the network element, as described
in “Connecting a local terminal to the network element LCAP” on page 6-3.
13 Log in to the OPC from the network element.
The User Session Manager appears.
14 Select the Port Configuration tool.
The Port Configuration main menu appears.
1.Query Port Configuration
2.Configure a service
3.Unconfigure a service
4.Exit
15 Query the port configuration by entering:
1↵
The OPC displays the current state of all available ports.
—continued—


16 If a port other than port 1 is configured for terminal service or if port 1 is

already configured for a service other than terminal, they must be
reconfigured. Press Return to go back to the Port Configuration main menu,
then enter:
3↵
A service menu appears. The service menu is customized for the services
that are configured.
17 Select the item number that corresponds to the menu item you need to
unconfigure by entering:
<item number> ↵
Note: PPL services (if applicable) must be unconfigured before terminal
services. (If PPL services are not unconfigured, they will automatically be
disabled.)
18 Repeat step 17 for each port that must be unconfigured. Then, go to step 19.
19 Return to the Main menu by entering:
8↵
The Main menu appears.
20 Display the service menu by entering:
2↵
A service menu displays.
21 Select terminal service by entering:
1↵
22 Select OPC port 1 from the displayed options by entering:
1↵
A message similar to the following appears:
Warning: Configuration on port 1 is changing from X.25 to
terminal. Do you wish to continue? (Yes/No)
23 Confirm your action by entering:
y↵
• If terminal service is already configured on another port (such as 2 or 3),
the configuration fails and the following message appears:
Terminal configuration successful on port 1
24 You can configure the other ports to whatever service you want. Repeat steps
2 through 20 as required. Remember that only one port can be configured for
terminal service.
25 Exit the Config port program by entering:
9↵
—continued—

26 Log out of the OPC, and if required, log out of the network element.
27 Go back to the beginning of the procedure and repeat the connection
procedure to connect the terminal to port 1 (or B) of the OPC.
Table 7-6
Suggested key mapping assignment for laptop function keys
Where possible, assign the following keyboard equivalents to the function keys
indicated. When using the keyboard, the symbol “_” denotes that the Control key
must be held down while you press the other key. For example, in the command
Ctrl_A, the Control key is be held down while pressing the “A” key.
Function Keyboard Operation
key equivalent
F1 Ctrl_A Select—selects the object that is currently pointed to on

the screen
F2 Ctrl_L + Menu—displays the menu associated with the object

that you are currently pointing to on the screen
F3 Ctrl_L / Alternate menu—displays a list menu or chooser,

depending on what you are currently pointing to on the
screen
F4 Ctrl_L T Tool menu—displays the tool menu for the tool currently
in use
F5 Ctrl_F 1 Step scroll—moves the scrolling text field or list currently

pointed to forward by a small amount
F6 Ctrl_F 3 Jump scroll—moves the scrolling text field or list

currently pointed to forward by a larger amount
F7 Ctrl_L W Window area—displays the window menu for the tool

currently in use
F8 Ctrl_T Tool—switches to tool mode
F9 Ctrl_^ Abort—aborts an executing task
F10 Break—alerts the network element that the user wishes

to log in.
Consult the vendor documentation for the emulation
package you are using
—end—

Procedure 7-2
Connecting a terminal to the portable OPC
Use this procedure to connect a terminal to a portable (slat) OPC. It is
recommended that you use a laptop as the display terminal.
Action
1 Connect the VT100-compatible terminal to the portable OPC (see
Figure 7-2). Use the serial A port on the VT100-compatible terminal, and
Port B on the portable OPC.
Figure 7-2
Portable OPC terminal connection
CS-10243
CS-10243
VT100-compatible
(rear view)
Port B
Portable OPC
2 Power up the portable OPC. (takes up to five minutes.)

—continued—

Connecting a terminal to the portable OPC
3 Power up the VT100 terminal. If you are using a laptop computer, ensure that
you have configured the terminal as an OPC terminal (see the System
Administration Guide, ARSVD00400, for terminal configuration procedures).
4 If you are using a terminal emulation program, start it and connect to the
OPC. The procedure for doing this is different for each program.
The VT100 emulation screen appears.
5 Press Return on the VT100 terminal.
When initialization is complete, the OPC logon prompt (login:) appears on
your terminal screen.
—end—

Procedure 7-3
Connecting the portable OPC to the network element
Use this procedure to connect the portable OPC to the side interconnect left
circuit pack of the common-equipment shelf. It is recommended that you use
a laptop as the display terminal. Either a VT100-compatible terminal or a
laptop computer with a VT100 emulation package can be used.
Requirements
• All required software is loaded on the portable OPC.
• A CNet cable, 9-pin D-sub (M) to 9-pin D-sub (M) (NT4K86).
• Two control-network terminator plugs (NT7E5072).
Action
1 Connect the control-network cable to the CNET port on the portable OPC and
the Ctl Net In connector on the side interconnect left circuit pack on the
common-equipment shelf, as shown in Figure 7-3.
Figure 7-3
OPC connection to CNET
FW-10248
Common-equipment shelf
FW-10248
9-pin to 9-pin
CNet cable
Portable OPC
Note: Attach terminator
to unused CNet port.
—continued—

Connecting the portable OPC to the network element
2 Install control-network terminator plugs to cover unused control-network

ports on the portable OPC and on the side interconnect left circuit pack, as
Figure 7-4
CNET terminator plugs
FW-10247
FW-10247
Caution
Caution
Co
(J1nt Ne
0) t In
OCI-12
OCI-12 Active
Active LOS Co
(J0nt Ne
LOS Fail
Fail
9) t O u
t
Terminator
plug
—end—

Procedure 7-4
Connecting a remote terminal to the OPC using an
external modem
Use this procedure to connect a terminal to the OPC port using an external
modem.
Requirements
Verify that the remote terminal has been configured for VT100 emulation. The
following are default parameters (these are found on the terminal
communication setup screen):
• VT100
• data bits (8)
• stop bit (1)
• parity (none)
• no local echo (full duplex)
• baud rate = 2400 (most modems, default for modem [DTE] port on shelf
right wing)
Action
1 Connect one end of the NT7E44EA/EB 9/25-pin user interface cable to the
9-pin OPC port 1 connector J08.
2 Connect the 25-pin end of the cable directly to the modem. Pin assignments
for the shelf connector are provided in the following table:
Pin Function Pin Function
8 DCD 6 N/C
3 Rx 4 RTS
2 Tx 5 CTS
20 DTR 1 N/C
7 GND
Note: N/C = not connected.

3 Ensure that the OPC Port 1 is configured for terminal operation. (Refer to the
System Administration Guide, ARSVD00400, for the procedure on
configuring the OPC ports.)
—continued—

Connecting a remote terminal to the OPC using an external modem
4 Set the following parameters for the external modem:

Assignment ON or OFF
Enable DTR recognition ON
Provide word result codes ON
Send result codes ON
Echo commands OFF
Auto-answer enable ON
Carrier detect ON
RJ-11 jack ON
Enable commands OFF
Enable RTS detection OFF
Constant CTS ON
Note: The above setup procedure provides default configuration parameters

for OPC port 1. These default configurations are used when the shelf is first
installed or after a system reboot. However, these user interfaces may have
been reprovisioned. In this case, the terminal, or modem, or both, must be
configured accordingly.
—end—

Procedure 7-5
Logging in to the OPC
Use this procedure to log in to the active OPC using a VT100-compatible
terminal or laptop computer with VT100 terminal emulation. Logging in using
this method starts the login at the OPC login screen and results in the User
Session Manager being displayed. You can also use this procedure to log in
from an X terminal, in which case the login starts at the OPC login screen at
the X terminal.
Action
If you are using the... Then go to...
character-mode terminal (CMT) user interface step 1
graphical user interface step 6

1 At the OPC login screen, type your userID after the login prompt and press
Return.
FW-20299
FW-20299
login:
password:
2 At the password prompt, type your password and press Return.

Note: The password does not appear in the field when you type it. Do not use
capital letters unless the capitalization is part of the password, because the
system treats uppercase and lowercase letters differently.
—continued—

3 The following prompt appears:

Term = (VT100)
Press Return.
The opc> prompt appears.
4 You can start the User Session Manager, or if your userID is root, you can
execute certain script commands, as directed in the procedures.
If you plan to... then...
execute script commands you have finished this procedure.
open tools from the User Session continue at step 5.

Manager
5 Type the following:

opcui ↵
The User Session Manager window appears, displaying the tools that are
available to you.
FW-21059
FW-21059
>. User Session Manager : root

Software Admin 2 >. OK OPC Status : Primary/Active
Reboot/Load Manager 3 - Unix Shell
Backup/Restore Mngr 4 - Unix Shell
Event Browser
NE SW Delivery Mngr
Network Upgrade Mngr
OPC Admin
Central User Admin
Remote OPC SW Inst.
OPC Save and Restore
OPC Shutdown
OPC Date
Port Cofiguration
IP Routing Admin
Unix Shell
[ Logout ]
Note: You are finished with this procedure. If you want to open an OPC tool
listed in the User Session Manager window, see the procedure, “Opening an
OPC tool” on page 7-31.
—continued—


6 To log into the GUI, start your GUI interface then type your user ID in the User
ID field.
FW-21059
FW-21160
FIBER WORLD
This software contains material which is
confidential to Northern Telecom Limited
and is made available solely pursuant to
the terms of a written license agreement
with Northern Telecom Limited.
Copyright. Northern Telecom Limited, 1991
User ID:
Password:
Done Alt+Return
7 Tab to the Password field and type your password.

Note: The password does not appear in the field when you type it. Do not use
capital letters unless the capitalization is part of the password, because the
system treats uppercase and lowercase letters differently.
—continued—

8 Tab to the Done button and press the Alt_Return key; or click on the
Done pushbutton.
The Alt key is labelled Alt on NCD, Extend Char on HP, Left or Right or the
<diamond symbol> on SUN.
The workspace appears, displaying the tools available. You are logged into
the OPC. See Chapter 3 for details on using the graphical user interface.
FW-21699
FW-21699
Toolset icon Toolset A Toolset B Toolset C Toolset D
Pointer X
—end—

Procedure 7-6
Logging in to the remote OPC from a local OPC
Use this procedure to log in to a remote OPC with a graphical user interface
terminal session. CMTs do not have this ability. This procedure displays the
User Session Manager, not the graphical desktop for the remote OPC (at step
5). When you have logged in, you can perform any operation that can usually
be done on that OPC.
Requirements
Using the Commissioning Manager, ensure that the remote OPC has been
added to the list of OPCs that this OPC can reach.
Action
1 Display the Utilities toolset and select the Remote OPC Login tool.
The Remote OPC Login dialog appears.
FW-20656
Remote OPC Login
OPC:
Login Alt+Return Cancel Ctrl+Escape
2 In the OPC field, display the chooser menu by right clicking on the “- “ on the
right side of the OPC field and select the OPC that you want to log in to.
The name of the OPC appears in the OPC field.
—continued—

3 Select the Login button.

A session window appears with the Login prompt.
FW-20658
FW-20658
OPC LOGIN (OPCM001P)

login:
4 At the login prompt, type your userID and press Return.

The Password prompt appears.
FW-20659
FW-20659
OPC LOGIN (OPCM001P)

login: admin
Password:
—continued—


5 At the Password prompt, type your password and press Return.

Note: The password does not appear in the field when you type it. Passwords
are case sensitive.
You are now logged in to the remote OPC. The User Session Manager for the
remote OPC appears.
Note: Remember to log out when you no longer need the connection.
FW-21059
FW-21059

Software Admin 2 > . OK OPC Status : Primary/Active
Event Browser
NE SW Delivery Mngr
OPC Admin
Central User Admin
Remote OPC SW Inst.
OPC Shutdown
OPC Date
Port Cofiguration
IP Routing Admin
Unix Shell
[ Logout ]
—end—
Procedure 7-7
Logging in to an OPC from a network element
Use this procedure to log in to an OPC from a network element.
The following table lists the commands entered for logging in to an OPC from
a network element.
Command entered Host that is reached
rlogin opc sets up a session with the active OPC for the network
element that you issue the command from.
rlogin opc9999b sets up a session with the backup OPC that has an alias
of opc9999b.
rlogin opc9999p sets up a session with the primary OPC that has an alias
of opc9999p.
rlogin opc backup error message is returned. This parameter is not

supported in this release.
rlogin london does not set up a session if the real name of this network
element is London. For uppercase and lowercase names,
quotes must be used around the name.
rlogin this command invokes the listnodes command and the

user is requested to enter a valid name.
Action
1 From the network element user interface screen, type:
rlogin opc ↵
The login screen appears.
It is recommended that you use the opc name as the alias, that is, if you call
the primary OPC “opc9999p”, then this is the number you enter for the alias.
Similarly the alias for the backup is opc9999b. The alias name is the name
that is stored against the OPC serial number. In the current release, this is the
only way that you can set up a session with an OPC other than the active OPC
for the span of control that you are in.
2 Enter your userID after the login prompt and press Return. Your userID is
case sensitive.
You are prompted for a password.
—continued—


Logging in to an OPC from a network element
3 Enter the password after the password prompt and press Return. Your
password is case sensitive.
The password does not appear in the field when you type it.
4 If you log in as a root user, you access the UNIX shell layer of the interface.
To access the OPC user interface, enter:
opcui ↵
The User Session Manager appears showing you the tools that you are
allowed to use.
FW-21059
FW-21059

Event Browser
NE SW Delivery Mngr
OPC Admin
Central User Admin
Remote OPC SW Inst.
OPC Shutdown
OPC Date
Port Cofiguration
IP Routing Admin
Unix Shell
[ Logout ]
—end—
Procedure 7-8
Use this procedure to log in to the Cornerstone tool set from the OPC.
Action
1 Log in to the OPC and open the NE Login Manager tool.
The NE Login Manager main window appears.
FW-22023
FW-22023
>. NE Login Manager

Available Nodes:
NE ID NE Name
35 Ottawa
36 London
Network Element: >
[ Auto login U] [ Login L]
[Refresh list R]
If you... then go to...
know the NE ID or NE name type the ID or name directly in the

Network Element field and go to
step 3.
do not know the NE name or NE ID go to step 2.
—continued—


2 Tab to the Available Nodes list and move the cursor to the node that you want.
Select it by pressing Ctrl_A (or Keypad 0).
The ID (and name) of the selected node appears in the Network Element
field.
If you... then go to...
log in with the same user ID and password used to log in step 3.
to the OPC
log in using another user ID and password step 4.
3 To log in without reentering your userID and password, tab to the Auto login
button and select it by pressing Ctrl_A (or Keypad 0).
If a connection is possible at this time, you are logged in directly to the node.
The main menu of the network element user interface appears. You can now
enter network element commands.
Proceed to step 5.
CS-10216
CS-10216
1 . . . 1 . . . .
S/DMS Nodes
2
5 1 . . . . . * .
6 PerfMon
7 FWPUI:
8
9
10 Protectn
11
12
13 JackAcc
14
15 Equipmnt
16 Facility
17 Admin
18 Help
NE 1
Time 20:13 >
—continued—

4 To log in by specifying a userID and password:

a. Tab to the Login button and select it by pressing Ctrl_A (or Keypad 0).
A blank screen appears, followed by the userID prompt.
FW-21218
FW-21218
Trying...
Trying...
Enter User Name

>
b. Type your network element userID and press Return.

<userID> ↵
The password prompt appears.
c. Type your password and press Return.
<password> ↵
If the userID and password are correct, and connection is possible at this
time, you are logged in to the node. The main menu of the network
element user interface appears (as shown previously). You can now enter
network element user interface commands.
5 Quit to the CI level of the user interface by entering:
quit all ↵
6 Log in to the Cornerstone toolset by entering:
cornerstone ↵
You are now logged into the Cornerstone toolset, and can now enter any of
the Cornerstone tools by entering the tool name (CVALRM, CVEQPT,
CVLOADER, CVPATH, CVPROV, CVSPMN, CVTRAF, CVV5, and VLCMCI)
—end—

Procedure 7-9
Opening an OPC tool
Use this procedure to open an OPC tool.
Some tools allow you to open more than one instance of the same tool. For
example, you may have three instances of a tool open at one time. If a tool
cannot be opened because you have reached the maximum number of
instances, a disable icon appears in front of the tool name, and you must use
one of the open instances of the tool.
Action
1 Display the User Session Manager by pressing Ctrl_T 0.
The Session Manager displays.
FW-21059
FW-21059

Event Browser
NE SW Delivery Mngr
OPC Admin
Central User Admin
Remote OPC SW Inst.
OPC Shutdown
OPC Date
Port Cofiguration
IP Routing Admin
Unix Shell
[ Logout ]
2 In the User Session Manager window, look for the tool name in the Available
tools list.
If the tool name... then go to...
does not have a disable icon step 3.
has a disable icon step 4.
—continued—

Opening an OPC tool
3 In the Available tools list, move to the tool you want to open and select it by
pressing Ctrl_A .
A progress dialog appears while the tool is opening. Then the main window
for the tool appears.
Go to step 6.
4 If the disable icon appears beside the tool name, you cannot open the tool,
but you can use an open instance of the tool. Look for the tool name in the
Open tools list. If the tool you want to view is listed there, tab to the Open tools
list.
5 Move to the tool you want to use and select it by pressing Ctrl_A.
The main window for that tool appears.
6 You have completed the procedure. Return to the main procedure that
directed you to this procedure.
—end—

Procedure 7-10
Closing an OPC tool
Use this procedure to close an OPC tool.
If you have only one instance of a tool open, then this procedure closes the tool
and automatically displays the Session Manager, leaving you logged in to the
OPC.
If you have more than one tool (or instance of a tool) open, then you must
repeat this procedure to close each open tool. Alternatively, go to the Session
Manager and log out from the OPC, as explained in the procedure titled
“Logging out of the OPC” on page 7-34.
Action
1 Display the window menu by pressing Ctrl_L W (or Keypad 6).
The window menu is shown following:
2 Select the Exit command by pressing Space (or Keypad 0).

The tool closes. The Session Manager window appears.
—end—
Procedure 7-11
Logging out of the OPC
Use this procedure to log out of the OPC. This procedure automatically closes
all tools and removes their windows.
Action
1 If the Session Manager is not displayed, display it by pressing Ctrl_T 0.
The Session Manager window appears.
FW-21059
FW-21059

Event Browser
NE SW Delivery Mngr
OPC Admin
Central User Admin
Remote OPC SW Inst.
OPC Shutdown
OPC Date
Port Cofiguration
IP Routing Admin
Unix Shell
[ Logout ]
—continued—


Logging out of the OPC
2 In the Session Manager, tab to the Logout button and select it by pressing
Ctrl_A (or Keypad 0).
The following confirmation dialog appears.
FW-20664
FW-20664
Warning Logout will close all windows.
[ Logout Return ] [ Cancel ]
3 In the confirmation dialog, tab to the Logout button and press Ctrl_A (or
Keypad 0).
The confirmation dialog closes, the User Session Manager window closes,
and the login screen appears.
—end—
Procedure 7-12
Changing your password
Use this procedure to change your password for a particular userID on the
OPC. If you have a userID for some network elements and a different userID
for other network elements, you have to change the password for each userID
separately.
UserIDs are stored on the OPC. Therefore, you have different userIDs for
different spans of control.
Requirements
Select a new password that conforms to the security criteria of your
installation. It must be different from your current password.
A new password must meet the following criteria:

• the password must have between five and eight characters
• the first character must be alphabetic (a–z, lowercase only) or a $ symbol
• the remaining characters can be alphabetic (a–z, lowercase only), digits
1–9, _ (underscore), or a $ symbol
—continued—


Action
1 Open the Password Update tool.
The Password Update tool main window appears.
FW-21120
FW-21120
>. Password Update
Type in Old password and press Return
>
[ Update ]
2 Enter your old password by entering:

<old password> ↵
If the password you entered is correct, the field label changes from “Type in
old password followed by Return” to “Type in new password followed by
Return”.
If the password is incorrect, an X is placed beside the field and the field label
remains unchanged.
If... then...
the password is correct continue with the next step.
the password is incorrect repeat step 2.
you want to exit the tool go to step 6.
—continued—

3 Enter your new password by typing (the characters do not appear as you type
them but the cursor moves):
<new password> ↵
The field label indicates whether the new password is accepted or rejected.
If the password is accepted, the text above the field changes to “Retype new
password followed by Return”. If the password is rejected, an X is placed
beside the field.
If... then...
the password is correct continue with the next step.

the password is incorrect repeat step 2.
4 Reenter your new password by typing:

<new password> ↵
The field label confirms whether the new password is accepted or rejected.
If the password matches your previous entry, the field label changes to
“Password Match”, and the field is removed. If the passwords do not match,
an X is placed beside the field.
If... then...
the passwords match continue with the next step.
the passwords do not match repeat step 3.
5 Select the Update button by pressing Ctrl_A (or Keypad 0).

Your password is changed on the OPC for all network elements that you have
permission to access, and the new password is put into effect. The Password
Update dialog appears.
6 Close the Password Update tool.
—end—

Procedure 7-13
Displaying OPC status
Knowing which OPC you are logged in to is important when you are
performing data backups or restores, installing software, or commissioning
network elements. Use this procedure to display the following information
about a particular OPC:
• OPC name, as defined by the SLAT user during OPC commissioning
• OPC function, which can be primary, or out of service
• OPC status, which can be active, inactive, or out of service
• the network element in which the OPC is located
• the shelf in which the OPC is equipped
• the version of software that is currently running in the OPC
Action
1 Display the User Session Manager by pressing Ctrl_T 0.
The User Session Manager appears. Note that the OPC Status tool is at the
top of the Open tools list.
FW-20131A
FW-20131
>. User Session Manager : admin

Software admin 2 >. OK OPC Status : Primary/Active
Reboot/Load Manager
Backup/Restore Mngr
Event Browser
SW Optionality Mngr
SW Delivery Mngr
OPC Admin
Group and User Setup
Remove OPC SW Inst.
OPC Shutdown
OPC Date
Unix Shell
Network Admin
Network Telemetry
[ Logout ]
Note: The OPC Status tool is always open throughout a session; you cannot
close it. In the User Session Manager screen, it always appears in the Open
tools list, never in the Available tools list.
—continued—

Displaying OPC status
2 Tab to the Open tools list.

3 Move the cursor to the OPC Status entry in the list and select it by pressing
The OPC Status window appears.
FW-10796
FW-10796
>. OPC Status
OPC Name: OPCM002P

OPC Function: Primary
OPC Status: Active
Network Element: 641
Shelf: 1
SW Version: OPCAL06AJ
Backup OPC Status: Not Commissioned
4 After viewing the OPC status, return to the User Session Manager by
pressing Ctrl_ T 0.
The User Session Manager appears. The OPC Status tool remains at the top
of the Open tools list.
—end—

Procedure 7-14
Changing the name of an OPC
Use this procedure to change the name of an in-service OPC.
Requirements
Prior to carrying out this procedure, do the following:
• Obtain a userID and password for the SLAT security level of a network
element in the OPC span of control.
• Obtain a userID and password of the primary and the backup OPC at the
SLAT security level.
• Make the OPC, that you want to rename, the primary OPC for that span of
control.
• Log on to the network element at the slat security level. The default userID
is “SLAT” and the default password is “slat”.
• Log on to the primary OPC from the network element at the slat security
level. The default userID is “SLAT” and the default password is “slat.”
—continued—
Action
1 Open the Commissioning Manager tool.
The Commissioning Manager main window appears.
CS-10229
CS-10229
>. OPC Commissioning Manager (Version opc06ca_hp_65) Options
System: NE06 OPC Serial Number: A1d3e0138
=> 1. [ Clear commissioning data 1]

2. [ Edit system data 2]
3. [ Commission new network element 3]
Commissioned network elements:
NE Shelf Type Function FCOT Serial Number OPC
4. [ Transfer data to Primary OPC (from SLAT OPC) 4]

5. [ Transfer data to Backup OPC (from Primary OPC) 5]
2 Tab to the Edit system data button and select it by pressing Ctrl_A
(or Keypad 0).
The following dialog appears.
FW-20677
FW-20677
System Commissioning Data

Network number: 1
Network name:
System ID: 1
System name:
System type:
OPC name: > <
Primary OPC serial number: > OPC
Primary OPC alias: >
Backup OPC serial number:
Backup OPC alias:
[ OK Return] [ Cancel Del]
—continued—


Changing the name of an OPC
3 Tab to the OPC name field, and type in the name for the primary OPC. The
backup OPC will take this name also. OPC names must be unique within the
network, and have the following format:
OPC<nnnn>
Where... is...
<nnnn> any alphanumeric character (for example: OPC1D37)
4 Tab to the OK button and select it by pressing Ctrl_A (or Keypad 0).
5 Return to the User Session Manager on the OPC by entering Ctrl_T 0.
6 Copy the data from the primary OPC to the backup OPC (as described in the
procedure “Transferring data between OPCs” on page 8-24“.
7 Reboot the primary OPC (as described in the procedure “Shutting down an
OPC” on page 8-3“.
8 Log out of the primary OPC.
9 Log in to the backup OPC from the network element.
10 Reboot the backup OPC (as described in the procedure “Shutting down an
OPC” on page 8-3“.
All network elements in the OPC span of control are updated with the new
OPC name automatically. In the event of a network element rebooting, it will
be able to reach its newly named OPC and reload its software.
—end—

8-1
Other OPC procedures 8-

This chapter contains common OPC procedures. Use these procedures as
required during testing, or when reference is made to them in other procedures.
Chapter task list

The following table lists the tasks described in this chapter. If you cannot
successfully complete these procedures, contact your next level of support.
Procedure Task See
8-1 Shutting down an OPC page 8-3
8-2 Checking the OPC tape identification page 8-7
8-3 Saving OPC data to tape page 8-9
8-4 Restoring OPC data from tape page 8-15
8-5 Transferring data between OPCs page 8-24
8-6 Detecting and/or removing existing OPC software page 8-27
8-7 Installing software in a local OPC page 8-31
8-8 Restoring an NE database page 8-34
8-9 Setting the time zone, date, or time page 8-39
8-2 Other OPC procedures
Requirements
Before performing the procedures in this user guide, review the following
requirements.
• You must be familiar with the OPC user interface. Descriptions of the
character mode terminal (CMT) and graphical user interfaces are given in
Chapters 2 and 3 respectively.
• You must be logged into the terminal connected to the OPC.
• To shut down an OPC, you must have a userID and password of a user that
has permission to shut down the OPC. Only users in the root, slat, or admin
class can shut down the active OPC; users in the root or standby class for
the inactive OPC.
• Procedures for identifying tape data and saving or restoring data to tape,
require that the OPC tape be installed in the OPC tape drive. (Always allow
the tape to reach room temperature. Never insert a tape that has been stored
at temperatures outside the range 10°C to 30°C (50°F to 90°F) until it has
reached room temperature.)
Other requirements specific to a procedure are listed in the procedure itself.

Procedure 8-1
Shutting down an OPC
Use this procedure to shut down or reboot an OPC.
The procedure is the same for restarting or halting. If you restart the OPC, the
OPC will shutdown and immediately restart. If you want to remove all power
from the OPC so that it can be removed from the shelf, select the halt option.
Note: It is recommended that a maintenance restart is done every 8 to 12

weeks.
Action
1 Open the OPC Shutdown tool.
The OPC Shutdown tool main window appears.
CS-10222
CS-10222
>. OPC Shutdown
Press the shutdown button to

proceed, or close this tool
by selecting exit.
[ Shutdown ] [ Exit )]
2 Select the Shutdown button by pressing Ctrl_A (or Keypad 0).

A confirmation dialog appears, indicating the amount of time required for the
shutdown and giving you a final chance to abort the shutdown.
If you want to... then go to...
abort the OPC shutdown step 3.
proceed with the OPC shutdown step 5.
—continued—

3 Select the Cancel button by pressing Ctrl_A (or Keypad 0).

The OPC Shutdown tool main window appears.
4 Display the window menu by pressing Ctrl_L W (or Keypad 6) and select the
Exit command by pressing Space (or Keypad 0).
The OPC Shutdown tool closes.
5 Tab to the Proceed button and select it by pressing Ctrl_A (or Keypad 0).
This commits the tool to shut down the OPC.
The OPC shutdown process starts. A console message appears.
FW-20706
FW 20706
Information OPC System Shutting Down.
[ OK Return ]
6 Select the OK button by pressing Ctrl_A (or Keypad 0).

A shutdown progress dialog appears. As the shutdown progresses, the dots
on the dialog are replaced with Xs.
FW-21328
In progress...
Shutdown in progress:
XXX..
This progress dialog indicates that the OPC is shutting down normally. Since
the shutdown continues while the console message in step 5 appears, the
shutdown might complete before you select the OK button. In this case, you
will not see the progress message.
A dialog stating that the OPC is out of service appears (to all users who are
currently logged in to the OPC).
—continued—


7 Select the Done button by pressing Ctrl_A (or Keypad 0).

The following dialog appears.
FW-20709
FW-20709
Information If you are NOT going to remove or power down the OPC,
select the Restart option and then select OK to complete
the shutdown.
Otherwise, ensure that no tape is in the OPC drive and

then select OK to complete the shutdown.
If this is the primary or backup OPC, wait for the green

LED to be switched off, and then immediately pull it out
of the shelf.
If this is the portable OPC, wait for the green LED

labelled Active to be switched off, and then immediately
( ) Halt ( ) Restart
power down the OPC.
[ OK Return ]
8 Depending on the task you are performing, you might be required to remove
the OPC module from its shelf or to power down a portable OPC. In these
cases, you must take the required action before the OPC attempts to reboot.
If you will be... then go to...
removing or powering down the OPC step 11.
allowing the OPC to start up step 9.
9 Tab to the Restart button and select it by pressing Ctrl_A (or Keypad 0).
This action causes the OPC to reboot without delay after the shutdown
completes. If you select this option, you will not have time to physically
remove the OPC without damaging the OPC.
The shutdown procedure completes. The OPC then initiates a reboot (takes
about 5–10 minutes). When it is complete, the OPC login prompt (login:)
appears.
The shutdown of the OPC terminates all user login sessions. You have to log
in again after the OPC returns to service.
You must not remove or power down the OPC during the reboot process.
When the login: prompt appears, return to the main procedure.
The shutdown procedure continues. When it is complete, the green Activity
Indicator LED on the OPC turns off.
—continued—

CAUTION
Risk of data corruption
Do not remove or power down the OPC after the red LED has
turned on. If you do, you will corrupt the data on its hard drive. The
shut down process takes 5 to 10 minutes.
12 Immediately after the green LED turns off, remove the OPC or power down
the portable OPC.
To power down a portable OPC:
• Switch the power switch at the back of the portable OPC to the OFF
position when the shutdown dialog informs you to do so.
• Remove the CNET cable from both the network element and the portable
OPC.
If the OPC is still in place or if the portable OPC is powered up 3 minutes after
the LED turns off, a start up is initiated. If you have not removed or powered
down the OPC by this time, the red Unit Fail LED turns on and an alarm is
raised.
—end—

Procedure 8-2
Checking the OPC tape identification
Use this procedure to confirm that the correct tape has been inserted in the
OPC tape drive or to determine the data that is on a particular tape.
Action
1 Open the OPC Save and Restore tool.
The OPC Save and Restore main window appears. The Save to tape button
is selected and the buttons for saving OPC data to tape appear in the bottom
half of the window.
FW-20361A
FW-20361

—continued—

Checking the OPC tape identification
2 Select the Display tape details button by pressing Ctrl_A (or Keypad 0).
The Tape Details dialog appears. It shows information about the tape.
CS-10221A
CS-10221
Tape Details
Tape type: OPC and NE software delivery

Date created: Tue May 13 23:18:37 1996
Created on network: CSV01

Created on system: AccessNode
Created on OPC: OPCM002
From OPC load: OPCANCL13AX

From product: Cornerstone Voice
[ Done Return ]
3 Check the fields in the dialog to confirm that you have inserted the correct
tape into the tape drive.
If the tape has never been used, the “Tape type” will be “Unknown” and all
other fields will be blank.
You cannot change the information in this dialog. This information is written to
this dialog by the OPC when tape is used to record the backup data from the
OPC.
4 If the wrong tape has been inserted, insert the correct one.
5 To exit the Tape Details dialog, select the Done button by pressing Ctrl_A
(or Keypad 0).
The Tape Details dialog closes.
6 If you are finished with the tape, remove it and close the OPC Save and
Restore tool. Otherwise continue as follows:
overwrite the data on the tape Procedure 8-3 on page 8-9
restore data from the tape to an OPC Procedure 8-4 on page 8-15
—end—

Procedure 8-3
Saving OPC data to tape
Use this procedure to save OPC data to a backup tape in the OPC tape drive.
Once the save operation is started, you cannot access any other OPC tool until
the operation is canceled or completed. The save operation can take up to 40
minutes to complete depending on the amount of data on the disk.
CAUTION
Risk of damage to electrostatic-sensitive devices
Electrostatic-sensitive devices can be damaged by
electrostatic discharge. Always ground yourself before
handling the tape.
You cannot select individual files to be saved. The OPC Save and Restore tool
automatically selects and saves the appropriate files.
Note: When the tool is first opened, the “Save to tape” operation should be
selected by default, as shown in the illustration on the next page. If the
“Save to tape” button is disabled, the local OPC is inactive and you cannot
perform this procedure.
The tool contains two action buttons: Display tape details and Save OPC
data to tape. It is recommended that you select both buttons in the order that
they appear.
—continued—

Action
1 Open the OPC Save and Restore tool.
The OPC Save and Restore main window appears. The Save to tape button
is selected and the buttons for saving OPC data to tape appear in the bottom
half of the window.
FW-20361A
FW-20361

—continued—


2 Select the Display tape details button by pressing Ctrl_A (or Keypad 0).
The Tape Details dialog appears. It shows information about the tape.
CS-10221A
CS 10221
Tape Details
Tape type: OPC and NE software delivery

Date created: Tue May 13 23:18:37 1996


[ Done Return ]
3 Check the fields in the dialog to confirm that you have inserted the correct
tape into the tape drive. If this is not the correct tape, remove it and insert the
correct one. Press Ctrl_A (or Keypad 0) to exit the dialog, then return to
step 2.
4 When the correct tape has been inserted in the tape drive, select the Done
button by pressing Ctrl_A (or Keypad 0).
The Tape Details dialog closes and the arrow in the main window moves down
to the Save OPC data to tape button in the OPC Save and Restore tool main
window.
5 Select the Save OPC data to tape button by pressing Ctrl_A (or Keypad 0).
The Save confirmation dialog appears, prompting you to confirm your
request.
FW-21001A
FW-21001
Saving OPC data will cause the contents of the

tape in the tape drive to be overwritten and the
operation will take up to 40 minutes to complete
(depending on the amount of data on disk).
Do you want to proceed with saving OPC data?
[Yes Return ] [ No - ]
—continued—

6 Tab to the Yes button and select it by pressing Ctrl_A (or Keypad 0).
If the backup tape... then...
is blank step 8.
contains data that you are overwriting step 7.
7 A confirmation dialog appears.

If the tape contains a data archive, the following dialog prompts you to confirm
your request to overwrite the existing data on the tape.
CS-10225A
CS-10225
The tape contains a SAVE AND RESTORE ARCHIVE and

performing a save to tape will overwrite it.
The following are the tape details:
Date created: Tue May 13 1996
Select OK if you still want to proceed with the save.
[ OK Return ] [ Cancel Del ]
A progress dialog appears, indicating that the save operation has been
initiated.
continue with the save operation step 8.
cancel the save operation step 9.
—continued—


If the tape contains a software load, the following dialog prompts you to
confirm your request to overwrite the existing data on the tape.
FW 21004 FW-21004A
The tape contains OPC and NETWORK ELEMENT SOFTWARE

and performing a save to tape will overwrite it.
DO YOU WANT TO OVERWRITE THE SOFTWARE?
Select OK to proceed with the save.
Note: It is recommended that you not overwrite the contents of a tape which have
the OPC and Network Element Software. Find a clean blank tape and put it in the
tape drive after ejecting the Software tape.
A progress dialog appears, indicating the progress of the save operation.
FW-21002A
FW-21002
In progress... Preparing OPC data for a save to tape, you can

cancel the operation by selecting Cancel.
Please wait...
[ Cancel Del ]
continue with the save operation step 12.
cancel the save operation step 9.
—continued—

9 Tab to the Cancel button and select it by pressing Ctrl_A (or Keypad 0).
A confirmation dialog appears, prompting you to confirm your request to
cancel the save operation.
FW-21005A
FW-21005
You have requested to stop the Save to tape operation

however the operation will continue until you select OK.
Do you really want to stop it?
Select OK to terminate the Save operation.
The confirmation dialog closes and another progress dialog appears. This
indicates that the save operation is being canceled and the tape is being
erased.
When the save operation is canceled, a dialog appears stating so.
Go to step 14.
12 After the save operation is completed, a completion dialog appears.
FW-21007A
The save operation has been successfully

completed.
[ Done Return ]

14 Close the OPC Save and Restore tool.
—end—

Procedure 8-4
Restoring OPC data from tape
Use this procedure to retrieve data from a backup tape to the OPC disk. This
procedure overwrites all existing data on the OPC disk.
For example, if the network element configuration data on the tape is different
from that on the OPC disk, the old data will be transferred to the disk after the
tape data is restored to the disk.
CAUTION
Risk of damage to electrostatic-sensitive devices
Electrostatic-sensitive devices can be damaged by electrostatic
discharge. Always ground yourself before handling the tape.
This procedure contains two operations:

• an operation to display the tape name so that you know you are using the
correct tape
• a restore operation
The entire procedure can take more than 40 minutes to complete.
When the restore operation begins, you cannot cancel the operation or use any
other OPC tool until the operation is completed. During the restore operation,
the local OPC is taken out of service and all current OPC operations are
interrupted. At the end of the restore operation, a reboot occurs.
CAUTION
Risk of network outage
If the restore operation fails, check that the appropriate network
element loads remain on the OPC using the OPC Reboot/Load
Manager tool. If the network element loads have been corrupted,
you must attempt to restore the loads as quickly as possible or
transfer the standby OPC to duty. If you leave the loads off the
duty OPC, and a network element requires a reboot, no load will
be available and you risk causing a network outage.
—continued—

This procedure overwrites existing data on the local OPC. Overwriting the
existing data affects any OPC tools that use this data. For example, restoring
OPC data on the local OPC can cause inaccurate download statistics in the
Reboot/Load Manager tool.
When the OPC Save and Restore tool is first opened, the main window appears
in default save mode. This procedure shows you how to toggle from this main
window so that it appears in restore mode. The main window displays the
buttons for selecting restore OPC data. These restore buttons are displayed at
the bottom of the main window. You need to select these restore buttons in the
order they are shown.
Note: Be aware that inconsistencies between the OPC and NE database can
be introduced after performing the restore operation. There can be a
mismatch between the NE and the OPC since the data from the OPC
database is based on the last save operation.
Requirements
To perform this procedure, you must meet the following requirements:
• allow the tape to reach room temperature. Never insert a tape that has been
stored at temperatures outside the range 10°C to 30°C (50°F to 90°F) until
it has reached room temperature.
• insert the backup tape in the local OPC tape drive
• have a userID and password that permit access to the OPC
Note: Read the command conventions in Chapter 2 and Chapter 3 for the
interface (CMT or graphical) you are using.
—continued—


Action
1 Log in to the OPC and open the OPC Save and Restore tool.
If you do not know how to do this, see Chapter 7.
The OPC Save and Restore main window appears in save mode. The Save
to tape button is selected and the buttons for saving OPC data to tape appear
in the bottom half of the window.
FW-20361A
FW-20361

2 Tab to the Save to tape button at the top of the main window. Do not select it.
—continued—

3 Using the down arrow key, move to the Restore from tape button and select
it by pressing Ctrl_A (or Keypad 0).
The buttons for restoring OPC data from tape appear in the main window. An
arrow appears to the left of the first button.
FW-22303

Restoring OPC data from tape:
2. [ Restore OPC data from tape 2]
—continued—


4 To confirm that the correct tape is inserted in the tape drive, select the
Display tape details button by pressing Ctrl_A (or Keypad 0).
After an In progress message appears, the Tape Details dialog appears,
displaying information about the tape. If you do not have a tape inserted, the
Tape type field shows “unknown.”
FW-22304
FW-22304
Tape Details
Tape type: OPC data archive

Date created: Tue Jul 16 08:39:31 1996
Created on network: AN12

Created on system: AN12
Created on OPC: OPCM047P
From OPC load: ACNL12CD

From product: S/DMS AccessNode ABM
[ Done Return ]
5 Check the fields in the Tape Details dialog to confirm that you have inserted
the correct tape into the tape drive.
6 To remove the Tape Details dialog, select the Done button by pressing Ctrl_A
(or Keypad 0).
The Tape Details dialog closes. In the main window, the arrow moves down
to the Restore OPC data from tape button.
—continued—

7 In the main window, select the Restore OPC data from tape button by
pressing Ctrl_A (or Keypad 0).
A confirmation dialog appears, prompting you to confirm your request.
FW-21008A
FW-21008
Restoring OPC data will cause any existing data

on this OPC to be replaced. This OPC will go out of
service while the data is being restored and the
operation will take up to 40 minutes to complete
(depending on the amount of data on tape).
Do you want to proceed with restoring OPC data?
[ Yes Return ] [ No -]
The confirmation dialog closes. Several In progress messages appear in
succession showing the progress of the tape extraction. During this period the
local OPC becomes inactive. A dialog appears, indicating that the OPC is out
of service.
FW-20707
FW-20707
This OPC is out of service.
[ Done Return]
—continued—


9 To remove the information dialog, select the Done button by pressing Ctrl_A
(or Keypad 0).
The out-of-service dialog closes. A dialog appears, indicating the progress of
the restore operation. The restore operation can take up to 40 minutes to
complete. When the OPC becomes active again, the following information
dialog appears for each user session.
FW-21009A
FW-21009
This OPC has just entered the active state.

Normal operations will be resumed.
[ Done Return ]
10 To remove the information dialog, select the Done button by pressing Ctrl_A
(or Keypad 0).
The information dialog closes. A completion dialog appears, indicating that
the restore operation is complete.
FW-22306
FW-22306
The restore operation has been successfully

completed.
System needs to shutdown to reset its internal

variables.
Press the Done button to start the OPC Shutdown

tool.
[ Done Return ]
—continued—

11 To remove the completion dialog, select the Done button by pressing Ctrl_A
(or Keypad 0).
The completion dialog closes. An In progress message appears indicating
the OPC Shutdown tool is being opened. The OPC Shutdown tool appears.
FW-22307
FW-22307
>• OPC Shutdown
Press the shutdown button to

proceed, or close this tool
by selecting exit.
[ Shutdown ] [ Exit ]
? C0 M0 m1 w2 FailProt 0 Lckt 0 ActProt 0 PrfAlrt 0 11:38
12 Select the Shutdown button by pressing Ctrl_A (or Keypad 0).

A warning dialog appears.
FW-22308
FW-22308
Warning A shutdown at this time will take approximately

5 minutes. Once initiated, the shutdown cannot be
terminated. It will close all windows and
terminate all actively running processes.
Port B will be configured as indicated on
reboot.
Confirm port B configuration, then select

Proceed or Cancel.
[*] Confirm shutdown. Port B is currently configured

as a terminal.
[Proceed ] [ Cancel Del ]
—continued—


13 Tab to the Proceed button and select it by pressing Ctrl_A (or Keypad 0).
An information dialog appears.
FW-22309
FW-22309
Information If you are NOT going to remove or power down

the OPC, select the Restart option and then
select OK to complete the shutdown.
Otherwise, ensure that no tape is in the OPC

drive and then select OK to complete the
shutdown.
If this is the primary or backup OPC, wait

for the green LED to be switched off, and then
immediately pull it out of the shelf.
If this is the portable OPC, wait for the green

LED labelled Active to be switched off, and
then immediately power down the OPC.
( ) Halt ( ) Restart
[ OK Return ]
14 Tab to the Restart button and select it by pressing Ctrl_A (or Keypad 0).
An Information dialog appears indicating the OPC System is shutting down.
An In progress message appears followed by the Out of service dialog.
FW-20707
FW-20707
This OPC is out of service.
[ Done Return]

The dialog closes. A reboot occurs.
If after performing this procedure, there are NEs that need to be recovered or
if the alarm “Database not restored. Type Q approve at NE.” has to be cleared,
then use the information in Chapter 12 of the Maintenance Guide,
ARSVD00404, to clear the alarm.
—end—
Procedure 8-5
Transferring data between OPCs
Use this procedure any time to transfer OPC data from the disk of one OPC in
a span of control to any other OPC in the same span of control. You can transfer
data between backup, primary, and portable OPCs, as long as you are
transferring the data from an active OPC.
This procedure can take up to 30 minutes to complete.
Note: It is recommended that you transfer OPC data to the backup OPC
after you have restored data from a backup tape. This procedure is included
as part of Procedure 8-4, “Restoring OPC data from tape.”
Action
1 Open the OPC Save and Restore tool on the OPC that contains the network
data that you want to save.
The OPC Save and Restore main window appears in save mode. The Save
to tape button is selected and the buttons for saving OPC data to tape appear
in the bottom half of the window.
FW-20361A
FW-20361

2 Tab to the Save to tape button. Do not select it.

—continued—


3 Move to the Restore from tape button and select it by pressing Ctrl_A
(or Keypad 0).
The buttons for restoring OPC data from tape are displayed.
FW-20374A
FW-20374

Restoring OPC data from tape:
2. [ Restore OPC data from tape 2]
3. [ Transfer data to Backup OPC 3]
4 Tab to the Transfer data to Backup OPC button and select it by pressing
If you are transferring data from the backup or portable OPC to the primary
OPC, this button reads Transfer data to Primary OPC.
A confirmation dialog appears, prompting you to confirm your request.
FW-21123
3
Transferring data to the OPC001PB OPC will cause

any existing data on the OPC001PB OPC to be
overwritten and the operation will take between
4 and 30 minutes to complete.
Do you want to proceed with the data transfer?
[Yes Return ] [ No - ]
—continued—

The confirmation dialog closes and a progress dialog appears, indicating that
the data on the OPC disk is being copied to the other OPC. (This operation
can take up to 30 minutes to complete.) When the transfer is complete, the
following completion dialog appears.
FW-21124
FW-21124
The Transfer OPC data operation has been

successfully completed.
[ Done Return ]

The dialog closes.
7 Close the OPC Save and Restore tool.
—end—

Procedure 8-6
Detecting and/or removing existing OPC software
Use this procedure to detect if an OPC software load exists on an OPC. Do not
use this procedure as part of the process for upgrading the software in an
in-service OPC. This procedure applies to any new or spare OPC that is
currently not in use, including modular (shelf-mountable) primary and backup
OPCs, and the portable OPC (also referred to as the SLAT OPC).
If software exists, but it is not the desired load, then you can use this procedure
to remove the existing OPC software. Note that the OPC database, which
contains all of the commissioning data, is not preserved by this operation, so
this procedure should only be performed on a spare or stored OPC that requires
an “initial” software load.
Requirements
A VT100-compatible terminal must be connected to OPC port 1 (or port B).
You also need the root password and tape(s) containing the OPC and NE
software loads.
You need a tape or tapes containing the desired OPC software load and
network element software loads.
CAUTION
Enter UNIX commands carefully
If you enter a UNIX command incorrectly, it may be difficult to
recover from the error. Be sure to read this procedure carefully
to distinguish between similar symbols such as !, |, and /, or -
and =. Commands shown in lower case must be entered in lower
case. Contact your next level of support if required.
Action
1 Log in to the OPC using the root userID.
The “Term=(VT100)” prompt appears.
2 Press Return (↵).
The “opc>” prompt appears.
—continued—

3 Check whether the OPC has a software load on it. Enter:

opcui ↵
• If the response yields a message indicating that the command was not
found, then no OPC software is loaded, in which case you are finished
with this procedure. You are now ready to install software on the OPC. If
necessary, refer to the procedure “Installing software in a local OPC” on
page 8-31.
• If the User Session Manager appears, then OPC software is loaded.
Continue at step 4.
4 Check to make sure that the OPC contains the desired software load. Do this
by selecting the OPC Status tool and examining the contents of the SW
Version field (it identifies the software version currently running in this OPC).
5 Log out of the OPC Status tool and display the User Session Manager by
pressing Ctrl_T 0.
6 Tab to the Logout button and select it by pressing Ctrl_A (or Keypad 0).
A confirmation dialog appears.
7 Tab to the Logout button and select it by pressing Ctrl_A (or Keypad 0).
The User Session Manager closes, and the “opc>” prompt appears.
Note: It is essential to completely log out from the OPC user interface. Do not
simply select a UNIX shell within the User Session Manager.
8 If the OPC:
• contains the desired software, then you are finished with this procedure.
• does not contain the desired software, continue at step 9.
9 Carefully insert the tape that contains the desired OPC software load, into the
OPC tape drive.
—continued—


CAUTION
If you force the tape into the tape drive, you may damage the
drive, and you may not be able to remove the tape. If you
cannot insert the tape easily, it may be oriented the wrong way
(see the figure on page 8-30).
10 Load the “remove OPC load” file, RMOPCLD, from the tape and execute the
removal by entering the following, since these are Unix commands they must
be entered exactly as written (in lower case):
cd /tmp ↵
dd if=/dev/rdt/tape2 bs=20b | tar xvf - ↵
cd install ↵
rmopcld ↵
A message informing you that you are about to wipe out the OPC load
appears and prompts you for a confirmation.
y↵
A message asking you to continue or abort the removal process appears.
c↵
The script removes the existing software load. The OPC reboots.
—continued—

11 Remove the tape from the OPC tape drive, using the tape eject button shown
in Figure 8-1.
Figure 8-1
Tape eject button
FW-10864
FW-10864
Operations
controller
(OPC)
Tape eject
button
il
N Fa
il
E LA Fa
et
CN e
tiv
Ac
il
Fa
Slide
white tab
open to
protect
data
—end—

Procedure 8-7
Installing software in a local OPC
Use this procedure to perform the initial transfer of OPC software and NE
software from tape to the local operations controller (OPC), prior to
commissioning a system and its network elements (NEs).
Do not use this procedure as part of the process for upgrading the software in
an in-service OPC. This procedure applies to a new or spare OPC that is
currently not in use, including modular (shelf-mountable) primary and backup
OPCs, and the portable (SLAT) OPC.
Requirements
A VT100-compatible terminal must be connected to OPC port 1 (or port B).
You also need the root password and tape(s) containing the OPC and NE
software loads.
Identify, and if necessary, remove existing OPC software. Refer to

Procedure 8-6, “Detecting and/or removing existing OPC software,” for
details.
Action
1 Log in to the OPC using the root userID.
The “Term=(VT100)” prompt appears.
The “opc>” prompt appears.
3 Carefully insert the tape that contains the desired OPC software load, into the
OPC tape drive, as shown in the figure on page 8-30.
—continued—

4 Note the following cautions:

CAUTION
If you force the tape into the tape drive, you may
damage the drive, and you may not be able to remove
the tape. If you cannot insert the tape easily, it may be
oriented the wrong way (see page 8-30).
CAUTION
Enter UNIX commands carefully
If you enter a UNIX command incorrectly, it may be
difficult to recover from the error. Be sure to read this
procedure carefully to distinguish between similar
symbols. Commands shown in lower case must be
entered in lower case.
5 To install the OPC software, enter the following, since these are Unix
commands they must be entered exactly as written (in lower case)::
cd /tmp ↵
dd if=/dev/rdt/tape2 bs=20b | tar xvf - ↵
cd install ↵
localOPCinstall ↵
A dialog appears prompting you to select the type of software you are
installing.
6 Select Cornerstone software by entering:
access ↵
A dialog appears asking you to proceed with or abort the “upgrade”. Although
you are not performing an upgrade, a confirmation is required to continue with
the installation process.
7 To confirm, enter:
y↵
The OPC software is installed and then the OPC reboots. When the OPC
becomes operational, the login prompt appears.
—continued—


8 Log in to the OPC as in step 1 and use the NE Software Delivery Manager to
load the NE software from tape into the OPC.
Note 1: The destination OPC is the actual local OPC. Transfer all Proc, HMU,
TAC, and LC loads.
Note 2: After you install the software, you may receive a message stating that
the software has been successfully transferred but not installed. If this
message appears, it does not mean that the installation was unsuccessful.
Software will be installed automatically as soon as the OPC is commissioned.
Therefore, continue with the next step.
9 Now that both the OPC and NE software has been installed, remove the tape
from the OPC tape drive. Refer to the figure on page 8-30 for the location of
the tape eject button.
—end—
Procedure 8-8
Restoring an NE database
Use this procedure to replace an active database on the HDT with a new
database. The new database may be on tape or already on the OPC hard drive.
Requirements
The following are necessary for performing this procedure:
• root access to the OPC

• the replacement database (which may be on tape, the OPC, or another OPC
accessible over the LAN)
Action
Perform the tasks in this procedure in the following order:
Task Page
Disabling automatic database backup 8-35
Copying the database 8-36
Restarting automatic database backup 8-37
Loading the new databases 8-38
—continued—


Disabling automatic database backup

1 Log into the OPC as root.
2 At the opc> prompt, type the following command:
opc> drmstat ↵
The drmstat screen appears.
3 Use the arrow keys to move down to option 7 (Backup/Restore Manager) and
press b.
This disables automatic database backup.
4 Press q to quit the drmstat tool.
—continued—

Copying the database

Note: This task is optional. You can use it to ensure that copies of the
databases exist in case of corruption.
If the database is… Then
on tape Use the OPC Save and Restore tool to load the
database (see “Restoring OPC data from tape” on
page 8-15 for details). Do not restart the OPC when
prompted.
Note: The restore operation automatically places the
database in the /users/VFS/nedsb directory.
on the OPC hard Use the following command to copy the database:
drive cp /path/to/database /users/VFS/nedsb ↵
on another OPC Use the ftp command to transfer the database to
/users/VFS/nedsb on the local OPC.
Note: Make sure you specify a binary transfer.
2 Use the following commands to make a backup copy of the databases:

opc> cd /tmp ↵
opc> mkdir bkdb ↵
opc> cp users/VFS/nedsb/<dbname> /tmp/bkdb ↵
where
<dbname> is the name of the database(s) you want to copy
(e.g. N1.S1.EQ205.E1.REL1904*). The asterisk is a
wildcard character; see “Using UNIX” on page 2-29
for other information.
The OPC copies the specified files to the temp directory.

3 Make sure you have copied the right databases using the following command:
opc> ll temp ↵
The OPC displays the database files in the temp directory.
—continued—


Restarting automatic database backup

1 At the opc> prompt, type the following command:
opc> drmstat ↵
The drmstat screen appears.
2 Use the arrow keys to move down to option 7 (Backup/Restore Manager) and
press r.
This restarts automatic database backup.
3 Press q to quit the drmstat tool.
—continued—

Loading the new databases

1 Log into the NE.
You can do this by using the OPC UI or the command nelogin <ne>, where
<ne> is the number of the NE.
The MAPCI screen appears.
2 Type the following commands to load the new database:
eq proc a ↵
datasync ↵
switch ↵
y↵
The NE logs out all users and begins loading the new database. The loading
process takes about 3 minutes.
3 Log back into the NE and type the following commands to re-enable data
synchronization:
eq proc a ↵
datasync ↵
The Proc equipment screen indicates data synchronization is on, and the
datasync state changes to synced after the database is loaded and
synchronized on both processors.
4 Type the following commands to determine whether provisioned Voice Ports
and lines have recovered:
fwp ↵
eq vplc <vpid> ↵
where
<vpid> is the VPID or alias of a Voice Port with at least one

provisioned line.
The Voice Port lines should be In Service.

5 Use the Alarm Monitor to check alarm status on the NE.
6 Type the following commands to make sure the number of provisioned lines
on the NE is correct:
quit all ↵
cornerstone ↵
cvprov ↵
querycapacity all ↵
—end—

Procedure 8-9
Setting the time zone, date, or time
Use the following procedure to change the time zone, date, or time for an
operational OPC. The time zone codes are listed in the date tool, and the
appropriate code is selected using this procedure. See Table 8-1 on page 8-46
at the end of this procedure for a list of valid time zones.
The OPC keeps track of local and Greenwich mean time, and provides a
system time-of-day clock for the NEs it controls. NEs synchronize their clocks
with the OPC every two hours.
Note: The OPC date must not be set backwards or the OPC must be
reloaded.
The local time and date must be set during initial commissioning and whenever
the OPC’s clock battery has discharged. It should not be necessary to set the
clock again unless the OPC is moved to a new time zone or replaced. Changing
the time or date of an operational OPC involves shutting it down.
Battery drain occurs only when the OPC is powered down. It takes at least two
weeks to discharge the battery from a fully-charged state.
CAUTION
Changing the OPC time can disguise the real time order of
event logs and alarms
Many activities in the OPC, such as the generation of event
logs, are time-stamped by the system. When you change the
time, a gap or an overlap in time is introduced to time-stamped
activities. It may be confusing to surveillance personnel to find
that logs arriving in sequence have unusually-spaced time
stamps.
If you set the system time to a future value and then restore it to
actual time, a log generated while the system was in future time
will appear at the top of the list (in the Event Browser tool) and
remain there. Any subsequent log generated in actual time will
not displace the earlier log until actual time catches up.
Be sure that the time you specify is correct, since the time
stamps created for events are not automatically adjusted when
the system time is changed; and they cannot be changed
manually.
Caution other administrative personnel about the

consequences of the changes you make.
—continued—

Requirements
You need to know the local time, date, and the time zone code for your time
zone.
Action
1 Open the OPC Date tool.
The OPC Date tool is opened and the main window appears.
FW-21186
FW-21186
>. OPC Date Options
The OPC data (DD/MM/YYYY) is 01/05/1995.

The OPC timezone is EST5EDT#Canada.
Select the Adjust Time button to change the current

time within 30 minutes of its current value.
Select the Reset Time button to change the current time

by more than 30 minutes, or to change the time zone. An
OPC shutdown is required to reset the time. You will
be prompted to enter new date, time, and time zone at
the end of OPC shutdown.
[ Adjust Time ] [ Reset Time ]
? C0 M0 m0 w0 FailProt 0 Lckt 0 ActProt 0 PrfAlrt 0 07:37
If you want to change the time by… Then go to…
30 minutes or less step 3
more than 30 minutes step 7
—continued—


3 Select the Adjust Time button by pressing Ctrl_A (or Keypad 0).
The time and date change dialog appears.
FW-21189
FW-21189
Specify new time, within 30 minutes of current new time, then

select the Update button. The time will adjust at the rate of
about 30 minutes per 12 hours.
Date (DD/MM/YYYY) : > 01/04/1999
Time (HH:MM) : > 13:17
Time Zone : EST5EDT#Canada
[ Update ] [ Cancel Del ]
4 Enter a new value in the Date field in the form dd/mm/yyyy.

Where... is the...
dd day of the month (range 01 to 28, 29, 30 or 31 depending

on the month).
mm month (range 01 to 12).
yyyy year (range 1976 to 2035).
The new date appears in the Date entry field.

Note 1: Ensure that any old date is removed, by using the right arrow key to
position the cursor after the old text and pressing the backspace key.
Note 2: When using the Adjust Time capability, you may only change the
date to the immediately preceding or following day, and only if the current
time is in 30 minutes of that day. Modifications to the date field at this point is
required to support a 30 minute time advance near the end of the day.
5 Enter a new value in the Time field in the form hh:mm.
Where... is the...
hh hour (range 00 to 23).
mm minute (range 00 to 59).
The new time appears in the Time entry field.

Note: It is recommend that the current time of the active OPC clock be used
as the source of the correct time when setting the inactive OPC clock.
—continued—

6 Tab to the Update button; select it by pressing Ctrl_A (or Keypad 0).
The data you entered is validated. If incorrect, an error dialog appears, which
tells you what to do. If correct, the time and date dialog closes, returning you
to the main window. The clock rate is slightly modified to begin a gradual
adjustment.
If you select the Cancel button, the changes you have made will be ignored.
If you selected Update, proceed to step 15.
7 Tab to the Reset Time button; select it by pressing Ctrl_A (or Keypad 0).
A confirmation dialog appears, indicating the amount of time required for the
shutdown and allowing you a final chance to abort the shutdown.
FW-21190
FW-21190
Warning A shutdown at this time will take approximately 5

minutes. Once initiated, the shutdown cannot be
terminated. It will close all windows and
terminate all actively running processes.
Select Proceed or Cancel.

[ Proceed ] [ Cancel Del ]
8 Tab to the Proceed button; select it by pressing Ctrl_A (or Keypad 0).
The confirmation dialog closes and the OPC shutdown process starts. A
console message appears.
Note: The selection of the Proceed button commits the shutdown of the
OPC, even if you decide later to abort the changes to the time and date. To
abort the OPC shutdown procedure, select the Cancel button.
FW-20706
FW-20706
Information OPC System Shutting Down.
[ OK Return ]
—continued—



A shutdown progress message appears. As the shutdown progresses, the
dots on the dialog are replaced with Xs.
The progress message indicates that the OPC is shutting down normally.
Since the shutdown continues while the previous console message appears,
the shutdown may complete before you select the OK button in this step. In
this case, you will not see the progress message.
FW-21328
FW-21328
In progress...
Shutdown in progress:
XXX..
A dialog stating that the OPC is out of service appears to all users who are
currently logged in to the OPC.
The dialog is replaced by the Time and Date Change dialog.
FW-20708
FW-20708
Specify new time, date or time zone, then select the Update button.
Date (DD/MM/YYYY): > 26/02/1993
Time (HH:MM): > 18:18
Time Zone: > EST5EDT#Canada
Time Zone Name

EST5EDT Eastern Standard Time, Eastern Daylight Time
AST4ADT Atlantic Standard Time, Atlantic Daylight Time
NST3:30NDT Newfoundland Standard Time, Newfoundland Daylight Time
WET0WETDST Western European Time, Western European Daylight Time
PWT0PST Portuguese Winter Time, PortuGuese Summer Time
MET-1METDSY Middle European Time, Middle European Daylight Time
[ Update ] [ Cancel Del ]
—continued—

11 Enter a new value in the Date field in the form dd/mm/yyyy.

Where... is the...
dd day of the month (range 01 to 28, 29, 30 or 31 depending
on the month).
mm month (range 01 to 12).
yyyy year (range 1976 to 2035).
The new date appears in the Date entry field.

Note: Ensure that any old data is removed by using the right arrow key to
position the cursor ahead of any old text and by pressing the backspace key.
12 Enter a new value in the Time field in the form hh:mm.
Where... is the...
hh hour (range 00 to 23).
mm minute (range 00 to 59).
The new time appears in the Time entry field.

Note: It is recommended that the current time on the active OPC clock be
used when setting the inactive OPC clock.
13 To change the time zone, tab to the Time Zone list, and select a new time
zone.
The selected entry will be placed in the Time Zone field.
Note: A table of valid time zone codes is located at the end of this procedure.
—continued—


14 Tab to the Update button; select it by pressing Ctrl_A (or Keypad 0).
A confirmation message appears. If you made a mistake, a message appears
to tell you that selecting the new time and date requires a second OPC
shutdown to correct.
FW-21188
FW-21188
Warning
Please ensure that the new date entered is
correct, as you will have to reboot the
OPC to correct any errors.
Note: If you select the Cancel button, the changes you have made will be
ignored and you are returned to the time and date change dialog. The OPC
will continue to shut down.
15 Tab to the OK button; select it by pressing Ctrl_A (or Keypad 0).
The data you entered is validated. If incorrect, an error dialog appears, which
tells you what to do. If correct, the time and date information is saved, and the
OPC begins its reboot sequence. You may see the Session Manager screen
briefly.
The reboot process takes about 5 to 10 minutes. When it completes, the OPC
login prompt (login:) appears.
The shutdown of the OPC terminates all user login sessions, and you will
have to log in again, after the OPC returns to service.
—continued—
Table 8-1
Time zone codes and GMT offsets
Time zone Country: region Time zone code

(GMT offset in minutes)
Hawaiian Std Time United States: Hawaii HST10 (-600)

Hawaiian Daylight Time (-540)*
Aleutian Std Time United States: Alaska (parts) AST10ADT (-600)

Aleutian Daylight Time (-540)*
Yukon Std Time United States: Alaska (parts) YST9YDT (-540)

Yukon Daylight Time (-480)*
Pacific Std Time Canada: British Columbia PST8PDT#Canada (-480)

Pacific Daylight Time (-420)*
Pacific Std Time United States: California, Idaho PST8PDT (-480)

Pacific Daylight Time (parts), Nevada, Oregon (parts), (-420)*
Washington
Mountain Std Time Canada: Alberta, Saskatchewan MST7MDT#Canada (-480)

Mountain Daylight Time (parts) (-360)*
Mountain Std Time United States: Colorado, Idaho MST7MDT (-480)

Mountain Daylight Time (parts), Kansas (parts), Montana, (-360)*
Nebraska (parts), New Mexico,
North Dakota (parts), Oregon
(parts), South Dakota (parts),
Texas (parts), Utah, Wyoming
Mountain Std Time United States: Arizona MST7 (-420)

Mountain Daylight Time (-360)*
Central Std Time Canada: Manitoba, Ontario (parts), CST6CDT#Canada (-360)

Central Daylight Time Saskatchewan (parts) (-300)*
Central Std Time United States: Alabama, Arkansas, CST6CDT (-360)

Central Daylight Time Florida (parts), Illinois, Iowa, (-300)*
Kansas, Kentucky (parts),
Lousiana, Michigan (parts),
Minnesota, Mississippi, Missouri,
Nebraska, North Dakota,
Oklahoma, South Dakota,
Tennessee (parts), Texas,
Wisconsin
Central Std Time United States: Indiana (most) EST5CDT (-300)

Central Daylight Time (-240)*
Eastern Std Time Canada: Ontario (parts), Quebec EST5EDT#Canada (-300)

Eastern Daylight Time (parts) (-240)*
—continued—

Table 8-1
Time zone codes and GMT offsets (continued)

Eastern Std Time United States: Connecticut, EST5EDT (-300)

Eastern Daylight Time Delaware, District of Columbia, (-240*)
Florida, Georgia, Kentucky, Maine,
Maryland, Massachusetts,
Michigan, New Hampshire, New
Jersey, New York, North Carolina,
Ohio, Pennsylvania, Rhode Island,
South Carolina, Tennessee (parts),
Vermont, Virginia, West Virginia
Atlantic Std Time Canada: Newfoundland (parts), AST4ADT (-240)

Atlantic Daylight Time Nova Scotia, Prince Edward Island, (-180)*
Quebec (parts)
Newfoundland Std Time Canada: Newfoundland (parts) NST3:30NDT (-210)

Newfoundland Daylight Time (-150)*
Western European Time Great Britain, Ireland WET0WETDST (0)

Western European Daylight (60)*
Savings Time
Portuguese Winter Time Portugal PWT0PST (0)

Portuguese Summer Time (60)*
Middle European Time Austria, Belgium, MET-1METDST (60)

Middle European Daylight Savings Bosnia-Hercegovina, Denmark, (120)*
Time Croatia, Czech Republic, France,
Germany, Hungary, Italy,
Luxembourg, Poland, Slovakia,
Slovenia, Spain, Sweden,
Switzerland, Yugoslavia
South Africa Std Time South Africa SAST-2SADT (120)
South Africa Daylight Time (180)*
Japan Std Time Japan JST-9 (540)
Australian Western Std Time Australia: Western Australia WST-8:00 (480)
Australian Central Std Time Australia: Northern Territory CST-9:30 (570)
Australian Eastern Std Time Australia: Queensland EST-10 (600)
Australian Central Std Time Australia: South Australia CST-9:30CDT (570)

Australian Central Daylight Time (630)*
—continued—
Table 8-1
Time zone codes and GMT offsets (continued)

Australian Eastern Std Time Australia: New South Wales, EDT-10EDT(600)

Australian Eastern Daylight Time Victoria (660)*
Note: Offsets marked with an asterisk denote the NE offset that should be used when the Daylight
Saving Time is observed in the corresponding region.
—end—

9-1
Using the CI tool user interface 9-

This chapter describes the procedures for the command interpreter (CI) user
interface.
This chapter contains procedures for opening and closing command interpreter
(CI) tools, as well as a procedure on how to get help within a CI tool.
Refer to Chapter 4 for a description of the CI commands available for a

Cornerstone system.
How to use this chapter

Look up the procedure you need in the following table, then refer to the page
indicated.
of support.
Procedure Task Refer to
9-1 Opening a CI tool page 9-2
9-2 Displaying the help screen for a CI tool page 9-4
9-3 Entering a CI command page 9-5
9-4 Closing the CI tool page 9-6
9-2 Using the CI tool user interface
Procedure 9-1
Opening a CI tool
Use this procedure to open a CI tool.
Figure 9-1
Commands required to navigate through different levels of software
FW-2529
CI software FW-10175
quit mapci
command command
quit all fwp

command MAPCI software command
quit fwpui
command command
NE User Interface software
Action
1 Log in to the OPC.
2 Open the NE Login Manager tool.
The NE Login Manager screen appears.
The Network Element User Interface (NEUI) screen appears.
4 At the prompt, enter the following:
quit all ↵
If you want to use... then...
a Cornerstone CI tool go to step 5.
a CI tool other than Cornerstone enter CI commands for that tool.
—continued—


Opening a CI tool
5 At the CI prompt, enter the following:

cornerstone ↵
The CORNERSTONE CI prompt appears.
6 Open the CI tool by entering the name of the CI tool. For example, if you want
to perform spectrum maintenance, enter:
cvspmn ↵
The CI tool cvspmn loads. You are now ready to enter CI commands.
—end—
Procedure 9-2
Displaying the help screen for a CI tool
Use this procedure to display the help screen for a CI tool.
Action
1 Open the CI tool.
If you want to display... then go to...
the main help window step 2.
a list of all Cornerstone CI commands step 3.
Cornerstone help on a requested level step 4.
2 Display the main help window by entering:

help ↵
Note: For Cornerstone you can also use the command cvhelp.
The help screen appears.
3 Display a list of all Cornerstone CI commands by entering:
help commands ↵
A list of all Cornerstone commands appears.
4 Display Cornerstone help on a requested level by entering:
help <level>↵
Where... is the...
<level> Cornerstone CI tool: cvpath, cvprov, cveqpt, cvloader,

cvspmn, cvalrm, vlcmci.
A list of commands for the level appears.

—end—

Procedure 9-3
Entering a CI command
Use this procedure to enter a CI command.
Action
1 Type the name of the command, i.e. queryvp vp <vp id#>, and press the
Return key (↵).
The CI displays any parameter that you need to enter before it can perform
the command.
2 Once you have entered the necessary parameters, the CI displays the
system responses.
—end—
Procedure 9-4
Closing the CI tool
Use this procedure to close the CI tool. See Figure 9-1 on page 9-2 for an
illustration of the commands required to navigate through the different levels
of software.
Action
If you are closing... then go to...
a Cornerstone CI tool step 2.
a CI tool other than Cornerstone step 3.
2 Close the Cornerstone CI tool by entering:

quit ↵
The CI tool closes and the CI prompt appears.
Note: If you have more than one Cornerstone CI tool open, enter the
command quit until you are back at the CI prompt.
3 Return to the NEUI by entering:
fwp ↵
4 Log out of the NEUI by entering:
logout ↵
The tool closes and returns you to the NE Login Manager screen.
5 Close the NE Login Manager tool.
6 Log out of the OPC.
—end—

10-1
OPC Ethernet port configuration and

connections 10-
This chapter provides the information required to establish communications
between the OPC and an X terminal, an Ethernet LAN, or the Northern
Telecom Network Manager. This chapter describes the hardware specifications
and software setup requirements for X terminals supported by the OPC.
Procedures for connecting X terminals to the OPC and for configuring the
OPC for X terminal communications are included, following the chapter task
list starting on this page.
X terminals are graphical terminals that have a local memory, a processor, and
software to support the X Windows System. X terminals handle the graphical
display functions locally, for applications running within the OPC. The OPC
also has X Windows software which allows the OPC to control X terminal
displays and run X clients.
The X Display Manager (XDM) on the OPC generates a login banner which
appears on the X terminal displays. The user provides login information
through this login banner and the XDM starts the session if the login
information is correct. The XDM also handles session termination.
10-2 OPC Ethernet port configuration and connections
How to Use this Chapter

The following tasks are included in this chapter to support Network Manager
and X terminal connections to the OPC Ethernet port.
of support.
Procedure Tasks Refer to
10-1 Initializing the OPC Ethernet port page 10-16
10-2 Enabling and disabling the OPC Ethernet port page 10-20
10-3 Connecting the OPC to network equipment page 10-23
10-4 Establishing a telnet session between an X terminal and page 10-24

the OPC
10-5 Adding, changing, or deleting an NCD19 configuration page 10-25

file
10-6 Loading the NCD19 configuration data from the OPC to page 10-29
an NCD19 X terminal running NCDware v.2
10-7 Loading the NCD19 configuration data from the OPC to page 10-31
an NCD19 X terminal running NCDware v.3
10-8 Reconfiguring X terminals following an OPC upgrade page 10-32
Requirements
To perform the procedures in this chapter you must do the following:
• obtain the necessary tools for installation
• obtain the appropriate connection cable (see “Cabling options” on
page 10-9)
• obtain the root password that enables access to the OPC Ethernet port
• familiarize yourself with the OPC graphical user interface (Chapter 3)
Other requirements unique to a procedure are listed in the procedure itself.

X terminal support
The X terminals specifically supported by the OPC include the following:
• models NCD19 and NCD19R which are manufactured by Network
Computing Devices of Mountain View, California. In this document, the
term NCD19 is used for both the NCD19 and the NCD19R
• model 700/RX which is manufactured by Hewlett-Packard
• model XP18 which is manufactured by Tektronix.
For administrators who have the freedom to choose any of the three terminals,
the NCD19 is recommended.
The OPC automatically provides the OPC font path to these terminals as well
as keyboard mapping.
X terminal models other than those listed above might be able to connect to the
OPC. If the OPC login banner (shown following) appears after a reboot of an
X terminal connected to the appropriate OPC port, then the OPC automatically
provides the OPC font path to the X terminal. For this to happen, the X
terminal must be able to have its font path changed remotely from a host.
Keyboard mapping for unsupported terminals is not guaranteed.

FW-21160
FW-21160
FIBER WORLD
User ID:
Password:
Done Alt+Return
X terminal equipment recommendations

This section includes general recommendations that apply to all X terminals as
well as recommendations that are specific to each X terminal model.
General recommendations
The following recommendations apply to all X terminals:
• To connect with the OPC, the X Server software must run with at least X
version 11 Release 4 (X11 R4).
• X terminals connected to the OPC either directly or through a hub on a
LAN should be configured with a twisted-pair communication port (the
IEEE 802.3 10BaseT interface). The physical port is an RJ45 connector.
• X terminals must be equipped with local X server communications
software as the OPC does not support downloading of X server
communications software. Typically, this is available from the vendor in
the form of an X server programmable read only memory (PROM) or an X
server flash ROM. If local communications software is not provided, there
must be a network server available to the X terminal(s) that can provide it.
When setting up the X terminal, it will be necessary to identify the server.
Note: The equipment lists that follow are subject to vendor-initiated

changes that are beyond the control of Northern Telecom (Nortel).
Therefore, if the specified equipment is not available, use the lists to
establish a configuration that comes as close as possible to that
recommended.
NCD equipment
The NCD19 model should be ordered as follows:
• NCD19R model
• 19-in monochrome (19RP15TWKP) or color (19CP17TWKP) monitor
• X server PROM
• 8 megabytes of random access memory (RAM)
• N-101 keyboard
Note: For NCD X terminals, you must set the font path to “/iws/x11/fonts”
rather than the default.

Hewlett-Packard equipment
The 700/RX model should be ordered as follows:
• 700/RX X terminal model
• 19-in monochrome monitor
• 8 megabytes of RAM (in addition to the 2 megabytes of basic RAM)
• X server and fonts on ROM card
• North American HIL keyboard
Tektronix equipment
The XP18 model should be ordered as follows:
• XP18 X terminal model
• 17-in. color monitor
• 8 megabytes of RAM
• 2 megabytes of flash ROM
• boot ROM and fonts
• PC keyboard
X terminal setup requirements

This section specifies parameter values that must be set on X terminals in order
for them to operate with the OPC. The parameters listed here represent only
those required for connection to the OPC. Other operating environment
characteristics, such as router types and LAN configurations, must be
considered because they often require the setting of other parameters to
specific values.
Contact the terminal vendor to identify the appropriate value based on the type
of router or the LAN configuration that you are using.
IP addresses and node names

Both the Internet Protocol (IP) address and the node name can be assigned
according to your network requirements. However, the following restrictions
must be considered:
• all addresses and names must be unique within the network
• if the local network is to be connected to an external network, the IP
address must conform to DARPA allocation standards to ensure that the IP
addresses are unique.
Obtain the IP addresses and node names from the communications planning
department in your organization or, in the case of the IP addresses that the
planning department does not have, directly from DARPA.
General setup requirements

For operation with the OPC, the following parameters must be setup on all X
terminals:
• for an X terminal that has been used in another application, reset the
terminal to its factory defaults before setting up the other parameters listed
here
• specify the IP address of the X terminal
• set the terminal for remote configuration
• for the remote configuration host, specify the IP address of the OPC
• for the remote configuration file access, specify TFTP
Note: The term “remote configuration” is generic. Each manufacturer has
their own term. Contact the manufacturer’s representative if the X terminal
documentation does not indicate the remote configuration terminology.
• if your network uses node names, specify the node name (IP address alias)
for both the X terminal and the OPC.
NCD-specific requirements
When an NCD19 X terminal reboots, the XDMCP enable flag and the IP
address of the OPC are lost. To compensate for this, the OPC provides an
automatic process for reestablishing these parameters on the NCD X terminal.
The process requires that a configuration file be created on the OPC for each
NCD X terminal. Instructions for adding, changing, or deleting entries in the
configuration file are provided later in this chapter.
700/RX-specific requirements
In addition to the parameters listed previously, the 700/RX has these additional
parameters to define:
• enable XDMCP with Direct Access
• for the XDMCP host, specify the IP address of the OPC

XP18-specific requirements
In addition to the parameters listed previously, the XP18 requires the definition
of the following Host File Access configuration parameters:
• enable XDMCP with Direct Access
• for the XDMCP host, specify the IP address of the OPC
• under Host File Access, set the Primary XP File Root to “/usr/lib/X11/XP”
(quotes not included)
The flash ROM for XP18 X terminals is not always delivered with the X server
software flashed on it. In such a case, the X server communications software
must be downloaded from a network server to the flash ROM. It is only
necessary to do this once.
Note: The OPC does not provide X server communications software

download capability.
Instructions for X terminal setup

Refer to the X terminal documentation for specific instructions on setting up
the X terminal. Contact the X terminal representative if problems arise.
Once the parameters have been defined, they must be saved to NVRAM. To
activate them, the X terminal must be rebooted.
Replacing or exchanging X terminals

If an X terminal is replaced, either with the same vendor’s equipment or with
a different vendor’s equipment, the full setup procedure for the new terminal
has to be followed (as specified in the vendor’s documentation). This is true
even if the IP address is kept the same.
LAN considerations
The following issues should be considered when the OPC is connected to a
LAN:
• When there is WAN access to the LAN, the OPC does not distinguish
between X terminals on the local LAN and other X terminals located
anywhere on the WAN. This might present a security issue that must be
addressed through LAN and WAN administration.
• The OPC assumes that any user session from an OPC is started directly
from an X terminal. Logins to the OPC through an X terminal session
running on an intermediate host are not recommended since problems with
the LAN segment between the OPC and the host, or the host and the X
terminal, might affect the OPC user session. Problems with this type of
setup are beyond the control of the OPC.
• LAN configuration (that is, routers, hubs, connectors) and proper use of
LAN resources is the responsibility of the customer.
• Consider the impact on LAN integrity and performance that will result
when X terminals are connected to an OPC over the LAN. Analysis of the
particular LAN is recommended since LAN configurations vary widely,
making general guidelines inappropriate. LAN engineers using a protocol
analyzer can perform the required analysis.
Note: X clients running from an OPC are the same as X clients running
from a UNIX workstation.
• Modem connections with X terminals over serial lines are not supported on
the OPC (including access through the serial line protocol XRemote).
• At any given time, only one user session from one OPC is supported on an
X terminal.

Cabling options
X terminals, LANs, and Nortel’s Network Manager connect to the OPC using
the Ethernet port on the faceplate of the OPC. Figure Figure 10-1 illustrates the
cabling options for connecting the OPC to network equipment. Details on the
connector pinouts and the cabling options follow the figure.
Figure 10-1
Cabling options for connecting the OPC to the network element
FW-20041
Option A
FW-20041
Dupont connector RJ45 connector
Crossover cable
X terminal
OPC
Option B 15-pin D-type

male connector
RJ45 connector
Dupont connector plugged into MAU
MAU
Straight-through cable
X terminal
OPC
Option C
Dupont connector RJ45 connector

LAN
Straight-through cable hub
OPC
Connector pin-outs
Figure 10-2 shows the pinouts for the Dupont and RJ45 connectors.
Figure 10-2
Dupont and RJ-45 connector pinouts
FW-21702
Dupont connector
FW-21702
1 8
1 3 5 RJ45 connector
pin assignment
2 4 6
Dupont connector
pin assignment RJ45 connector
Cabling option A
Option A applies when there is a point-to-point connection between the OPC
and an X terminal that supports the recommended twisted-pair communication
port (the IEEE 802.3 10BaseT interface). Nortel prefabricated cables have a
2x3 Dupont male connector on one end for connection to the OPC. The other
end has an RJ45 connector for connection to the X terminal. Each cable has
two shielded twisted pairs with transmit and receive crossed over. The cables
conform to FCC Class A requirements. The available cables are as follows:
X terminal straight through cables
Length Product Engineering Code (PEC)
20 m (65 ft) NT4K8ESB
40 m (130 ft) NT4K8ESC
100 m (325 ft) NT4K8ESD

Pin assignments for the crossover cables are shown in the following table:
Dupont connector pin number RJ45 connector pin number
1 Tx+ 3 Rx+
2 Tx- 6 Rx-
5 Rx- 2 Tx-
6 Rx+ 1 Tx+
Cabling option B
Option B applies when there is a point-to-point connection between the OPC
and an X terminal and the X terminal has a 15-pin D-type connector that
conforms to the IEEE 802.3 pin configuration. Nortel prefabricated cables for
this application have a 2x3 Dupont male connector on one end for connection
to the OPC. The other end has an RJ45 connector for connection to the X
terminal. Each cable has two shielded twisted pairs with transmit and receive
wired straight through. The cables conform to FCC Class A requirements. The
available cables are as follows:
X terminal straight-through cables
Length PEC
20 m (65 ft) NT4K8ESB
40 m (130 ft) NT4K8ESC
100 m (325 ft) NT4K8ESD
For Option B, a media access unit (MAU) is required to interface between the
RJ45 IEEE 802.3 connector of the straight through cable and the 15-pin D-type
IEEE 802.3 connector on the X terminal. The Hewlett-Packard HP28685B
Ethertwist Transceiver is a suitable MAU.
Pin assignments for the straight-through cables are shown in the following
table:
Dupont connector pin number RJ45 Connector pin number
1 Tx+ 1 Tx+
2 Tx- 2 Tx-
5 Rx- 6 Rx-
6 Rx+ 3 Rx+
Cabling option C
Option C applies when the OPC is connected to a LAN. In this case, the
straight-through cables NT4K86LA, LB, LC are used to connect the OPC to
the LAN hub.
Network Manager options

Nortel’s Network Manager is a software package designed to run on a
workstation. Consult the workstation hardware and documentation to
determine which cabling option applies.
Note: For more information on the Network Manager, see the Nortel
Network Manager User Guide, 323-4001-050.
Session-terminating conditions
The OPC sends an audit message to the X terminal every minute and
terminates an active session if the X terminal does not respond within one
minute. Any condition that prevents the X terminal from responding to the
audit causes the session to terminate.
NCD19, pre-NCDware v.3 and HP 700/RX considerations

For NCD19 X terminals running pre-NCDware v.3 software and for HP
700/RX X terminals, the terminal does not respond to OPC audit messages
when it is in the Setup mode. To avoid a session termination when in the Setup
mode, perform configuration changes when there is no session established
between the X terminal and the OPC.
OPC window relocation considerations

When you want to relocate a window, the window is represented by a wire grid
image that moves around the screen under control of the mouse. The actual
window reappears when you select the new location. The OPC does not
respond to audit messages while the wire grid is displayed. To avoid session
termination, select the new location for the window within one minute.

Troubleshooting guidelines for X terminals

This section provides troubleshooting guidelines for the most common
problems when connecting X terminals to the OPC.
700/RX and XP18: OPC login banner does not appear

Some versions of the HP 700/RX and Tektronix XP18 X terminal software
have a factory-set time period that applies during the call setup portion of a
connection. The terminals wait for a response from the remote end for this
pre-defined period. If there is no response, the terminals stop polling the
remote end. This is a limitation of the XDMCP functionality on these X
terminal models and, generally, the time period is not configurable.
If the OPC is rebooting when one of these terminals initiates call setup, it is
possible that the time period will be exceeded before the OPC responds. In this
case, the OPC login banner never reappears. To get the OPC login banner to
reappear in such situations, reboot the X terminal after the OPC has returned
to service (allow five to ten minutes for the OPC to reboot).
No OPC login banner after a power failure

When a power failure of both the OPC and the X terminals connected to it
occurs, the X terminals always come back up before the OPC (assuming power
is restored simultaneously on both). In this case, the OPC login banner does
not reappear on these X terminals either because:
• the X terminals give up polling the OPC after a predefined time period (as
is the case for the HP 700/RX and Tektronix XP18)
• the X terminals cannot read their remote configuration file on the OPC
while the OPC is rebooting (as is the case for the NCD19)
To get the OPC login banner to reappear in such situations, reboot the X
terminals after the OPC has returned to service (allow five to ten minutes for
the OPC to reboot).
NCD19 v.3 post-failure windows and dialog boxes

Under some failure scenarios, NCDware version v.3 for the NCD19 displays
specific windows and dialog boxes. The two most common scenarios are loss
of connection during an active OPC session and unavailability of the OPC
while the X terminal is trying to establish a connection.
Loss of connection during an active OPC session

Loss of connection during an active OPC session can occur when the OPC
experiences a power failure or when the Ethernet connection between the OPC
and the X terminal is disabled. In such a case, a dialog with the following
message appears on the X terminal screen:
TCP login manager on “OPC IP address” not responding.

There are X local and Y remote applications running.
Shutdown windows and logout?
Select the YES button on that dialog when it appears.
Unavailability of the OPC during the call setup phase

If the OPC is unavailable while the NCD19 is trying to establish a connection,
the NCD19 X terminal gives up trying to connect to the OPC after a specified
amount of time. Usually, this occurs after rebooting the OPC. A window then
appears with the following message:
Login host not responding; choose another or try

again later?
Wait until the OPC has returned to service (allow approximately five minutes
for the OPC to reboot), then select the OK button on this window. The OPC
login banner from the OPC appears.
Problems connecting over a LAN

Almost all problems associated with LANs arise because of LAN
interconnectivity issues that are independent of the OPC, though they often
prevent communications with the OPC. Contact the LAN vendor since most
issues can be quickly resolved by them.

Engineering guidelines for OPC X terminal sessions

A maximum of four X terminals can be running X mode user sessions at the
same time on the same OPC. This maximum corresponds to a system limit of
any combination of CMT and X mode user sessions. Therefore, if four X mode
user sessions are running on an OPC, no CMT user sessions can be started.
Response time, execution, and tools startup decrease significantly with four
simultaneous X mode user sessions on the same OPC. This is due to full CPU
usage and shortage in available system swap space.
Table 10-1 shows how many tools can be started by the user before the OPC
runs out of swap space, depending on the number of X mode user sessions.
Table 10-1
User session vs. tool capacity
Number of X mode user sessions Number of tools that can be started by

running the user
4 4 to 8
3 10 to 14
2 16 to 20
Note 1: The numbers shown do not include tools that are started automatically.
Note 2: The number of tools that can be started depends on the tools started as well as the
number of X mode user sessions.
The recommendation is to run a maximum of one X mode user session at any

time on the OPC in order to have a sufficient amount of available swap space
and to achieve reasonable execution and response time.
Procedure 10-1
Initializing the OPC Ethernet port
For the OPC to recognize and support communications with a Network
Manager or an X terminal using the Ethernet port on the OPC faceplate, the
OPC Ethernet port must be initialized. Use this procedure to initialize the OPC
Ethernet port so that it can communicate with a Network Manager or an X
terminal.
Requirements
Ensure that the OPC module is properly installed and has booted up.
Obtain the node name, Internet Protocol (IP) address, and IP netmask for the
OPC whose Ethernet port is being initialized.
Action
1 Log in to the OPC using the root userID and password.
The UNIX shell prompt “opc>” appears.
2 Start the Ethernet administration script by typing:
/iws/lan/ether_admin ↵
The Ethernet port command list appears:
1. Initialize and enable the Ethernet port
2. Ethernet port control (enable/disable)
3. X terminals configuration
4. Help
5. Quit
Select one of the above commands [1-5]:
Note: The Ethernet port must be initialized before it can be enabled or
disabled.
3 Select the Ethernet port initialization command by typing:
1↵
A message describing the port initialization requirements appears, followed
by a node name prompt:
Enter the nodename:
4 Type the nodename assigned to the OPC.
The node name consists of up to eight alphanumeric characters. An example
node name is “OPCM001P.”
—continued—



The nodename is checked. If the nodename is not in the correct format an
error message appears, followed by another nodename prompt. If the
nodename prompt reappears, re-execute this step.
Once you enter an acceptable nodename, an IP address prompt appears:
Enter the IP address:
6 Type the unique IP address number assigned to the OPC.
Note: The IP address consists of four numbers, each separated by a period.
Each number must be greater than or equal to 0, and less than or equal to
255. An example IP address is “99.205.1.93”.
The IP address is checked. If the IP address is not in the correct format, or it
is reserved, or already assigned to another OPC, an error message appears,
followed by another IP address prompt. If the IP address prompt re-appears,
re-execute this step.
Once you enter an acceptable IP address, the netmask prompt appears:
Enter the netmask [default 255.255.255.0]:
8 Type the netmask number assigned to the OPC.
The default netmask value is 255.255.255.0. You can accept this value by
pressing Return. If desired, you can enter a new netmask number using the
same criteria as the IP address.
The netmask is checked. If the netmask is not in the correct format, an error
message appears followed by another netmask prompt. If the netmask
prompt re-appears, re-execute this step.
Once you enter an acceptable netmask number, the gateway prompt
appears:
Enter the default gateway [default none]:
—continued—

10 Type the gateway address for the OPC’s LAN.

The gateway is the IP address of the device that routes data for connections
to devices not on the same LAN as the OPC. Leave this blank if you do not
need or want a gateway.
The gateway address is checked. If the address is not in the correct format,
an error message appears followed by another gateway prompt. If the
gateway prompt re-appears, re-execute this step.
Once you enter an acceptable gateway address, a summary of the Ethernet
port initialization values appear, followed by a request to continue:
Initializing Ethernet to:
name: <OPCM001P>
address: <99.205.1.93>
netmask: <255.255.255.0>
gateway: <99.205.1.254>
Do you wish to continue? [yes;no]:
11 Check the initialization values in the summary and verify that they are correct.
continue the Ethernet port initialization step 12.
discontinue the Ethernet port initialization step 15.
12 Continue the Ethernet port initialization process by typing:

yes ↵
The Ethernet port command list appears.
4. Help
5. Quit
Select one of the above commands [1-5]
13 The Ethernet port is now initialized and enabled.
14 Reboot the OPC. If necessary, refer to the procedure “Shutting down an OPC”
in Chapter 6.
The OPC is now ready to communicate with the Network Manager or X
terminal.
—continued—


15 Discontinue the Ethernet port initialization process by typing:

no ↵
16 If you want to re-execute the Ethernet port initialization process, go to step 3.
17 Quit the Ethernet administration script by typing:
5↵
—end—
Procedure 10-2
Enabling and disabling the OPC Ethernet port
Use this procedure to enable or disable the OPC Ethernet port. The OPC can
communicate with the Network Manager or X terminal only when the Ethernet
port is enabled.
Requirements
Ensure that the OPC Ethernet port is initialized (Procedure 10-1). If you
attempt to control the Ethernet port before initializing it, a message that
indicates the port must be initialized before it can be controlled appears.
Action
1 Log in to the OPC using the root userID and password.
The UNIX shell prompt “opc>” appears:
2 Start the Ethernet administration script by typing:
4. Help
5. Quit
3 Select the Ethernet port control command by typing:
2↵
A message that identifies the Ethernet port control values displays, followed
by a prompt for the new Ethernet port status:
You will be prompted for the following information:
new Ethernet port status: enabled or disabled
Type 'abort' at the prompt to terminate the command.
Enter new Ethernet port status [e - enable, d - disable]
—continued—


4 You must disable the Ethernet port to allow the OPC to communicate with the
Network Manager or X terminal. When the Ethernet port is disabled, the OPC
is disconnected from the network.
enable the Ethernet port step 5.
disable the Ethernet port step 6.
5 Enable the Ethernet port by typing:

e↵
The following message appears:
Warning: Unable to add default route in the routing table.
Changes to the routing table will only take effect after
the OPC is rebooted with the OPC shutdown tool.
Refer to Chapter 8, on how to reboot the OPC.
The Ethernet port is now enabled. The OPC is now ready to communicate
with the Network Manager or X terminal.
If the Ethernet port is already enabled, this step has no effect.
Go to step 10.
6 Disable the Ethernet port by typing:
d↵
The following warning message appears:
Warning!
Disabling the Ethernet port will cause loss of network
connectivity.
Do you wish to continue? [yes, no]:
7 If you disable the Ethernet port, the OPC will not be able to communicate with
the Network Manager or X terminal.
continue and disable the port step 8.
leave the port enabled and quit the procedure step 9.
—continued—

8 Continue and disable the Ethernet port by typing:

yes ↵
4. Help
5. Quit
The Ethernet port is disabled, and the OPC will not be able to communicate
with the Network Manager or X terminal.
Go to step 10.
9 Terminate the Ethernet port control procedure without disabling the port by
typing:
no ↵
4. Help
5. Quit
10 Quit the Ethernet administration script by typing:
5↵
The unix shell prompt “opc>” appears.
—end—

Procedure 10-3
Connecting the OPC to network equipment
Use this procedure to connect the OPC to an X terminal, a LAN, or Nortel’s
Network Manager. In this procedure, the term “network equipment” is used to
refer to an X terminal, a LAN, or the Network Manager.
Action
1 Connect the cable to the OPC.
Note: The connector is located on the faceplate of the OPC, under the tape
drive cover.
2 Route the cable to the top of the shelf and secure it using the screws provided
with the cable.
3 Route the cable along the frame’s upright and secure it in place.
4 Run the cable either underneath the floor or on top of the cable troughs to the
location of the X terminal or to the Ethernet LAN’s hub connector.
5 Consult the documentation for the network equipment to identify the location
of the equipment’s Ethernet port.
If the network equipment then go to...
has a twisted pair port step 6.
has a DB-15 port step 7.
6 Connect the RJ45 connector of the cable to the appropriate port on the
network equipment.
Go to step 9.
7 Connect the RJ45 connector of the cable to the MAU.
8 Plug the MAU in to the appropriate port on the network equipment.
9 Ensure that all connectors are fully and firmly seated.
Note: Pin assignments for the cables are shown in the section “Cabling
options” on page 10-9.
—end—
Procedure 10-4
Establishing a telnet session between an X terminal
and the OPC
Use this procedure to establish a telnet session with the OPC.
Requirements
Ensure that the Ethernet port is enabled and initialized.
Action
1 From the X terminal documentation, determine how to start a telnet session.
When instructed to do so, enter the IP address of the OPC.
The OPC “login:” prompt appears.
2 Log in to the OPC as the root user.
The “TERM = (VT100)” prompt appears.
4 The X terminal is now connected to the OPC and is emulating a VT100
terminal in a UNIX session.
If you want to... then
logout type “logout” after the UNIX shell prompt ”opc>”.
continue enter the desired command after the UNIX shell

prompt “opc>”.
—end—

Procedure 10-5
Adding, changing, or deleting an NCD19
configuration file
Because the NCD19 X terminal does not retain certain XDMCP parameters
following a reboot, an NCD19 configuration file on the OPC must be created
to store these parameters.
Use this procedure to add (create), change, or delete an NCD19X terminal

configuration file on the OPC. Once the file is created, it is then loaded to the
NCD19 terminal (using Procedure 8-6 or 8-7).
Requirements
Obtain the software version and IP address of the NCD19 X terminal.
Obtain the NCD19 booting source, either its PROM or the IP address of the
bootserver.
Action
1 Log in to the OPC using the root userID and password on a character-mode
terminal (CMT) or through a telnet session from an X terminal.
2 At the “opc>” prompt, start the Ethernet administration (ether_admin)
program by typing:
4. Help
5. Quit
—continued—

Adding, changing, or deleting an NCD19 configuration file
3 Select the X terminals configuration command by typing:

3↵
A message describing the X terminals configuration option appears. The
system then prompts you to select the desired operation.
add or change the configuration file step 4.
delete an entry in the configuration file step 11.
4 To add or change a configuration file (the process is the same for both), type:
a↵
A message describing the requirements for adding an X terminal
configuration file appears. You are then prompted for the NCD19 software
version number.
If the software version number is... then enter...
v.2 2.
v.3 3.
The system prompts you to enter the IP address of the X terminal.

IP addresses are unique and assigned by your network administrator. The IP
address consists of four numbers, each separated by a period. Each number
falls in the range of 0 to 255, for example, 99.205.1.93.
5 Enter the IP address of the X terminal at the prompt.
The system prompts you to enter the Boot Server IP address.
If the X terminal is... then go to...
is equipped with an X Server PROM step 6.
is not equipped with an X Server PROM and so step 7.

requires communications with a Boot Server in
order to boot
6 If the X terminal is equipped with an X Server PROM, press Return (↵).

Go to step 8.
7 If the X terminal is not equipped with an X server PROM, enter the IP address
of the Boot Server at the prompt, and press Return.
—continued—


8 Continue as required:
If you are... then go to...
changing an existing file step 9.
adding a new file step 10.
9 If you are changing an existing file, the following message appears:

<file name> already exists. Replace it (y or n)?
Enter:
y↵
A message appears stating that the file was added.
Go to step 13.
10 If you are adding a new file, the following message appears:
NCD19 configuration file <file name> added (replaced). Press any key to
continue.
Go to step 13.
11 To delete a configuration file, type:
d↵
A message describing the requirements for deleting an X terminal
configuration file appears. The system then prompts you to enter the IP
address of the X terminal.
Note: IP addresses are unique and assigned by your network administrator.
The IP address consists of four numbers, each separated by a period. Each
number falls in the range of 0 to 255, for example, 99.205.1.93.
12 Enter the IP address of the X terminal at the prompt.
A message appears showing the IP address of the Xterm whose
configuration file is being deleted. A confirmation is required:
Enter:
y↵
A message indicating that an NCD19 configuration file was deleted appears.
13 Continue by pressing Return (↵).
The Ethernet port command list reappears.
14 Quit the Ethernet administration program by typing:
5↵
—continued—

15 Log out of the session by typing:

logout ↵
It is now necessary to load the NCD19 data from the OPC to the NCD19 X
terminal.
If the software version number is... Then continue with...
v.2 Procedure 10-6 on page 10-29
v.3 Procedure 10-7 on page 10-31
—end—

Procedure 10-6
Loading the NCD19 configuration data from the OPC
to an NCD19 X terminal running NCDware v.2
Use this procedure to load the NCD19 configuration parameters that were
created using the ether_admin program. This procedure applies to any version
v.2 of NCDware.
The HP 700/RX X terminal and the Tektronix XP18 X terminal are not covered
because these terminals are self-booting and do not need configuration data
from the OPC. Procedures are not required for these.
After you successfully complete this procedure, a graphical OPC login dialog
appears on the NCD19. Thereafter, the OPC login dialog appears each time
you power on or reset the NCD19.
Requirements
Review the NCD19 User's Manual, to become familiar with the configuration
screens and capabilities.
Verify that the NCDware version is in the v.2 family.
Action
1 Set up the X terminal according to the requirements provided earlier in this
chapter, in “X terminal setup requirements” on page 10-5.
2 From the Main Menu, select Network Parameters in the Configuration Menus
group.
The Network Parameters window appears.
3 Set the Remote Configuration parameter field to Yes.
To change a parameter, click Select on the parameter's value field. The next
value appears in the field. Continue clicking on the field until the desired value
appears.
4 Move the pointer to the Configuration Server field and type the IP Address of
the OPC.
5 Return to the Main window by selecting the Main Menu button in the Network
Parameters window.
6 Select the Save Power-On Values button in the Main Menu window.
—continued—

Loading the NCD19 configuration data from the OPC to an NCD19 X terminal running NCDware v.2
7 Select the Reset Server button in the Main Menu window.

After you confirm the reset request, the NCD19 executes its reset procedure.
After some progress messages, a grey pattern appears on the screen.
An OPC login dialog appears.
FW-21160
FW-21160
FIBER WORLD
User ID:
Password:
Done Alt+Return
The NCD19 is now fully configured and ready to use.

—end—

Procedure 10-7
Loading the NCD19 configuration data from the OPC
to an NCD19 X terminal running NCDware v.3
Use this procedure to load the NCD19 configuration parameters that were
created using the ether_admin program. This procedure applies to any version
v.3 of NCDware.
The HP 700/RX X terminal and the Tektronix XP18 X terminal are not covered
because these terminals are self-booting and do not need configuration data
from the OPC. Procedures are not required for these.
After you successfully complete this procedure, a graphical OPC login dialog
appears on the NCD19. Thereafter, the OPC login dialog appears each time
you power on or reset the NCD19.
Requirements
Review the NCD19 User's Manual, to become familiar with the configuration
screens and capabilities.
Verify that the NCDware version is in the v.3 family.
Action
1 Set up the X terminal according to the requirements provided earlier in this
chapter, in the section “X terminal setup requirements” on page 10-5.
2 From the NCD User Services: Console window, pull down the Console menu
and select Reboot.
The Reboot dialog appears.
3 Select the OK button.
The NCD19 executes its reboot procedure. After some progress messages,
a grey pattern appears on the screen.
4 After a few seconds, an OPC login dialog appears (as shown on page 10-30).
5 The NCD19 is now fully configured and ready to use.
—end—
Procedure 10-8
Reconfiguring X terminals following an OPC upgrade
To display the OPC login banner on an X terminal following an OPC software
upgrade, reboot the terminal. The OPC login banner will appear enabling you
to log in to the OPC.
—end—

11-1
Index 11-
700/RX specific requirements 10-6 B
Bit inversion
A E1 port query 4-152
Access timeslot setting 4-153
NEUI 5-4 Blocking log 4-112
local 5-4 Busy hour 4-109, 4-110, 4-111
remote 5-4
OPCUI 5-5
local 5-5
C
remote 5-5 Cable connectors and pinouts 7-5
user interfaces 5-4 Cabling options 10-9
actIF 4-116 A 10-10
addCP 4-43 B 10-11
addDMC 4-11 C 10-12
addIF 4-117 Call
addLine 4-71 monitoring 4-105
addLink 4-118 statistics totals, display 4-108
Addresses, IP 10-5 Call reference values
Administration modify for one or more lines 4-143
IP routing 5-17 reassign lines 4-144
menus 1-27 Carrier path
OPC 5-14 add new to network 4-43
provisioning 5-29 change route diversity settings 4-65
Alarms channel service state, change 4-100
commands details 4-6 downstream, assign modem 4-47
history buffer, display 4-9 frequency channel range, assign 4-46
menus 1-21 frequency range, reduce or deallocate 4-53
Modem Shelf monitor upstream 4-51
details 4-6 noise threshold, show setting 4-58, 4-59, 4-66,
specific details, display 4-8 4-67
Voice Ports PCM channels 4-78
details 4-6 remove 4-55
allocMarshSpectCP 4-45 rename 4-50
allocSpectCP 4-46 table, frequency channel bands 4-57
alrmdisp 4-7 upstream
alrmrpt 4-8 assign modem 4-47
APU database query 4-87 Voice Port assigned 4-90
asgnModemCP 4-47 CATV
asgnVpHEM 4-73 modem, display 4-97
Autoband 6-4 service, disable 4-74
chanMap 4-99
Channel specified status 4-102
11-2 Index
Character Mode Terminal Commands

logging into HP host systems 2-1 common 4-2
Sun host systems 2-2 NE status 6-22
user interface 2-1 Commissioning, setting time zone, date,
editing text 2-26 time 8-39
getting help 2-22 Common frequency, allocate 4-45
using dialogs 2-20 Communication frequency
using menus 2-12 downstream, change 4-14
using tools 2-8 upstream, change 4-14
checkvp 4-12 conclog 4-112
chgChanState 4-100 Configuration, OPC Ethernet port 10-1
chgIFVariant 4-120 Configuring LC timings 6-23
chgInitialRing 4-121 Connecting a RS-232C cable 6-3
chgLCtimings 4-122 Connections
chgLinkId 4-123 OPC Ethernet port 10-1
chgLinkState 4-124 Connector pinouts 10-10
chgMarshMode 4-49 Considerations
chgModemChan 4-14 LAN 10-8
chgNameCP 4-50 NCD19, preNCDware v.3 10-12
chgPortState 4-125 OPC window relocation 10-12
chgRingCadence 4-126 Cornerstone
chgSMPortCP 4-51 common commands 4-2
chgstate 6-21 toolset
chgstateDMC 4-15 logging in from NEUI 6-16
chgstateModem 4-16 logging in from OPC 7-28
chgstateSM 4-17 correlate 4-77
chgstateVP 4-18 cpCapacity 4-78
chgVpID 4-75 CRV. See Call reference values.
clearTstAcc 4-76 CSOPTCI 4-3
CLLI (trunk group ID), display for current Enable 4-5
HDT 4-146 queryOpt 4-4
Cluster, OPCUI 5-1 CSS and erlangs, toggle display between 4-114
CMT. See Character Mode Terminal. CVALRM 4-6
CNET port 7-15 alrmdisp 4-7
Command Interpreter (CI) alrmrpt 4-8
CSOPTCI 4-3 history 4-9
CVALRM 4-6 cvclear 4-113
CVEQPT 4-10 CVEQPT 4-10
CVloader 4-33 addDMC 4-11
CVPATH 4-41 checkvp 4-12
CVPROV 4-68 chgModemChan 4-14
CVSPMN 4-98 chgstateDMC 4-15
CVTRAF 4-105 chgstateModem 4-16
CVV5 4-115 chgstateSM 4-17
entering a command 9-5 chgstateVP 4-18
FAMCI 4-148 delDMC 4-19
help screen, displaying 9-4 delSM 4-20
MVIPROV 4-142 delVP 4-21
OMCCI 4-154 diagSM 4-22
tool queryBattery 4-23
closing 9-6 queryDMC 4-24
opening 4-2, 9-2 queryMS 4-25
user interface 4-1 queryMSC 4-26
user interface, using 9-1 querySM 4-27
VLCMCI 4-159 queryVP 4-28

Index 11-3
resetMSC 4-31 setLoopCurrent 4-94

resetVP 4-32 setTstAcc 4-95
cvload 4-34 setWideband 4-96
CVloader 4-33 VPmap 4-97
cvload 4-34 CVSPMN 4-98
listdefaults 4-35 chanMap 4-99
mscflswact 4-36 chgChanState 4-100
queryCVswldFile 4-37 freqMap 4-101
queryload 4-38 queryChannel 4-102
setCVswldFile 4-39 queryRF 4-103
syncdefaults 4-40 CVTRAF 4-105
CVPATH 4-41 conclog 4-112
addCP 4-43 cvclear 4-113
allocMarshSpectCP 4-45 queryBHbrief 4-110
allocSpectCP 4-46 queryCallInfo 4-108
asgnModemCP 4-47 querygos 4-111
chgMarshMode 4-49 queryTopBH 4-109
chgNameCP 4-50 trafunits 4-114
chgSMPortCP 4-51 CVV5 4-115
deallocMarshSpectCP 4-52 actIF 4-116
deallocSpectCP 4-53 addIF 4-117
deasgnModemCP 4-54 addLink 4-118
delCP 4-55 chgIFVariant 4-120
Enable_ExtRange 4-56 chgInitialRing 4-121
queryCP 4-57 chgLCtimings 4-122
queryPortThSM 4-58, 4-59, 4-66, 4-67 chgLinkId 4-123
setMinMarshDistance 4-60 chgLinkState 4-124
setModemRxPower 4-61 chgPortState 4-125
setModemTxPower 4-62 chgRingCadence 4-126
setPortThSM 4-63 deactIF 4-127
setProtBandCP 4-64 delIF 4-128
setRouteDiversity 4-65 delLink 4-129
CVPROV 4-68 queryFreePort 4-130
addLine 4-71 queryInitialRing 4-131
asgnVpHEM 4-73 queryLCtimings 4-133
CATV 4-74 queryLink 4-132
chgVpID 4-75 queryPort 4-134
ClearTstAcc 4-76 queryRingCadence 4-136
correlate 4-77 queryV5 4-137
cpCapacity 4-78 setDefLCTimings 4-139
deasgnVp 4-79 setDefRingCadence 4-140
delLine 4-80
enableConc 4-81
modemCapacity 4-82 D
Movevp 4-83 Data
queryCapacity 4-84 provisioning, display 4-86
queryEncryption 4-85 retrieving from tape 8-15
queryLCMsvc 4-86 saving to tape 8-9
queryLCTemplate 4-87 service specified, display 4-97
queryMVIsvc 4-88 specified unit 4-84
queryTstAcc 4-89 transferring between OPCs 8-24
queryVpSvc 4-90 Database
queryWideband 4-91 restoring 8-34
setEncryption 4-92 Date, commissioning 8-39
setLCTemplate 4-93 deactIF 4-127
11-4 Index
deallocMarshSpectCP 4-52 associations, display 4-132

deallocSpectCP 4-53 unassign from V5.2 4-129
deasgnModemCP 4-54 V5.2 switch interface 4-118
deasgnVp 4-79 port, query bit inversion 4-152
delCP 4-55 editCRV 4-143
delDMC 4-19 editIDT 4-147
Deleting Enable 4-5
OMC link 4-157 Enable_ExtRange 4-56
delIF 4-128 enableConc 4-81
delLine 4-80 Encryption
delLink 4-129 querying 4-85
delSM 4-20 setting 4-92
delVP 4-21 Equipment
Deprovisioning HP 10-5
cable TV 4-68 menus 1-24
carrier paths 4-41 Modem shelf, status 4-25
CATV and phone services 4-68 NCD 10-4
facility 4-151 Spectrum Manager, status 4-25
headend modems 4-41 Tektronix 10-5
line Ethernet port
phone services 4-68 configuration and connections 10-1
selected DMC 4-19 enabling and disabling 10-20
Detecting/removing existing OPC software 8-27 initializing 10-16
diagSM 4-22 Extended range
Dialogs, using 2-20 checkvp 4-12
Digital Test Access (DTA) enable 4-5, 4-56
deprovision lines 4-76 queryvp 4-28
provision lines 4-95
provisioned VP lines 4-89
query lines 4-89 F
Voice Port provisioning 4-95 Faceplate, OPC 5-2
Display Facility
help for a CI tool 9-4 assignments, display 4-150
VLCM status 4-159 currentassignments, display 4-148
D-link modem card maintenance 4-10 deprovision 4-151
DMC menus 1-23
deprovision 4-19 provisioning 4-149
primary state, change 4-15 famAssign 4-149
provision, manually 4-11 FAMCI 4-148
show status 4-24 famAssign 4-149
Downloading firmware loads to famQuery 4-150
modem shelf equipment 4-33 famUnassign 4-151
Voice Ports 4-33 qBitInv 4-152
Downstream sBitInv 4-153
communication frequency, change 4-14 famQuery 4-150
direction, display 4-57 famUnassign 4-151
set distance between headend and VP 4-60 Feature, enable optional 4-5
set transmission power level 4-62 Features
Downstream, assign modem 4-47 NEUI 1-1
DTA. See Digital Test Access. FiberWorld product user interface
closing 6-9
logging in problems 6-10
E File
E1 Modem shelf load lineup 4-37
facility update 4-39

Index 11-5
Firmware Line
downloading 4-33 assignments, display current 4-145
modem shelf equipment 4-33 deprovisioning
Voice Ports 4-33 service provisioning 4-71
freqMap 4-101 service, deleting 4-80
Frequency channel range, assign 4-46 Line-by-line terminal 6-9
Frequency range, reduce or deallocate 4-53 Line card 6-20
FWPUI. See FiberWorld product user interface. configuring 6-23
instance, display 4-97
provisioning 6-20
G timings
Gateway, IP routing 5-17 current settings,display 4-133
set default values 4-139, 4-140
H timings, changing 4-122
working with 6-20
HDT. See Host Digital Terminal.
Headend Link
CATV enabled 4-73 OMC
modem deleting 4-157
deassign 4-54 Link ID value, changing 4-123
Voice Ports 4-82, 4-83 linkStatus 4-160
set distance to VP 4-60 listdefaults 4-35
Help menus 1-29 Lists, using 2-18
Help, getting 2-22 Local Craft Access Panel (LCAP) 6-3
Hewlett-Packard equipment 10-5 Log monitoring 4-112
history 4-9 Logging
Host Digital Terminal (HDT) Cornerstone toolset, into 7-28
enable extended range 4-56 in and out of NEUI 6-7
software, reload or upgrade 4-34 into OPC 7-19
V5.2 switch interface, activate 4-116 into OPC from NE 7-26
wideband channels, enabling/disabling 4-96 into remote OPC from local OPC 7-23
Host Provisioning Manager tool 5-22 OPC, out of 7-34
HP host systems 2-1 out of the NEUI 6-9
Loop current specified line, setting 4-94
I M
IG. See Interface group.
Initializing OPC Ethernet port 10-16 Main menu, displaying 6-9
Installing software in a local OPC 8-31 Mapci menus 1-21
Interface group Mapping
display for current HDT 4-146 channels to frequencies 4-99
modify for one or more lines 4-143 frequencies to channels 4-101
reassign all lines 4-147 Marshalling
reassign lines 4-144 frequency channel
Interface type, display for current HDT 4-146 deallocate 4-52
Interface, OPC mode, change 4-49
character-mode user interface 2-1 OOB mode 4-52
graphical user interface (OPCUI) 3-1 Menus
IP addresses and node names 10-5 administration 1-27
alarms 1-21
displaying 2-14
L equipment 1-24
LAN considerations 10-8 facility 1-23
LC template, setting the 4-93 Help 1-29
LCAP. See Local Craft Access Panel. Mapci 1-21
LCM services provisioning data display 4-86 mode 2-15
11-6 Index
performance monitoring 1-22 database

protection 1-22 restoring 8-34
Message list, reset 4-164 far-end 6-11
Messages, display unexpected 4-162 logging
Modem into OPC, commands for 7-26
assign 4-47 NEUI 5-1
busiest hour, display 4-110 OPC, logging into 7-26
external 7-17 password, changing 6-19
headend, deassign 4-54 portable OPC, connecting 7-15
primary state, change 4-16 status
Voice Port assigned 4-90 commands 6-22
Modem Shelf determining 6-22
active alarms, display 4-7 screen 6-8
alarm template type 4-87
history 4-9 user interface. See Network Element User
alarms, viewing detailed information 4-6 Interface
equipment Network Element User Interface (NEUI)
maintenance 4-10 access 5-4
load lineup file 4-37 command menus 1-20
load lineup file, update 4-39 description 5-6
status 4-25 far-end, logging in 6-11
Modem Shelf Controller (MSC) features 1-1
default load entity set, update 4-40 I/O editing features 1-11
equipment levels of control 5-1
query 4-26 local access 5-4
reset 4-31 local, logging in and out 6-7
loads currently contained, display 4-35 logging
OPC read defaults load file 4-40 in/out 6-13
swaps and resets to the processor 4-36 out 6-9
modemCapacity 4-82 menu
Monitoring calls 4-105 based screens 5-6
moveCRV 4-144 hierarchy 1-1
movevp 4-83 overview 5-1
MSC. See Modem Shelf Controller procedures 6-1
mscflswact 4-36 remote access 5-4
MVI services provisioning information, screen
query 4-88 attributes 1-1, 1-2
MVIPROV 4-142 layout 1-2, 1-10
editCRV 4-143 session, opening 6-17, 6-22
editIDT 4-147 status messages 1-9
moveCRV 4-144 Network Manager 5-1
queryIDT 4-146 options 10-12
queryProv 4-145 Network surveillance tools
Alarm Monitor 5-24
Event Browser 5-24
N Network Browser 5-24
Name, OPC changing 7-41 Network Summary 5-24
NCD NEUI. See Network Element User Interface.
equipment 10-4 Node names, IP 10-5
specific requirements 10-6 Noise threshold
NCD19 considerations 10-12 set power level 4-63
NE. See Network Element. show setting for carrier path 4-58, 4-59, 4-66,
Network Element (NE) 4-67
connecting
a local terminal 6-3
a VT100 terminal 6-5, 7-17

Index 11-7
O password, changing 7-36

portable, details
OAM&P commands 4-115 connecting to a terminal 7-13
omc add 4-155 connecting to network element 7-15
omc delete 4-157 procedures, other 8-1
omc query 4-158 remote, logging into a 7-23
OMCCI 4-154 removing tape from tape drive 8-30
omc add 4-155 setting time zone, date, or time 8-39
omc delete 4-157 shutting down/rebooting 8-3
omc query 4-158 software
setdlchan 4-156 detecting/removing 8-27
OPC. See Operations Controller. installing 8-31
OPCUI. See Operations Controller, graphical status, displaying 7-39
user interface. Telnet session with X terminal 10-24
Operations Controller (OPC) terminal
cabling options 10-9 CNET port 7-15
A 10-10 connecting to a portable 7-13
B 10-11 connections 7-8
C 10-12 portable terminator plug 7-16
checking tape identification 8-7 tool
commands 7-26 closing 7-33
connecting 10-23 opening 7-31
a terminal 7-4 window relocation considerations 10-12
data Operations Controller User Interface
retrieving from tape 8-15 (OPCUI) 2-8
saving to tape 8-9 access 5-5
transferring data between OPCs 8-24 cluster 5-1
Ethernet port common procedures 7-1
configuration/connections 10-1 description 5-7
controlling 10-20 local access 5-5
initializing 10-16 logging
faceplate 5-2 in/out of NE 6-13
graphical user interface logging in from an NE 7-26
closing a tool 3-37 remote access 5-5
command areas 3-35 software
editing text 3-32 administration toolset 5-10
entering information 3-23, 3-26 tools and toolsets 5-7
getting help 3-23 span of control 5-22
introduction 3-1 tool
logging Alarm Monitor 5-25
in 3-1 Alarm Provisioning Manager 5-23
out 3-38 Backup/Restore Manager 5-11
managing the workspace 3-16 Centralized User Administration 5-14
using Cluster Level Inventory 5-21
menus 3-11 Commissioning Manager 5-28
mouse and keyboard 3-1 Connection Manager 5-20
tools and toolsets 3-1 E2A Alarm Manager 5-19
UNIX 3-37 Event Browser Manager 5-12
LAN considerations 10-8 Host Provisioning Manager 5-22
logging IP Routing Admin 5-17
in 7-19 NE Login Manager 5-30
into Cornerstone toolset 7-28 NE Software Delivery Manager 5-13
out 7-34 Network Browser 5-27
loss of connection 10-14 Network Summary 5-26
MSC defaults load file, read 4-40 OPC Date 5-16
name, changing 7-41
11-8 Index
OPC Save and Restore 5-16 DMC, selected 4-11

OPC Shutdown 5-16 facility 4-149
OS Connection Manager 5-29 headend modems 4-41
Password Update 5-31 information, query 4-88
Port Configuration 5-17 line
Reboot/Load Manager 5-10 card 6-20
Remote OPC Software Installation 5-15 service 4-71
Status 5-18 phone services 4-68
UNIX shell 5-17 ring cadence ring types 4-136
toolset V5.2 switch interface 4-117
network administration 5-18 VLCM
Network surveillance 5-24 DS1/E1 links 4-160
OPC administration 5-14 units, current state 4-163
Provisioning administration 5-29 Voice Port
SLAT 5-27 data 4-79
Utilities 5-30 line for DTA 4-95
User Session Manager 5-9 services 4-90
Operations Maintenance Channel (OMC) Pulse duration modify initial ring 4-121
deleting link 4-157
links 4-154
provisioning link 4-155 Q
query link assignments 4-158 qBitInv 4-152
Optionality Query optionality 4-4
commands 4-3 queryBattery 4-23
query 4-4 queryBHbrief 4-110
Other 8-1 queryCallInfo 4-108
queryCapacity 4-84
queryChannel 4-102
P queryCP 4-57
Password queryCVswldFile 4-37
changing 7-36 queryDMC 4-24
NE, changing 6-19 queryEncryption 4-85
update 5-31 queryFreePort 4-130
PCM channels 4-78 querygos 4-111
Voice Ports 4-82 queryIDT 4-146
Peak hour 4-110, 4-111 Querying
usage 4-109 OMC link assignments 4-158
Performance monitoring menus 1-22 queryInitialRing 4-131
Pinouts, connector 10-10 queryLCMsvc 4-86
Port ID unassigned values, display 4-130 queryLCTemplate 4-87
Port status, display 4-134 queryLCtimings 4-133
Procedures queryLink 4-132
OPC, other 8-1 queryload 4-38
OPCUI 7-1 queryMS 4-25
Processor queryMSC 4-26
current load, display 4-38 queryMVIsvc 4-88
load specified 4-34 queryOpt 4-4
Protection menus 1-22 queryPort 4-134
Provision queryPortThSM 4-58, 4-59, 4-66, 4-67
OMC link 4-155 queryProv 4-145
Provisioning queryRF 4-103
administration 5-29 queryRingCadence 4-136
cable TV 4-68 querySM 4-27
carrier paths 4-41 queryTopBH 4-109
CATV and phone services 4-68 queryTstAcc 4-89

Index 11-9
queryV5 4-137 Password Update 5-31

queryVP 4-28 Port Configuration 5-17
queryVpSvc 4-90 Progress dialog 8-13
queryWideband 4-91 Reboot/Load Manager 5-10
Remote OPC Software Installation 5-15
Save confirmation dialog 8-11
R Shutdown process dialog 8-4
Rebooting OPC 8-3 SLAT 5-27
Requirements Tape Details dialog 8-8
700/RX specific 10-6 Time and date change dialog 8-41
general 10-6 User Session Manager 2-3, 5-9
NCD specific 10-6 setCVswldFile 4-39
XP18 specific 10-7 setDefLCTimings 4-139
resetMSC 4-31 setDefRingCadence 4-140
resetVP 4-32 setdlchan 4-156
Restoring an NE database 8-34 setEncryption 4-92
Restoring OPC data from tape 8-15 setLCTemplate 4-93
RF setLoadName 4-161
concentration mode, modify 4-81 setLoopCurrent 4-94
detected energy levels 4-103 setMinMarshDistance 4-60
Ring cadence setModemRxPower 4-61
modify for ring type 4-126 setModemTxPower 4-62
provisioned, display current settings for 4-136 setPortThSM 4-63
Ring pulse duration setting, display 4-131 setProtBandCP 4-64
Route diversity, change settings 4-65 setRouteDiversity 4-65
RS-232C cable 6-3 Setting time zone, date, or time 8-39
setTstAcc 4-95
S Setup
general requirements 10-6
Saving data to tape 8-9
sBitInv 4-153 X terminal 10-7
Screens setWideband 4-96
Alarm Monitor 5-25 Shutting down OPC 8-3
Alarm Provisioning Manager 5-23 SLAT toolset 5-27
Backup/Restore Manager 5-11 Slot assignments, display or modify 4-142
Centralized User Administration 5-14 Software
Cluster Level Inventory 5-21 detecting/removing OPC 8-27
Commissioning Manager 5-28 download channel, assigning 4-156
Completion dialog 8-14 local OPC, installing in a 8-31
Confirmation dialog 8-14 OPCUI
Connection Manager 5-20 administration toolset 5-10
E2A Alarm Manager 5-19 tools and toolsets 5-7
Event Browser Manager 5-12 reload or upgrade in HDT
Host Provisioning Manager 5-22 restart on a VP 4-32
Line Card Provisioning 6-20 Span of control 5-22
Main window 2-11 Spectrum Manager
NE Login Manager 5-30 chassis run diagnostics 4-22
NE Software Delivery Manager 5-13 delete 4-20
Network Browser 5-27 equipment
Network Element Status 6-8 maintenance 4-10
Network Summary 5-26 state, change 4-17
Network Surveillance Manager 5-24 maintenance commands 4-98
OPC Save and Restore 5-16, 8-7 monitor upstream Carrier path 4-51
OPC Shutdown 8-3 selected status 4-27
OPC Status 5-18 status 4-25
OS Connection Manager 5-29 Status, displaying OPC 7-39
11-10 Index
Sun host systems 2-2 CI

syncdefaults 4-40 closing 9-6
displaying help 9-4
entering a command 9-5
T opening 9-2
Tables Cluster Level Inventory 5-21
Menu modes and effects of End and Commissioning Manager 5-28
Abort 2-15 Connection Manager 5-20
Port locations and designations for an OPC in a E2A Alarm Manager 5-19
ABM shelf 7-4 Event Browser Manager 5-12
Suggested key mapping assignment for laptop Host Provisioning Manager 5-22
function keys 7-12 IP Routing Admin 5-17
Time zone codes and GMT offsets 8-46 NE Login Manager 5-30
Tape identification, OPC 8-7 NE Software Delivery Manager 5-13
TCP/IP routing 5-17 Network Browser 5-27
Tektronix equipment 10-5 Network Summary 5-26
Terminal OPC
connecting to closing 7-33
a network element 6-3 opening 7-31
a portable OPC 7-13 OPC Date 5-16
an OPC 7-4 OPC Save and Restore 5-16
connections to OPC 7-8 OPC Shutdown 5-16
line-by-line 6-9 opening 2-10
VT100 OS Connection Manager 5-29
compatible 6-5 Password Update 5-31
requirements 7-7 Port Configuration 5-17
X11 Reboot/Load Manager 5-10
connecting to the OPC 10-23 Remote OPC Software Installation 5-15
engineering guidelines 10-15 Status 5-18
equipment UNIX shell 5-17
HP 10-5 Toolset
NCD 10-4 Cornerstone 6-16, 7-28
recommendations 10-4 Network administration 5-18
Tektronix 10-5 Network surveillance 5-24
NCD19 configuration OPC administration 5-14
data, loading from the OPC 10-29, Provisioning administration 5-29
10-31 SLAT 5-27
file 10-25 Utilities 5-30
reconfiguring after OPC upgrade 10-32 Traffic monitoring counter, clearing 4-113
replacing or exchaning 10-8 trafunits 4-114
session, terminating 10-12 Transferring data between OPCs 8-24
setup 10-7 Transmit levels, checking for explicit 4-12
requirements 10-5 Troubleshooting X terminal 10-13
support 10-3
Telnet session with OPC 10-24
troubleshooting 10-13 U
Testing OPC procedures 8-1 Unit capacity data 4-84
Time UNIX
commissioning 8-39 common commands 2-30
zone commissioning 8-39 editor (vi) 2-31
Tools tool, shell 5-17
Alarm Monitor 5-25 using 2-29
Alarm Provisioning Manager 5-23 unknown (command) 4-162
Backup/Restore Manager 5-11 Upstream
Centralized User Administration 5-14 assign modem 4-47

Index 11-11
capacity, PCM channels 4-78 Voice Ports

channels, RF detected energy levels 4-103 alarms
communication frequency, change 4-14 detailed information, viewing 4-10
direction, display 4-57 viewing detailed information 4-6
monitor carrier path 4-51 alias, correlating with VPID 4-77
setting aliases 4-2
noise threshold power level 4-63 assigned to modem or carrier path 4-90
protection bands 4-64 changing or added new ID 4-75
receiving power level 4-61 configuration, query 4-28
User interface delete provisioning data 4-79
access 5-4 equipment
Network Element data, delete 4-21
command menus 1-20 maintenance 4-10
features 1-1 headend with CATV 4-73
I/O editing features 1-11 id, display 4-97
menu hierarchy 1-1 lines provisioned for DTA 4-89
screen maintenance 4-10
attributes 1-1, 1-2 marshalling state, query 4-28
layout 1-2, 1-10 moving from one HEM to another 4-83
status messages 1-9 PCM channels 4-82
User Session Manager 5-9 provisioning data, delete 4-21
Using CI tools 9-1 restart software 4-32
services provisioned, display 4-90
set distance to headend 4-60
V specific criteria, listing 4-12
V5.2 specified battery conditions, display all 4-23
interface status, query 4-28
assign variant_id 4-120 toggle between IS and OOS states 4-18
commands 4-115 VPID 4-77
information, display 4-137 VPmap 4-97
NE status 6-22 VT100
put link in a given state 4-124 remote, connecting through BIP modem 6-5,
put port in a given state 4-125 7-17
switch terminal
activates on HDT 4-116 connecting to portable OPC 7-13
deactivate on HDT 4-127 requirements 7-7
E1 facility association 4-118
OAM&P commands 4-115
provisioning 4-117 W
remove from HDT 4-128 Wideband
unassign E1 facility 4-129 channels on HDT 4-96
VLCM flag 4-91
DS1/E1 links 4-160 status of system based flag 4-91
interface commands 4-159
set load name 4-161
status X
checking 4-159 X terminal
display 4-159 connecting to the OPC 10-23
VLCMCI 4-159 engineering guidelines 10-15
linkStatus 4-160 equipment
setLoadName 4-161 HP 10-5
unknown 4-162 NCD 10-4
vlcmStatus 4-163 recommendations 10-4
zero 4-164 Tektronix 10-5
vlcmStatus 4-163 HP 700/RX 10-12
NCD19
11-12 Index
configuration
data, loading from the OPC 10-29,
10-31
file, creating 10-25
considerations 10-12
reconfiguring after OPC upgrade 10-32
replacing or exchaning 10-8
session, terminating 10-12
setup 10-7
requirements 10-5
support 10-3
Telnet session with OPC, establishing 10-24
troubleshooting 10-13
XP18 specific requirements 10-7
Z
zero (command) 4-164

Cornerstone
User Interfaces Reference Guide
 2001 ARRIS
All rights reserved
The information in this document is subject to change without
notice. The statements, configurations, technical data, and
recommendations in this document are believed to be accurate
and reliable, but are presented without express or implied
warranty. Users must take full responsibility for their applications
of any products specified in this document. The information in this
document is proprietary to ARRIS.
ARRIS, ARRIS Interactive, and Voice Port are trademarks of

ARRIS Licensing Company. Cornerstone is a registered
trademark of ARRIS Licensing Company. AccessNode is a
registered trademark of Nortel Networks. All other trademarks
and registered trademarks are the property of their respective
holders.
Document number: ARSVD00399

Release 8.1 Standard 1.0
September 2001

UIReference - Arris PDF

Caricato da

Informazioni sul documento

Titolo originale

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

UIReference - Arris PDF

Caricato da

Copyright:

Formati disponibili

Cornerstone

Release 8.1 Standard 1.0 September 2001

Document number: ARSVD00399

Cornerstone ARSVD00399 Release 8.1 Standard 1.0 September 2001

Moving through the CMT user interface 2-5

Cornerstone ARSVD00399 Release 8.1 Standard 1.0 September 2001

Using tools and toolsets 3-5

Menu bar menus 3-11

MVIPROV commands 4-142

Cornerstone ARSVD00399 Release 8.1 Standard 1.0 September 2001

X terminal running NCDware v.2 10-29

Cornerstone ARSVD00399 Release 8.1 Standard 1.0 September 2001

About this document

Chapters 1 through 4 describe the user interfaces available for a Cornerstone

If you cannot successfully complete any of the procedures in this manual,

References in this document

The following is a list of other related reference documents:

Warnings and safety precautions

To avoid damage to equipment or service interruptions, follow all caution

Samples of danger and caution warnings follow.

Cornerstone ARSVD00399 Release 8.1 Standard 1.0 September 2001

Network element user interface 1-

The NEUI provides the following screen attributes:

• categorized on-screen alarm indicators

Each network element allows multiple users to be connected to the user

Selected NE System Status Area

Output Scroll Area

Host NE Command Input Area

As shown above, the screen is partitioned into six areas:

Cornerstone ARSVD00399 Release 8.1 Standard 1.0 September 2001

System status area

Critical Major minor warning FailProt Lockout ActProt PrfAlrt

Command menu display area

Cornerstone ARSVD00399 Release 8.1 Standard 1.0 September 2001

Command input area

NE identity and time area

Cornerstone ARSVD00399 Release 8.1 Standard 1.0 September 2001

Network Element Status Shelf: 1

NE ID Alarms Protection Prf

The concept of “context”

Cornerstone ARSVD00399 Release 8.1 Standard 1.0 September 2001

Note: It is not possible to toggle a parameter on a number of objects

Monitoring Unavailable - Autonomous updating of the current screen (that

Communications Lost - The communications link to the indicated network

Operation In Progress, Please Wait - On initial entry to the Network

Cornerstone ARSVD00399 Release 8.1 Standard 1.0 September 2001

Input and output editing features

Throughout this documentation, to “enter” a command means to type in the

All alphabetic input is case insensitive and is converted to uppercase.

Commands with optional parameters have default values assigned to the

To create a macro, type:

To use a macro, type:

Command parameter prompting

Cornerstone ARSVD00399 Release 8.1 Standard 1.0 September 2001

Last command recall

Multiple command entry

Common menu commands or options

Forceout This allows a user with “admin” privileges to login to a

Msg The message command allows you to send messages to one

Quit Returns to the parent level menu in the current menu

Showval On the performance screens, this command shows values in

Cornerstone ARSVD00399 Release 8.1 Standard 1.0 September 2001

<ctrl> F Moves the cursor to the right, one position.