1511 302 PDF

323-1511-302
Nortel Networks
OPTera Connect DX Connection
Manager Rel 1 & TN-64X Rel 3
External Interface Configuration Procedures
Standard August 2000
What’s inside...
External communications ports
Configuring OPC ports
Managing X terminals for the OPC
Copyright  2000 Nortel Networks, All Rights Reserved
The information contained herein is the property of Nortel Networks and is strictly confidential. Except as expressly authorized in
writing by Nortel Networks, the holder shall keep all information contained herein confidential, shall disclose it only to its employees
with a need to know, and shall protect it, in whole or in part, from disclosure and dissemination to third parties with the same degree
of care it uses to protect its own confidential information, but with no less than reasonable care. Except as expressly authorized in
writing by Nortel Networks, the holder is granted no rights to use the information contained herein.
Nortel Networks, the Nortel Networks logo, the Globemark, How the World Shares Ideas, S/DMS TransportNode, and Unified
Networks are trademarks of Nortel Networks.
VT100 is a trademark of Digital Equipment Corporation.

UNIX is a trademark of X/Open Company Ltd.
Printed in Canada and in the United Kingdom

i
Contents 0
About this document iii
External communications ports 1-1
Configuring OPC ports 2-1

List of procedures
2-1 Configuring an OPC port to support terminal operation 2-5
2-2 Configuring an OPC port to support TCP/IP applications using PPL
(SLIP) 2-10
2-3 Configuring an OPC port to support printer operation 2-25
2-4 Unconfiguring an OPC port 2-33
2-5 Connecting the cable 2-37
2-6 Configuring a modem for PPL (SLIP) 2-39
Managing X terminals for the OPC 3-1

X terminal support 3-2
X terminal equipment recommendations 3-3
General recommendations 3-3
NCD equipment 3-3
Hewlett-Packard equipment 3-3
Tektronix equipment 3-4
X terminal setup requirements 3-4
IP addresses and node names 3-4
General setup requirements 3-4
NCD-specific requirements 3-5
700/RX-specific requirements 3-5
XP18-specific requirements 3-5
Instructions for X terminal setup 3-6
Replacing or exchanging X terminals 3-6
LAN considerations 3-6
Cabling options 3-7
Cabling option A 3-8
Cabling option B 3-9
Cabling option C 3-9
Preside Applications Platform options 3-10
Session-terminating conditions 3-10
NCD19, pre-NCDware v.3 and HP 700/RX considerations 3-10
OPC window movement 3-10
External Interface Configuration Procedures 323-1511-302 Standard Aug 2000

ii Contents
Troubleshooting guidelines for X terminals 3-11

700/RX and XP18: OPC log in banner does not appear 3-11
No OPC log in banner after a power failure 3-11
NCD19 v.3 post-failure windows and dialog boxes 3-11
Problems connecting over a LAN 3-12
Engineering guidelines for OPC X terminal sessions 3-13
List of procedures
3-1 Initializing the OPC Ethernet port 3-15
3-2 Controlling the OPC Ethernet port 3-20
3-3 Establishing a telnet session between an X terminal and the OPC 3-24
3-4 Adding, changing, or deleting an NCD19 configuration file 3-26
3-5 Loading the NCD19 configuration data from the OPC to an NCD19 X terminal
running NCDware v.2 3-31
3-6 Loading the NCD19 configuration data from the OPC to an NCD19 X terminal
running NCDware v.3 3-34
3-7 Reconfiguring X terminals following an OPC upgrade 3-36
OPTera Connect DX Connection Manager Rel 1 & TN-64X Rel 3 323-1511-302 Standard Aug 2000
iii
About this document 0

This document describes the external interface configuration procedures for
Nortel Networks’ OPTera Connect DX Connection Manager (referred to
OPTera Connect DX in this document) and TN-64X Release 3 network
elements. Topics covered include the following:
• external communications ports
• OPC port configuration
• communications between OPC and X terminals
Audience
This document is for the following members of the operating company:
• planners
• provisioners
• network administrators
• transmission standard engineers
• maintenance personnel

iv About this document
OPTera Connect DX and TN-64X Release 3 NTP Libraries

Managing and Supporting
Installing, Maintaining and
Planning a documentation for the
Network
Commissioning and Provisioning Troubleshooting
OPTera Connect DX
Testing a Network a Network
a Network and TN-64X Library
TN-1X NTP Library

(323-1061-XXX)
TN-4X NTP Library

(323-1121-XXX)
Installation User Interface Performance
Planning Guide
Procedures Connection Procedures Monitoring Procedures
(NTRR11DA)
(323-1531-201) (323-1511-301) (323-1531-520)
Planning Guide Installation External Interface Performance TN-4XE NTP Library

(NTRR12DA) Procedures Monitoring Procedures (323-1123-XXX)
(323-1551-201)
Configuration (323-1551-520)
About the OPTera Procedures
Connect DX SDH Powering up and (323-1511-302)
Software Administration
Fault Detection
and TN-64X Commissioning (323-1531-541)
NTP Libraries Procedures Procedures
(323-1531-090 or (323-1531-220) (323-1511-303) TN-16X NTP Library
Fault Detection (323-1211-XXX)
323-1551-090 or
Data Administration (323-1551-541)
323-1531/1551-090) Powering up and
Commissioning Procedures
Procedures (323-1511-304) Alarm Reference
Circuit
Pack Descriptions (323-1551-220) Guide
Security Management (323-1531-542)
(323-1511-102) Procedures Optical Networks
Site Testing (323-1511-305) Applications Library
Ordering Procedures Alarm Reference (NTCA66BA)
Information (323-1531-221) Guide
Provisioning and (323-1551-542)
(323-1531-151) Operations Procedures
Site Testing (323-1531-310)
Ordering Procedures Trouble Clearing and
Information (323-1551-221) Module Replacement
Provisioning and (323-1531-543) OPTera Long Haul
(323-1551-151)
Operations Procedures 1600 NTP Library
System Commissioning (323-1551-310)
NE User Interface and Testing Procedures Trouble Clearing and (NTCA65EC)
Description (323-1531-222) Module Replacement
Protection (323-1551-543)
(323-1511-195) Switching Description
System Commissioning and Procedures
OPC User Interface and Testing Procedures (323-1531-311) Log Reference
Description (323-1551-222) (323-1511-840)
Orderwire User
(323-1511-196) Protection Guide
Switching Description (NTCA66DA)
and Procedures
(323-1551-311)
References for NTP 302

Preside NTP
OPC User Interface Description, 323-1511-196 Library
Installation Procedures, 323-1531/-1551-201 (450-3101-XXX)
User Interface Connection Procedures, 323-1511-301
Software Administration Procedures, 323-1511-303
Security Management Procedures, 323-1511-305
Provisioning and Operations Procedures, 323-1531/-1551-310
About this document v
External Interface Configuration Procedures Summary

Main tasks:
• As required, configure an OPC port to support the following operations:
— Terminal operation (Procedure 2-1)
— TCP/IP applications using PPL (SLIP) (Procedure 2-2)
— Printer operation (Procedure 2-3)
• Unconfigure an OPC port (Procedure 2-4)

• Connecting a cable (Procedure 2-5).
• Configuring a modem for PPL (SLIP) (Procedure 2-6).
• Manage the X terminals for the OPC

— Initialize and control the OPC Ethernet port (Procedure 3-1 and Procedure 3-2)
— Connect the OPC to network equipment (Procedure 3-3)
— Establish a Telnet session between an X terminal and the OPC (Procedure 3-3)
— Manage an NCD19 configuration (Procedure 3-4, Procedure 3-5, and Procedure 3-6)
— Reconfigure the X terminals after an OPC upgrade (Procedure 3-7)

vi About this document
High level procedure introduction

This document contains high level procedure introductions that provide
information necessary for a qualified user to perform a procedure. You can find
an overview of the requirements, the main procedure tasks, and the expected
results on a single page. The step numbers in parentheses provide hypertext
links to specific procedure steps in the complete procedure.
Some detailed procedures can include warning, caution, or danger messages

imbedded between detailed steps. You can find precautionary message icons
included next to specific steps in the high level introduction. To read the full
precautionary message in the complete procedure, look for the equivalent step
as indicated in parentheses after the procedure task.
Example of a high level procedure introduction
Before you start

• Log on to the network element user interface (NE UI).
Procedure tasks
• Access the main menu of the NE UI with admin or read/write privileges (step 1).
• Put the associated facility OOS if you are taking a CPG OOS (step 4).
• Put the corresponding output facility OOS if you are taking the protection ESI CPG OOS (step 10).
• Put the protection ESI CPG OOS (step 14).
• Put the output facility for the working ESI CPG OOS (step 18).
• Set the target filter mode to freerun if you are taking the working ESI CPG OOS (step 20).
Expected results
• The primary state of the CPG changes.
• If the expected results do not occur:
— Perform the procedure again.
— Contact your next level of support.
1-1
External communications ports 1-

The external communications ports on the network element are as follows:
• two RS-232 ports for VT100 connectivity, one on the faceplate of the
maintenance interface (MI) circuit pack and one on the local craft access
panel (LCAP)
• two data communications channel (DCC) ports, identified SCC3 and
SCC4, for serial communications. Ports are on each of the optical port
circuit packs. The circuit packs are as follows:
— STM-64 transport interface
— STM-16 tributary interface
— STM-4 tributary interface (for TN-64X bay only)
— Quad STM-1 tributary interface (for TN-64X bay only)
— Quad STM-4
• three Ethernet ports on the MI faceplate for connections between network
elements
• 32 parallel telemetry inputs and eight parallel telemetry outputs, located on
the parallel telemetry circuit pack
You can configure the RS-232 ports and Ethernet ports on the MI circuit pack
through the network element user interface (NE UI). You can configure the
RS-232 port on the LCAP circuit pack through the NE UI. The DCC ports and
the Ethernet ports can be enabled or disabled through the NE UI. You can not
set or modify configuration parameters for these ports. You require admin
privileges to enable or disable these ports.
For details on provisioning OPTera Connect DX network elements, refer to

