User Interface Connection Procedures

323-1501-301
Nortel Networks
OPTera Connect DX Connection
Manager
User Interface Connection Procedures
Standard Rel 1 August 2000
What’s inside...
Connecting terminals or personal computers
Logins/Logouts
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.
Netscape is a trademark of Netscape Communications Corporation.
Printed in Canada and in the United Kingdom

i
Contents 0
About this document iii
Connecting terminals or personal computers 1-1

List of procedures
1-1 Connecting a VT100-compatible terminal to a network element RS-232
port 1-2
1-2 Connecting a remote terminal or PC to a network element RS-232 port 1-6
1-3 Connecting a terminal to an OPC 1-10
1-4 Connecting a PC to a network element Ethernet port 1-17
1-5 Configuring a network element as a host node on a TCP/IP network 1-19
1-6 Enabling or disabling TCP/IP traffic on the network element 1-22
Logins/Logouts 2-1
List of procedures
2-1 Logging in to an OPC from a VT100-compatible device 2-3
2-2 Logging in to an OPC from an X terminal 2-6
2-3 Logging out of an OPC (VT100-compatible device) 2-9
2-4 Logging in to a network element from an OPC 2-12
2-5 Logging in to a remote OPC from an OPC 2-15
2-6 Logging in to a network element from a terminal 2-18
2-7 Configuring a PC for a network element PPP connection through a
modem 2-20
2-8 Logging in to the NE UI through a telnet session 2-26
2-9 Logging in to a network element from a network element 2-29
2-10 Logging in to an OPC from a network element 2-33
2-11 Logging out from a network element 2-36
User Interface Connection Procedures 323-1501-301 Rel 1 Standard Aug 2000

ii Contents
OPTera Connect DX Connection Manager 323-1501-301 Rel 1 Standard Aug 2000

iii
About this document 0

This document describes the user interfaces connection procedures for the
OPTera Connect DX Connection Manager Release 1 and OC-192 network
elements. Topics covered include the following:
• setting up terminal connections to network elements, operation controllers,
modems, and laptop computers
• logging in to or out of the operation controller
• logging in to or out of the network element
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 SONET NTP Library

(OPTera Connect DX & OC-192 Platforms)
Managing and Supporting
Installing, Managing and Maintaining and
Planning a documentation for
Network
Commissioning and Provisioning
Provisioning Troubleshooting
the OPTera Connect
Testing a Network a Network
aa Network
Network
DX SONET Library
OC-3/OC-12 NE
TBM NTP Library
(323-1111-XXX)
OC-48 NTP Library

(323-1201-XXX)
Installation Performance
Planning Guide
(NTRR10DA) Procedures User Interface Monitoring Procedures
(323-1521-201) (323-1521-520)
Connection Procedures
About the OPTera Installation (323-1501-301)
External Interface Performance
Connect DX SONET Procedures Configuration Monitoring Procedures OC-192 NTP Library
NTP Library (323-1541-201) Procedures (323-1541-520) (323-1301-XXX)
(323-1521-090 or (323-1501-302)
323-1541-090 or Powering up and Fault Detection
323-1521/1541-090) Commissioning Software Administration (323-1521-541)
Procedures Procedures
Circuit (323-1521-220) (323-1501-303)
Optical Networks
Pack Descriptions Fault Detection
Data Administration Applications Library
(323-1501-102) (323-1541-541)
Powering up and Procedures (NTCA66BA)
Commissioning (323-1501-304)
Ordering Procedures Alarm Reference
Information (323-1541-220) Guide
(323-1521-151) Security Management (323-1521-542)
Procedures
Site Testing (323-1501-305)
Ordering Procedures Alarm Reference OPTera Long Haul
Information (323-1521-221) Guide 1600 NTP Library
(323-1541-151) Provisioning and (323-1541-542)
Operations Procedures (NTCA65EC)
TL1 Interface Site Testing (323-1521-310)
Procedures Trouble Clearing and
Description Module Replacement
(323-1521-190) (323-1541-221) Provisioning and (323-1521-543)
Operations Procedures
TL1 Interface System Commissioning (323-1541-310) Orderwire User
and Testing Procedures Trouble Clearing and Guide
Description Module Replacement
(323-1541-190) (323-1521-222) Protection (NTCA66CA)
Switching Description (323-1541-543)
NE User Interface System Commissioning and Procedures
and Testing Procedures (323-1521-311) Log Reference
Description
(323-1541-222) (323-1501-840)
(323-1501-195)
Protection
Switching Description Preside NTP
OPC User Interface Library
Description and Procedures
(323-1541-311) (450-3101-XXX)
(323-1501-196)
References for NTP 301
Ordering Information, 323-1521/-1541-151

OPC User Interface Description, 323-1501-196
Installation Procedures, 323-1521/-1541-201
Provisioning and Operations Procedures, 323-1521/-1541-310
External Interface Configuration Procedures, 323-1501-302
Security Management Procedures, 323-1501-305

About this document v
OPC User Interface Connection Procedures Summary

Main tasks:
• Set up the connections as required
— Connect the following equipment (as required) to an RS-232 port at the local craft access
panel (LCAP) or the maintenance interface (MI)
— VT-100 compatible terminal (Procedure 1-1)
— terminal or PC (Procedure 1-2)
— Connect a PC with an Ethernet card to an Ethernet port at the maintenance interface (MI)
(Procedure 1-4)
— Connect a terminal through the serial port on the OPC Interface circuit pack (Procedure 1-3)
• Configure your PC for a network element PPP connection through a modem (Procedure 2-7)
• Configure the network element for a TCP/IP network

— Configure a network element as a host node on a TCP/IP network (Procedure 1-5)
— Enable or disable TCP/IP traffic on the network element (Procedure 1-6)
• Log in to an OPC
— from a VT100-compatible device (Procedure 2-1)
— from an X terminal (Procedure 2-2)
— from a network element (Procedure 2-10)
• Log in to a remote OPC from an OPC (Procedure 2-5)
• Log out of an OPC (Procedure 2-3)
• Log in to the network element user interface (NE UI)

— from an OPC (Procedure 2-4)
— from a terminal (Procedure 2-6)
— through a telnet session (Procedure 2-8)
— from an network element (Procedure 2-9)
• Log out of a network element (Procedure 2-11)

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
Connecting terminals or personal

computers 1-
This chapter provides procedures on how to connect terminals or personal
computers to OPTera Connect DX Connection Manager Release 1 equipment.
Chapter procedure list

Table 1-1 lists the procedures that are available in this chapter. Use these
procedures to connect different terminals, personal computers (PCs), routers,
and modems.
Table 1-1
Connecting terminals, laptops, and modems procedure list
Action Details
Connecting a VT100-compatible terminal to a network element Procedure 1-1

RS-232 port
Connecting a remote terminal or PC to a network element RS-232 Procedure 1-2
port
Connecting a terminal to an OPC Procedure 1-3
Connecting a PC to a network element Ethernet port Procedure 1-4
Configuring a network element as a host node on a TCP/IP Procedure 1-5

network
Enabling or disabling TCP/IP traffic on the network element Procedure 1-6

1-2 Connecting terminals or personal computers
Procedure 1-1
Connecting a VT100-compatible terminal to a network
element RS-232 port
Use this procedure to connect a VT100-compatible terminal to the network
element RS-232 connection at the local craft access panel (LCAP) port, or
maintenance interface (MI) port.
Before you start

