Optera Metro 4100-4200 Lab Manual
Optera Metro 4100-4200 Lab Manual
2
3
Local Login ‐ Physical Connectivity
RS‐232 cable
End 1 25‐Pin D Male Connector Æ CAT terminal
End 2 9‐Pin Female Connector Æ COM Port
(Desktop/Laptop)
Laptop/Desktop TN-1X
DB 9 (FEMALE) DB 25 (MALE)
2 3
3 2
4 20
5 7
6 6
7 4
8 5
4
Select Appropriate COM port
5
Duty Classes:
The TN‐1X supports three user sessions from the EC‐1 and one from the CAT
–Only
Only one system engineer login is permitted
–Either Preside EC‐1 or CAT (but not from both simultaneously)
The configuration manager and status manager classes can have more than one login
6
Menu Navigation
C fi / Vi
Config/ View_status/ Session/ Admin/Maintenance/ Diagnostic/ Logout
/ S i / Ad i /M i / Di i /L
TN‐1X /
>>
The User Interface (UI) for the TN‐1X has a text‐based hierarchical menu tree
After login a user is positioned at the top level of the menu tree
Menu items which have subordinate menu levels are suffixed with the ‘/’character
Menu items without a suffix are commands in the current menu
Menu navigation is achieved by typing the desired menu item name or a short version of
Menu navigation is achieved by typing the desired menu item name, or a short version of
this name
UI is line oriented, and as such it requires a carriage return CR after each user request
The user interface is not case sensitive
There are three methods of entering commands:
1.The user can type the entire command, such as ‘config’
2.The user can type three or more letters to uniquely identify the command
p f
Example: First 3 letters of the command name
7
3.The user can type a shortcut for the command
–Displayed in upper case in the command name
Displayed in upper case in the command name
–If numbers are included in the shortcut, the entire shortcut is shown in square brackets after the
command name
Two special characters can be used to move around the menu system:
1.The asterisk character (*)
Moves the user up one level in the command hierarchy
2.The tilde character (~)
Moves the user to the top (root) of the command hierarchy
T
Try navigating thru the Menu listed in the following pages
i ti th th M li t d i th f ll i
Go up One level Æ *
Go up x level Æ x*
Go to root Æ ~
Access a menu
Menu shortcuts (Alphabets highlighted in caps/Numeric value within square brackets)
Note: All commands will work only at the respective menus. If a command is entered at the wrong menu an
appropriate error message will be displayed. If one is not sure of the menu prefix all the commands given in
the manual with the ‘~’ sign (tilde sign).
h l h h ‘ ’ ( ld )
8
1.Duty Classes
Logout can occur either manually or automatically
1.Manual logout
•This is achieved using the Logout command, which is available from the top‐level (root)
menu
•No confirmation is required
TN‐1X/
>>l ¿
Bye;
2.Automatic logout
•This occurs after no activity has occurred for a predetermined period
•Automatic logout period can be adjusted using ‘Session’ menu commands
9
10
11
Example: Equip
Trib Card 2m
e ↵
2m ↵
12s3 slot no. ↵
12
Data Communication Channels
Step 1.9 Enable Regenerator LAPD link service
~c o s nr aggregate_port ↵
Disable Regenerator LAPD link service
s or aggregate_port ↵
Enable Multiplexer LAPD link service
s nm aggregate port
aggregate_port ↵
Disable Multiplexer LAPD link service
s om aggregate_port ↵
View LAPD Link Service Configuration
s v ↵
Note: LAPD – Link Access Procedure –D Channel is a protocol used to
exchange information through the Data Communications Channel
(DCC)
13
Step 2.2 :Configure transmitted path trace
14
Step 2
2.5
5 Transmit/Receive override values
Transmit Override
to synchronization source quality level
Receive Override
ro synchronization source quality level
Synchronization switching
Forced Switching
n synchronization source ↵
Manual Switching m o ↵
s m synchronization source ↵
Menu Æ View/Sync_Source_status
v ss ↵
Menu Æ Config/Sync_source
st ↵
15
OPTera Metro 4100/4200 OMA&P 6/24/2010
1. Source/protection payload
When setting up a protected connection, two complete traffic paths are provisioned. The source and
protection channels are identified at each end of the connection.
2. Working/standby path
One of the traffic paths is selected to drop traffic and is labelled as the working path. The other path
carries identical traffic and is available for selection in the event of a failure in the working path. This is
labelled as the standby. If a protection switch occurs the traffic is selected from the standby path. When
the protection switch is complete the labelling of the working and standby paths is reversed.
reversed
If a power loss occurs the current nomination of the working and standby paths is lost. On a cold restart
all connections are re‐established using the source payload.
3. Connection Signal Fail Alarm
If both the source and protection payloads on a protected connection have a fault condition which would
normally cause a switch trigger, the connection service cannot be maintained. This condition causes a
Signal Fail alarm to be raised against the connection drop point instance; for a VC‐4 connection the alarm
is “HP‐SF”, for a VC‐3 or VC‐12 connection the alarm is “LP‐SF”.
RELIANCE INFOCOMM For internal
use only 16
OPTera Metro 4100/4200 OMA&P 6/24/2010
The payload connections between the ports are configured both in terms of the connection type and the
traffic rate (payload) allocated to the connection.
The traffic rate at each aggregate or tributary port contains a collection of any of the 2 Mbit/s, 140 Mbit/s,
VC‐4, VC‐3 or VC‐12 payload types up to the maximum port capacity. The available connection types are
through, add/drop, tributary to tributary, dual tributary to aggregate, and ring to ring.
In future releases of OPTera Metro 4100, software only upgrades will provide the following functions;
unidirectional connections, unidirectional drop and continue connections, unidirectional broadcast,
asymmetric PPS connections,
connections and matched node connections.
connections
The limit to the quantity of connections is a logical limit. For example a VC‐4 connection cannot be made to a
terminated VC‐4 that has VC‐3 (or VC‐12) connections. Or a VC‐3 connection cannot be made to a VC‐3 used
for another connection.
RELIANCE INFOCOMM For internal
use only 17
Unprotected Add/Drop connection
p p
Syntax
Step : 2.8 Connect Aggregate Port 1‐Payload Tributary Port‐Payload
Command composition – Aggregate Port Slot number‐Port Number‐AUG number‐KLM
Number (Payload)
Command composition – Tributary Port Slot number‐Port number
( Example:
c s6‐1‐j1‐k112
s6 1 j1 k112 s2 1
s2‐1 ↵)
18
Protected Add/Drop
p connection
(Example C S11‐1‐J1‐k212 S6‐1‐J3‐k242&S8‐1‐J1‐K242)
4. Aggregate to Trib and Trib
Step 3.2 Menu Æ Config /Connection
Syntax ‐Connect Aggregate Port‐payload Trib Port 1‐ Payload&Trib Port 1 – Payload
(Example C S6‐1‐J4‐k121 S11‐1‐J1‐K321&S12‐1‐J1‐k321)
19
21
22
Step 3.2 Disable PPS
p
o aggregate slot‐port | tributary port
view protection status
st ↵
Menu Æ Viewstatus
vc ↵
PPS has 2 Modes – UI Selectable
1.Automatic
2.Manual
Manual Protection switching
Step 3.4 Menu Æ Maintenance/Operation/Pps
~ m o p ↵
a Manual Switching to Aggregate Port A ↵
b Manual Switching to Aggregate Port B ↵
Note: Default tributary port setting is ‘ALL’
23
Step
p 3.6 Protection switching
g
Forced Switching
r f port ↵
Manual Switching
r m port ↵
Lockout
r l port ↵
Exercise
r e port ↵
Release protection switching
r r port ↵
24
25
OPTera Metro 4100/4200 OMA&P 6/24/2010
Before an SEMF switch occurs, the standby card is checked. The table below shows the conditions which
cause a switch request and the conditions which prevent a switch occurring.
Before removing the aggregate card with the active SEMF, control must pass to the standby aggregate card.
The SEMF changeover operation is equivalent to a warm start of the new active aggregate. The NE has no
management function or data communications during the change over period. To allow the configuration to
stabilize leave an interval of 15 minutes before another SEMF switch.
CAUTION
Risk of loss of data
An SEMF protection switch causes a temporary loss of traffic. Maximum switching time is 140 ms.
RELIANCE INFOCOMM For internal
use only 26
OPTera Metro 4100/4200 OMA&P 6/24/2010
RELIANCE INFOCOMM For internal
use only 28
OPTera Metro 4100/4200 OMA&P 6/24/2010
1. When a local loopback is set up, the serial data send signal feeds back to the serial data receive circuit.
The serial data send signal continues on to the laser transmitter; the transceiver blocks the incoming
serial data receive signal from the laser receiver.
2. When a remote loopback is set up, the serial data receive signal feeds back to the serial data transmit
circuit. The serial data send signal continues on to the signal processing circuits however the transceiver
blocks the serial data transmit signal.
3
3. A remote optical loopback applied at a remote NE can cause loss of communications between the NE and
the management platform.
4. Application of a local or a remote loopback on an an SDH port raises the RS‐Loopback‐ON alarm.
RELIANCE INFOCOMM For internal
use only 29
OPTera Metro 4100/4200 OMA&P 6/24/2010
1. A local loopback facility is available on each electrical tributary port. Outgoing data routes back to the
receiver,
i and
d transmits
i to the h line.
li
2. A remote loopback facility is also available on each tributary port. Incoming data routes back to the
transmitter, and passes through to the multiplexer.
3. Application of a local or a remote loopback on an an SDH port raises the RS‐Loopback‐ON alarm.
Application of a local or a remote loopback on a PDH tributary port raises the PPI‐Loopback‐ON alarm.
4. When a local loopback is set up, the serial data send signal feeds back to the serial data receive circuit.
The serial data send signal continues on to the laser transmitter; the transceiver blocks the incoming
serial data receive signal from the laser receiver.
5. When a remote loopback is set up, the serial data receive signal feeds back to the serial data transmit
circuit. The serial data send signal continues on to the signal processing circuits however the transceiver
blocks the serial data transmit signal.
6. A remote optical loopback applied at a remote NE can cause loss of communications between the NE and
the management platform.
7. Application of a local or a remote loopback on an an SDH port raises the RS‐Loopback‐ON alarm.
RELIANCE INFOCOMM For internal
use only 30
A loopback facility on the multiplexer enables the user to perform test
procedures for fault finding.
Loopback can be Local towards network or Remote towards Customer Network
Element.
31
Example
p
24h ppi_cv mo a ↵
The above command turns off the 24-hous monitoring of “MS_Ne”
parameter for aggregate port A.
Step 3.9 View performance logs
Menu Æ View_status / perF_mon
>> ~ v pf -1
1 ↵
Note: -1 facilitates the access to the latest log.
32
OPTera Metro 4100/4200 OMA&P 6/24/2010
RELIANCE INFOCOMM For internal
use only 33
34
35
Step 4.2: Backup procedure
Initialize Backup
Menu ÆAdmin / Confg_tbl /Back Up
>>~a c bu backupfilename.txt ↵
Click Transfer (shortcut Alt+T) on the HyperTerminal menu and select “Receive File”. Set
appropriate configuration in the dialog box provided:
36
Once the procedure complete message will be displayed as backup completed.
37
38
OPTera Metro 4100/4200 OMA&P 6/24/2010
RELIANCE INFOCOMM For internal
use only 41