Part 1 of Provisioning and Operations Procedures, 323-1531-310. For details
on provisioning TN64X Release 3 network elements, refer to Part 1 of
Provisioning and Operations Procedures, 323-1551-310.
You can enable or disable the parallel telemetry inputs through the NE UI, and
you can edit some of the parameters. Through the NE UI, you can enable or
disable, and manually operate or release the parallel telemetry outputs.

1-2 External communications ports
2-1
Configuring OPC ports 2-

This chapter describes how to reconfigure the serial port on a three circuit pack
(partitioned) OPC. The serial port supports the following type of connections:
• point-to-point link (PPL), also known as serial line Internet protocol
(SLIP)
• VT100-type terminal
• printers
The default configuration of the OPC serial port is for a VT100-compatible
terminal.
For a description of the Port Configuration tool, refer to OPC User Interface
Description, 323-1511-196.

2-2 Configuring OPC ports
Figure 2-1
Port locations on the partitioned OPC Interface circuit pack
F3837-192_R21
X25
X25
SERIAL
Serial
ETHERNET
Ethernet
FW-3187
Chapter procedure list

Table 2-1 lists the procedures that are available in this chapter. Perform these
procedures to configure and modify external communications ports from the
OPC.
Table 2-1
Configuring and modifying OPC ports procedure list
Action Details
Configuring an OPC port to support terminal operation Procedure 2-1
Configuring an OPC port to support TCP/IP applications using Procedure 2-2

PPL (SLIP)
Configuring an OPC port to support printer operation Procedure 2-3
Unconfiguring an OPC port Procedure 2-4
Connecting the cable Procedure 2-5
Configuring a modem for PPL (SLIP) Procedure 2-6

Task-specific groupings
Use the procedures in each of the following tables to complete a specific task.
Perform these procedures in the order that each table lists the tasks.
Configure an OPC port for printing

Table 2-2 lists the procedures necessary to configure an OPC port to support
printer operations.
Table 2-2
Configure an OPC port for printer support
Action Details
Configuring an OPC port to support printer operation Procedure 2-3
Configuring the printer (see printer

documentation)
Configure an OPC port for VT100-type terminal access

Table 2-3 lists the procedures necessary to configure an OPC port for
VT100-type terminal access.
Table 2-3
Configure an OPC port for terminal support
Action Details
Configuring an OPC port to support terminal operation Procedure 2-1
Configure the OPC for TCP/IP using PPL (SLIP)

Table 2-4 lists the procedures necessary to configure the OPC for TCP/IP using
PPL (SLIP).
Table 2-4
Configure the OPC port for TCP/IP using PPL (SLIP)
Action Details
Configuring an OPC port to support TCP/IP applications Procedure 2-2

using PPL (SLIP)
Configuring a modem for PPL (SLIP) Procedure 2-6
Procedure 2-1
Configuring an OPC port to support terminal
operation
Use this procedure to configure the OPC serial port to support terminal
operation.
The values you define in this procedure are permanent, unless you use this
procedure to change the values again. The software saves these values during
a kernel upgrade.
Note: To allow communication with the OPC, make sure that you set the
terminal configuration parameters as follows: character length = 8 bits,
parity = none.
Before you start

• Make sure you have a user account and password, such as root or admin, that has Port Configuration
tool access.
Procedure tasks
•Configure an OPC port for terminal (step 6 to step 8).
Expected results
• A message appears indicating that the terminal baud rate configuration is successful.
—continued—

Procedure 2-1 (continued)

Configuring an OPC port to support terminal operation
Action
Step Action
1 Continue with the current config_port session. If a config_port session is not

running, you must start one.
If you are Then go to

starting a config_port session step 2
continuing from another procedure step 5
2 Log in to the OPC from a network element or open a telnet session.

To log in from a network element, refer to the procedure in User Interface
Connection Procedures, 323-1501-301. To log in by a telnet session, see
Procedure 3-3, “Establishing a telnet session between an X terminal and the
OPC”.
If you are logging in as Then

root the UNIX prompt “opc>” appears;
go to step 3
admin (or other UserID with the User Session Manager appears;
Port Configuration access) go to step 4
3 Start the Port Configuration tool by entering:

config_port ↵
The Port Configuration main menu appears.
CONFIG_PORT V2.00
************************************
* Port Configuration Main Menu *
************************************
1 Query Configuration
2 Configure a service
3 Unconfigure a service
4 View config_port_log file
10 Exit
Enter the number for your selection:

Go to step 5.
—continued—

Step Action
4 To start the Port Configuration tool, move to the Port Configuration tool in the
Available tools list. To select the tool, press Ctrl_A (or Keypad 0).
CONFIG_PORT V2.00
************************************
************************************
10 Exit

5 Display the Configure a service menu by entering:
2↵
The Configure a service menu appears.
1 Terminal
2 Printer
3 X.25
4 X.3 PAD
5 PPL
6 TCP/IP over X.25
9 Return to Main menu
10 Exit

—continued—


Step Action
6 Configure a terminal by entering:

1↵
The following menu appears:
Baud Rate:
1 9600 baud
2 19200 baud
9 Return to Configure Menu
10 Exit

7 To select a baud rate, enter its matching menu number and press the Return
key.
If you are configuring the terminal, a message indicates that the tool is
configuring your request. The message prompts you to enter either yes or no
to continue.
If you are changing an existing baud rate, the following message appears:
The terminal baud rate is changing to <xxxxx>
Do you wish to continue (yes/no):
8 Confirm the change by entering:
y↵
The following message appears:
Search ttyd1
Terminal baud rate configuration successful on the Serial
Port (xxxxx baud)
1 Terminal
2 Printer
3 X.25
4 X.3 PAD
5 PPL
6 TCP/IP over X.25
10 Exit

9 Return to the Port Configuration main menu by entering:
9↵
—continued—

Step Action
10 Select an operation.
If you must Then go to

configure this port to support PPL (SLIP) Procedure 2-2
exit step 11
Note: If you must configure a port for printer operation, you must unconfigure
the currently configured terminal service on that port. You can configure one
service at a time on a specified port.
11 Exit by entering:
10 ↵
The Port Configuration tool closes. If you are a root user, the “opc>” prompt
appears. If you are an admin user, the User Session Manager appears.
—end—

Procedure 2-2
Configuring an OPC port to support TCP/IP
applications using PPL (SLIP)
Use this procedure to configure an OPC port to establish a point-to-point link
(PPL) between an OPC and a remote workstation. Another name for the PPL
is serial line Internet protocol (SLIP) connection. When you establish this
communication link, you can perform electronic software delivery (ESWD)
operations and issue any transmission control protocol/Internet protocol
(TCP/IP) command, such as telnet or FTP, to either the OPC or the remote
workstation. Both the OPC and the remote workstation can start or receive the
connection request over the modem link.
Note: Complete this procedure before you perform the ESWD transfer
operation. Refer to Software Administration Procedures, 323-1511-303,
for more details on electronic software delivery. (You can perform
electronic software delivery if the Ethernet port is enabled.)
For the PPL configuration to be successful, you must consider the following
details and setup options:
• modem selection and setup
• cables and connectors
• network administration (hostnames and IP addresses)
• OPC port selection
Modem
This procedure recommends that you use a 19200 or 9600 baud modem with
the AT command set. You must program the modem correctly, as described in
Procedure 2-6, “Configuring a modem for PPL (SLIP)”. Connect a VT100
terminal directly into the modem and issue the different setup commands as
listed. (You can use a personal computer with a terminal program to program
the modem.) Set the modem dip switches if the switches are present. The
procedures in this document are for a Microcom QX modem. If you are using
a different modem, determine the equivalent configuration for the specified
modem.
Cabling
Most problems you find during the setup of a PPL connection are related to
cabling. For successful configuration, see Procedure 2-5, “Connecting the
cable” and make sure that you use the correct cable.
—continued—

Configuring an OPC port to support TCP/IP applications using PPL (SLIP)
Network administration
Use PPL to provide a communication channel between an OPC and a
workstation through which you can run TC/IP applications. For the
configuration to be valid, you must define a hostname and an IP address for
both the OPC and the workstation. For the PPL link to function correctly, all
hostnames and IP addresses must be unique in the network. Contact your
network administrator to receive unique hostnames and IP addresses for the
PPL connection. Do not use an existing hostname and IP address for the OPC
and workstation. You must define different names and addresses.
OPC ports
The OPC serial port supports the PPL connection.
Values defined in this procedure are permanent unless you change these values
again using this procedure. The OPC saves these values during a kernel
upgrade.
Before you start

• Make sure you have a user account and password, such as root or admin, that have Port Configuration
tool access.
• Make sure that you configure one port for terminal operation. To configure one port for terminal
operation, see Procedure 2-1, “Configuring an OPC port to support terminal operation” in this chapter.
Procedure tasks
• View PPL parameters (step 12).
• Delete a PPL host (step 18).
• Define parameters for a new host (step 22).
• Modify parameters for an existing host (step 23).
• Enable PPL login for Dial-in (step 33).
• Enable PPL dial-out and begin a dial-out session with the remote host (step 37).
Expected results
• A message confirms that PPL dial-in has been enabled.
• A message confirms that PPL dial-out has been enabled.
— Check the assigned PPL values.
—continued—


Action
Step Action
1 Continue with the current config_port session. If you have not started a
config_port session, you must start a session.

2 Log in to the OPC from a network element or by a telnet session.

OPC”.

go to step 3
admin (or other UserID with Port the User Session Manager appears;
Configuration access) go to step 4