•Power up the network element you must connect your terminal to, and make sure the network element
completes its self-tests.
• Check that there is an appropriate power source (110V ac) available for the terminal.
•Have a VT100-compatible terminal.
•Make sure you have an RS-232 user interface cable. Use the 25/25-pin NTCC90EB, 20m (65 ft) for the
LCAP connection. Use the 25/25-pin NTCC90GA, 0.3 m (1 ft) and 9/25-pin NTCC8930, 20 m (65 ft) for
the MI connection. For detailed cable information for the OPTera Connect DX platform, refer to Ordering
Information, 323-1521-151. For the OC-192 platform, refer to Ordering Information, 323-1541-151.
Procedure tasks
• Connect the interface cable to a terminal and a LCAP or MI (step 1 and step 2).
• Plug in the power cord for the terminal and switch the terminal on (step 2).
• Set the terminal connection parameters (step 3).
Expected results
• The terminal “login:” prompt appears.
— Check the connection between the terminal and LCAP or MI.
— Replace the cable if necessary.
—continued—

Procedure 1-1 (continued)

Connecting a VT100-compatible terminal to a network element RS-232 port
Action
Step Action
1 Connect the LCAP or MI user interface cable to the VT100-compatible

terminal.
2 Connect the other end of the user interface cable to either the female 25-pin
connector on the LCAP or the female 9-pin connector on the MI. See Figure
1-1 and Figure 1-2. Plug in the power cord and switch on the power to the
user terminal.
3 Set the terminal communication parameters according to manufacturer
instructions. The factory default values for the LCAP port or MI are as follows:
Parameter Value
data bits 8
baud rate 9600
stop bits 1
parity none
duplex full (no local echo)
emulation VT100
scroll jump
autowrap off
4 If the login prompt does not appear, press the Return key.
5 If the login prompt does not appear after you press the Return key, check the
connections between the LCAP or MI, and the terminal. Replace the cable if
necessary. Also, confirm with your system administrator that LCAP or MI port
parameters have not changed.
—end—

Figure 1-1
Connecting the user interface cable to the LCAP
F3176-192_R30
Pinouts for
cable NTCC90EB Function
BK
1 BR
1 GND
2 R
2 Rx
3 O
3 Tx User interface
4 Y
4 RTS port (RS-232)
5 5 CTS
6
G
6 DSR 25-pin female
BL connector
7 V
7 GND
8 W/BK/BR
8 DCD
20 20 DTR
Local craft
Equipment Peripheral access panel
Male
25/25-pin user
interface cable
NTCC90EB (20 m, 65 ft)
Male
Plug directly
into VT100-compatible
terminal

Figure 1-2
Connecting the user interface cable to the MI
DX0005
9-pin connector
to MI card
FW-3153.7
RS-232
9/25-pin cable

Procedure 1-2
Connecting a remote terminal or PC to a network
element RS-232 port
Use this procedure to connect a remote terminal or PC to the network element
RS-232 connection at the MI port using an external modem.
To access the OPC remotely using a modem, connect to the network element
and then access the OPC from the network element user interface. There is an
additional level of security to log in to the network element.
Note: You can also use this procedure to connect a local PC to an RS-232
port on the MI. For this procedure, connect the PC (with modem card)
directly to the modem.
Table 1-2 lists the pin assignments for the user interface port on the MI.
Table 1-2
Pin assignments for the MI pinouts
Pin Function Pin Function
1 DCD 6 not connected

2 Rx 7 RTS
3 Tx 8 CTS
4 DTR 9 not connected
5 GND
—continued—


Connecting a remote terminal or PC to a network element RS-232 port
Before you start

• Make sure you have an acceptable power source.
• Make sure that two 33600 modems are available (customer provided).
• Make sure that appropriate RS-232 cables are available. Cables connect the two modems to the
telephone line and connect the terminal to the modem (customer provided).
• Make sure you have an RS-232 user interface cable such as a 9/25 pin NTCC8930, 20 m (65 ft) for the
MI connection.
• Make sure you have cable ties, as required. Use 120 mm long (P0880609) or 300 mm long (P0880610).
• Make sure you have a 6.5 mm parallel tip, flat blade screwdriver.
• Refer to the following NTPs for detailed cable information:
— For the OPTera Connect DX platform, refer to Ordering Information, 323-1521-151.
— For the OC-192 platform, refer to Ordering Information, 323-1541-151.
• Make sure you have a VT100-compatible terminal. The customer is responsible for the equipment from
a third-party source.
• When you connect the modem to a telephone line, the telephone line must not have the call waiting
feature enabled.
Procedure tasks
• Connect a user interface RS-232 cable to a network element MI RS-232 port and a modem (step 1 and
step 2).
• Set the modem parameters (step 3).
• Connect the telephone line to the modem (step 4).
• Connect the remote terminal and modem according to the instructions from the manufacturer (step 6).
• Set terminal parameters (step 7).
Expected results
• Youconnect a remote terminal or PC to a network element. This connection provides remote and secure
access to the OPC.
— Check all physical connections.
— Use the MS-DOS ping utility on the PC to check that the PC to NE connection exists.
— Check all parameter settings.
— Replace the cables if necessary.
—continued—


Action
Step Action
1 Connect the 25-pin connector of the MI user interface cable to the modem.
2 Connect the other end of the user interface cable to the 9-pin connector on
the MI (see Figure 1-2).
3 Set the modem parameters as follows:
Assignment On or off
Data Terminal Ready (DTR) Override Off

Verbal/Numeric Result Codes Off
Result code Display On
Command Mode Local Echo Suppression Off

Auto-Answer Suppression Off
Carrier detect (CD) Override Off
Power-on and ATZ Reset Software On

Defaults
AT Command Set Recognition On
4 Connect the telephone line to the telephone jack on the modem with a
customer-provided RS-232 cable. See the Note at the beginning of this
procedure.
5 If you route the cables down the frame vertical, fasten the cables to the frame
with the cable ties.
6 Connect the remote terminal or PC to the telephone jack on the modem with
a customer-provided RS-232 cable. Use the manufacturer’s instructions for
the modem. See the Note at the beginning of this procedure.
—continued—


Step Action
7 Make sure that the configuration settings for the VT100-compatible terminal
are as follows:
Parameter Value
data bits 8
baud rate 9600
stop bits 1
parity none
8 To configure your PC for a network element point-to-point protocol (PPP)

connection through a modem, see Procedure 2-7, “Configuring a PC for a
network element PPP connection through a modem”.
9 See Procedure 2-6, “Logging in to a network element from a terminal” to log
in to the network element.
—end—

Procedure 1-3
Connecting a terminal to an OPC
Use this procedure to connect a terminal to a primary or backup OPC through
the serial port on the OPC interface circuit pack.
Before you start

• Check that there is an appropriate power source for the terminal.
• You must have a terminal. (The terminal can be a VT100-compatible terminal or a laptop computer with
a VT100 emulation package). Purchasing the equipment from a third-party source is the customer’s
responsibility. If you must connect an X terminal to the OPC, refer to External Interface Configuration
Procedures, 323-1501-302.
• You must have an RS-232 user interface cable with D-type, 25-pin male connectors.
You can configure the OPC serial port to support terminal or printer. To connect a terminal to the OPC
serial port, configure the port for terminal operation. This procedure assumes that you set up the port for
the default operation (terminal).
Procedure tasks
• Connect the laptop computer to the OPC (step 6).
• Connect the terminal to the OPC (step 8).
Expected results
• The login prompt appears.
— Check all connections between the terminal or laptop and the OPC.
— Configure the OPC serial port as a terminal.
—continued—


Cable connectors and pinouts

Use standard RS-232 cables to connect terminals to the OPC serial port.
Generally, a VT100-compatible terminal uses a 25-pin connector, while a
laptop uses a 9-pin connector.
Order the cables from Nortel Networks to support your hardware. For the
OPTera Connect DX platform, refer to Ordering Information, 323-1521-151.
For the OC-192 platform, refer to Ordering Information, 323-1541-151. Table
1-3 lists the terminal types and the appropriate ports.
Table 1-3
Terminal to user interface port cables
Terminal Type OPC Serial Port
VT100, printer, or laptop NTCC90EB cable assembly, 20 m (65 ft) or

configured with a 25-pin NTCC90EA, 5 m (16ft), and
connector NTCC90GA cable assembly, 0.3 m (1 ft)
modem configured with a NTCC90EB cable assembly, 20 m (65 ft)

25-pin connector
VT100 terminal settings

See Table 1-4 for configuration settings for a VT100-compatible terminal.
Table 1-4
VT100-compatible terminal configuration settings
Parameter Value
data bits 8
baud rate 19200

stop bits 1
parity none
duplex full (no local echo)
emulation VT100
scroll jump
autowrap off
—continued—


DANGER
Risk of electrical hazard
Before you connect the power, make sure you configure the
equipment for the local power source. You must provide a
ground on the power cord.
CAUTION
Risk of damaging equipment
Do not operate the equipment immediately after exposure to
extreme temperatures. Leave the equipment at room
temperature for two hours before operating. The operating
range is 0°C to 40°C (32°F to 104°F).
CAUTION
Risk of equipment failure
Do not obstruct air vents. Leave 75 mm (3 in.) of free air space
around the equipment to make sure there is enough ventilation.
Action
Step Action
1 Select a VT100-compatible terminal, or a laptop computer (with a VT100

emulator) as the terminal to connect to serial port.
If you use Then go to

a VT100-compatible terminal step 8
a laptop computer step 2
2 Power up the laptop.

The MS-DOS prompt appears.
3 Use the vendor documentation for the emulation package to determine how
to configure your laptop as a VT100-compatible terminal.
—continued—


Step Action
4 If the emulation package requires you to select options, select the following
options:
baud rate 19200

mode (emulation) VT100
port 1 or 2 (Serial Port A) as COM yes
data bits 8
stop bit 1
parity none
full duplex no local echo
scroll jump
autowrap no
protocol ASCII
modem type direct connect (no modem)
For the other options, accept the defaults.

Refer to the suggested key mapping assignment for laptop function keys. The
mapping assignment allows you to use the function keys for many of the
common VT100-terminal user interface functions.
5 Exit from the emulation installation program using the vendor documentation.
The laptop emulates a VT100 terminal and the MS-DOS prompt appears.
6 Connect the laptop to the serial port on the OPC interface using the
appropriate RS-232 cable in Table 1-3. Connect the other end of the cable to
the serial port A on the laptop.
7 Send a break command by entering:
Alt_B ↵
Not all emulation packages or laptops use Alt_B as the break command.
Refer to your documentation to determine the break command if this
command does not cause the login prompt to display.
Go to step 11.
8 Use the appropriate RS-232 cable to connect the terminal to a network
element OPC serial port.
9 Power up the terminal.
10 Press the Return key.
The OPC login prompt (login:) appears on your screen.
—continued—


Step Action
11 Establish if the login prompt appears or not.
If Then go to
the login prompt appears, you connected the Procedure 2-1 to log in to
equipment correctly the OPC
the login prompt does not appear step 12
12 Check all connections between the OPC port and the terminal. Make sure
that you power up the terminal and repeat step 6 to step 11. If the prompt still
does not appear, proceed to step 13 to set up the port for terminal operation.
13 Connect a VT100-compatible terminal to the LCAP port of the network
element as described in Procedure 1-1, “Connecting a VT100-compatible
terminal to a network element RS-232 port”.
14 Log in to the network element (see Procedure 2-6, “Logging in to a network
element from a terminal”). If you do not have a UserID or password for the
network element, see your system administrator.
15 Log in to the OPC from the network element (see Procedure 2-10, “Logging
in to an OPC from a network element”). If you do not have an admin user
account and password, see your system administrator.
The User Session Manager appears
16 Tab to the Port Configuration tool and select it by pressing Ctrl_A (or
Keypad 0).
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:

—continued—


Step Action
17 Query the port configuration by entering:

1↵
The current state of all available ports appears.
18 Press the Enter key to return to the main menu.
19 Display the Configure a service menu by entering:
2↵
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
9 Return to Main menu
10 Exit

20 Select the terminal by entering:
1↵
A message appears, as follows:
Baud Rate:
1 9600 baud
2 19200 baud
9 Return to Configure Menu
10 Exit

21 Select a baud rate by entering its matching menu number and press the
Return key.
The terminal baud rate is changing to <xxxxx>
Do you wish to continue (yes/no):
—continued—


Step Action
22 Confirm the baud rate by entering:

y↵
Terminal baud rate configuration successful on the Serial
Port (xxxxx baud)
The Configure a service menu appears again.
Configure a service:
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

23 Exit from the service menu by entering:
10 ↵
24 Log out from the OPC. See Procedure 2-3, “Logging out of an OPC
(VT100-compatible device)”.
—end—

Procedure 1-4
Connecting a PC to a network element Ethernet port
Use this procedure to connect a PC (with an Ethernet card) to a network
element at one of the maintenance interface (MI) Ethernet ports. This
connection provides access to the network element user interface (NE UI)
through a telnet session.
Before you start

• Make sure that the MI Ethernet port is in service. For the OPTera Connect DX platform, refer to
Provisioning and Operations Procedures, 323-1521-310. For the OC-192 platform, refer to Provisioning
and Operations Procedures, 323-1541-310.
• You must have a PC with an Ethernet card (customer provided).
• For a direct connection, make sure you have an Ethernet cable. You can use the NTCC90CA
(9-pin/teladapt), 20 m (65 ft) to connect the PC to the MI.
• If you require a LAN connection, you must have a router. Connect the router to the LAN with an Ethernet
cable (customer provided). Also, connect the PC to the LAN with an Ethernet cable (customer provided).
• For a LAN connection, make sure you have an Ethernet cable. You can use the NTCC90BA
(9-pin/teladapt), 20 m (65 ft) to connect the MI to the router.
• For OPTera Connect DX cable information, refer to Ordering Information, 323-1521-151. For OC-192
cable information, refer to Ordering Information, 323-1541-151.
• See Procedure 1-5, “Configuring a network element as a host node on a TCP/IP network” to set the
Internet protocol (IP), subnet mask, and gateway addresses on a network element. The subnet mask
and gateway address are optional and for use only when you use subnetting. Do not set the subnet mask
and gateway address for a direct connection between the PC and the network element.
• See Procedure 1-6, “Enabling or disabling TCP/IP traffic on the network element” to enable TCP/IP
traffic.
Procedure tasks
• Connect the interface cable to the PC (step 2) or router (step 3).
• Connect the other end of the interface cable to the MI Ethernet port (step 4).
• Switch on the power to the PC ( step 5).
• Set the PC connection parameters (step 6).
• Set the Internet protocol (IP), subnet mask, and gateway address on an NE as required ( step 7).
• Enable TCP/IP traffic ( step 7).
Expected results
• You correctly connect the PC to the network element at the MI port.
• You can log into the NE UI through a telnet session.
— Check the physical connection between the PC and the MI.
— Use the ping utility on the PC to check that the PC to network element connection exists.
— Make sure you set the PC IP address correctly.
— Replace the cable if necessary.
—continued—


Connecting a PC to a network element Ethernet port
Action
Step Action
1 Connect to the PC, as follows.