config_port ↵
CONFIG_PORT V2.00
************************************
************************************
10 Exit

Go to step 5.
—continued—

Step Action
CONFIG_PORT V2.00
************************************
************************************
10 Exit

5 Query the existing port configurations by entering:
1↵
A list of the current port configurations appears.
6 Check that the configuration for the serial port is terminal operation.
If the serial port is Then go to

configured for terminal operation step 7
not configured for terminal operation Procedure 2-1
7 Press the Return key to return to the Port Configuration main menu.
2↵
Configure a service:
1 Terminal
2 Printer
3 X.25
4 X.3 PAD
5 PPL
6 TCP/IP over X.25
10 Exit

—continued—


Step Action
9 Attach the modem to the port configured for terminal operation (serial port)
with a cable described in Procedure 2-5, “Connecting the cable”.
Preconfigure the modem for 9600 baud. Make sure the modem can use the
AT command set. See Procedure 2-6, “Configuring a modem for PPL (SLIP)”,
for more details.
10 Configure PPL (SLIP) by entering:
5↵
The Configure PPL support menu appears.
Configure PPL support:
1 View parameters
2 Modify parameters
3 Enable PPL login
4 Enable and Dial-out to PPL host
9 Return to Configure menu
10 Exit

11 Select your next step.

view parameters step 12
delete a PPL host step 15
modify parameters for a new host step 20
modify parameters for an existing host step 22
enable PPL login step 32
enable PPL dial-out and begin a dial-out session step 37
exit step 42
—continued—

Step Action
12 View parameters by entering:

1↵
If you have not defined the PPL parameters, the following message appears.
No PPL hosts defined.
Press Return to continue.
If you have defined the PPL parameters, the parameters appear as shown in
the following example.
Remote Host Local Host Type Phone Number Baud Rate

1)wsslip opcslip DIALIN #555-1212 19200
Press Return to continue:

Note: The entries shown in the preceding example are for illustration
purposes only. The actual entries that appear depend on what you defined
previously.
13 Press the Return key to continue.
The Configure PPL Support menu appears.
1 View parameters
2 Modify parameters
3 Enable PPL login
10 Exit


delete a PPL host step 15
modify parameters for a new host step 20
modify parameters for an existing host step 22
enable PPL login step 32
enable PPL dial-out and begin a dial-out session step 37
exit step 42
—continued—


Step Action
15 To delete a PPL host, enter the following command from the Configure PPL
support menu:
2↵
The Modify PPL Configuration menu appears:
Modify PPL Configuration:
1 Add a new PPL host
2 Modify an existing PPL host
3 Delete a PPL host
9 Return to previous menu
10 Exit

16 From the Modify PPL Configuration menu, enter:
3↵
A message such as the following appears:
Delete PPL host entry:
Remove Host Local Host Type Phone Number Baud Rate
1) col opcC01 DIALIN & 555-5555 19200
DIALOUT
2) other opcC01 DIRECT 9600
Enter the remote host to delete:

17 Enter the remote host you must delete, for example, enter:
1↵
The following entry will be deleted:
1) col opcC01 DIALIN & 555-5555 19200
DIALOUT
18 Delete the PPL host by entering:
y↵
Delete PPL host entry:
1) col opcC01 DIALIN & 555-5555 19200
DIALOUT
Enter the remote host to delete:
—continued—

Step Action

If you must Then
delete another PPL host go to step 17
return to the Configure PPL Support menu press the Return key,
then enter 8 ↵
go to step 14
20 To modify parameters for a new host, enter the following command from the
Configure PPL support menu:
2↵
The following message and the Modify PPL Configuration menu appear.
3 Delete a PPL host
10 Exit

21 Add a new PPL host by entering:
1↵
The Add a PPL host screen appears. The parameters appear in turn. For
each parameter, enter the value and press the Return key. The next
parameter appears. If a value appears in brackets following the parameter
name, select this value by pressing the Return key without entering anything
else.
Enter the PPL values below:
Enter remote hostname []:

Enter remote SLIP address []:
Enter local hostname []:
Enter local SLIP address []:
Enter network mask []:
—continued—


Step Action
A list of the possible connection types appears. A message prompts you to

select a connection type.
The current type is []
The possible connection types are:
1 DIALIN
2 DIALOUT
3 DIALIN & DIALOUT
4 DIRECT
Enter connection type:
Go to step 25.
22 To modify parameters for an existing host, enter the following command from
the Configure PPL Support menu:
2↵
A list of the current entries followed by the Modify PPL Configuration menu
appear as shown in the following example.
The following hosts have been defined:


3 Delete a PPL host
10 Exit

23 Modify an existing PPL host by entering:
2↵
A list of the currently defined hosts appears. A message prompts you to select
the PPL host that you must modify.
The following hosts have been defined:

Enter remote host to modify []:

—continued—

Step Action
24 Enter the number of the PPL host that requires modification and press the
Return key.
The Modify PPL host entry screen appears. The parameters appear in turn.
For each parameter, enter the value and press the Return key. The next
parameter appears. The currently defined value appears in brackets after the
parameter name; Press the Return key to select this value.
Enter the PPL values below:
Enter remote hostname [wsslip]:

Enter remote SLIP address [xx.xx.xx.xx]:
Enter local hostname [opcslip]:
Enter local SLIP address [xx.xx.xx.xx]:
Enter network mask [xx.xx.xx.xx]:
A list of the possible connection types appears. A message prompts you to
select a connection type.
Note: The parameter values in these steps are examples. The actual values
that appear depend on what you configure earlier on your system.
The current type is [DIALIN]
The possible connection types are
1 DIALIN
2 DIALOUT
3 DIALIN & DIALOUT
4 DIRECT
Enter connection type (1):
25 Enter the connection type and press the Return key. If an entry appears in
brackets, you can select that entry and then press the Return key.
If the connection type is Then
Dialout enter the phone number of the
remote site, press the Return key,
and continue with this step.
different from Dialout continue with this step
A message prompts you to enter the baud rate.

Enter the baud rate: [ ]
—continued—


Step Action
26 Enter the baud rate 9600 or 19200.

The configuration parameters appear and a message prompts you to confirm
the data.
If Then go to
the data is correct step 28
the data is wrong step 29
you do not want to save the changes step 30
28 Confirm that the data is correct by entering:

y↵
A confirmation message appears.
Go to step 31.
29 Confirm that the data is incorrect by entering:
n↵
The Modify PPL host entry screen appears, allowing you to correct the
values.
Go to step 24.
30 End the modification session without saving any changes by entering:
q↵
The Modify PPL Configuration menu appears. The PPL configuration
remains unchanged.
31 Return to the Configure PPL Support menu by entering:
9↵
1 View parameters
2 Modify parameters
3 Enable PPL login
10 Exit
—continued—

Step Action
32 To enable the PPL login, select your next step.

If the host is Then go to
Dial-in step 33
Dial-out step 37
33 Enable PPL login for Dial-in by entering:

3↵
Enter the port number after the prompt.
Enable PPL login:
The following have been defined for DIALIN:

Which host is allowed to login []:

Note: The host listed in this step is an example. The actual host that appears
depends on the configuration parameters that you enter in your system.
34 Type the number of the host you must enable. In this example, enter:
1↵
A message appears:
The Port will be reconfigured to 19200 baud.
Do you want to continue y/n (n):
35 Continue by entering:
y↵
The following prompts appear:
search ttyd1
Terminal baud rate configuration successful on the Serial
Port (19200 baud)
Please choose a new password for the PPL user:
New password:
—continued—


Step Action
36 Enter the password (no longer than eight characters) the remote terminal
user must use to log in to the OPC and press the Return key. To confirm the
password, enter the password again and press the Return key.
A message confirms that PPL dial-in has been enabled.
Done. PPL login has been enabled.
Ensure a modem that has been configured for dial-in is

attached to port x
The Configure PPL support menu appears again.
1 View parameters
2 Modify parameters
3 Enable PPL login
10 Exit

Go to step 14
37 Before you enable PPL dial-out and begin a dial-out session with the remote
host, read the following notes:
Note 1: Enable a dial-out session when you must access a remote terminal
to have PPL software delivered.
Note 2: If you enabled PPL dial-out earlier on the serial port, disable PPL
dial-out before you log in using a terminal on the serial port. If you try to log
in using a terminal on the serial port, the following message appears:
Login using a terminal on the Serial Port will not be
possible until PPL dialout is disabled using config_port.
Ensure a modem that has been configured for dialout is
attached to the Serial Port.
—continued—

Step Action
38 Enable PPL dial-out and begin a dial-out session with the remote host by
entering:
4↵
A message prompts you to select a port number and a dial-out host.
Enter the port number after the port number prompt.
Dial-out to PPL host:
The following hosts have been defined for DIALOUT:

1)wsslip opcslip DIALOUT #
Dial-out to which host ():

Note: The host listed in this example is an example. The actual host that
appears depends on the configuration parameters that you enter in your
system.
39 Enter the number of the remote host you must enable.
The equipment establishes a SLIP connection with the specified host.
You can start electronic software delivery using the electronic software
delivery procedures in Software Administration Procedures, 323-1501-303.
Dialing ...
Done. SLIP CONNECTION ESTABLISHED.

40 Return to the Configure a Service menu by entering:
9↵
The Configure a Service menu appears.
Configure a service:
1 Terminal
2 Printer
3 X.25
4 X.3 PAD
5 PPL
6 TCP/IP over X.25
10 Exit

—continued—


Step Action

9↵
Note: If you must configure a port for printer or terminal operation,
unconfigure the service that you configured earlier on that port. You can
configure only one service at a time on a specified port.
42 Exit the tool by entering:
10 ↵
—end—
Procedure 2-3
Configuring an OPC port to support printer operation
Use this procedure to configure the OPC serial port to support printer
operation.
The values you define in this procedure are permanent unless you use this
procedure to change them again. The software saves the values during a kernel
upgrade.
Before you start

tool access.
• Make sure you have a printer with an RS-232 interface which can print the complete ASCII character set.
• Read the material entitled “Printer and port configuration parameters” at the beginning of this procedure.
Procedure tasks
• Configure an OPC port for printer (step 7 to step 12).
Expected results
• A message indicates that the printer configuration is successful.
• A message indicates that the printer is now enabled
—continued—


Printer and port configuration parameters

You must define two parameters when you configure a port to support a
printer. Make sure that the values supplied are compatible with the capabilities
of the selected printer and its settings.
Baud rate
Baud rate is the speed at which the OPC transmits characters between the OPC
and the printer. The operating manual for that printer defines the speed at
which a printer can accept characters. Select a value from the possible port
configuration values which includes 300, 1200, 2400, 4800, 9600, or 19200.
To define this value, see Procedure 2-3, “Configuring an OPC port to support
printer operation”, in this document.
Mode
Mode indicates the flow control method used. The serial interface section of
the printer operating manual defines this capability.
If the printer supports hardware flow control using DTR and CTS signals, then
set the mode to “simple”. If the printer supports software flow control using
the XON/XOFF protocol, set the mode to “direct”. Refer to your printer
manual for details.
Printer configuration
Use the following printer configuration in Table 2-5 to communication with
the OPC, regardless of baud rate and mode:
Table 2-5
Printer configuration
Interface: RS-232 serial

Character length: 8 bits
Parity: one
Character set: Standard ASCII
—continued—

If the printer fails to operate

When you complete the port and printer configuration procedures and the
printer does not print, perform the following steps:
• plug in the printer and turn on the power switch
• connect the cable between the OPC and the printer
• enable the printer. Repeat this procedure and verify that the following
message appears after step 12
Printer is now enabled.
If the printer drops characters

If the printer is not printing characters, there is a flow control problem. To
prevent a flow control problem, perform the following steps:
• enable the flow control on your printer and make sure that the flow control
matches the mode parameter
• reduce the baud rate of the port (see step 8 in the following procedure)
• select draft print quality on your printer
—continued—


Action
Step Action
1 Continue with the current config_port session. If a config_port session is not

running, you must start one.

2 Log in to the OPC from a network element or by telnet session.

To log in from a network element, refer to the following procedures:
• the procedure in User Interface Connection Procedures, 323-1511-301
• Procedure 3-3, “Establishing a telnet session between an X terminal and
the OPC”, in this document (to log in by telnet session)

go to step 3

config_port ↵
CONFIG_PORT V2.00
************************************
************************************
10 Exit

Go to step 5.
—continued—

Step Action
Available tools list. Select the tool by pressing Ctrl_A (or Keypad 0).
CONFIG_PORT V2.00
************************************
************************************
10 Exit

2↵
1 Terminal
2 Printer
3 X.25
4 X.3 PAD
5 PPL
6 TCP/IP over X.25
10 Exit

6 Display the Printer options by entering:
2↵
The Printer menu appears.
1 Configure Printer
2 Enable Printer
10 Exit

—continued—


Step Action
7 Select the Configure Printer option by entering:

1↵
The Baud Rate menu appears:
Baud Rate:
1 300 baud
2 1200 baud
3 2400 baud
4 4800 baud
5 9600 baud
6 19200 baud
9 Return to Configure Menu
10 Exit

8 To select a baud rate, enter its matching menu number and press the Return
key.
The Printer mode menu appears.
Printer mode:
1 Simple
2 Direct
10 Exit

9 To select a printer mode, enter its matching menu number and press the
Return key.
The following message appears.
Configuration on the Serial Port is changing from
Terminal to Printer
Warning: Terminal operation is being removed from the
Serial Port
Do you wish to continue? (yes/no):
—continued—

Step Action
10 Confirm the change by entering:

y↵
The following messages appear.
Terminal operation has been removed from the Serial Port
Remove the terminal cable and insert the appropriate
printer cable
Press RETURN when you are done
PRINTER operation <xx baud, xx mode> is being configured
on the Serial Port
11 Confirm the configuration change by entering:
y↵
The following message appears followed by the configure printer menu.
Printer configuration successful on Port <x> <baud rate>
<mode>
1 Configure printer
2 Enable printer
10 Exit

12 Enable the printer by entering:
2↵
The following message appears followed by the configure printer menu.
Printer is now enabled.
1 Configure printer
2 Enable printer
10 Exit

—continued—


Step Action
13 Return to the Configure a service menu by entering:

9↵
1 Terminal
2 Printer
3 X.25
4 X.3 PAD
5 PPL
6 TCP/IP over X.25
10 Exit

9↵
Note: If you must configure a port for terminal operation, or a PPL connection
(SLIP), unconfigure the currently configured printer service on port <x>. OPC
port <x> is the only port that supports terminal operation, printer operation,
and a PPL connection. You can configure one service at a time on a specified
port.
15 Exit by entering:
10 ↵
—end—
Procedure 2-4
Unconfiguring an OPC port
Use this procedure to unconfigure any OPC service. For example, you can use
this procedure to remove a service from a port.
Note: You cannot change the configuration of the port used to log in.
Before you start

tool access.
Procedure tasks
• Unconfigure a service (step 6 to step 8).
Expected results
• A message confirms the removal of the service from a port.
—continued—


Action
Step Action
1 Log in to the OPC from a network element or through a telnet session.

OPC”

go to step 2

config_port ↵
CONFIG_PORT V2.00
************************************
************************************
10 Exit

Go to step 4.
—continued—

Step Action
CONFIG_PORT V2.00
************************************
************************************
10 Exit

4 Query the current OPC port configurations by entering:
1↵
The port configurations list appears.
5 Record the port configurations and press the Return key to display the main
menu.
6 Display the Unconfigure a service menu by entering:
3↵
The Unconfigure a service menu appears.
The tool customizes the menu for the services you configure. In this example,
you configure the serial port for terminal, and port X25 for X.25, supporting
X.3 PAD and TCP/IP over X.25.
Unconfigure a service:
1 terminal service on the SERIAL Port
2 X.25 on the X25 Port
3 X.3 PAD
5 TCP/IP over X.25
10 Exit

—continued—


Step Action
7 Enter the required menu item number and press the Return key.
Note: You must unconfigure PPL services before you can unconfigure
terminal operation.
The following message appears.
Do you wish to continue (Yes/No):
8 Confirm the unconfiguration of the service by entering:
y↵
The system confirms the removal of the service.
The Unconfigure a service menu appears after a short period of time.
9 Repeat step 7 for each service you must unconfigure.
10 Exit the Port Configuration tool by entering:
10 ↵
—end—
Procedure 2-5
Connecting the cable
Use this procedure to connect cables between the OPC serial port and the
communications modem, printer, or terminal.
To identify the cables for TN-64X Release 3 used between the OPC ports and
the communications modem, printer or terminal, refer to Installation
Procedures, 323-1551-201. To identify the cables for OPTera Connect DX
used between the OPC ports and the communications modem, printer or
terminal, refer to Installation Procedures, 323-1531-201.
Before you start

• Complete the required procedures listed in Table 2-1, “Configuring and modifying OPC ports procedure
list” for the device you connect to the OPC.
• Make sure you have the appropriate cable.
Procedure tasks
• Connect a cable between the port of a partitioned OPC to a device (step 1 to step 3).
Expected results
• You correctly connect a cable between the port of a partitioned OPC to a device.
— Make sure you used the correct cable
— Make sure that the connections are secure.
— Make sure the external equipment is in working condition.
—continued—


Connecting the cable
Action
Step Action
1 Connect the 25-pin end of the cable to the serial port.

2 Connect the other end of the cable to the modem, printer or terminal.
3 Make sure that the connections are secure.
—end—
Procedure 2-6
Configuring a modem for PPL (SLIP)
Use this procedure to configure and connect a Microcom QX communications
modem to an OPC and HP workstation. Use the PPL (SLIP) connection for
electronic software delivery (ESWD). If you use a modem different from a
Microcom QX communications modem, refer to the documentation of the
modem for the DIP switch settings.
Before you start

• Make sure you have a 9600, 19200, or higher baud modem.
• Make sure you have a telephone line for a modem.
• Make sure you have a modem-to-serial port cable for your workstation.
• Have access to a workstation.
Procedure tasks
• Configure a modem for PPL (SLIP) (step 1, step 2, and step 4 or step 5).
• Connect a modem to an OPC (step 7).
• Connect a modem to an HP700 (step 8).
Expected results
• You configure the modem for PPL (SLIP).
— Check DIP switch settings.
— Check your connections.
—continued—


Action
Step Action
1 Remove the front faceplate of the modem and set the front DIP switches
according to the following table:
Switch Position Description
1 Up DTR on, mode 2
2,3 Down, Up AT command mode
4 Up Echo on
5 Up Auto answer on
6,7 Up, Up CD, DTR on
8 Down Smart mode
9 Up or Down Not connected
10 Up Asynchronous mode
Note: Switch 9 is not connected. Do not set switch 9.

2 Set the back DIP switches of the modem according to the following table:
Switch Position Description
1,2 Up, Up no hardware flow control
3,4 Down, Up auto-reliable
5 Down MNP result codes
6 Up use software configuration
7 Up do not read switch configuration
8 Down BPS adjust off
3 Determine which modem configuration you require.
If you must configure the modem for Then go to

PPL Dial-in step 5
PPL Dial-out step 4
—continued—

Step Action
4 Connect a VT100 terminal to the modem and issue the AT commands in the
order listed in the following table:
Command Description
AT&F ↵ return to factory settings
AT\G1 ↵ software flow control
AT\N3 ↵ auto-reliable mode
AT\J0 ↵ BPS adjust off
AT\Q0 ↵ hardware flow control off
AT&D2 ↵ DTR on, mode 2
AT&C1 ↵ CD on, mode 1
ATQ0 ↵ quiet mode off
AT&W ↵ save configuration
Note: Set the dial-out modem front panel switch to originate mode.
Go to step 6.
—continued—