If you are connecting the MI Then go to
directly to a PC (with Ethernet card) step 2
to a PC (with Ethernet card) through a LAN step 3
2 Connect the teladapt connector of the Ethernet user interface cable to the PC
(with Ethernet card).
Go to step 4.
3 Connect the teladapt connector of the Ethernet user interface cable to the
router (customer provided).
Note: The customer is responsible for the connection of the router to the
LAN. The customer is responsible for the connection of the PC (with Ethernet
card) to the LAN. Both of these connections use Ethernet cables.
4 Connect the other end (9-pin) of the Ethernet user interface cable to one of
the MI Ethernet ports. For the OPTera Connect DX platform , refer to
Installation Procedures, 323-1521-201. For the OC-192 platform, refer to
Installation Procedures, 323-1541-201.
5 Switch on the power to the PC.

6 Set the IP address of the PC according to the PC manufacturer’s instructions.
Note: Do not use IP addresses 224.0.0.0 to 224.255.255.255, 192.0.0.0 to
192.0.0.255, and 194.0.0.1 to 194.0.0.4. The network element reserves these
addresses.
7 Set the Internet protocol (IP) on a network element. Also set the subnet mask
and default gateway address if there are connections to a LAN. See
Procedure 1-5, “Configuring a network element as a host node on a TCP/IP
network” for the detail procedures.
8 After you set the required addresses, enable the TCP/IP traffic on the
Ethernet port. See Procedure 1-6, “Enabling or disabling TCP/IP traffic on the
network element”.
See Procedure 2-8, “Logging in to the NE UI through a telnet session” to log
in to the NE UI.
—end—

Procedure 1-5
Configuring a network element as a host node on a
TCP/IP network
Use this procedure to configure a network element (NE) as a host node on a
TCP/IP network. The configuration procedure involves adding the following
Internet protocol (IP) addresses to the NE:
• the IP address for the NE maintenance interface Ethernet port
• the IP subnet mask address for the NE maintenance interface Ethernet port
• the gateway IP address
You require the IP subnet mask address and the gateway IP address when there
are connections to a LAN. The NE sends responses to the default gateway
through the IP subnet mask address.
This procedures also includes steps for modifying or deleting IP addresses and
for displaying the current TCP/IP configuration.
Before you start

• Make sure you know the IP address for the task you must complete. The network administrator assigns
the IP addresses.
• You must have Admin or read/write access privileges to the NE UI.
Procedure tasks
• Add or modify an IP address (step 3 ).
• Delete an IP address (step 5 ).
• Display the current TCP/IP configuration (step 7 ).
Expected results
• You configure the NE as a host node on a TCP/IP network.
— Make sure you enter the correct IP address.
— Contact you next level of support.
—continued—


Configuring a network element as a host node on a TCP/IP network
Action
Step Action
1 Log in to the NE UI. If you do not know how to do this, see Chapter 2,
“Logins/Logouts” in this document.
2 Select your next step.
If you must Then go to
add or modify the current IP address step 3
delete an IP address step 5
display the current TCP/IP configuration step 7
3 To add or modify the current address, enter the command:

ipedit <type> <n.n.n.n> ↵
where
<type> is ip, subnet, or gateway
<n.n.n.n> is the IP address in standard dot notation
n is any integer from 0 to 255, inclusive
For example, a standard dot notation address is
47.43.0.223
Note: Do not use the following range of IP
addresses: 192.0.0.0 to 192.0.0.255, 192.0.0.1 to
194.0.0.4, and 224.0.0.0 to 224.255.255.255. The
network element reserves these addresses for
internal use.
The software accepts the address and configures the network element as a
host. An error message appears if the software does not accept the
addresses.
4 If you are adding a new address, enable TCP/IP traffic. See Procedure 1-6,
“Enabling or disabling TCP/IP traffic on the network element”.
—continued—


Configuring a network element as a host node on a TCP/IP network
Step Action
5 Delete the current address by entering:

ipdelete <type> <n.n.n.n> ↵
where
<type> is ip, subnet, or gateway
<n.n.n.n> is the IP address in standard dot notation
n is any integer from 0 to 255, inclusive
For example, a standard dot notation address is
47.43.0.223
The software deletes the current address.

log out of the NE UI step 8
7 Display the current TCP/IP configuration by entering:

ipquery ↵
Configuration information appears as shown in the following example:
IP Address:47.214.52.223
Subnet Mask:255.255.240.0
Default Gateway:ENABLED
Ethernet Address:00:00:75:51:14:01
8 Log out of the NE UI by entering:
logout ↵
—end—

Procedure 1-6
Enabling or disabling TCP/IP traffic on the network
element
Use this procedure to enable or to disable TCP/IP traffic on the network
element (NE) maintenance interface (MI) Ethernet port.
Before you start

• You must configure the NE as a host node on a TCP/IP network. See Procedure 1-5, “Configuring a
network element as a host node on a TCP/IP network”, in this chapter.
• You must have Admin or read/write access privileges to the NE UI.
Procedure tasks
• Display the current TCP/IP configuration (step 3).
• Enable TCP/IP traffic on the network element (step 4).
• Disable TCP/IP traffic on the network element (step 5).
Expected results
• You enable TCP/IP traffic. The NE receives TCP/IP traffic.
• You disable TCP/IP traffic. The NE no longer receives TCP/IP traffic.
—continued—


Enabling or disabling TCP/IP traffic on the network element
Action
Step Action
1 Log in to the NE UI. If you do not know how to do this, see Chapter 2,
“Logins/Logouts” in this document.
enable TCP/IP traffic on the NE step 4
disable TCP/IP traffic on the NE step 5
log out of the NE UI step 6
3 Display the current TCP/IP configuration by entering:

ipquery ↵
Configuration information appears as shown in the following example:
IP Address:47.214.52.223
Subnet Mask:255.255.240.0
Default Gateway:ENABLED
Ethernet Address:00:00:75:51:14:01
4 Enable the TCP/IP traffic on the NE by entering:
iptraffic enable ↵
The following message appears.
iptraffic command successful
5 Disable the TCP/IP traffic on the NE by entering:
iptraffic disable ↵
The NE no longer received TCP/IP packets on the MI Ethernet port.
6 Log out of the NE UI by entering:
logout ↵
—end—


2-1
Logins/Logouts 2-
This chapter provides procedures on how to log in and log out at the operations
controller (OPC) and the network element (NE).
Chapter procedure lists

Table 2-1 lists the procedures available in this chapter to manage log in and log
out procedures at the OPC.
Table 2-1
Logins and logouts at the OPC
Action Details
Logging in to an OPC from a VT100-compatible device Procedure 2-1
Logging in to an OPC from an X terminal Procedure 2-2
Logging out of an OPC (VT100-compatible device) Procedure 2-3

Logging in to a network element from an OPC Procedure 2-4
Logging in to a remote OPC from an OPC Procedure 2-5
Table 2-2 lists the procedures available in this chapter to manage log in and log
out procedures at the NE.
Table 2-2
Logins and logouts at the NE
Action Details
Logging in to a network element from a terminal Procedure 2-6
Configuring a PC for a network element PPP connection through Procedure 2-7

a modem
Logging in to the NE UI through a telnet session Procedure 2-8

2-2 Logins/Logouts
Table 2-2 (continued)

Logins and logouts at the NE
Action Details
Logging in to a network element from a network element Procedure 2-9

Logging in to an OPC from a network element Procedure 2-10
Logging out from a network element Procedure 2-11

Logins/Logouts 2-3
Procedure 2-1
Logging in to an OPC from a VT100-compatible device
Use this procedure to log in to an OPC from a VT100-compatible device.
For information about how the OPC handles intrusion attempts, refer to
Security Management Procedures, 323-1501-305.
Before you start

• Have a UserID and password that allow you access to the OPC.
• Connect a terminal to the OPC as described in Chapter 1, “Connecting terminals or personal computers”.
Procedure tasks
• Log in to an OPC (step 1 and step 2).
• Access the User Session Manager (step 5).
Expected results
• The TERM = (VT100) prompt appears (if you logged on as root).
• The User Session Manager appears.
— Check your UserID and password.
—continued—