Step Action
5 Connect a VT100 terminal to the modem and issue the following AT

commands in the order listed in the table below:
Command Description
AT&F ↵ return to factory settings
AT\G1 ↵ software flow control
AT\N3 ↵ auto-reliable mode
AT\J0 ↵ BPS adjust off
AT\Q0 ↵ hardware flow control off
AT&D2 ↵ DTR on, mode 2
AT&C1 ↵ CD on, mode 1
ATS0=1 ↵ answer mode on
ATQ1 ↵ quiet mode on
AT&W ↵ save configuration
Note 1: Set the dial-in modem front panel switch to answer mode, if used on
leased lines.
Note 2: When you issue the ATQ1 command, the modem still accepts
commands, but no longer responds with OK, or other result codes.
6 Select the terminal designation to which you are connecting the modem.
If you are connecting to Then go to

the OPC step 7
HP700 step 8
—continued—

Step Action
7 Wire the modem-to-OPC serial port (OPC Interface circuit pack) cable
according to the following table.
Note: The cable must have a DB-9M connector for the OPC serial port (DTE)
end and a DB-25M connector for the modem (DCE) end.
OPC serial port OPC serial port Modem Pin

Signal Pin Assignment Assignment
DCD 1 8
Rx 2 3
Tx 3 2
DTR 4 20
GND 5 7
DSR 6 6
RTS 7 (see Note) 4
CTS 8 (see Note) 5
n/c 9
Note: Connect Pins 7 and 8 together on the OPC serial port instead of
wiring to modem pins 4 and 5 if you do not require hardware flow control.
The modem-to-OPC cable connection is complete.

—continued—


Step Action
8 Wire the modem-to-HP700 cable according to the following table.

Note: The cable must have a DB-9M connector for the HP700 (DTE) end and
a DB-25M connector for the modem (DCE) end.
HP700 Signal HP700 Pin Assignment Modem Pin Assignment
DCD 1 8
Rx 2 3
Tx 3 2
GND 5 7
DTR 4 20
DSR 6 6
RTS 7 (see Note) 4
CTS 8 (see Note) 5
RI 9 22
Note: Connect Pins 7 and 8 together on the HP700 instead of wiring to

modem pins 4 and 5 if you do not require hardware flow control.
—end—
3-1
Managing X terminals for the OPC 3-

This chapter describes how to establish communications between the
operations controller (OPC) and an X terminal, a local area network (LAN), or
Nortel Networks’ Preside Network management system. This chapter
describes the hardware specifications and software setup requirements for X
terminals supported by the OPC. This chapter contains procedures to connect
X terminals to the OPC, and to configure the OPC for X terminal
communications.
Note: For information about the OPC graphical user interface for X
terminals, and the OPC tools available through this interface, refer to OPC
User Interface Description, 323-1511-196.
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 log in banner which
appears on the X terminal displays. The user provides log in information
through this log in banner and the XDM starts the session if the log in
information is correct. The XDM also handles session termination.

3-2 Managing X terminals for the OPC
X terminal support
The X terminals supported by the OPC are as follows:
• models NCD19 and NCD19R
This document uses the term NCD19 for both the NCD19 and the
NCD19R. These models are produced by Network Computing Devices of
Mountain View, California.
• model 700/RX
Hewlett-Packard produces this model.
• model XP18
Tektronix produces this model.
For administrators who are free to select any of the three terminals, Nortel
Networks recommends the NCD19. It is possible that there are other
X terminal models, different from those listed above, that you can use to
connect to the OPC.
The OPC automatically provides the OPC font path to these terminals and
keyboard mapping. Keyboard mapping for unsupported terminals is not
guaranteed.
If the OPC log in banner (shown below) appears after a reboot of an X terminal
connected to the appropriate OPC port, the OPC automatically provides the
OPC font path to the X terminal. For this to happen, you must be able to
remotely change the X terminal font path from a host.
F21160
FW-21160
FIBER WORLD
This software contains material which is
confidential to Nortel Networks Corporation
and is made available solely pursuant to
the terms of a written license agreement
with Nortel Networks Corporation.
(c) 1989 - 1999 Nortel Networks Corporation
User ID:
Password:
Done Alt+Return
X terminal equipment recommendations

This section includes general recommendations that apply to all X terminals,
and recommendations that are specific to each X terminal model.
General recommendations
Several recommendations apply to all X terminals:
• To connect with the OPC, the X Server software must be running with at
least X version 11 Release 4 (X11 R4).
• Configure X terminals connected to the OPC directly, or through a hub on
a LAN with a twisted-pair communication port (the IEEE 802.3 10BaseT
interface). The physical port is an RJ45 connector.
• X terminals must have local X server communications software as the OPC
does not support downloading of X server communications software. This
software is available from the vendor in the form of an X server
programmable read only memory (PROM) or an X server flash read only
memory (ROM). If the vendor does not provide local communications
software, the X terminal(s) must have a network server to provide the
software. To set up the X terminal, you must identify the server.
Note: The equipment lists that follow are subject to vendor-initiated
changes that are beyond the control of Nortel Networks. 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
Order the NCD19 model as follows:
• NCD19R model
• 19-in monochrome monitor
• X server PROM
• 8 megabytes of random access memory (RAM)
• N-101 keyboard
Hewlett-Packard equipment
Order the 700/RX model 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
Order the XP18 model 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 X terminal parameter values in order for the terminals to
operate. The parameters listed here represent only those required for
connection to the OPC. Consider other operating environment characteristics,
such as router types and LAN configurations 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 use.
IP addresses and node names

You can assign both the Internet Protocol (IP) address and the node name
according to your network requirements. You must consider two restrictions:
• all addresses and names must be unique within the network
• if the local network connects to an external network, the IP address must
conform to Internet Assigned Numbers Authority (IANA) standards to
ensure that the IP addresses are unique.
Make sure you have the IP addresses and node names from the
communications planning department in your organization. If your planning
department does not have IP addresses and node names, get the addresses and
names directly from IANA.
General setup requirements

To perform operations using the OPC, you must set up several parameters on
all X terminals:
• for an X terminal used in another application, reset the terminal to its
factory defaults before you set 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 trivial file transfer
protocol (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 terminal loses the XDMCP enable
flag and the IP address of the OPC. To compensate for this, the OPC provides
an automatic process for reestablishing these parameters on the NCD X
terminal. The process requires that you create a configuration file on the OPC
for each NCD X terminal. There are instructions later in this chapter for
adding, changing, or deleting entries in the configuration file.
700/RX-specific requirements
In addition to the parameters listed previously, the 700/RX has the following
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)
If the vender delivers the flash ROM for XP18 X terminals without the
X server software, get the software from a network server. Download the X
server communications software from a network server to the flash ROM. You
need to do this one time.
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.
When you define the parameters, save the parameters to nonvolatile random
access memory (NVRAM). To activate them, reboot the X terminal.
Replacing or exchanging X terminals

If you replace an X terminal, you must follow the full setup procedure for the
new terminal. This is true even if you keep the IP address the same.
LAN considerations
You must consider several issues when you connect the OPC to a LAN:
• When there is wide area network (WAN) access to the LAN, the OPC does
not distinguish between X terminals on the local LAN and those on the
WAN. If this condition presents a security issue, address the issue through
LAN and WAN administration.
• The OPC requires that any user session from an OPC starts directly from
an X terminal. Do not log in to the OPC through an X terminal session
running on an intermediate host. This is because problems with the LAN
segment between the OPC and the host, or the host and the X terminal, can
have an effect on the OPC user session. Problems with this type of setup
are beyond the control of the OPC.
• The customer is responsible for LAN configuration (for example, routers,
hubs, connectors) and correct use of LAN resources.
• Consider the impact on LAN integrity and performance that will result
when you connect X terminals to an OPC over the LAN. It is
recommended that you analyze the particular LAN because 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 identical to X clients running
from a UNIX workstation.
• The OPC does not support modem connections with X terminals over
serial lines (including access through the serial line protocol XRemote).
• At any given time, the OPC supports one user session from one OPC on an
X terminal.
Cabling options
Figure 3-1 shows the cabling options to connect the OPC (Ethernet port on the
faceplate) to X terminals, LANs, and Nortel Networks’ Preside. For
information about installing OPTera Connect DX cables, refer to Installation
Procedures, 323-1531-201. For information about installing TN64X Release
3 cables, refer to Installation Procedures, 323-1551-201. For information
about Preside network management, refer to the Preside NTP library,
450-3101-xxx.

Figure 3-1
Cabling options - OPC to network equipment
F20041-192_R30
Option A
9-pin (Ethernet) 9-pin connector

connector plugged into a MAU
MAU
Crossover
X terminal
OPC
15-pin D-type
Option B male connector

connector plugged into a MAU
MAU
Crossover
X terminal
OPC
Option C

connector plugged into a MAU LAN
MAU hub
Straight through
OPC
Cabling option A
Option A applies when there is a point-to-point connection between the OPC
Ethernet port and an X terminal that supports the recommended twisted-pair
communication port. Refer to the IEEE 802.3 10BaseT interface. Nortel
Networks’ prefabricated cables have a 9-pin male connector on one end for
connection to the OPC. The other end also has a 9-pin connector for
connection to the X terminal. If required, use an appropriate media access unit

(MAU) to interface between the 9-pin connector of the crossover cable and the
X terminal. Each cable has two shielded twisted pairs with transmit and
receive crossed over. The cables conform to FCC Class A requirements. Table
3-1 lists the length and PEC for the cables.
Table 3-1
X terminal crossover cables
Length PEC
20 m (65 ft) NTCC90CA
Cabling option B
Option B applies when there is a point-to-point connection between the OPC
Ethernet port and an X terminal that has a 15-pin D-type connector that
conforms to the IEEE 802.3 pin configuration. Nortel Networks’ prefabricated
cables have a 9-pin male connector on one end for connection to the OPC. The
other end also has a 9-pin connector for connection to the X terminal. If
required, use an appropriate media access unit (MAU) to interface between the
9-pin connector of the crossover cable and the X terminal. Each cable has two
shielded twisted pairs with transmit and receive crossed over. The cables
conform to FCC Class A requirements. Table 3-2 lists the length and PEC for
the cables.
Table 3-2
X terminal crossover cables
Length PEC
20 m (65 ft) NTCC90CA
Cabling option C
Option C applies when you connect the OPC to a LAN. The straight through
cables used to connect the OPC to the LAN hub. Table 3-3 lists the length and
PEC for the cables. If required, use an appropriate MAU to interface between
the 9-pin connector of the straight through cable and the LAN hub.
Table 3-3
LAN straight through cables
Length PEC
20 m (65 ft) NTCC90BA
40 m (130 ft) NTCC90BB

Preside Applications Platform options

Nortel Networks’ Preside is a software package designed to run on a
workstation. Refer to the workstation hardware and documentation to
determine which cabling option applies.
Note: For more information about Nortel Networks’ Preside network

management system, refer to the Preside NTP library, 450-3101-XXX.
Session-terminating conditions
The OPC sends an audit message to the X terminal every minute. The OPC
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 with pre-NCDware v.3 software and for HP 700/RX
X terminals, the terminal does not respond to OPC audit messages when in the
Setup mode. To prevent 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 movement

When you need to move a window on the display, a wire grid representation
of the window appears. Use the mouse to move the image and select the
position of the window. The actual window appears again when you select the
new location. The OPC does not respond to audit messages while you move
the wire grid representation of the window. To prevent 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 log in 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 of a connection.
The terminals wait for a response from the remote end for this predefined
period. If there is no response, the terminals stop polling the remote end. This
condition 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 from the X terminal graphical user interface that begins
call setup, it is possible to exceed the time period before the OPC responds. In
this case, the OPC log in banner never appears again. To get the OPC log in
banner to appear again in such situations, reboot the X terminal after the OPC
returns to service. Allow five to ten minutes for the OPC to reboot. If you are
rebooting the OPC from the VT100 terminal, the log in banner appears on the
X terminal as usual.
No OPC log in 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. This statement
assumes that you restore the power to both simultaneously. In this case, the
OPC log in banner does not appear again 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 can not read their remote configuration file on the OPC
while the OPC is rebooting (as is the case for the NCD19)
To get the OPC log in banner to appear again in situations, reboot the X
terminals after the OPC returns 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 failure scenarios
are as follows:
• loss of connection during an active OPC session
• unavailability of the OPC while the X terminal tries 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. Loss of connection can occur when an event
disables the Ethernet connection between the OPC and the X terminal. In this
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
During call setup, the OPC can be unavailable. Normally this event occurs
after rebooting the OPC. If the OPC is not available when the NCD19 attempts
to establish a connection, the NCD19 X terminal does not try to establish a
connection to the OPC after a specified amount of time. In this case, a window
appears with a message, as follows:
Login host not responding; choose another or try again later?
Wait until the OPC returns to service, allow approximately five minutes for the
OPC to reboot. Select the OK button on this window. The OPC log in banner
from the OPC appears.
Problems connecting over a LAN

Most problems associated with LANs arise because of LAN interconnectivity
issues that are independent of the OPC. These issues often prevent
communications with the OPC. Contact the LAN vendor since the vendor can
resolve these issues quickly.
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. If you run four X mode
user sessions on an OPC, you can not start CMT user sessions.
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.
If you run four X mode user sessions, you can run four to eight more tools over
all sessions before the OPC runs out of swap space.
If you run three X mode user sessions, you can run 10 to 14 more tools over
all sessions before the OPC runs out of swap space.
If you run X mode user sessions, you can run 16 to 20 more tools over all
sessions before the OPC runs out of swap space. This amount is over and
above the tools that the OPC starts automatically.
It is recommended that you run a maximum of one X mode user session at any
time on the OPC. One session allows you to have a sufficient amount of
available swap space, and to achieve reasonable execution and response time.
Chapter procedure list

Table 3-4 lists the procedures that you need to perform to manage X terminals
for the OPC.
Table 3-4
Managing X terminals for the OPC procedure list
Action Details
Initializing the OPC Ethernet port Procedure 3-1
Controlling the OPC Ethernet port Procedure 3-2
Connecting the OPC to network equipment

For TN64X Release 3 network elements, see Installation Procedures,
323-1551-201. For OPTera Connect DX network elements see Installation
Procedures, 323-1531-201
Establishing a telnet session between an X terminal and the Procedure 3-3

OPC
Adding, changing, or deleting an NCD19 configuration file Procedure 3-4

Table 3-4
Managing X terminals for the OPC procedure list
Action Details
Loading the NCD19 configuration data from the OPC to an Procedure 3-5
NCD19 X terminal running NCDware v.2
Loading the NCD19 configuration data from the OPC to an Procedure 3-6
NCD19 X terminal running NCDware v.3
Reconfiguring X terminals following an OPC upgrade Procedure 3-7
Task-specific grouping
Table 3-5 lists the procedures necessary to configure the OPC Ethernet port for
X terminal support. Perform the procedures, as required, in the order shown.
Table 3-5
Configure the OPC Ethernet port for X terminal support
Action Details
Initializing the OPC Ethernet port Procedure 3-1
Controlling the OPC Ethernet port Procedure 3-2
Connecting the OPC to network equipment

For TN64X Release 3 network elements, see Installation Procedures,
323-1551-201. For OPTera Connect DX network elements, see Installation
Procedures, 323-1531-201
Establishing a telnet session between an X terminal and the OPC Procedure 3-3
Adding, changing, or deleting an NCD19 configuration file Procedure 3-4
Loading the NCD19 configuration data from the OPC to an NCD19 Procedure 3-5
X terminal running NCDware v.2
Loading the NCD19 configuration data from the OPC to an NCD19 Procedure 3-6
X terminal running NCDware v.3
Procedure 3-1
Initializing the OPC Ethernet port
Use this procedure to initialize the OPC Ethernet port so that it can
communicate with an operations system, the Preside tool, or an X terminal.
Before you start

• Make sure that you correctly install and boot up the OPC module.
• Make sure you have several identifiers for the OPC:
— the node name
— the IP address
— the IP netmask
• Log in to the OPC with access privileges for the Ethernet Admin tool. For log in instructions and an
overview of the OPC user interface, see OPC User Interface Description, 323-1511-196.
The Ethernet Admin tool is a restricted tool. With the exception of the root user, only non-default UserIDs
can access restricted tools, such as those assigned to the default tech support user group. The default
tech support user group includes the Restricted Tools toolset. The system administrator can assign a
non-default UserID (see Security Management Procedures, 323-1511-305). You must access the tool as
the root user:
— if a non-default UserID does not exist
— if you do not want to use a non-default UserID
• The OPC allows you to use up to eight characters for the SYSTEM_NAME variable in the /etc/rc file.
The X terminal installation fails if you exceed this limit.
Procedure tasks
• Initialize and enable the OPC Ethernet port (step 3 to step 14).
Expected results
• Warnings and a message saying the Ethernet port configuration is complete.
— If the initialization values are wrong, discontinue initialization and complete the Ethernet port
initialization port process again.
—continued—


Action
Step Action
1 If you have logged in to the OPC as Then go to

root step 2
a non-default user step 3
2 At the UNIX shell prompt (“opc>”), start the User Session Manager by
entering:
opcui ↵
The User Session Manager appears.
3 To open the Ethernet Admin tool from the User Session Manager, move the
cursor to the tool name and press Ctrl_A (or Keypad 0).
A warning message followed by the Ethernet Admin tool appears:
1. Initialize and enable the Ethernet port
2. Ethernet port control (enable/disable)
3. X terminals configuration
4. Current Ethernet configuration
5. Help
6. Quit
Select one of the above commands [1-6]:
4 Select the Ethernet port initialization command by entering:
1↵
A message describing the port initialization requirements appears followed by
a node name prompt:
Enter the nodename:
5 Type the nodename assigned to the OPC.
The nodename is the UNIX hostname and can be up to a maximum of eight
alphanumeric characters.
Note: To determine this initialization sequence, enter abort ↵ at the
command prompt.
6 Press the Return key.
The system checks the nodename. If the nodename is not in the correct
format an error message appears, followed by another nodename prompt. If
the nodename prompt appears again, complete this step again.
When you enter an acceptable nodename, an IP address prompt appears:
Enter the IP address:
—continued—

Step Action
7 Type the unique IP address number assigned to the OPC.

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 Ethernet Admin tool checks the IP address. If the tool has reserved the
IP address, has assigned it to another OPC, or if the IP address is not in the
correct format, an error message appears, followed by another IP address
prompt. If the IP address prompt appears again, complete this step again.
When you enter an acceptable IP address, the netmask prompt appears:
Enter the netmask [default 255.255.255.0]:
9 Type the netmask number assigned to the OPC.
The default netmask value is 255.255.255.0. To accept this value, press the
Return key. If required, you can enter a new netmask number using the same
criteria as the IP address.
The Ethernet Admin tool checks the netmask. If the netmask is not in the
correct format an error message appears followed by another netmask
prompt. If the netmask prompt appears again, complete this step again.
When you enter an acceptable netmask number, the default gateway prompt
appears.
Enter the default gateway [99.205.1.93]
11 Type the default gateway address.
If you enter a default gateway address use the same format as the IP
address. If you do not enter an address, and press the Return key, the
Ethernet Admin tool assigns the OPC IP address to the default gateway
value.
—continued—