2-4 Logins/Logouts

Action
Step Action
1 Type your UserID after the login prompt and press the Return key at the OPC
login screen.
The password prompt appears.
password:
2 Type your password and press the Return key at the password prompt.
The password does not appear in the field when you enter it.
Note: Passwords are lowercase only.
If your UserID is Then go to

root step 3
not root the User Session
Manager opens
automatically
3 Press the Return key when the “TERM = (VT100)” prompt appears.
4 As a root user, you can execute script commands, or you can start the User
Session Manager.
If you must Then

execute script commands Procedure 2-1 ends here
open tools from the User Session Manager go to step 5
—continued—

Logins/Logouts 2-5

Step Action
5 Access the User Session Manager by entering:

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

Available tools Open tools
Toolset/Tools ID State Tool
Software Admin 2 > . OK OPC Status : Primary/Active
Alarm Monitor 3 - Unix Shell
Event Browser 4 - Unix Shell
Network Upgrade Mngr
OPC Admin
Central User Admin
OPC Save and Restore
OPC Shutdown
OPC Date
Port Cofiguration
IP Routing Admin
Unix Shell
OPC PM Coll.Filter
TL1 Configuration
OPC Alarm Prov
[ Logout ]
C 0 M 0 m 1 w 2 FailProt 0 Lckt 0 ActProt 0 PrfAlrt 0 10:10
—end—

2-6 Logins/Logouts
Procedure 2-2
Logging in to an OPC from an X terminal
Use this procedure to log in to an OPC from an X terminal.
Before you start

• Have a UserID and password that allow you access to the OPC.
• Connect an X terminal to the OPC as described in the chapter on Managing X terminals for the OPC.
Refer to External Interface Configuration Procedures, 323-1501-302.
Procedure tasks
• Log in to an OPC from an X terminal (step 1 and step 2).
Expected results
• The workspace window appears and you can log in.
—continued—

Logins/Logouts 2-7

.Action
Step Action
1 Enter your UserID in the User ID field at the OPC login screen as shown in
the following example.
DX0001
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
2 Tab to the password field and enter your password.

Note: Passwords are lowercase only.
—continued—

2-8 Logins/Logouts

Step Action
3 Tab to the Done button and press Alt_Return.

Note: Some workstations do not have an Alt key. For an HP workstation, use
the Extend Char key. For a SUN workstation use the Left or Right key or the
<diamond symbol>. The NCD workstation has an Alt key.
The workspace displays the tools that are available to you.
F21699
FW-21699
Toolset icon Toolset A Toolset B Toolset C Toolset D
Pointer X
This step completes the log in procedure.

Refer to OPC User Interface Description, 323-1501-196, for details on the
use of the graphical user interface.
—end—

Logins/Logouts 2-9
Procedure 2-3
Logging out of an OPC (VT100-compatible device)
Use this procedure to log out from the OPC.
Before you start

• Log in to the OPC.
•Make sure that you complete all work for that session.
Procedure tasks
• Log out of the OPC (step 2).
Expected results
• If any OPC tools are open, the logout command automatically closes the tools and removes their
windows.
• The login screen appears.
—continued—

2-10 Logins/Logouts

Action
Step Action
1 If you do not have the User Session Manager window open, you must open it.
To display the User Session Manager, press Ctrl_T 0.
(Ctrl_T 0 means that you hold the Control key down while you press T. Next,
release both the Control and the T keys and press the 0 key.)
The User Session Manager window appears.
F21059-192_R60
FW-21059

OPC Admin
Central User Admin
OPC Shutdown
OPC Date
Port Cofiguration
IP Routing Admin
Unix Shell
OPC PM Coll.Filter
TL1 Configuration
OPC Alarm Prov
[ Logout ]
—continued—

Logins/Logouts 2-11

Step Action
2 In the User Session Manager, tab to the Logout button and select it by
pressing Ctrl_A (or Keypad 0).
A confirmation message appears.
DX1907
Warning Press the Logout Button to close

all windows, or the Cancel Button
to dismiss this dialog and resume
with the current session.
[ Logout Return] [ Cancel Del]
3 In the confirmation dialog, tab to the Logout button and select it by pressing
Ctrl_A (or Keypad 0).
The confirmation dialog closes, the User Session Manager window closes,
and the login screen appears.
—end—

2-12 Logins/Logouts
Procedure 2-4
Logging in to a network element from an OPC
Use the following procedure to log in to a network element from the OPC.
For information about how the OPC and network elements handle intrusion
attempts, refer to Security Management Procedures, 323-1501-305.
Before you start

• Have aUserID and password that allow you access to the OPC in the same span of control as the
network element that you must access.
• Have a UserID and password that allow you access to the network element that you must work on.
• Log in to the OPC. See Procedure 2-1, “Logging in to an OPC from a VT100-compatible device” or
Procedure 2-2, “Logging in to an OPC from an X terminal”.
Procedure tasks
•Open the NE Login Manager tool (step 1).
• Select the required NE (step 3) .
• Select the appropriate login method (step 5 orstep 6 ).
Expected results
• The main menu of the network element user interface appears.
—continued—

Logins/Logouts 2-13

Action
Step Action
1 Open the NE Login Manager tool. If you do not know how to do this, refer to
OPC User Interface Description, 323-1501-196.
The NE Login Manager main window appears.
F21216-192_R30
FW-21216
>. NE Login Manager

Available Nodes:
NE ID NE Name
4885
4886
Network Element: >
[ Auto login Q] [ Login L]
[Refresh list R]
C 0 M 0 m 1 w 2 FailProt - Lckt 0 ActProt 0 PrfAlrt - 11:11
If you Then
know the network element ID or name enter the ID or name directly
in the Network Element field
go to step 4
do not know the network element ID or name go to step 2
2 Tab to the Available Nodes list.

3 Move to the required network element by using the down arrow key. Select
the network element by pressing Ctrl_A (or Keypad 0).
—continued—

2-14 Logins/Logouts

Step Action
4 Select the appropriate login method for the network element that appears in
the Network Element field.
You can have a different UserID and password for the network element than
for the OPC. See your system administrator to determine your UserID and
password for the OPC and the network elements.

log in without entering your UserID and password step 5
log in using another UserID and password step 6
5 If you have the same UserID and password for the OPC and network
element, tab to the Auto login button. Select the button by pressing Ctrl_A
(or Keypad 0).
If a connection is possible and you have access privileges, the main menu of
the network element user interface appears.
Note: After five consecutive failed login tries, the NE locks the serial port.
The NE automatically releases the serial port after 60 seconds from the last
try.
Go to step 9.
6 If you need to specify a different UserID and password for the network
element, tab to the Login button. Select the button by pressing Ctrl_A (or
Keypad 0).
7 Enter your user name.
<user_name> ↵
The following prompt appears:
>Enter Password
8 Enter your password.
<user_password> ↵
If a connection is possible and you have access privileges, the main menu of
the network element user interface appears.
Note: After five consecutive failed login attempts, the NE lock the serial port.
The NE automatically releases the serial port after 60 seconds from the last
try.
9 Enter network element commands as required.
—end—

Logins/Logouts 2-15
Procedure 2-5
Logging in to a remote OPC from an OPC
Use this procedure to log in to a remote OPC with a graphical terminal session.
Note: At step 5 of this procedure, you move from the graphical terminal
session to a character-mode terminal (CMT) session.
Before you start

• Use the Commissioning Manager tool to add the remote OPC to the list of OPCs that this OPC can
reach.
• Have a UserID and password that allow you access to the local OPC.
• Have a UserID and password that allow you access to the remote OPC.
• Log in to the local OPC. See Procedure 2-1, “Logging in to an OPC from a VT100-compatible device”.
Procedure tasks
• Log in to a remote OPC from an OPC using the Remote OPC Login tool (step 1).
Expected results
• The User Session Manager window for the remote OPC appears.
—continued—

2-16 Logins/Logouts

Action
Step Action
1 Display the Utilities toolset and select the Remote OPC Login tool.
The Remote OPC Login dialog appears.
F20658
FW-20658
File Help
OPC:
Login Alt+Return
2 In the OPC field, open the pull-down menu by clicking the right mouse button.
Select the OPC that you must log in to or enter the name of the OPC directly
into the field.
The name of the OPC appears in the OPC field.
3 Select the Login button.
A session window appears with the Login prompt.
OPC LOGIN (OPCM0011P)
login:
4 At the Login prompt, type your UserID and press the Return key.
The Password prompt appears.
OPC LOGIN (OPCM0011P)
login: admin
password:
—continued—

Logins/Logouts 2-17

Step Action
5 At the Password prompt, type your password and press the Return key.
The remote OPC allows you to log in. The User Session Manager for the
remote OPC appears. Remember to log out when you finish.
Note 1: Passwords are lowercase only.
Note 2: The screen display can be different for users different from admin.
F21059-192_R60
FW-21059

OPC Admin
Central User Admin
OPC Shutdown
OPC Date
Port Cofiguration
IP Routing Admin
Unix Shell
OPC PM Coll.Filter
TL1 Configuration
OPC Alarm Prov
[ Logout ]
—end—

2-18 Logins/Logouts
Procedure 2-6
Logging in to a network element from a terminal
Use this procedure to log in to a network element
• from a locally connected VT100-compatible terminal
• from a VT100-compatible terminal that connects to the shelf by way of a
modem connection
For information about how the network element handles intrusion attempts,
refer to Security Management Procedures, 323-1501-305.
Before you start

• Connect a VT100-compatible terminal to the network element, either directly by way of one of the
network element ports or indirectly by way of a modem. See Chapter 1, “Connecting terminals or
personal computers”.
• Power up the VT100-compatible terminal.
• Have a UserID and password that allows you access to the network element that you must work on. If
you are not sure if you have a UserID, consult your system administrator.
Procedure tasks
• Use your user name and password to log in to a network element (step 2 and step 3).
Expected results
• The main menu of the network user interface appears.
—continued—

Logins/Logouts 2-19

Logging in to a network element from a terminal
Action
Step Action

The login prompt appears:
login:
2 Enter your user name:
<user_name> ↵
The password prompt appears:
password:
3 Enter your password:
<user_password> ↵
The main menu of the network element user interface appears.
—end—

2-20 Logins/Logouts
Procedure 2-7
Configuring a PC for a network element PPP
connection through a modem
Use this procedure to configure your PC for a network element (NE)
connection through a modem and with the point-to-point protocol (PPP).
Before you start

• Have a PC remotely connected to a network element. See Procedure 1-5, “Configuring a network
element as a host node on a TCP/IP network”.
• Enter the telephone number of the modem so that you can automatically dial in.
Procedure tasks
• From the PC Control Panel, configure your PC for a PPP connection (step 2 to step 16).
• Configure the Dial-up Networking (step 17 to step 40).
• Start the PPP connection to the network element (step 41 to step 46 ).
• Disconnect the established connection (step 47 ).
Expected results
• You connect to a network element which allows you to log in to the network element.
— Use the ping utility on the PC to check that the RS-232 connection between the PC and the network
element. The connection at the network element is through the MI port.
—continued—

Logins/Logouts 2-21

Configuring a PC for a network element PPP connection through a modem
Action
Step Action
Setting up your PC for a PPP connection

1 Power up your PC.
2 From your PC, go to the Control Panel and double click on Network.
The Network Control Panel dialog appears.
3 Click on the Configuration tab and verify that the following network
components are installed. If the following components are not installed on
your PC, then contact your next level of support.
Network component
Client for Microsoft Networks
Dial-up Adapter
TCP/IP
4 Select TCP/IP and click on Properties.

The TCP/IP Properties dialog appears.
5 Click on the IP Address tab and verify that the Obtain an IP address
automatically option is selected.
6 From the TCP/IP Properties dialog, click on the WINS Configuration tab.
7 Select the Disable WINS Resolution option.
8 From the TCP/IP Properties dialog, click on the DNS Configuration tab.
9 Select the Disable DNS option and click on OK to return to the Network
Control Panel dialog.
The Network Control Panel dialog appears
10 Make sure the Configuration is selected.
11 Verify that “Client For Microsoft Networks” appears in the Primary Network
Logon box.
12 Click on the Identification tab from the Network Control Panel dialog.
13 Enter your user name for the Computer name.
14 Enter “Dial-Up” for the Workgroup and click on OK.
The Network Control Panel dialog closes.
15 If you are prompted for the Windows 95/98 CD, insert the CD and click on OK.
If not, go step 17.
16 When Windows prompts you to restart your computer, click on Yes. After the
computer restart, continue with step 17.
—continued—

2-22 Logins/Logouts

Step Action
Configuring Dial-up networking

17 Double click on the My Computer icon.
The My Computer dialog appears.
18 Double click on Dial-up Networking.
The Dial-up Networking window appears.
19 Double click on Make New Connection.
The Make New Connection dialog appear.
20 Enter a name for the network element (NE) or computer you are dialing.
Note: The default is “My connection”. You can leave the default selection or
choose a name for your connection.
21 In the “Select a device field”, select the modem you want to use and click on
the Configure button.
Note: The choices available depend on the modem drivers installed on your
computer.
The modem configuration dialog appears.
22 Click on the General tab, and configure the modem as follows:
a. Select the maximum speed from the pull-down menu by pressing down
on the arrow to the right of the box.
b. Make sure the Only Connect at this Speed box is not selected.
23 Select the Connection tab from the modem configuration dialog.
24 Under Connection Preferences, set the following:
a. Set Data Bits to 8.
b. Set Parity to None.
c. Set Stop Bits to None.
25 Under Call Preferences, set the following:
a. Select Wait for Dial Tone Before Dialing.
b. Select Cancel the Call If Not Connected Within.
c. Set the number of seconds to 60.
26 Click on the Options tab from the modem configuration dialog.
27 Under Connection Control, select Select Bring Up Terminal Window After
Dialing.
28 Under Dial Control, make sure Operator Assisted or Manual Dial is not
selected.
—continued—

Logins/Logouts 2-23

Step Action
29 Under Status Control, select Display Modem Status and click OK.
The Make New Connection dialog appears again.
30 Click on the Next button.
31 Enter the Area Code, Phone number and Country code of the modem
connected to the NE to which you need to connect and click on the Next
button.
A dialog appears to confirm the creation of the new connection.
32 Click on the Finish button to close the Make New Connection dialog.
33 From the Dial-up Networking dialog, click on the icon for the new NE
connection.
34 From the File menu, select Properties.
The new connection Properties dialog appears.
35 Click on the Server Types tab and select the following:
a. Under Advanced Options, select Enable Software Compression.
b. Under Allowed Network Protocols, select TCP/IP.
36 Click on the TCP/IP button.
The TCP/IP setting dialog appears.
37 From the TCP/IP settings dialog, perform the following:
a. Select Server Assigned IP Address.
b. Select Server Assigned Name Server Addresses.
c. Select Use IP Header Compression.
d. Make sure Use Default Gateway on Remote Network is not selected.
e. Click on OK.
The Properties dialog for the new NE connection appears.
38 Click on OK.
The Dial-up Networking dialog appears.
39 From the Connection menu, select Settings.
The Dial-up Networking Settings dialog appears.
—continued—

2-24 Logins/Logouts

Step Action
40 From the General tab, select the following:

a. Select Show an Icon on Taskbar After Connected.
b. Make sure Prompt For Information Before Dialing is not selected.
c. Make sure Show a Confirmation Dialog After Connected is not selected.
d. Check the box to the left of Redial.
e. Enter 99 for Before Giving Up Retry.
f. Enter 5 minutes for Between Tries Wait.
g. Select Prompt to Use Dial-up Networking and click on OK.
The Dial-up Networking Settings dialog closes.
Starting a PPP connection
41 From the Dial-up Networking dialog, double-click on the icon for new NE
connection.
The Connect To dialog appears.
42 Enter your user name and password and click on Connect.
The Connecting To <NE Name> dialog appears to indicate you are being
connected to the NE.
The Post-Dial Terminal dialog appears.
43 Press the Enter key.
The login prompt appears.
login:
44 Configure the PC for a point-to-point protocol by entering:
ppp ↵
The Dialing Progress dialog appears.
45 Select Continue.
The Post-Dial Terminal screen closes.
The Connecting to <NE number> dialog appears showing Status: Logging on
to network.
After a short while, the Enter Network Password dialog appears.
46 Press the Esc key.
The previous dialogs close.
To log in to a network element, go to Procedure 2-8, “Logging in to the NE UI
through a telnet session”.
—continued—

Logins/Logouts 2-25

Step Action
Disconnecting an established connection

47 You can disconnect from the network element in the following ways:
a. From the Dial-up Networking window, double-click on the network
element connection icon and select Disconnect.
b. Double-click on the Taskbar icon and select Disconnect.
c. Right-click on the Taskbar icon and select Disconnect.
—end—

2-26 Logins/Logouts
Procedure 2-8
Logging in to the NE UI through a telnet session
Use this procedure to log in to a network element user interface (NE UI)
through a telnet session.
For an Ethernet connection, you can connect the PC directly to the network
element, or through a local area network (LAN). You can connect the PC to the
network element with an RS-232 connection.
Before you start

• Make sure your PC is connected to a network element directly, through a LAN, or through modems.
See Procedure 1-4, “Connecting a PC to a network element Ethernet port” or Procedure 1-5,
“Configuring a network element as a host node on a TCP/IP network”.
• Power up the PC.
• Have RFC compliant telnet client software installed on your PC, for example, TNVT Plus.
• Make sure you understand the commands and operations provided by your telnet client software. User
commands vary with the software application.
• Have the network element IP address available.
• Have a name (UserID) and password that allows you access to the network element that you must work
on. If you are not sure if you have a UserID, consult your system administrator.
Procedure tasks
• Configure the telnet application (step 2).
• Check that the TCP/IP connection between the PC and network element exists (step 3).
• Login to the network element user interface (step 4 to step 6).
Expected results
• The ping response shows that a connection exists between the PC and network element.
• The main menu of the NE UI appears.
— Use the ping utility on the PC to check that the TCP/IP connection between the PC and the network
element exists.
—continued—

Logins/Logouts 2-27

Action
Step Action

configure the telnet application step 2
log in to the NE UI using telnet step 4
2 To configure the telnet application, open the telnet application and, if possible,
configure the settings, as follows:
a. Turn off the local echo.
b. Set the Terminal emulation to VT-100.
3 With the telnet application open, check that the TCP/IP connection between
the PC and the network element exists. Ping the network element by entering:
ping <IP address> ↵
If you have Then enter the IP address
an Ethernet connection for the network element
a PPP RS-232 connection to the MI or LCAP for the Mi or LCAP port
Ping results appear. To stop a ping in progress, enter the command,

Control_C, or refer to the ping software documentation.
If you do not establish a connection, make sure you set the Internet Protocol
(IP) correctly. For the OPTera Connect DX platform, refer to Provisioning and
Operations Procedures, 323-1521-310. For the OC-192 platform, refer to
Provisioning and Operations Procedures, 323-1541-310.
4 Log in to the NE UI by entering:
telnet <IP address> ↵
The login prompt appears as follows:
login:
5 Enter your user name:
<user_name> ↵
The password prompt appears, as follows:
password:
—continued—

2-28 Logins/Logouts

Step Action
6 Enter your password:

<user_password> ↵
The main menu of the network element user interface appears.
Note: Make sure you understand the commands and operations provided by
your telnet client software. User commands vary with the software
application. For example, the command Control_C allows UNIX telnet users
to escape to the telnet command mode from the NE UI. The command has
no effect for PC telnet users.
—end—

Logins/Logouts 2-29
Procedure 2-9
Logging in to a network element from a network
element
Use this procedure to log in to a network element from another network
element or from an operations controller (OPC). If you log in to the Network
Manager and you must access a network element, refer to Nortel Networks’
Preside network management system documentation.
For information about how the network element handles intrusion attempts,
refer to Security Management Procedures, 323-1501-305.
From the OPC, you must access a network element as described in

Procedure 2-4, “Logging in to a network element from an OPC”. You can also
to log in to a remote OPC from a network element (see Procedure 2-10,
“Logging in to an OPC from a network element”).
To access another network element from a local network element, use the
rlogin command.
The rlogin command allows the user to reach network elements outside of the
span of control of the local network element. In addition, the rlogin command
allows access to different systems. For example, you use the rlogin command
to access an OC-12 network element from another OC-192 network element.
In this example, you must connect the network element that you must reach to
the local network element by way of an optical fiber.
If you use rlogin, you can operate the network element as if you logged in to
a terminal connected directly to the network element.
—continued—

2-30 Logins/Logouts

Logging in to a network element from a network element
Before you start

• Connect to the local network element through a VT100-compatible terminal connected to the network
element, directly or indirectly. Connect directly by way of a network element port. Connect indirectly by
way of a modem. See Chapter 1, “Connecting terminals or personal computers”.
• Have a UserID and password that allows you access to both the local and the remote network element
that you must work on. If you are not sure if you have a UserID for both the local and the remote network
element, consult your system administrator.
• Understand the limitations of the rlogin command. You cannot perform a remote login to one network
element and then remote login to a third network element. It is only a single-stage command.
Procedure tasks
• List all the network elements that you can log in to remotely from the network element (step 1).
• Log in to the required network element (step 2).
Expected results
• A list of network elements and OPCs that you can reach appears on the screen.
• The main menu of the network user interface appears.
— Check the network element name and identifier.
—continued—

Logins/Logouts 2-31

Action
Step Action
1 If you do not know the name or the network element identifier that you must
open a session with, enter:
listnodes [ne] [opc] [myopc] ↵
where
[ne] lists all the network elements that you can reach from
this network element
[opc] lists all the OPCs that you can be reach from this
network element
[myopc] lists the active OPC for this network element
Note: If you enter the listnodes command without entering any variables,
the screen lists all network elements and all OPCs that you can reach from
this network element.
A screen appears showing all the network elements and OPCs that you can
reach by the rlogin command from this network element.
2 Login remotely by entering:
rlogin [‘<node_name>’] [ne <neid>] [‘<opc_nodename>’]
]
where
<node_name> The node name is the name of the remote
network element. The node name changes to
uppercase letters if you do not enclose the node
name in single quotation marks.
<neid> The neid is the network element identifier, not
the network element name (that is enter ne 1305
rather than ‘toronto_no5’ as the node name
parameter).
<opc_nodename> The OPC nodename is the OPC identifier. The
OPC identifier is the alias associated with the
OPC serial number. See Procedure 2-10,
“Logging in to an OPC from a network element”.
The OPC node name changes to uppercase
letters if you do not enclose the OPC nodename
in single quotation marks.
—continued—

2-32 Logins/Logouts

Step Action
The following table provides examples of different logins.
Command entered Host that you reach
rlogin ‘Sometown’ The Host sets up a session with the network element
called Sometown
rlogin ne1305 The Host sets up a session with the network element
that has the network element identifier 1305
rlogin This command provides the user with the correct
parameters to use.
3 When requested, enter your user name and press the Enter key.
<user_name> ↵
4 Enter your user password and press the Enter key.
<user_password> ↵
The main menu of the network user interface appears.
—end—

Logins/Logouts 2-33
Procedure 2-10
Logging in to an OPC from a network element
Use this procedure to log in to an OPC from a network element.
For information about how the OPC and network element handle intrusion
attempts, refer to Security Management Procedures, 323-1501-305.
Before you start

• Have a UserID and password for the network element.
• Have a UserID and password for the OPC.
• Connect a terminal to the network element in the same span of control as the OPC that you must reach.
See Chapter 1, “Connecting terminals or personal computers”.
• Log in to the network element.
Procedure tasks
• List the node names for the OPCs in the current configuration (step 1).
• Log in to the required OPC (step 2).
Expected results
• The list of OPCs that you can reach from this network element.
• The User Session Manager window appears.
— Check the OPC node name.
—continued—

2-34 Logins/Logouts

Logging into an OPC from a network element
Action
Step Action
1 From the network element user interface, enter:

listnodes ↵
A message lists the node names for the network elements and OPCs in the
current configuration.
2 Enter the following command from the network element screen:
rlogin <opc nodename>↵
where
<opc nodename> is a unique OPC identifier
A screen appears with a login prompt.
login:
Command entered Host that you reach
rlogin opc Sets up a session with the active OPC for the network
element that you issue the command from.
rlogin opc99999b Sets up a session with the backup OPC that has an
alias of opc99999b.
rlogin opc99999p Sets up a session with the primary OPC that has an
alias of opc99999p.
rlogin opc backup Returns an error message. This release does not
support this parameter.
rlogin Calls up the listnodes command, and prompts the

user to enter a valid name.
Note: Nortel Networks recommends that you use the OPC name as the
alias. If you call the primary OPC “opc99999p”, then “opc99999p” is the
number you enter for the alias. In the same way, the alias for the backup is
opc99999b. The alias is the name that the software stores against the OPC
serial number. This method is the only way that you can set up a session
with an inactive OPC.
—continued—

Logins/Logouts 2-35

Logging in to an OPC from a network element
Step Action
3 Enter your UserID after the login prompt. Your UserID is case sensitive.
A message prompts you for a password.
4 Enter the password after the password prompt. Your password is lowercase
only.
5 If you log in as a root user, you automatically access the UNIX shell layer of
the interface. Access the OPC user interface by entering:
opcui ↵
The User Session Manager appears showing you the tools that you can use.
F21059-192_R60
FW-21059

OPC Admin
Central User Admin
OPC Shutdown
OPC Date
Port Cofiguration
IP Routing Admin
Unix Shell
OPC PM Coll.Filter
TL1 Configuration
OPC Alarm Prov
[ Logout ]
—end—

2-36 Logins/Logouts
Procedure 2-11
Logging out from a network element
Use the following procedure to log out from a network element. The result of
a log out depends on your log in method to the network element.
There are two ways to log in to the network element:

• indirectly, through another network element or an operations controller
(OPC)
• directly, through a local terminal or a terminal connected through a modem
Before you start

• Log in to a network element locally, from another network element, or from an OPC.
• All your work on the network element must be complete.
Procedure tasks
• Logout of a network element (step 2 or step 3).
Expected results
• If you logged in remotely from the OPC, the NE Login Manager appears.
• You are logged out of the network element.
—continued—

Logins/Logouts 2-37

Logging out from a network element
Action
Step Action
1 Determine your log in method.
If you logged in to the network element Then go to

from another network element, from a local step 2
terminal or from a remote terminal
from an OPC step 3
2 End a session from any screen in the network element user interface by
entering:
logout ↵
The network element logs you out.
3 Return to the NE Login Manager on the OPC by entering:
logout ↵
A message prompts you to press the Return key.
The NE Login Manager window appears.
—end—

2-38 Logins/Logouts

Nortel Networks
OPTera Connect DX
Connection Manager
User Interface Connection 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.
Netscape is a trademark of Netscape Communications
Corporation.
323-1501-301
Standard Rel 1
August 2000
Printed in Canada and in the United Kindgom

User Interface Connection Procedures

Hochgeladen von

Dokumentinformationen

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

User Interface Connection Procedures

Hochgeladen von

Copyright:

Verfügbare Formate

323-1501-301

Standard Rel 1 August 2000

VT100 is a trademark of Digital Equipment Corporation.

Printed in Canada and in the United Kingdom

Connecting terminals or personal computers 1-1

User Interface Connection Procedures 323-1501-301 Rel 1 Standard Aug 2000

OPTera Connect DX Connection Manager 323-1501-301 Rel 1 Standard Aug 2000

About this document 0

User Interface Connection Procedures 323-1501-301 Rel 1 Standard Aug 2000

OPTera Connect DX SONET NTP Library

OC-48 NTP Library

References for NTP 301

Ordering Information, 323-1521/-1541-151

OPTera Connect DX Connection Manager 323-1501-301 Rel 1 Standard Aug 2000

OPC User Interface Connection Procedures Summary

• Configure the network element for a TCP/IP network

• Log in to a remote OPC from an OPC (Procedure 2-5)

• Log out of an OPC (Procedure 2-3)

• Log in to the network element user interface (NE UI)

• Log out of a network element (Procedure 2-11)

User Interface Connection Procedures 323-1501-301 Rel 1 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

OPTera Connect DX Connection Manager 323-1501-301 Rel 1 Standard Aug 2000

Connecting terminals or personal

Chapter procedure list

Connecting a VT100-compatible terminal to a network element Procedure 1-1

Connecting a terminal to an OPC Procedure 1-3

Connecting a PC to a network element Ethernet port Procedure 1-4

Configuring a network element as a host node on a TCP/IP Procedure 1-5

Enabling or disabling TCP/IP traffic on the network element Procedure 1-6

User Interface Connection Procedures 323-1501-301 Rel 1 Standard Aug 2000

Before you start

OPTera Connect DX Connection Manager 323-1501-301 Rel 1 Standard Aug 2000

Procedure 1-1 (continued)

1 Connect the LCAP or MI user interface cable to the VT100-compatible

baud rate 9600

User Interface Connection Procedures 323-1501-301 Rel 1 Standard Aug 2000

OPTera Connect DX Connection Manager 323-1501-301 Rel 1 Standard Aug 2000

User Interface Connection Procedures 323-1501-301 Rel 1 Standard Aug 2000

Pin Function Pin Function

1 DCD 6 not connected

OPTera Connect DX Connection Manager 323-1501-301 Rel 1 Standard Aug 2000

Procedure 1-2 (continued)

Before you start

User Interface Connection Procedures 323-1501-301 Rel 1 Standard Aug 2000

Procedure 1-2 (continued)

Data Terminal Ready (DTR) Override Off

Result code Display On

Command Mode Local Echo Suppression Off

Carrier detect (CD) Override Off

Power-on and ATZ Reset Software On

AT Command Set Recognition On

OPTera Connect DX Connection Manager 323-1501-301 Rel 1 Standard Aug 2000

Procedure 1-2 (continued)

8 To configure your PC for a network element point-to-point protocol (PPP)

User Interface Connection Procedures 323-1501-301 Rel 1 Standard Aug 2000

Before you start

OPTera Connect DX Connection Manager 323-1501-301 Rel 1 Standard Aug 2000

Procedure 1-3 (continued)

Cable connectors and pinouts

VT100, printer, or laptop NTCC90EB cable assembly, 20 m (65 ft) or