Step Action

If the default gateway is not in the correct format an error message appears
followed by another netmask prompt. If the default gateway appears again,
complete this step again.
When you enter an acceptable default gateway address, a summary of the
Ethernet port initialization values appears, followed by a request to continue
with the initialization process:
Initializing Ethernet to:
name: <OPCM001P>
address: <99.205.1.93>
netmask: <255.255.255.0>
Do you wish to continue? [yes;no]:
13 Check the initialization values in the summary and make sure that they are
correct.
continue the Ethernet port initialization step 14
discontinue the Ethernet port initialization step 15
—continued—

Step Action
14 Continue the Ethernet port initialization process by entering:

yes ↵
If this address is a new or a modified IP address, a warning 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.
Ethernet port configuration complete.
Another warning message followed by the Ethernet Admin tool appears:
5. Help
6. Quit
Select one of the above commands [1-6] :
The Ethernet Admin tool initializes and enables the Ethernet port. The OPC
is ready to communicate with the Network Manager or X terminal.
Note: As previous warning message indicates, the addition or modification
of the IP address makes the network routing table invalid. To restore the
network routing table, restart the OPC using the OPC Shutdown tool.
Go to step 16.
15 Discontinue the Ethernet port initialization process by entering:
no ↵
A warning message followed by the Ethernet port command list appears.
If you must complete the Ethernet port initialization process again, go to step
4.
16 Close the tool by entering:
5↵
—end—

Procedure 3-2
Controlling the OPC Ethernet port
Use this procedure to enable or disable the OPC Ethernet port. The OPC can
communicate with the Preside tool, an operations system, or an X terminal
when the Ethernet port is enabled.
Before you start

• Log in to the OPC with access privileges for the Ethernet Admin tool. For log in instructions and an
overview of the OPC user interface, refer to OPC User Interface Description, 323-1511-196.The Ethernet
Admin tool is a restricted tool. With the exception of the root user, only non-default UserIDs can access
restricted tools, such as those assigned to the default tech support user group. The default techsupport
user group includes the Restricted Tools toolset. The system administrator can set up a UserID (see
Security Management Procedures, 323-1511-305). You must access the tool as the root user:
• Determine if you need to initialize the Ethernet port. Use the Ethernet port control (enable/disable)
command with (IP provisioning) or without (no IP provisioning) initializing the OPC Ethernet port (see
Procedure 3-1, “Initializing the OPC Ethernet port”).
• If you enable or disable the Ethernet port before you provision the Ethernet port, you:
— impact open system interface (OSI) traffic only (turn ON/OFF communications with the operations
system or a network element if you connect either through the lan0 port)
— do not allow TCP/IP traffic to pass through the lan0 port
• If you enable or disable the Ethernet port after you provision the Ethernet port, you:
— impact OSI and TCP/IP traffic (turn ON/OFF both traffics)
— lose any communications through the lan0 port
Procedure tasks
• Enable the Ethernet port control (step 6).
• Disable the Ethernet port control (step 7 to step 9).
Expected results
• The Ethernet port is enabled or disabled.
—continued—

Action
Step Action

root step 2
2 At the UNIX shell prompt (“opc>”), open the User Session Manager by
entering:
opcui ↵
5. Help
6. Quit
4 Select the Ethernet port control command by entering:
2↵
A message that identifies the Ethernet port control values appears, 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]
5 You must enable the Ethernet port to allow the OPC to communicate with the
Preside tool, operations system, or X terminal. When you disable the
Ethernet port the OPC disconnects from the network.
enable the Ethernet port step 6
disable the Ethernet port step 7
—continued—


Step Action
6 Enable the Ethernet port by entering:

e↵
The Ethernet port is now enabled. The OPC is ready to communicate with the
Network Manager, operations system, or X terminal.
Note: If the Ethernet port is already enabled, this step has no effect.
Go to step 10.
7 Disable the Ethernet port by entering:
d↵
A warning message appears:
Warning!
Disabling the Ethernet port will cause loss of network
connectivity.
Do you wish to continue? [yes, no]:
8 If you disable the Ethernet port, the OPC can not communicate with the INM,
operations system, or X terminal.
continue and disable the port step 9
leave the port enabled and quit the procedure step 10
9 Continue and disable the Ethernet port by entering:

yes ↵
5. Help
6. Quit
The command causes the Ethernet port to disable. The command
disconnects the OPC from the Network Manager, operations system, X
terminal, or other element connected on the LAN through the lan0 port.
Go to step 11.
—continued—

Step Action
10 Terminate the Ethernet port control procedure without disabling the port by
entering:
no ↵
5. Help
6. Quit
11 Close the tool by entering:
6↵
—end—

Procedure 3-3
Establishing a telnet session between an X terminal
and the OPC
Use this procedure to establish a telnet session with the OPC.
Before you start

• Make sure you have the IP address of the OPC.
• Make sure you have the root password that allows you to access the OPC.
• Understand the OPC user interface (refer to OPC User Interface Description, 323-1511-196).
Procedure tasks
• Telnet to an OPC (step 1).
• Log in to an OPC (step 2).
Expected results
• The OPC “login” prompt appears.
• The “opc>” prompt appears.
— Check the instructions on how to start a telnet session with the X terminal vendor.
—continued—

Establishing a telnet session between an X terminal and the OPC
Action
Step Action
1 From the vendor’s documentation, determine how to start a telnet session.

When the software prompts you, 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.
The UNIX shell prompt ““opc>” appears.
The X terminal connects to the OPC and emulates a VT100 terminal in a
UNIX session.
4 Select the required command to enter after the UNIX shell prompt (“opc>”).
If you must Then enter
display the User Session Manager opcui ↵
logout logout ↵
—end—

Procedure 3-4
Adding, changing, or deleting an NCD19
configuration file
Use this procedure to add, change, or delete an NCD19 X terminal
configuration file on the OPC. The procedure to change a file is identical to the
procedure to add a file.
Because the NCD19 X terminal does not retain certain XDMCP parameters
following a reboot, the OPC provides a way to store these parameters. The
Ethernet Admin tool enables you to create an NCD19 configuration file. The
OPC uses this configuration file to accept the NCD19 parameters after a
reboot.
Before you start

• Make sure you have the software version of the NCD19 X terminal (v.2 or v.3).
• Make sure you have the IP address of the NCD19 X terminal.
• Check that the NCD19 is booting from PROM.
• Log in to the OPC with access privileges for the Ethernet Admin tool.
The Ethernet Admin tool is a restricted tool. With the exception of the root user, only non-default UserIDs
can access restricted tools, such as those assigned to the default tech support user group. The default
tech support user group includes the Restricted Tools toolset. The system administrator can set up a
non-default UserID (refer to Security Management Procedures, 323-1511 -305). You must access the
tool as the root user:
Procedure tasks
• Add or change an NCD19 (X terminal) configuration file (step 5 to step 9).
• Delete an NCD19 (X terminal) configuration file ( step 10 and step 11 ).
Expected results
• A message indicates the addition, replacement, or removal of the NCD19 configuration file on the OPC.
—continued—

Adding, changing, or deleting an NCD19 configuration file
Action
Step Action

root step 2
2 At the UNIX shell prompt (“opc>”), enter:

opcui ↵
4. Help
5. Quit
4 Select the X terminals configuration command by entering:
3↵
A message describing the X terminals configuration option appears. The
system then prompts you to select the required operation:
Enter the operation to perform [a - add, d - delete]:
add or change the configuration file step 5
delete an entry in the configuration file step 10
Note: Use the same procedure to add or change the configuration file.
5 Add or change a configuration file by entering:
a↵
A message describing the requirements for adding an X terminal
configuration file appears. The system then prompts you to enter an NCD19
version number:
Enter the NCD19 X terminal software version number [2-3]:
—continued—


Step Action

If the software version number is Then type
v.2 2↵
v.3 3↵
The system prompts you to enter the IP address of the X terminal:

Enter the X terminal IP address [format must be n.n.n.n,
where n is between 0 and 255]:
IP addresses are unique and assigned by the manufacturer. The IP address
has four numbers, each separated by a period. Each number falls in the
range of 0 to 255, for example, 99.205.1.93.
7 Enter the IP address of the X terminal at the prompt.
The system prompts you to enter the Boot Server IP address:
Enter the Boot Server IP address [format must be n.n.n.n,
where n is between 0 and 255; press Return to Boot From
PROM]:
In order to boot, the NCD19 X terminal requires either an
X Server PROM (as suggested in the X terminal Equipment
Recommendations presented earlier in this chapter) or a
Boot Server available for it to boot from.
If the X terminal Then go to
has an X Server PROM step 8
does not have an X Server PROM and so requires step 9
communications with a Boot Server to boot
8 If the X terminal has with an X Server PROM, press the Return key.
If you create (change) the file, a message prompts you for confirmation. The
following message appears:
NCD19 configuration file ‘file number’ added (replaced).
Press any key to continue.
Go to step 12.
—continued—

Step Action
9 If the X terminal does not have an X Server PROM, enter the IP address of
the Boot Server at the prompt, and press Return.
If you create (change) the file, a message prompts you for confirmation. A
message appears, as follows:
NCD19 configuration file ‘file number’ added (replaced).
Go to step 12.
10 Delete a configuration file by entering:
d↵
A message that describes the requirements to delete an X terminal
configuration file appears. The system then prompts you to enter the IP
address of the X terminal:
Enter the X terminal IP address [format must be n.n.n.n,
where n is between 0 and 255]:
IP addresses are unique and assigned by the manufacturer. The IP address
has four numbers, each separated by a period. Each number falls in the
range of 0 to 255, for example, 99.205.1.93.
11 Enter the IP address of the X terminal at the prompt.
A message appears. The message indicates the tool removed the NCD19
configuration file:
NCD19 configuration file ‘file number’ removed.
4. Help
5. Quit
13 Quit the Ethernet administration program by entering:
5↵
—continued—


Step Action
14 Log out of the session by entering:

logout ↵
Load the NCD19 data from the OPC to the NCD19 X terminal.
If the software version number is Then go to
v.2 Procedure 3-5, “Loading the NCD19
configuration data from the OPC to an
NCD19 X terminal running NCDware
v.2”
v.3 Procedure 3-6, “Loading the NCD19
configuration data from the OPC to an
NCD19 X terminal running NCDware
v.3”
—end—
Procedure 3-5
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 from the
configuration file created in Procedure 3-4, “Adding, changing, or deleting an
NCD19 configuration file”. This procedure applies to any version v.2 of
NCDware.
This procedure does not cover the HP 700/RX X terminal and the Tektronix
XP18 X terminal because these terminals self-boot. These terminals do not
require configuration data from the OPC.
After you correctly complete this procedure, a graphical OPC log in dialog
appears on the NCD19. The OPC log in dialog appears when you power on or
reset the NCD19.
Before you start

• Create the NCD19 configuration file according to Procedure 3-4, “Adding, changing, or deleting an
NCD19 configuration file”.
• Review the NCD19 User Manual to understand the configuration screens and capabilities.
• Make sure you have the IP address of the OPC.
• Check that the NCDware version is in the v.2 series.
Procedure tasks
• Configure an NCD19 X terminal running NCDware v.2 (step 2 to step 7).
Expected results
• An OPC dialog appears.
— Check the X terminal setup requirements.
—continued—


Loading the NCD19 configuration data from the OPC to an NCD19 X terminal running NCDware v.2
Action
Step Action
1 Set up the X terminal according to the requirements provided earlier in this

chapter, in the section “X terminal setup requirements”.
2 From the main menu, select Network Parameters in the Configuration Menu
group.
The Network Parameters window appears.
DX-21181
FW-21181
Network Parameters
Active Ethernet Address Static Ethernet Address
Server Code from TCP/IP Remote Configuration Yes

Boot X at Reset Yes
Config File access TFTP Configuration Server 47.105.2.78
Primary Font access NFS Secondary Font Server 47.105.2.78
Secondary Font access TFTP
System Hostname bmert228
TCP/IP Access Control on
Load Previous Values Protocol Parameters Main Menu
3 Set the Remote Configuration parameter field to Yes.

To change a parameter, click Select on the parameter value field. The next
value appears in the field. Continue to click on the field until the required 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—

Step Action
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.
After a few seconds, an OPC log in dialog appears.
DX0001
FW-21160
FIBER WORLD
User ID:
Password:
Done Alt+Return
You have configured the NCD19.

—end—

Procedure 3-6
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 from the
configuration file created in Procedure 3-4, “Adding, changing, or deleting an
NCD19 configuration file”. This procedure applies to any version v.3 of
NCDware.
This procedure does not cover the HP 700/RX X terminal and the Tektronix
XP18 X terminal because these terminals are self-boot. These terminals do not
require configuration data from the OPC.
After you correctly complete this procedure, a graphical OPC log in dialog
appears on the NCD19. The OPC log in dialog appears when you power on or
reset the NCD19.
Before you start

• Create the NCD19 configuration file according to Procedure 3-4, “Adding, changing, or deleting an
NCD19 configuration file”.
• Review the NCD19 User Manual, to understand the configuration screens and capabilities.
• Check that the NCDware version is in the v.3 family.
Procedure tasks
• Configure an NCD19 X terminal running NCDware v.3 (step 2 and step 3).
Expected results
• An OPC dialog appears.
—continued—

Action
Step Action
1 Set up the X terminal according to the requirements provided earlier in this

chapter, in the section “X terminal setup requirements”.
2 From the NCD User Services: Console window, open 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.
After a few seconds, an OPC log in dialog appears.
DX0001
FW-21160
FIBER WORLD
User ID:
Password:
Done Alt+Return
You have fully configured the NCD19.

—end—

Procedure 3-7
Reconfiguring X terminals following an OPC upgrade
Use this procedure to display the OPC log in banner on an X terminal
following an OPC software upgrade. The procedure applies to X terminals that
you already connected to the OPC before the upgrade.
Before you start

• Understand that the instructions indicate the parameters that you have to set up, but do not provide
equipment-specific details.
Procedure tasks
• Determine the type of X terminal you are configuring (step 1).
• Configure an X terminal (NCD19, 700/RX, or XP18) remotely (step 2 to step 10)
Expected results
• The OPC log in banner appears.
—continued—

Reconfiguring X terminals following an OPC upgrade
Action
Step Action
1 Determine the type of X terminal:

If the X terminal is Then go to
an NCD19 step 10
a 700/RX or an XP18 step 2
2 Set the X terminal for remote configuration.

3 For the remote configuration host, specify the Internet protocol (IP) address
of the OPC.
4 For the remote configuration file access, specify TFTP.
Note: The term “remote configuration” is generic. Each manufacturer has
their own term. Contact the manufacturer if the X terminal documentation
does not use remote configuration terminology for the terminal.
5 Enable XDMCP with Direct Access.
6 Set the XDMCP host to the IP address of the OPC.
7 Determine the type of X terminal:
If the X terminal is Then go to
a 700/RX step 9
an XP18 step 8
8 Under Host File Access, set Primary XP File Root to /usr/lib/X11/XP.

9 Save the parameter settings to NVRAM.
10 Reboot the terminal.
The OPC log in banner appears.
You can now log in to the OPC.
—end—

Optical Networks Products
OPTera Connect DX
Connection Manager Rel 1 &
TN-64X Rel 3
External Interface Configuration
Procedures
Copyright  2000 Nortel Networks, All Rights Reserved
The information contained herein is the property of Nortel

Networks and is strictly confidential. Except as expressly
authorized in writing by Nortel Networks, the holder shall keep all
information contained herein confidential, shall disclose it only to
its employees with a need to know, and shall protect it, in whole
or in part, from disclosure and dissemination to third parties with
the same degree of care it uses to protect its own confidential
information, but with no less than reasonable care. Except as
expressly authorized in writing by Nortel Networks, the holder is
granted no rights to use the information contained herein.
Nortel Networks, the Nortel Networks logo, the Globemark, How

the World Shares Ideas, S/DMS TransportNode, and Unified
Networks are trademarks of Nortel Networks.
VT100 is a trademark of Digital Equipment Corporation.

UNIX is a trademark of X/Open Company Ltd.
323-1511-302
Standard
August 2000
Printed in Canada and in the United Kingdom

1511 302 PDF

Enviado por

Dados do documento

Título original

Direitos autorais

Formatos disponíveis

Compartilhar este documento

Compartilhar ou incorporar documento

Opções de compartilhamento

Você considera este documento útil?

Este conteúdo é inapropriado?

Direitos autorais:

Formatos disponíveis

1511 302 PDF

Enviado por

Direitos autorais:

Formatos disponíveis

323-1511-302

Standard August 2000

VT100 is a trademark of Digital Equipment Corporation.

Printed in Canada and in the United Kingdom

External communications ports 1-1

Configuring OPC ports 2-1

Managing X terminals for the OPC 3-1

External Interface Configuration Procedures 323-1511-302 Standard Aug 2000

Troubleshooting guidelines for X terminals 3-11

About this document 0

External Interface Configuration Procedures 323-1511-302 Standard Aug 2000

OPTera Connect DX and TN-64X Release 3 NTP Libraries

TN-1X NTP Library

TN-4X NTP Library

Planning Guide Installation External Interface Performance TN-4XE NTP Library

References for NTP 302

External Interface Configuration Procedures Summary

• Unconfigure an OPC port (Procedure 2-4)

• Manage the X terminals for the OPC

External Interface Configuration Procedures 323-1511-302 Standard Aug 2000

High level procedure introduction

Some detailed procedures can include warning, caution, or danger messages

Example of a high level procedure introduction

Before you start

External communications ports 1-

For details on provisioning OPTera Connect DX network elements, refer to

External Interface Configuration Procedures 323-1511-302 Standard Aug 2000

Configuring OPC ports 2-

External Interface Configuration Procedures 323-1511-302 Standard Aug 2000

Chapter procedure list

Configuring an OPC port to support terminal operation Procedure 2-1

Configuring an OPC port to support TCP/IP applications using Procedure 2-2

Configuring an OPC port to support printer operation Procedure 2-3

Unconfiguring an OPC port Procedure 2-4

Connecting the cable Procedure 2-5

Configuring a modem for PPL (SLIP) Procedure 2-6

External Interface Configuration Procedures 323-1511-302 Standard Aug 2000

Configure an OPC port for printing

Configuring an OPC port to support printer operation Procedure 2-3

Configuring the printer (see printer

Connecting the cable Procedure 2-5

Configure an OPC port for VT100-type terminal access

Configuring an OPC port to support terminal operation Procedure 2-1

Connecting the cable Procedure 2-5

Configure the OPC for TCP/IP using PPL (SLIP)

Configuring an OPC port to support TCP/IP applications Procedure 2-2

Configuring a modem for PPL (SLIP) Procedure 2-6

Before you start

External Interface Configuration Procedures 323-1511-302 Standard Aug 2000

Procedure 2-1 (continued)

1 Continue with the current config_port session. If a config_port session is not

If you are Then go to

2 Log in to the OPC from a network element or open a telnet session.

If you are logging in as Then

3 Start the Port Configuration tool by entering:

Enter the number for your selection:

Procedure 2-1 (continued)

Enter the number for your selection:

Enter the number for your selection:

External Interface Configuration Procedures 323-1511-302 Standard Aug 2000

Procedure 2-1 (continued)

6 Configure a terminal by entering:

Enter the number for your selection: